cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1677
Views
0
Helpful
1
Replies

RTSP Stream terminnating Prematurely

banderson614
Level 1
Level 1

We are requesting RTSP streams of calls that MediaSense is currently recording, but after 120 seconds the streams terminate. Since in the response to the initial play request we get “timeout=120” this appears to be an issue with the session timing out. We have tried sending both Play and Options messages for the same session  prior to the 120 seconds in order to prevent the session from timing out, but this has not worked. We are seeing this in our lab and at a customer's site so i do not believe that it is environmental.


Here is a pcap tcp trace of our request to the MediaSense and it's responses to us


Highlighted in yellow = Coming from Uptivity   Highlighted in green = Coming from Mediasense

OPTIONS rtsp://10.105.30.196/eca1454785bdad1 RTSP/1.0

CSeq: 1

User-Agent: CC_RTSP_Client

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

       

RTSP/1.0 200 OK

Server: Cisco MediaSense Media Server

CSeq: 1

Public: DESCRIBE, PLAY, SETUP, SET_PARAMETER, GET_PARAMETER, TEARDOWN, PAUSE, RECORD, OPTIONS

DESCRIBE rtsp://10.105.30.196/eca1454785bdad1 RTSP/1.0

CSeq: 2

User-Agent: CC_RTSP_Client

Accept: application/sdp

Accept-Language: en-US

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

RTSP/1.0 302 Moved Temporarily

Server: Cisco MediaSense Media Server

CSeq: 2

Location: rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064633^d0ab401d956c9fd0ae23ec7e8c1915f49cb6e9e8

DESCRIBE rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 3

User-Agent: CC_RTSP_Client

Accept: application/sdp

Accept-Language: en-US

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

        RTSP/1.0 200 OK

CSeq: 3

Content-Base: rtsp://10.105.30.196:9554/eca1454785bdad1/

Content-Type: application/sdp

Content-Length: 743

v=0

o=- 15487880279310217208 15487880279310217808 IN IP4 10.105.30.196

s=Cisco Live Media Streaming Session

e=NONE

c=IN IP4 10.105.30.196

u=rtsp://10.105.30.196:9554/eca1454785bdad1

t=0 0

a=control:rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822

m=audio 0 RTP/AVP 0 13

a=range:npt=now-

b=AS:8000

a=control:rtsp://10.105.30.196:9554/Pool_Device_122/Audio_Pool_122?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822

m=audio 0 RTP/AVP 0 13

a=range:npt=now-

b=AS:8000

a=control:rtsp://10.105.30.196:9554/Pool_Device_123/Audio_Pool_123?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822

SETUP rtsp://10.105.30.196:9554/Pool_Device_122/Audio_Pool_122?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 4

User-Agent: CC_RTSP_Client

Accept-Language: en-US

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

Transport: RTP/AVP;unicast;client_port=6970-6971

x-retransmit: our-retransmit

x-dynamic-rate: 1

x-transport-options: late-tolerance=2.900000

       

RTSP/1.0 200 OK

CSeq: 4

Session: 747595639;timeout=120

Transport: RTP/AVP;unicast;client_port=6970-6971;server_port=24576-24577;mode="PLAY";ssrc=516173345

SETUP rtsp://10.105.30.196:9554/Pool_Device_123/Audio_Pool_123?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 5

User-Agent: CC_RTSP_Client

Accept-Language: en-US

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

Transport: RTP/AVP;unicast;client_port=6972-6973

Session: 747595639

x-retransmit: our-retransmit

x-dynamic-rate: 1

x-transport-options: late-tolerance=2.900000

       

RTSP/1.0 200 OK

CSeq: 5

Session: 747595639;timeout=120

Transport: RTP/AVP;unicast;client_port=6972-6973;server_port=24578-24579;mode="PLAY";ssrc=516173346

PLAY rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 6

User-Agent: CC_RTSP_Client

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

Session: 747595639

Range: npt=0.000000-

x-prebuffer: maxtime=2.000000

RTSP/1.0 200 OK

CSeq: 6

Session: 747595639

RTP-Info: url=rtsp://10.105.30.196:9554/Pool_Device_122/Audio_Pool_122;seqno=61268,url=rtsp://10.105.30.196:9554/Pool_Device_123/Audio_Pool_123;seqno=37325

Range: npt=0.00-

OPTIONS rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 7

User-Agent: CC_RTSP_Client

Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy

Session: 747595639

RTSP/1.0 200 OK

CSeq: 7

Session: 747595639

Public: DESCRIBE, SETUP, PLAY, PAUSE, TEARDOWN, PAUSE, GET_PARAMETER, SET_PARAMETER, ANNOUNCE

TEARDOWN rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0

CSeq: 10

User-Agent: CC_RTSP_Client

Session: 747595639

RTSP/1.0 454 Session Not Found (Session <747595639> not found)

CSeq: 10

Session: 747595639

I have also attached the MediaSense API service and Call control services logs for a different example:

MediaSense IP: 10.105.30.196

Our service IP: 10.100.5.124

Test call with trace log:

RTSP URI: rtsp://10.105.30.196/eca1454785bdad1 

SessionId: 747595639

The test call start at: 2014-04-09 13:25:17.330 Debug 0 Stream Detected - Remote Recording Start with RTSP URI:rtsp://10.105.30.196/eca1454785bdad1

RTSP setup message send: 2014-04-09 13:25:30.285 Debug   0 RTSP Request message:["OPTIONS rtsp://10.105.30.196/eca1454785bdad1 RTSP/1.0","CSeq: 1","User-Agent: CC_RTSP_Client","Authorization: Basic Y3RpdXNlcjpjdGl1c2Vy","",""]   

RTSP Play message send: 2014-04-09 13:25:32.987 Debug   0 RTSP >> Request message:"PLAY rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0\r\nCSeq: 6\r\nUser-Agent: CC_RTSP_Client\r\nAuthorization: Basic Y3RpdXNlcjpjdGl1c2Vy\r\nSession: 747595639\r\nRange: npt=0.000000-\r\nx-prebuffer: maxtime=2.000000\r\n\r\n"      

Repeating option messages:

2014-04-09 13:27:27.974 Debug 0 RTSP >> Request message:"OPTIONS rtsp://10.105.30.196:9554/eca1454785bdad1?token=eca1454785bdad1^LA^0^0^0^1397064634^e5833cdd052f0b8f1f9aa63d530c08922d641822 RTSP/1.0\r\nCSeq: 7\r\nUser-Agent: CC_RTSP_Client\r\nAuthorization: Basic Y3RpdXNlcjpjdGl1c2Vy\r\nSession: 747595639\r\n\r\n"

Last UDP message send by MediaSense: 2014-04-09 13:27:33.748102

Stream duration: 13:25:33.052665 ~ 13:27:33.748102 (see AudioStreamStart.png and AudioStreamStop.png))

1 Reply 1

mbenenso
Level 1
Level 1

Hi

MS use ICMP ping to check, if client ip is available, if MS does not receives responses to ping, it will stop sending playback RTP

I do not see ICMP pings in the tcpdump, seems ping from MS box to the client box does not come through.

could you, please:

1. verify that you could ping client ip from the MS box using CLI command

-- utils network ping <client_ip> count 10

2. If tcpdump was collected on Client box, collect it on MS box, using CLI command

--- utils network capture file tcpdump1 count 100000 size ALL

and then download pcap to your sftp serevr, using CLI command

--- file get activelog platform/cli/tcpdump1.cap

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: