[1.33.8] Phone rang although # not in contacts

[Winfried]

Hello

Although I have CF set to block unknown contacts, and the number is in neither Android's nor my PIM's contacts… the phone rang.

Why is that? Am I missing something in the Settings?

Thank you.

---
Edit: In the meantime, I added a wildcard since I also got another fake call with the same prefix

 

[admin]

Hello

Although I have CF set to block unknown contacts, and the number is in neither Android's nor my PIM's contacts… the phone rang.

Why is that? Am I missing something in the Settings?

Thank you.

---
Edit: In the meantime, I added a wildcard since I also got another fake call with the same prefix

Hello,

We need a bit more detail to understand what happened.

Please send the phone number. If it is a spam number, you can post it openly here.

Also, please tell me what text was shown under the number in the Calls tab. In your screenshot this part is blurred, so I cannot read it.

 

[Winfried]

+33162300761 and +33162300950

For some reason, one got blocked as expected (since it's not in either phonebooks) while the other rang.

 

[Oliver]

Hello @Winfried

This is caused by the filter priority order.

The function “Block all calls except contacts” has the lowest priority by default. Callfilter.app applies filters one by one in the same order as they are placed in the Filter priority section.

In your case, when checking the community database, Callfilter.app identified this number as allowed (green), so the call was allowed before the “Block all calls except contacts” rule was reached.

 

[Oliver]

Although I can see that both numbers have a negative rating, so this does look like an error.

I will try to reproduce it on my side and I will write back a bit later with the result.

 

[Oliver]

+33162300761 and +33162300950

For some reason, one got blocked as expected (since it's not in either phonebooks) while the other rang.

Hello @Winfried

We found a bug that caused some numbers with a negative rating to not be blocked and to appear in the app as green. It affected only about 1-2% of users, but that was still unacceptable.

We fixed it over the past few days, and the issue should disappear once the database has fully updated.

Thank you very much for your help! It helps us keep the app working properly and effectively.