> You should contact the camera's manufacturer, asking them to fix
their camera's RTSP server.
Thank you for investigating it, I'll contact them.
With luck, they'll have a firmware upgrade already available...
> By the way, you were incorrect when you said that a previous version
of our code (2009.07.27, according to your "working.txt" log) handled
this camera correctly. As far as I can tell, we have *never*
accepted a "Range:" header that says "ntp" instead of "npt". You
must have hacked your own version of the code to accept this (broken)
"Range:" header, and then forgotten about it.
I have never modified live555 to handle this. Maybe the npt was not handled
correctly, but at least, with some older versions, the play didn't
fail with an
error.
Yes, I was mistaken about this. Although the code that checks the
"Range:" header has not changed in a long time, it turns out that -
in old versions of "RTSPClient" - we were silently ignoring "Range:"
headers - like this one - that were malformed. In our recent new
"RTSPClient" implementation we started reporting malformed headers as
errors - which happened to catch the bug in this camera server.
--
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
