← Blog
·2 min readGrowthSmall Providers

Multi-OCN Growth: What Changes When You Add a Second OCN

TL;DR
  • Each OCN needs its own certificate and its own SPC token — there’s no shared certificate across OCNs.
  • Renewal dates will no longer line up neatly once OCNs are added at different times — tracking gets harder without a system.
  • Your Robocall Mitigation Database filing needs to separately and accurately describe every OCN you operate.
  • This is usually the point where a spreadsheet-based tracking approach stops being sufficient.
  • Track every OCN’s certificate and RMD status in one place, and treat recurring renewal-tracking pain as a trigger to evaluate ACME automation.

Adding a second OCN — whether through growth, an acquisition, or a new line of business — changes the shape of your STIR/SHAKEN compliance work in ways that aren't always obvious until you're in the middle of it.

Certificates and Tokens Don't Share Across OCNs

Each OCN requires its own certificate and its own SPC token — there's no way to extend a single certificate to cover multiple OCNs. If you're used to thinking about "your certificate" in the singular, that mental model needs to shift to "your certificates," plural, each with its own lifecycle.

Renewal Dates Stop Lining Up

When you only had one OCN, there was one renewal date to remember. Once a second OCN is added — especially if it's added mid-year rather than at the same time as the first — you now have renewal dates on different schedules. This is exactly the kind of thing that's easy to track informally at first and then quietly becomes unmanageable.

Your RMD Filing Needs to Keep Pace

Your Robocall Mitigation Database filing needs to accurately describe every OCN you operate, not just the one you started with. Adding an OCN without updating your RMD filing to reflect it is a compliance gap that's easy to miss since the filing itself doesn't visibly "break" the way an expired certificate does.

When to Stop Tracking This by Hand

A single OCN is manageable with Telonium's automated expiration reminders alone. Two is usually still fine with a shared spreadsheet. Beyond that — or even at two, if renewal dates are staggered awkwardly — it's worth considering either a dashboard that shows all your OCNs' certificate status in one place, or ACME automation that removes manual renewal tracking from the equation entirely.

Conclusion

Growing to a second OCN is a good moment to get more deliberate about how you track certificates, not just repeat whatever informal process worked when you only had one.

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.