[Live-devel] Proxy Server REGISTER option

[Bob Bischan]

Ross,

Works perfectly!

Just a few thoughts for your consideration:

1. Do you think the naming convention (registeredProxyStream-N) for
REGISTERED streams will adequately support most users / use cases? This has
been convenient in my particular case and allows me to proceed  with my
current efforts, however, I'm not sure it is the best approach. Would
having an option that allows the stream name to be specified in the
REGISTER command make sense? Default behavior would then fall back to Proxy
Server parsing the URL into prefix/suffix as originally implemented.

2. A small item to note. During the course of my testing (using several
different client implementations)  I found a problem when trying to
REGISTER_REMOTE since it is not explicitly list in the OPTIONS list from
Proxy Server. Some client's (3rd party applications) may fail with "Method
Not Allowed". For me it is not an issue...I simply use a client
implementation that does not retrieve the OPTIONS list before sending the
REGISTER_REMOTE command.

Thanks again for your time and efforts. I'm going to close this thread for
now...will open new ones as I move forward with testing / evaluation.

Bob


On Tue, Oct 8, 2013 at 7:09 PM, Ross Finlayson <finlayson at live555.com>wrote:

> I did not see a way to send a REGISTER command to the Proxy Server.
>
>
> We have code that allows a RTSP server to register one of its *own*
> streams with a proxy server (or with a client application).  We don't have
> code that allows some 3rd-party application to send a "REGISTER_REMOTE"
> (not "REGISTER") command to a proxy server (or client application).  We
> might provide this at some point, but it's not a high priority.
>
> The main motivation for this functionality was to allow a server - located
> behind a NAT in a non-public portion of the Internet (i.e., without a
> publically accessible URL) - to advertise its stream to a
> (publically-accessible) proxy server (and thereby to the public Internet).
>
>
> Is there any chance that the -t option is not being processed for streams
> that are being registered?
>
>
> Yes, you're correct - this was a bug/deficiency in the code.
>
> I've just installed a new version (2013.10.09) of the "LIVE555 Streaming
> Media" code that should fix this.
>
>
> 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/20131009/2132449c/attachment-0001.html>