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

dial-peer help - Wrong dial-peer matching.

I have a problem where a wrong dialpeer is getting matched to a number I am trying to dial and making the call fail.

I am trying to dial a number "9141123456"

9 is to "dial out"

141 is a prefix to make the call appear from "unknown"

123456 is the number i am trying to call.

Here are the three dial peers that are getting matched.

dial-peer voice 17 pots

description ** 141 - Hide CLI **

destination-pattern 9141T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

port 0/0/0:15

prefix 141

dial-peer voice 12 pots

description ** Unrestricted **

destination-pattern 9T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

port 0/0/0:15

dial-peer voice 9 pots

description ** Local Numbers **

destination-pattern 9[1-9].....

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

port 0/0/0:15

forward-digits 6

Part of my "debug voice dialpeer all" is as follows:

Jan 10 16:37:50.023: //-1/3463D35A8655/DPM/dpMatchCore:

Dial String=9141123, Expanded String=9141123, Calling Number=

Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

Jan 10 16:37:50.023: //-1/3463D35A8655/DPM/MatchNextPeer:

Result=Success(0); Outgoing Dial-peer=9 Is Matched

Jan 10 16:37:50.023: //-1/3463D35A8655/DPM/MatchNextPeer:

Result=Success(0); Outgoing Dial-peer=12 Is Matched

Jan 10 16:37:50.023: //-1/3463D35A8655/DPM/MatchNextPeer:

Result=Success(0); Outgoing Dial-peer=17 Is Matched

Jan 10 16:37:50.027: //-1/3463D35A8655/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

Jan 10 16:37:50.027: //-1/3463D35A8655/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=17

2: Dial-peer Tag=9

3: Dial-peer Tag=12

As the system is only really letting me dial 9141123 before call fails it appears that the call is getting caught by dial-peer 9, which then isnt expecting more numbers so it attempts the call with the half number and then fails.

My thought was that the more exact the dialed number was to a dial-peer's destination pattern the more likely it was to use that dial-peer. So because I dialed 9141 it should match dial-peer 17 rather than dial-peer 9.

Is this not the case? Is there a way I can make it use dial-peer 17 (or 12) another way? maybe with the "preference" command?

Many thanks.

David.

3 REPLIES
Bronze

Re: dial-peer help - Wrong dial-peer matching.

Hi,

Outbound IOS dial-peers are matched according to the 'first match' and not the 'longest match' rule (if digits are presented one by one).

Preference will only take place when you have identical destination-pattern in two dial-peers.

The way it should be solved is by differentiating the patterns, usually dialed numbers would not start with 1, not sure about the scenario you are describing but can you change the destination-pattern of dial-peer 9 to be 9[2-9]..... ?

HTH, Avner.

New Member

Re: dial-peer help - Wrong dial-peer matching.

To isolate the problem, I'd take out dial peers 9 and 12 and see what the behavior is then. Is the problem with dial peer 17 or the problem created when the others are added.

New Member

Re: dial-peer help - Wrong dial-peer matching.

I have changed the matching dial-peer to:

dial-peer voice 9 pots

description ** Local Numbers **

destination-pattern 9[1-9].....T

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

port 0/0/0:15

forward-digits 6

Having added the "T" on the end of the destination-pattern. This has solved my problem.

448
Views
6
Helpful
3
Replies
CreatePlease to create content