[Live-devel] Confirm absolute time playing position on startup

[Erlandsson, Claes P (CERLANDS)]

Is this intended, or is it somehow server dependent?

 

I don't know.  Please show the complete RTSP protocol exchange for each
case, so I can try to figure out what's happening.

 





I've attached the protocol exchange for the following example:

 

1. Start up an archive stream without any timestamp.

PLAY rtsp://192.168.1.103/archive/TVF-01a/ RTSP/1.0

 

2. Seek in that stream.

Range: clock=20130322T200000.000Z-

 

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 response to #2:

Range: clock=20130322T200000Z-20130322T204538Z

 

The PLAY- response to #3:

Range: clock=20130320T203757Z-20130322T204804Z

 

 

So, if I interpret this correctly it's the Cisco server that is
inconsistent.

I don't see any specific examples of this in the RFC2326, but appears like
an error to me. Please comment.

 

 

/Claes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130322/1fa30cf5/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: RTSP-communication.txt
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130322/1fa30cf5/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5740 bytes
Desc: not available
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20130322/1fa30cf5/attachment.bin>