← Blog
·2 min readComplianceChecklist

After the June 20 Deadline: A Compliance Catch-Up Checklist for Small Providers

TL;DR
  • Missing a compliance deadline is solvable, not terminal — the priority is closing the gap quickly, in order.
  • Confirm your OCN and SPC token first, then request a certificate from an approved STI-CA — most issue within a business day.
  • Actually deploy signing and confirm outbound calls carry a signed Identity header, not just that a certificate exists.
  • Update your Robocall Mitigation Database filing once signing is live, so it reflects reality.
  • Keep a simple log of dates and actions taken, in case your compliance timeline is ever questioned.

The FCC's STIR/SHAKEN deadline has passed. If your organization is still catching up, the good news is that implementation is a well-trodden path at this point — there's no need to reinvent anything, just work through it in order.

Step One: Confirm Your OCN and SPC Token

Everything downstream depends on having an OCN assigned to your company and a valid SPC token from iConectiv. If you don't have these yet, this is where to start — a certificate request can't proceed without them.

Step Two: Request a Certificate

Once your SPC token is in hand, request a certificate from an approved STI-CA, such as Telonium. Issuance timelines vary by provider, but many issue within a single business day once the token checks out, so this step shouldn't be the bottleneck it might have been during the original deadline crunch.

Step Three: Actually Deploy Signing

A certificate alone doesn't authenticate calls — it has to be deployed on your signing infrastructure, whether that's your own SBC configuration or a hosted signing service. Confirm that outbound calls are actually carrying a signed Identity header, not just that a certificate exists in a dashboard somewhere.

Step Four: Update Your Robocall Mitigation Database Filing

The Robocall Mitigation Database is a self-certification — it needs to reflect what's actually true about your network. Once signing is live, update your filing. An outdated RMD entry claiming a robocall mitigation program when you've since implemented real STIR/SHAKEN signing (or vice versa) is its own compliance gap.

Step Five: Document As You Go

Keep a simple record of when you obtained your SPC token, when your certificate was issued, and when signing went live. This costs nothing to maintain and is the kind of thing you'll be glad to have if your compliance timeline is ever questioned later.

Conclusion

Catching up on STIR/SHAKEN after a missed deadline is a checklist, not a crisis — OCN and SPC token, certificate, deployed signing, an updated RMD filing, and a paper trail. None of it is complicated; it just needs to happen in order.

This article is provided for general informational purposes only and does not constitute legal or compliance advice. Consult a qualified attorney or compliance professional about your organization’s specific obligations under FCC rules and the STIR/SHAKEN framework.

Need a STIR/SHAKEN certificate?

Telonium is an approved STI-CA — request your first certificate today.