What is Enhanced 911 (E911)?

Basic 911 connects a caller to an answering point and stops there. Enhanced 911 attaches a callback number and a location record to that same call, delivered automatically so the call taker is not depending on a frightened or injured person to describe where they are. The FCC states the purpose in one line: E911 "was developed to provide PSAPs with the caller's location and a call-back number as part of each 911 call."[5]

The number is older than the data behind it. Congress designated 9-1-1 as the universal emergency assistance number in the Wireless Communications and Public Safety Act of 1999, which also set out federal support for states upgrading their 911 capabilities.[7] The rules that attach data to that number now sit in 47 CFR Part 9, which defines a public safety answering point, or PSAP, as "an answering point that has been designated to receive 911 calls and route them to emergency services personnel."[1]

The two data elements

Automatic Number Identification identifies the calling party and may be used as the callback number, so an answering point can reestablish a 911 call that drops.[1] Automatic Location Identification is defined in the same rule as information "transmitted while providing E911 service that permits emergency service providers to identify the geographic location of the calling party."[1] On a legacy landline that record was a street address tied to the billing telephone number, while a wireless call returns latitude and longitude and a properly configured business phone system returns an address with a floor or room attached.[1][2]

How the scope kept widening

E911 began as a wireline capability and reached wireless in stages. Phase I required carriers to give the PSAP the caller's number and the location of the cell site handling the call, and Phase II required latitude and longitude accurate to somewhere between 50 and 300 meters depending on the technology in use.[8][2] Interconnected VoIP providers then picked up their own E911 duties, including an obligation to warn subscribers in plain language about the circumstances in which E911 may be limited or unavailable and to keep a record that each subscriber acknowledged that warning.[3] Multi-line telephone systems in offices, hotels, campuses, and schools came last, through Kari's Law and Section 506 of RAY BAUM'S Act.[4][5]

ANI is the calling party's number, delivered with the call and used by the answering point as the callback number.[1] The FCC's Phase I wireless rules were built directly on it, requiring licensees to provide the PSAP with the telephone number of the 911 caller and the location of the cell site receiving the call, through the use of ANI and Pseudo-ANI.[2]

Pseudo-ANI covers the cases where a real directory number will not do the job. Part 9 defines it as a number with the same digit count as an ANI that is not a North American Numbering Plan directory number and that carries a special meaning agreed between the systems that originate and route the call.[1] Legacy wireless and enterprise deployments used it as a routing and lookup key, which is how a single physical building could present separate location records for separate floors.

The practical failure here is a callback that reaches the wrong phone. If a business phone system presents its main billing number rather than the extension that dialed, the PSAP calls a switchboard instead of the person in trouble, which is why the MLTS notification rules require a valid callback number in the alert sent to on-site staff.[1]

ALI is the location half of E911, defined in Part 9 as information transmitted while providing E911 service that permits emergency service providers to identify the geographic location of the calling party.[1] In the legacy architecture it is a database lookup rather than something the call itself carries. The call arrives with a number, the answering point queries an ALI database with that number, and the database returns a stored record.

That indirection explains most of the historical weak points, because the record is only as good as whatever was last written to it. A phone that moved to a different floor in March still reports its January address until somebody updates the database. The FCC's interconnected VoIP rules attack the same problem from the provider side, requiring that location information be available to the PSAP from or through the appropriate ALI database, and requiring nomadic services to obtain a Registered Location from the customer before service starts and then either prompt for a new one or update it automatically when the service is used somewhere else.[3]

What ALI returns depends on the call type. A wireline call returns a civic address, while a wireless Phase II call returns latitude and longitude held to accuracy standards that run from 50 meters for 67 percent of calls on handset-based technology up to 300 meters for 90 percent of calls on network-based technology.[2] A correctly configured business phone system returns a civic address with the floor or room attached, which is the standard the MLTS rules now require.[4]

Routing is a separate problem from location, and in the legacy design it runs over dedicated infrastructure. Part 9 defines the Wireline E911 Network as a dedicated wireline network that is interconnected with but largely separate from the public switched telephone network, that includes a selective router, and that is used to route emergency calls and related information to PSAPs.[1] Interconnected VoIP providers are required to route all 911 calls through that network using ANI and, where necessary, pseudo-ANI, unless the call goes first to a national emergency call center because the provider cannot confirm the caller's location.[3]

Wireless routing has been the weaker link. Because a wireless 911 call was historically routed on the location of the tower handling it, a call placed near a jurisdictional boundary could land at a neighboring answering point and need a transfer before help was dispatched. The Alliance for Telecommunications Industry Solutions estimated that on average 12 percent of wireless legacy E911 voice calls nationwide are misrouted.[9]

The FCC's answer was location-based routing, adopted in January 2024, which requires wireless providers to route 911 voice calls and real-time text using precise device location rather than tower sector. Nationwide providers were given six months to implement it for voice calls, while non-nationwide providers and all providers implementing it for real-time text were given 24 months.[9] AT&T told the Commission that its own nationwide implementation gave roughly 10 percent of wireless 911 voice calls on its network a better route, so those calls no longer needed a transfer.[9]

Part 9 defines dispatchable location as a location delivered to the PSAP with a 911 call consisting of the validated street address of the calling party, plus additional information such as suite, apartment, or similar information necessary to adequately identify the location of the calling party.[1] Validation carries as much weight as the address itself, since the wireless version of the definition adds that the street address must be validated and, to the extent possible, corroborated against other location information before it is delivered.[2]

What Kari's Law requires

Kari's Law Act of 2017 amended the Communications Act to require that a multi-line telephone system be pre-configured so a user can dial 911 directly from any station equipped with dialing facilities, without any additional digit, code, prefix, or trunk-access code such as the digit 9.[6] The law is named for Kari Hunt, who was killed in a motel room in Marshall, Texas in 2013 while her nine-year-old daughter tried four times to reach 911 from the room phone and never got through, because she did not know the system required dialing 9 first.[5] It applies to any MLTS manufactured, imported, first sold or leased, or installed after February 16, 2020.[5]

The same rule adds MLTS notification, meaning an alert to a security desk or other monitored location that goes out contemporaneously with the 911 call and must not delay it. At minimum that alert has to report that a 911 call was made, give a valid callback number, and repeat the location conveyed to the PSAP.[1][4]

What RAY BAUM'S Act added

Section 506 of RAY BAUM'S Act directed the FCC to ensure that dispatchable location travels with a 911 call regardless of the technological platform used.[5] The resulting deadlines are specific. On-premises fixed telephones on an MLTS had to provide automated dispatchable location no later than January 6, 2021, and on-premises non-fixed devices and off-premises devices had until January 6, 2022, with a fallback to an end-user manual update or, for off-premises devices, coordinate-based enhanced location where automation is not technically feasible.[4] Fixed interconnected VoIP services carry the same automated dispatchable location duty, while non-fixed VoIP services work down a feasibility ladder through Registered Location, alternative location information, and routing to a national emergency call center.[3] Compliance vendors read the scope the same way, describing the obligations as reaching any US organization operating an MLTS, from hotels and hospitals to schools and offices.[13]

The wireless equivalent

Wireless carriers are held to a parallel standard expressed in coordinates. Nationwide providers had to deliver either dispatchable location or an x/y location within 50 meters for 80 percent of wireless 911 calls at the six-year benchmark, and they had until April 3, 2025 to deploy either dispatchable location or z-axis technology on a nationwide basis.[2] Where z-axis is used, the metric is within 3 meters above or below the handset for 80 percent of calls from a z-axis capable device, reported as Height Above Ellipsoid, with floor level added when the carrier has it.[2] Since January 6, 2022, all CMRS providers have had to provide dispatchable location with wireless E911 calls where doing so is technically feasible.[2]

The location record can be stale

In the legacy architecture E911 location data is a stored record rather than a live measurement. A desk phone that moved floors, or a softphone signed in from a hotel room, can produce a call that routes and displays confidently to the wrong address. The FCC's response for nomadic VoIP is a duty on the provider to detect that the service is being used somewhere other than the Registered Location and then either prompt the customer for a new one or update it without customer action.[3]

Remote and mobile users are the hard case

Off-premises devices on a business system are allowed to fall back to coordinate-based enhanced location when automated dispatchable location is not technically feasible, which is a materially lower bar than a street address with a floor number.[4] Platform vendors close some of that gap with network mapping. Microsoft, for example, ties Teams emergency locations to validated civic addresses carrying geo codes, and lets administrators associate subnets and Wi-Fi access points with those locations so the client reports where it actually is.[12] Nomadic implementations track the endpoint's current location instead of a static record, either through that kind of network mapping or by carrying location in the SIP signaling itself.[12][14]

The architecture underneath is being replaced

Next Generation 911 moves emergency traffic onto IP networks and away from selective routers and ALI database lookups. In September 2024 the FCC adopted rules defining the responsibilities of originating service providers and setting deadlines for delivering 911 calls to NG911 systems, while preserving the authority of state, territorial, regional, Tribal, and local governments over configuration, timing, and cost.[10] The transition runs at different speeds in different jurisdictions, so a national enterprise will be delivering into legacy and NG911 systems at the same time for years.

The rulebook itself keeps shifting

In January 2026 the FCC published a direct final rule removing provisions it considered obsolete, including the pre-2021 transitional VoIP E911 paragraph at 47 CFR 9.11(a) and the dispatch-service exception at 9.10(n), effective March 16, 2026.[11] A compliance document written against older citations can now point at paragraphs that no longer exist.

It is not the same thing as 911

Basic 911 is the duty to deliver the call. Wireless carriers must transmit all 911 calls to a PSAP regardless of whether the caller subscribes to their service, and that obligation exists independently of the Phase I and Phase II location duties layered on top of it.[2][8]

It is not Next Generation 911

NG911 is the IP-based replacement architecture, with its own FCC implementation rules adopted in 2024.[10] E911 describes the legacy capability set that NG911 is designed to absorb and extend, so a given answering point can be receiving E911 data today and NG911 data next year with nothing changing on the caller's handset.

It is not a product you buy once

The rules assign duties to different parties at different stages. Manufacturers and importers may not ship a multi-line telephone system unless it is pre-configured for direct 911 dialing and capable of providing dispatchable location, and installers, managers, and operators may not run one unless it stays configured that way with current location data.[4] An organization that buys an E911 solution and never revalidates addresses after an office move is still exposed under the operator duty, whatever the product does.

It is not a guarantee of per-call accuracy

The wireless standards are statistical thresholds rather than promises about any individual call, which is why they are written as 50 meters for 67 percent of calls or z-axis within 3 meters for 80 percent of calls.[2] Interconnected VoIP providers must also warn every subscriber, prominently and in plain language, about the circumstances in which E911 may be unavailable or limited, including loss of electrical power and relocation of the end user's equipment.[3]