Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1563
Views
0
Helpful
1
Replies

Supported RTP Payload Types on a SIP Trunk

TimothyBernard
Level 1
Level 1

‎07-09-2014 04:41 AM - edited ‎03-16-2019 11:21 PM

Hi All,

I am having a problem in setting the supported payload types for SIP trunks. I currently have the following configuration:

SIP Phone --> CUCM (9.1) --> SIP Trunk --> CUCM (4.1) --> SCCP Phone


I am able to make calls between the SIP and SCCP phones just fine. When the call is being setup the phone advertises several payload types (0, 97, 98, 99, 101) in it's invite to the CUCM. However, the CUCM is removing these and only passing along 0 and 101 on the invite sent out on the trunk. This is causing problems for me later on in the call.

As a note, if I place this same type of call between endpoints on the same CUCM (no trunk involved), the required codecs are not being removed by CUCM.

 

Any help or guidance would be appreciated.

 

 

Thanks,

Tim

Labels:
0 Helpful
1 Reply 1

TimothyBernard
Level 1
Level 1

‎07-10-2014 10:25 AM

Here is a wireshark capture of this call. Some details:

200.200.100.9 - SIP callmanager (CUCM 9.1)

200.200.100.101 - SIP Phone

200.100.0.2 - SCCP callmanager (CUCM 4.1)

 

INVITE sip:69935616@200.200.100.9:5060;transport=UDP SIP/2.0
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 INVITE
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c1-42d5bd6-10000
Max-Forwards: 70
Supported: replaces,timer
Allow: INVITE, ACK, BYE, REFER, NOTIFY, CANCEL
Contact: <sip:1234@200.200.100.101:5060;transport=UDP>
Session-Expires: 1800
Min-SE: 90
Content-Type: application/sdp
Content-Length: 546
v=0
o=1234 70081496 70081496 IN IP4 200.200.100.101
s=
c=IN IP4 200.200.100.101
t=0 0
m=audio 50000 RTP/AVP 0 18 4 96 118 126
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/6300
a=rtpmap:96 telephone-event/8000
a=rtpmap:118 v150fw/8000
a=rtpmap:126 NoAudio/8000
a=ptime:10
a=SilenceSupp:on
a=fmtp:18 annexb=yes
a=fmtp:96 0-16,32-35
a=fmtp:118 1,3
a=sqn:0
a=cdsc:1 audio udpsprt 120
a=cpar:a=sprtmap:120 v150mr/8000
a=cpar:a=fmtp:120 mr=1;mg=0;CDSCselect=1;mrmods=1-4,10-14,16-17;jmdelay=no;versn=1.1
a=sendrecv

 

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c1-42d5bd6-10000
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 INVITE
Allow-Events: presence
Content-Length: 0

 

INVITE sip:69935616@200.100.0.2:5060 SIP/2.0
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d46841cd2f
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Cisco-Guid: 1787982080-0000065536-0000000616-0157599944
Session-Expires:  1800
P-Asserted-Identity: <sip:1234@200.200.100.9>
Remote-Party-ID: <sip:1234@200.200.100.9>;party=calling;screen=yes;privacy=off
Contact: <sip:1234@200.200.100.9:5060>
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 215
v=0
o=CiscoSystemsCCM-SIP 21791 1 IN IP4 200.200.100.9
s=SIP Call
c=IN IP4 200.200.100.9
t=0 0
m=audio 25210 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

 

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d46841cd2f
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>;tag=16777884
Date: Wed, 09 Jul 2014 11:22:52 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
CSeq: 101 INVITE
Allow-Events: telephone-event
Content-Length: 0

 

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d46841cd2f
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>;tag=16777884
Date: Wed, 09 Jul 2014 11:22:52 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
Allow-Events: telephone-event
Remote-Party-ID: <sip:9935616@200.100.0.2>;party=called;screen=no;privacy=off
Contact: <sip:69935616@200.100.0.2:5060>
Content-Disposition: session;handling=required
Content-Type: application/sdp
Content-Length: 225
v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 200.100.0.2
s=SIP Call
c=IN IP4 200.100.0.2
t=0 0
m=audio 25226 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

 

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d46841cd2f
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>;tag=16777884
Date: Wed, 09 Jul 2014 11:22:52 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
Allow-Events: telephone-event
Remote-Party-ID: <sip:9935616@200.100.0.2>;party=called;screen=no;privacy=off
Contact: <sip:69935616@200.100.0.2:5060>
Content-Disposition: session;handling=required
Content-Type: application/sdp
Content-Length: 225
v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 200.100.0.2
s=SIP Call
c=IN IP4 200.100.0.2
t=0 0
m=audio 25226 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

 

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c1-42d5bd6-10000
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Send-Info: conference, x-cisco-conference
Remote-Party-ID: <sip:9935616@200.200.100.9>;party=called;screen=no;privacy=off
Contact: <sip:69935616@200.200.100.9:5060>
Content-Type: application/sdp
Content-Length: 235
v=0
o=CiscoSystemsCCM-SIP 21790 1 IN IP4 200.200.100.9
s=SIP Call
c=IN IP4 200.200.100.9
b=TIAS:64000
b=AS:64
t=0 0
m=audio 25212 RTP/AVP 0 96
a=rtpmap:0 PCMU/8000
a=ptime:10
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15

 

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c1-42d5bd6-10000
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Send-Info: conference, x-cisco-conference
Remote-Party-ID: <sip:9935616@200.200.100.9>;party=called;screen=no;privacy=off
Contact: <sip:69935616@200.200.100.9:5060>
Content-Length: 0

 

SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d46841cd2f
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>;tag=16777884
Date: Wed, 09 Jul 2014 11:22:52 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
CSeq: 101 INVITE
Session-Expires: 1800;refresher=uac
Require: timer
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
Allow-Events: telephone-event
Remote-Party-ID: <sip:9935616@200.100.0.2>;party=called;screen=yes;privacy=off
Contact: <sip:69935616@200.100.0.2:5060>
Content-Type: application/sdp
Content-Length: 225
v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 200.100.0.2
s=SIP Call
c=IN IP4 200.100.0.2
t=0 0
m=audio 25226 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

 

ACK sip:69935616@200.100.0.2:5060 SIP/2.0
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d5376fb860
From: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
To: <sip:69935616@200.100.0.2>;tag=16777884
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

 

SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c1-42d5bd6-10000
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
Date: Wed, 09 Jul 2014 10:40:19 GMT
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Send-Info: conference, x-cisco-conference
Session-Expires:  1800;refresher=uas
Require:  timer
Remote-Party-ID: <sip:9935616@200.200.100.9>;party=called;screen=yes;privacy=off
Contact: <sip:69935616@200.200.100.9:5060>
Content-Type: application/sdp
Content-Length: 235
v=0
o=CiscoSystemsCCM-SIP 21790 1 IN IP4 200.200.100.9
s=SIP Call
c=IN IP4 200.200.100.9
b=TIAS:64000
b=AS:64
t=0 0
m=audio 25212 RTP/AVP 0 96
a=rtpmap:0 PCMU/8000
a=ptime:10
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15

 

ACK sip:69935616@200.200.100.9:5060 SIP/2.0
From: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
To: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 1 ACK
Via: SIP/2.0/UDP 200.200.100.101:5060;rport;branch=z9hG4bK-111c9-42d7cd8-10001
Max-Forwards: 70
Contact: <sip:1234@200.200.100.101:5060;transport=UDP>
Content-Length: 0

 

BYE sip:1234@200.200.100.9:5060 SIP/2.0
Via: SIP/2.0/UDP  200.100.0.2:5060;branch=z9hG4bK21b04360
From: <sip:69935616@200.100.0.2>;tag=16777884
To: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
Date: Wed, 09 Jul 2014 11:23:00 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
User-Agent: Cisco-CCM4.1
Max-Forwards: 70
CSeq: 101 BYE
Content-Length: 0

 

SIP/2.0 200 OK
Via: SIP/2.0/UDP  200.100.0.2:5060;branch=z9hG4bK21b04360
From: <sip:69935616@200.100.0.2>;tag=16777884
To: <sip:1234@200.200.100.9>;tag=21791~64ed6652-41a2-4296-bdd8-87c4330590d0-27980332
Date: Wed, 09 Jul 2014 10:40:31 GMT
Call-ID: 6a927100-3bd11c13-1ad-964c8c8@200.200.100.9
CSeq: 101 BYE
Content-Length: 0

 

BYE sip:1234@200.200.100.101:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d6346013bc
From: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
To: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
Date: Wed, 09 Jul 2014 10:40:28 GMT
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
User-Agent: Cisco-CUCM9.1
Max-Forwards: 70
CSeq: 101 BYE
Reason: Q.850;cause=16
Content-Length: 0

 

SIP/2.0 200 OK
From: "69935616"<sip:69935616@200.200.100.9:5060;user=phone>;tag=21790~64ed6652-41a2-4296-bdd8-87c4330590d0-27980331
To: "1234"<sip:1234@200.200.100.9>;tag=95ad3228-c8c86465-13c4-a35c-20003-d6217e11
Call-ID: 95ad9280-c8c86465-13c4-80a0-10001-3b31f82@200.200.100.9
CSeq: 101 BYE
Via: SIP/2.0/UDP 200.200.100.9:5060;branch=z9hG4bK1d6346013bc
Supported: replaces,timer
P-RTP-Stat: PS=271,OS=22340,PR=1110,OR=88800,PL=0,JI=78,DU=2
Content-Length: 0

0 Helpful
Customers Also Viewed These Support Documents