Duy,
Remember, the digit analyzer in IOS will always match the peer with the
most matching digits first.
So for the first issue of forwarding to VM. The config you have is
exactly right. All of the extensions at that site are 4001 - 4003. So
when you dial 24001, it will always match that ephone first and go where
you want tit to go.
The same goes with the WAN dial peer (2300). The extension rages at the
other locations are 2001-4 and 3001-4 respectively. The only time you
would get into hot water is if you had an extension at HQ that was 2400.
Then you would have a problem.
For the third requirement the answer is simple make a peer with the
destination patten of: 2[23]...
Chris
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.
