Outbound dial peer selection

Answered Question
Feb 1st, 2012

I have a customer with the following dial peers on a 15.1 CME router:

dial-peer voice 402 pots                  
corlist outgoing CORList-Mobile
description Outbound-SNPR-Mobile
translation-profile outgoing callerid
destination-pattern 98.......                   (9 digits entered)


port 0/0/0:15
forward-digits 8

dial-peer voice 404 pots
corlist outgoing CORList-TollFreeIntl
description Outbound-SNPR-TollFreeIntl
translation-profile outgoing callerid
destination-pattern 9800.......                (11 digits entered)
port 0/0/0:15
forward-digits 10

The problem is that when an IP phone dials 98001101635 for example, dial peer 402 is selected instead of 404.  We have tried adding $ to the end of both peers, but behavior is the same.  It looks like the shorter pattern is matched, and selected, even though there is a longer and more specific peer available.  Is this expected behavior?  Suposedly, longest prefix is chosen, but that doesn't seem to be happening. 

I think I can work around by replacing peer 402 with a pair of peers, with dest patterns

98[1-9]......

and

98.[1-9].....

This should cause 9800 to fail the match, while allowing 9801 and 9810, but is there a a simpler way?  I believe I am correct in saying that the order of the peers is irrelevant, so I can't fix it by putting peer 404 ahead of 402 in config?

Any insights would be appreciated.  Dial peer selection still seems to murky despite all the CCO doc and discussions. 

Thanks

I have this problem too.
0 votes
Correct Answer by Udit Mehrotra about 2 years 2 months ago

Make the following change -

dial-peer voice 402 pots                 
corlist outgoing CORList-Mobile
description Outbound-SNPR-Mobile
translation-profile outgoing callerid
destination-pattern 98.......T

you see this behavior because CME does dial-peer match digit by digit, and as soon as a dial-peer is matched with an exact match, call is routed using that dial-peer

Adding T, makes the dial peer wait for more digits and introduces inter digit timeout. If you see delay in 9 digit calls, try reducing the inter digit timeout.

--

Udit

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
Chris Deren Wed, 02/01/2012 - 12:54

Delete dial-peer 402, and re-add it, sometimes the order of them matters even though it is not suppose to. Alos, I am assuming both cor-lists are accessible, right?

Chris

mflanigan021 Wed, 02/01/2012 - 13:09

Chris,

Thanks.  If memory serves, the customer did try re-ordering the peers, but I'll ask him to try again.  The cor-lists have been

checked, and should be OK

Correct Answer
Udit Mehrotra Wed, 02/01/2012 - 13:11

Make the following change -

dial-peer voice 402 pots                 
corlist outgoing CORList-Mobile
description Outbound-SNPR-Mobile
translation-profile outgoing callerid
destination-pattern 98.......T

you see this behavior because CME does dial-peer match digit by digit, and as soon as a dial-peer is matched with an exact match, call is routed using that dial-peer

Adding T, makes the dial peer wait for more digits and introduces inter digit timeout. If you see delay in 9 digit calls, try reducing the inter digit timeout.

--

Udit

mflanigan021 Fri, 02/17/2012 - 08:06

The issue was resolved - the customer ended up applying the dial-peer alterations I suggested, but I don;t knw if he tried any of the other suggestions.  Thanks to all for help.

Actions

Login or Register to take actions

This Discussion

Posted February 1, 2012 at 12:33 PM
Stats:
Replies:5 Avg. Rating:5
Views:397 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 21,036
2 15,047
3 10,325
4 8,014
5 4,856
Rank Username Points
116
105
103
62
61