Dear Ross Finlayson, Thank you for you response. Really I didn't observe that there is the function registerStream. And I started to integrate the sending REGISTER process into the RTSPServer process by myself :-). I tested the function. And it works very well with openRTSP (as RTSPclient) and TestOnDemandRTSPServer.(as RTSPserver)
Hopefully the Live555 proxy (client side) also handles well the REGISTER as in openRTSP. ? I wonder if I put an openRTSP as a client to connect to the above live555 RTSP (the server side), what changes do I have to make to ensure that the openRTSP via live555 proxy can command and receive the stream from the TestOnDemandRTSPServer behind NAT ? Currently how does the live555 proxy handle the asynchron of receiving REGISTER command from the TestOnDemandRTSPServer (client side of the proxy) and of receiving OPTION / DESCRIBE command from the openRTSP (server side of the proxy)? Many thanks in advance for your help Best regards Son Vào Th 4, 5 thg 2, 2020 vào lúc 04:29 Ross Finlayson < [email protected]> đã viết: > The “registerRTSPStream” application can be used to register a stream with > a remote RTSP client. However, this cannot be used to connect a server > (behind a NAT) to a (public) client, reusing the TCP connection. To do > that, you would need to send the RTSP “REGISTER” command from *within* the > server itself. > > If your RTSP server - behind a NAT - is an ‘off the shelf’ device (such as > a network camera) that you cannot change, then you can’t use this feature. > Instead, you would need to change the implementation of the server. I.e., > this feature is intended to be used by *developers* of RTSP servers. > > However, if you are developing a RTSP server using *our* implementation, > then you can register one of the server’s streams with a remote client by > using the “RTSPServer::registerStream()” function (see > “liveMedia/include/RTSPServer.hh”, lines 47-62). > > Also, our “openRTSP” client application can receive and handle “REGISTER” > commands; see the section "Playing a stream without knowing its "rtsp://“ > URL” here: http://live555.com/openRTSP/#other-options And, of course, > our “LIVE555 Proxy Server” can do the same (for back-end streams). > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > [email protected] > http://lists.live555.com/mailman/listinfo/live-devel >
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
