Wesley,
Number one will match any 4 digit string beginning with 2 even 2200.
But #2 is preferred for any 5 digit string beginning with 22, like
22000. By default IOS will pick the destination pattern that matches the
greatest number of the dialed digits.
Of course you could always use the command:
dial-peer hunt 6
Then the router will chose dial peers at random regardless of the
destination pattern. :)
Chris
Wesley Lim wrote:
Interesting.
How I would tackle this.
Lets assume we have 2 dialpeers as of the following:
1. 2...
2. 22...
No matter what, both dialpeers are overlapping. Hence for the dialpeer
with 2... , i would put a timeout at the end of the destination
pattern - for eg 2...T
On 3/31/09, CCIE OSL <ccie...@gmail.com> wrote:
I think you need new dial-peer with
diall-peer voice 2400 voip
destination-p 2[23]...
to match 22... and 23...
and may need to create GK prefix match this as well. 23*, 22*
and setup call forward all,
On CCM, need RP for 24xxx and point to GK, may also need GK prefix and
point to CME.
24*
I do not think you can use dial-peer 2300.
Is this a requirement that you must use one dial-peer?
If so, you can use voice translation profile to strip "2", but I do not
think you can make it go directly to VM, it will ring the ext 2001 first
Unless you setup ext 2001 to call forward all directly to VM, Which I do
not think you want to do.
voice translation-rule 1
rule 1 /^2\(2...\)/ /\1/
rule 2 /^2\(3...\)/ /\1/
/Jin Jung...
Duy Nguyen wrote:
How would I achieve this?
User at Site C should press 24XXX, then it will forward to user's
voice mailbox greeting.
E.g. when user dial 24001, then it will be forwarding directly to 4001
VM and leave a message. This call routing should work over the WAN also.
My solution:
ephone-dn 20
number 24...
call-forward all 4111
Problem is:
dial-peer voice 2300 voip
destination-pattern [23]...
session target ras
tech-prefix 1
dtmf-relay h245-alphanumeric
ip qos dscp cs3 signaling
no vad
!
Another issue, it is also asking for the same on CCM side when user
dials 22XXX should go to VM directly and should also work over the
WAN. From CME could not dial 22XXX since it keeps hitting Dial-peer
voice 2300 voip.
If I change the
dial-peer voice 2300
destination-pattern [23][0128]..
Still won't achieve calling to Main site phone's VM.
