CID Blacklist rules

[NCIA]

Any idea on why a rule of UNKNOWN* would not block calls with a CID of "UNKNOWN (+DIDNUMBER)"?
My other CID rules are working, generating a busy signal and a reason of "Route busy" in the Call Log report.

V20.0 Update 2 (Build 715 Release)

 

[TheodorosG_3CX]

If you set this rule to the top priority the issue is the same?

 

[NCIA]

If you set this rule to the top priority the issue is the same?

How is priority set? Top item in the list? If so, I see no other way to do this than to delete all rules and recreate them in the desired order. I could not find documentation regarding the import feature, nor find a way to export the existing rules.

I will delete and recreate, and then I will report back.

 

[TheodorosG_3CX]

Let me know the outcome

 

[NCIA]

Still waiting on a call with that CID to come in. We usually get 3-5 a week.

 

[TheodorosG_3CX]

No problem, check and update the post.

 

[NCIA]

Still not working.

 

[TheodorosG_3CX]

Set the CID rules with a space like "UNKNOWN *" and check again please.

 

[NCIA]

Changing the rule to add a space "UNKNOWN *" ended up blocking all incoming calls to our PBX.

 

[TheodorosG_3CX]

Then something is different on the sip invite. Are you using a 3CX Supported Provider?

 

[NCIA]

Then something is different on the sip invite. Are you using a 3CX Supported Provider?

We are using Wiretap Telecom https://www.wiretaptelecom.com/

 

[Cody Schilke]

Please reach out to us directly if you'd like us to assist.