SPAM Calls / Inbound CID Rule Question

[jst2]

I am having a problem with local spam calls. As such, I wanted to create an Inbound CID rule capturing phone numbers directing them to ring group keeping them in loop until the call is being dropped.

Setting up the CID rule was easy, but now incoming phone calls from the specified area code go to the ring group specified in the CID AND the ring group specified in the extension.

I was kind of expecting the CID rule to overwrite the trunk setup, but this doesn't seem to be the case. I am also suspicious that using a dead extension will end the call immediately.

How can I get this to work?

Maybe somebody has a better idea? Basically, I would like to keep spam calls in a loop without ringing any phones.

Any suggestion to reduce spam calls would be appreciated.

 

[craigreilly]

This will cost you money for as long as they are connected to your PBX right?
Why not just drop the call?

Create dummy extension 123
Create dummy Queue 456
Add that extension 123 to the Queue 456
Set that extension 123 to Logged In
Queue On "Destination if no answer" - outside number - 456

It's not very elegant... Hold music just comes in for a sec, then out, in , out.

Maybe a CFD?

 

[jst2]

Thank you for your suggestions!

It would be fine to just drop the call, but it appears that spam callers really don't like numbers that never pick up and have no VM.

Two questions on your suggestion:

1. How would I direct the incoming call to this extension? CID rule?
2. How can I set an extension to "logged in"?

Any idea on how I can overcome the issue that 3CX is processing CID rules in addition to the rule specified in the trunk?

 

[craigreilly]

1. Yes - Make sure they are in the right order. I am not exactly clear on what was happening about going to 2 ring groups - ??
2. Extension - click it once - then at top menu goto Status.

 

[jst2]

On 1:
I have the CID rule over the DID rule for the trunk. However that doesn't fix the problem. Any incoming call is first executing the rule specified in the trunk (IVR). So, basically it starts ringing all extensions and then it executes the CID rule.

Here is a copy of the log:

06/21/2019 11:45:19 AM	Name (CID)	SPAM Extension (XXXB)	Not Answered
06/21/2019 11:45:14 AM	Name (CID)	IVR (XXXA)	00:00:05

Obviously, I would want it to only call the SPAM Extension and drop the call.

On 2:
Yes, the SPAM Extension is set to "Available".

I guess the real question is how can I stop the incoming spam call from going to IVR? Maybe I should remove the IVR settings in the trunk and only have the DID rule?

 

[craigreilly]

# 1) Doesn't seem right. Do you have an Inbound Rule for default traffic to the trunk? Or only the Trunk rule? Make sure you have a rule in Inbound Rules. I forward my wife's cell phone directly to my extension using CID, then further down the list is the DID rule for the remainder of the traffic to our Main DID.

You have to know what you are sending to the Spam Extension - is it a list of numbers? How do you know it's Spam?


2) Set SPAM Extension to Logged In... This way an extension is available.

 

[jst2]

I have the trunk rule and an inbound DID rule.

I guess the real question is how these rules are processed. Is the trunk rule processed first? If that's a case, I can only get this to work if I get rid of the trunk rule and use a DID rule instead. At the moment, I have both which might be overkill.

We have one spam caller who is using numbers any number like XXX-YYY-???? As such, I can just drop the whole block XXXYYY*. It is not ideal and I know I include legit callers, but the spam calls are coming early in the morning and are just a real nuisance.

I have already contacted the service provider because obviously the numbers are spoofed, but they are no help and don't see SPAM calls as their responsibility. Quite sad since I am quite sure that they might be able to identify some SPAM calls very easily.

 

[leejor]

Unfortunately, if the SPAM caller is changing their number, as most do, you won't be able to screen using caller ID. If it is really bad, you can screen callers using an IVR and requiring them to dial a digit before continuing. Many PSTN providers offer a similar service for residential customers. The initial recording could be something such as ..."Thank you for calling the ABC company, please press 1 to be transferred to our main reception." You can even include some information, such as the opening hours. Callers can also transfer to other departments as required. Requiring the single digit will prevent all spam callers from getting through. Just remember to send any callers that do not input a digit (rotary phone?), off to another recording (voicemail?), or simply end that call.

 

[jst2]

Thank you for your feedback!

I like your idea of having callers having to press 1 to continue. Just one question: Would it be possible to somehow exclude known numbers (stored as a 3CX contact)? Otherwise I would miss all legit automated calls.

 

[craigreilly]

A dummy extension as the main point of presence.
Send calls to the IVR
unless they are in the extensions exception list


Will need some more work for after hours, etc.

 

[jst2]

Maybe after hour processing could be handled by setting up an exception dummy extension using forwarding rules?

I think this sounds promising and I might give this a try next week. Will report back on that..

Only issue would be legit automated calls with a rotating number.

Thank you!

 

[jst2]

OK. I have now tried the solution above and it works well.

However, I won't be able to use it myself because I am getting automated calls that, sadly, use rotating phone numbers.

Back to the drawing board for now...

 

[leejor]

However, I won't be able to use it myself because I am getting automated calls that, sadly, use rotating phone numbers.

They aren't stupid. They know that you will catch on if they use the same number, so they keep changing it. That's why you need to make them "jump through some hoops" before they reach you, just to prove they are a real person. We have to do it on our computers "I am not a robot"...

 

[jst2]

Well, this is what the solution outlined above does. However, it doesn't work if you are getting automated calls using rotating phone numbers. I am still researching this some more and hope that these calls are using a limited block which would allow me to use the solution.

It definitely worked like a charm when I used it yesterday. Only problem was that one call I needed to get that the method decided to block because it wasn't on the list.

Still doing more research to make it work here.

Sorry, if my previous email wasn't clear on it: This solution should definitely work for anyone using 3CX for home or a business that doesn't get automated calls.