I have a gripe with the way Caller ID works — or in fact, increasingly doesn’t work — on wireless phones. I’ve noticed that most very stinking time I get a call on my wireless phone, the Caller ID information is wrong. Sometimes the number is correct, but the city is wrong. When Caller ID was introduced a few decades ago, it was great. It started on the landline phone, either providing a name or number to give you a heads up as to who was calling. Fast-forward to the present. Today, when a call comes into our wireless phone, the information that appears on the screen is accurate only some of the time.
> Do you agree, or am I getting upset over nothing?
You are right to complain, but we need to replace the obsolete SS7 network with pure IP networks first because inaccurate CID is not the only fault in legacy networks, you also have issues with SMS & location privacy and all sorts of other horrendous security flaws.
Why Is Wireless Caller ID So Often Wrong?
Posted by: Jeff Kagan September 24, 2018 10:35 AMI have a gripe with the way Caller ID works — or in fact, increasingly doesn’t work — on wireless phones. I’ve noticed that most very stinking time I get a call on my wireless phone, the Caller ID information is wrong. Sometimes the number is correct, but the city is wrong. When Caller ID was introduced a few decades ago, it was great. It started on the landline phone, either providing a name or number to give you a heads up as to who was calling. Fast-forward to the present. Today, when a call comes into our wireless phone, the information that appears on the screen is accurate only some of the time.
You are right to complain, but we need to replace the obsolete SS7 network with pure IP networks first because inaccurate CID is not the only fault in legacy networks, you also have issues with SMS & location privacy and all sorts of other horrendous security flaws.