From: Barman, Partha (PBarman@necbns.com)
Date: Fri Jan 02 2004 - 05:34:46 GMT-3
dial-peer cor custom
name NewYork
name All
!
!
dial-peer cor list NewYork
member NewYork
!
dial-peer cor list All
member All
dial-peer voice 212 pots
corlist outgoing NewYork
destination-pattern 91212.......
port 1/0/0
forward-digits 10
!
dial-peer voice 91 pots
destination-pattern 91.T
port 1/0/0
ephone-dn 2
number 7002
description Phone7002
name Phone 7002
call-forward busy 7004
call-forward noan 7004 timeout 10
transfer-mode blind
!
!
ephone-dn 3
number 7003
name SharedLine 7003
cor incoming All
hold-alert 15 shared
I have the above config. What I want is 7003 should be restricted from calling 91212.......; but with the above config, both 7002 and 7003 are able to call 912125251000.
If I remove the dial-peer 91, then 7003 is not able to call 912125251000; and 7002 is able to call which desired.
In the first case, it looks like when 7003 dials 912125251000, the router sees that it cannot use the dial-peer 212 because of COR restriction and uses dial-peer 91 to make the outbound call.
My question is, if a call is restricted by COR config, does it hunt for other dial-peers to match and let the call progress? This is what seems here!
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:35 GMT-3