Quote:
Originally Posted by DiapDealer
Exactly. That's why it can't just be shut down altogether. But there's no reason (technologically) that they can't be stopped from supplying caller id numbers that include area codes and exchanges that they're not actually responsible for.
I make all of our outgoing calls from various numbers spoof the main number of our business for caller id purposes. All calls look like they originated from our main business number. But all those other numbers that are spoofing our main number are still under our control. And our service provider KNOWS this.
There's no reason telco's can't reject calls that are providing caller id info for numbers they don't own/lease/control. It wouldn't be difficult for software to verify that the actual number and the spoofed caller id number are in fact both controlled/owned/leased by the same entities.
|
I would suggest that most of those scam calls are from PBX's based outside the US. In my various jobs working as a developer for large telecommunications companies I've work both fraud and billing (i.e. working with the call records). I've also done some switch programming. On the surface it seems simple, but when you are working with calls that are international, or are coming from some small mom and pop telecom with a 30 year old MTSO, the details get pretty complex pretty quickly.
A telephone company rejecting a call because of caller id info is seriously not an option. Most telephone companies are heavily regulated and were even more regulated 20 years ago. Telephone companies seriously don't want to explain why the call to the police department didn't go through because the caller id information was not valid. For that matter, law enforcement agencies don't want telephone companies to reject spoofed caller id, mostly because they use that particular feature rather heavily.