Solved Blacklist issue with SIP Trunk

[wmeter]

Hi,

I'm trying to use the blacklist feature from 3CX but in my situation it has an unwanted side-effect.

I assume that 3CX sends back a 'reject' or 'don't want this call' signal to the SIP Trunk that presented the
original call, my SIP Trunk has a 'emergency' number configured at the carrier (Swisscom SBC) that sends calls to my cell phone if my PBX is down. So, you guess what happens, a known telemarketer does not ring anymore at home / office, but it now does ring on my cell... Not really a wanted situation...

Is it possible to 'tweak' the 3CX blacklist behavior to not 'SIP-reject' a call but to send it to a voice-file or virtual extension ?

Any other suggestions ? I saw articles talking about creating a virtual extension and adding the numbers of known call centers to the 'exceptions' for this extension, but that's going to be a huge list... And if yes, e.g. if there is no limit to this list of exceptions, can I bulk-csv-import this list too ?

Thanks in advance for any suggestions

 

[3CXDude]

I use CID inbound rules and route them to an eternal queue with a long max queue wait time and pretty awful MOH. They end up sitting there on hold for a little while and then give up.

After a month or so they stop calling, we now get ZERO marketing calls

 

[Peter Richardson]

If your SIP Trunk provider is sending the calls to your mobile while your PBX is down, then the calls aren't going through your PBX, so there's nothing to tweak

If it is reaching your PBX, could you set up another extension and filter calls from certain numbers to the voicemail of that extension?

 

[wmeter]

If your SIP Trunk provider is sending the calls to your mobile while your PBX is down, then the calls aren't going through your PBX, so there's nothing to tweak

If it is reaching your PBX, could you set up another extension and filter calls from certain numbers to the voicemail of that extension?

No, it's more that the call does get trough to the 3CX, the 3CX rejects it due to the call being from a number that's on a blacklist. The 3CX signals back to the trunk 'I don't want your shit*y call' and my trunk provider sees that as a technical error worthy of forwarding that call to my 'backup number'.

 

[wmeter]

I use CID inbound rules and route them to an eternal queue with a long max queue wait time and pretty awful MOH. They end up sitting there on hold for a little while and then give up.

After a month or so they stop calling, we now get ZERO marketing calls

Thx !!! Will try !

 

[YiannisH_3CX]

Hello @wmeter

Please note that the PBX will send a 603 Decline to the provider if the calling number is in the blacklist. Your provider is miss-interpreting this as the 603 Decline means that i received the call but i do not want it. In your scenario where the provider is sending the call to your mobile the best option is to ue a CID rule as mentioned by @3CXDude and set the destination to a desired destination

 

[wmeter]

Hello @wmeter

Please note that the PBX will send a 603 Decline to the provider if the calling number is in the blacklist. Your provider is miss-interpreting this as the 603 Decline means that i received the call but i do not want it. In your scenario where the provider is sending the call to your mobile the best option is to ue a CID rule as mentioned by @3CXDude and set the destination to a desired destination

Your feedback helped me identify the issue, in fact it was not the 'drop target' parameter that send the call to my mobile phone, but I had also a 'deviate if not reachable' per DID that was active. Removing that one on the carrier side did the trick, I now get a tri-tone message for blacklisted numbers, exactly what I wanted.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.