Thank you, Ross. The problem is gone now. On May 2, 2015, at 8:43 PM, Ross Finlayson <finlay...@live555.com<mailto:finlay...@live555.com>> wrote:
I have just installed a new version (2015.05.03) of the “LIVE555 Streaming Media” software that should fix this problem. Now, whenever a “RTSPClientConnection” object (i.e., the RTSP TCP connection) is closed, the server will - at the same time - close any RTP/RTCP-over-TCP streaming that was taking place over the same TCP socket. (Usually, this will also cause the associated “RTSPClientSession” object to get deleted - though not necessarily, as in principle it’s possible, for example, to have one track in a stream use RTP/RTCP-over-TCP, and another track use RTP/RTCP-over-UDP. It’s also possible to have different tracks streaming RTP/RTCP-over-TCP using different TCP connections; if one TCP connection closes, then only the tracks that were streaming over that connection will get closed.) Thanks again for the bug report. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com<mailto: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
