[Live-devel] RTSP stops after 5 minutes
Cristiano Belloni
belloni at imavis.com
Thu May 7 02:55:55 PDT 2009
Shiva and Ron, could you please monitor the client / camera interaction
with sniffer tools like Wireshark or Tcpdump?
The behaviour seems compatible with my very same problem (connection
shut down after a while, only in tcp mode), and in my case it is due to
openRTSP not sending RR packets (that causes the server to send a RTCP
BYE after some time).
You should sniff the connection RTCP packets and see if openRTSP sends
RR packets or, like in my case, does not at all.
Thanks,
Cristiano.
Ron McOuat wrote:
> The media.amp ending on the URL says you are using an Axis camera. If
> you replace the -t option with -T 80 you will switch from using
> regular RTSP/RTP by TCP to TCP tunneled on HTTP to port 80 which the
> Axis camera will accept. This did not fail for me after a time period.
> I compiled live555 with the -DDEBUG option added to CFLAGS and
> followed the trace for the sessions quiting with the -t option. I
> could not get to the bottom of it because of time pressure and I had
> for me a workable solution using -T 80. I posted the trace to the list
> over a year ago but as Ross says it requires getting in and tracing it
> in detail. I also found the amount of time before failure varied up to
> 30-40 minutes in my case. In the end I didn't know if I was fighting a
> problem in the LAN, a problem with the Axis camera or a live555
> problem. Axis has released patches to firmware for some models that
> mention fixes to the MPEG4 image transfer mode so you should look at
> that as well.
>
> Shiva Shankar N wrote:
>> Hi
>>
>> this is there any way that i would make openrtsp client streaming to
>> work for more than 5 minutes with TCP tunneling i.e., with -t option.
>>
>> thanking you
>> shiv
>>
>>
>> On Mon, May 4, 2009 at 2:04 AM, Shiva Shankar N <nshamshiva at gmail.com
>> <mailto:nshamshiva at gmail.com>> wrote:
>>
>> Hi Ross,
>> Thanks for your quick reply.
>> Do you have any suggestion for me to fix this bug. I am really in
>> urgent to finish off this project. I saw some of your previous
>> posting in 2007 (appox april) there was a same problem. And you
>> had release new code with the bug fixed.
>>
>> thanks
>> shiv
>>
>>
>>
>> On Mon, May 4, 2009 at 12:20 AM, Ron McOuat <rmcouat at smartt.com
>> <mailto:rmcouat at smartt.com>> wrote:
>>
>> I ran into this with Axis cameras, judging from the URL this
>> is what you are using. I found the -T option for HTTP
>> tunneling also worked as well as leaving off the -t option as
>> you have found.
>>
>> Shiva Shankar N wrote:
>>
>> Hi Ross,
>>
>> It is working fine if i tunnel the data thru UDP. I.e.,
>> removing -t option it is working fine.
>>
>> thanks
>> shiv
>>
>>
>> On Sun, May 3, 2009 at 8:35 PM, Shiva Shankar N
>> <nshamshiva at gmail.com <mailto:nshamshiva at gmail.com>
>> <mailto:nshamshiva at gmail.com
>> <mailto:nshamshiva at gmail.com>>> wrote:
>>
>> Hi Ross,
>>
>> This is error i am getting. please if you now where
>> exactly it
>> going wrong.
>> please let me know. So that it would reduce my
>> debugging time
>>
>>
>>
>> *********************************************************************************************************************************************
>>
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>>
>> Received OPTIONS response: RTSP/1.0 200 OK
>> CSeq: 1
>> Public: DESCRIBE, GET_PARAMETER, PAUSE, PLAY, SETUP,
>> TEARDOWN
>>
>>
>> Sending request: DESCRIBE
>> rtsp://128.197.178.101/mpeg4/media.amp
>> <http://128.197.178.101/mpeg4/media.amp>
>> <http://128.197.178.101/mpeg4/media.amp> RTSP/1.0
>>
>> CSeq: 2
>> Accept: application/sdp
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>>
>> Received DESCRIBE response: RTSP/1.0 200 OK
>> CSeq: 2
>> Content-Base:
>> rtsp://128.197.178.101:554/mpeg4/media.amp/
>> <http://128.197.178.101:554/mpeg4/media.amp/>
>> <http://128.197.178.101:554/mpeg4/media.amp/>
>>
>> Content-Type: application/sdp
>> Content-Length: 684
>>
>>
>> Need to read 684 extra bytes
>> Read 684 extra bytes: v=0
>> o=- 1241378493017427 1241378493017434 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
>> <http://128.197.178.101/mpeg4/media.amp>
>> <http://128.197.178.101/mpeg4/media.amp>", returning a
>> SDP description
>>
>> :
>> v=0
>> o=- 1241378493017427 1241378493017434 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
>> 51302-51303)
>> Sending request: SETUP
>> rtsp://128.197.178.101:554/mpeg4/media.amp/trackID=1
>> <http://128.197.178.101:554/mpeg4/media.amp/trackID=1>
>> <http://128.197.178.101:554/mpeg4/media.amp/trackID=1>
>> RTSP
>>
>> /1.0
>> CSeq: 3
>> Transport: RTP/AVP/TCP;unicast;interleaved=0-1
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>>
>> Received SETUP response: RTSP/1.0 200 OK
>> CSeq: 3
>> Session: 1098178773;timeout=60
>> Transport:
>> RTP/AVP/TCP;unicast;mode=play;interleaved=116-117
>>
>>
>> Setup "video/MP4V-ES" subsession (client ports
>> 51302-51303)
>> Sending request: PLAY
>> rtsp://128.197.178.101:554/mpeg4/media.amp/
>> <http://128.197.178.101:554/mpeg4/media.amp/>
>> <http://128.197.178.101:554/mpeg4/media.amp/> RTSP/1.0
>>
>> CSeq: 4
>> Session: 1098178773
>> Range: npt=0.000-
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>>
>> Received PLAY response: RTSP/1.0 200 OK
>> CSeq: 4
>> Session: 1098178773
>> Range: npt=now-
>> RTP-Info: url=trackID=1;seq=39372;rtptime=2047243131
>>
>>
>> Started playing session
>> Receiving streamed data...
>> Received RTCP "BYE" on "video/MP4V-ES" subsession
>> (after 313 seconds)
>> Sending request: PLAY
>> rtsp://128.197.178.101:554/mpeg4/media.amp/
>> <http://128.197.178.101:554/mpeg4/media.amp/>
>> <http://128.197.178.101:554/mpeg4/media.amp/> RTSP/1.0
>>
>> CSeq: 5
>> Session: 1098178773
>> Range: npt=0.000-
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>>
>> Failed to start playing session: Failed to read
>> response: No error
>> Sending request: TEARDOWN
>> rtsp://128.197.178.101:554/mpeg4/media.amp/
>> <http://128.197.178.101:554/mpeg4/media.amp/>
>> <http://128.197.178.101:554/mpeg4/media.amp/> RTSP/1.0
>>
>> CSeq: 6
>> Session: 1098178773
>> User-Agent: openrtsp (LIVE555 Streaming Media
>> v2009.04.20)
>>
>> Thanks
>> shiv
>>
>>
>>
>> On Sun, May 3, 2009 at 6:52 PM, Ross Finlayson
>> <finlayson at live555.com <mailto:finlayson at live555.com>
>> <mailto:finlayson at live555.com
>> <mailto:finlayson at live555.com>>> wrote:
>>
>> What do you mean "stops working"?
>> The application stop or close automatically..
>> to be
>> exactly after 5 minutes 40 sec
>>
>> I want to play this application continuously ..
>> and this
>> the setting i am using
>>
>> openrtsp -b 500000 -v -V -w 704 -h 480 -4 -t -c
>> rtsp://128.xxx.xx.xxx/mpeg4/media.amp >stream.m4v
>>
>>
>> Please omit the "-V" option, and send us the
>> diagnostic output
>> that "openRTSP" displays (to stderr). This should
>> help
>> explain what's happening.
>>
>> --
>> Ross Finlayson
>> Live Networks, Inc.
>> http://www.live555.com/
>> _______________________________________________
>> live-devel mailing list
>> live-devel at lists.live555.com
>> <mailto:live-devel at lists.live555.com>
>> <mailto:live-devel at lists.live555.com
>> <mailto:live-devel at lists.live555.com>>
>>
>> http://lists.live555.com/mailman/listinfo/live-devel
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> live-devel mailing list
>> live-devel at lists.live555.com
>> <mailto:live-devel at lists.live555.com>
>> http://lists.live555.com/mailman/listinfo/live-devel
>>
>> _______________________________________________
>> live-devel mailing list
>> live-devel at lists.live555.com
>> <mailto:live-devel at lists.live555.com>
>> http://lists.live555.com/mailman/listinfo/live-devel
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> live-devel mailing list
>> live-devel at lists.live555.com
>> http://lists.live555.com/mailman/listinfo/live-devel
>>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
--
Belloni Cristiano
Imavis Srl.
www.imavis.com <http://www.imavis.com>
belloni at imavis.com <mailto://belloni@imavis.com>
More information about the live-devel
mailing list