← Blog
·1 min readComplianceChecklist

A 2026 STIR/SHAKEN Compliance Checklist for Small Voice Service Providers

TL;DR
  • A new year is a good forcing function to confirm every OCN you operate has an active, correctly-scoped certificate.
  • Documentation habits built now — who requested what, and when — pay off if compliance history is ever questioned later.
  • Signing coverage should be re-verified, not assumed — confirm every outbound trunk is actually using your certificate, not just the one you tested originally.
  • This is also a good time to reconsider whether your current certificate authority and workflow still fit your current scale.
  • List every OCN’s certificate status, verify every trunk is actually signing, re-check your RMD filing, and reassess whether your current CA still fits your scale.

January is as good a time as any to step back from the week-to-week and confirm STIR/SHAKEN compliance is still solid across your whole operation, not just the piece that happens to be top of mind.

Every OCN, Covered

If you operate more than one OCN, it's worth explicitly listing each one and confirming it has its own active, correctly scoped certificate. It's easy for a newly added OCN to slip through without the same certificate process the original one went through.

Signing Coverage, Verified Not Assumed

A certificate existing in your dashboard doesn't guarantee every outbound call is actually signed with it. Confirm every SIP trunk, SBC, or signing path you operate is actually sending signed Identity headers — not just the one path you tested when you first set things up.

Documentation That Would Hold Up

Keep a simple, dated record of certificate requests, renewals, and any SPC token changes. This doesn't need to be elaborate — a shared document with dates and brief notes is enough to answer questions quickly if your compliance history is ever reviewed.

Does Your Setup Still Fit?

A new year is also a reasonable moment to ask whether your current certificate authority, pricing, and workflow still make sense. If you've grown from one OCN to several, or started wanting ACME automation you didn't need before, it may be worth re-evaluating rather than assuming your original setup is still the best fit.

Conclusion

None of this is complicated, but all of it is easy to let slide during a busy year. A short checklist at the start of the year keeps small gaps from becoming real problems later.

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.