<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] openRTSP -r
-p</title></head><body>
<blockquote type="cite" cite><font face="Arial" size="-1">To get
around this, we are using openRTSP with the -r and -p options
(openRTSP -r -p 20006 rtsp://192.168.1.9:8554/path/video.ts) and
receiving the RTP data with a separate application (just receiving it,
counting how much we receive, and throwing it away). However, at
45 seconds, our RTP streaming stops (consistently). The video
file is definitely longer than this (and works properly without -r
-p). We believe it may be related to the server not receiving
some sort of heartbeat (maybe via RTCP).</font></blockquote>
<div><br></div>
<div>That's exactly what's happening. The server apparently uses
RTCP "RR" packets - from the receiver - as a liveness
indication. If it doesn't receive these, it assumes that the
receiver has died, and it times out the session.</div>
<div><br></div>
<div>If your RTSP server uses our implementation, then you can modify
it to disable this timeout by setting the
"reclamationTestSeconds" parameter from 45 to 0.
(E.g., if you are using the "LIVE555 Media Server", then see
"DynamicRTSPServer.cpp", line 44.)</div>
<div><br></div>
<div>Alternatively, of course, you could add RTCP to your reception
application.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>