[Live-devel] Bad "Range:" header error introduced
Krishna Patel
megaplace at hotmail.com
Sat Feb 8 10:24:58 PST 2014
This is really strange.
I compiled openRTSP with Visual Studio 2008. This is app output:
Opening connection to 128.197.178.101, port 80...
...remote connection opened
Requesting RTSP-over-HTTP tunneling (on port 80)
Sending request: GET /mpeg4/media.amp HTTP/1.1
CSeq: 1
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Host: 128.197.178.101
x-sessioncookie: 04f86c4ff28f926de9b83f5
Accept: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache
Received 63 new bytes of response data.
Received a complete GET response:
HTTP/1.0 200 OK
Content-Type: application/x-rtsp-tunnelled
Opening connection to 128.197.178.101, port 80...
...remote connection opened
Sending request: POST /mpeg4/media.amp HTTP/1.1
CSeq: 1
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Host: 128.197.178.101
x-sessioncookie: 04f86c4ff28f926de9b83f5
Content-Type: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 32767
Expires: Sun, 9 Jan 1972 00:00:00 GMT
Sending request: OPTIONS rtsp://128.197.178.101/mpeg4/media.amp RTSP/1.0
CSeq: 2
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
The request was base-64 encoded to: T1BUSU9OUyBydHNwOi8vMTI4LjE5Ny4xNzgu
MTAxL21wZWc0L21lZGlhLmFtcCBSVFNQLzEuMA0KQ1NlcTogMg0KVXNlci1BZ2VudDogb3BlblJUU1Ag
KExJVkU1NTUgU3RyZWFtaW5nIE1lZGlhIHYyMDE0LjAyLjA0KQ0KDQo=
Received 91 new bytes of response data.
Received a complete OPTIONS response:
RTSP/1.0 200 OK
CSeq: 2
Public: DESCRIBE, GET_PARAMETER, PAUSE, PLAY, SETUP, TEARDOWN
Sending request: DESCRIBE rtsp://128.197.178.101/mpeg4/media.amp RTSP/1.0
CSeq: 3
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Accept: application/sdp
The request was base-64 encoded to: REVTQ1JJQkUgcnRzcDovLzEyOC4xOTcuMTc4
LjEwMS9tcGVnNC9tZWRpYS5hbXAgUlRTUC8xLjANCkNTZXE6IDMNClVzZXItQWdlbnQ6IG9wZW5SVFNQ
IChMSVZFNTU1IFN0cmVhbWluZyBNZWRpYSB2MjAxNC4wMi4wNCkNCkFjY2VwdDogYXBwbGljYXRpb24v
c2RwDQoNCg==
Received 823 new bytes of response data.
Received a complete DESCRIBE response:
RTSP/1.0 200 OK
CSeq: 3
Content-Base: rtsp://128.197.178.101:554/mpeg4/media.amp/
Content-Type: application/sdp
Content-Length: 684
v=0
o=- 1391865650758305 1391865650758312 IN IP4 128.197.178.101
s=Media Presentation
e=NONE
c=IN IP4 0.0.0.0
b=AS:8000
t=0 0
a=control:*
a=range:npt=now-
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoDUAE8BAf/1AQOAbwABQFBkYXRhOmFw
cGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBUjBCR3dVZkF4Y0F5U1FBWlFRTklCRUVrK0FBZWhJ
QUFIb1NBQVlCQkE9PQQNAQUABAAAAAAAAAAAAAYJAQAAAAAAAAAAAzoAAkA2ZGF0YTphcHBsaWNhdGlv
bi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTWVFTSVVFVUZQd0E9BBICDQAAAgAAAAAAAAAABQMAAEAG
CQEAAAAAAAAAAA=="
m=video 0 RTP/AVP 96
b=AS:8000
a=control:trackID=1
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245; config=000001B0F5000001B5090000010000000120008C4
019285820F0A21F;
a=mpeg4-esid:201
Opened URL "rtsp://128.197.178.101/mpeg4/media.amp", returning a SDP description
:
v=0
o=- 1391865650758305 1391865650758312 IN IP4 128.197.178.101
s=Media Presentation
e=NONE
c=IN IP4 0.0.0.0
b=AS:8000
t=0 0
a=control:*
a=range:npt=now-
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoDUAE8BAf/1AQOAbwABQFBkYXRhOmFw
cGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBUjBCR3dVZkF4Y0F5U1FBWlFRTklCRUVrK0FBZWhJ
QUFIb1NBQVlCQkE9PQQNAQUABAAAAAAAAAAAAAYJAQAAAAAAAAAAAzoAAkA2ZGF0YTphcHBsaWNhdGlv
bi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTWVFTSVVFVUZQd0E9BBICDQAAAgAAAAAAAAAABQMAAEAG
CQEAAAAAAAAAAA=="
m=video 0 RTP/AVP 96
b=AS:8000
a=control:trackID=1
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245; config=000001B0F5000001B5090000010000000120008C4
019285820F0A21F;
a=mpeg4-esid:201
Created receiver for "video/MP4V-ES" subsession (client ports 55900-55901)
Sending request: SETUP rtsp://128.197.178.101:554/mpeg4/media.amp/trackID=1 RTSP
/1.0
CSeq: 4
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
The request was base-64 encoded to: U0VUVVAgcnRzcDovLzEyOC4xOTcuMTc4LjEw
MTo1NTQvbXBlZzQvbWVkaWEuYW1wL3RyYWNrSUQ9MSBSVFNQLzEuMA0KQ1NlcTogNA0KVXNlci1BZ2Vu
dDogb3BlblJUU1AgKExJVkU1NTUgU3RyZWFtaW5nIE1lZGlhIHYyMDE0LjAyLjA0KQ0KVHJhbnNwb3J0
OiBSVFAvQVZQL1RDUDt1bmljYXN0O2ludGVybGVhdmVkPTAtMQ0KDQo=
Received 120 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 4
Session: 1767047643;timeout=60
Transport: RTP/AVP/TCP;unicast;mode=play;interleaved=60-61
Setup "video/MP4V-ES" subsession (client ports 55900-55901)
Created output file: "video-MP4V-ES-1"
Sending request: PLAY rtsp://128.197.178.101:554/mpeg4/media.amp/ RTSP/1.0
CSeq: 5
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Session: 1767047643
Range: npt=0.000-
The request was base-64 encoded to: UExBWSBydHNwOi8vMTI4LjE5Ny4xNzguMTAx
OjU1NC9tcGVnNC9tZWRpYS5hbXAvIFJUU1AvMS4wDQpDU2VxOiA1DQpVc2VyLUFnZW50OiBvcGVuUlRT
UCAoTElWRTU1NSBTdHJlYW1pbmcgTWVkaWEgdjIwMTQuMDIuMDQpDQpTZXNzaW9uOiAxNzY3MDQ3NjQz
DQpSYW5nZTogbnB0PTAuMDAwLQ0KDQo=
Received a complete PLAY response:
RTSP/1.0 200 OK
CSeq: 5
Session: 1767047643
Range: npt=now-
RTP-Info: url=trackID=1;seq=34609;rtptime=3603019675
Failed to start playing session: Bad "Range:" header
Sending request: TEARDOWN rtsp://128.197.178.101:554/mpeg4/media.amp/ RTSP/1.0
CSeq: 6
User-Agent: openRTSP (LIVE555 Streaming Media v2014.02.04)
Session: 1767047643
The request was base-64 encoded to: VEVBUkRPV04gcnRzcDovLzEyOC4xOTcuMTc4
LjEwMTo1NTQvbXBlZzQvbWVkaWEuYW1wLyBSVFNQLzEuMA0KQ1NlcTogNg0KVXNlci1BZ2VudDogb3Bl
blJUU1AgKExJVkU1NTUgU3RyZWFtaW5nIE1lZGlhIHYyMDE0LjAyLjA0KQ0KU2Vzc2lvbjogMTc2NzA0
NzY0Mw0KDQo=
Krishna.
From: finlayson at live555.com
Date: Sat, 8 Feb 2014 10:39:34 +1300
To: live-devel at ns.live555.com
Subject: Re: [Live-devel] Bad "Range:" header error introduced
I switched from Live555 version 2013.09.08 to 2014.02.04 and PLAY command sent to Axis 213 camera now results in "Bad "Range:" header" error returned by Live555. "Range: npt=now-" is returned by the camera that seems to get rejected. The camera is on-line and can be accessed via HTTP tunneling: rtsp://128.197.178.101/mpeg4/media.amp.
That's odd. I'm not seeing this at all. Running "openRTSP -T 80" (to specify RTSP-over-HTTP tunneling) on this URL works just fine:
%openRTSP -T 80 rtsp://128.197.178.101/mpeg4/media.amp
Opening connection to 128.197.178.101, port 80...
...remote connection opened
Requesting RTSP-over-HTTP tunneling (on port 80)
Sending request: GET /mpeg4/media.amp HTTP/1.1
CSeq: 1
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
Host: 128.197.178.101
x-sessioncookie: 11828aef671cfcf975c137d
Accept: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache
Received 63 new bytes of response data.
Received a complete GET response:
HTTP/1.0 200 OK
Content-Type: application/x-rtsp-tunnelled
Opening connection to 128.197.178.101, port 80...
...remote connection opened
Sending request: POST /mpeg4/media.amp HTTP/1.1
CSeq: 1
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
Host: 128.197.178.101
x-sessioncookie: 11828aef671cfcf975c137d
Content-Type: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache
Content-Length: 32767
Expires: Sun, 9 Jan 1972 00:00:00 GMT
Sending request: OPTIONS rtsp://128.197.178.101/mpeg4/media.amp RTSP/1.0
CSeq: 2
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
The request was base-64 encoded to: T1BUSU9OUyBydHNwOi8vMTI4LjE5Ny4xNzguMTAxL21wZWc0L21lZGlhLmFtcCBSVFNQLzEuMA0KQ1NlcTogMg0KVXNlci1BZ2VudDogLi9vcGVuUlRTUCAoTElWRTU1NSBTdHJlYW1pbmcgTWVkaWEgdjIwMTQuMDIuMDcpDQoNCg==
Received 91 new bytes of response data.
Received a complete OPTIONS response:
RTSP/1.0 200 OK
CSeq: 2
Public: DESCRIBE, GET_PARAMETER, PAUSE, PLAY, SETUP, TEARDOWN
Sending request: DESCRIBE rtsp://128.197.178.101/mpeg4/media.amp RTSP/1.0
CSeq: 3
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
Accept: application/sdp
The request was base-64 encoded to: REVTQ1JJQkUgcnRzcDovLzEyOC4xOTcuMTc4LjEwMS9tcGVnNC9tZWRpYS5hbXAgUlRTUC8xLjANCkNTZXE6IDMNClVzZXItQWdlbnQ6IC4vb3BlblJUU1AgKExJVkU1NTUgU3RyZWFtaW5nIE1lZGlhIHYyMDE0LjAyLjA3KQ0KQWNjZXB0OiBhcHBsaWNhdGlvbi9zZHANCg0K
Received 823 new bytes of response data.
Received a complete DESCRIBE response:
RTSP/1.0 200 OK
CSeq: 3
Content-Base: rtsp://128.197.178.101:554/mpeg4/media.amp/
Content-Type: application/sdp
Content-Length: 684
v=0
o=- 1391790981113890 1391790981113897 IN IP4 128.197.178.101
s=Media Presentation
e=NONE
c=IN IP4 0.0.0.0
b=AS:8000
t=0 0
a=control:*
a=range:npt=now-
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoDUAE8BAf/1AQOAbwABQFBkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBUjBCR3dVZkF4Y0F5U1FBWlFRTklCRUVrK0FBZWhJQUFIb1NBQVlCQkE9PQQNAQUABAAAAAAAAAAAAAYJAQAAAAAAAAAAAzoAAkA2ZGF0YTphcHBsaWNhdGlvbi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTWVFTSVVFVUZQd0E9BBICDQAAAgAAAAAAAAAABQMAAEAGCQEAAAAAAAAAAA=="
m=video 0 RTP/AVP 96
b=AS:8000
a=control:trackID=1
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245; config=000001B0F5000001B5090000010000000120008C4019285820F0A21F;
a=mpeg4-esid:201
Opened URL "rtsp://128.197.178.101/mpeg4/media.amp", returning a SDP description:
v=0
o=- 1391790981113890 1391790981113897 IN IP4 128.197.178.101
s=Media Presentation
e=NONE
c=IN IP4 0.0.0.0
b=AS:8000
t=0 0
a=control:*
a=range:npt=now-
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoDUAE8BAf/1AQOAbwABQFBkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBUjBCR3dVZkF4Y0F5U1FBWlFRTklCRUVrK0FBZWhJQUFIb1NBQVlCQkE9PQQNAQUABAAAAAAAAAAAAAYJAQAAAAAAAAAAAzoAAkA2ZGF0YTphcHBsaWNhdGlvbi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTWVFTSVVFVUZQd0E9BBICDQAAAgAAAAAAAAAABQMAAEAGCQEAAAAAAAAAAA=="
m=video 0 RTP/AVP 96
b=AS:8000
a=control:trackID=1
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=245; config=000001B0F5000001B5090000010000000120008C4019285820F0A21F;
a=mpeg4-esid:201
Created receiver for "video/MP4V-ES" subsession (client ports 51914-51915)
Sending request: SETUP rtsp://128.197.178.101:554/mpeg4/media.amp/trackID=1 RTSP/1.0
CSeq: 4
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
The request was base-64 encoded to: U0VUVVAgcnRzcDovLzEyOC4xOTcuMTc4LjEwMTo1NTQvbXBlZzQvbWVkaWEuYW1wL3RyYWNrSUQ9MSBSVFNQLzEuMA0KQ1NlcTogNA0KVXNlci1BZ2VudDogLi9vcGVuUlRTUCAoTElWRTU1NSBTdHJlYW1pbmcgTWVkaWEgdjIwMTQuMDIuMDcpDQpUcmFuc3BvcnQ6IFJUUC9BVlAvVENQO3VuaWNhc3Q7aW50ZXJsZWF2ZWQ9MC0xDQoNCg==
Received 120 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 4
Session: 1825287805;timeout=60
Transport: RTP/AVP/TCP;unicast;mode=play;interleaved=24-25
Setup "video/MP4V-ES" subsession (client ports 51914-51915)
Created output file: "video-MP4V-ES-1"
Sending request: PLAY rtsp://128.197.178.101:554/mpeg4/media.amp/ RTSP/1.0
CSeq: 5
User-Agent: ./openRTSP (LIVE555 Streaming Media v2014.02.07)
Session: 1825287805
Range: npt=0.000-
The request was base-64 encoded to: UExBWSBydHNwOi8vMTI4LjE5Ny4xNzguMTAxOjU1NC9tcGVnNC9tZWRpYS5hbXAvIFJUU1AvMS4wDQpDU2VxOiA1DQpVc2VyLUFnZW50OiAuL29wZW5SVFNQIChMSVZFNTU1IFN0cmVhbWluZyBNZWRpYSB2MjAxNC4wMi4wNykNClNlc3Npb246IDE4MjUyODc4MDUNClJhbmdlOiBucHQ9MC4wMDAtDQoNCg==
Received a complete PLAY response:
RTSP/1.0 200 OK
CSeq: 5
Session: 1825287805
Range: npt=now-
RTP-Info: url=trackID=1;seq=52465;rtptime=806046324
Started playing session
Receiving streamed data (signal with "kill -HUP 93865" or "kill -USR1 93865" to terminate)...
------So, I can't explain why it's not working for you.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20140208/8b4f48e7/attachment.html>
More information about the live-devel
mailing list