STIR and SHAKEN Overview
Your Guide to Everything STIR and SHAKEN
STIR (Secure Telephony Identity Revisited) and SHAKEN (Secure Handling of Asserted information using toKENs) are the frameworks that promise to prevent the completion of illegally spoofed calls.
Overview
STIR and SHAKEN use digital certificates, based on common public key cryptography techniques, to ensure the calling number of a telephone call is secure. Each telephone service provider obtains their digital certificate from a certificate authority who is a trusted authority. The certificate technology enables the called party to verify that the calling number is accurate and has not been spoofed.
SHAKEN Work Flow

- A SIP INVITE is received by the originating telephone service provider.
- The originating telephone service provider checks the call source and calling number to determine how to attest for the validity of the calling number.
- Full Attestation - The service provider has authenticated the calling party and attest that they are authorized to the use the calling number. An example of this case is a subscriber registered with the originating telephone service provider’s softswitch.
- Partial Attestation - The service provider has authenticated the call origination but cannot verify the call source is authorized to use the calling number. An example of this use case is a telephone number behind an enterprise PBX.
- Gateway Attestation - The service provider has authenticated from where it received the call but cannot authenticate the call source. An example of this case would be a call received from an international gateway.
- The originating telephone service provider uses the authentication service to create a SIP identity header. The authentication service could be a third party service hosted in the cloud, or a software application integrated with the telephone service provider’s Session Border Controller (SBC) or a softswitch. The SIP identity header contains the following encrypted data:
- Calling number
- Called number
- Date and time
- Attestation
- Unique originating identifier
Webinar: How to Implement SHAKEN
February 19, 2019, 11:00 a.m. EST
- The SIP INVITE with the SIP identity header is sent to the terminating telephone service provider.
- The SIP INVITE with identity header is passed to the verification service.
- The verification service obtains the digital certificate of the originating telephone service provider from the public certificate repository. The two step process of verification commences. Verification is a two-step process. First, the SIP Identity header is base-64 decoded and the details are compared to the SIP INVITE message. If they match, the next step is to use the public key of the certificate to verify the SIP identity header signature. If both verification steps are successful, then the calling number has not been spoofed.
- The verification service returns the results to the terminating service provider’s softswitch or SBC.
- The call is completed to the called party.
For more information on STIR/SHAKEN, see our Understanding STIR/SHAKEN whitepaper.
Contact us today to learn more about STIR and SHAKEN.
More on TransNexus.com
February 14, 2019
FCC issues Report on Robocalls
February 4, 2019
Stopping Bad Robocalls Act reintroduced into the House of Representatives
January 31, 2019
STI-GA director Struthers comments on the STI-PA timeline
January 11, 2019
T-Mobile launches caller verification with SHAKEN/STIR
January 7, 2019
FCC proposed rulemaking to implement anti-spoofing provisions in RAY BAUM’s Act
December 10, 2018
Providers respond to Pai’s call to implement SHAKEN without delay
November 16, 2018
New bill to mandate SHAKEN introduced in the U.S. Senate
November 6, 2018
FCC chairman asks telecom carriers to implement SHAKEN without delay
TransNexus has developed a comprehensive workshop to help you understand the business and technical issues that would come into play while deploying SHAKEN in your company.
We can help you get ready for SHAKEN with specific strategies tailored to your network and call scenarios.
Learn more