FCC SHAKEN Second Report and Order deadlines

The FCC Second Report and Order was published in the Federal Register today, which sets its effective date, at which point it will be written into the rules, at December 17, 2020. These rules contain several deadline dates. Here’s a quick overview.

Second Report and Order key points

The Commission adopted their Second Report and Order for the Call Authentication Trust Anchor on September 29, 2020. Here are the key points in the Second Report and Order:

  1. Service providers originating calls with NANP calling numbers must do either STIR/SHAKEN or robocall mitigation (if they qualify for an extension) on every call they originate with a NANP calling number.
    • Many OSPs will do SHAKEN on some calls, robocall mitigation on others.
  2. Every service provider that originates or transports calls with NANP calling numbers must file a certification with the FCC explaining how they use SHAKEN and/or robocall mitigation. This certification filing will be publicly accessible in a Robocall Mitigation Database.
  3. Every service provider must refuse to transit or terminate calls from upstream providers that do not have a certification on file.

Deadline dates

Since the Second Report and Order was published in the Federal Register on November 17, 2020, it will take effect on December 17, 2020. However, this effective date does not change the deadlines in the order itself; December 17 is when the new requirements are written into the rules.

Here are the deadline dates that appear within the rules:

June 30, 2021

  • Voice service providers shall
    • Fully implement STIR/SHAKEN in their IP networks.
      • Those who are eligible for an exemption will use a robocall mitigation program on calls they originate.
    • File a certification with the FCC in a new portal for the Robocall Mitigation Database.
      • In this certification, each service provider shall explain how they use STIR/SHAKEN and/or robocall mitigation to prevent the origination of illegal robocalls on their network.
  • Intermediate providers shall
    • Pass unaltered to the subsequent provider in the call path any authenticated caller identification information it receives with a SIP call
    • Authenticate unsigned calls. This requirement is excused if the intermediate provider cooperatively participates with the industry traceback consortium.
  • Providers with non-IP networks shall provide documented proof that they are participating, either on their own or through representatives, as members of groups working to develop a non-IP caller ID authentication solution.

September 28, 2021

  • Intermediate and terminating voice service providers shall not accept calls from an upstream provider that does not have a certification on file in the Robocall Mitigation Database.

June 30, 2021

  • Voice service providers must have filed for a Section 214 discontinuance in order to receive the exemption for STIR/SHAKEN processing on services scheduled for such discontinuance.

June 30, 2022

  • Voice service providers discontinuing services under Section 214 must have discontinued the service.

June 30, 2023

  • The exemption for small voice service providers with 100,000 or fewer voice subscriber lines ends. Such providers must begin STIR/SHAKEN call authentication.

TransNexus solutions

We offer STIR/SHAKEN and robocall prevention solutions in our ClearIP and NexOSS software platforms.

In addition, we help service providers with all aspects of STIR/SHAKEN deployment, including registering with the Policy Administrator and filing their certification with the FCC.

Contact us today to learn more.

Request info about our products and services

* required

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.