Bug with multicast RTSP session. bad "Transport:" header

[tonimoro]

Hi all,

i encountered a problem with the lastest versions of VLC (problem present in the 1.1.4 version and still present in 1.1.7) during the dialog with a RTSP server which provides a multicast video session. In fact VLC sends to the server a teardown request, in log messages console we can see the following error "live555 error: SETUP of'video/H264' failed Missing or bad "Transport:" header"

This bug seems to be already known but for me it is not fixed. http://trac.videolan.org/vlc/ticket/4129
In fact, VLC doesn't respect anymore the transport part of RFC 2326 http://www.ietf.org/rfc/rfc2326.txt.
It appears that VLC stop the dialog after the setup reply of the server. In this answer,the server sends the port numbers with the following expression "port=...." which is the correct response. VLC now seems to waiting for a response like that : "server_port=..." which is only valid for unicast session. You can see below a capture of this dialog :

============= VLC REQUEST ===============
SETUP rtsp://10.11.16.32/test/trackID=1 RTSP/1.0
CSeq: 4
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)
Transport: RTP/AVP;multicast;client_port=5000-5001

=============== RTSP ANSWER ================
RTSP/1.0 200 OK
CSeq: 4
Server: (Argos)
Date: Friday, March 25, 2011 09:36:37 GMT
Session: 42
Transport: RTP/AVP;multicast;port=5000-5001

============== VLC REQUEST ===============
TEARDOWN rtsp://10.11.16.32/test/ RTSP/1.0
CSeq: 5
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)
Session: 42


in chapter 12.39 of the RFC2326 the terms port, client_port ans server_port are defined like this :
«
port:
This parameter provides the RTP/RTCP port pair for a multicast
session. It is specified as a range, e.g., port=3456-3457.

client_port:
This parameter provides the unicast RTP/RTCP port pair on
which the client has chosen to receive media data and control
information. It is specified as a range, e.g.,
client_port=3456-3457.

server_port:
This parameter provides the unicast RTP/RTCP port pair on
which the server has chosen to receive media data and control
information. It is specified as a range, e.g.,
server_port=3456-3457.
»

So, the server responseis valid. Moreover, I try with VLC 1.1.2 and it's ok with this version.
I also make a patch on my RTSP server (it answers "client_port" instead of "port" for multicast session -> vlc 1.1.7 plays the video : no "bad transport header error").

Thanks in advance for the fix.

[Sébastien Escudier]

Hi,

could you share a test url so I can reproduce the problem ?
And please show full logs of vlc and live555.

[tonimoro]

Here are the complete VLC full logs :

main debug: processing request item rtsp://10.11.16.32/test node Liste de lecture skip 0
main debug: resyncing on rtsp://10.11.16.32/test
main debug: rtsp://10.11.16.32/test is at 1
main debug: starting new item
main debug: creating new input thread
main debug: Creating an input for 'rtsp://10.11.16.32/test'
main debug: thread started
main debug: using timeshift granularity of 50 MiB
main debug: using timeshift path 'C:\DOCUME~1\MoreauAn\LOCALS~1\Temp'
main debug: thread (input) created at priority 1 (../.././src/input/input.c:214)
main debug: `rtsp://10.11.16.32/test' gives access `rtsp' demux `' path `10.11.16.32/test'
main debug: creating demux: access='rtsp' demux='' path='10.11.16.32/test'
main debug: looking for access_demux module: 1 candidate
qt4 debug: IM: Setting an input
live555 debug: RTP subsession 'video/H264'
live555 error: SETUP of'video/H264' failed Missing or bad "Transport:" header
live555 debug: setup start: 0.000000 stop:0.000000
live555 error: Nothing to play for rtsp://10.11.16.32/test
main debug: no access_demux module matching "rtsp" could be loaded
main debug: TIMER module_need() : 309.000 ms - Total 309.000 ms / 1 intvls (Avg 309.000 ms)
main debug: creating access 'rtsp' path='10.11.16.32/test'
main debug: looking for access module: 1 candidate
main debug: net: connecting to 10.11.16.32 port 554
main debug: connection succeeded (socket = 1628)
access_realrtsp debug: rtsp connected
access_realrtsp warning: only real/helix rtsp servers supported for now
main debug: no access module matching "rtsp" could be loaded
main debug: TIMER module_need() : 213.000 ms - Total 213.000 ms / 1 intvls (Avg 213.000 ms)
main debug: waitpipe: object killed
main error: open of `rtsp://10.11.16.32/test' failed: (null)
main debug: thread ended
main debug: dead input
main debug: thread times: real 0m0.515625s, kernel 0m0.000000s, user 0m0.000000s
main debug: changing item without a request (current 1/2)
main debug: nothing to play
qt4 debug: IM: Deleting the input
main debug: TIMER input launching for 'rtsp://10.11.16.32/test' : 546.000 ms - Total 546.000 ms / 1 intvls (Avg 546.000 ms)

[tonimoro]

and the corresponding RTSP dialog :


============== VLC REQUEST ===============
OPTIONS rtsp://10.11.16.32/test RTSP/1.0
CSeq: 2
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)


=============== Server ANSWER ================
RTSP/1.0 200 OK
CSeq: 2
Server: (Argos)
Date: Monday, March 28, 2011 08:07:38 GMT
Public: DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE


============== VLC REQUEST ===============
DESCRIBE rtsp://10.11.16.32/test RTSP/1.0
CSeq: 3
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)
Accept: application/sdp


=============== Server ANSWER ===============
RTSP/1.0 200 OK
CSeq: 3
Server: (Argos)
Date: Monday, March 28, 2011 08:07:38 GMT
Content-Base: rtsp://10.11.16.32/test/
Content-Length: 483
Content-Type: application/sdp

v=0
o=- 1301299595 1301299595 IN IP4 10.11.16.32
s=test
u=rtsp://10.11.16.32/test
c=IN IP4 225.100.10.10/3
b=AS:2134
t=0 0
a=control:*
a=range:npt=now-
m=video 10000 RTP/AVP 96
b=AS:2134
b=RR:80025
b=RS:26675
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; profile-level-id=4d4015; sprop-parameter-sets=Z0
1AFY2NICwS2ApEAAADAAQAAAMAy4EAAehIAAehJ/GOMCAAPQkAAPQk/jHDtCRKJA==,aOpTJIA=
a=framesize:96 352-288
a=framerate:25.000000
a=control:trackID=1
a=TIAS:2000000
a=maxprate:400


============== VLC REQUEST ===============
SETUP rtsp://10.11.16.32/test/trackID=1 RTSP/1.0
CSeq: 4
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)
Transport: RTP/AVP;multicast;client_port=10000-10001



=============== Server ANSWER ================
RTSP/1.0 200 OK
CSeq: 4
Server: (Argos)
Date: Monday, March 28, 2011 08:07:38 GMT
Session: 44
Transport: RTP/AVP;multicast;port=10000-10001




============== REQUEST ===============
TEARDOWN rtsp://10.11.16.32/test/ RTSP/1.0
CSeq: 5
User-Agent: LibVLC/1.1.7 (LIVE555 Streaming Media v2011.01.06)
Session: 44


It's not possible for me to provide a test url so i hope it's enough to see the problem. I can also send the logs with my "patched"version which only replaces in the setup answer the word "port" by "server-port" but works without any problem.

[Sébastien Escudier]

reading at live555 source code, it looks like a "destination" field is required in case of multicast, in the Transport header.
So the problem is not with the "port" param which is well recognized.

[tonimoro]

Thanks for the reply. i added the destination field and now it's work fine. In fact, in older versions, i suppose that the connection field present in the Describe answer was sufficent to acquire a multicast stream.