Blocking a nuisance caller

[C_ATCHY01]

Hi all,

I have a query regarding nuisance callers.

The end user is reporting nuisance calls from an automated system around the same time every day, however the calling numbers last 4 or 5 digits change every time they call (it’s not a pattern I could review to block them). On searching the number it seems to be coming from the Middle East / asia and we can’t block all calls from there.

I’ve blocked callers before on the SBC EMS, EC500 and using VDNs, VRTs ANIs etc. But this one has got me because of the random digits at the end each time. Any ideas how I could do this?

Avaya CM 6.3 (Due an upgrade to 7)

 

[Saiyan656]

Vector route table e.g., 1: 61922?????

 

[C_ATCHY01]

Hey,

Thanks for the quick response. Completely overlooked the wildcards...

So would I just go about this by amending the incoming call handling treatment to check that table for the specific entries? If so, can you give me a brief description example?

Thanks so much

 

[kyle555]

How were you doing it on the SBC?
On CM, on the incoming call form for the trunk you'd make the call go to a VDN and vector. In the vector, "goto step 5 if ani in table 1" and if you 'change vrt 1' you can have 011222333?.
Step 5 = disconnect, otherwise, route-to user's extension

It's the same way you'd have a call center open 9-5 'local' hours and have a VRT of every 'east coast' area code like 212? and central, mountain, etc. If your system were in Eastern time, then goto step 10 if ani in table 1 (EST) and step 10 says 'go to step 15 if hours between 9-17' and for the ANI's in central time, go to step 20 and if hours are between '10EST and 18EST' then queue up.

The SBC can have wildcards in it's URI groups as well. Your default flow for 'calls from the carrier' on 'uri group' * 'goes to sm', but if you're adventurous, you can have a URI group 011-222-333-* that the SBC blocks on a rule with max concurrent sessions = 0