Next Generation 911 (NG911) is an IP-based system for receiving, routing and delivering 911 calls. It replaces the circuit-switched network behind legacy E911, short for Enhanced 911, which delivers a voice call with the caller's phone number and location. The functions carry over, and the architecture changes. The legacy network picks the answering center from a table, and the center looks up the caller's address by phone number. NG911 routes on a location that travels inside the call, over a network designed to carry text, photos, video and data as well. Each 911 authority moves to it when its own network is ready.
\n","summary":"NG911 is an IP-based system for receiving, routing and delivering 911 calls. It replaces the circuit-switched network behind legacy E911, which delivers a voice call with the caller's number and location. The functions carry over and the architecture changes: NG911 routes on a location carried inside the call. Each 911 authority moves to it when its own network is ready.","publishedAt":"2026-06-17T16:31:53.296","verifiedAt":"2026-07-17T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-10-10T03:02:03.474","nextReviewDueAt":"2026-10-17T00:00:00","templateVersion":"v2","aliases":["NG911 vs E911","What is NG911?","What is the difference between Next Generation 911 and Enhanced 911?","NG9-1-1 explained","How is NG911 different from E911?","What does Next Generation 911 mean?","NG911 definition","E911 vs NG911 for businesses","What is an ESInet?","Is NG911 replacing E911?","NG911 requirements for service providers","Next Generation 911 architecture"],"confidenceScore":92,"confidenceLabel":"High","canonicalUrl":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"contributorOrganizationProfile":null,"contributorPerson":null,"sections":[{"id":"f81639a7-61e9-41c5-aa59-5f57ec97174e","sectionKey":"what_e911_adds","sectionType":"markdown_section","heading":"What E911 adds to a 911 call","introMarkdown":"Enhanced 911 sends two things along with the voice call. One is the caller's number, known as automatic number identification, or ANI. The other is the caller's location. Federal rules define [automatic location information](https://www.ecfr.gov/current/title-47/section-9.3), or ALI, as information \"that permits emergency service providers to identify the geographic location of the calling party.\"\n\nThe legacy network delivers both through a chain of lookups, and the FCC's [July 2026 order on 911 reliability](https://www.federalregister.gov/documents/2026/07/10/2026-13998/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability) walks through it. Your provider hands the call to the legacy 911 network, where a switch called a selective router collects it. The router picks the answering center from a routing table. That table is built from the Master Street Address Guide, a database of valid addresses in each center's service area, and from an ANI/ALI database that pairs phone numbers with those addresses. The call then travels to the central office that serves the answering center, \"typically along dedicated trunk lines.\" The center, called a [public safety answering point](https://www.answerstack.io/q/what-is-a-psap-public-safety-answering-point) or PSAP, queries the ANI/ALI databases to confirm the location and the callback number.\n\nSo in the legacy E911 network, the answering center gets your location from a stored record, and your phone number is the key that retrieves it. The rules for internet phone service were written around that network. Under [47 CFR 9.11](https://www.ecfr.gov/current/title-47/section-9.11), an interconnected VoIP provider must supply E911 as a condition of service. It has to transmit every 911 call with the ANI and the caller's location, and the PSAP has to be able to get that location through the ALI database. That is why a VoIP provider has to obtain a location for the caller. How it does that depends on the service, and we cover the usual step in [how to register a VoIP phone for 911](https://www.answerstack.io/q/how-do-i-register-a-voip-phone-for-911).","introHtml":"Enhanced 911 sends two things along with the voice call. One is the caller's number, known as automatic number identification, or ANI. The other is the caller's location. Federal rules define automatic location information, or ALI, as information "that permits emergency service providers to identify the geographic location of the calling party."
\nThe legacy network delivers both through a chain of lookups, and the FCC's July 2026 order on 911 reliability walks through it. Your provider hands the call to the legacy 911 network, where a switch called a selective router collects it. The router picks the answering center from a routing table. That table is built from the Master Street Address Guide, a database of valid addresses in each center's service area, and from an ANI/ALI database that pairs phone numbers with those addresses. The call then travels to the central office that serves the answering center, "typically along dedicated trunk lines." The center, called a public safety answering point or PSAP, queries the ANI/ALI databases to confirm the location and the callback number.
\nSo in the legacy E911 network, the answering center gets your location from a stored record, and your phone number is the key that retrieves it. The rules for internet phone service were written around that network. Under 47 CFR 9.11, an interconnected VoIP provider must supply E911 as a condition of service. It has to transmit every 911 call with the ANI and the caller's location, and the PSAP has to be able to get that location through the ALI database. That is why a VoIP provider has to obtain a location for the caller. How it does that depends on the service, and we cover the usual step in how to register a VoIP phone for 911.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":10},{"id":"3cd7ac8a-4cae-49cb-baeb-43e983547b13","sectionKey":"what_ng911_replaces","sectionType":"markdown_section","heading":"What NG911 puts in place of that network","introMarkdown":"NG911 replaces the selective routers, trunks and lookup databases with an IP network. The [federal definition](https://www.ecfr.gov/current/title-47/section-9.28) calls NG911 an \"Internet Protocol-based system\" that ensures interoperability, is secure, uses commonly accepted standards and lets emergency communications centers \"receive, process, and analyze all types of 911 requests for emergency assistance.\"\n\nThe network is called an Emergency Services IP Network, or ESInet, and a 911 authority or its vendors run it. NENA, the association that writes 911 standards, [describes ESInets](https://cdn.ymaws.com/www.nena.org/resource/resmgr/ng9-1-1_project/whatisng911.pdf) as \"engineered, managed networks\" built on packet-switched technology that can carry voice along with large amounts of data.\n\nInside the ESInet, a group of functions called NG911 Core Services does the work of the selective router and its databases. The FCC order names the main ones. A Location Validation Function checks a civic address against a geographic information system database. Once the location is validated, an Emergency Call Routing Function maps it within the boundaries of emergency response zones to pick the PSAP, and routing proxies deliver the call with its callback information.\n\nThis changes how the answering center is chosen. The legacy network looks up the address on file for a phone number. NG911 places the caller's location on a map and finds the response zone around it. For that to work, the location has to arrive with the call. The second phase of the FCC's [NG911 transition rules](https://www.ecfr.gov/current/title-47/section-9.29) requires providers to embed location in the call signaling, in a format called PIDF-LO or a functional equivalent.\n\nAn IP network can also carry more than a voice call. NENA notes that legacy 911 networks carry voice and little else. The FCC says NG911 \"in its end state\" will support \"the transmission of text, photos, videos, and data to PSAPs.\" The phrase \"end state\" matters here. It describes the finished design, and each authority reaches it on its own schedule.","introHtml":"NG911 replaces the selective routers, trunks and lookup databases with an IP network. The federal definition calls NG911 an "Internet Protocol-based system" that ensures interoperability, is secure, uses commonly accepted standards and lets emergency communications centers "receive, process, and analyze all types of 911 requests for emergency assistance."
\nThe network is called an Emergency Services IP Network, or ESInet, and a 911 authority or its vendors run it. NENA, the association that writes 911 standards, describes ESInets as "engineered, managed networks" built on packet-switched technology that can carry voice along with large amounts of data.
\nInside the ESInet, a group of functions called NG911 Core Services does the work of the selective router and its databases. The FCC order names the main ones. A Location Validation Function checks a civic address against a geographic information system database. Once the location is validated, an Emergency Call Routing Function maps it within the boundaries of emergency response zones to pick the PSAP, and routing proxies deliver the call with its callback information.
\nThis changes how the answering center is chosen. The legacy network looks up the address on file for a phone number. NG911 places the caller's location on a map and finds the response zone around it. For that to work, the location has to arrive with the call. The second phase of the FCC's NG911 transition rules requires providers to embed location in the call signaling, in a format called PIDF-LO or a functional equivalent.
\nAn IP network can also carry more than a voice call. NENA notes that legacy 911 networks carry voice and little else. The FCC says NG911 "in its end state" will support "the transmission of text, photos, videos, and data to PSAPs." The phrase "end state" matters here. It describes the finished design, and each authority reaches it on its own schedule.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":20},{"id":"9d9fd03c-9662-47b8-81f7-aa4674d656e9","sectionKey":"e911_ng911_side_by_side","sectionType":"table_section","heading":"E911 and NG911 side by side","introMarkdown":null,"introHtml":null,"outroMarkdown":null,"outroHtml":null,"contentJson":{"rows":[{"cells":["What it is","The circuit-switched network that delivers the caller's number and location with a voice 911 call","An IP-based system for receiving, routing and delivering 911 traffic"]},{"cells":["How calls travel","Through a selective router and over dedicated trunks","Over an ESInet run by a 911 authority or its vendors, with NG911 Core Services"]},{"cells":["How the PSAP is chosen","A routing table built from the address guide and the ANI/ALI database","A routing function maps the validated location to a response zone"]},{"cells":["How location reaches the PSAP","The PSAP queries the ALI database by phone number","Location arrives in the call signaling as PIDF-LO or an equivalent"]},{"cells":["What it is designed to carry","Voice and limited data","Voice, text, photos, video and data in the end state"]}],"columns":["What changes","Legacy E911 network","NG911"]},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":30},{"id":"44bb0177-7537-400b-8157-14d5653f6bc7","sectionKey":"provider_and_address","sectionType":"markdown_section","heading":"Where your provider and your address fit","introMarkdown":"NG911 changes the network that delivers a 911 call. The location still starts with you and your provider, and providers have duties under both architectures.\n\nAtlantech Online, a business phone and fiber provider based in the Washington, DC area, documents [two ways to store 911 location data](https://www.atlantech.net/blog/store-911-location-data-pidf-lo) for its customers. With the static option, you assign an address to each phone number. Atlantech stores it and sends it to the 911 center when that number dials 911. It works the way the legacy lookup does: a number retrieves a stored address. Atlantech calls it \"the simplest and most common way\" to store the data, suited to a business whose phones stay at one fixed location. The static record holds a street address with no floor, suite or room number.\n\nThe dynamic option moves the location into the call. You configure the location of each phone in your network switches and Wi-Fi access points, and that information passes to Atlantech's network in PIDF-LO headers. The record updates when a phone moves within your network, and it can include the floor, suite or room. It needs network equipment that supports PIDF-LO, and Atlantech notes that a firewall or NAT device can block or alter the headers.\n\nSuppose a school has four buildings behind one street address. Its switches and access points are configured with the building and room each one serves, and teachers carry Wi-Fi phones from room to room. A static record gives responders the same street address for every call. A dynamic record can give them the building and room, as precisely as that configuration allows. Federal rules define a [dispatchable location](https://www.ecfr.gov/current/title-47/section-9.3) as a validated street address \"plus additional information such as suite, apartment or similar information necessary to adequately identify the location of the calling party.\" On a campus like that one, Atlantech's static record can't supply the extra detail, and a location configured in the network can.\n\nPIDF-LO is also the format the NG911 rules name for the hop from a provider to the 911 network. That is a separate hop from the one Atlantech's post describes, which runs from your network to the carrier. The idea is the same on both: location travels inside the call, where the legacy network keeps it in a database keyed to a phone number.","introHtml":"NG911 changes the network that delivers a 911 call. The location still starts with you and your provider, and providers have duties under both architectures.
\nAtlantech Online, a business phone and fiber provider based in the Washington, DC area, documents two ways to store 911 location data for its customers. With the static option, you assign an address to each phone number. Atlantech stores it and sends it to the 911 center when that number dials 911. It works the way the legacy lookup does: a number retrieves a stored address. Atlantech calls it "the simplest and most common way" to store the data, suited to a business whose phones stay at one fixed location. The static record holds a street address with no floor, suite or room number.
\nThe dynamic option moves the location into the call. You configure the location of each phone in your network switches and Wi-Fi access points, and that information passes to Atlantech's network in PIDF-LO headers. The record updates when a phone moves within your network, and it can include the floor, suite or room. It needs network equipment that supports PIDF-LO, and Atlantech notes that a firewall or NAT device can block or alter the headers.
\nSuppose a school has four buildings behind one street address. Its switches and access points are configured with the building and room each one serves, and teachers carry Wi-Fi phones from room to room. A static record gives responders the same street address for every call. A dynamic record can give them the building and room, as precisely as that configuration allows. Federal rules define a dispatchable location as a validated street address "plus additional information such as suite, apartment or similar information necessary to adequately identify the location of the calling party." On a campus like that one, Atlantech's static record can't supply the extra detail, and a location configured in the network can.
\nPIDF-LO is also the format the NG911 rules name for the hop from a provider to the 911 network. That is a separate hop from the one Atlantech's post describes, which runs from your network to the carrier. The idea is the same on both: location travels inside the call, where the legacy network keeps it in a database keyed to a phone number.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":40},{"id":"4244d872-ca15-4720-a2a1-f2183c3532c6","sectionKey":"when_ng911_arrives","sectionType":"markdown_section","heading":"When NG911 reaches your area","introMarkdown":"NG911 has no national switch-on date. The FCC's rules start a clock for a provider only when a 911 authority asks. Under [47 CFR 9.31](https://www.ecfr.gov/current/title-47/section-9.31), the authority first has to certify that it \"has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format\" and pass that traffic to its PSAPs.\n\nIn the first phase, the provider delivers 911 traffic in that IP format to delivery points the authority designates. The second phase adds the embedded location. [Section 9.30](https://www.ecfr.gov/current/title-47/section-9.30) gives an interconnected VoIP provider six months to meet each phase after a valid request, and some smaller carriers get 12.\n\nSo progress varies from one place to the next. The FCC's July 2026 order says: \"Many 911 Authorities have made significant progress to implement the transition to NG911.\" The order also describes transitional networks that \"blend some legacy network components with IP-based infrastructure.\" Those can keep selective routers and ANI/ALI databases in the call path while the ESInet is being built, with gateways that translate between the old and new formats. The order also cites the FCC's annual 911 fee report, in which 42 states, the District of Columbia, Guam and Puerto Rico reported spending on NG911 programs during 2024.\n\nFor this reason the NG911 label says little by itself. A state can have an NG911 program and still deliver your call through a selective router. To learn what applies to your calls, ask your provider whether the 911 authority for your address has sent a Phase 1 or Phase 2 request. And check that your own location record carries the floor and suite a responder would need, because that record is used under either architecture.","introHtml":"NG911 has no national switch-on date. The FCC's rules start a clock for a provider only when a 911 authority asks. Under 47 CFR 9.31, the authority first has to certify that it "has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format" and pass that traffic to its PSAPs.
\nIn the first phase, the provider delivers 911 traffic in that IP format to delivery points the authority designates. The second phase adds the embedded location. Section 9.30 gives an interconnected VoIP provider six months to meet each phase after a valid request, and some smaller carriers get 12.
\nSo progress varies from one place to the next. The FCC's July 2026 order says: "Many 911 Authorities have made significant progress to implement the transition to NG911." The order also describes transitional networks that "blend some legacy network components with IP-based infrastructure." Those can keep selective routers and ANI/ALI databases in the call path while the ESInet is being built, with gateways that translate between the old and new formats. The order also cites the FCC's annual 911 fee report, in which 42 states, the District of Columbia, Guam and Puerto Rico reported spending on NG911 programs during 2024.
\nFor this reason the NG911 label says little by itself. A state can have an NG911 program and still deliver your call through a selective router. To learn what applies to your calls, ask your provider whether the 911 authority for your address has sent a Phase 1 or Phase 2 request. And check that your own location record carries the floor and suite a responder would need, because that record is used under either architecture.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":50}],"citations":[{"title":"47 CFR Part 9, Subpart J: Next Generation 911","url":"https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-9/subpart-J","excerpt":"Next Generation 911 (NG911). An Internet Protocol-based system that (1) Ensures interoperability; (2) Is secure; (3) Employs commonly accepted standards; (4) Enables emergency communications centers to receive, process, and analyze all types of 911 requests for emergency assistance.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Regulatory definition of NG911, ESInet, LVF, LIS and SIP; Phase 1 and Phase 2 requirements including PIDF-LO and NG911 Delivery Points; six and twelve month implementation deadlines; valid request certifications; cost responsibilities; modification by mutual agreement with 30 day notification.","domain":"ecfr.gov","publisherName":"Electronic Code of Federal Regulations (National Archives / GPO)"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Location-Based Routing for Wireless 911 Calls (Report and Order, 89 FR 78066)","url":"https://www.federalregister.gov/documents/2024/09/24/2024-18603/facilitating-implementation-of-next-generation-911-services-ng911-location-based-routing-for","excerpt":"With the transition to NG911, the circuit-switched architecture of legacy 911 will eventually be entirely replaced by IP-based technologies and applications that provide all of the same functions as the legacy 911 system, as well as new capabilities.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Legacy E911 architecture with selective router, MSAG and ANI/ALI lookup, dedicated trunks and PSAP ALI query; over 217 million 911 calls per year; NG911 end state supporting text, photos, videos and data; statement that no fully enabled NG911 systems were yet operating as of 2024; existence of the F","domain":"federalregister.gov","publisherName":"Federal Communications Commission, via Federal Register"},{"title":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability (Second Report and Order, 91 FR 42794)","url":"https://www.federalregister.gov/documents/2026/07/10/2026-13998/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability","excerpt":"The ESRP is a routing engine that queries the ECRF and routes the traffic to the geographically appropriate PSAP in accordance with the PRF, which is the rule set that decides how traffic should be routed based on predetermined policies.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"NGCS functional elements (LVF, ECRF, ESRP, PRF) replacing selective router, ANI/ALI and MSAG functions; effective date August 10, 2026; expanded covered 911 service provider definition; physical diversity contrast between legacy and IP networks; adopted NG911 interoperability definition; one-time in","domain":"federalregister.gov","publisherName":"Federal Communications Commission, via Federal Register"},{"title":"NENA i3 Standard for Next Generation 9-1-1 (NENA-STA-010.3e-2021)","url":"https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/NENA-STA-010.3e-2021_i3_Stan.pdf","excerpt":"At that point, SRs and existing ALI systems are decommissioned and all 9-1-1 calls are routed using the Emergency Call Routing Function (ECRF) and arrive at the ESInet/NGCS via Session Initiation Protocol (SIP).","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"i3 architecture and functional elements; ESInet as an IP inter-network shared by public safety agencies; use of gateways for non-IP originating networks and legacy PSAPs; end state in which selective routers and existing ALI systems are decommissioned and calls route via the ECRF over SIP.","domain":"cdn.ymaws.com","publisherName":"National Emergency Number Association (NENA)"},{"title":"What is NG9-1-1?","url":"https://cdn.ymaws.com/www.nena.org/resource/resmgr/ng9-1-1_project/whatisng911.pdf","excerpt":"Next Generation 9-1-1 (NG9-1-1) networks replace the existing narrowband, circuit switched 9-1-1 networks which carry only voice and very limited data.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Limits of narrowband circuit-switched 911 for text, images, video and telematics or building plan data; ESInet as an engineered, managed, multi-purpose packet network arranged as a network of networks; NG911 designed to support emergency access codes used internationally.","domain":"cdn.ymaws.com","publisherName":"National Emergency Number Association (NENA)"},{"title":"47 CFR 9.10: 911 Service (wireless E911 Phase I and Phase II, indoor location accuracy)","url":"https://www.ecfr.gov/current/title-47/section-9.10","excerpt":"Within 3 meters above or below (plus or minus 3 meters) the handset for 80% of wireless E911 calls made from the z-axis capable device.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Phase I and Phase II enhanced 911 obligations for CMRS providers; horizontal requirement of dispatchable location or x/y within 50 meters on a rising percentage schedule; z-axis metric of plus or minus 3 meters for 80 percent of calls from z-axis capable devices.","domain":"ecfr.gov","publisherName":"Electronic Code of Federal Regulations (National Archives / GPO)"},{"title":"47 CFR 9.11: E911 Service (interconnected VoIP)","url":"https://www.ecfr.gov/current/title-47/section-9.11","excerpt":"Providers of fixed interconnected VoIP services must provide automated dispatchable location with each 911 call.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Interconnected VoIP E911 obligations: automated dispatchable location for fixed service; registered location, alternative location information, or national emergency call center routing for non-fixed service; delivery of location through the ALI database.","domain":"ecfr.gov","publisherName":"Electronic Code of Federal Regulations (National Archives / GPO)"},{"title":"47 CFR 9.16: General obligations, direct 911 dialing, notification, and dispatchable location","url":"https://www.ecfr.gov/current/title-47/section-9.16","excerpt":"a user may directly initiate a call to 911 from any station equipped with dialing facilities, without dialing any additional digit, code, prefix, or post-fix, including any trunk-access code such as the digit 9","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Multi-line telephone system obligations under Kari's Law and section 506 of RAY BAUM'S Act: direct 911 dialing without a trunk access digit, on-site MLTS notification, and dispatchable location for fixed, on-premises non-fixed, and off-premises devices.","domain":"ecfr.gov","publisherName":"Electronic Code of Federal Regulations (National Archives / GPO)"},{"title":"Location-Based Routing for Wireless 911 Calls (Report and Order, 89 FR 18488)","url":"https://www.federalregister.gov/documents/2024/03/13/2024-03157/location-based-routing-for-wireless-911-calls","excerpt":"Wireless 911 calls have historically been routed to PSAPs based on the location of the cell tower that handles the call. Sometimes, however, the 911 call is routed to the wrong PSAP because the cell tower is not in the same jurisdiction as the 911 caller.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Historic routing of wireless 911 calls on cell tower location; misrouting near jurisdictional borders and the resulting PSAP transfers; six month deadline for nationwide providers and 24 months for non-nationwide providers on voice, and 24 months for real-time text.","domain":"federalregister.gov","publisherName":"Federal Communications Commission, via Federal Register"},{"title":"RFC 6881: Best Current Practice for Communications Services in Support of Emergency Calling","url":"https://www.rfc-editor.org/rfc/rfc6881.html","excerpt":"The call is routed based on location using the Location-to-Service Translation (LoST) protocol, which maps a location to a set of PSAP URIs.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Service URN marking of emergency calls; conveyance of civic or geodetic location between SIP entities using the RFC 6442 extension; routing on location via the Location-to-Service Translation (LoST) protocol.","domain":"rfc-editor.org","publisherName":"Internet Engineering Task Force (IETF)"},{"title":"Plan and manage emergency calling - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing","excerpt":"To assign an emergency location to a network identifier for dynamic emergency calling, the emergency address must contain an appropriate geo code.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Enterprise dispatchable location practice: validated emergency addresses, geo codes required for assigning a location to a network identifier, and dynamic emergency calling based on the current location of the Teams client.","domain":"learn.microsoft.com","publisherName":"Microsoft Learn"},{"title":"NG911 Status","url":"https://www.nasna911.org/ng911-status","excerpt":"The 9-1-1 Network (ESInet/NGCS), Originating Service Providers (OSPs), and Public Safety Answering Points (PSAPs), each worth 0 to 10 points.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"State-by-state NG911 progress is scored across three separate domains: the 911 network (ESInet and NGCS), originating service providers, and PSAPs, each rated on a 0 to 10 scale.","domain":"nasna911.org","publisherName":"National Association of State 911 Administrators (NASNA)"},{"title":"How to Store Your 911 Location Data","url":"https://www.atlantech.net/blog/store-911-location-data-pidf-lo","excerpt":"This location information is then passed through to our network via PIDF-LO headers, which are special data packets that carry location information.","quoteText":null,"sourceRole":"SUPPORTING","verifiedAt":"2026-07-17T00:00:00","supportsText":"Operator-side illustration that carriers receive customer location through PIDF-LO headers, and that the dynamic PIDF-LO method suits environments where phones move rather than sitting at a fixed jack. Corroborated for the underlying protocol behavior by [10] and for the regulatory requirement by [1","domain":"atlantech.net","publisherName":"Atlantech Online"}],"revisions":[{"revisedAt":"2026-07-20T16:31:53.296+00:00","versionLabel":"Originally published","note":"","reviewedBy":null}],"relatedAnswers":[{"id":"b03c7fc2-b75b-407b-94c2-28d16792a61d","slug":"how-do-i-register-a-voip-phone-for-911","question":"How do I register a VoIP phone for 911?","publishedAt":"2026-07-20T16:31:58.611","confidenceScore":85,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"emergency-calling","label":"Emergency Calling","description":"911, E911, and NG911 for VoIP and SIP: registration, location accuracy, and call routing.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Registering a VoIP phone for 911 means giving your provider the street address where the phone is used, plus the suite or floor if responders would need it, so the provider can tie that location to the phone. Atlantech Online documents two options: a static address per phone number for a desk phone, and location taken from switches and access points for phones that move inside a building. It also documents a support-ticket route for corrections, and a 933 call that reads the registered address back.","url":"/q/how-do-i-register-a-voip-phone-for-911"},{"id":"eec6f088-b596-4007-a107-81939f09ee74","slug":"what-is-a-psap-public-safety-answering-point","question":"What is a PSAP (Public Safety Answering Point)?","publishedAt":"2026-05-12T16:31:56.115","confidenceScore":93,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"emergency-calling","label":"Emergency Calling","description":"911, E911, and NG911 for VoIP and SIP: registration, location accuracy, and call routing.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"A public safety answering point, or PSAP, is the 911 center designated to receive emergency calls and route them to emergency services personnel. A primary PSAP gets the call first, and a secondary PSAP takes calls transferred from a primary. The caller's location decides which PSAP a call reaches, which is why the address a VoIP provider holds for a phone matters at the PSAP's end.","url":"/q/what-is-a-psap-public-safety-answering-point"},{"id":"dc46b870-84ce-4ca3-97d2-5d91dd4818de","slug":"what-is-enhanced-911-e911","question":"What is Enhanced 911 (E911)?","publishedAt":"2026-04-16T16:31:50.28","confidenceScore":90,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"emergency-calling","label":"Emergency Calling","description":"911, E911, and NG911 for VoIP and SIP: registration, location accuracy, and call routing.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"E911 sends the caller's phone number and location to the 911 center with the call. For business phone systems the standard is a dispatchable location, which the business records for each device, keeps current and tests.","url":"/q/what-is-enhanced-911-e911"}],"contributorStats":{"verifiedAnswers":149,"openDisputes":0},"schemaJson":{"@context":"https://schema.org","@type":"Question","name":"What is Next Generation 911 (NG911), and how is it different from E911?","text":"What is Next Generation 911 (NG911), and how is it different from E911?","url":"https://www.answerstack.io/q/what-is-next-generation-911-ng911-and-how-is-it-different-from-e911","answerCount":1,"datePublished":"2026-06-17T16:31:53.296","about":[{"@type":"Thing","name":"Emergency Calling"},{"@type":"Thing","name":"Telecommunications"}],"acceptedAnswer":{"@type":"Answer","text":"Next Generation 911 (NG911) is an IP-based system for receiving, routing and delivering 911 calls. It replaces the circuit-switched network behind legacy E911, short for Enhanced 911, which delivers a voice call with the caller's phone number and location. The functions carry over, and the architecture changes. The legacy network picks the answering center from a table, and the center looks up the caller's address by phone number. NG911 routes on a location that travels inside the call, over a network designed to carry text, photos, video and data as well. Each 911 authority moves to it when its own network is ready.","url":"https://www.answerstack.io/q/what-is-next-generation-911-ng911-and-how-is-it-different-from-e911","upvoteCount":0,"datePublished":"2026-06-17T16:31:53.296","dateModified":"2026-07-17T00:00:00","citation":[{"@type":"CreativeWork","name":"47 CFR Part 9, Subpart J: Next Generation 911","url":"https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-9/subpart-J"},{"@type":"CreativeWork","name":"Facilitating Implementation of Next Generation 911 Services (NG911); Location-Based Routing for Wireless 911 Calls (Report and Order, 89 FR 78066)","url":"https://www.federalregister.gov/documents/2024/09/24/2024-18603/facilitating-implementation-of-next-generation-911-services-ng911-location-based-routing-for"},{"@type":"CreativeWork","name":"Facilitating Implementation of Next Generation 911 Services (NG911); Improving 911 Reliability (Second Report and Order, 91 FR 42794)","url":"https://www.federalregister.gov/documents/2026/07/10/2026-13998/facilitating-implementation-of-next-generation-911-services-ng911-improving-911-reliability"},{"@type":"CreativeWork","name":"NENA i3 Standard for Next Generation 9-1-1 (NENA-STA-010.3e-2021)","url":"https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/NENA-STA-010.3e-2021_i3_Stan.pdf"},{"@type":"CreativeWork","name":"What is NG9-1-1?","url":"https://cdn.ymaws.com/www.nena.org/resource/resmgr/ng9-1-1_project/whatisng911.pdf"},{"@type":"CreativeWork","name":"47 CFR 9.10: 911 Service (wireless E911 Phase I and Phase II, indoor location accuracy)","url":"https://www.ecfr.gov/current/title-47/section-9.10"},{"@type":"CreativeWork","name":"47 CFR 9.11: E911 Service (interconnected VoIP)","url":"https://www.ecfr.gov/current/title-47/section-9.11"},{"@type":"CreativeWork","name":"47 CFR 9.16: General obligations, direct 911 dialing, notification, and dispatchable location","url":"https://www.ecfr.gov/current/title-47/section-9.16"},{"@type":"CreativeWork","name":"Location-Based Routing for Wireless 911 Calls (Report and Order, 89 FR 18488)","url":"https://www.federalregister.gov/documents/2024/03/13/2024-03157/location-based-routing-for-wireless-911-calls"},{"@type":"CreativeWork","name":"RFC 6881: Best Current Practice for Communications Services in Support of Emergency Calling","url":"https://www.rfc-editor.org/rfc/rfc6881.html"},{"@type":"CreativeWork","name":"Plan and manage emergency calling - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing"},{"@type":"CreativeWork","name":"NG911 Status","url":"https://www.nasna911.org/ng911-status"},{"@type":"CreativeWork","name":"How to Store Your 911 Location Data","url":"https://www.atlantech.net/blog/store-911-location-data-pidf-lo"}]}}}