[cisco-voip] Block call based on ANI and DNIS at the same time

[Telecom]

I was able to get this working and I thank everyone for their help and feedback! It is a little tricky with all the xlates and css/partition combos, but diagramming it really does help and is the step I took to get it working in my environment.

I appreciate the help!

On Jul 25, 2016, at 05:47 PM, Ryan Huff <ryanhuff at outlook.com> wrote:

Here is a quick drawing I just threw together; the technique can bit a little confusing to conceptualize at first so I always find drawings help. This does involve a bit of CSS/XLATE trickery and as such; can create a 'fragile' dial-plan. If you implement something like this, I'd advise documenting the flow you create very well and make sure it is a consideration anytime dial-plan changes are made.



Hope this helps,

-Ryan

From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Ryan Huff <ryanhuff at outlook.com>
Sent: Monday, July 25, 2016 4:17 PM
To: Telecom
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Block call based on ANI and DNIS at the same time
 
In other words, when you do route to next hop by calling party id; rather than route ALL calls to the next hop, only route calls that do not match a particular number/pattern (called party). 

This technique will capitalize on the most specific route wins matching algorithm. So if the number matches a specific pattern "do not route" else match a "!" pattern that does route.

On the patterns that you match where you do not route, you can do all sorts of interesting things. Something like a simple reorder tone; or in the case of an aggressive auto dialing bot, you could play of vacant circuit SIT tone (the three tones of happiness). Or you could forward it to unity connections system call handler that plays a nice little message asking the caller to not call back.

Sent from my iPhone

On Jul 25, 2016, at 4:07 PM, Ryan Huff <ryanhuff at outlook.com> wrote:

I am NOT trying to intentionally plug my blog here; however this is a very good article that addresses your very query.

https://ryanthomashuff.com/2014/11/call-blocking-by-caller-id/

The only thing you would do, is modify slightly so that the technique only applied to a particular called number/pattern.

Hope this helps,

-Ryan

On Jul 25, 2016, at 3:36 PM, Telecom <telecom3390 at me.com> wrote:

Hi all!

I am trying to figure out if it is possible to block calls from an ANI but only to a specific DNIS while allowing calls to other extensions to proceed from that ANI? 

The scenario:
800-555-5555 calls our extension 1000. However, extension 1000 is an executive and shouldn't be getting those calls. 800-555-5555 is a valid number associated with a vendor of ours, and calls to other internal numbers are OK, but not to extn. 1000. 

I am familiar with the "Route Next Hop By Calling Party Number" and have tested that functionality but it seems to apply to all extensions and I don't see a way to filter based on called extension as well as ANI at the same time. 

We are using CUCM 9.x with an MGCP gateway. 

We have also asked the vendor not to call extn 1000 but it is taking them a while to remove that number from their autodialers I guess as calls are still arriving.

Thanks for any ideas

Mike S.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160727/c8bb4c6c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flow.jpg
Type: image/jpeg
Size: 51363 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160727/c8bb4c6c/attachment.jpg>