Compliance Without Chaos: What E911 Regulations Really Require and What They Don't

As emergency communications regulations evolve, so too does the pressure on IT and business leaders to “stay compliant.” Unfortunately, this often results in over-compliance—driven not by legal necessity, but by fear, misunderstanding, or aggressive vendor sales tactics.

When it comes to E911 in the United States, two key federal laws—Kari’s Law and the RAY BAUM’s Act—set the baseline for emergency access and dispatchable location in enterprise phone systems. Despite the clarity of the statutes, confusion and vendor misinformation routinely lead organizations to spend tens or hundreds of thousands of dollars on complex, high-maintenance tracking solutions they don’t actually need.

Important Regulatory Note: While this article focuses on U.S. federal E911 requirements, several states have enacted additional rules (such as square-footage or multi-floor thresholds) that may apply to your facilities. Always review both federal and state regulations when designing your E911 architecture.

Let’s break down what federal law actually requires—and how to meet the standard cleanly using infrastructure you already own.

What the Laws Actually Mandate

Kari’s Law Requires:

1. Direct 911 Dialing: Users must be able to dial 911 directly without dialing a prefix (such as 9 for an outside line).
2. On-Site Notification: When a 911 call is placed, the system must send a contemporary notification to designated personnel (e.g., security desk, facilities, or front desk) including the fact that a 911 call occurred, a valid callback number, and the caller’s location information when available.

The RAY BAUM’s Act Requires:

1. Dispatchable Location: Every 911 call must convey a “dispatchable location”—such as the validated street address plus floor, suite, or room identifier—to help first responders locate the caller rapidly.
2. Fixed vs. Non-Fixed Devices: This applies to fixed on-premises telephones and extends to non-fixed or off-premises VoIP devices when technically feasible and economically reasonable.
3. Nomadic User Location Updates: For non-fixed VoIP softphones, providers must offer a straightforward mechanism for users to update their physical location and prompt them to confirm or update it when connecting from a new network.

The “Feasibility” Clause: The Most Overlooked Line in the Law

Here are the exact federal regulatory clauses that aggressive sales pitches frequently omit when discussing non-fixed and dynamic dispatchable location:

“…if technically feasible.” — 47 CFR § 9.11(b)(4)(ii)(A)

“…at a reasonable cost.” — 47 CFR § 9.16(b)(3)(iii)

These clauses are critical.

Businesses are routinely pitched expensive third-party add-ons suggesting that real-time GPS tracking, continuous per-user room triangulation, or complex cardinal-direction floor zoning (North/South/East/West/Northeast/Southwest quadrants on every floor) are legally mandatory for every single device, including mobile apps. They are not.

Keeping employees safe is paramount and represents the true spirit of the law. But burning out your engineering team and overspending your budget on brittle, over-engineered location granularity is not required by federal statute.

Pragmatic E911 Architecture Using Existing Infrastructure

Most modern UCaaS platforms (including Zoom Phone, Microsoft Teams, and Cisco) already include native dynamic E911 capabilities that map locations using your existing network topology:

1. Use IP Subnets for Fixed & Wired Devices

Most enterprises already segment VLANs and IP subnets by building, floor, or wing. Mapping IP subnets to dispatchable locations in your phone system provides an automated, zero-maintenance way to assign accurate floor-level emergency locations whenever a desk phone or wired workstation moves.

2. Use Wireless Access Point (BSSID) Mapping for On-Premises Softphones

Wireless endpoints (laptops and mobile softphones on corporate Wi-Fi) associate with specific Wireless Access Point BSSIDs (MAC addresses). Your wireless LAN controller already knows which APs are mounted on which floors and zones—exporting that AP BSSID inventory into your UC platform automatically tags wireless 911 calls with the correct floor and zone.

3. Leverage Switch / LLDP Chassis & Port Mapping Where Needed

If a site uses flat IP subnets across multiple floors, you can map endpoints by the network switch MAC address or LLDP chassis/port identifier to maintain floor-level dispatchable accuracy without re-IPing the building.

4. Train Remote Workers for Off-Premises Softphones

Remote employees working from home or traveling aren’t tied to corporate switches or APs. Configure your UC client to prompt users to confirm or update their emergency address when an unrecognized external network is detected, and include E911 location confirmation in employee onboarding.

Summary: Compliance Is a Safety Goal—Not a Sales Opportunity

The purpose of Kari’s Law and the RAY BAUM’s Act is to get first responders to people in need quickly. Before buying an expensive third-party E911 overlay, ask three architectural questions:

1. Is this granularity actually required by federal or state statute?
2. Can we achieve the exact same dispatchable-location outcome natively using our existing subnets, Wi-Fi BSSIDs, and UC platform?
3. Are we designing a maintainable safety system, or over-engineering for a vendor sales pitch?

Primary Regulatory References

• Code of Federal Regulations — Title 47, Part 9: 47 CFR Part 9 (FCC Interconnected VoIP 911 Obligations)
• Kari’s Law Act of 2017: H.R. 582 (115th Congress)
• RAY BAUM’S Act of 2018: H.R. 4986 (115th Congress)