<div dir="ltr"><div class="gmail_extra">On 4 April 2013 10:16, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>I find this very difficult to believe - especially considering that nobody else has reported this problem.</div>
</div></blockquote><div><br></div><div style>I'm not sure what to say but GET_PARAMETER is causing problems with almost all cameras I have here to test (excluding a Chinese no brand one ironically). I've made one more stream publicly available, this time from Axis - arguably the leaders in the market. </div>
<div style><br></div><div style>The stream doesn't freeze as quickly as the Sony stream, but does freeze after a few minutes or so:</div><div style><br></div><div style>rtsp://<a href="http://viewer:password@86.162.35.136/axis-media/media.amp">viewer:password@86.162.35.136/axis-media/media.amp</a><br>
</div><div style><br></div><div style>Instead of freezing after the first GET_PARAMETER like Sony, it seems to do this after a few GET_PARAMETER requests around the 2 and a half minute mark:</div><div style><br></div><div style>
<div>Sending request: GET_PARAMETER rtsp://<a href="http://86.162.35.136/axis-media/media.amp/">86.162.35.136/axis-media/media.amp/</a> RTSP/1.0</div><div>CSeq: 11</div><div>Authorization: Digest username="viewer", realm="AXIS_00408CC61141", nonce="0003b3acY558862c87aa9f41d1bb2e0ce73a2ab572b750", uri="rtsp://<a href="http://86.162.35.136/axis-media/media.amp/">86.162.35.136/axis-media/media.amp/</a>", response="dba33206b01ca464ce5c693aeb55c6c1"</div>
<div>User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.01)</div><div>Session: 0E2C46CE</div><div>Content-Length: 2</div><div><br></div><div><br></div><div><br></div><div>Received 266 new bytes of response data.</div>
<div>Received a complete GET_PARAMETER response:</div><div>RTSP/1.0 401 Unauthorized</div><div>CSeq: 11</div><div>Session: 0E2C46CE</div><div>WWW-Authenticate: Digest realm="AXIS_00408CC61141", nonce="0003b442Y74661773895f565b0a7480ea3bff2193120c0", stale=TRUE</div>
<div>WWW-Authenticate: Basic realm="AXIS_00408CC61141"</div><div>Date: Fri, 05 Apr 2013 08:41:21 GMT</div></div><div style><br></div><div style><br></div><div style>ProxyServerMediaSubsession["H264"]::closeStreamSource()<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>
<br>
</div><div>Nonetheless, because you provided definitive evidence of at least one buggy server, I've now installed a new version (2013.04.04) of the code that should avoid crashing this server. The proxy code will now always sends "OPTIONS" - rather than "GET_PARAMETER" - as the 'liveness check' command, unless the server explicitly indicated (by a "Session:" header "timeout" parameter in the "SETUP" response) that it wants to receive periodic in-session "GET_PARAMETER" commands instead. (Some servers have another bug whereby they don't use RTCP "RR" packets - from the client (or proxy) - to indicate client (or proxy) liveness.)</div>
</div></blockquote><div><br></div><div style>I've compiled the latest version and unfortunately I'm seeing the exact same output as above, after about 2 and a half minutes of streaming, I see this:</div><div style>
<br></div><div style><div>Sending request: GET_PARAMETER rtsp://<a href="http://86.162.35.136/axis-media/media.amp/">86.162.35.136/axis-media/media.amp/</a> RTSP/1.0</div><div>CSeq: 11</div><div>Authorization: Digest username="viewer", realm="AXIS_00408CC61141", nonce="0003b564Y2228267e47cfeaebe489a7adc01614e45c593", uri="rtsp://<a href="http://86.162.35.136/axis-media/media.amp/">86.162.35.136/axis-media/media.amp/</a>", response="68581b599686f52057b105915c628adf"</div>
<div>User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.05)</div><div>Session: F1965CF1</div><div>Content-Length: 2</div><div><br></div><div><br></div><div><br></div><div>Received 266 new bytes of response data.</div>
<div>Received a complete GET_PARAMETER response:</div><div>RTSP/1.0 401 Unauthorized</div><div>CSeq: 11</div><div>Session: F1965CF1</div><div>WWW-Authenticate: Digest realm="AXIS_00408CC61141", nonce="0003b5faY417690407232ac53139bf9e460a425d4722ba", stale=TRUE</div>
<div>WWW-Authenticate: Basic realm="AXIS_00408CC61141"</div><div>Date: Fri, 05 Apr 2013 08:48:42 GMT</div></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>Yes, but I still find it strange that nobody else has reported this. (It would be nice to get independent confirmation of this from a professional user, and also have this bug reported to the camera manufacturer(s)!)</div>
</div></blockquote><div><br></div><div><br></div><div style>I noticed this problem back in January, but just used the 2012.12.24 version assuming some kind of PEBKAC since I have a couple of patches I used (like allowing to specify a port from the command line), but then reproduced it with vanilla. I am also very surprised nobody reported this.</div>
</div></div></div>