Page 1 of 1

live555 error: Failed to connect with rtsp

Posted: 15 Aug 2013 05:18
by alank
I have checked similar posts but can't see a solution as yet so maybe someone can steer me in the right direction.

I have been successfully connecting to this RTSP stream for a number of weeks but this week it failed to connect. I can connect to the same streaming source via my browser okay, so the streaming is working. I can also connect to other streaming via VCL although they are not RTSP format. I was using vcl-2.0.5-win32 but upgraded to vcl-2.0.8-win32 in an effort to fix the problem - no luck there. I have email the community FM station to ask if they have changed anything but haven't heard back - they have FM transmission problems after a lightening strike on the antenna so their minimal resources are occupied elsewhere.

OS Win8 - 64

Here is a VCL log of what is happening when attempting to connect

>>>> ***** >>>> 209.197.30.211 replaced by 209URL211 due to url restrictions
>>>> ***** >>>> 192.168.0.2 replaced by 192URL2 due to url restrictions


main debug: processing request item: rtsp://209.URL.211/2nsblive/2nsblive.sdp, node: Playlist, skip: 0
main debug: resyncing on rtsp:// 209URL211/2nsblive/2nsblive.sdp
main debug: rtsp:// 209URL211/2nsblive/2nsblive.sdp is at 1
main debug: starting playback of the new playlist item
main debug: resyncing on rtsp:// 209URL211/2nsblive/2nsblive.sdp
main debug: rtsp:// 209URL211/2nsblive/2nsblive.sdp is at 1
main debug: creating new input thread
main debug: Creating an input for 'rtsp:// 209URL211 /2nsblive/2nsblive.sdp'
main debug: using timeshift granularity of 50 MiB, in path 'C:\Users\Alan\AppData\Local\Temp'
main debug: `rtsp:// 209URL211 /2nsblive/2nsblive.sdp' gives access `rtsp' demux `' path `209.URL.211/2nsblive/2nsblive.sdp'
main debug: creating demux: access='rtsp' demux='' location= 209URL211 /2nsblive/2nsblive.sdp' file='\\ 209URL211 \2nsblive\2nsblive.sdp'
main debug: looking for access_demux module: 1 candidate
live555 debug: version 2012.12.18
qt4 debug: IM: Setting an input
live555 debug: we will now try HTTP tunneling mode
live555 debug: connection error 403
live555 error: Failed to connect with rtsp:// 209URL211 /2nsblive/2nsblive.sdp
main debug: no access_demux module matching "rtsp" could be loaded
main debug: TIMER module_need() : 2727.783 ms - Total 2727.783 ms / 1 intvls (Avg 2727.783 ms)
main debug: creating access 'rtsp' location= 209URL211 /2nsblive/2nsblive.sdp', path='\\ 209URL211 \2nsblive\2nsblive.sdp'
main debug: looking for access module: 1 candidate
main debug: net: connecting to 209URL211 port 554
main debug: connection succeeded (socket = 2116)
access_realrtsp debug: rtsp connected
access_realrtsp warning: only real/helix rtsp servers supported for now
main debug: no access module matching "rtsp" could be loaded
main debug: TIMER module_need() : 897.191 ms - Total 897.191 ms / 1 intvls (Avg 897.191 ms)
main error: open of `rtsp:// 209URL211 /2nsblive/2nsblive.sdp' failed
main debug: dead input
main debug: changing item without a request (current 1/2)
main debug: nothing to play
qt4 debug: IM: Deleting the input
main debug: TIMER input launching for 'rtsp:// 209URL211 /2nsblive/2nsblive.sdp' : 3663.268 ms - Total 3663.268 ms / 1 intvls (Avg 3663.268 ms)


At the same time I used WireShark to capture the packet flow - don't understand much of this but was getting sumcheck values of '0' (Len=0). It may be of use.

No. Time Source Destination Protocol Length Info
11 2.688969000 192URL.2 209URL211 TCP 66 50032 > rtsp [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
12 2.982178000 209URL211 192URL2 TCP 66 rtsp > 50032 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1452 SACK_PERM=1 WS=128
13 2.982316000 192URL2 209URL211 TCP 54 50032 > rtsp [ACK] Seq=1 Ack=1 Win=66560 Len=0
14 2.992308000 192URL2 209URL211 RTSP 191 OPTIONS rtsp://209.URL.211/2nsblive/2nsblive.sdp RTSP/1.0
15 3.286149000 209URL211 192URL2 TCP 60 rtsp > 50032 [ACK] Seq=1 Ack=138 Win=6912 Len=0
16 3.286536000 209URL211 192URL2 RTSP 259 Reply: RTSP/1.0 200 OK
17 3.286697000 192URL2 209URL211 RTSP 217 DESCRIBE rtsp://209.197.30.211/2nsblive/2nsblive.sdp RTSP/1.0
18 3.581471000 209URL211 192URL2 RTSP 137 Reply: RTSP/1.0 403 Forbidden
19 3.581690000 192URL2 209URL211 TCP 54 50032 > rtsp [FIN, ACK] Seq=301 Ack=289 Win=66304 Len=0
20 3.581917000 192URL2 209URL211 TCP 66 50033 > http [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
21 3.874177000 209URL211 192URL2 TCP 60 rtsp > 50032 [FIN, ACK] Seq=289 Ack=302 Win=8064 Len=0
22 3.874266000 192URL2 209URL211 TCP 54 50032 > rtsp [ACK] Seq=302 Ack=290 Win=66304 Len=0
23 3.875448000 209URL211 192URL2 TCP 66 http > 50033 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1452 SACK_PERM=1 WS=128
24 3.875564000 192URL2 209URL211 TCP 54 50033 > http [ACK] Seq=1 Ack=1 Win=66560 Len=0
25 3.881632000 192URL2 209URL211 HTTP 289 GET /2nsblive/2nsblive.sdp HTTP/1.0
26 4.178410000 209URL211 192URL2 TCP 60 http > 50033 [ACK] Seq=1 Ack=236 Win=6912 Len=0
27 4.178842000 209URL211 192URL2 TCP 264 [TCP segment of a reassembled PDU]
28 4.179208000 192URL2 209URL211 TCP 66 50034 > http [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
29 4.253890000 19x2.168.0.2 209URL211 TCP 54 50033 > http [ACK] Seq=236 Ack=211 Win=66560 Len=0
30 4.476102000 209URL211 19x2.168.0.2 TCP 66 http > 50034 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1452 SACK_PERM=1 WS=128
31 4.476226000 192URL2 209URL211 TCP 54 50034 > http [ACK] Seq=1 Ack=1 Win=66560 Len=0
32 4.476339000 192URL2 209URL211 TCP 358 [TCP segment of a reassembled PDU]
33 4.774146000 209URL211 192URL2 TCP 60 http > 50034 [ACK] Seq=1 Ack=305 Win=6912 Len=0
34 4.774235000 192URL2 209URL211 TCP 238 [TCP segment of a reassembled PDU]
35 5.071090000 209URL211 192URL2 TCP 60 http > 50034 [ACK] Seq=1 Ack=489 Win=8064 Len=0
36 5.071488000 209URL211 192URL2 TCP 259 [TCP segment of a reassembled PDU]
37 5.071687000 192URL2 209URL211 TCP 274 [TCP segment of a reassembled PDU]
38 5.123161000 192URL2 209URL211 TCP 54 50033 > http [ACK] Seq=236 Ack=416 Win=66304 Len=0
39 5.368206000 209URL211 192URL2 TCP 60 http > 50034 [ACK] Seq=1 Ack=709 Win=9088 Len=0
40 5.415430000 209URL211 192URL2 TCP 137 [TCP segment of a reassembled PDU]
41 5.415678000 192URL2 209URL211 TCP 54 50033 > http [FIN, ACK] Seq=236 Ack=499 Win=66048 Len=0
42 5.415742000 192URL2 209URL211 TCP 54 50034 > http [FIN, ACK] Seq=709 Ack=1 Win=66560 Len=0
43 5.417140000 192URL2 209URL211 TCP 66 50037 > rtsp [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
44 5.707981000 209URL211 192URL2 HTTP 60 HTTP/1.0 200 OK (application/x-rtsp-tunnelled)
45 5.708071000 192URL2 209URL211 TCP 54 50033 > http [ACK] Seq=237 Ack=500 Win=66048 Len=0
46 5.711965000 209URL211 192URL2 TCP 66 rtsp > 50037 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1452 SACK_PERM=1 WS=128
47 5.712061000 209URL211 192URL2 TCP 60 http > 50034 [FIN, ACK] Seq=1 Ack=710 Win=9088 Len=0
48 5.712090000 192URL2 209URL211 TCP 54 50037 > rtsp [ACK] Seq=1 Ack=1 Win=66560 Len=0
49 5.712150000 192URL2 209URL211 TCP 54 50034 > http [ACK] Seq=710 Ack=2 Win=66560 Len=0
50 5.718202000 192URL2 209URL211 TCP 98 [TCP segment of a reassembled PDU]
51 6.014373000 209URL211 192URL2 TCP 60 rtsp > 50037 [ACK] Seq=1 Ack=45 Win=5888 Len=0
52 6.014460000 192URL2 209URL211 RTSP 389 OPTIONS rtsp://209.197.30.211:554 RTSP/1.0
53 6.311309000 209URL211 192URL2 TCP 60 rtsp > 50037 [ACK] Seq=1 Ack=380 Win=6912 Len=0
54 6.311681000 209URL211 192URL2 RTSP 259 Reply: RTSP/1.0 200 OK
55 6.313123000 192URL2 209URL211 TCP 54 50037 > rtsp [FIN, ACK] Seq=380 Ack=206 Win=66560 Len=0
56 6.605949000 209URL211 192URL2 TCP 60 rtsp > 50037 [FIN, ACK] Seq=206 Ack=381 Win=6912 Len=0
57 6.606039000 192URL2 209URL211 TCP 54 50037 > rtsp [ACK] Seq=381 Ack=207 Win=66560 Len=0


In WireShark you can 'Follow the Stream' and this is what it says..

OPTIONS rtsp:// 209URL211:554 RTSP/1.0
CSeq: 1
User-Agent: RealMedia Player Version 6.0.9.1235 (linux-2.0-libc6-i386-gcc2.95)
ClientChallenge: 9e26d33f2984236010ef6253fb1887f7
PlayerStarttime: [28/03/2003:22:50:23 00:00]
CompanyID: KnKV4M4I/B2FjJ1TToLycw==
GUID: 00000000-0000-0000-0000-000000000000
RegionData: 0
ClientID: Linux_2.4_6.0.9.1235_play32_RN01_EN_586

RTSP/1.0 200 OK
Supported: play.basic, con.persistent
Cseq: 1
Server: Wowza Media Server 2.2.3.07 build27138
Public: DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE, OPTIONS, ANNOUNCE, RECORD, GET_PARAMETER


Any help would be greatly appreciated - My thanks in advance!

Re: live555 error: Failed to connect with rtsp

Posted: 15 Aug 2013 16:24
by Jean-Baptiste Kempf
live555 debug: connection error 403

Re: live555 error: Failed to connect with rtsp

Posted: 17 Aug 2013 04:57
by alank
Solved.

I have found a HTTP source that is now working.

Yeah, I saw that error but just thought it was due to the HTTP tunneling. I assume this error is coming from the transmission source but I don't understand why the RTSP stream had work fine over a number of weeks and then came to an abrupt halt.

Anyway thanks for you help. I seemed to have learned a few other things about how streaming works and after installing RealPlayer in an attempt at a fix that it is a PIA to use ... and all those ads. Will dump it now.