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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Bronze

Dial-peer matching

I have the following dial peer configuration, I thought dial peers get the best longest match then by preferene (lowest being first choice). Here is my debug and dial-peers thanks.

I am expeting dial peer 4000 to be matched first.

Feb 17 09:36:29.081 DST: Inside dpMatchCore:

Feb 17 09:36:29.081 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 09:36:29.081 DST: Inside dpMatchCore:

Feb 17 09:36:29.081 DST: destination pattn: 2605 expanded string: 2605

Feb 17 09:36:29.081 DST: Inside dpMatchCore:

Feb 17 09:36:29.081 DST: destination pattn: 2605 expanded string: 2605

Feb 17 09:36:29.081 DST: MatchNextPeer: Peer 2000 matched

Feb 17 09:36:29.085 DST: MatchNextPeer: Peer 2001 matched

Feb 17 09:36:29.085 DST: Inside dpMatchCore:

Feb 17 09:36:29.085 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 09:36:29.085 DST: Inside dpMatchCore:

Feb 17 09:36:29.085 DST: destination pattn: 2605 expanded string: 2605

Feb 17 09:36:29.085 DST: Inside dpMatchCore:

Feb 17 09:36:29.085 DST: destination pattn: 2605 expanded string: 2605

Feb 17 09:36:29.089 DST: MatchNextPeer: Peer 2000 matched

Feb 17 09:36:29.089 DST: MatchNextPeer: Peer 2001 matched

Feb 17 09:36:29.093 DST: Inside dpMatchPeersMoreArg

Feb 17 09:36:29.093 DST: dpMatchPeersMoreArg: Match Dest. pattern; called (093461409)

Feb 17 09:36:29.093 DST: Inside dpMatchCore:

Feb 17 09:36:29.093 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 09:36:29.097 DST: MatchNextPeer: Peer 1 matched

Feb 17 09:36:29.097 DST: MatchNextPeer: Peer 4000 matched

Feb 17 09:36:29.097 DST: dpMatchPeersMoreArg: Result=0 after MATCH_ORIGINATE u all

dial-peer voice 1 pots

preference 3

destination-pattern 0T

progress_ind alert enable 8

direct-inward-dial

port 1/0:15

!

dial-peer voice 4000 voip

preference 1

destination-pattern 093461409

session target ipv4:10.200.200.1

dial-peer voice 2000 voip

preference 1

destination-pattern 2...

progress_ind setup enable 3

voice-class codec 729

voice-class h323 10

session target ipv4:10.201.200.1

dtmf-relay h245-alphanumeric

no vad

!

dial-peer voice 2001 voip

preference 2

destination-pattern 2...

progress_ind setup enable 3

voice-class codec 729

voice-class h323 10

session target ipv4:10.200.200.1

dtmf-relay h245-alphanumeric

no vad

4 REPLIES
Silver

Re: Dial-peer matching

double post - see below - oops

Silver

Re: Dial-peer matching

Well, I would expect that too, based on this snip from the 'understanding dial peer matching' doc:

Now, assume the dial-string from an inbound POTS interface is "81690".

dial-peer voice 3 voip

destination-pattern 8T

session target ipv4:172.22.10.1

!

dial-peer voice 4 voip

destination-pattern 81690T

session target ipv4:172.22.10.1

In this case, the longest-prefix rule applies, and dial peer 4 is matched for the outbound call leg.

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#topic10

On thing that would be worth trying is replacing your last digit on your more specific match with a T, in case that is somehow coming into play. The other thing is, I remember reading in some very old doc that if there is a pots peer and a voip peer, the pots always wins, but I thought that was equal matches. The preference is used for equal matches, and yours are not equal, so that is not weighed here.

Mary Beth

Bronze

Re: Dial-peer matching

Hi,

It is using POTS before voip.

I added the following dial-peer

dial-peer voice 5000 pots

preference 8

destination-pattern 0T

progress_ind alert enable 8

direct-inward-dial

port 1/0:15

get the result:

Feb 17 15:19:52.824 DST: Inside dpMatchCore:

Feb 17 15:19:52.824 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 15:19:52.824 DST: Inside dpMatchCore:

Feb 17 15:19:52.824 DST: destination pattn: 2605 expanded string: 2605

Feb 17 15:19:52.824 DST: Inside dpMatchCore:

Feb 17 15:19:52.824 DST: destination pattn: 2605 expanded string: 2605

Feb 17 15:19:52.824 DST: MatchNextPeer: Peer 2000 matched

Feb 17 15:19:52.828 DST: MatchNextPeer: Peer 2001 matched

Feb 17 15:19:52.828 DST: Inside dpMatchCore:

Feb 17 15:19:52.828 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 15:19:52.828 DST: Inside dpMatchCore:

Feb 17 15:19:52.828 DST: destination pattn: 2605 expanded string: 2605

Feb 17 15:19:52.828 DST: Inside dpMatchCore:

Feb 17 15:19:52.832 DST: destination pattn: 2605 expanded string: 2605

Feb 17 15:19:52.832 DST: MatchNextPeer: Peer 2000 matched

Feb 17 15:19:52.832 DST: MatchNextPeer: Peer 2001 matched

Feb 17 15:19:52.836 DST: Inside dpMatchPeersMoreArg

Feb 17 15:19:52.836 DST: dpMatchPeersMoreArg: Match Dest. pattern; called (093461409)

Feb 17 15:19:52.836 DST: Inside dpMatchCore:

Feb 17 15:19:52.836 DST: destination pattn: 093461409 expanded string: 093461409

Feb 17 15:19:52.836 DST: MatchNextPeer: Peer 1 matched

Feb 17 15:19:52.840 DST: MatchNextPeer: Peer 5000 matched

Feb 17 15:19:52.840 DST: MatchNextPeer: Peer 4000 matched

Feb 17 15:19:52.840 DST: dpMatchPeersMoreArg: Result=0 after MATCH_ORIGINATE

i thought it may be using the peer number as well so added one higher then the specific match just to see if it displays the order..Even added the T onto the 4000 dial peer destination pattern, makes no difference.

Silver

Re: Dial-peer matching

What is your platform and sw version? I can't imagine that this is still supposed to work like this, even if it was a reasonable idea with equal match destinations, it is certainly a bad idea when you have a more specific match pointing to a voip peer! I think you need a TAC case to have them fix or explain this - and then tell us what they say.

Mary Beth

132
Views
0
Helpful
4
Replies