Block Calls based on Caller ID

[afeinb]

We need to block inbound calls from specific CLID's (abusive, threatening or nuisance calls). What's the easiest way to do it?

We currently have a list of about 20 numbers we want to block and currently do it through AACC and the Master Script, but this only helps if these callers call into a call center. We want to block them entirely.

I keep seeing something called "call blocker" but can't find documentation on it.

Avaya CS1k 7.6
ASM 6.3.6
Avaya SBC 6.2.1

[mlombardi1]

In the SBC-E, create a URI group for unwanted callers. Then, on the Compliance tab of the Security Rule assigned to Session Mgr, add this URI group to the "From URI Blacklist" field. This will prompt the SBC-E to inspect the From header on calls destined for Session Mgr and firewall those you've specified.

[afeinb]

Thanks, I set that up (on both SBC's) using my cell number to test and calls still getting through.

URI rule set as Regular Expression like this: 7175551212@* and compliance tab selecting the URI group.
Am I missing a piece somewhere?

[jimvicom]

use a vactor table

I use a vector step, add a table and have the inbound calls get checked like it does for holiday hours or business hours....then if they match send them to a disconnect step....

[mlombardi1]

I use a vector step, add a table and have the inbound calls get checked like it does for holiday hours or business hours....then if they match send them to a disconnect step....

Looks like he has a CS1000, not CM. This would be easier using a vector.

URI rule set as Regular Expression like this: 7175551212@* and compliance tab selecting the URI group. Am I missing a piece somewhere?

Instead of Reg Expression, set your URI type to Plain.

[afeinb]

It's true, it's CS1K, not a CM.

Still can't get this to work. There must be something I'm missing?

You mentioned that Vectors would be easier, but this was pretty easy to set up....Too easy? Have I missed a step or item somewhere?

[mlombardi1]

Hard to say without seeing your Endpoint Policy Groups. Try applying the URI blacklist to the Security Rule assigned to the SIP trunk instead. Vectors are a CM feature and not available in Nortel.

[afeinb]

Do I want to touch the URI group under Next Hop Routing in the Routing profile for the Trunk? It's currently set at *, but the drop down lists Emergency, Unwanted Callers (built by me) and an additional one.


I think I'm over my head and not willing to try much else for fear of breaking it all.
SBC class in April, perhaps they'll cover this, if not I'll surely be asking.

[smith2001]

I tried to block a call from a specific CLID by setting up a "Numbers to Block" URI Group and adding it to Domain Policies-->Security Rules Compliance Tab and it blocked all outgoing calls from the PBX instead of blocking my one specific incoming call (that I wanted to block). Any one have any suggestions?

[downe14]

I use the format of:

0123456789@*

or for international calls I want to block:

*35xxxxxxx@*

To block the numbers in the URI group and this works ok.