Ralf,
Thanks for the note. Your patch looks like a good idea; it will likely be
incorporated into the next release of the software.
However, although your patch is a good idea (basically, a 'sanity check' for
the case when a '$'-framed packet is received without an appropriate handler
for the
Oops, you forgot to attach your patch.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
>>> Ross Finlayson 16/10/12 11:50 PM >>>
Apologies, the buggy mail software seems to have dropped the attached patch,
or at least I can't see it on the mailing list. Attempt #2.
Regards,Ralf
--
This message is subject to the CSIR's copyright terms and conditions, e-mail
legal notice, and i
Hi Ross,
> So if you still see problems even with the latest version of the software
> (for both the server and client), then you're going to
have to track this down yourself. (Please don't bother sending 'wireshark'
logs; I never look at those.)
After upgrading the server, the issue persiste
Hi Ross,
We are putting a rather large custom calibration structure (xml text) in
the SDP for our media sessions and we ran into a limit on the server side.
In the RTSPServer code the fResponseBuffer and fRequestBuffer are both
limited by the #define of RTSP_BUFFER_SIZE which is set to 1.
> I tried with a new version of live555Proxy as well
You should have tried with a new version *only*, because (as you know) the
latest version of the software is the only version that we support.
> , it sends a DESCRIBE request, however, SETUP command after DESCRIBE is
> having same Session ID
Hi Ross,
I am using Live555ProxyServer to proxy a stream from a camera. Proxy server
establishes the session with the camera and I am able to get the stream from
the proxy.
However, in case camera gets disconnected and then connects again. Now if I try
to get stream from the proxy using a RTSP
