Solved Unable to Block SPAM Number

[buecker02]

I can't seem to block this one specific spammer and I have the number listed in the blacklist. Last time I had a spammer on another 3cx instance I was able to block the number easily.

Anything else I can do to block it? It's hitting the phone systems once every 3 seconds.

 

[Alphabetic]

What is the number in the call log? Use it for the blacklist number.

 

[buecker02]

Yes, I am using the number from the call log but it is not working.

 

[YiannisH_3CX]

Try using a wildcard so you can account for all formats of the same number.
So if the number is +1234567890 add it as *234567890

 

[leejor]

Anything else I can do to block it? It's hitting the phone systems once every 3 seconds.

I suppose you have confirmed it is coming in on a SIP trunk, and is not a Direct SIP call.
If it is happening that often, and always the same number (which seems odd, as spammers usually change their number to avoid being blocked), then you might want to get your provider involved, to see if they are able to help. That would stop calls from even hitting the PBX.

 

[buecker02]

I did have alternatives set. I added a 1 and a +1 as two other variables.

This is inbound on an AT&T PRI line. I also think this is being done on purpose due to who is being targeted. This afternoon it is targeting a specific individual.

I also created an inbound rule for that number to have the call drop. That didn't work but I did have it on the bottom of the rules list. I am going to move it to the top to see if that helps.

 

[leejor]

As a last resort, you could set the caller ID forwarding options, in the extension settings, to end the call (or maybe an endless loop IVR).

 

[YiannisH_3CX]

I did have alternatives set. I added a 1 and a +1 as two other variables.

This is inbound on an AT&T PRI line. I also think this is being done on purpose due to who is being targeted. This afternoon it is targeting a specific individual.

I also created an inbound rule for that number to have the call drop. That didn't work but I did have it on the bottom of the rules list. I am going to move it to the top to see if that helps.

Check the Activity Log for the Invite coming from AT&T and check in which SIP field they are sending the caller ID to. Then check your inbound parameters of the trunk and make sure you are reading the caller ID from the correct SIP header. If the PBX is set to read the caller ID from a different SIP header then blacklisting the number of assigning a CID rule to it won't work.

 

[buecker02]

Check the Activity Log for the Invite coming from AT&T and check in which SIP field they are sending the caller ID to. Then check your inbound parameters of the trunk and make sure you are reading the caller ID from the correct SIP header. If the PBX is set to read the caller ID from a different SIP header then blacklisting the number of assigning a CID rule to it won't work.

Thanks for the suggestion. I reviewed the call log this morning and the CID rule is working. When that specific number comes in it is immediately dropped.

 

[YiannisH_3CX]

Thanks for the suggestion. I reviewed the call log this morning and the CID rule is working. When that specific number comes in it is immediately dropped.

Glad to see you were able to resolve the issue.