This means calls traveling through interconnected phone networks would have their caller ID "signed" as legitimate by originating carriers and validated by other carriers before reaching consumers. STIR/SHAKEN digitally validates the handoff of phone calls passing through the complex web of networks, allowing the phone company of the consumer receiving the call to verify a call is in fact from the number displayed on Caller ID.
See more information by the FCC on call authentication.
FCC Wireline Competition Bureau announced voice service providers are required to file certifications of their implementation of the STIR/SHAKEN caller ID authentication framework by the June 30, 2021 deadline for the Robocall Mitigation Database submission. Inteliquent is currently signing all outbound calls for customers using hosted unified communications and SIP Trunking services on our UC platforms.
See more FCC timeline information.
STIR/SHAKEN certification and Robocall Mitigation Program requirements are not applicable to Inteliquent UC retail customers that are consuming Unified Communications and SIP Trunking services as an end user.
The FCC requires all voice service providers to certify their traffic is either fully, partially or not yet signed with STIR/SHAKEN. All certifications must be signed by an officer in conformity with FCC Rule 1.16.
For voice service providers certifying “some or all” of the calls they originate, they are subject to a Robocall Mitigation Plan (RMP). Such providers must submit additional information with their certifications including the type of extension or extensions received under the FCC rules, specific reasonable steps taken under an RMP to avoid originating illegal robocalls, and a commitment to respond to traceback requests and to cooperate with investigating and stopping illegal robocalls.
See the full FCC filing instructions.
See the Inteliquent UC STIR/SHAKEN release notes.
As part of STIR/SHAKEN compliance, Inteliquent signs and provides attestation for outbound retail call services. No changes are required by Inteliquent retail customers as this is an inter-carrier connection.
Inteliquent is providing signed authentication, where calls are signed using our keypair and certificate. No network changes are required on any customer equipment. STIR/SHAKEN signing was validated in a lab environment before being deployed to production.
As a Inteliquent UC platform end user, STIR/SHAKEN support is included at no charge.
For inbound calls, we have enabled enhanced CNAM. Enhanced CNAM will provide a pre-pended “v” on Caller ID Display where an inbound call has passed STIR/SHAKEN validation.
Unfortunately, no. A validated call (TN-Validation-Passed, indicated to an end user by the pre-pended “v” in Caller ID Display) simply means the call was signed and an attestation provided by the originating service provider, and the authentication header was validated by the terminating service provider. STIR/SHAKEN by itself does not guarantee legitimacy of a caller, it makes it easier to trace and shut down abuse. The lack of validation also can not be used to assume a call is not legitimate, spoofed, or a robocall as STIR/SHAKEN capabilities are not available across 100% of the PSTN (most notably, calls originated from carriers that are still relying on TDM interconnection).
Again, unfortunately no. STIR/SHAKEN digitally validates the handoff of phone calls passing through the complex web of networks, allowing the phone company of the consumer receiving the call to verify a call is in fact from the number displayed on Caller ID. Thus, STIR/SHAKEN provides a verified originating service provider to identify where the call originated so if there is an issue with robocalling or fraud, the call can be traced, and the issue can be addressed with the originating service provider. The FCC order on participation in the Robocalling Mitigation Database provides a framework for handling the response, ensuring the originating carrier has contacts and is committed to participation in addressing robocall and fraud mitigation.
Equally important as the June 30, 2021 deadline for database submission, intermediate providers and terminating voice service providers will be prohibited from accepting traffic from voice service providers not listed in the Robocall Mitigation Database as of September 28, 2021.