[Live-devel] Developed a Server, choose "RTSP-over-UDP" was ok, but choose "RTSP-over-TCP" was error

Thu Dec 18 19:24:12 PST 2014

Hi ALL.
    I developed a program modeled "testOnDemandRTSPServer" capture screen in real time, and then compressed into h264 and released. In the beginning the test, the client uses UDP to transmit data, the server is working properly. Then I want to test TCP mode, let the client choose RTSP over tcp, server performance is not normal, probably sent a few minutes after stop sending packets (using Wireshark capture). In debug mode, the server is still report "sending report, sending packet……". Until 65 seconds (default timeout) after the service side display "time out".
    Then I tried a variety of approaches to debug, still does not solve the problem. So to see the "live555MediaServer" source code and use it as a server test, the results "live555MediaServer" also have this problem, and greater the resolution of the video, there is a problem of time sooner.

 Remarks:
    1. the server (live555 libraries and MediaServer): Version Dec 09 2014
    2. the client has three: testRTSPClient, VLC (2.1.5), FFMpeg (N-67100, oct 22 2014).
    3. if the server has consol window and enable DEBUG_SEND, then the server is working properly.

 Redirect "stderr" to file, the information:
Play using the URL "rtsp://192.168.10.117/live"
 (We use port 80 for optional RTSP-over-HTTP tunneling.)
accept()ed connection from 192.168.10.117
RTSPClientConnection[006B12E8]::handleRequestBytes() read 87 new bytes:OPTIONS rtsp://192.168.10.117:554/live RTSP/1.0
 CSeq: 1
 User-Agent: Lavf56.10.100

parseRTSPRequestString() succeeded, returning cmdName "OPTIONS", urlPreSuffix "", urlSuffix "live", CSeq "1", Content-Length 0, with 0 bytes following the message.
sending response: RTSP/1.0 200 OK
 CSeq: 1
 Date: Fri, Dec 19 2014 02:48:44 GMT
 Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY, PAUSE, GET_PARAMETER, SET_PARAMETER

 RTSPClientConnection[006B12E8]::handleRequestBytes() read 113 new bytes:DESCRIBE rtsp://192.168.10.117:554/live RTSP/1.0
 Accept: application/sdp
 CSeq: 2
 User-Agent: Lavf56.10.100

parseRTSPRequestString() succeeded, returning cmdName "DESCRIBE", urlPreSuffix "", urlSuffix "live", CSeq "2", Content-Length 0, with 0 bytes following the message.
sending response: RTSP/1.0 200 OK
 CSeq: 2
 Date: Fri, Dec 19 2014 02:48:44 GMT
 Content-Base: rtsp://192.168.10.117/live/
 Content-Type: application/sdp
 Content-Length: 503

 v=0
 o=- 1418957320293789 1 IN IP4 192.168.10.117
 s=Session streamed by "testOnDemandRTSPServer"
 i=live
 t=0 0
 a=tool:LIVE555 Streaming Media v2014.12.17
 a=type:broadcast
 a=control:*
 a=range:npt=0-
 a=x-qt-text-nam:Session streamed by "testOnDemandRTSPServer"
 a=x-qt-text-inf:live
 m=video 0 RTP/AVP 96
 c=IN IP4 0.0.0.0
 b=AS:96
 a=rtpmap:96 H264/90000
 a=fmtp:96 packetization-mode=1;profile-level-id=64001F;sprop-parameter-sets=Z2QAH6zZQMgTflw4QAAAAwBAAAAMg8YMZYA=,aOvjyyLA
 a=control:track1
 RTSPClientConnection[006B12E8]::handleRequestBytes() read 136 new bytes:SETUP rtsp://192.168.10.117/live/track1 RTSP/1.0
 Transport: RTP/AVP/TCP;unicast;interleaved=0-1
 CSeq: 3
 User-Agent: Lavf56.10.100

parseRTSPRequestString() succeeded, returning cmdName "SETUP", urlPreSuffix "live", urlSuffix "track1", CSeq "3", Content-Length 0, with 0 bytes following the message.
sending response: RTSP/1.0 200 OK
 CSeq: 3
 Date: Fri, Dec 19 2014 02:48:44 GMT
 Transport: RTP/AVP/TCP;unicast;destination=192.168.10.117;source=192.168.10.117;interleaved=0-1
 Session: 866DBD85;timeout=65

 RTSPClientConnection[006B12E8]::handleRequestBytes() read 119 new bytes:PLAY rtsp://192.168.10.117/live/ RTSP/1.0
 Range: npt=0.000-
 CSeq: 4
 User-Agent: Lavf56.10.100
 Session: 866DBD85

parseRTSPRequestString() succeeded, returning cmdName "PLAY", urlPreSuffix "live", urlSuffix "", CSeq "4", Content-Length 0, with 0 bytes following the message.
RTCPInstance[0074CAE8]::RTCPInstance()
schedule(1.778641->1418957326.302863)
SocketDescriptor(socket 528)::registerRTPInterface(channel 0): isFirstRegistration 1
SocketDescriptor(socket 528)::registerRTPInterface(channel 1): isFirstRegistration 0
SocketDescriptor(socket 528)::registerRTPInterface(channel 1): isFirstRegistration 0
sending REPORT
sending RTCP packet
 80c80006 efcaaa68 d83e108c 8634eb9a ee023e83 00000000 00000000 81ca0005 efcaaa68 010d5869 654d696e 677a616e 2d706300
sendRTPorRTCPPacketOverTCP: 52 bytes over channel 1 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
sendRTPorRTCPPacketOverTCP: 492 bytes over channel 0 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
sending response: RTSP/1.0 200 OK
 CSeq: 4
 Date: Fri, Dec 19 2014 02:48:44 GMT
 Range: npt=0.000-
 Session: 866DBD85
 RTP-Info: url=rtsp://192.168.10.117/live/track1;seq=59383;rtptime=3993136724

 sendRTPorRTCPPacketOverTCP: 42 bytes over channel 0 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
sendRTPorRTCPPacketOverTCP: 20 bytes over channel 0 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
sendRTPorRTCPPacketOverTCP: 1456 bytes over channel 0 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
sendRTPorRTCPPacketOverTCP: 1456 bytes over channel 0 (socket 528)
sendRTPorRTCPPacketOverTCP: completed
......
......
......
sendRTPorRTCPPacketOverTCP: completed
sendRTPorRTCPPacketOverTCP: 1456 bytes over channel 0 (socket 528)
SocketDescriptor(socket 528)::deregisterRTPInterface(channel 255)
sendRTPorRTCPPacketOverTCP: failed! (errno 10035)
sending REPORT
sending RTCP packet
 80c80006 efcaaa68 d83e1097 b6290eed ee119b9d 000007c9 002b16e4 81ca0005 efcaaa68 010d5869 654d696e 677a616e 2d706300
schedule(3.052983->1418957338.764567)
schedule(1.448056->1418957340.220447)
sending REPORT
......
......
......
sending REPORT
sending RTCP packet
 80c80006 efcaaa68 d83e10c9 04cc4695 ee55522b 00000c7f 003f286f 81ca0005 efcaaa68 010d5869 654d696e 677a616e 2d706300
schedule(4.098311->1418957389.117072)
sending REPORT
sending RTCP packet
 80c80006 efcaaa68 d83e10cd 329e6eeb ee5b0f58 00000de7 00467069 81ca0005 efcaaa68 010d5869 654d696e 677a616e 2d706300
schedule(5.901020->1418957395.098769)
RTSP client session (id "866DBD85", stream name "live") has timed out (due to inactivity)
RTCPInstance[0074CAE8]::~RTCPInstance()
sending BYE
sending RTCP packet
 80c80006 efcaaa68 d83e10cd 89e1198b ee5b872d 00000ded 004687c5 81cb0001 efcaaa68
RTSPClientConnection[006B12E8]::handleRequestBytes() read -1 new bytes (of 20000); terminating connection!

  Regards,
Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20141219/3bbfe0b6/attachment-0001.html>