Congress Forces FCC To Go Beyond Its Tame, 'Voluntary' Anti-Robocalling Plan
from the ill-communication dept
Last June you might recall that the Trump FCC unveiled a new robocall plan that it claimed would finally put the annoying problem to bed. And while the tech press tripped over itself to suggest the plan was a dramatic departure from FCC robocall policies of the past, the reality is there was little to nothing in the plan that was actually new. As is often the case with this FCC, a coagulation of half-measures, already existing efforts, and empty nonsense were just kind of thrown together in a pile and deemed to be something new and revolutionary.
The biggest change was FCC rule adjustment that would let wireless carriers install robocalling blocking tools on consumer devices by default, in contrast to the current paradigm where consumers have to opt in (assuming the tools are offered at all). But while the plan urged wireless carriers deploy anti-spoofing technology like SHAKEN/STIR to help prevent robocallers from hiding their real numbers, there was absolutely nothing in the plan that actually requires they actually do so. Because hard, clear rules with genuine accountability make AT&T and Verizon mad, you see.
Not surprisingly, the voluntary measures weren't likely to actually drive massive telecom companies to actually shore up their anti-robocall efforts. There were also justified concerns that as wireless carriers deployed anti-spoofing technologies, they'd use the opportunity to further price gouge US consumers. Realizing this, Congress passed the Traced Act, which would require wireless carriers provide anti-spoofing tech to consumers at no additional cost.
Amusingly, last week FCC boss Ajit Pai announced he was considering making deployment of SHAKEN/STIR anti-spoofing technology mandatory. In the FCC announcement, Pai tries to frame the effort as something he came up with on his own, despite the fact he was actually being mandated to do so by Congress:
"Pai framed it as his own decision, with his announcement saying the chairman "proposed a major step forward... to protect consumers against spoofed robocalls." But in reality the FCC was ordered by Congress and President Trump to implement this new rule. The requirement on the FCC was part of the TRACED Act that was signed into law in December 2019. Pai previously hoped that all carriers would deploy the technology voluntarily."
Pai didn't actually release his plan, but when he does it's likely to just mirror what was already established by new law. The problem remains that the Pai FCC will still need to be tough with giant companies that lag on deploying this technology, and, given the agency's tendency to roll over and bare its tummy on feckless fealty to industry, actual follow through will likely prove hard to come by, especially if bigger, more politically potent companies are the ones lagging behind.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: ajit pai, congress, fcc, robocalling, robocalls, shaken/stir, spoofing
Reader Comments
Subscribe: RSS
View by: Time | Thread
there! i thought Pai had done this all by his lonesome! guess i'll have to go back to my original opinion of the tosser!
[ link to this | view in thread ]
The FCC is tough on "being tough on giant companies." That's close enough, right?
/s
[ link to this | view in thread ]
I'm really hoping this actually happens but I won't hold my breath. I've been dealing with large numbers of robocalls for so long I've almost gotten used to them. My record so far is 18 calls in a 4 hour period.
[ link to this | view in thread ]
Re:
I would never hold my breath but would be encouraged if Pai's bosses assisted him in holding his.
[ link to this | view in thread ]
Honestly
I don't care why this is being done, I've gotten three calls from fucking "card services" today. The only thing that would make me happier is to line the bastards against a wall.
[ link to this | view in thread ]
Long ago, far away...
I asked a person incharge about the caller ID system, and if certain things could be done.
They said NOPE, cant be done.
Later found out there was a way to have computers READ all the data coming from the phone system, before you pick up the phone.
Would be REAL NICE, to have that tech in cellphones. The odds are against it, as it COULD be a privacy issue.
But with 99.99% of the WHOLE system(should be anyway) being Digital, there should be allot of things in this that would allow an easy trace.
Then there is the '*' system WE USED to have, do we still have it. Where a Fake call can be sent to the Attorney general. Which can only be looked up if there is a Person taking it to court, or enough Physical Complaints.,..
https://en.wikipedia.org/wiki/Vertical_service_code
https://www.verizon.com/support/r esidential/homephone/calling-features/star-codes-other-features
https://en.wikipedia.org/wiki/Mobile _dial_code
https://www.vaughns-1-pagers.com/telecom/star-codes-guide.htm
(seems a few are missing from the first link)
(this one shows the charges for use)
[ link to this | view in thread ]
Or use Callcentric
[ link to this | view in thread ]