Mr. Ross, Thank you very much for quick answer. Am I understood correctly: client session object deleted in multicast mode, even one client from multi has a timeout???? ThanX again.
On Sun, Mar 6, 2011 at 12:33 PM, Ross Finlayson <finlay...@live555.com>wrote: > why multicast checking removed from livenessTimeoutTask API??? >> > > Because there was no longer any need to exclude multicast sessions from the > normal client liveness checking. > > I.e., as with all RTSP/RTP streams, the server will timeout the stream if > it doesn't receive any indication of 'liveness' (e.g., a RTCP packet, or a > RTSP command) from a client within the timeout period. > > (Note that all clients - whether unicast or multicast - are required to > send back RTCP "RR" packets.) > > In any case, as always, you can disable the server's liveness checking by > starting the server with the "reclamationTestSeconds" parameter set to 0. > -- > > 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