Hey everyone,
Just a quick heads-up for all US providers, resellers, and wholesalers: The FCC’s deadline to implement your own STIR/SHAKEN certificate-based authentication is coming up fast—June 20, 2025.
What does this mean for you?
If you’re running FS PBX, I’ve got some good news: We have a STIR SHAKEN module that lets you sign your calls locally using your own certificate—no need for a hosted solution, SIP redirects, or third-party involvement. It’s private, fast, and rock-solid reliable.
If you need more info or want to see how it works, feel free to reach out. Happy to help!
Just a quick heads-up for all US providers, resellers, and wholesalers: The FCC’s deadline to implement your own STIR/SHAKEN certificate-based authentication is coming up fast—June 20, 2025.
What does this mean for you?
- You’ll need to get your SPC token and obtain your own certificate.
- Make sure your outbound calls are signed with the correct attestation level.
- Don’t forget to update your Robocall Mitigation Plan in the FCC database, specifying whether you’ve fully, partially, or not yet implemented STIR/SHAKEN.
If you’re running FS PBX, I’ve got some good news: We have a STIR SHAKEN module that lets you sign your calls locally using your own certificate—no need for a hosted solution, SIP redirects, or third-party involvement. It’s private, fast, and rock-solid reliable.
If you need more info or want to see how it works, feel free to reach out. Happy to help!