02-05-2011 06:18 AM - edited 03-16-2019 03:17 AM
Hello all,
the question is following:
I have two dial-peers on CCME with
a) destination-pattern 9.......... (10 digits without "9")
b) destination-pattern 900............ (12 digits witout "9")
how to configure CCME that it will select dial-peer (b) when dialed something like that: 90012345678912 (currently CCME select more shorter destination-pattern (a))
02-05-2011 06:52 AM
Hi
It should choose 900............ by default, Since this is the closest match for the dialled number 90012345678912
But Make Sure the Dial-peer hunt 0 should be there by default.
dial-peer hunt ?
<0-7> Dial-peer hunting choices, listed in hunting order within each choice:
0 – Longest match in phone number, explicit preference, random selection. Default
1 – Longest match in phone number, explicit preference, least recent use.
2 – Explicit preference, longest match in phone number, random selection.
3 – Explicit preference, longest match in phone number, least recent use.
4 – Least recent use, longest match in phone number, explicit preference.
5 – Least recent use, explicit preference, longest match in phone number.
6 – Random selection.
7 – Least recent use.
Say if you have dial-peer hunt set to 2 or 3 and if you have preference set for both the Dial-Peers
dial-peer voice 100 pots
destination pattern 9..........
port 1/3
preference 1
dial-peer voice 200 pots
destination pattern 900............
port 1/5
preference 2
Now the dialpeer 100 will match if anyone dials 90012345678912
Please find the link below for Dial-peer Matching
http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/dial_peer/dp_confg.html
02-05-2011 08:35 AM
Don't think that will work for SCCP Phones registered on the CME. When they dial digit-by-digit it will match the shorter dial-peer.
For eg.
dial-peer voice 224 voip
destination-pattern 9...
session target ipv4:14.160.122.100
dial-peer voice 225 voip
destination-pattern 9.....
session target ipv4:14.160.122.100
03841: Feb 5 16:32:30.706: //78918/52CD621AB9D3/CCAPI/cc_api_display_ie_subfields:
ccCallSetupRequest:
cisco-username=
----- ccCallInfo IE subfields -----
cisco-ani=3003
cisco-anitype=0
cisco-aniplan=0
cisco-anipi=0
cisco-anisi=0
dest=9000
cisco-desttype=0
cisco-destplan=0
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-rdntype=0
cisco-rdnplan=0
cisco-rdnpi=0
cisco-rdnsi=0
cisco-redirectreason=0 fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0
As soon as I dial the fourth digit...
103849: Feb 5 16:32:30.710: //78920/52CD621AB9D3/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1
103850: Feb 5 16:32:30.710: //78920/52CD621AB9D3/CCAPI/ccCallSetContext:
Context=0x45AC6598
103851: Feb 5 16:32:30.710: //78918/52CD621AB9D3/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=224
103852: Feb 5 16:32:30.722: //78920/52CD621AB9D3/CC
It might work for ENBLOC dialling. but not for Digit-by-digit dial. In digit-by-digit dialing, as soon as it finds a match it dials out.!
I think ...
you should use.
dial-peer voice 100 pots
destination pattern 9..........T
port 1/3
dial-peer voice 200 pots
destination pattern 900............T
port 1/5
You can just instruct users to dial # to get rid of the interdigit timeout.!
HTH
PS:Rate useful posts!
02-05-2011 08:37 AM
Or use different access codes for these.!
02-05-2011 08:55 AM
Hi John,
I got it, I agree with your solution, Thanks for the clarification
dial-peer voice 100 pots
destination pattern 9..........T
port 1/3
dial-peer voice 200 pots
destination pattern 900............T
port 1/5
02-05-2011 08:59 AM
I am always in the "lab-it-up" Mode . Maybe its a occupational HAZARD
HTH
PS:Rate useful posts
02-06-2011 07:45 AM
thanks!
i've created universal dial-peer with dest-pattern 9T (because for ex in Germany is a variable-number numbering plan) and strip "9" via trans rule:
rule 1 /^9\(.*$\)/ /\1/
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide