« Back to SIP Trunk Questions

rtp packets come in

Combination View Flat View Tree View
Threads [ Previous | Next ]
rtp packets come in
active recording sip trunk accept
Answer
6/15/11 3:10 AM
I have recorded calls with switch port monitor stuff in the past, now i want to use the active recording feature. But i can't accept the INVITE sip packet in order to get the rtp packets come in. The CallManager don't send any information about my fault in sip packets in order to get it working. The question is how can i get information about the reason because my sip packets are being ignored by the CallManager, some logs files or tools i can use ?
 
The following is my sip session if anywhone know what could be wrong, thanks in advance.
 
 INVITE sip:0000@192.168.100.107:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9a70127dfb
From: <sip:1007@192.168.100.11;x-nearend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024774
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-8f-b64a8c0@192.168.100.11
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <sip:192.168.100.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 1551140736-0000065536-0000000143-0191146176
Session-Expires:  1800
P-Preferred-Identity: <sip:1007@192.168.100.11>
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Contact: <sip:1007@192.168.100.11:5060>;isfocus
Max-Forwards: 70
Content-Length: 0

 

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9a70127dfb
From: <sip:1007@192.168.100.11;x-nearend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024774
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-8f-b64a8c0@192.168.100.11
CSeq: 101 INVITE
Allow-Events: presence, kpml
Content-Length: 0


SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9a70127dfb
From: <sip:1007@192.168.100.11;x-nearend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024774
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-8f-b64a8c0@192.168.100.11
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Contact: <sip:1007@192.168.100.11:5060>;isfocus
Call-Info: <sip:192.168.100.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Preferred-Identity: <sip:1007@192.168.100.11>
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Content-Length: 0


SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9a70127dfb
From: <sip:1007@192.168.100.11;x-nearend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024774
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-8f-b64a8c0@192.168.100.11
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Contact: <sip:1007@192.168.100.11:5060>;isfocus
Call-Info: <sip:192.168.100.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Preferred-Identity: <sip:1007@192.168.100.11>
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Content-Type: application/sdp
Content-Length: 340

v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 192.168.100.11
s=SIP Call
c=IN IP4 192.168.100.107
t=0 0
m=audio 4000 RTP/AVP 9 0 8 18 101
a=rtpmap:9 G722/8000
a=ptime:20
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:18 G729/8000
a=ptime:20
a=sendonly
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9a70127dfb
From: <sip:1007@192.168.100.11;x-nearend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024774
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-8f-b64a8c0@192.168.100.11
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Contact: <sip:1007@192.168.100.11:5060>;isfocus
Supported: replaces
Call-Info: <sip:192.168.100.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
P-Preferred-Identity: <sip:1007@192.168.100.11>
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Content-Type: application/sdp
Content-Length: 340

v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 192.168.100.11
s=SIP Call
c=IN IP4 192.168.100.107
t=0 0
m=audio 4000 RTP/AVP 9 0 8 18 101
a=rtpmap:9 G722/8000
a=ptime:20
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:18 G729/8000
a=ptime:20
a=sendonly
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15




 INVITE sip:0000@192.168.100.107:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.11:5060;branch=z9hG4bK9b733ee241
From: <sip:1007@192.168.100.11;x-farend;x-refci=22024770;x-nearenddevice=SEP001FCA34B442>;tag=17aaa711-49d3-4807-aa6a-f4185bae4bde-22024777
To: <sip:0000@192.168.100.107>
Date: Tue, 14 Jun 2011 22:05:16 GMT
Call-ID: 5c748780-df71db14-90-b64a8c0@192.168.100.11
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <sip:192.168.100.11:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 1551140736-0000065536-0000000144-0191146176
Session-Expires:  1800
P-Preferred-Identity: <sip:1007@192.168.100.11>
Remote-Party-ID: <sip:1007@192.168.100.11>;party=calling;screen=no;privacy=off
Contact: <sip:1007@192.168.100.11:5060>;isfocus
Max-Forwards: 70
Content-Length: 0

 
Flag

RE: rtp packets come in
Answer
7/4/11 10:31 AM as a reply to Juan Hartwig Byers.
There is my sample recorder SIP session in Delayed Offer mode (in Early Offer mode CCM will send content with codecs in INVITE message and you should select codec in your OK message, ACK will have an empty content):

-------------------------------------Received INVITE from CCM:

INVITE sip:7776@192.168.202.60:5060 SIP/2.0
Date: Wed, 29 Jun 2011 10:49:03 GMT
Call-Info: <sip:192.168.202.75:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY
From: <sip:71517@192.168.202.75;x-nearend;x-refci=31063449;x-nearenddevice=SEP001BD40B5D88>;tag=0233c108-4589-4574-ad6a-7547060a324f-31063454
Allow-Events: presence,kpml
Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation
Min-SE: 1800
Remote-Party-ID: <sip:71517@192.168.202.75>;party=calling;screen=no;privacy=off
User-Agent: Cisco-CUCM7.1
To: <sip:7776@192.168.202.60>
Contact: <sip:71517@192.168.202.75:5060>;isfocus
Expires: 180
Call-ID: 6606ff00-e0b1031f-15c19-4bcaa8c0@192.168.202.75
Via: SIP/2.0/UDP 192.168.202.75:5060;branch=z9hG4bK316cf2f392690
CSeq: 101 INVITE
P-Preferred-Identity: <sip:71517@192.168.202.75>
Session-Expires: 1800
Max-Forwards: 70
Content-Length: 0

-------------------------------------My app open port and generate OK message:

SIP/2.0 200 OK
To: <sip:7776@192.168.202.60>;tag=327ef8e1
Via: SIP/2.0/UDP 192.168.202.75:5060;branch=z9hG4bK316cf2f392690
CSeq: 101 INVITE
Call-ID: 6606ff00-e0b1031f-15c19-4bcaa8c0@192.168.202.75
From: <sip:71517@192.168.202.75;x-nearend;x-refci=31063449;x-nearenddevice=SEP001BD40B5D88>;tag=0233c108-4589-4574-ad6a-7547060a324f-31063454
Content-Type: application/sdp
Contact: <sip:7776@192.168.202.60>;expires=0
Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY,PUBLISH
User-Agent: SIP/1.0.1
Content-Length: 286

v=0
o=PhoneUP_Recorder 2000 1 IN IP4 192.168.202.60
s=SIP Call
c=IN IP4 192.168.202.60
t=0 0
m=audio 1024 RTP/AVP 0 9 18 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:9 G722/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

-------------------------------------Received ACK from CCM:

ACK sip:7776@192.168.202.60:5060 SIP/2.0
Date: Wed, 29 Jun 2011 10:49:03 GMT
From: <sip:71517@192.168.202.75;x-nearend;x-refci=31063449;x-nearenddevice=SEP001BD40B5D88>;tag=0233c108-4589-4574-ad6a-7547060a324f-31063454
Allow-Events: presence,kpml
To: <sip:7776@192.168.202.60>;tag=327ef8e1
Content-Type: application/sdp
Call-ID: 6606ff00-e0b1031f-15c19-4bcaa8c0@192.168.202.75
Via: SIP/2.0/UDP 192.168.202.75:5060;branch=z9hG4bK316d25eb6a6aa
CSeq: 101 ACK
Max-Forwards: 70
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 192.168.202.75
s=SIP Call
c=IN IP4 192.168.202.46
t=0 0
m=audio 4000 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=sendonly
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

-------------------------------------Session start completed - rtp packets come in...

-------------------------------------Received BYE from CCM:

BYE sip:7776@192.168.202.60:5060 SIP/2.0
Date: Wed, 29 Jun 2011 10:49:03 GMT
From: <sip:71517@192.168.202.75;x-nearend;x-refci=31063449;x-nearenddevice=SEP001BD40B5D88>;tag=0233c108-4589-4574-ad6a-7547060a324f-31063454
User-Agent: Cisco-CUCM7.1
To: <sip:7776@192.168.202.60>;tag=327ef8e1
Call-ID: 6606ff00-e0b1031f-15c19-4bcaa8c0@192.168.202.75
Via: SIP/2.0/UDP 192.168.202.75:5060;branch=z9hG4bK316d527094536
P-Preferred-Identity: <sip:71517@192.168.202.75>
CSeq: 102 BYE
Max-Forwards: 70
Content-Length: 0

-------------------------------------My app close port and generate OK:

SIP/2.0 200 OK
To: <sip:7776@192.168.202.60>;tag=327ef8e1
Via: SIP/2.0/UDP 192.168.202.75:5060;branch=z9hG4bK316d527094536
CSeq: 102 BYE
Call-ID: 6606ff00-e0b1031f-15c19-4bcaa8c0@192.168.202.75
From: <sip:71517@192.168.202.75;x-nearend;x-refci=31063449;x-nearenddevice=SEP001BD40B5D88>;tag=0233c108-4589-4574-ad6a-7547060a324f-31063454
Contact: <sip:7776@192.168.202.60>;expires=0
Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY,PUBLISH
User-Agent: SIP/1.0.1
Content-Length: 0
Flag

RE: rtp packets come in
Answer
7/25/11 6:20 PM as a reply to Sergei Gorbunov.
Sergei, Thanks for your post, it was very useful, we are using active recording now. The next step is to implement this with encrypted calls, have you tried this before, any hints in this, do you think it is possible?


Regards,

Juan
Flag