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
