[FFmpeg-devel] Realmedia patch

Luca Abeni lucabe72
Tue Sep 9 17:36:32 CEST 2008

Hi Ronald,

Ronald S. Bultje wrote:
>>> As for the transport, it can always be x-pn-tng for Real servers
>> Are you really sure about this? I've seen real servers handling this
>> properly (that is, accepting requests with the correct "Transport:"
>> tag and replying with a correct "Transport:").
> SETUP rtsp://streamr.hitpops.jp/ngc/mov/m0609.mov/streamid=0 RTSP/1.0
> Transport: x-pn-tng/TCP;mode=play
> If-Match:
> RealChallenge2: d5273de0821265735b2910a6cbe0406201d0a8e3, sd=d38651c4
> CSeq: 5
> --
> line='RTSP/1.0 200 OK'
> line='CSeq: 5'
> line='Date: Mon, 08 Sep 2008 21:11:37 GMT'
> line='Session: 276998441-5'
> line='Reconnect: true'
> line='RealChallenge3: 1f1f861dfc36d2d379d74c951ba1f8bd4f213d09,sdr=18fd741f'
> line='RDTFeatureLevel: 2'
> line='Transport: x-pn-tng/tcp;interleaved=0'
> The resulting stream is RTP, not RDT.

I did a little test with this URL, capturing the traffic with wireshark.
And wireshark is telling me that the protocol encapsulated inside the RTSP
connection is actually RDT, not RTP. I have no time to perform other tests,
but wireshark is detecting "RDT packet (data)" with sequence numbers,
timestamps, etc...

So, I guess real is less broken than what it seems: it is not failing
with "x-pn-tng/tcp" just because it supports this "X-SorensonVideo" in RDT.

This seems to confirm that payload type and transport protocol are really


More information about the ffmpeg-devel mailing list