[FFmpeg-devel] [rtsp/rtp] update rtp to support rfc3550
Sat Apr 17 10:52:08 CEST 2010
On 04/16/2010 10:53 PM, Martin Storsj? wrote:
> On Fri, 16 Apr 2010, Luca Barbato wrote:
>> For google it's relatively easy to report and hopefully have them update
>> their server. For dss I'm afraid it will be quite a pain.
> Yeah, dss generally is more or less stalled as far as I've understood.
> Patching it in yourself could be more or less problematic, too, I'm not
> familiar enough with the codebase to comment on that.
... dss is written in a C++ a bit hard to follow with a bit complex file
> Hmm, how would you fall back if the peer didn't work with rfc3550? For
> google rtsp that gives an error on the SETUP, one could simply retry with
> a new SETUP with a normal port pair, but if DSS simply gives OK but
> interprets it as something else than what was sent, we would have to redo
> the SETUP for that stream - is that ok within RTSP?
> Also, if acting as a server, how do we know if it's appropriate to reply
> to a client's SETUP with a non-consecutive port pair?
the server side could be configured I think.
> Both with these questions in mind, and being primarily a DSS user, I'd
> prefer trying to allocate normal port pairs initially, if possible, and
> only then revert to unmatched pairs ? la rfc3550 if unable to get a
> working normal pair after a few attempts.
it's sensible indeed.
More information about the ffmpeg-devel