Article 50BY1 FCC requires anti-robocall tech after “voluntary” plan didn’t work out [Updated]

FCC requires anti-robocall tech after “voluntary” plan didn’t work out [Updated]

by
Jon Brodkin
from Ars Technica - All content on (#50BY1)
GettyImages-1143981819-800x533.jpg

Enlarge (credit: Getty Images | MassimoVernicesole)

Update (April 1, 2020): The Federal Communications Commission voted unanimously to finalize the anti-robocall order on March 31, 2020, complying with instructions the commission received from Congress. The order "requires all originating and terminating voice service providers to implement STIR/SHAKEN in the Internet Protocol (IP) portions of their networks by June 30, 2021, a deadline that is consistent with Congress's direction in the recently-enacted TRACED Act," the FCC said. As we wrote earlier, the FCC plans a one-year deadline extension for small phone providers. The FCC also voted to seek public comment on how "to promote caller ID authentication on voice networks that do not rely on IP technology," meaning older landline networks.

Original story from March 6, 2020 follows: Phone companies would be required to deploy technology that prevents spoofing of Caller ID under a plan announced today by Federal Communications Commission Chairman Ajit Pai.

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.

Read 8 remaining paragraphs | Comments

index?i=ZdVEGcWH0QA:lKZHNm_x5Ac:V_sGLiPB index?i=ZdVEGcWH0QA:lKZHNm_x5Ac:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments