<div dir="ltr"><div><div><div>Hi,<br><br></div>Thanks for the quick answer. You are right: when QuickTime is configured to run RTSP over UDP it seems to work fine. Unfortunately I need it to be TCP or HTTP as I'm planning to use connections over a WAN 3G network where UDP traffic may not be allowed. Is there a way to be 100% sure this is a player issue? Which other players do you suggest? I tried VLC but the Web plugin does not seems to be very stable...<br>
<br></div>The other solution, setting reclamationTestSeconds to 0, does not seems to work. In fact, it ends very bad as the program terminates unexpectedly (see attached log). Any ideas on this one?<br><br></div><div>Is QT supposed to work over HTTP? I mean, has this been tested?<br>
<br></div>Regards<br><br>Rafael Gil<br>Vaelsys<br><div><br><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2012/12/27 Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div class="im"><div><blockquote type="cite"><div dir="ltr"><div>I'm trying to access a live RTSP stream from an AXIS camera through the RTSP proxy with the proxyServer program. So far no luck. It works just fine for VLC but not for QuickTime. The problem seems to be that RR packets are not treated the same way: with VLC the noteClientLiveness method is called so the client session does not timeout. With QuickTime noteClientLiveness is not called so after a few seconds I get the message "RTSP client session (id "6F559A12", stream name "proxyStream") has timed out (due to inactivity)". Find attached both logs in verbose and debug mode. Any ideas?<br>
</div></div></blockquote><div><br></div></div></div>Hmm, you failed to mention that there are a lot of things different about your two client sessions - apart from just the media player application that they use. <div><br>
</div><div>You are apparently running VLC on the same computer (192.168.0.26) on which you're running the "LIVE555 Proxy Server". That's OK, but strange.</div><div><br></div><div>On the other hand, you are running QuickTime Player on a different computer: 192.168.0.28. That's also OK (and not strange :-). What *is* strange, however, is that QuickTime Player is requesting RTSP-over-HTTP streaming (using port 8000), even though it seems to be running on the same subnet as the proxy server, and therefore could probably just requested regular RTSP streaming instead.</div>
<div><br></div><div>The problem seems to be that - for some unknown reason (perhaps an incompatibility in the way that QuickTime Player implements RTSP-over-HTTP streaming?) - the QuickTime Player client is not sending periodic RTCP packets to indicate its liveness.</div>
<div><br></div><div>The quickest solution would be to stop your QuickTime Player client from requesting RTSP-over-HTTP streaming - something that it probably doesn't need to do.</div><div><br></div><div>Another solution (not recommended) would be to stop the proxy server from timing out clients due to inactivity. You can do that by setting the "reclamationTestSeconds" parameter to 0 in the calls to "RTSPServer::createNew()" in "proxyServer/live555ProxyServer.cpp". I.e., change the calls to</div>
<div><span style="white-space:pre-wrap"> </span>RTSPServer::createNew(*env, rtspServerPortNum, authDB);</div><div>to</div><div><span style="white-space:pre-wrap"> </span>RTSPServer::createNew(*env, rtspServerPortNum, authDB, 0);</div>
<div>(The disadvantage of this, however, is that TCP connections (and sockets) for clients that die without doing a RTSP "TEARDOWN" will stay around indefinitely, and eventually your proxy server will run out of sockets.)</div>
<div><br></div><div>The ideal solution would be fix whatever problem is causing QuickTime (when using RTSP-over-HTTP streaming) to apparently not send RTCP "RR" packets correctly. Unfortunately we can't help you with this; however, you should make sure that QuickTime is up-to-date on this computer (which looks like it's running Windows XP).</div>
<span class="HOEnZb"><font color="#888888"><br><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px">Ross Finlayson<br>
Live Networks, Inc.<br><a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></span></span>
</div>
<br></font></span></div><br>_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Rafael Gil<br>Vaelsys<br><br>
</div>