[Live-devel] Modifications to the RTSP "REGISTER" command and API

[Bob Bischan]

Understanding the author's original intent and design philosophy is key,
especially when it comes to using their software :-)

In regards to the registering RTSP-over-HTTP back-end servers...I do not
anticipate a need for this, however, your clarification on it's
implementation within Proxy Server is good to know.  RTP/RTCP over UDP is
what I'm currently using and it seems to work the best in my particular
case.

Embedding code on the Axis camera to call home is an excellent idea !

As a side note: Proxy Server is running quite well !


Bob


On Fri, Oct 18, 2013 at 1:01 PM, Ross Finlayson <finlayson at live555.com>wrote:

> - Proxy Server -T option does not allow for specifying a unique port per
> stream. In NAT cases streams would have different ports. Would it be
> possible to have this option for streams that will be using RTSP over HTTP.
>
>
> FYI, right now back-end RTP/RTCP-over-RTSP-over-HTTP tunneling works only
> for 'back-end' streams that are specified on the command line.  It does
> *not* work for 'back-end' streams that have been "REGISTER"ed (even if the
> "-T <http-port-num>" option was given on the command line).
>
>
> The reason for this, BTW, is that the primary intended purpose for the new
> "REGISTER" command was to allow a back-end server to register it's *own*
> stream, using the "RTSPServer::registerStream()" method, and to allow the
> receiving client (or proxy server) to reuse the TCP connection on which the
> "REGISTER" command was sent.  If this is done, then you don't need
> RTP/RTCP-over-RTSP-over-HTTP tunneling at all, because you already have a
> TCP connection set up.  You can just to RTP/RTCP-over-RTSP tunneling (over
> that same TCP connection) instead.
>
> The way that you're using the "REGISTER" command - to allow a 3rd party to
> register a back-end stream with a proxy server - is a nice way to use the
> mechanism, but it wasn't my primary purpose for developing it.
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20131018/5fa93b63/attachment-0001.html>