TCP stream at T8705 decoder

[a573net]

I want to connect with a TCP stream on a T8705 decoder.
If anyone knows how to connect to a TCP stream, please let me know.

The T8705 opens a UDP stream by default when an RTSP connection is made.
Burst packets from the gigabit-connected camera cause UDP packet loss because the T8705 has a 100 Mbps connection.
This situation can be resolved if the T8705 can make a TCP connection.
I don't care about RTSP. You can also use HTTP over RTSP. I don't want to use UDP.

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @a573net ,
I hope you have tried adding an Axis camera using the following options while adding video sources in Axis T8705:

[a573net]

Hi vivekatoffice,

Thank you for your reply.
I understand that you have TCP in the GUI. You proved that the T 8705 can make TCP connections. Thank you.

However, the information I presented was not enough.
I control my equipment through APIs, not GUIs.
http://www.axis.com/vapix-library/subjects/t10175981/section/t10122502/display

The API specifies the RTSP URL and the default UDP-unicast is chosen.
Looking for ways to specify TCP via API.

[vivekatoffice]

Hi @a573net ,
Thank you for adding more information.

Please test with the following parameter and check:

Agree with you on missing information in VAPIX documentation. Used Google Chrome Inspect feature link to know about these APIs.

Note: Please keep in mind that these are not documented on VAPIX documentation and may change in future

[a573net]

Hi vivekatoffice,

Thank you for waiting.
I tried many things in a production environment. Finally, I chose to use MJPEG for HTTP communication.

I tried the pattern below, but the decoder was still communicating UDP.

"rtspTransportMode":"Tcp"
"rtspTransportMode":"Http"
"rtspTransportMode":"Tls"
"RtspTransportMode":"Tcp"
"rtspTransport":"Tcp"
"Transport":"Tcp"
"protocol":"Tcp"
"protocols":"Tcp"

The decoder is not likely to recognize these attribute information correctly.

Finally, it was changed to TCP by allowing HTTP connections.

"url": "http://198.51.100.1/axis-cgi/mjpg/video.cgi?resolution=1920x1080&fps=15&compression=50",
"videoCodec": "mjpeg",

Thank you for your support!

[vivekatoffice]

Hi @a573net ,
Great 👍
Using MJPG stream is a great solution but may not work if audio is required.

I am adding the Mp4 container over HTTP URL for reference:

http://198.51.100.1/axis-cgi/media.cgi?container=mp4&resolution=1920x1080&fps=15&compression=50

Reference

[a573net]

Hi vivekatoffice,

Sound is unnecessary in our environment. It's been a few days since I switched to MJPEG, and it works fine.

I forgot to write it down, but I also try the pattern below.
In this setting, the decoder accepts the setting, but HDMI displays a black screen. The decoder error screen is not displayed either.

"url": "http://198.51.100.1/axis-cgi/media.cgi?container=mp4&resolution=1920x1080",
"videoCodec": "h264",

I will try "container=mp4" again the next time I get a chance to go to the site.