Is it possible to block incoming calls from an entire area code?
Thanks
Add them all to this list using an excel import, to maybe look at blocking at the carrier level.
https://sangomakb.atlassian.net/wiki/spaces/PG/pages/20644332/Blacklist+Module+User+Guide
@mahbell - Thanks for that link. It’s not really what I want, I want to block an entire area code. I know that sounds heavy handed but we’re getting a lot of spam calls from this area code and since we don’t really have business or contacts there we just want to block all phone numbers from this area code.
I did learn something that will help in the intermediate from the link you provided and that is *32 to add the last call to the block list. Until now I was manually entering the numbers one-by-one into the block list via the web interface.
However it seems that the spammers are figuring out they are blocked and rotating their number to others so we are playing bop-a-mole on the daily.
Create an inbound route with the CID set to intercept the area code in quesiton. Depending on the CID format of incoming calls it might look like any of the following
902NXXXXXX
1902NXXXXXX
+1902NXXXXXX
I can’t recall if a leading underscore is required for this field. Check the CID field tooltip.
@lgaetz - Thank you for this! I have set it up, correctly hopefully. I will report on the success on this in a few days to a week and let you know the results.
1 Like
@lgaetz - I’ve tried all three of your suggestions individually, one at a time:
902NXXXXXX
1902NXXXXXX
+1902NXXXXXX
But none have stopped the inbound callers.
Here is a screenshot of what I did:
If I’ve done something wrong please let me know.
Try putting setting CallerID Number to _1971NXXXXXX and setting CID Priority Route to Yes.
If no luck, check the CallerID field of the CDR record of a mishandled call and confirm that you have entered CallerID Number in the correct format.
If still no luck, paste the Asterisk log for a mishandled call at pastebin.com and post the link here.
1 Like
@Stewart1 - I have changed the Inbound Route as you suggested, but no calls since I made the change.
In the meantime here is a call record that you asked for:
I believe that you need CallerID Number for the Inbound Route to be
_+1971NXXXXXX
You could also consider not allowing transport on UDP:5060, (that should fix it fast 
)
@Stewart1 - Using:
_+1971NXXXXXX
Also did not work.
So far I’ve tried:
_+1971NXXXXXX
902NXXXXXX
1902NXXXXXX
+1902NXXXXXX
But none have stopped the spam calls from ringing through and not being added to the block list.
@dicko - I do not understand how blocking a port will block an entire area code range. But if it will help please tell me how I would do your suggestion.
Here is the call log from this morning:
Sorry, I missed that CEL != CDR in your case, because the from-pstn-e164-us context rewrote the number!
So your Inbound Route should have CallerID Number
_971NXXXXXX
and CID Priority Route should be Yes.
2 Likes
@Stewart1 - I wanted to run the last inbound route CID for a while to make sure it was working and I can confirm that
_971NXXXXXX
Is stopping the spam calls.
I was under the impression that this setting would add the incoming call number to the block list, however it seems that it is stoping the inbound calls only because the block list has not added a single number. Attachments. Not that I really mind because I am getting the result I wanted. I may not understand the set destination settings correctly.
Thank you all for your help and input. I always get useful assistance from you folks!
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.