Blacklist not working

[Ben C]

Hi. Last week I got a request to blacklist a number. Today that person complains she got a call from that number again.
I decided to play with my cell, so I added my cell to blacklist. Surprisingly that call went through !!! Our main number is routed to 'Digital receptionist'.
I have a long list of blacklisted numbers, but this is the first time a person complaining getting calls from any of these blacklisted numbers.
I can't say for sure if this feature had worked in the past or not.

I read in the forum that this feature doesn't work when you add-delete-add again a phone number.

Anyone experiencing the same?

Thank you

 

[leejor]

Check the 3CX log of an incoming call of the number you are blocking. Be sure that it matches exactly. I haven't had any issues. What version 3CX are you running?

 

[livn46]

Yes, look for whether it matches exactly or not. I had this same experience, and learned that I had to add two entries for every incoming number I wanted to blacklist: both XXXXXXXXXX AND 1XXXXXXXXXX. Many times there's a 1 in front, so a blacklist rule without a 1 won't match. You also can't put any dashes or parentheses or anything else in: just straight numbers.

 

[Ben C]

Sorry, I forgot the version: v.14 SP3 Build 491690.513.

The log shows exact the same number of the caller, without 1.
23-Aug-2016 11:22:36.818 [CM503007]: Call(C:1711): Ivr:700 has joined, contact <sip:[email protected]:5483>
23-Aug-2016 11:22:36.816 [CM503007]: Call(C:1711): Line:10001<<8668783xxx has joined, contact <sip:[email protected]:5060>
23-Aug-2016 11:22:36.815 L:1711.2[Ivr] has joined to L:1711.1[Line:10001<<8668783xxx]
23-Aug-2016 11:22:36.665 [CM503025]: Call(C:1711): Calling T:Ivr:700@[Dev:sip:[email protected]:5483;rinstance=f039512de8ab9c27] for L:1711.1[Line:10001<<8668783xxx]
23-Aug-2016 11:22:36.616 [CM503027]: Call(C:1711): From: Line:10001<<8668783xxx ("Unavailable:Main AA" <sip:[email protected]:5060>) to T:Ivr:700@[Dev:sip:[email protected]:5483;rinstance=f039512de8ab9c27]
23-Aug-2016 11:22:36.616 [CM503004]: Call(C:1711): Route 1: from L:1711.1[Line:10001<<8668783xxx] to T:Ivr:700@[Dev:sip:[email protected]:5483;rinstance=f039512de8ab9c27]
23-Aug-2016 11:22:36.615 [CM503001]: Call(C:1711): Incoming call from Line:10001<<8668783xxx to <sip:[email protected]:5060>

I have the numbers on the blacklist without the '1'.

I just did a test with another cell number (not blocked before) with and without the 1 and the call still went through...!!

 

[leejor]

Something I forgot about... I prefix all incoming numbers with a 9 so that redial will work with the number displayed on the sets, I also put numbers in the blacklist with the 9 prefix, and it works. You might try that if you do something similar.

 

[Ben C]

Hi leejor
We don't use 9 to dial outside, just direct dial of 3 or 10 digits, so I don't think we need to add the 9.

I think blacklist was working and I was wandering if it stopped at some point, probably after applying any sp...

Thank you
Ben

 

[Ben C]

Can anyone confirm if 'Number Blacklist' works or not on V14 sp3 build 49169.513 ?

Thank you

 

[leejor]

That's the version I'm running, and it works for me.

 

[livn46]

I had not had reason to question this, but I just had a report from our front desk that a blocked number called them, so I investigated. As Ben C describes, the number in the call log matches exactly the number I have in my block rule, but the number is still not blocked. Also, as he describes, I put my own cell phone into the blacklist and it did not block it. It does seem possible to me that this stopped working during some recent update perhaps? Because I'm pretty sure it was working before. We are also running v14.0.49169.513.

 

[livn46]

I was able to get a response from 3CX support. Apparently the blacklist not working is a known issue with v14.0.49169.513, and will not be fixed: their recommended resolution was to upgrade to v15 (not an option for us at this time...)

 

[Ben C]

Thank you 'livn46' for clarifying this.
So it's not me, it's the version. I feel better now

 

[Ben C]

Hi livn46
I tested the 'exceptions' rules under 'Extension->Forwarding rules' and seems to work.
This is for extension level, not company wide block.
The limit is 15 rules per extension. At least there is something...