STIR/SHAKEN Deadline: What Service Providers Need to Know
June 8, 2021
Service Providers Need to Implement STIR/SHAKEN Before June 30, 2021 Deadline
Beginning July 1, 2021, the Federal Communications Commission (FCC) requires all service providers to take certain steps to combat illegal robocalling. These requirements are set forth in different orders and laws, including the Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act.
The most notable obligation imposed upon service providers is the requirement to implement STIR/SHAKEN call authentication for the Internet Protocol (IP) portion of their networks and have a robocall mitigation plan in place for all phone calls for which it has not implemented STIR/SHAKEN (including calls sent using Time Division Multiplexing (TDM)).
What Obligations Must Service Providers Meet to Be Compliant?
Inteliquent is unable to provide you with legal advice, however, our team thought it would be helpful to summarize the FCC’s pronouncements with respect to your obligations under the various rules and orders:
- All service providers must have an FCC Registration Number (FRN), identification information for their company and a specific person named as a point of contact.
- You must commit to cooperating with the Commission, law enforcement and industry traceback group in investigating and stopping illegal robocalling.
- All service providers are mandated to register in the FCC’s Robocall Mitigation Database (RMD) by June 30, 2021.
- You must have either implemented STIR/SHAKEN or certify in the RMD you have implemented an alternate robocall mitigation plan.
- The FCC has not defined the specific robocall mitigation plans needing to be implemented, but a range of viable solutions may include, but are not limited to:
- Provide verified caller ID information to end-users
- Use call analytics to provide call treatment
- Implement a system from a vendor providing call monitoring and management
- Implement a strict “Know Your Customer” program to ensure bad actors are not sending calls
- Traffic from service providers who have not registered in the RMD as of September 28, 2021, must be blocked by all intermediate and terminating providers.
You must be prepared to not accept calls from other service providers who are not registered in the RDM as of September 28, 2021.
How Will Inteliquent Support STIR/SHAKEN Requirements?
On or before June 30, 2021, Inteliquent will implement STIR/SHAKEN and pass unaltered authentication information contained in the headers of calls using North American Numbering Plan Administration (NANPA) numbers.
Calls that do not contain authentication information will either be authenticated by Inteliquent at the appropriate attestation level or will be passed on as “unsigned” to the downstream provider. Unauthenticated calls are expected to be completed but may be labeled in a manner that is less likely to be answered by the recipient.
Inteliquent recommends all service providers authenticate calls, if possible, even if such providers have been granted extensions that do not currently obligate them to do so.
Are Service Providers Eligible for FCC Extensions?
As a solution for non-IP calls has not yet been approved, therefore, such calls are not subject to STIR/SHAKEN certification at this time. However, service providers are still required to register with the RMD. As part of the registration process, you must implement a robocall mitigation plan to combat the origination of illegal robocalls.
Providers with less than 100,000 voice service subscriber lines, qualify for a two-year extension, but still must register with the RMD and implement a robocall mitigation program to combat the origination of illegal robocalls during the extension period.
Where Can I Find Out More about the FCC’s STIR/SHAKEN Requirements for Service Providers?
In addition to the following resources, we recommend you discuss the rules with U.S. telecommunications regulatory counsel to ensure no interruption in service.
- FCC STIR/SHAKEN Information
- Robocall Mitigation Database Registration Notice
- Robocall Mitigation Database Registration Instructions