Barring a call 1

[Mindly]

I have an IPO that is being BOMBARDED with junk incoming calls from a single DID.
Calls are received with just silence; no audible message accompanying.
Calls hit the IPO approximately 6 to 12 times per minute, 24 hrs / day!
The DID is configured to be barred.
They are being successfully barred about 95% of the time.
For some unknown reason, the exact same DID occasionally manages to avoid being barred, hits the auto-attendant and then rings multiple phones in a hunt group.
Obviously this is very disruptive to users.

Anyone ever experienced such a problem?

 

[IPid10t]

Hello Mindly, the number that they are calling from, is it the same number every time? Or do they change their caller ID each time? Also what kind of lines do you have, PRI, SIP, or analog?

 

[IPid10t]

If it is coming from the same number every time then this should be easy to block.

If PRI

1: Go to Line
2: Select PRI
3: Check to see if there is anything in the Prefix field. If so remember the number. We will need this later. You might see 9, or 91 those are most common (usually goes with your dial out code)
4: Now to build our route to block this number go to Incoming Call Route
5: Right click select New
6: in the incoming number field enter * (this is a wildcard and will be used to match any phone number they call into on the system)
7: In the Incoming CLI field enter the prefix you documented in step 3 (For example, if it was a 9 then it would look like 9xxxxxxxxxx replace the x's with the phone number. If there was nothing in your prefix field then you can continue on this step) then enter the phone number you wish to block.
8: Leave destination empty and save. Since there would be no destination programmed the call would ring busy and disconnect since it has nothing to route to.


If SIP
1: Go to Line
2: Select your SIP line
3: Check to see if there is anything in the Prefix field. If so remember the number. We will need this later. You might see 9, or 91 those are most common (usually goes with your dial out code)
4: Now to build our route to block this number go to Incoming Call Route
5: Right click select New
6: in the incoming number field enter * (this is a wildcard and will be used to match any phone number they call into on the system)
7: In the Incoming CLI field enter the prefix you documented in step 3 (For example, if it was a 9 then it would look like 9xxxxxxxxxx replace the x's with the phone number. If there was nothing in your prefix field then you can continue on this step) then enter the phone number you wish to block.
8: Leave destination empty and save. Since there would be no destination programmed the call would ring busy and disconnect since it has nothing to route to.

 

[TouchToneTommy]

And, if it still somehow slips through to Voicemail Pro, add an action just after the Start to compare $CLI with the number you don't want calling, and if true connect to a disconnect and if false continue with the call flow.

 

[Mindly]

IPid10t and TouchToneTommy
Thank you for your responses.
1) The actual number that the calls are coming from is the same each time.
2) The line is a PRI circuit.
3) The prefix for the PRI line is 81.
4) In System Monitor call logging, it was noted that the offending calls are coming in with varying prefixes, “81”, “811” and “81+1” followed by the same phone number.
5) An ICR entry accounting for each prefix / phone number combination with destination field empty has been created.

TouchToneTommy: This is embedded voicemail.

Thanks again.
Keeping fingers crossed.