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

Lelio Fulgenzi lelio at uoguelph.ca
Sun Feb 11 22:48:16 EST 2007


Ok then, so basically, I create a dial-peer that allows all long distance dialing, and then create dial-peers that block the area codes I want to block and then make sure that those dial-peers match the same CoR as the phones I want to prevent dialing those area codes. For everyone else, I make sure their CoR is a subset of the dial-peer cor so they do not match and therefor by pass the blocking dial-peer.


  ----- Original Message ----- 
  From: Ted Nugent 
  To: Lelio Fulgenzi ; cisco-voip at puck.nether.net 
  Sent: Sunday, February 11, 2007 10:17 PM
  Subject: Re: [cisco-voip] dial-peers and more specific vs less specific matching


  Ahhh... ok... sorry been a long weekend.. :-)
  Well in this case I would probably use voice
  translation rules. 

  voice translation-rule 5500
   rule 1 reject /919005655555/
  !
  voice translation-profile block
   translate called 5500
  !
  dial-peer voice 976001901 pots
   corlist outgoing call-toll-fraud
   translation-profile outgoing block
   huntstop
   destination-pattern 919005655555



   
  --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

  > But I still don't see how to block them for the
  > other extensions.....I would thinking blocking
  > specific outbounding area codes is a regular thing.
  > 
  >   ----- Original Message ----- 
  >   From: Ted Nugent 
  >   To: Lelio Fulgenzi ; cisco-voip at puck.nether.net 
  >   Sent: Sunday, February 11, 2007 9:34 PM
  >   Subject: Re: [cisco-voip] dial-peers and more
  > specific vs less specific matching
  > 
  > 
  >   Your 919005655555 DP is assigned to your
  >   call-toll-fraud COR List so you'd need to assigned
  >   that cor list to the DN... You mentioned it the
  > other
  >   way around before??
  > 
  >   call-manager-fallback
  >     cor incoming call-toll-fraud 1 3000
  > 
  > 
  > 
  > 
  > 
  >   --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
  > 
  >   > Well, I'm basically looking for an easy way to
  >   > blocking calling to specific numbers, for
  > example,
  >   > 900 numbers. But not only do I want to block
  > them, I
  >   > want to be able to assign them to another CoR so
  >   > that while they are blocked for the most people,
  > I
  >   > can assign the CoR to others. It has to be a
  >   > scalable solution though, since we may want to
  >   > prevent access to other specific area codes but
  >   > assign them to others.
  >   > 
  >   > 
  >   >   ----- Original Message ----- 
  >   >   From: Ted Nugent 
  >   >   To: Lelio Fulgenzi ;
  > cisco-voip at puck.nether.net 
  >   >   Sent: Sunday, February 11, 2007 11:12 AM
  >   >   Subject: Re: [cisco-voip] dial-peers and more
  >   > specific vs less specific matching
  >   > 
  >   > 
  >   >   That is the expected behavior, I try to think
  > of
  >   > it as
  >   >   PT/CSS, the call_long_dist COR does not have
  >   > visibilty
  >   >   to the 976001901 DP because its in a different
  >   > COR, it
  >   >   can only see the DP in its COR list. I'm not
  > 100%
  >   >   certain what your trying to accomplish however
  > if
  >   > you
  >   >   do not assign COR to a dailpeer it will be
  > visible
  >   > by
  >   >   all COR lists, sorta like putting it in the
  > null
  >   > PT.
  >   > 
  >   > 
  >   > 
  >   >   --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
  >   > 
  >   >   > 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...
  >   >   > >
  >   > _______________________________________________
  >   >   > cisco-voip mailing list
  >   >   > cisco-voip at puck.nether.net
  >   >   >
  >   >
  > https://puck.nether.net/mailman/listinfo/cisco-voip
  >   >   > 
  >   > 
  >   > 
  >   > 
  >   >    
  >   >  
  >   >
  >  
  >
  ____________________________________________________________________________________
  >   >   Now that's room service!  Choose from over
  > 150,000
  >   > hotels
  >   >   in 45,000 destinations on Yahoo! Travel to
  > find
  >   > your fit.
  >   >  
  > http://farechase.yahoo.com/promo-generic-14795097
  >   > >
  > _______________________________________________
  >   > cisco-voip mailing list
  >   > cisco-voip at puck.nether.net
  >   >
  > https://puck.nether.net/mailman/listinfo/cisco-voip
  >   > 
  > 
  > 
  > 
  >    
  >  
  >
  ____________________________________________________________________________________
  >   Have a burning question?  
  >   Go to www.Answers.yahoo.com and get answers from
  > real people who know.
  > 



   
  ____________________________________________________________________________________
  Sucker-punch spam with award-winning protection. 
  Try the free Yahoo! Mail Beta.
  http://advision.webevents.yahoo.com/mailbeta/features_spam.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070211/6ffa6df8/attachment-0001.html 


More information about the cisco-voip mailing list