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

Dial-peer for international call not working

Hi,

I'm trying to setup a working international dial-peer on ccme.

Every time I try to dial the following on my debug output I see it match the following dialpeers:

dial-peer 2003

dial-peer 1001

dial-peer 20018

I found a preconfigured dial-peer, dialpeer 64 and also tried creating a dial-peer, dialpeer 5004.

When I try to dial, I can dial 901 but once I dial the 4th digit 9011 it gives a slow busy signal.

This is a UC520 CME system.

Any advice?

Config attached.

-TIA

Fred

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Dial-peer for international call not working

You can delete dial peers 1000-1008. You will need 2 dial peers - one for incoming calls from the SIP trunk, one for outgoing calls to the SIP trunk. So, dial peer 5004 as mentioned in your last post would work for outgoing calls destined for DNs 5000-5999 on CUCM. You would need another dial peer for incoming calls from CUCM such as:

dial-peer 5005 voip

incoming-called number [1239]..

session protocol sipv2

codec g711ulaw

no vad

This would cover calls to DNs 100-199, 200-299, 300-399 and 900-999 on the CME.

Hope this helps.

Brandon

3 REPLIES

Re: Dial-peer for international call not working

Fred,

A couple of suggestions.

1. You have many dial peers with "preference 5". When you have multiple dial peers for a given destination pattern, these should have different preferences so that calls to to port 0, 1, 2, etc. sequentially. So, make you preferences "prefernce 0 (the default)", "preference 1", "preference 2", etc.

2. Remove dial peer 5004

3. Change your CUE numbers so they don't overlap with your dial plan. For example, the CUE AA number is 901$. Make it 801$ or another non-overlapping number.

4. Change your SIP trunk destination pattern to something more specific than 9T or remove this dial peer and make the SIP trunk another dial peer and preference for your existing patterns.

Let me know if you have questions and where you are after these changes.

Brandon

New Member

Re: Dial-peer for international call not working

Brandon,

I was able to resolve issues problems with suggestion 1,2,3. I changed my outgoing dial key from 9 to 8.

I'm not quite sure how to resolve suggestion 4 because I want to make a SIP trunk connection that connects to CUCM4.2 from my CME.

On CUCM4.2, I created sip trunk, and defined a route pattern to use the SIP trunk (trunk going to CCME).

For CUCM4.2 I also had to use a different port than the default port 5060 for incoming/outgoing, I changed it to 5061 for incoming/outgoing.

My question is for CME side, should I use dial-peer 1000-1008? Or is it best to create a new dial-peer for this task and delete dialpeer 1000-1008.

I found a dial-peer in another article on forums I'm not sure if this is the proper one for what I'm trying to accomplish.

dial-peer voice 5004 voip

destination-pattern 5....

session protocol sipv2

session target ipv4:CUCMIPhere

session transport tcp

dtmf-relay rtp-nte

codec g711ulaw

no vad

Also, thanks for the reply every suggestion was correct.

-Fred

Re: Dial-peer for international call not working

You can delete dial peers 1000-1008. You will need 2 dial peers - one for incoming calls from the SIP trunk, one for outgoing calls to the SIP trunk. So, dial peer 5004 as mentioned in your last post would work for outgoing calls destined for DNs 5000-5999 on CUCM. You would need another dial peer for incoming calls from CUCM such as:

dial-peer 5005 voip

incoming-called number [1239]..

session protocol sipv2

codec g711ulaw

no vad

This would cover calls to DNs 100-199, 200-299, 300-399 and 900-999 on the CME.

Hope this helps.

Brandon

491
Views
5
Helpful
3
Replies
CreatePlease to create content