Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

STIR/SHAKEN is a regulatory framework designed to help combat illegal robocalling. With STIR/SHAKEN, service providers will sign and authenticate phone calls using different Attestation or “trust” levels depending on who the call is coming from. Further information can be found at FCC.Gov/call-authentication.

This is a summary article detailing basic facts about STIR/SHAKEN, and how the framework is implemented on the VI network.

Frequently Asked Questions

What are the different levels of attestation?

  • Full Attestation (Attestation A) - The service provider has confirmed the user that is making the call is authorized to use the calling number.

  • Partial Attestation (Attestation B) - The service provider has authenticated the user but cannot verify that they are authorized to use the calling number. Calls using ANIs (Calling Numbers) that have been purchased from another provider will receive this level of attestation.

  • Gateway Attestation (Attestation C) - The service provider can authenticate the call’s origination but cannot verify the source of the call. 

Since VI has completely implemented STIR/SHAKEN, can I list this status for my own voice network in the FCC’s Robocall Mitigation Database?

For the vast majority of voice service providers, VI’s STIR/SHAKEN implementation status will have no effect on your company’s own status. VI highly recommends seeking consultation from a legal and/or telecom compliance expert to ensure that you are providing your company’s correct status in the Robocall Mitigation Database. Recommendations regarding consultation services can be found in VI’s STIR/SHAKEN Implementation Guide.

I have implemented STIR/SHAKEN on my voice network and provide attestation for my outbound traffic. Is there any further action required in regards to VI?

No, VI will pass your headers without any alterations. No action required.

What steps are required to receive headers on inbound calls?

By default, VI does not send inbound headers since these additional headers can cause fractured packets, and subsequently cause calls to fail if your network and/or firewall is not prepared to receive them.

Service providers that have implemented STIR/SHAKEN can request these headers to be sent by Creating a Support Ticket. Please be ready to include the list of Endpoint Groups that you would like to receive the headers for.

Will VI provide attestation for invalid Caller IDs?

No, outbound calls made from an invalid source number will be rejected with a 503 by VI’s network.

  • No labels