How do I register a VoIP phone for 911?

Registration is the act of telling your voice provider the exact physical address where a phone or app is used, so a 911 call carries that address to the public safety answering point covering the area. Federal rules call the stored value a Registered Location, defined as the most recent information a provider has that identifies the physical location of an end user [2]. An interconnected VoIP provider has to obtain that location from you before service starts, and it has to offer at least one update method that relies only on the customer premises equipment you already use for the service [1].

This differs from a landline in one structural way. A copper line was wired to a single building, so the address came out of the wiring records. An IP phone can be plugged in anywhere with a broadband connection, and the IP address it picks up says almost nothing dependable about the street it sits on, which is why the address has to be stored and maintained as data rather than inferred from the connection.

What the address has to contain

The target is a dispatchable location, which the rules define as the validated street address of the calling party plus additional detail such as suite, apartment, or similar information needed to identify where that caller is [2]. A street address on its own puts responders in the parking lot of a five-story office building, and the floor and suite are what gets them to the right door.

Who is responsible for keeping it accurate

Responsibility splits by service type. On a consumer or small business account you usually maintain the record yourself in the provider portal. On a business phone system the organization operating a multi-line telephone system carries obligations of its own, including automated dispatchable location from on-premises fixed phones since January 6, 2021 and from non-fixed and off-premises devices since January 6, 2022 where it is technically feasible [3][4].

Two arrangements exist, and which one you are in decides whether you can fix the address yourself in two minutes or have to raise a ticket. On a self-managed account the provider gives the account holder an emergency address page you edit directly, which is what the federal rules require: at least one update method that uses only the equipment needed to access the service, available at will and in a timely manner [1]. On a managed business system the emergency address usually sits with an administrator. In Vonage Business Cloud the super user or administrators manage emergency services for their locations from the admin portal [10], and in 8x8 Admin Console the emergency address lives inside each user profile under Home and then Users [11].

Why this matters before you start

Editing the wrong record is a common way to end up with a registration that looks correct and still sends responders somewhere else. A number assigned to a person, a physical desk phone, and a shared device such as a conference room phone can each carry a separate emergency location. Microsoft treats these as distinct objects: a registered address is assigned to a user, while a location ID can also be attached to a network identifier or a common area device [5].

What to check first

Open the emergency address field for the line in question and see whether you can change it. If it is greyed out, the account is administered centrally and the change has to go through whoever holds the console. Ask that person for the full location list rather than just the one address, because you need to know whether a location for your building and floor already exists before creating a duplicate.

Type the address into the provider's lookup or map tool rather than pasting it off a letterhead, because the record has to match the emergency address data used for routing. Vonage Business Cloud verifies addresses against the Master Street Address Guide and states that validation can take up to 30 days to complete [10]. Until an address passes, calls do not go straight to the local answering point: an unverified Vonage address routes to a national emergency call center, where an agent asks for your address before transferring the call to the closest PSAP [10], which adds a manual step for a caller who may not be able to speak clearly.

Use the lookup tool, not free text

Microsoft recommends creating emergency addresses with the map search feature in Teams admin center, which formats the address, marks it validated, and attaches the geo code [5]. Those latitude and longitude values are not cosmetic. An emergency address without an appropriate geo code cannot be assigned to a network identifier, so skipping the lookup quietly blocks dynamic location later in the build [5][7]. Microsoft also notes that emergency addresses more than a couple of years old have to be re-created before they can be assigned to network identifiers [7].

What to do when validation fails

8x8 shows a warning and refuses to save a user whose site address is invalid, and where an address fails validation it offers a choice between an existing validated address and the address exactly as you typed it [11]. Taking the override is tempting for a new building or a rural address the database has not caught up with. The consequence is stated in 8x8's own documentation: an overridden address might not be registered for emergency services if it is not validated [11]. Where the address genuinely exists and the database disagrees, the fix is to get the record corrected with the provider rather than saving the override.

Saving an address creates a record, and assigning it is what makes a 911 call carry it. In Teams, creating an emergency address generates a location ID, and adding a place such as a floor creates a second location ID for the combination, which is the ID actually associated with the user or site [5]. Zoom Phone uses a similar shape, with admins defining parent locations at the building level and optional sub-locations for floors and suites, each carrying its own street address [8].

Add the place detail

A floor, wing, suite, or room number is the part of a dispatchable location the rules call out specifically, alongside the validated street address [2]. In a single-tenant building the extra detail can feel redundant, but in a multi-tenant tower it is often the only thing that keeps responders from checking floors one at a time.

Assign per user, per number, and per device

Each Calling Plan user in Teams needs a registered emergency address associated with the assigned telephone number, and a common area phone or Teams Room can carry a static location of its own [5]. In 8x8 the user profile defaults to the site address, and you clear that checkbox to give an individual a different emergency address, which is what a remote employee needs when their phone number belongs to a different city than the house they work from [11]. Vonage splits it into two jobs: create the locations first, then assign devices to those locations so calls route correctly [10].

Watch the shared and forgotten endpoints

Conference room phones, lobby phones, elevator phones, and warehouse handsets are most often left behind, because no individual owns them, and they still place 911 calls. Walk the floor plan against the device list rather than trusting an inventory export, since a phone moved to another room keeps whatever location it was given at provisioning.

Portable endpoints need a location derived at call time rather than typed once. Teams does this with a Location Information Service the administrator populates with network identifiers and their matching emergency locations, and when a client connects it matches on wireless access point first, then Ethernet switch and port, then switch, then subnet, using the first match it finds [7]. Zoom Phone runs a comparable hierarchy, matching network switch MAC address and port ahead of wireless access point identifiers, then IP subnet, then public IP [8]. RingCentral maps emergency response locations to access point BSSIDs, public and private IP ranges, and Ethernet switch chassis and port values, and the automatic location updates feature has to be enabled on the account by a RingCentral account manager first [9].

Home offices need a different mechanism

Network mapping only covers networks you control. For people working from home, Teams uses the operating system location service to suggest an address that the user then confirms, edits, or replaces, and the confirmed address is saved on the client so it is reused whenever that client reconnects to the same network [6]. Zoom's personal locations work along the same lines, prompting the user to confirm or update the emergency address whenever the app roams into a location it does not recognize [8].

The confirmation prompt changes how the call routes

Microsoft publishes a routing table showing that an address obtained from the operating system and confirmed by the user goes direct to the PSAP, while an address taken from the operating system without confirmation, or typed in manually and confirmed, is screened by a call center before transfer [6]. The prompt that users tend to dismiss therefore has a measurable effect, because confirming the address is what removes the screening step. The location itself travels with the call as PIDF-LO data in the SIP signaling, which is why a Direct Routing deployment has to set PidfloSupported to true on the session border controller handling emergency calls [7][14].

Dial 933 from the registered line. In the United States and Canada that reaches an automated service which reads back the emergency address and callback number on file, and Telnyx states that a successful 933 test confirms the address associated with the test call and does not dispatch emergency services [12]. The same documentation warns against placing live 911 calls for routine testing [12].

On Teams the 933 bot returns more than a readback. Microsoft says it echoes the calling line ID, the emergency address or location, and whether the call would be routed automatically to the PSAP or screened first [7]. That last field is worth listening for, because a screened result usually means the address was entered manually or was never confirmed by the person using the client.

When to run the test

Run it when a line is first provisioned, after any address change, after an office move, and after network work that touches the identifiers dynamic location depends on, such as replacing access points or re-addressing a subnet. Microsoft notes that network settings changes can take up to four hours to propagate to Teams clients [7], so a test immediately after an edit may still report the old location.

Set a repeating check

Nothing in the system tells you when a registration has gone stale. People change desks, a satellite office closes, an employee relocates to another state and keeps the same number. A quarterly pass over the location list, paired with 933 tests from a sample of endpoints at each site, catches most of that drift.

The record is only as current as your last edit

A Registered Location is defined as the most recent information the provider holds about where the end user is [2], and nothing audits it after you save. A desk phone carried to a new suite keeps its old address until somebody changes the record, and a 911 call from it carries that old address without flagging anything as wrong.

It does not survive a power or internet outage

VoIP depends on both power and broadband at the premises. The California Public Utilities Commission notes that service during a power outage depends on the provider's underlying facility and that arranging backup power at the site is the customer's responsibility [13]. A correctly registered address does nothing if the phone cannot place the call, which is the argument for keeping an alternative path to 911 at every staffed site.

Validation lag can leave a gap

An address awaiting validation is not the same as an address that routes. Vonage puts validation at up to 30 days, during which an unverified address routes through a national call center before reaching the local PSAP [10]. New construction and recently renumbered streets are where this shows up most, so provision the address ahead of a move rather than on the morning of it.

Registering an address is not the same as Kari's Law compliance

Multi-line telephone systems carry separate obligations. A user has to be able to reach 911 directly from any station equipped with dialing, without an access code, and the system has to send its notification contemporaneously with the call without delaying it [3]. Dispatchable location deadlines for those systems ran January 6, 2021 for on-premises fixed phones and January 6, 2022 for non-fixed and off-premises devices where technically feasible [3][4]. An accurate address in the portal does not satisfy the dial plan or the notification requirement.

A 933 test confirms the record, not the response

The readback tells you what your provider has stored and, on some platforms, how the call would be routed [7][12]. It says nothing about whether responders can find the right door once they reach the building, which is the job the floor and suite detail does [2].