STIR/SHAKEN call authentication
STIR/SHAKEN compliance, done properly.
Sign, attest and verify every call your network originates or terminates. VoIP Radar delivers STIR/SHAKEN that meets FCC requirements under the TRACED Act — with attestation decisions you can defend.
What you get
A complete STIR/SHAKEN implementation
Signing, verification, attestation logic, certificates and the documentation the FCC expects to see.
A / B / C attestation
Attestation is assigned automatically from customer KYC status and number-ownership records — call by call.
Call signing
Outbound INVITEs signed with your certificate and delivered with a valid Identity header and PASSporT.
Inbound verification
Verify signatures on terminating calls, expose the result to your switch and route, label or block accordingly.
Certificates (SPC / STI-CA)
We guide you through STI-PA registration, your SPC token and certificate issuance with an approved STI-CA — and keep them renewed.
RMD filing support
Plan templates and expert guidance so your Robocall Mitigation Database certification reflects what you actually run.
Non-IP call handling
Support for call authentication across TDM interconnects and legacy trunks that can't carry SIP end to end.
Why it matters
STIR/SHAKEN is table stakes — mitigation is the rest
Under the TRACED Act and FCC rules, voice providers must implement STIR/SHAKEN in the IP portions of their networks (unless covered by a specific exemption or extension) and file a certification in the Robocall Mitigation Database. Providers that are not listed — or are removed — lose the ability to hand traffic to other U.S. carriers, because those carriers are prohibited from accepting it.
Signing alone does not stop fraud: a bad actor with legitimately assigned numbers can still receive full attestation. That is why VoIP Radar pairs STIR/SHAKEN with KYC and real-time fraud scoring. Attestation becomes an active defense — reducing spoofed traffic, protecting your reputation with downstream carriers and keeping answer rates healthy.
Getting live with VoIP Radar
- 01
Eligibility & registration
Confirm your OCN, FCC Form 499 filing and RMD listing, then register with the STI-PA.
- 02
Certificate & keys
Obtain your SPC token and certificate from an approved certification authority.
- 03
Attestation policy
Map customers, number inventories and trunks to the right A / B / C rules.
- 04
Sign & verify
Route calls through VoIP Radar for signing and verification — usually a single SBC routing change.
- 05
Monitor
Track attestation mix, verification failures and downstream labeling from one dashboard.
- 06
Document
Keep your RMD certification and mitigation plan aligned with your live configuration.
STIR/SHAKEN FAQ
Do small providers still have an extension?
Most of the original STIR/SHAKEN extensions have ended, and the FCC has narrowed the circumstances in which providers can rely on others to sign on their behalf. If you are unsure where you stand, we will check your filings and tell you plainly.
Can we use a third party to sign our calls?
Yes, but the FCC now expects providers using a third party to sign with their own SPC token so the attestation is attributable to them. VoIP Radar supports this model.
Does an A attestation mean the call is legal?
No. Attestation describes how well the originating provider knows the caller and their right to the number. It does not say the call is wanted or lawful — which is why mitigation and analytics are still required.
What about calls over TDM?
STIR/SHAKEN was designed for SIP. Calls that cross non-IP segments need additional handling, which the FCC has been pushing providers to address. We can help you plan for it.
Get in touch
Find out where your network stands
Tell us about your switch and traffic. A VoIP Radar engineer will map your STIR/SHAKEN, RMD and fraud exposure and send a written assessment — free, within one business day.
- STIR/SHAKEN & attestation review
- RMD certification gap check
- Fraud & robocall exposure snapshot
- Deployment plan for your SBC / softswitch