> 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.
Yes, you're correct - the server needs to be fixed so th
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 w
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
"Media
Title: Samsung Enterprise Portal mySingle
Dear sir,
I am implementing bidirectiotnal audio connection based on the ONVIF specification.
But ONVIF spec use a extension of RTSP. I couldn't implement it with live555.
The procedure is simple as below.
== Server with onvif backchannel
