VoIP E911 compliance requirements obligate any interconnected VoIP provider to collect a physical Registered Location from every subscriber, give clear warnings about the service’s limitations, automatically deliver a callback number and location to the correct emergency dispatch center when a subscriber dials 911, meet direct-dial and dispatchable-location rules where they apply, and report outages that affect 911 within tight deadlines. These duties live primarily in 47 C.F.R. Part 9, Subpart D, and the FCC enforces them with forfeitures that have reached eight figures.
Who the Rules Apply To
The FCC’s 911 obligations attach to any service that meets the definition of “interconnected VoIP” in 47 C.F.R. § 9.3: real-time two-way voice, a broadband connection at the user’s location, IP-compatible customer equipment, and the ability to both receive calls from and place calls to the public telephone network.1eCFR. 47 CFR 9.3 – Definitions
For 911 purposes the net is wider than that. A separate provision pulls in services that only permit outbound calls to the traditional phone network, even if inbound calls from that network are not possible.1eCFR. 47 CFR 9.3 – Definitions If your service can dial a regular phone number, plan on the full Subpart D framework applying regardless of business model.
Registered Location for Every Subscriber
Before activating service, a provider must obtain a Registered Location from the subscriber. This is the physical street address where the service will first be used, with enough specificity to send help to the right door: street address, apartment or suite number, city, state, and zip code.2eCFR. 47 CFR 9.11 – E911 Service That address is what the provider’s system transmits to the dispatcher on a 911 call.
The provider must also give subscribers at least one method to update that address using nothing more than the equipment they already use for the service. The regulation requires the update to be possible “at will and in a timely manner.”2eCFR. 47 CFR 9.11 – E911 Service Mail-in forms or business-hours-only phone support don’t meet the standard. The update path has to be fast and available through the service itself, because VoIP equipment is portable and subscribers routinely take it to new addresses.
Subscriber Advisories and Warning Labels
Every interconnected VoIP provider must clearly explain how its 911 service differs from a traditional landline. The disclosures must be prominent, in plain language, and must cover specific scenarios: the service may not work during a power outage, during an internet connection failure, or if the subscriber moves the equipment without updating the Registered Location.3GovInfo. 47 CFR Part 9 – 911 Requirements The provider cannot activate the account until the subscriber affirmatively acknowledges receiving and understanding the advisory.
Providers also have to distribute physical warning labels, such as stickers, describing these limitations and instructing the subscriber to place them on or near the VoIP equipment.3GovInfo. 47 CFR Part 9 – 911 Requirements New subscribers must receive labels before service begins, and existing subscribers must receive them as well.
Routing, Callback, and Location Delivery
When a subscriber dials 911, the provider’s system must automatically transmit a callback number (Automatic Number Identification, or ANI) and the subscriber’s location alongside the voice call. The callback number lets the dispatcher reach the caller if the connection drops; the location data tells the dispatcher where to send help. Nothing about this exchange depends on the caller speaking or acting, which matters when a caller is injured or unable to talk.2eCFR. 47 CFR 9.11 – E911 Service
The call itself must travel through the dedicated Wireline E911 Network, using the ANI to route to the correct Public Safety Answering Point (PSAP). The provider maps the Registered Location against address databases to identify the right jurisdiction and delivers the call to that jurisdiction’s PSAP. If the provider cannot confirm the caller’s location, it may route the call to a national emergency call center as a last resort so that responders can determine where to go.4eCFR. 47 CFR 9.11 – E911 Service
Dispatchable Location, Direct Dial, and Multi-Line Systems
Two additional statutes tighten the location and dialing rules for certain deployments. Kari’s Law, codified at 47 U.S.C. § 623, requires that any multi-line telephone system (MLTS) manufactured, sold, or installed after February 16, 2020, allow a user to dial 911 directly from any phone with a keypad, with no prefix, access code, or extra digit. The obligations run through the whole supply chain: manufacturers and importers cannot sell a non-compliant system, and installers, managers, and operators cannot set one up or run it.5Office of the Law Revision Counsel. 47 USC 623 – Configuration of Multi-Line Telephone Systems for Direct Dialing of 911
Kari’s Law also requires that a 911 call from a multi-line system trigger a notification to a central on-site location, such as a front desk or security office, provided the hardware and software can support it without upgrades.5Office of the Law Revision Counsel. 47 USC 623 – Configuration of Multi-Line Telephone Systems for Direct Dialing of 911 The FCC’s implementing rules add that the notification must go out at the same time as the 911 call and must not delay the emergency call itself, and it has to reach a location where someone is likely to see or hear it.6eCFR. 47 CFR 9.16 – Direct 911 Dialing, Notification, and Dispatchable Location
Section 506 of RAY BAUM’s Act pushed location accuracy past a bare street address for MLTS and non-fixed VoIP. The goal is a “dispatchable location,” meaning a validated street address plus additional detail such as floor, suite, or room number.7Federal Communications Commission. Multi-line Telephone Systems – Kari’s Law and RAY BAUM’s Act 911 Direct Dialing, Notification, and Dispatchable Location Requirements Deadlines vary by device type. Fixed on-premises devices at MLTS locations have been subject to automated dispatchable location since January 6, 2021. Non-fixed and off-premises devices came under the rule on January 6, 2022. Where automated dispatchable location is not technically feasible, the fallback is coordinate-based data sufficient to identify the building and approximate floor, or a manually updated Registered Location.8Federal Communications Commission. Dispatchable Location for 911 Calls from Fixed Telephony, Interconnected VoIP, TRS, and Mobile Text Service
Non-fixed interconnected VoIP providers carry the hardest version of this obligation because the equipment moves. They must deliver automated dispatchable location when technically feasible, supply a Registered Location or alternative location data when it is not, and only route to a national emergency call center as a last resort after a good-faith effort to obtain location from every available source. The provider must also detect when a subscriber appears to be calling from somewhere other than the Registered Location and either prompt for a new address or update it automatically.8Federal Communications Commission. Dispatchable Location for 911 Calls from Fixed Telephony, Interconnected VoIP, TRS, and Mobile Text Service
Outage Reporting Deadlines
Outages don’t pause 911 obligations. Under 47 C.F.R. Part 4, an outage lasting at least 30 minutes that could affect a 911 center or other special facility requires electronic notification to the FCC within 240 minutes of discovering the problem. For outages affecting at least 900,000 user-minutes of service and causing a complete loss of service, the notification window is 24 hours. A Final Communications Outage Report is due within 30 days.9eCFR. 47 CFR 4.9 – Outage Reporting Requirements – Threshold Criteria
Separately, providers must notify any potentially affected PSAP as soon as possible, and no later than 30 minutes after discovering an outage on facilities they own, operate, or use.10Federal Communications Commission. Order on Reconsideration (FCC 24-73) The FCC treats the initial notification as a preliminary heads-up rather than a full incident report; the point is to give the PSAP enough warning to activate backup procedures. Late or missing PSAP notifications are one of the most common triggers for large enforcement penalties.
Penalties for Getting It Wrong
Under 47 U.S.C. § 503, the FCC can impose forfeitures of up to $100,000 per violation or per day of a continuing violation for common carriers, capped at $1,000,000 for a single act or failure to act. For entities outside the common carrier category, the caps are $10,000 per violation and $75,000 total.11Office of the Law Revision Counsel. 47 USC 503 – Forfeitures Each failed 911 call and each unnotified PSAP can count separately, which is how penalty figures escalate quickly.
Consent decrees have gone larger. The FCC’s settlement with Charter Communications over 911 and outage reporting violations required a $15 million payment along with multi-year compliance monitoring.12Federal Communications Commission. FCC Settles 911 Rule Investigation with Charter for $15M The Commission can also deny or revoke access to telephone numbering resources, which effectively prevents a provider from operating in the United States.
A Note on Non-Interconnected Services
Services that never touch the traditional phone network — apps that only allow calls between users of the same platform — are classified as non-interconnected VoIP. The FCC has stated that providers of non-interconnected VoIP services are not currently required to comply with the Commission’s 911 and E911 rules.13Federal Communications Commission. VoIP and 911 Service If your service sits near that boundary and can dial regular phone numbers in any direction, assume the full Subpart D framework applies and build the compliance program accordingly.