[cisco-voip] dial-peers and more specific vs lessspecificmatching
Lelio Fulgenzi
lelio at uoguelph.ca
Mon Feb 12 13:40:14 EST 2007
I can give them a "this call has been blocked" message somehow? For outbound dialpeers?
--------------------------------------------------------------------------------
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...
----- Original Message -----
From: Paul Choi
To: cisco-voip at puck.nether.net
Sent: Monday, February 12, 2007 1:28 PM
Subject: Re: [cisco-voip] dial-peers and more specific vs lessspecificmatching
That would also work if you just want to prevent those
calls from going through as opposed to giving them a
'this call has been blocked' message instead.
Cheers,
Paul
--- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> Well, that would explain it.
>
> I'm not averse to using CoR, but I just haven't been
> able to figure out how I can let people dial long
> distance, but selectively block calling some area
> codes such as 900 or other high risk area codes like
> 684.
>
> I don't want to have to create some sort of crazy
> regexp that allows everything but what I want to
> block, that just does not seem scalable to me.
>
> I have tested my translations and found that this
> works:
>
> voice translation-rule 684
> rule 1 /^91684......./ //
>
> or at least I get error tone. ;)
>
>
--------------------------------------------------------------------------------
> 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...
>
> ----- Original Message -----
> From: Paul Choi
> To: cisco-voip at puck.nether.net
> Sent: Monday, February 12, 2007 1:16 PM
> Subject: Re: [cisco-voip] dial-peers and more
> specific vs less specificmatching
>
>
> Lelio,
>
> After looking through my GWGK textbook, it states
> that
> voice translation rules can be used to block
> *incoming* calls. It does not say anything about
> being
> able to block outgoing calls. I highly suggest you
> use
> CoR instead of voice translation rules in this
> case.
>
> Cheers,
> Paul
> --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> > Ok, so I tried things out, and it seemed it was
> > still hitting the longdistance dial peer (debug
> was
> > showing a match of two dial-peers), so to
> simplify
> > things, I removed the long distance dial-peer
> > (91..........) altogether and confirmed I
> couldn't
> > dial long distance, but when I tried dialing a
> > number that matched the dialpeer that should
> have
> > been blocked, the call went through! ayieeeeeee.
> >
> > The only thing I can think of is that the
> > blocking/rejecting rules are not taking effect
> for
> > some reason.....any ideas out there?
> >
> >
> >
> >
>
>
------------------------------------------------------------------------------
> >
> > config:
> >
> > voice translation-rule 684
> > rule 1 reject /^91684/
> > !
> > voice translation-profile
> > uogdev_block_ibac_684_vtp
> > translate called 684
> > !
> > dial-peer voice 91684901 pots
> > corlist outgoing uogdev-block-ibac-css
> > translation-profile outgoing
> > uogdev_block_ibac_684_vtp
> > huntstop
> > destination-pattern 91684.......
> > port 3/0:23
> > forward-digits 11
> > !
> >
>
>
------------------------------------------------------------------------------
> > debug output:
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Calling Number=, Called
> Number=916845551212,
> > Peer Info Type=DIALPEER_INFO_SPE
> > ECH
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Match Rule=DP_MATCH_DEST; Called
> > Number=916845551212
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchCore:
> > Dial String=916845551212, Expanded
> > String=916845551212, Calling Number=
> > Timeout=FALSE, Is Incoming=FALSE, Peer Info
> > Type=DIALPEER_INFO_SPEECH
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/MatchNextPeer:
> > Result=Success(0); Outgoing
> Dial-peer=91684901
> > Is Matched
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Result=Success(0) after DP_MATCH_DEST
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersMoreArg:
> > Result=SUCCESS(0)
> > List of Matched Outgoing Dial-peer(s):
> > 1: Dial-peer Tag=91684901
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Calling Number=, Called
> Number=916845551212,
> > Peer Info Type=DIALPEER_INFO_SPE
> > ECH
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Match Rule=DP_MATCH_DEST; Called
> > Number=916845551212
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchCore:
> > Dial String=916845551212, Expanded
> > String=916845551212, Calling Number=
> > Timeout=TRUE, Is Incoming=FALSE, Peer Info
> > Type=DIALPEER_INFO_SPEECH
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/MatchNextPeer:
> > Result=Success(0); Outgoing
> Dial-peer=91684901
> > Is Matched
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersCore:
> > Result=Success(0) after DP_MATCH_DEST
> > Feb 12 10:43:56:
> > //-1/ACDBBF608086/DPM/dpMatchPeersMoreArg:
> > Result=SUCCESS(0)
> > List of Matched Outgoing Dial-peer(s):
> > 1: Dial-peer Tag=91684901
> >
> >
>
>
------------------------------------------------------------------------------
> >
> >
>
>
--------------------------------------------------------------------------------
> > 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...
> >
> > ----- Original Message -----
> > From: Ted Nugent
> > To: Lelio Fulgenzi ;
> cisco-voip at puck.nether.net
> > Sent: Sunday, February 11, 2007 11:16 PM
> > Subject: Re: [cisco-voip] dial-peers and more
> > specific vs less specific matching
> >
> >
> > Yep, I personally like to make things a bit
> more
> > granular to give it more of a PT/CSS feel,
> works
> > better for me. I'd probably go this route,
> might
> > have
> > fat fingered something but I think you'll get
> the
> > idea
> >
> > voice translation-rule 900
> > rule 1 reject /^91900/
> > !
> > voice translation-profile block
> > translate called 900
> > !
> >
> > 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 toll-fraud
> > !
> > dial-peer cor list Unrestricted-Users
> > member long-dist
> > !
> > dial-peer cor list Restricted-Users
> > member long-dist
> > member toll-fraud
> > !
> > dial-peer voice 91901 pots
> > corlist outgoing call-long-dist
> > destination-pattern 91[2-9]..[2-9]......
> > port 3/0:23
> > forward-digits 11
> >
> > dial-peer voice 1900 pots
> > corlist outgoing call-toll-fraud
> > translation-profile outgoing block
> > huntstop
> > destination-pattern 91900.......
> >
> > call-manager-fallback
> > cor incoming Restricted-Users 1 3000 <-900s
> > blocked
> > cor incoming Unrestricted-Users 1 3000
> <-900s
> > allowed
> >
> >
> >
> >
> > --- Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> >
> > > 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.
> > >
> > === message truncated ===>
> >
> _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > >
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> >
> >
> >
> >
> >
> >
>
>
____________________________________________________________________________________
> > It's here! Your new message!
> > Get new email alerts with the free Yahoo!
> Toolbar.
> >
> >
> http://tools.search.yahoo.com/toolbar/features/mail/
> > >
> _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
>
>
>
>
>
____________________________________________________________________________________
> Get your own web address.
> Have a HUGE year through Yahoo! Small Business.
> http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
>
> https://puck.nether.net/mailman/listinfo/cisco-voip
> > _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
____________________________________________________________________________________
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070212/0117a4e4/attachment-0001.html
More information about the cisco-voip
mailing list