Get ready for the STIR/SHAKEN call authentication mandate

You may have heard the news that the Pallone-Thune TRACED Act has been signed into law. You might have questions about it.

We have collected frequently asked questions and listed them here, along with answers, to help you stay informed and be prepared.

Does the STIR/SHAKEN mandate apply to my company?

If your company provides voice service in the U.S., then yes, it does.

The Pallone-Thune TRACED Act was signed into law on December 30, 2019. Here’s the mandate:

“The Commission shall —

  1. require a provider of voice service to implement the STIR/SHAKEN authentication framework in the internet protocol networks of the provider of voice service; and
  2. require a provider of voice service to take reasonable measures to implement an effective call authentication framework in the non-internet protocol networks of the provider of voice service.”

When’s the deadline?

It has two parts:

  1. Voluntary compliance within 12 months after enactment, or else
  2. An explicit mandate for compliance within 18 months after enactment.

My company doesn’t have SIP interconnects with other providers, and we can’t get them either. Does this excuse us from the mandate?

No, it doesn’t. Part B of the mandate listed above requires voice service providers to implement an effective call authentication framework in non-internet protocol networks too. That includes providers who route calls over TDM networks.

I thought STIR/SHAKEN only works over SIP and doesn’t work over TDM. How can we authenticate calls routed over TDM networks?

Out-of-band STIR/SHAKEN provides a way to send the SHAKEN Identity token separately, across the internet, to the terminating provider. Everything else works the same as typical STIR/SHAKEN.

Get ready for the STIR/SHAKEN call authentication mandate

With out-of-band STIR/SHAKEN, it doesn’t matter how calls are routed. You might need to install a SIP gateway device, but otherwise, there’s no need to change your telecom network unless you want to.

We have added out-of-band STIR/SHAKEN to our software as another option for service providers who need it. Our customers have been using it to authenticate caller ID for months.

Other than complying with this mandate, are there any other benefits to STIR/SHAKEN?

Here are the main benefits of STIR/SHAKEN:

  1. Authenticates caller ID to instill trust that it wasn’t spoofed
  2. Helps with traceback
  3. Makes robocall prevention call analytics more effective
  4. Less churn. You won’t lose subscribers to competitors who offer effective robocall prevention.
  5. Supports Rich Call Data, which lets you put more information about the caller in the SHAKEN Identity token
    • Makes consumers more comfortable answering calls
    • Helps enterprise callers improve call completion—this will be extremely valuable to them.

Where can I find more information?

Here are three ways you can learn more about STIR/SHAKEN and call authentication:

  1. For more information about call authentication benefits, see an article we published in Pipeline magazine, Restoring Telecom Trust. It describes STIR/SHAKEN, call analytics, and Rich Call Data in more detail and explains how they work well together.
  2. Watch our webinar, Get Ready for the STIR/SHAKEN Call Authentication Mandate. This presentation includes testimonials from voice service providers who are using STIR/SHAKEN in their production networks today.
  3. Contact us today to learn how we can help you deploy STIR/SHAKEN in your network quickly and easily.

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.

November 30, 2020

Service providers request SHAKEN extensions

November 20, 2020

FCC SHAKEN Second Report and Order deadlines

November 18, 2020

U.S. STI-GA to update the Service Provider Code token access policy for STIR/SHAKEN

November 3, 2020

Comments on caller ID authentication best practices

November 2, 2020

STIR/SHAKEN, least cost routing and attestation

October 28, 2020

Reply comments on caller ID authentication progress

October 26, 2020

Standards-based STIR/SHAKEN

October 21, 2020

SHAKEN benefits for enterprise callers

October 19, 2020

PASSporTs used with STIR/SHAKEN

October 19, 2020

How to register with the STI Policy Administrator to authenticate calls with STIR/SHAKEN

October 14, 2020

Should US service providers file for the voluntary SHAKEN exemption?

October 14, 2020

International SHAKEN — how that might work

October 7, 2020

Best practices for call authentication – first proposal

October 5, 2020

Three requirements from the FCC SHAKEN orders that will apply to most U.S. providers

September 30, 2020

FCC approves second order on SHAKEN

September 28, 2020

SHAKEN, robocall mitigation, or both?

September 22, 2020

Initial reactions to FCC Second Order on SHAKEN

September 16, 2020

Robocall mitigation program mandate

August 26, 2020

Update to SHAKEN standard improves authentication of forwarded and diverted calls

June 25, 2020

Open source Call Placement Service advances SHAKEN call authentication for all

April 1, 2020

FCC issues STIR/SHAKEN mandate

January 2, 2020

STIR/SHAKEN mandate signed into U. S. law

Out of band STIR/SHAKEN enables call authentication for everyone