<!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 size=2>Thanks Ted....that's the idea I got after reading your post.
Glad to see I'm on the right track.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>...there's no such thing as a bad timbit...<BR></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 11:16
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>Yep, I personally like to make things a bit more<BR>granular to
give it more of a PT/CSS feel, works<BR>better for me. I'd probably go this
route, might have<BR>fat fingered something but I think you'll get the
idea<BR><BR>voice translation-rule 900<BR> rule 1 reject
/^91900/<BR>!<BR>voice translation-profile block<BR> translate called
900<BR>!<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 toll-fraud<BR>!<BR>dial-peer
cor list Unrestricted-Users<BR> member
long-dist<BR>!<BR>dial-peer cor list Restricted-Users<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[2-9]..[2-9]......<BR> port
3/0:23<BR> forward-digits 11<BR><BR>dial-peer voice 1900
pots<BR> corlist outgoing call-toll-fraud<BR> translation-profile
outgoing block<BR> huntstop<BR> destination-pattern
91900.......<BR><BR> call-manager-fallback<BR> cor incoming
Restricted-Users 1 3000 <-900s blocked<BR> cor incoming
Unrestricted-Users 1 3000 <-900s<BR>allowed<BR><BR><BR><BR><BR>--- Lelio
Fulgenzi <<A href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>>
wrote:<BR><BR>> Ok then, so basically, I create a dial-peer that<BR>>
allows all long distance dialing, and then create<BR>> dial-peers that
block the area codes I want to block<BR>> and then make sure that those
dial-peers match the<BR>> same CoR as the phones I want to prevent
dialing<BR>> those area codes. For everyone else, I make sure<BR>> their
CoR is a subset of the dial-peer cor so they<BR>> do not match and therefor
by pass the blocking<BR>> dial-peer.<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 10:17
PM<BR>> Subject: Re: [cisco-voip] dial-peers and more<BR>>
specific vs less specific matching<BR>> <BR>> <BR>>
Ahhh... ok... sorry been a long weekend.. :-)<BR>> Well in this
case I would probably use voice<BR>> translation rules.
<BR>> <BR>> voice translation-rule
5500<BR>> rule 1 reject
/919005655555/<BR>> !<BR>> voice
translation-profile block<BR>> translate called
5500<BR>> !<BR>> dial-peer voice 976001901
pots<BR>> corlist outgoing
call-toll-fraud<BR>> translation-profile outgoing
block<BR>> huntstop<BR>>
destination-pattern 919005655555<BR>> <BR>> <BR>>
<BR>> <BR>> --- Lelio Fulgenzi <<A
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>> wrote:<BR>>
<BR>> > But I still don't see how to block them for
the<BR>> > other extensions.....I would thinking
blocking<BR>> > specific outbounding area codes is a
regular<BR>> thing.<BR>> > <BR>>
> ----- Original Message ----- <BR>>
> From: Ted Nugent <BR>> > To:
Lelio Fulgenzi ;<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<BR>> > Sent: Sunday, February 11, 2007 9:34
PM<BR>> > Subject: Re: [cisco-voip] dial-peers
and more<BR>> > specific vs less specific
matching<BR>> > <BR>> >
<BR>> > Your 919005655555 DP is assigned to
your<BR>> > call-toll-fraud COR List so you'd
need to<BR>> assigned<BR>> > that cor list to
the DN... You mentioned it<BR>> the<BR>> >
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<BR>> to<BR>>
> > blocking calling to specific numbers,
for<BR>> > example,<BR>> >
> 900 numbers. But not only do I want to block<BR>> >
them, I<BR>> > > want to be able to assign
them to another<BR>> CoR so<BR>> > > that
while they are blocked for the most<BR>> people,<BR>> >
I<BR>> > > can assign the CoR to others. It
has to be a<BR>> > > scalable solution
though, since we may want<BR>> to<BR>> > >
prevent access to other specific area codes<BR>> but<BR>>
> > assign them to others.<BR>>
> > <BR>> > >
<BR>> > > ----- Original Message
----- <BR>> > > From: Ted Nugent
<BR>> > > To: Lelio Fulgenzi
;<BR>> > <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<BR>> more<BR>>
> > specific vs less specific matching<BR>>
> > <BR>> > >
<BR>> > > That is the expected
behavior, I try to<BR>> think<BR>> >
of<BR>> > > it as<BR>>
> > PT/CSS, the call_long_dist COR does
not<BR>> have<BR>> > >
visibilty<BR>> > > to the
976001901 DP because its in a<BR>> different<BR>>
> > COR, it<BR>> >
> can only see the DP in its COR list. I'm<BR>>
not<BR>> > 100%<BR>> >
> certain what your trying to accomplish<BR>>
however<BR>> > if<BR>> > >
you<BR>> > > do not assign COR to
a dailpeer it will be<BR>> > visible<BR>>
> > by<BR>> > >
all COR lists, sorta like putting it in<BR>> the<BR>> >
null<BR>> > > PT.<BR>>
> > <BR>> > >
<BR>> > > <BR>>
> > --- Lelio Fulgenzi <<A
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>><BR>>
wrote:<BR>> > > <BR>>
> > > Trying to get my head around
these<BR>> > dial-peers,<BR>>
> > and<BR>> >
> > just when I thought I knew what I
was<BR>> > doing....<BR>> >
> > <BR>> > >
> I created a few dial-peers, some more<BR>> >
specific<BR>> > > than<BR>>
> > > others, in the hopes that I
could<BR>> > selectively<BR>>
> > route<BR>> >
> > calls based on the CoR list assigned. We<BR>>
do<BR>> > > > something
similar in CallManager and I<BR>> was<BR>> >
> hoping to<BR>> > > >
emulate things as much as possible.<BR>> >
> > <BR>> > >
> A simple example (pardon spelling<BR>> 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<BR>> >
it's<BR>> > > > matching the
91.......... dial-peer.<BR>> > >
> <BR>> > > > is that the
way things are supposed to<BR>> work?<BR>> >
> even if<BR>> > > > there
is a more specific dial-peer (that<BR>> >
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>>
><BR>>
<BR>><BR>--------------------------------------------------------------------------------<BR>>
> > > Lelio Fulgenzi, B.A.<BR>> <BR>===
message truncated
===><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>It's
here! Your new message! <BR>Get new email alerts with the free Yahoo!
Toolbar.<BR><A
href="http://tools.search.yahoo.com/toolbar/features/mail/">http://tools.search.yahoo.com/toolbar/features/mail/</A><BR></BLOCKQUOTE></BODY></HTML>