Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 02-03-2015, 07:51 AM
afeinb afeinb is offline
Member
 
Join Date: Apr 2014
Posts: 7
afeinb has 10 reputation points
Default Block Calls based on Caller ID

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
Reply With Quote
  #2  
Old 02-03-2015, 12:46 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Genius
 
Join Date: Sep 2010
Location: New York
Posts: 396
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

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.
Reply With Quote
  #3  
Old 02-03-2015, 01:54 PM
afeinb afeinb is offline
Member
 
Join Date: Apr 2014
Posts: 7
afeinb has 10 reputation points
Default

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?
Reply With Quote
  #4  
Old 02-04-2015, 08:07 AM
jimvicom jimvicom is offline
Hot Shot
 
Join Date: Jan 2011
Posts: 17
jimvicom has 10 reputation points
Default 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....
__________________
-Jim
ACIS-CM
Reply With Quote
  #5  
Old 02-04-2015, 08:16 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Genius
 
Join Date: Sep 2010
Location: New York
Posts: 396
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

Quote:
Originally Posted by jimvicom View Post
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.
Quote:
Originally Posted by afeinb View Post
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.
Reply With Quote
  #6  
Old 02-04-2015, 01:17 PM
afeinb afeinb is offline
Member
 
Join Date: Apr 2014
Posts: 7
afeinb has 10 reputation points
Default

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?
Reply With Quote
  #7  
Old 02-04-2015, 01:19 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Genius
 
Join Date: Sep 2010
Location: New York
Posts: 396
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

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.
Reply With Quote
  #8  
Old 02-04-2015, 01:28 PM
afeinb afeinb is offline
Member
 
Join Date: Apr 2014
Posts: 7
afeinb has 10 reputation points
Default

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.
Reply With Quote
  #9  
Old 09-21-2018, 04:29 PM
smith2001 smith2001 is offline
Aspiring Member
 
Join Date: Sep 2018
Posts: 1
smith2001 has 10 reputation points
Default

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?
Reply With Quote
  #10  
Old 09-26-2018, 02:24 AM
downe14 downe14 is offline
Member
 
Join Date: Jun 2016
Posts: 8
downe14 has 10 reputation points
Default

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.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:22 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.