Ross, Thanks for your reply....despite the absence of an actual question :-) A few days after posting the email to the list, I discovered that this had been "asked and answered".
ProxyServer seems to handle reconnect scenarios pretty well. Would your implementation of RTSPClient in ProxyServer be a good model for how to add this functionality for client applications? Have you considered adding file sink and output options to ProxyServer? Bob On Mon, Dec 23, 2013 at 6:34 PM, Ross Finlayson <finlay...@live555.com>wrote: > I have a quick question regarding the expected behavior of openRTSP client > w/ file output when connection to the server is lost due to reboot, loss of > connectivity...etc. > > > The rest of your message didn't contain a question :-) However... > > The only reliable way for a client to detect when a server 'dies' is to > notice that RTP packets from the server stop arriving. (Note that a TCP > connection can stay alive for a long time after the remote end dies, so you > can't reliably detect this from the TCP connection.) > > You can detect this in "openRTSP" using the "-D > <maximum-inter-packet-gap>" option; see > http://www.live555.com/openRTSP/#playing-time > > Note, however, that "openRTSP" uses a single connection only, and does not > - by itself - attempt to reconnect to a dead server. If you want to do > that, you'll need to run "openRTSP" a separate time, e.g. from a shell > script. > > > 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 >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
