Blocking all international calls for multiple destinations

Milos Boksan

Gold Partner
Advanced Certified
Joined
Jun 26, 2024
Messages
42
Reaction score
17
I have a specific request from a customer, and I am having a bit of trouble on how to implement this.

It is a series of restaurants, all with their own DID.
They want me to filter all anonymous calls, and all calls not from the local country code.

Blocking anonymous calls is easy enough.
I am having issue with implementing the "exclude all country codes except for one" rule so call to a specific DID still continue to the original destination.

Any hints are appreciated.

Thanks
 
Just to add one idea is to make several rules in the Advanced->CID Rules to block all other country IDs.

Something like this:
block_anon_int_example.png

The example is I want only Belgian (+32) inbound numbers to come through.
 
What about forwarding calls with the correct CID, to one destination, then route those based on the DID. Send all other calls to a "default" destination that ends them, or gives them a recording of some sort.

I question why a restaurant would want to block callers that don't have the same country code on their number? It could be a visitor, using their mobile. Do they not want any tourist business? Business must be great if they can afford to be that picky.
 
Last edited:
When a call comes in its the inbound rules that determine where the call is routed based on DID.
What is the type of object that can do DID routing? A call script?
If I route the call with a correct CID to a queue, or digital receptionst, how do I then route that same call to the extension of the specific location? I am having trouble thinking up of what might have the ability to do what you said.

The "restaurant" part is made up. Dont get hung up on it.
 
Just to add one idea is to make several rules in the Advanced->CID Rules to block all other country IDs.

Something like this:
View attachment 50250

The example is I want only Belgian (+32) inbound numbers to come through.
That looks good, why not using it? It should do what you want.

When a call comes in its the inbound rules that determine where the call is routed based on DID.
What is the type of object that can do DID routing? A call script?
Yes, a call script triggered on trunk calls can do that - even before the 3CX CID and DID rules are processed.
If you use your CID rules described above you don't need a call script. Not for that.

If I route the call with a correct CID to a queue, or digital receptionst, how do I then route that same call to the extension of the specific location? I am having trouble thinking up of what might have the ability to do what you said.
If you use CID rules to block all unwanted callers from undesired countries (and you don't use a CID rule for the desired country, e.g. +32), then for the remaining calls the regular DID rules will be followed to route them to the desired destinations. No need for a call script :)
 
  • Like
Reactions: KyriacosS_3CX
I did implement this, its working well.

Thanks all for feedback, just wanted to get some validation that I'm not missing something obvious.
 

Members Online Now

Forum statistics

Threads
111,832
Messages
589,282
Members
164,662
Latest member
DejanMDS