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

[Bob Bischan]

Ross,

Very nice...I look forward to seeing how this evolves.

I noticed that you implemented the ability to specify stream suffix! I will
be setting up a new test environment with the latest code base to work
through these API changes. I'll provide feedback, should I encounter
anything of interest.

Since this an initial draft, I assume your still open for
comments/suggestions :-)

- 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.
- Not sure if this would make sense, but would an UN-REGISTER method
further enhance the capabilities of Proxy Server? This would allow for a
perpetually running server that could dynamically REGISTER/UN-REGISTER
streams as needed.

Bob


On Fri, Oct 18, 2013 at 5:03 AM, Ross Finlayson <finlayson at live555.com>wrote:

> FYI, I have just submitted to the IETF a new Internet-Draft document that
> describes our new custom "REGISTER" RTSP command (that we use in our proxy
> server implementation).  You can find a copy online at
> http://tools.ietf.org/html/draft-finlayson-rtsp-register-command-00
>
> I have also released a new version (2013.10.18) of the "LIVE555 Streaming
> Media" code that changes the implementation to conform to this document.
>  In particular:
> - There are no longer separate "REGISTER" and "REGISTER_REMOTE" commands.
>  Now, there's only "REGISTER".  An optional Boolean parameter
> "reuse_connection" - in the RTSP "Transport:" header - can be used to
> specify whether the recipient should reuse the TCP connection.
> - There is a new optional parameter "proxy_url_suffix" (again, in the
> RTSP "Transport:" header) that can be used to specify the URL suffix that
> the receiving proxy server should use to advertise the proxied stream.
>
> If you are "REGISTER"ing one of your "RTSPServer"s own streams (e.g., with
> a proxy server), then note that the "RTSPServer::registerStream()" API has
> changed.
>
> If you are using a 3rd-party application to construct and send "REGISTER"
> commands - as Bob Bischan is doing - then note that
> - The command to send is now "REGISTER", not "REGISTER_REMOTE", and
> - There are optional parameters that you can specify in a RTSP
> "Transport:" header.
>
>
> 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/04b94e98/attachment-0001.html>