Solved Blacklist Number not working

[rbergthold]

i'm trying to block a number on the blacklist. it shows up in call log as: First Last (4066723102)
i added the number to the blacklist as 4066723102
however, the call is still ringing through. My concern is that i have something set incorrectly on my SIP TRUNK inbounc parameters. Can you advise?

 

[Curtis C]

try putting a wildcard in front of the number so that way if it is coming in as +14066723102 or 14066723102 the star will take away anything preceding the number so
*4066723102
It works for me

 

[TheodorosG_3CX]

This depends on how the number is represented in the PBX. As @Curtis C mentioned wildcard will help here.

 

[rbergthold]

it's being presented as 10 digits. i tried wild card and no change. Per my previous question, could it have anything to do with my SIP Trunk Inbound Parameters? How do you have yours set?

 

[Curtis C]

My trunk is exactly the same, with no check mark in Call Source Identification.Try the wild card with just the last 4 digits *3102
see if that works. Just remember that the code will block every number ending in 3102

 

[rbergthold]

so this is also interesting. it works on one of my other systems; but not on the system i am attempting to set it up with. This systerm is using same SIP provider with same settings. here is what i see in the activity log when i call in:

01/17/2024 9:40:24 AM - [Flow] Call(C:799): caller's number '4066723102' is in blacklist

However, call completes to the Digital Receptionist

 

[TheodorosG_3CX]

Run a capture and check how the number is represented in the PBX. Then proceed accordingly.

 

[rbergthold]

my capture shows number listed as ten digits. I dialed on this capture from 4062488900:

"Start Time","Stop Time","Initial Speaker","From","To","Protocol","Duration","Packets","State","Comments"
"3.938463","29.184560","208.85.62.103",""CONNECT TEL & C" <sip:[email protected]>","<sip:[email protected]>","SIP","00:00:25","7","COMPLETED","INVITE 200"

I did notice that when the number is on the block list, it just rings & rings until then goes to voicemail for a user. it's not following any sort of day routing, after hours routing, ring group or queue routing.

 

[TheodorosG_3CX]

The blacklisted number should not be routed to any endpoint.
If it is not possible to locate the issue you can also create a support ticket to further investigate.

 

[rbergthold]

it's not routed to any endpoint. the only inbound parameters i spoke of are on in the screenshot on my first entry on this thread. Set exactly the same as they are on another system with the same provider, sending the same amount of digits. it's just weird that it works on one system then not the other. I do feel like there is something i am missing; but I'm not sure, lol I may take your advise and open a support ticket.

 

[TheodorosG_3CX]

This might also require to check logs as well. Give it a try and you are welcome to contact us to check and advice.

 

[rbergthold]

This might also require to check logs as well. Give it a try and you are welcome to contact us to check and advice.

what specifically in the logs should i look for?

 

[rbergthold]

just to reiterate, this is what i saw in the activity log:

01/17/2024 9:40:24 AM - [Flow] Call(C:799): caller's number '4066723102' is in blacklist

 

[TheodorosG_3CX]

This might require a combination of logs.

 

[rbergthold]

So, here's the update. The PBX IS sending a 603 declined. However, for some reason, the SIP provider, instead of dropping the call, is sending the call to a configured "unavailable forward" to a user cell. That unavailable forward is a backup, so customer doesn't miss calls in the event the 3CX were down. I would like to name drop Dimitris Lappas,from 3CX Helpdesk who ran PCAPS with me to chase this down!

 

[TheodorosG_3CX]

Glad to know this is resolved