> My Scenario is like below,
> Device1(Camera) ---> NAT(Router) -> Internet ---> Device2.
>  
> Device2 wants to initiate a streaming request to Device1 using 
> openRTSPclient. It is not possible to make since Device1 is in private 
> network.
> I googled it, I found it is possible using -R option in openRTSPclient with 
> proxyserver setup. I found this link 
> http://lists.live555.com/pipermail/live-devel/2013-June/017112.html 
> <http://lists.live555.com/pipermail/live-devel/2013-June/017112.html>,
> I am trying to use the registerRTSPStream/live555ProxyServer/openRTSPClient 
> commands. I didn't achieve this setup.
> 

There are two possible ways to do what you want:
1/      “Device1(Camera) -> a RTSP client application that understands our 
“REGISTER” command, or
2/       “Device1(Camera) -> the “LIVE555 Proxy Server” (run with the “-R” 
option) -> one or more RTSP clients.
You probably want option 2/, unless you have complete control over which RTSP 
client(s) get used.

In either case, you will need to update your “Device1(Camera)” so that you call 
“RTSPServer::registerStream()” on it, to tell it to ‘register’ the stream with 
the RTSP client application (in case 1/) or with the “LIVE555 Proxy Server” (in 
case 2/).  Because ‘Device1(Camera)’ is in a private network, you *won’t* be 
able to use the “registerRTSPStream” demo application to do this; instead, you 
need to use "RTSPServer::registerStream()”, so that the remote client (or proxy 
server) can reuse the TCP connection from the server when it later sends its 
own RTSP commands to request the stream.

(Unfortunately this is as much help as I can give you here ‘for free’ on this 
mailing list.  If your company is interested in having me consult further on 
your project, then please have your management let me know (via separate 
email).)

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

Reply via email to