Understanding VoIP with 911: Essential Information for Users (2026)

VoIP 911 calls work fundamentally differently from traditional landline emergency calls, and understanding those differences could determine whether help reaches you in time. When you dial 911 on a VoIP phone, your call travels through an internet-based routing system rather than a dedicated copper circuit, which introduces location accuracy challenges, power dependency risks, and routing delays that simply do not exist with conventional landlines. This guide breaks down exactly how 911 calls on VoIP systems are processed, what federal regulations govern E911 compliance, what you and your team must do before an emergency occurs, and what actions to take when seconds count. Whether you are an IT manager deploying a cloud phone system for 500 employees or a small business owner using a residential VoIP line, this information applies directly to your situation.

Traditional 911 vs. VoIP 911: A Side-by-Side Breakdown

To understand why VoIP 911 requires special attention, it helps to understand how traditional emergency calling works and where VoIP diverges from that model.

When someone dials 911 on a traditional Public Switched Telephone Network (PSTN) landline, the call is routed directly to the nearest Public Safety Answering Point based on the physical circuit serving that address. The PSAP dispatcher sees your Automatic Number Identification (ANI) and Automatic Location Identification (ALI) data appear on their screen automatically, typically within seconds. The address tied to that phone line is stored in the Local Exchange Carrier’s database and fed directly to the PSAP. No manual input is required from the caller. The system is deterministic: one physical line equals one fixed address.

VoIP phone calls travel as data packets over the internet. Your VoIP provider assigns you a phone number, but that number is not physically tied to any specific location. You can plug a VoIP adapter into any broadband connection in the country and make calls using the same number. That portability is the core selling point of VoIP technology, and it is also the core challenge for 911 routing.

When you dial 911 on a VoIP line, your call is first sent to your VoIP provider’s infrastructure, which then queries an E911 database to find the PSAP associated with your registered service address. The call is then forwarded to that PSAP or, in many cases, to a national emergency call center operated by a third-party provider such as West Safety Services, Bandwidth, or Intrado. That call center either transfers you to the correct local PSAP or relays your information to local dispatchers. This intermediary step adds latency, introduces additional failure points, and means the PSAP may not receive your location data automatically the way they would with a landline call.

Feature	Traditional PSTN 911	VoIP E911
Call Routing Path	Direct to local PSAP via circuit	VoIP provider, then E911 database, then PSAP or emergency call center
Location Detection	Automatic via ALI database	Based on registered service address; may require manual confirmation
Power Dependency	Low (POTS lines often self-powered)	High (requires router, modem, and device power)
Portability	Fixed to physical address	Usable from any internet connection globally
Dispatchable Location	Automatically transmitted	Requires proper configuration and regular updates
Call Center Intermediary	None	Often present, especially for non-native VoIP
Regulatory Framework	FCC Part 68, local tariffs	FCC VoIP E911 rules, Kari’s Law, RAY BAUM’S Act

For a deeper look at how VoIP technology fits into broader communications planning, the guide on UCaaS vs VoIP: Decoding the Key Differences for Your Business Communications provides useful context on how these platforms are architected and where emergency calling responsibilities fall within each model.

How VoIP 911 Call Routing Actually Works

The Internal Routing Path Step by Step

Understanding VoIP 911 internal routing is essential for IT managers, because each step in the chain represents a potential point of failure or misconfiguration. Here is what happens technically when a user dials 911 from a VoIP device.

First, the SIP client or IP phone sends a SIP INVITE to the VoIP provider’s session border controller (SBC). The provider’s system recognizes that 911 has been dialed and triggers a special routing path separate from normal call handling. The provider queries its Emergency Services Routing Proxy (ESRP) or contacts a third-party emergency services aggregator. That aggregator checks a database called the Automatic Location Information system to find the registered address for the originating device. Based on that address, the ESRP selects the appropriate PSAP and routes the call there, along with whatever location data is available.

If the E911 aggregator cannot identify a specific PSAP, or if the registered address is incomplete or incorrect, the call may be routed to a national emergency call center operated by companies like Bandwidth Inc., Intrado (formerly West Safety), or Lumen Technologies. These centers have trained operators who gather your location verbally and transfer the call to the correct local PSAP. This is why some callers notice a brief delay or an extra operator before reaching a local dispatcher.

Why the 911 Dispatcher May Not See Your Location

One of the most critical differences between 911 calls on VoIP and traditional 911 is that the dispatcher screen may not automatically populate with your address. In traditional telephony, the ALI database query happens at the PSAP level and displays your address and callback number on the dispatcher’s console before they even answer. With VoIP, whether that data appears depends on several factors: whether your provider has properly provisioned your E911 record, whether the PSAP has been upgraded to accept digital location data, and whether your registered address is current and accurate.

Many PSAPs across the United States are still running older equipment that was designed for PSTN calls. When a VoIP call arrives through an emergency call center intermediary, the location data may be transmitted verbally from the call center operator rather than appearing automatically on the dispatcher’s screen. This introduces human error into the process and adds precious seconds to response time.

Softphones, Remote Workers, and the Location Problem

The location challenge becomes significantly more complex when users are working remotely or using softphone applications on laptops or mobile devices. A softphone installed on an employee’s laptop can travel with them from home to a coffee shop to a hotel conference room, and the E911 system has no automatic way to know which of those locations is current unless the user explicitly updates their location or the platform uses dynamic location services.

Modern UCaaS platforms including Microsoft Teams Phone, Cisco Webex Calling, RingCentral, and Zoom Phone have all introduced dynamic E911 features that attempt to address this problem. Microsoft Teams uses a feature called Location-Based Routing combined with the Emergency Location Identification Number (ELIN) framework to determine which network a device is connected to and match it against a location database. Zoom Phone offers emergency address auto-detection using network-based location identification. RingCentral provides dynamic E911 through a partnership with Intrado, using a software client that detects the user’s current network and updates their emergency address accordingly. These tools work well in controlled corporate network environments where wireless access points and network segments can be mapped to specific physical locations, but they require substantial initial configuration by IT teams.

Location Accuracy: Your Most Important E911 Responsibility

Why Your Registered Address Is the Foundation of E911

Every VoIP E911 system ultimately depends on a registered service address. This is the address your VoIP provider submits to the E911 database on your behalf, and it is the address that emergency services will receive when you dial 911. If that address is wrong, outdated, or incomplete, help will be sent to the wrong location. There is no automatic fallback, and there is no way for a dispatcher to independently verify your location during the call unless you tell them.

For residential users, the registered address should be your primary home address. For business users, every device, every extension, and every softphone profile should have a specific physical location registered, down to the floor and suite number where possible. This is not a one-time setup task. It is an ongoing operational responsibility that needs to be built into your IT and HR processes.

Common Reasons Location Data Fails to Reach Dispatchers

Several specific technical and administrative failures can prevent accurate location data from reaching a 911 dispatcher. Understanding these failure modes is the first step toward eliminating them.

• Stale address records: The most common cause. An employee moved offices, a company relocated, or a home user moved without updating their VoIP service address. The E911 database still points to the old location.
• Unregistered devices: A new IP phone or softphone was provisioned for a user but the E911 address for that specific device or extension was never configured. Some platforms require per-device E911 registration separate from the main account.
• Softphone portability: A user is running a softphone on a laptop and is working from a location different from their registered address, with no dynamic location service enabled.
• Network address translation (NAT) issues: The device is behind a NAT gateway, and the emergency services routing system cannot accurately determine which physical network segment the call is originating from.
• PSAP technical limitations: The local PSAP has not been upgraded to process digital location data, so even correctly transmitted location information may not display on the dispatcher’s console.
• VoIP provider misconfiguration: The provider has not correctly linked the account’s service address to the E911 database, or the database record contains a formatting error that prevents correct PSAP matching.

How to Audit and Maintain Your E911 Address Records

For businesses, E911 address management should follow a formal process rather than being handled ad hoc. Here is a practical framework for IT managers and procurement leads to implement.

1. Inventory every endpoint: Create a complete list of every VoIP device, softphone license, and virtual extension on your system. Include the physical location of each device at the granularity of building, floor, and room or workstation.
2. Verify E911 records in your provider’s admin portal: Log into your UCaaS or VoIP admin console and confirm that each device or user profile has an accurate emergency address assigned. Most enterprise platforms including RingCentral MVP, Microsoft Teams Admin Center, and Cisco Unified Communications Manager have dedicated E911 configuration sections.
3. Conduct test calls: Work with your E911 provider to conduct periodic test calls to verify that location data is correctly transmitted and received by the appropriate PSAP. Document the results, including which address appeared on the dispatcher’s system.
4. Build address updates into HR workflows: Any time an employee changes offices, works remotely permanently, or the company opens or closes a location, trigger an automatic E911 address review process.
5. Implement dynamic E911 for remote and mobile users: Deploy a dynamic location solution such as Microsoft Teams Emergency Location Integration with network topology mapping, or a third-party tool like RedSky E911 or Bandwidth Dynamic Location Routing for softphone users.
6. Schedule quarterly audits: Set a calendar reminder to audit E911 records every 90 days. Cross-reference your device inventory with your E911 database records to catch any discrepancies.

Power and Internet Dependency: The Hidden Risk in VoIP 911

Why VoIP Fails When Traditional Phones Often Do Not

Plain Old Telephone Service (POTS) landlines draw their operating power directly from the telephone network itself through the copper loop. This means that during a power outage, a traditional landline phone with no external power requirements often continues to work. Many households and businesses discovered this during major storms or infrastructure events when cell towers were congested and internet was down, but the old landline kept working.

VoIP has no equivalent self-powering mechanism. A VoIP phone system requires at minimum: an active broadband internet connection, a powered modem, a powered router or switch, and a powered VoIP phone or the device running a softphone. If any single one of those components loses power, your ability to call 911 via VoIP is eliminated. In a serious emergency, the very conditions that make 911 necessary, such as a fire, a severe storm, or a medical crisis, are also the conditions most likely to cause power or internet outages.

Mitigation Strategies for Power and Internet Outages

IT managers and facility planners need to treat VoIP 911 continuity as a genuine infrastructure risk and plan accordingly. The following measures significantly reduce the probability that a power or internet failure will prevent emergency calls.

• Uninterruptible Power Supply (UPS) for network equipment: Deploy UPS units on every modem, router, switch, and VoIP gateway in the building. Size the UPS to provide at minimum 4 hours of runtime at full load. APC, Eaton, and CyberPower all offer rack-mounted units appropriate for network closets, with prices ranging from approximately $300 for small office units to over $2,000 for larger deployments.
• Cellular backup for internet connectivity: Deploy an LTE or 5G failover router such as the Cradlepoint E3000 or Peplink MAX BR1 Pro to maintain internet connectivity during broadband outages. These devices automatically switch traffic to a cellular connection when the primary circuit fails, with monthly cellular plan costs typically ranging from $40 to $150 per month depending on data requirements.
• Maintain at least one cellular phone per floor or zone: Ensure that designated emergency wardens or front desk staff carry a fully charged cellular phone at all times. Cell phones can reach 911 regardless of VoIP system status, and they automatically provide the cell tower’s general location to dispatchers even without GPS.
• Post emergency backup procedures in visible locations: Place laminated cards near main reception areas, break rooms, and common areas that instruct staff to use a cell phone if the VoIP system is unavailable.
• Consider retaining at least one POTS line: In locations where emergency calls are critical, such as a security desk, reception, or server room, maintaining a single traditional POTS line as a backup 911 circuit is still a viable and relatively inexpensive option.

The Federal Regulatory Framework: Kari’s Law and the RAY BAUM’S Act

Kari’s Law: Direct 911 Dialing Without a Prefix

Kari’s Law was signed into federal law in February 2018 following the tragic death of Kari Hunt Dunn, who was murdered in a hotel room in 2013. Her nine-year-old daughter attempted to call 911 multiple times but did not know she had to dial 9 first to get an outside line on the hotel’s multi-line telephone system. The call never connected.

Kari’s Law (47 U.S.C. 623) applies to multi-line telephone systems (MLTS) manufactured, imported, sold, leased, or installed in the United States on or after February 16, 2020. It has two core requirements. First, users must be able to dial 911 directly without any prefix, access code, or trunk seizure digit. Second, when a 911 call is placed from an MLTS, the system must simultaneously send a notification to a central location that is capable of receiving and acting on the notification, such as a front desk, security station, or building management system. This notification must include the caller’s extension or location information when technically feasible.

For businesses using VoIP-based MLTS platforms including Cisco Unified Communications Manager, Avaya Aura, Microsoft Teams Phone System, or any hosted UCaaS solution, Kari’s Law compliance is a hard legal requirement, not a best practice. Non-compliance exposes the organization to FCC enforcement action and significant civil liability.

RAY BAUM’S Act: Dispatchable Location Transmission

The RAY BAUM’S Act, passed as part of the Consolidated Appropriations Act of 2018 and named after Oregon Representative Ray Blaine Baum, goes further than Kari’s Law by addressing the quality of location information transmitted with every 911 call. The Act directs the FCC to adopt rules ensuring that 911 calls include a dispatchable location, defined as a location that consists of the street address of the calling party and additional information such as room number, floor number, or similar information necessary to adequately identify the location of the calling party.

The FCC implemented RAY BAUM’S Act requirements in phases. As of January 6, 2021, fixed MLTS on-premises deployments must transmit dispatchable location with every 911 call. For non-fixed MLTS environments, including cloud-hosted systems and softphone deployments, the deadline for compliance was January 6, 2022. This means that if you are running a UCaaS platform today and your remote workers’ softphones are not transmitting dispatchable location data with 911 calls, you are currently out of compliance with federal law.

The practical implication for IT teams is significant. Simply configuring a street address for each user is not enough. You need floor and suite information, and for dynamic environments, you need a technical system capable of providing that information automatically based on the user’s current network location. This is addressed in more detail in the section on dynamic E911 solutions above.

For additional background on how these regulations intersect with broader VoIP compliance considerations, the article on Understanding VoIP with 911: Safety, Features, and Regulations covers the regulatory landscape in additional depth.

FCC Enforcement and the Cost of Non-Compliance

The FCC has enforcement authority over both Kari’s Law and the RAY BAUM’S Act requirements for MLTS operators. Penalties can include monetary forfeitures, and in cases of serious harm attributable to non-compliance, organizations may face significant civil liability. Beyond regulatory enforcement, consider the reputational and human cost of a situation in which a 911 call from your facility fails to connect or fails to transmit the correct location.

Procurement leads evaluating VoIP and UCaaS platforms should require vendors to provide written documentation of their E911 compliance capabilities, including which specific RAY BAUM’S Act scenarios they support, what dynamic location technologies they offer, and whether they have formal partnerships with certified E911 service providers. This documentation should be part of your standard RFP process.

Critical Actions to Take During a 911 Call on VoIP

Stay on the Line Until Dismissed

The single most important behavioral rule for 911 calls on VoIP systems is to remain on the line until the dispatcher explicitly tells you it is acceptable to hang up. Unlike traditional landlines, where the dispatcher can call back a disconnected number and be confident it will ring at the same physical address, a VoIP callback may reach a voicemail system, a phone that has gone offline, or a device that is no longer in the caller’s hands. If you disconnect before the dispatcher has confirmed your location and the nature of the emergency, you may create a situation in which emergency responders are dispatched to an uncertain location with incomplete information.

Immediately State Your Physical Location

Do not assume the dispatcher has your address. The very first thing you should say after the dispatcher answers is your complete physical location, including street address, building name if applicable, floor number, and room or suite number. Follow that with your callback number and then the nature of the emergency. This sequence ensures that even if the call is subsequently disconnected, the dispatcher has the minimum information needed to send help to the correct location.

If the Call Drops, Call Back Immediately

VoIP calls are subject to packet loss, jitter, and session timeouts that can cause unexpected disconnections. If your 911 call drops before the dispatcher releases you, call 911 again immediately. Do not wait. When reconnected, immediately identify yourself, state that you are calling back after a disconnection, and restate your location. If your VoIP service is also unavailable at that point, use a cell phone, a neighbor’s phone, or any other available communications device.

What Information to Have Ready

Prepare the following information before any emergency occurs, so that you or any member of your household or staff can provide it quickly under stress.

• Your complete street address including apartment, suite, or unit number
• The floor number if you are in a multi-story building
• Building name and nearest major cross street if the address may be ambiguous
• Your callback number, which is the number associated with the VoIP device you are calling from
• A brief, clear description of the emergency type: medical, fire, intrusion, hazmat, etc.
• Number of people involved and whether anyone is injured or in immediate danger
• Any access information that may be needed: gated entry codes, elevator keys, locked doors

Educating Employees, Household Members, and Guests

Why Training Is a Mandatory Component of VoIP Deployment

Technical E911 configuration alone is not sufficient to ensure emergency call effectiveness. Every person who might use a VoIP phone in your environment needs to understand the limitations of VoIP 911 and what they are expected to do differently compared to a traditional landline. This includes full-time employees, part-time staff, contractors, visitors, household members, and overnight guests in hospitality settings.

A surprising number of VoIP deployments treat E911 training as an afterthought, buried in a user manual that nobody reads. In enterprise environments governed by Kari’s Law and RAY BAUM’S Act, this approach creates real legal exposure in addition to the obvious safety risk. E911 education should be a mandatory component of new employee onboarding, part of your annual safety training program, and reviewed whenever a significant change to the phone system occurs.

Core Messages Every VoIP User Must Understand

The training content does not need to be technically complex. The following points cover everything a typical user needs to know to respond correctly in an emergency.

• VoIP 911 calls may be routed through an intermediate call center before reaching local dispatchers. There may be a brief delay or an additional operator on the line.
• Your location may not appear automatically on the dispatcher’s screen. Always state your full address, floor, and room number as your first words after the dispatcher answers.
• If the internet or power is out, your VoIP phone may not work. Know where the nearest cellular phone is and how to access it.
• Do not hang up until the dispatcher tells you to. If the call drops, call back immediately using any available phone.
• Your registered address on file with the VoIP provider determines where help is sent. If you are working from a location other than your registered address, be especially explicit about stating your current physical location.

Using Warning Labels and Visual Reminders

Physical warning labels placed on or immediately adjacent to VoIP phones serve as a constant, passive reminder of E911 limitations. Many VoIP providers supply these labels or make printable templates available. The label should include a brief note that this phone uses VoIP service, that the caller must state their location when dialing 911, and that the phone requires power and internet to function. For hospitality environments including hotels, hospitals, and university dormitories, these labels are especially critical because guests and visitors have no prior familiarity with the specific phone system in use.

For organizations deploying large numbers of VoIP endpoints, labeling can be incorporated into your infrastructure documentation process. The guidance in Mastering ANSI/TIA-606: Essential Guidelines for Telecommunications Infrastructure Labeling provides a useful framework for systematically labeling telecom infrastructure, which can be extended to include E911 status indicators on individual devices.

Enterprise E911 Compliance: Operationalizing Your Deployment

Building E911 Into Your UCaaS Implementation Plan

For enterprise IT managers, E911 compliance is not a setting you enable once during platform deployment and then forget. It is a continuous operational process that requires integration with your HR systems, facility management, network infrastructure, and vendor relationships. The organizations that handle this best treat E911 as a workstream within their broader UC program management, with a named owner, documented procedures, and regular review cycles.

When evaluating UCaaS platforms for enterprise deployment, E911 capability should be a primary evaluation criterion, not a secondary consideration. Ask vendors specifically how their platform handles the following scenarios: a user connects their softphone from an unrecognized network, a new office is opened and devices are provisioned before the E911 address is registered, an employee works permanently from home in a state different from the company’s main office, and a visitor uses a conference room phone from a floor different from the registered address for that device.

The answers to those questions will reveal the actual maturity of the vendor’s E911 implementation. For a broader view of how enterprise communications platforms compare on these dimensions, the analysis of CCaaS platforms and their enterprise capabilities offers useful comparative context.

Third-Party E911 Solutions for Complex Environments

Organizations with complex multi-site, multi-tenant, or heavily remote-work environments often need to supplement their UCaaS platform’s native E911 capabilities with a dedicated third-party E911 solution. Several specialized providers operate in this space.

RedSky E911 (now part of Bandwidth) offers a cloud-based E911 platform that integrates with Cisco, Microsoft, Avaya, and other major UC platforms. It provides dynamic location services, per-device address management, and dispatchable location transmission. Pricing is typically on a per-user per-month basis, ranging from approximately $1.50 to $3.50 per user per month depending on the platform and feature set.

Intrado Emergency Routing Service (ERS) is one of the largest E911 aggregators in the United States, providing PSAP routing for a large percentage of all VoIP 911 calls in the country. Many UCaaS vendors use Intrado as their backend E911 routing provider. Organizations can also integrate directly with Intrado for custom enterprise E911 deployments.