Yesterday marked the FCC’s deadline for blocking phone traffic from voice service providers that have not certified that they’ve implemented the STIR/SHAKEN caller ID authentication standards nor filed a robocall mitigation plan with the Commission. Beginning immediately, if a voice service provider’s certification and other required information does not appear in the FCC’s Robocall Mitigation Database, intermediate and voice service carriers will be prohibited from accepting that provider’s traffic.
“The FCC is using every tool we can to combat malicious robocalls and spoofing – from substantial fines on bad actors to policy changes to technical innovations like STIR/SHAKEN,” said FCC Acting Chairwoman Jessica Rosenworcel. The deadline establishes what she calls “a very powerful tool” for blocking unlawful robocalls.
As of 1:30 p.m. EST yesterday, 4,798 companies had filed in the Robocall Mitigation Database. All of the largest phone carriers have certified they’ve implemented STIR/SHAKEN standards on their IP networks. Hundreds of other carriers have also certified to full implementation on their IP networks, according to the agency.
STIR/SHAKEN improves the quality of caller ID information. It helps verify the phone number from which the call was made – or flag that it is not verified. This, in turn, helps blocking services both at the consumer level and before the call reaches the consumer.
In April, the FCC launched the Robocall Mitigation Database in which voice service providers must file certifications to inform the agency of their STIR/SHAKEN implementation status and, in some cases, their robocall mitigation efforts. Hundreds of voice service providers have certified to either full STIR/SHAKEN implementation or full implementation on the IP portions of their networks.
Voice service providers certifying to anything short of full STIR/SHAKEN implementation must describe the robocall mitigation steps they are taking to ensure they are not the source of illegal robocalls. All voice service providers must also submit identifying business information and the name and contact information for a person within the company responsible for addressing robocall mitigation-related issues. If a voice service provider does not file in the database, as of now, intermediate providers and other voice service providers must block the noncompliant provider’s calls.
Reader Interactions