NG9-1-1 for Small and Rural Carriers: Why 12 Months Go Faster Than You Think

When the FCC adopted Order 24-78, it gave non-nationwide originating service providers (OSPs) a 12-month window to comply with NG9-1-1 service requests. For smaller and rural carriers already stretched thin, that may have sounded like a reasonable runway. But compliance with FCC 24-78 isn't a single task. It's a sequence of interconnected steps, each with its own dependencies. And the clock doesn't start when you decide to act. It starts the moment a 9-1-1 Authority submits a valid service request.

If you haven't started planning yet, this post is for you. We'll walk through what NG9-1-1 compliance actually involves, where the time goes, and how carriers can get ahead of the curve.

First, A Quick Recap: What FCC 24-78 Requires

Under FCC 24-78, OSPs (including non-nationwide wireless carriers and wireline/CLEC providers) must be capable of delivering 9-1-1 traffic to PSAPs in an IP-based format. The order defines two phases:

• Phase 1: Deliver 9-1-1 traffic using SIP (Session Initiation Protocol) as specified by the local 9-1-1 Authority.

• Phase 2: Deliver 9-1-1 traffic in a fully NG9-1-1-compliant i3 format meeting NENA standards.

For each phase, non-nationwide OSPs have 12 months from the receipt of a valid service request to comply. That 12-month window applies per phase, meaning compliance is a two-phase, multi-year journey, and each phase requires its own technical and operational preparation.

It's also worth noting: service requests won’t necessarily be sent directly to you. Many 9-1-1 Authorities are filing requests through the FCC's Electronic Comment Filing System (ECFS). If you're not monitoring the docket regularly, a compliance clock could already be running without your knowledge.

While some requests are filed on a local or regional basis, other requests are coming from the state level, with both Kansas and North Carolina filing statewide Phase 1 requests at the time of this publication.

You should also be aware that some 9-1-1 Authorities have bypassed Phase 1 entirely, submitting valid Phase 2 requests, which truncates the deadline to just one year to comply. Both Massachusetts and Illinois have filed valid statewide Phase 2 requests.

You can find the docket here, but you can also reach out to our team to learn more about the status in areas you serve. Our team tracks RFSs across the nation, monitors Phase 1 and 2 readiness, and works to interoperate with all ESInet providers behind the scenes to ensure a seamless rollout.

Where the 12 Months Actually Go

Twelve months sounds like a lot of time, but here's what that timeline can look like in practice for a non-nationwide carrier:

When you map it out this way, 12 months doesn't feel so generous. And that's before accounting for the realities that many smaller and rural carriers face every day.

The Real Challenges Smaller and Rural Carriers Face

Nationwide carriers have dedicated compliance teams, established vendor relationships, and internal engineering resources specifically scoped for projects like this. Most non-nationwide carriers don't. That gap matters enormously when a regulatory clock is running.

Here are some of the most common challenges we hear from smaller and rural carriers:

• Limited internal engineering resources. SIP interconnection and i3 implementation require specialized technical expertise. For a carrier with a lean IT or network team, this work often competes directly with keeping day-to-day operations running.

• Procurement and contracting timelines. If your organization requires formal vendor evaluation processes, budget approvals, or board-level sign-off on significant contracts, that process alone can consume two to three months.

• Geographic complexity. Rural carriers often serve multiple counties, jurisdictions, and PSAPs, sometimes across state lines. Each PSAP has its own readiness status and interconnection requirements, multiplying the coordination effort.

• Lack of a dedicated compliance function. Monitoring the FCC docket, tracking PSAP service request status, managing certificates, and maintaining audit trails often falls to staff who are also handling many other responsibilities.

• Tribal and sovereign nation considerations. For carriers serving tribal lands, there may be additional coordination requirements with tribal governments, unique jurisdictional factors, and 9-1-1 infrastructure that is still in transition.

None of these challenges are insurmountable. However, it does mean that 12 months, while technically sufficient, requires a clear plan and, ideally, a head start.

Three Things You Can Do Right Now

Whether you've already received a service request or you're anticipating one, here are the most impactful steps you can take today:

1. Start monitoring the FCC docket. Not all service requests are delivered directly to OSPs. In fact, many 9-1-1 Authorities are filing via the FCC's ECFS system under the previously mentioned docket. If a request has been filed and you're not aware of it, your compliance window may already be running.

2. Audit your current 9-1-1 infrastructure. Before you can plan for compliance, you need a clear picture of where you stand today. That means understanding your current call routing paths, the PSAP readiness levels across your service area, and where the technical gaps exist between your current infrastructure and Phase 1 SIP requirements.

3. Evaluate whether an in-house or managed approach is right for you. Building NG9-1-1 compliance capabilities in-house is possible, but for most non-nationwide carriers, it represents a significant and ongoing operational investment. This is especially true when it comes to records management during both phases of the transition, as significant database changes are required to meet the IP and i3 formatting requirements. A managed solution can compress the implementation timeline, reduce internal resource requirements, and shift the ongoing operational burden (certificate management, records management, PSAP status tracking, ESInet interoperability testing, format delivery, etc.) to a dedicated team of experts.

What to Look for in a NG9-1-1 Compliance Partner 

If you're evaluating outside partners to help manage NG9-1-1 compliance, here are the capabilities that matter most for non-nationwide carriers:

• Proven ESInet interconnection experience: this includes established relationships with state ESInet operators and deep familiarity with local PSAP readiness variations

• Full PSAP status management: the ability to track every PSAP in your service area, determine the required delivery format (TDM, SIP, or i3), and route traffic accordingly

• Certificate and compliance management: handling the ongoing operational requirements so your team doesn't have to

• Records management: offload internal management of 9-1-1 records during both phases of the transition to meet new IP and i3 formatting requirements

• Interoperability testing support: end-to-end testing with PSAPs and ESInet operators as part of the implementation process

• Scalability: a solution that can handle both Phase 1 and Phase 2 requirements without requiring a full re-implementation

At Intrado, we've built NG Nexus specifically to address the complexity of compliance for OSPs of all sizes. It's a fully managed, hosted solution that handles the full lifecycle of NG9-1-1 compliance, from initial PSAP status tracking through interoperability testing and ongoing delivery management. For carriers that don't have the resources to build this capability in-house, it's designed to make compliance manageable without the operational overhead.

The Bottom Line

The 12-month window for non-nationwide carriers isn't a gift of extra time; it's a realistic estimate of how long a well-executed compliance process takes. For smaller and rural carriers working with lean teams and complex service territories, it's a timeline that requires early action.

The carriers that will navigate this transition most successfully are the ones that start now: monitoring for service requests, assessing their current infrastructure, and putting a compliance plan in place before the clock starts running.

If you’d like to learn more, be sure to tune in to our webinar, “NG9-1-1 Conversations, Part 2: What OSPs Need to Know,” an ongoing discussion among experts that covers the ins and outs of compliance with FCC 24-78.

And if you'd like to talk through where your organization stands and what a path to compliance might look like, our team is here to help.

Additional Resources 

FAQs: A Quick Guide to FCC 24-78 and NG9-1-1 Compliance for OSPs