DVB Media Server - SAT>IP via TCP

[easy4me]

Good day,

 

I would like to enable "RTP/AVP/TCP transport" mode for the DMS SAT>IP Server. How do I enable the TCP support in DMS?

 

Thanks

[Griga]

It is available since Media Server 3.3.1.9 Beta. Read the "Added: RTSP (Sat>IP) Client: Client-side support for TCP interleaved transport mode" section and also the following.

 

It must be configured on the client side, not in the server, because the client requests the transport mode. The server only responds to the request, either by using the mode or with an error code, if the mode is unknown.

 

[easy4me]

Unfortunately, I'm getting the following error messages after enabling the TCP support in tvHeadend for the DMS SAT>IP tuner. I already installed DMS 3.3.1.12

 

 

2026-02-18 20:05:59.329 satip: SAT>IP DVB-C Tuner #2 (192.168.8.51@TCP) - RTSP SETUP error -5 (Input/output error) [6-404]

[Griga]

vor 10 Stunden schrieb easy4me:

Unfortunately, I'm getting the following error messages after enabling the TCP support in tvHeadend for the DMS SAT>IP tuner. I

 

Confirmed. Tvheadend doesn't like a detail in the Media Server's response header:

 

Zitat

CSeq: 1
Session: 888;timeout=0
Transport: RTP/AVP/TCP;interleaved=0-1
com.ses.streamID: 1
Server: DVBViewer Media Server 3.3.1.13
Date: Thu, 19 Feb 2026 05:50:54 GMT

 

The timeout parameter specifies the interval in seconds between messages sent by the client confirming that it is still alive. For TCP it is not really needed, because (in contrast to UDP)  the server will notice anyway if the connection breaks. Consequently VLC does not send such messages in RTP/AVP/TCP mode. However, if the server expects them, it will stop delivering data after the timout interval has elapsed. That's why I've set the interval to 0 (= keep alive disabled) for RTP/AVP/TCP mode. But now tvheadend is unhappy with it. Sometimes it's hard to keep all kinds of clients satisfied

 

Anyway, I've added you as recipient to a PM where I provide Media Server test versions. The latest upload tries to detect the VLC as RTSP RTP/AVP/TCP client and sets the timeout value for other clients to > 0.

 

BTW: Please note that you should turn off using the frontend (fe) parameter in tvheadend. It is not compatible with the dynamic tuner allocation performed by the Media Server and the possibility to randomly change the tuner order in the Media Server's device list (see here). There is a setting in the tvheadend web interface for achieving it: Configuration -> DVB Inputs -> TV Adapters -> Select the Sat>IP Server entry -> FE supported (should be off)

 

You can check in the svcdebug.log (see DVBViever configuration folder) if tvheadend drops the fe=... parameter by looking for entries like

 

Zitat

19.02.26 06:33:11.211 SETUP                200              fe=1&src=1&&freq=12187.5&sr=27500&msys=dvbs&mtype=qpsk&pol=h&fec=34&ro=0.35&pids=0

 

[easy4me]

Thanks, the TCP mode is working now. But after disabling FE parameter, I'm getting another RTSP setup error, so I had to turn it on again.

[Griga]

vor 9 Stunden schrieb easy4me:

But after disabling FE parameter, I'm getting another RTSP setup error,

 

Strange. Here it's just the other way round. I would need more insight in your configuration, at least a zipped and attached svcdebug.log, for checking what's going on.

 

Be sure that letting tvheadend use the fe parameter will cause problems sooner or later, particularly if other clients are also accessing the Media Server or if the order of tuners in your device list gets changed for some reason.