Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CME 4.1 to CUCM 5.1 SIP Trunk

I have setup a sip trunk between my call manager and cme. I can call any phone from CUCM to the CME. When I try to place a call from CME to CUCM I am getting a fast busy. Here is by SIP Trunk on the CME side

dial-peer voice 1003 voip

destination-pattern 393

session protocol sipv2

session target ipv4:x.x.x.x

session transport tcp

dtmf-relay rtp-nte

codec g711ulaw

no vad

transfer-system full-consult

transfer-pattern .T

transfer-pattern 8...

transfer-pattern 128..

transfer-pattern 168..

I currently have the destination setup to try and call 1 specific phone for troubleshooting. On my CUCM side I have CSS set, Destination Address, MTP Preferred Origination Codec 711ulaw. Any ideas?

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Just noticed you have "session transport tcp". Please remove that to leave the default of UDP.

8 REPLIES
VIP Super Bronze

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Please check the following:

1. MRGL that yout sip trunk is assigned has a software MTP in it

2. The CSS on the inbound calls on your sip trunk has the partiton of your ip phones in it

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Re: CME 4.1 to CUCM 5.1 SIP Trunk

I have confirmed that the SIP trunk:

MRGL has a software MTP in it

CSS for inbound calls is in the partition of my phones.

Hall of Fame Super Gold

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Hi, "393" doesn't seem right as destination-pattern. Suppose CM extensions all start with 3 and are four digits, "3..." would be right.

In any case, take "debug ccsip message" with "term mon" when calling. That will show numbers and causes.

New Member

Re: CME 4.1 to CUCM 5.1 SIP Trunk

All the ext on the CUCM side are 3 digits. I have the destination-pattern set for 393 because I was testing with 1 extention for troubleshooting.

Hall of Fame Super Gold

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Then collect the debug trace as mentioned above.

Hall of Fame Super Gold

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Just noticed you have "session transport tcp". Please remove that to leave the default of UDP.

New Member

Re: CME 4.1 to CUCM 5.1 SIP Trunk

That worked thanks!

Hall of Fame Super Gold

Re: CME 4.1 to CUCM 5.1 SIP Trunk

Thanks for the appreciation and good luck!

218
Views
0
Helpful
8
Replies