[Live-devel] New LIVE555 release - fixes a problem with

Kamil Dobkowski kamildobk at poczta.onet.pl
Mon Jul 12 00:02:40 PDT 2010


Hi,
I downloaded LiveMedia once again and rebuilded whole project from fresh sources, but the effect is still the same. This is an example output from RTP over TCP session. Command line is :

openRTSP.exe -u admin admin -F rtp-tcp-data -t rtsp://192.168.3.75/VideoInput/1/jpeg/1 > _rtp_over_tcp.txt 2>&1

openRTSP output is ( rtp-tcp-data file is empty - it has 0 bytes and there are some strange errors : sendRTPOverTCP: failed!  int the output logs ) :

Opening connection to 192.168.3.75, port 554...
...remote connection opened
Sending request: OPTIONS rtsp://192.168.3.75/VideoInput/1/jpeg/1 RTSP/1.0

CSeq: 2

User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.07.07)




Received 96 new bytes of response data.
Received a complete OPTIONS response:
RTSP/1.0 200 OK

CSeq: 2

Server: SANYO RTSP Server

Public: DESCRIBE, SETUP, TEARDOWN, PLAY




Sending request: DESCRIBE rtsp://192.168.3.75/VideoInput/1/jpeg/1 RTSP/1.0

CSeq: 3

User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.07.07)

Accept: application/sdp




Received 100 new bytes of response data.
Received a complete DESCRIBE response:
RTSP/1.0 401 Unauthorized

CSeq: 3

Server: SANYO RTSP Server

WWW-Authenticate: Basic realm="/"




Resending...
Sending request: DESCRIBE rtsp://192.168.3.75/VideoInput/1/jpeg/1 RTSP/1.0

CSeq: 4

Authorization: Basic YWRtaW46YWRtaW4=

User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.07.07)

Accept: application/sdp




Received 187 new bytes of response data.
Have received 187 total bytes of a DESCRIBE RTSP response; awaiting 238 bytes more.
Received 238 new bytes of response data.
Received a complete DESCRIBE response:
RTSP/1.0 200 OK

CSeq: 4

Server: SANYO RTSP Server

Content-Base: rtsp://192.168.3.75/VideoInput/1/jpeg/1

Content-Type: application/sdp

Content-Length: 238

Cache-Control: no-cache



v=0

o=- -3466302438249376441 -3466302438248272635 IN IP4 192.168.3.75

s=Media Presentation

c=IN IP4 0.0.0.0

b=AS:944

t=0 0

m=video 0 RTP/AVP 26

b=AS:880

a=framerate:5.0

a=quality:0

a=control:trackID=0

a=rtpmap:26 JPEG/90000




Opened URL "rtsp://192.168.3.75/VideoInput/1/jpeg/1", returning a SDP description:
v=0

o=- -3466302438249376441 -3466302438248272635 IN IP4 192.168.3.75

s=Media Presentation

c=IN IP4 0.0.0.0

b=AS:944

t=0 0

m=video 0 RTP/AVP 26

b=AS:880

a=framerate:5.0

a=quality:0

a=control:trackID=0

a=rtpmap:26 JPEG/90000




RTCPInstance[0025DF58]::RTCPInstance()
schedule(1.026081->1278917070.353562)
Created receiver for "video/JPEG" subsession (client ports 49898-49899)
Sending request: SETUP rtsp://192.168.3.75/VideoInput/1/jpeg/1/trackID=0 RTSP/1.0

CSeq: 5

Authorization: Basic YWRtaW46YWRtaW4=

User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.07.07)

Transport: RTP/AVP/TCP;unicast;interleaved=0-1




Received 145 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK

CSeq: 5

Server: SANYO RTSP Server

Session: 00370932;timeout=60

Transport: RTP/AVP/TCP;unicast;interleaved=0-1;mode="PLAY"




Setup "video/JPEG" subsession (client ports 49898-49899)
Created output file: "_sanyo-tcp-2video-JPEG-1"
Sending request: PLAY rtsp://192.168.3.75/VideoInput/1/jpeg/1 RTSP/1.0

CSeq: 6

Authorization: Basic YWRtaW46YWRtaW4=

User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.07.07)

Session: 00370932

Range: npt=0.000-




Received a complete PLAY response:
RTSP/1.0 200 OK

CSeq: 6

Server: SANYO RTSP Server

Session: 00370932

Range: npt=now-

RTP-Info: url=VideoInput/1/jpeg/1/trackID=1;seq=1;rtptime=0




Started playing session
Receiving streamed data...
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(1.025838->1278917071.379863)
schedule(1.025086->1278917072.405915)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052049->1278917074.459067)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052058->1278917076.512183)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051872->1278917078.565193)
schedule(0.000056->1278917078.565310)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051972->1278917080.618363)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052033->1278917082.671521)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052049->1278917084.724676)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051986->1278917086.777710)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052025->1278917088.830846)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051975->1278917090.883915)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051999->1278917092.936068)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051975->1278917094.989158)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052034->1278917097.042345)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051990->1278917099.095418)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052062->1278917101.148599)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051958->1278917103.201604)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051999->1278917105.253802)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051953->1278917107.306847)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.051943->1278917109.358985)
schedule(-0.000001->1278917109.359013)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: completed
schedule(2.052011->1278917111.411215)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052039->1278917113.464248)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.051988->1278917115.517313)
schedule(0.000052->1278917115.517427)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052017->1278917117.570468)
schedule(0.000052->1278917117.570549)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052014->1278917119.623567)
schedule(0.000005->1278917119.623612)
schedule(-0.000000->1278917119.623666)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052100->1278917121.675883)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052107->1278917123.728901)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052102->1278917125.782022)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.051997->1278917127.835040)
schedule(0.000004->1278917127.835078)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052035->1278917129.887217)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052071->1278917131.940335)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052103->1278917133.993477)
sending REPORT
sending RTCP packet
 80c90001 800043da 81ca0004 800043da 01084b61 6d696c2d 50430000
sendRTPOverTCP: 28 bytes over channel 1 (socket 76)
sendRTPOverTCP: failed!
schedule(2.052021->1278917136.046527)
^C
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20100712/efe24365/attachment-0001.html>


More information about the live-devel mailing list