> sorry. it will return after 1min32sec  as receive BYE . 

What is probably happening here is that your RTSP server is not receiving any 
RTCP “RR” (Reception Report) packets from the client, and is therefore 
concluding that the client is no longer alive.  The server therefore 'times 
out’ and closes the session (and sends a RTCP “BYE” when it does this).

It appears that you have a firewall - somewhere between the client and the 
server - that is blocking RTCP packets from the client.  If you fix (or remove) 
this firewall, the server will start receiving RTCP “RR” packets from the 
client, and will no longer 'time out’ the connection after ~ 1min32sec.

(Another way to solve this is to arrange for your client to periodically send a 
‘keep-alive’ RTSP command (e.g., “OPTIONS”) back to the server - to tell the 
server that the client is still alive.  For an example of how to do this, see 
how our “openRTSP” application <http://www.live555.com/openRTSP/> implements 
the “-K” option; see “playCommon.cpp”, lines 371-374.)


Another problem you have (though less serious than the first problem) is that 
RTCP “SR” (Sender Report) packets from the server 192.168.11.114 are not 
reaching the client.  You can see this by the exclamation point (i.e., “!”) at 
the end of the “Presentation time”s for that server; “testRTSPClient” outputs 
this when the presentation time has not been synchronized by the arrival of a 
RTCP “SR” packet.

This is not serious, as long as the stream contains only a video track.  
However, if you want to have both a video and an audio track, and have them 
properly synchronized, then it’s important that the server send out RTCP “SR” 
packets, and that the client be able to receive them.


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

Reply via email to