> 2. Seek in that stream. > Range: clock=20130322T200000.000Z- > > The response to #2: > Range: clock=20130322T200000Z-20130322T204538Z > > 3. And then, after teardown, start up the same stream with the same seek-time. > PLAY rtsp://192.168.1.103/archive/TVF-01a/ RTSP/1.0 > Range: clock=20130322T200000.000Z- > > The PLAY- response to #3: > Range: clock=20130320T203757Z-20130322T204804Z > > > So, if I interpret this correctly it's the Cisco server that is inconsistent.
Yes, that looks like a bug in the 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