> I don’t see anything being received at all. So am I correct to assume that
> the Client software is definitely NOT sending RTCP RR or indeed any RTCP
> packets?
No, but you can definitely assume that RTCP packets are not arriving at the
server.
It's possible, I suppose, that the client - for
> Does the requirement of the RTCP (keepalive) change at all when using RTP
> over RTSP?
No.
> Certainly, applications get notifications (from the TCP stack) when their
> peer “goes away” (stops responding to TCP keepalives).
Yes, in principle. However, this might take a long time (possibly
Hi Ross,
>> 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 arri
ve-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
> 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 - desp
Hi Ross,
> Huh? If your RTSP server is "based on testOnDemandRTSPServer", then it
most certainly *is* 'starting' both RTP and RTCP. That's what a unicast
RTSP server does. You seem very confused here.
>But the issue here is your *client*. It is apparently not sending back
periodic RTCP "RR"
> >The problem is your client. It is apparently not sending any periodic RTCP
> >"RR" packets - which it is supposed to do as per the RTP/RTCP standard.
> But my RTSP server (based on TestOnDemandRTSPServer) doesn’t start RTCP (or
> RTP).
Huh? If your RTSP server is "based on testOnDemandRTSP
>The problem is your client. It is apparently not sending any periodic RTCP
"RR" packets - which it is supposed to do as per the RTP/RTCP standard.
But my RTSP server (based on TestOnDemandRTSPServer) doesn't start RTCP (or
RTP). So, if the Client doesn't send GET_PARAMETER messages like VCL, I
> Any ideas, what could be causing my FramedSource class to self-destruct every
> 60 seconds? This must be some kind of timeout.
Exactly. The server is timing out the client connection (and reclaiming its
state: sockets, ports, and memory) because it is not seeing any sign of
activity from the
Hi,
I have a strange problem with my live embedded rtsp H.264 server when
connected to a certain 3rd party client software package.
Every 60 seconds my FramedSource derived class(StreamSource) is getting
deleted. If I connect via VLC or openRTSP, this does not happen, but I'm
fairly sure it is n
10 matches
Mail list logo
