[cisco-voip] dial-peers and more specific vs less specificmatching
Lelio Fulgenzi
lelio at uoguelph.ca
Mon Feb 12 13:18:58 EST 2007
Yup, everything is matching as expected. It's the rule that doesn't seem to be taking affect. I got the following debugs below. It seems it doesn't like the 'reject' option. When I modify the rule to change the dialed number to something, say 18005551212, it works fine.
I never would have though it would be so hard to block outbound numbers!
------------------------------------------------------------------------------
configs
before: with reject rule it fails as per debug attached.
voice translation-rule 684
rule 1 reject /^91684......./
after: with search/replace, it works fine.
voice translation-rule 684
rule 1 /^91684......./ /918005551212/
------------------------------------------------------------------------------
debug with 'reject' rule:
3640-vgw#debug voice translation
VoIP Translation Rule debugging is enabled
3640-vgw#
Feb 12 13:06:39: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_profile_from_trunkgroup_internal: Voice port 0x6536494C does not belong to any trunk group
Feb 12 13:06:39: //-1/9E91EBED809B/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x654626F4; count=1
Feb 12 13:06:39: //-1/9E91EBED809B/RXRULE/regxrule_stack_push_RegXruleNumInfo: stack=0x654626F4; count=0
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_stack_push_RegXruleNumInfo: stack=0x654626F4; count=1
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: number=61003 type=unknown plan=unknown numbertype=calling
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_match_internal: Error: ruleset for calling number not found
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: No match: number=61003 type=unknown plan=unknown
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: number=916845551212 type=unknown plan=unknown numbertype=called
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_match: Skipping a call blockrule; number=916845551212 rule precedence=1
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_match_internal: No match found
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: No match: number=916845551212 type=unknown plan=unknown
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: number= type=unknown plan=unknown numbertype=redirect-called
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_match_internal: Error: ruleset for redirect-called number not found
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_profile_translate_internal: No match: number= type=unknown plan=unknown
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_dp_translate: calling_number=61003 calling_octet=0x0 called_number=916845551212 called_octet=0x80 redirect_number= redirect_type=0 redirect_plan=0 redirect_PI=0 redirect_SI=0
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_vp_translate: No profile found in voice port or trunk group for outgoing direction
Feb 12 13:06:44: //-1/9E91EBED809B/RXRULE/regxrule_vp_translate: calling_number=61003 calling_octet=0x0 called_number=916845551212 called_octet=0x80 redirect_number= redirect_type=0 redirect_plan=0
Feb 12 13:06:53: //-1/9E91EBED809B/RXRULE/regxrule_stack_pop_RegXruleNumInfo: stack=0x654626F4; count=2
------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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:09 PM
Subject: Re: [cisco-voip] dial-peers and more specific vs less specificmatching
Lelio,
Did you try testing your translation patterns to see
if you can get a match at least before you dialed?
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
>
____________________________________________________________________________________
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list&sid=396546091
_______________________________________________
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/7657518c/attachment-0001.html
More information about the cisco-voip
mailing list