Hi Ross,
Actually the "extension" is implemented in terms of RFC 2326 by using
"Require" header (12.32 Require).
So the question is how to get these "Require" headers from OPTIONS
request and respond with 200 OK or 551 Option not supported.
The second part of question is how to make a track with "a:sendonly"
attribute and accept data. The reverse media transport is part of RTP
standard and used in SIP protocol. I suppose the only implication is
when backchannel interleaved over TCP, but liveMedia should handle it to
process RTCP feedback.
Best wishes,
Yuri
On 14.04.2012 12:53, Ross Finlayson wrote:
Because - as you noted - these extensions are not part of the RTSP
standard, we don't support them. Also, unfortunately, it would not be
possible to support them without modifying (not just subclassing) the
existing LIVE555 library code. In particular, you would need to
reimplement the "MediaSubsession::initiate()" function. For
'backchannel' subsessions, you would need to create an appropriate
"RTPSink" subclass, rather than a "RTPSource" subclass that the
existing code always does.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
