Updated robocall mitigation filing rules
The FCC announced deadlines for compliance with new robocall mitigation rules. The deadlines are fast approaching! This article summarizes the requirements. Let’s have a look.
All providers are required to file certifications and robocall mitigation plans to the Robocall Mitigation Database (RMD). The deadline is February 26, 2024.
This requirement impacts every U.S. provider, including:
- All providers, regardless of whether they are required to implement STIR/SHAKEN,
- Providers that lack control over the network infrastructure necessary to implement STIR/SHAKEN, and
- All intermediate providers.
Existing filers must update their certification and robocall mitigation plan in the RMD by February 26, 2024.
Intermediate providers and voice service providers must refuse to carry traffic from any provider not listed in the RMD by May 28, 2024. This requirement includes traffic from non-gateway intermediate providers.
Robocall Mitigation Database
The online RMD certification form requires additional information. (This is why existing filers are required to update their certification.) The additional information to be collected includes:
- The role(s) the provider plays in the call chain,
- Detailed information about any claimed STIR/SHAKEN implementation extension or exemption,
- Information about principals, affiliates, subsidiaries, and parent companies,
- A statement about whether the filer is subject to official action or investigation due to suspected unlawful robocalling or spoofing,
- The filer’s Operating Company Number (OCN).
Robocall mitigation plan
All providers must submit a robocall mitigation plan with their updated certification by February 26, 2024. Existing filers who provided a plan previously must update and file their robocall mitigation plan by the same date.
As before, these plans must describe the reasonable steps the provider has taken to avoid originating, carrying, or processing illegal robocalls. Gateway providers must also describe their know-their-upstream-provider program.
The new, additional requirements for robocall mitigation plans include the following:
- Voice service providers must describe their affirmative, effective measures to prevent customers from originating illegal robocalls.
- Non-gateway intermediate providers and voice service providers must describe their know-their-upstream-provider program.
- All providers must describe any call analytics systems they use to identify and block illegal robocalls, including whether they use a third-party vendor and the name of the vendor(s).
- All mitigation plans must be provided in PDF.
TransNexus is a leader in developing innovative software to manage and protect telecommunications networks. The company has over 25 years’ experience in providing telecom software solutions including branded calling, toll fraud prevention, robocall mitigation and prevention, TDoS prevention, analytics, routing, billing support, STIR/SHAKEN and SHAKEN certificate services.
Contact us today to learn more.
This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.
TransNexus has a comprehensive suite of robocall mitigation solutions to prevent the origination of unlawful robocalls.Learn more