Compliance Guide

VoIP E911 Compliance

8 min read  ·  Updated April 2026

E911 is not optional for business VoIP. The FCC requires that all multi-line telephone systems provide Enhanced 911 with accurate location information. Non-compliance carries significant liability. Here is what is required and how to implement it.

In this guide

1. What Enhanced 911 requires

Basic 911 routes the call to a Public Safety Answering Point (PSAP). Enhanced 911 (E911) adds automatic transmission of the caller location and callback number to the PSAP dispatcher.

For VoIP and business phone systems, E911 requires:

2. RAY BAUM Act and Kari Law

Kari Law (effective February 2020): Requires that users of multi-line telephone systems can directly dial 911 without first dialing an access code (no 9-1-1 or 8-1-1 prefix required). The system must also notify a central location when 911 is dialed.

RAY BAUM Act (phased compliance 2021-2022): Requires dispatchable location be automatically provided with 911 calls. Location must be specific enough for responders to find the caller — floor and room number, not just building address.

These laws apply to:

3. E911 on SIP trunks

Most SIP trunk providers offer E911 service with DID numbers. To configure E911 on a SIP trunk:

  1. Register your address with the carrier: Log into the carrier portal and associate each DID with a physical service address
  2. Configure emergency routing: Ensure 911 calls are routed to the correct PSAP based on the registered address
  3. Set caller ID for 911: The From header on 911 calls must contain a valid DID that the carrier has registered with the PSAP
  4. Test with 933: Call 933 from each extension — it reads back the location information registered for that number
; Asterisk dialplan - route 911 calls ; Must NOT require any prefix to reach 911 exten => 911,1,NoOp(Emergency call from ${CALLERID(num)}) same => n,Set(CALLERID(num)=YOUR_E911_DID) same => n,Dial(PJSIP/911@emergency-trunk) same => n,Hangup() ; Also handle 9911 for users who dial 9 first exten => 9911,1,Goto(911,1) ; Internal notification exten => 911,1,System(notify-security.sh ${CALLERID(num)}) same => n,Dial(PJSIP/911@emergency-trunk)

4. E911 on UCaaS platforms

PlatformE911 Configuration
Microsoft TeamsTeams Admin Center → Emergency addresses. Assign addresses to users and network sites. Use dynamic emergency calling for location detection.
Zoom PhoneAdmin Portal → Emergency service addresses. Configure per user and per network location. Zoom supports dynamic E911 via Intrado/West integration.
RingCentralAdmin Portal → Emergency Response locations. Each user needs an assigned emergency address.
8x8Account Manager → Emergency locations. Assign per user and per site.

Dynamic E911 for remote workers

Remote workers present a major E911 challenge — their location changes and the registered address may be wrong. Dynamic E911 solutions (Intrado, West, RedSky) detect the user location via network information and update the PSAP database automatically. Most enterprise UCaaS platforms integrate with these services.

5. Testing E911

Test line 933: Call 933 from each extension. A recording plays back the name, address, and callback number registered for that line. This tests that your registration is correct without placing a real 911 call.

What to verify:

Do not call 911 to test — this wastes PSAP resources and may result in fines. Use 933 or coordinate with your carrier for supervised testing.

6. Liability and compliance

Non-compliance with Kari Law and RAY BAUM Act carries serious consequences:

Document your E911 implementation: keep records of address registrations, testing dates, and system configurations. If an emergency occurs and 911 failed, documentation of your compliance efforts is critical.

Review E911 configurations when: employees move desks or offices, the company moves locations, new remote workers are added, phone system is upgraded, or SIP trunk provider changes.

Frequently asked questions

What is E911 and is it required for business VoIP?

E911 (Enhanced 911) requires business VoIP systems to automatically transmit caller location and callback number to PSAPs when 911 is dialed. In the US, Kari Law (2020) and RAY BAUM Act (2021-2022) make E911 compliance mandatory for all multi-line telephone systems including UCaaS platforms, SIP trunks, and hosted PBX. Non-compliance carries FCC fines and civil liability.

How do I set up E911 on a SIP trunk?

Set up E911 on a SIP trunk by registering each DID with a physical service address in your carrier portal. Configure your Asterisk dialplan to allow direct 911 dialing without prefix and set the correct E911 DID as caller ID on emergency calls. Test using 933 which reads back the registered location information. Assign specific E911 DIDs for each building or floor to provide accurate dispatchable location.

What does the RAY BAUM Act require for VoIP?

The RAY BAUM Act requires that dispatchable location be automatically transmitted when 911 is called from a multi-line telephone system. Dispatchable location means a street address plus additional information (floor number, room number, building wing) specific enough for first responders to find the caller. A building street address alone is not sufficient for multi-story or multi-building campuses.

Need to verify your VoIP 911 configuration?

SIPSymposium analyzes SIP traces from emergency calls to verify correct caller ID, routing, and that 911 calls are not going to wrong destinations.

Analyze my trace Create free account
Related guides