> Received a complete PLAY response: > RTSP/1.0 200 OK > CSeq: 6 > Session: 872219556 > Range: npt=now- > RTP-Info: > url=rtsp://10.0.70.22:554/video1+audio1/trackID=0;seq=35711,url=rtsp://10.0.70.22:554/video1+audio1/trackID=1;seq=62268,url=rtsp://10.0.70.22:554/video1+audio1/events;seq=4796
FYI, it turned out that this "RTP-Info:" header - although legal - wasn't useful to us, because it didn't specify *both* the "seq" and "rtptime" parameters. Our RTSP client code was getting confused by this, which explains why the "NPT" values were turning out strange. I've just installed a new version of the code that ignores "RTP-Info:" headers - like this - that don't specify *both* the "seq" and "rtptime" parameters. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
