On 4 April 2013 10:16, Ross Finlayson <finlay...@live555.com> wrote: > I find this very difficult to believe - especially considering that nobody > else has reported this problem. >
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. The stream doesn't freeze as quickly as the Sony stream, but does freeze after a few minutes or so: rtsp://viewer:password@86.162.35.136/axis-media/media.amp 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: Sending request: GET_PARAMETER rtsp://86.162.35.136/axis-media/media.amp/RTSP/1.0 CSeq: 11 Authorization: Digest username="viewer", realm="AXIS_00408CC61141", nonce="0003b3acY558862c87aa9f41d1bb2e0ce73a2ab572b750", uri="rtsp:// 86.162.35.136/axis-media/media.amp/", response="dba33206b01ca464ce5c693aeb55c6c1" User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.01) Session: 0E2C46CE Content-Length: 2 Received 266 new bytes of response data. Received a complete GET_PARAMETER response: RTSP/1.0 401 Unauthorized CSeq: 11 Session: 0E2C46CE WWW-Authenticate: Digest realm="AXIS_00408CC61141", nonce="0003b442Y74661773895f565b0a7480ea3bff2193120c0", stale=TRUE WWW-Authenticate: Basic realm="AXIS_00408CC61141" Date: Fri, 05 Apr 2013 08:41:21 GMT ProxyServerMediaSubsession["H264"]::closeStreamSource() > > 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.) > 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: Sending request: GET_PARAMETER rtsp://86.162.35.136/axis-media/media.amp/RTSP/1.0 CSeq: 11 Authorization: Digest username="viewer", realm="AXIS_00408CC61141", nonce="0003b564Y2228267e47cfeaebe489a7adc01614e45c593", uri="rtsp:// 86.162.35.136/axis-media/media.amp/", response="68581b599686f52057b105915c628adf" User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.05) Session: F1965CF1 Content-Length: 2 Received 266 new bytes of response data. Received a complete GET_PARAMETER response: RTSP/1.0 401 Unauthorized CSeq: 11 Session: F1965CF1 WWW-Authenticate: Digest realm="AXIS_00408CC61141", nonce="0003b5faY417690407232ac53139bf9e460a425d4722ba", stale=TRUE WWW-Authenticate: Basic realm="AXIS_00408CC61141" Date: Fri, 05 Apr 2013 08:48:42 GMT 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)!) > 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.
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
