Jump to content

Strange RTSP Port Change


bounguine

Recommended Posts

One question.

In RS I use port 555 for RTSP broadcasting.

 

There's a strange thing.

In DVBViewer Pro I have 2 RTSP Network devices for DVB-C, 2 for DVB-T2 and 2 for DVB-S.

All have port 555 for connection.

But one of DVB-S RTSP devices automatically changes port to 556, when DVBViewer Pro starts.

 

In VLC and TVHeadend as a DVB>IP client DVB-C and DVB-T2 muxes taken from rtspchannels.m3u are scanned without problems.

But for DVB-S I have to change port  555 to 556 manually for starting broadcasting in strings like:

rtsp://192.168.1.139:555/?src=1&freq=11747&msys=dvbs2&plts=off&fec=34&pol=v&ro=0.35&sr=27500&mtype=8psk&tnr=1,11747,27500,10750,0,1,9,3,610,609,608,2013,6,360,25,3,2,253,-1,360&pids=0,16,17,18,20,608,609,611,610

 

Why?

Link to comment
vor 11 Stunden schrieb bounguine:

But one of DVB-S RTSP devices automatically changes port to 556, when DVBViewer Pro starts.

 

It happens on RTSP device initialisation if DVBViewer can't connect to the server. In this case an UPnP M-SEARCH request is used to find the server in the network. The port is part of the reply that DVBViewer gets from the server. This behaviour can be disabled by using the "Automatic RTSP server IP:Port detection" tweak (-> launch Tweaker.exe in the DVBViewer installation directory).

 

The RS changes the configured port automatically if it is already occupied by another RTSP server on the same PC, e.g. the Windows Media Player. However, I can't tell you why it only happens in case of DVB-S.

 

The described events should show up in the DVBViewer.log (only if DVBViewer is run in debug mode) and in the svcdebug.log. Both files are located in the configuration directory.

 

Link to comment

Thanks.

I did this and now I have 555 for everything.

DVB-T2 and DVB-C are working without problems in DVBViewer and VLC.

DVB-S channels are broadcasted withot audio and video.

Tiners are locked.

svcdebug.log

Link to comment
×
×
  • Create New...