> Looks like sending the session id in the OPTION header solved the problem!
>
> After my original post yesterday, I did determine that Axis cameras have a
> session time-out (default 60 sec) setting that was tearing down the session.
The Axis camera should also be using incoming RTCP "RR" packe
Ross,
Thanks for the code update.
Looks like sending the session id in the OPTION header solved the problem!
After my original post yesterday, I did determine that Axis cameras have a
session time-out (default 60 sec) setting that was tearing down the
session. The only thing I cannot explain is
Unfortunately I can't tell why the 'back-end' server (an Axis camera) is timing
out the sessions. (It is apparently a bug in the cameras.)
However, in hope of preventing this from happening, I've now installed a new
version (2013.10.16) of the "LIVE555 Streaming Media" code that now includes
Ross,
Attached is a log file showing the issue. I have edited the log due to size
limits on the mailing list.
Bob
On Mon, Oct 14, 2013 at 8:21 PM, Ross Finlayson wrote:
> I have run into an issue where the session between Proxy Server and the
> back-end server has timed-out, but the Proxy Serv
> I have run into an issue where the session between Proxy Server and the
> back-end server has timed-out, but the Proxy Server is still receiving
> responses to the periodic OPTION requests. In this situation when a request
> (Play / Pause) is made from a client you see "454 Session Not Found",
Ross,
I have run into an issue where the session between Proxy Server and the
back-end server has timed-out, but the Proxy Server is still receiving
responses to the periodic OPTION requests. In this situation when a request
(Play / Pause) is made from a client you see "454 Session Not Found",
how
