2 ms·
Exactly this. The last time I had a chance to talk to an FCC commissioner (they were in the Bay Area at an IEEE meeting) I strongly suggested that they could do
by ChuckMcM 8y ago
Exactly this. The last time I had a chance to talk to an FCC commissioner (they were in the Bay Area at an IEEE meeting) I strongly suggested that they could do a world of good by creating such a database, requiring anyone who wants to call into the US have their numbers registered in such a database, and to put 'DO NOT TRUST' on any number that wasn't in the data base as its default Caller ID.
Pair that with creating an access restriction to the US PSTN for any entity that originates a call with a spoofed number that is enforceable with technology rather than by voluntary or compelled action, and much of the problem will be mitigated.
- robrtsql 8y agoThat doesn't solve the problem where legitimate numbers are spoofed, does it? It seems my number is among the many that are being used by robocallers, because I sometimes get texts from strangers saying "who are you?", or "sorry, can't talk now".
- ChuckMcM 8y agoThat is part two, adding real teeth to spoofing a legitimate number. Basically on confirmation that a provider allowed such a call to be made on the US PSTN would result in all their numbers being blocked from the US PSTN until they could prove they had fixed the problem.
- sp332 8y agoThere's a system like that in the works now. Although it's not implemented by the FCC, the agency has threatened "regulatory intervention" against any providers who don't implement the SHAKEN and STIR protocols. https://arstechnica.com/information-technology/2019/03/att-and-comcast-claim-anti-robocalling-milestone-with-new-caller-id-tech/ https://arstechnica.com/information-technology/2019/03/att-a...