Facilitating Implementation of NG911 Services
To enable Next Generation 911 (NG911) to achieve its full capabilities, the Federal Communications Commission (FCC) adopted rules (47 CFR part 9, subpart j) requiring originating service providers (OSPs) – including wireline providers, commercial mobile radio service (CMRS) providers, text providers, interconnected Voice over internet Protocol (VoIP) providers and internet-based Telecommunications Relay Service (TRS) providers—to take specific actions to initiate or continue the transition of 911 traffic to IP-based networks in coordination with 911 Authorities.
The transition occurs in two phases, each of which is triggered by a valid request from a 911 Authority, such as a state or local 911 center.
The map below indicates the 911 Authorities that have submitted a valid request for Phase 1 and/or Phase 2 to the OSPs operating in their state. For a Map Key, use the icon in the top right corner to view Phase 1 requests indicated in a light blue color, Phase 2 requests indicated in a dark blue color, and county boundaries.
Data provided by the Federal Communications Commission (FCC). Data shown updated June 25, 2026.
Upon receiving a valid Phase 1 request from a 911 Authority, the OSP must:
1. Deliver all 911 traffic for the affected 911 centers in the IP-based Session Initiation Protocol (SIP) format requested by the Authority.
2. Enable the delivery of 911 traffic through the Emergency Service IP Network (ESInet) and next generation core services (NGCS) to the destination 911 center.
3. Route traffic to NG911 Delivery Points designated by the Authority.
4. Complete connectivity testing to verify that 911 traffic is being delivered in the requested SIP format.
A valid Phase 1 request must include:
Certification that infrastructure necessary to receive SIP traffic is operational.
Confirmation that agreements are in place with the ESInet, NG911 core services, and call handling equipment (CHE) providers.
Upon receiving a valid Phase 2 request, an OSP must:
1. Meet all Phase 1 requirements.
2. Deliver 911 traffic to designated NG911 Delivery Points in IP-based SIP format that complies with NG911 standards, including the transmission of caller location information (e.g., using PIDF-LO or equivalent).
3. Implement and maintain a Location Information Server (LIS) or equivalent for verifying customer location data.
4. Complete connectivity testing to verify delivery of both standards compliant 911 traffic and location information.
A valid Phase 2 request must include all Phase 1 requirements and:
Certify that the 911 Authority’s infrastructure is operational and compliant with applicable NG911 industry standards.
Confirm that the 911 Authority is prepared to receive standards-compliant SIP traffic and location data.
For additional information on Phase 1 and 2 requirements, go to Next Generation 911 (NG911) Services | Federal Communications Commission.