BRIGHTLINK STIR/SHAKEN

Frequently Asked Questions

Industry Background

With the rise of mobile phone usage in the US over the past five years, consumers have seen a sharp rise in robo and spam calls as well. According to call protection company First Orion, nearly 50% of all calls made to cell phones in the U.S. will be spam calls, with over 90% displaying familiar caller IDs.  Unwanted calls are the FCC’s number one consumer complaint and they have taken action – requiring all IP-based service providers to comply with STIR/SHAKEN protocols before the end of 2019.

STIR/SHAKEN FAQs

What is STIR/SHAKEN?

STIR (Secure Telephone Identity Revisited) and SHAKEN (Secure Handling of Asserted information using toKENs) are new telecommunications industry standards that help filter spam and robocalls.  STIR is the set of industry technical standards to certify the identity of a call and SHAKEN determines how authentication of call identification is then handled by providers.

How does STIR/SHAKEN work?

For Consumers: STIR/SHAKEN will verify that the person calling you is legitimate and calling you from the number displayed on your screen. While this verification does not stop robocalls from coming to your phone, it gives you more information before you answer the phone.

For Communications Providers & Enteprises: STIR/SHAKEN utilizes a trusted digital certificate infrastructure to ensure originating call data integrity. IP signaling will now include SIP Identity headers that include an attestation field that contains a confidence indicator letting the recipient of the call know if the call initiator owns, or has the right to, the number they’re calling from.

There are three levels of attestation the originating service provider can give:

 

      1. Full (A) – The service provider has authenticated the caller and that caller is authorized to use that number.
      2. Partial (B) – The service provider has authenticated the caller but cannot verify their number authorization.
      3. Gateway (C) – The service provider has authenticated where it received the call, but cannot verify the call source (i.e. this call is from Greenland, but the service provider does not know the general identity of the customer originating the call).

What is Brightlink doing to implement STIR/SHAKEN?

Our engineers have already implemented the necessary network modifications required for STIR/SHAKEN compliance.

When will Brightlink implement STIR/SHAKEN?

We are already implementing this with our customers and communications service provider partners.

For more information, please visit the FCC’s website.