<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=tednugent69@yahoo.com href="mailto:tednugent69@yahoo.com">Ted
Nugent</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, February 11, 2007 9:34
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] dial-peers and
more specific vs less specific matching</DIV>
<DIV><BR></DIV>Your 919005655555 DP is assigned to your<BR>call-toll-fraud COR
List so you'd need to assigned<BR>that cor list to the DN... You mentioned it
the other<BR>way around before??<BR><BR>call-manager-fallback<BR> cor
incoming call-toll-fraud 1 3000<BR><BR><BR><BR><BR><BR>--- Lelio Fulgenzi
<<A href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>>
wrote:<BR><BR>> Well, I'm basically looking for an easy way to<BR>>
blocking calling to specific numbers, for example,<BR>> 900 numbers. But
not only do I want to block them, I<BR>> want to be able to assign them to
another CoR so<BR>> that while they are blocked for the most people,
I<BR>> can assign the CoR to others. It has to be a<BR>> scalable
solution though, since we may want to<BR>> prevent access to other specific
area codes but<BR>> assign them to others.<BR>> <BR>>
<BR>> ----- Original Message ----- <BR>> From:
Ted Nugent <BR>> To: Lelio Fulgenzi ; <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<BR>> Sent: Sunday, February 11, 2007 11:12
AM<BR>> Subject: Re: [cisco-voip] dial-peers and more<BR>>
specific vs less specific matching<BR>> <BR>> <BR>> That
is the expected behavior, I try to think of<BR>> it as<BR>>
PT/CSS, the call_long_dist COR does not have<BR>>
visibilty<BR>> to the 976001901 DP because its in a
different<BR>> COR, it<BR>> can only see the DP in its COR
list. I'm not 100%<BR>> certain what your trying to accomplish
however if<BR>> you<BR>> do not assign COR to a dailpeer it
will be visible<BR>> by<BR>> all COR lists, sorta like
putting it in the null<BR>> PT.<BR>> <BR>> <BR>>
<BR>> --- Lelio Fulgenzi <<A
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>> wrote:<BR>>
<BR>> > Trying to get my head around these
dial-peers,<BR>> and<BR>> > just when I thought I knew
what I was doing....<BR>> > <BR>> > I
created a few dial-peers, some more specific<BR>> than<BR>>
> others, in the hopes that I could selectively<BR>>
route<BR>> > calls based on the CoR list assigned. We
do<BR>> > something similar in CallManager and I was<BR>>
hoping to<BR>> > emulate things as much as
possible.<BR>> > <BR>> > A simple example
(pardon spelling errors):<BR>> > <BR>> >
dial-peer cor custom<BR>> > name
long_dist<BR>> > name
toll_fraud<BR>> > <BR>> > dial-peer cor
list call_long_dist<BR>> > member
long_dist<BR>> > <BR>> > dial-peer cor
list call_toll_fraud<BR>> > member
long_dist<BR>> > member
toll_fraud<BR>> > <BR>> > dial-peer voice
91901 pots<BR>> > corlist outgoing
call_long_dist<BR>> > destination-pattern
91..........<BR>> > port 3/0:23<BR>>
> forward-digits 11<BR>> > <BR>>
> dial-peer voice 976001901 pots<BR>> > corlist
outgoing call_toll_fraud<BR>> >
huntstop<BR>> > destination-pattern
919005655555<BR>> > port 3/0:23<BR>>
> forward-digits 11<BR>> > <BR>>
> phones with an incoming dialpeer of<BR>>
call_long_dist<BR>> > can still call this 1900 number,
because it's<BR>> > matching the 91..........
dial-peer.<BR>> > <BR>> > is that the way
things are supposed to work?<BR>> even if<BR>> > there is
a more specific dial-peer (that doesn't<BR>> > match it's
cor list), it will use a less<BR>> specific<BR>> >
dial-peer that does match?<BR>> > <BR>> >
that seems odd to me.<BR>> > <BR>>
><BR>>
<BR>><BR>--------------------------------------------------------------------------------<BR>>
> Lelio Fulgenzi, B.A.<BR>> > Senior Analyst (CCS) *
University of Guelph *<BR>> > Guelph, Ontario N1G
2W1<BR>> > (519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>> ><BR>>
<BR>><BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>>
> <BR>> > ...there's no such thing as a bad
timbit...<BR>> > ><BR>>
_______________________________________________<BR>> >
cisco-voip mailing list<BR>> > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
><BR>> <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> <BR>> <BR>> <BR>> <BR>> <BR>>
<BR>><BR>____________________________________________________________________________________<BR>>
Now that's room service! Choose from over 150,000<BR>>
hotels<BR>> in 45,000 destinations on Yahoo! Travel to
find<BR>> your fit.<BR>> <A
href="http://farechase.yahoo.com/promo-generic-14795097">http://farechase.yahoo.com/promo-generic-14795097</A><BR>>
> _______________________________________________<BR>> cisco-voip
mailing list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
<A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
<BR><BR><BR><BR> <BR>____________________________________________________________________________________<BR>Have
a burning question? <BR>Go to <A
href="http://www.Answers.yahoo.com">www.Answers.yahoo.com</A> and get answers
from real people who know.<BR></BLOCKQUOTE></BODY></HTML>