SECURITY BREACH? CALL 888.234.5990 EXT 9999

BLOG ARTICLE

Is Your Organization’s Telephony Deployment E911 Compliant? – Part 1

Table of Contents

Introduction

For IT leaders, there’s no shortage of exciting projects—rolling out new technology, automating workflows, and driving innovation. Yet alongside these transformative efforts come essential but less glamorous responsibilities: documentation, audits, updates, and compliance checks. 

E911 compliance often falls into this second category. While it may not inspire the same enthusiasm as a major rollout, achieving compliance delivers peace of mind, safeguards employees, and protects your organization from legal risk. 

In this first part of our series, we’ll break down the regulations that define E911 compliance in the United States and outline what organizations need to consider when evaluating their telephony deployments. 

Understanding E911 Compliance

Enhanced 911 (E911) regulations in the United States are designed to ensure that anyone who dials 911 from a workplace phone system can be quickly and accurately located in an emergency. These rules are governed by the Federal Communications Commission (FCC) and shaped by two cornerstone regulations: 

  • Kari’s Law – Requires direct 911 dialing (no prefixes), on-site notification when an emergency call is placed, and improved accessibility for all users. 
  • RAY BAUM’S Act – Mandates that “dispatchable location” information (street address, floor, room, or suite) be transmitted to first responders for faster, more accurate emergency response. 

Key Compliance Requirements

Organizations must ensure their systems meet the following expectations: 

  • Direct 911 dialing without prefixes or access codes. 
  • Automatic notifications sent to designated staff when an emergency call is made. 
  • Complete dispatchable location details (address, floor, area, and callback number). 
  • Callback number functionality so emergency services can reconnect if a call drops. 
  • Routing of 911 calls directly to the appropriate Public Safety Answering Point (PSAP), where technically possible. 
  • User capability to input or update location details if the system cannot automatically determine them. 

 

Who Is Responsible?

E911 compliance is not limited to a single stakeholder group. Responsibility spans across: 

  • Manufacturers – PBX vendors such as Cisco, Avaya, Microsoft, and others. 
  • Installers – Service providers, managed service providers, or internal IT staff implementing the system. 
  • Managers – Telecom teams and IT administrators responsible for maintaining compliance on an ongoing basis. 

Steps Toward Compliance

For any voice or PBX system, the implementation path generally follows six high-level steps:

    1. Verify Local Regulations

    • Understand state and municipal requirements in addition to federal mandates. 

    2. Gather Information for Each Location

    • Physical addresses (building, floor, suite, wing). 
    • Outbound phone numbers. 
    • Network details (subnets, switches, wireless access points, public IPs). 
    • Notification recipients (individuals or groups). 

    3. Determine the Implementation Path

    • Select software or service providers. 
    • Identify implementation partners or internal owners. 
    • Design a compliant solution based on collected information. 

    4. Deploy the Solution

    • Configure systems, SIP trunks, and phone number mapping. 
    • Apply required settings across users and groups. 

    5. Validate the Setup

    • Confirm that all endpoints can transmit accurate location data. 
    • Perform controlled test calls (both to test numbers and live PSAPs where coordinated). 
    • Verify internal notification workflows function correctly. 

    6. Establish Ongoing Maintenance

    • Assign ownership with a clear responsibility matrix. 
    • Implement periodic reviews and updates. 
    • Continuously update all systems to reflect location or network changes. 

    What’s Next

    This post outlined the regulatory foundation and implementation path for E911 compliance. In the next part of this series, we’ll dive into the specifics of deploying an E911 solution within Microsoft Teams Voice, including configuration, best practices, and validation steps.

    SHARE THIS

    Let's get problem-solving