Hi Ross, Does the requirement of the RTCP (keepalive) change at all when using RTP over RTSP?
We've seen a few clients that DO NOT send keepalives when configured for RTP over RTSP, as the RTP "data" is interleaved over the same TCP "Session" as the the RTSP control. Apparently, they have determined that the TCP session "liveness" can be determined by the TCP stack, and that that is "adequate". Live555 certainly does still require the keepalives in that "configuration". Certainly, applications get notifications (from the TCP stack) when their peer "goes away" (stops responding to TCP keepalives). Are you aware of any specifications (based on alternate configuration) that remove the obligation of the RTCP (or noop message) keepalives? Thanks, Randy Roberts From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Thursday, January 26, 2012 9:12 AM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Server disconnects clients every 60 seconds I've talked to the developers of the NVR software (our client) and they tell me they do send regular RTCP reports, but they don't send GET_PARAMETER messages like VLC does. However, my streams don't keep alive and I don't see their RTCP report messages coming in. Then your client - despite the claims of its developers - must not be sending RTCP reports correctly. (I encourage these developers to get in touch with us - via this mailing list - to help fix this.) (Note, BTW, that "openRTSP" - which you noted works correctly with your server - doesn't send "GET_PARAMETER" requests either. But it keeps the session alive, because it sends periodic RTCP "RR" packets.) When I look at testOnDemandRTSPServer, I don't see any specify RTCPInstance:createNew() call That is done in the "OnDemandServerMediaSubsession" class. Where can I put some debug to catch the RTCP reports coming in? Add #define DEBUG 1 to the start of "liveMedia/RTCP.cpp". You will see reports of RTCP "SR" packets being sent by the server, and - if your client is working correctly (e.g., "openRTSP") - RTCP "RR" packets arriving from the client. I enabled the debug in RTSPServer::RTSPClientSession:: handleRequestBytes() after parseRTSPRequestString(), but I don't see the RTCP messages there. No. That function is used only for incoming RTSP commands, not RTCP packets. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ________________________________ Notice to recipient: This email is meant for only the intended recipient of the transmission, and may be a communication privileged by law, subject to export control restrictions or that otherwise contains proprietary information. If you receive this email by mistake, please notify us immediately by replying to this message and then destroy it and do not review, disclose, copy or distribute it. Thank you in advance for your cooperation.
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
