Forum Discussion
Call control doesn’t block or identify private/unknown callers
Hello, I have call control enabled on my account. A private caller was able to “pass screening”. The private caller is listed in the call control list as passed screening as well. I thought call c...
The purpose of Call Control is to filter out automated calls. It doesn't care what the caller ID says or doesn't say.
It would be nice to have the option to force callers to unblock their caller ID in order to pass Call Control. Not really a big deal for me because I rarely answer calls from Private Number - if they don't want me to know who's calling then I don't need to talk to them, they can leave a message.
The 1st time I called as "private", call control asked to enter the "code"
the 2nd time I called as "Private", got through call control as if call control was disabled. I checked the call logs and it shows the private number as "previously passed screening". does this now mean anyone calling private will get through without call control intecepting or does it really know who the private caller really is. either way all private numbers should be intercepted by call control.. sounds buggy to me!
- NFtoBC
Community Power User
Of course the system knows the number of all callers. Private number simply means they do not disclose the number to other parties (you). Thus, the system behaves as you describe. If an approved private number calls again, it is treated as a known private number, not an anonymous number.
As per Telus, if it’s blocked, the callerID (attribute I’m assuming, through SS7), is never sent out in the first place. Especially if it comes from another network. If it came from a Telus mobility subscriber, perhaps they could figure it out if they really needed to.
Interesting what Bugs is saying though. Since the caller passed call control already, that means subsequent calls could get through without having to pass again. Which could lead to automated floods of calls.
