[cisco-voip] dial-peers and more specific vs less specific matching

[Lelio Fulgenzi]

Trying to get my head around these dial-peers, and just when I thought I knew what I was doing....

I created a few dial-peers, some more specific than others, in the hopes that I could selectively route calls based on the CoR list assigned. We do something similar in CallManager and I was hoping to emulate things as much as possible.

A simple example (pardon spelling errors):

dial-peer cor custom
    name long_dist
    name toll_fraud

dial-peer cor list call_long_dist
    member long_dist

dial-peer cor list call_toll_fraud
    member long_dist
    member toll_fraud

dial-peer voice 91901 pots
 corlist outgoing call_long_dist
 destination-pattern 91..........
 port 3/0:23
 forward-digits 11

dial-peer voice 976001901 pots
 corlist outgoing call_toll_fraud
 huntstop
 destination-pattern 919005655555
 port 3/0:23
 forward-digits 11

phones with an incoming dialpeer of call_long_dist can still call this 1900 number, because it's matching the 91.......... dial-peer.

is that the way things are supposed to work? even if there is a more specific dial-peer (that doesn't match it's cor list), it will use a less specific dial-peer that does match?

that seems odd to me.

--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
...there's no such thing as a bad timbit...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070209/833c9807/attachment.html