How 911 Works on a VoIP Number
· VoiRelay · 1 view
Emergency calling was one of the first things I had to get straight while building VoiRelay. I was designing a low-cost U.S. phone number that works over Wi-Fi, from the web and from Android, and I did not want to treat 911 as a footnote. A VoIP number can place ordinary calls over an internet connection. Reaching emergency services is a different problem, with different limits, and the FCC has been clear about those limits for a long time.
I wrote earlier about why I built a cheap phone service that works over Wi-Fi, including a short note on 911. This post is the fuller version of what I learned.
What interconnected VoIP is required to do
The FCC distinguishes ordinary internet calling from "interconnected" VoIP: a service that can place calls to, and receive calls from, the regular telephone network. For those services, the FCC's guide to VoIP and 911 service says providers have Enhanced 911 (E911) obligations. E911 is meant to send the call, a callback number, and, in most cases, location information to the emergency call center.
The same guide says interconnected VoIP providers may not let customers opt out of 911. They have to obtain a physical address before service starts, give people a way to update that address if it changes, and transmit 911 calls along with a callback number and the registered location. The FCC also notes that providers which do not fully interconnect with the public network are not currently required to follow those 911 rules. The Commission's broader VoIP page makes the same basic point: 911 calls on VoIP are handled differently from 911 calls on regular telephone service, and not all VoIP services connect directly to 911 at all.
That legal shape mattered to me as I built VoiRelay. If I was going to offer a real U.S. number that can place regular calls, 911 could not be an optional extra I ignored.
A registered address is not the same as a cell tower fix
The hardest part, for me, was location. A portable VoIP service can be used from almost any internet connection, in almost any place. The FCC says that is exactly what makes it hard for emergency services to tell where a 911 call started. A VoIP 911 call may not reach the call center that serves the caller's current location. It may ring an administrative line instead of a trained 911 operator. It may connect to the right center and still fail to send the caller's number or location automatically.
A lot of that risk comes down to how the location is known. For interconnected VoIP, the rules in 47 CFR § 9.11 lean on a Registered Location: the physical address the provider has for the person using the service. The FCC's page on dispatchable location explains what that information is supposed to include — a street address, and, when it is needed to find someone in a larger building, something more precise such as a room or floor. For a phone that stays in one place, the rules call for that location to be generated automatically with the call. For a service that can be used from more than one place, automated location is required if it is technically feasible. If it is not, the provider can use the Registered Location, or other location information that is still good enough to identify the address, or, as a last resort, route the call to a national emergency call center.
The same dispatchable-location page notes that those VoIP rules do not apply to wireless carriers, which have a separate set of location-accuracy requirements. I read that as the core difference I had to accept. A cell phone can often be located through the wireless network itself. A VoIP 911 call, especially a portable one, may instead depend on an address I have registered in advance. If I have moved, and that address is still the old one, emergency services can be sent to the wrong place. The FCC tells providers to get the address before service starts, to make it possible to update, and — for non-fixed service — to notice when a 911 call is coming from somewhere other than the registered address and either prompt for a new one or update it.
I do not treat a registered address as a magic substitute for a phone that can be found where it actually is. I treat it as information I would have to keep current, and as a limit of the technology, not a minor setup step.
Why a power or internet outage can stop the call
The other limit is simpler, and I take it just as seriously. A VoIP call needs a working internet connection and, usually, working power for the modem, the router, and the device. The FCC notes that VoIP service may not work during a power outage, or when the internet connection fails or becomes overloaded. The same point appears in the FCC's general VoIP guide: some VoIP services do not work during power outages, and the provider may not offer backup power.
If the lights go out, or the hotel Wi-Fi dies, or the home connection drops, the number I built may not be able to reach anyone, including 911. That is not a rare edge case I can wave away. It is a basic property of an internet phone service. I still keep a regular mobile phone for emergencies, and I have learned not to treat a Wi-Fi-only number as a complete substitute for a phone that can place a 911 call when the internet is down.
How VoiRelay describes this publicly
I wanted the public explanation to match those limits, not to paper over them. VoiRelay's FAQ currently describes two kinds of numbers. On the Calling plan, 911 (E911) is included and required, and a confirmed address is registered so emergency services can find the caller. The FAQ also says internet-based 911 can fail if the power or the internet is out, and that the address needs to be kept up to date. The Text-only plan cannot place or receive calls at all, so it has no 911. The site is still in demo mode and is not taking new customers yet. That FAQ language is how the service is described today, not a claim that paid sign-ups are already open.
I built VoiRelay around that distinction on purpose. A number that can place ordinary calls, as I see it, comes with the 911 obligations that go with interconnected VoIP, and with an honest account of how that 911 path can fail. A number that cannot place calls is not a 911 number, and I did not want the public description to pretend otherwise. I still keep a mobile phone as a backup, because a registered address and a working internet connection are not the same thing as a wireless 911 call.
References
- VoIP and 911 Service – Federal Communications Commission
- Voice Over Internet Protocol (VoIP) – Federal Communications Commission
- 47 CFR Part 9, Subpart D – Interconnected Voice over Internet Protocol Services (eCFR), including § 9.11
- Dispatchable Location for 911 Calls from Fixed Telephony, Interconnected VoIP, TRS, and Mobile Text Service – Federal Communications Commission
- FAQ – VoiRelay
- Why I Built a Cheap Phone Service That Works Over Wi-Fi – VoiRelay