NG911 Compliance for Legacy Switches, Without a Forklift Upgrade
The FCC’s Next Generation 911 (NG911) mandate requires carriers to deliver 911 traffic in IP over a modern emergency network. Most of the switches carrying that traffic today are legacy TDM. A TelcoBridges Tmedia gateway drops in beside your existing switch and IP-enables it, so you meet the mandate in weeks instead of replacing the switch, and get a versatile media gateway you keep using long after 911 is handled, including after the switch itself is eventually replaced.
State 911 Requests Are Triggering Strict Compliance Timelines
In July 2024 the FCC adopted its Next Generation 911 Report and Order (FCC 24-78), and the rules took effect in November 2024. They put the obligation to modernize 911 delivery squarely on Originating Service Providers. The transition happens in two phases, and each phase’s clock starts when a state or local 911 Authority sends a valid request.
Phase 1 requires the provider to deliver 911 traffic in IP-based SIP format to the NG911 delivery points the 911 Authority designates, and to complete connectivity testing.
Phase 2 requires that SIP delivery to carry location embedded in the call itself, using a PIDF-LO location object rather than a legacy database lookup. Large providers get six months per phase after a valid request; rural and smaller providers get twelve. The practical message is the same for everyone: once your 911 Authority requests it, the countdown is short, and a legacy TDM switch cannot answer it on its own.
Most of the country has not finished the transition
For providers operating TDM switches, preparing a compliance strategy before a formal request arrives is essential. Maintaining dual legacy and IP 911 workflows increases operational complexity and costs over time, making an overlay gateway the most efficient way to bridge the gap quickly.
Why a legacy switch cannot reach
an NG911 network on its own
Legacy 911 and NG911 do not speak the same language at any layer. A legacy switch hands a 911 call to a selective router over CAMA trunks, passes the calling number as MF or SS7 signaling, and relies on a separate ALI database dip to attach the caller’s location. NG911 replaces all of that with an ESInet, an IP network on which every 911 call is signaled in SIP, media travels as RTP, and location rides inside the call as a PIDF-LO object routed by the ECRF using the LoST protocol.
Because the mismatch is at the signaling layer, the media layer, and the location layer at once, a copper-and-TDM switch cannot connect to an ESInet directly. Something has to sit between them and translate. The NENA i3 standard that defines NG911 anticipates exactly this and specifies a transitional element for it: the Legacy Network Gateway, which converts a legacy originating network’s TDM, SS7, and CAMA signaling into SIP so the call can enter the IP ESInet. The FCC’s own rules name this path directly, telling providers they may meet the mandate using a Legacy Network Gateway or its functional equivalent rather than replacing the switch.
How a Tmedia gateway makes a legacy switch NG911-ready
A TelcoBridges Tmedia gateway is that Legacy Network Gateway function in a carrier-grade box. You deploy it beside the switch you already run, and it immediately IP-enables that switch for 911.
- The Tmedia gateway terminates the switch’s TDM side over T1/E1, ISDN PRI, SS7, or CAMA trunks, the same interfaces the switch already uses for 911.
- It converts that signaling into SIP and packetizes the voice into RTP, presenting a clean IP interface toward the ESInet.
- It hands the call to the NG911 delivery points your 911 Authority designated, in the SIP format Phase 1 requires.
- The switch stays in place and keeps doing its job. Nothing is ripped out, and the subscriber base is untouched.
Carrier-grade, purpose-built
Tmedia gateways are built for exactly this kind of TDM-to-IP conversion, with support for SS7 ISUP, ISDN PRI, CAS, and H.248, and 99.999% availability with redundant power. This is the same platform TelcoBridges has deployed for TDM-to-IP modernization for years.
Sized to your switch
The family scales from the 1U TMG800 for a single site to the TMG3200 workhorse and the TMG7800, which reaches tens of thousands of channels. You match the gateway to the switch rather than over-buying.
A proven deployment model
Dropping a gateway beside a legacy switch to IP-enable it is not a workaround; it is how carriers have modernized central offices with TelcoBridges for years, including full TDM-to-IP transformations completed with zero customer disruption.
Gateway beside the switch vs. replacing the switch
Both paths can get you to NG911. They are not close on time, cost, or risk.
| Tmedia gateway beside the switch | Full switch replacement | |
|---|---|---|
| The switch | Stays in place and keeps running | Removed and replaced |
| What changes | A gateway is added beside it to IP-enable 911 | Core call processing is re-platformed |
| Subscriber impact | None; subscribers are untouched | Migration and cutover risk for every subscriber |
| Timeline | Weeks, to meet a request-driven deadline | A multi-year procurement and migration |
| Standards fit | The i3 and FCC-sanctioned Legacy Network Gateway path | A larger project than the 911 mandate itself requires |
| Afterward | You keep a versatile media gateway for other traffic, and it stays on as the local gateway when the switch is eventually replaced | Scope and spend tied to the switch platform |
The gateway path is the one the standards were written to support. It is why the FCC points providers at the Legacy Network Gateway rather than at a rip-and-replace.
Built for Compliance, Ready for Core Network Traffic
While NG911 compliance meets your immediate deadline, a Tmedia gateway provides immediate versatility across your core network. Once deployed, expanding its role to support SIP trunking, PSTN interconnect, SS7-to-SIGTRAN bridging, or lawful intercept is simply a matter of configuration.
Your investment also remains fully protected when you eventually retire your legacy Class 5 switch. When migrating to a softswitch or IMS core, the same Tmedia gateway stays in service to handle remaining TDM, PRI, and interconnect trunks. Switches are eventually replaced, but your Tmedia gateway carries your network through every stage of the transition.
Tailored for Operators Navigating the NG911 Transition
ILECs and rural carriers
Providers still running Class 5 and other legacy TDM switches, facing an NG911 request from a state or local 911 Authority and a copper-retirement clock at the same time.
CLECs and regional operators
Operators who need to deliver 911 in SIP to an ESInet without re-platforming a switch that still serves their subscribers well.
Carriers modernizing anyway
Providers already planning a TDM-to-IP move who want NG911 compliance now, a gateway that supports the rest of the transition next, and the same unit still in service in front of the new core once the legacy switch is gone.
Frequently Asked Questions
What is NG911?
NG911, or Next Generation 911, is the IP-based replacement for the legacy circuit-switched 911 system. Instead of routing 911 calls through selective routers over TDM trunks with location pulled from a separate ALI database, NG911 carries every 911 call as SIP over an Emergency Services IP network (ESInet), with the caller’s location embedded in the call. It also makes text, photos, and video to 911 possible, which the legacy system could not support.
NG911 vs E911: what is the difference?
E911 (Enhanced 911) is the legacy system: a 911 call travels over TDM trunks to a selective router, and the caller’s location is retrieved from an ALI database keyed to the calling number. NG911 is the IP-based successor: the call is signaled in SIP across an ESInet and the location travels inside the call as a PIDF-LO object. Put simply, in NG911 vs E911 the difference is that E911 is circuit-switched and database-driven, while NG911 is IP-native and carries location with the call.
Does NG911 compliance mean I have to replace my switch?
No. The FCC’s NG911 rules let a provider meet the mandate using a Legacy Network Gateway or its functional equivalent, which converts a legacy switch’s TDM 911 traffic into SIP for the ESInet. A TelcoBridges Tmedia gateway deployed beside your existing switch performs that function, so you can comply without a switch replacement.
What are the NG911 compliance deadlines?
Under FCC 24-78, deadlines are triggered when a state or local 911 Authority sends a valid request. Large providers then have six months to complete Phase 1 (SIP delivery of 911 traffic) and six months for Phase 2 (SIP with embedded PIDF-LO location); rural and smaller providers get twelve months per phase. Because the clock starts on the 911 Authority’s request, the time to prepare is before the request arrives, not after.
What NG911 solutions does TelcoBridges offer?
TelcoBridges provides Tmedia media gateways that act as the Legacy Network Gateway function for NG911: deployed beside a legacy TDM switch, they convert its TDM, SS7, PRI, and CAMA 911 traffic into SIP for the ESInet. The family scales from the TMG800 to the TMG7800, runs at 99.999% availability, and can carry other TDM-to-IP traffic once 911 is handled.
What happens to the gateway when we do replace the Class 5 switch?
It stays in the network. A Tmedia gateway is not tied to the switch it was bought to IP-enable, so when you re-platform onto a softswitch or IMS core the same unit goes on serving as the local gateway in front of that core, terminating the TDM that is still there: PRI and T1 business lines, SS7 interconnect, and any trunks not yet converted. Meeting the NG911 deadline with a gateway does not create an investment you write off the day the legacy switch is retired.
How long does a Tmedia NG911 deployment take?
Because the gateway is added beside the switch rather than replacing it, deployment is measured in weeks, not the multi-year timeline of a switch replacement. That is what makes it a practical answer to the short, request-driven deadlines in the FCC rules. TelcoBridges works with you to size, configure, and test the gateway against the NG911 delivery points your 911 Authority designates.
Make your legacy switch NG911-ready
Connect with our NG911 team to deploy a Tmedia gateway alongside your existing switch, meeting the FCC mandate on time—without a costly core replacement.
Learn how a single deployment secures immediate compliance while paving the way for your broader TDM-to-IP network transformation. Explore the Tmedia gateway family or learn what a media gateway can do for your network.
Sources
- National 911 Program, National 911 Annual Report: 2021 Data (published Feb 21, 2023), NG911 maturity levels, as compiled in Congressional Research Service report R48015 (Apr 5, 2024): 7 of 45 reporting states/territories at “jurisdictional end.” Reporting is voluntary; 2021 is the most recent federal state-by-state maturity data. congress.gov
- NTIA, Next Generation 9-1-1 (NG911) Cost Study (Apr 29, 2026): remaining nationwide transition cost estimated at $5.8B–$9.27B over about seven years. ntia.gov
- FCC, Seventeenth Annual 911 Fee Report (2024 data, released Feb 13, 2026): 212,910,794 voice 911 calls in 2024. fcc.gov
- FCC 24-78, Facilitating Implementation of Next Generation 911 Services (adopted Jul 18, 2024; effective Nov 25, 2024), 47 CFR Part 9 Subpart J. Two-phase OSP obligations, request-driven 6/12-month deadlines, Legacy Network Gateway path. ecfr.gov
- NENA i3 Standard for NG9-1-1 (NENA-STA-010.3b-2021): ESInet, SIP, PIDF-LO/ECRF/LoST, and the Legacy Network Gateway transitional element. nena.org