Designing E911 Emergency Calling Workflows and Dynamic Location Headers in 3CX

Overview

Key takeaways

• Understand regulatory compliance requirements including Kari's Law (direct dial 911, notifications) and RAY BAUM's Act (dispatchable location).
• Configure emergency routing rules in 3CX to override standard caller ID with location-specific Emergency Response Locations (ERLs).
• Implement Emergency Location Identification Numbers (ELINs) mapped to specific extension ranges or IP subnets.
• Structure SIP outbound parameters to transmit PIDF-LO XML bodies or Geolocation headers to E911 SIP carriers.
• Establish validation workflows using 933 test services without disrupting Public Safety Answering Points (PSAPs).

Prerequisites

• Administrator access to the 3CX Management Console or Web Client Admin area.
• A SIP trunk provider supporting E911 dynamic location passing or ELIN-based lookup (e.g., Bandwidth, Flowroute, Sinch, Intrado).
• Basic knowledge of SIP messaging (INVITE structure, PIDF-LO RFC 5139/6442, Geolocation headers).

Guide

1. section #1

   Regulatory Requirements: Kari's Law and RAY BAUM's Act

   Kari's Law Compliance

   Kari's Law mandates that multi-line telephone systems (MLTS) like 3CX allow users to dial 911 directly without dialing a prefix such as '9' or '0'. Additionally, the system must trigger an immediate notification to internal security or administrative personnel when an emergency call is initiated.

   RAY BAUM'S Act Requirements

   RAY BAUM's Act emphasizes the transmission of a dispatchable location to the PSAP. A dispatchable location includes the validated street address plus additional vital information such as suite, floor, or room number, ensuring emergency responders reach the caller efficiently regardless of whether the endpoint is a desk phone or a softphone application.

   Core Regulatory Checklist

   • Direct Dialing: Ensure no outbound prefix is required for emergency calls.
   • Internal Notifications: Configure real-time email, chat, or audio notifications for administrative staff.
   • Dispatchable Location: Map precise physical locations to callers across all network segments.
2. section #2

   Configuring 3CX Emergency Routing Rules and ELIN Mapping

   Emergency Number Definition

   In 3CX, emergency calls bypass standard outbound rules and are processed by dedicated Emergency Numbers defined under system parameters. Defining '911' and '9911' ensures that accidental prefix dialing still reaches emergency services immediately.

   Extension and Group Overrides

   To provide accurate location context, 3CX allows administrators to override default outbound caller IDs based on extension ranges or groups. Each extension group (e.g., Floor 1, Warehouse, Annex) is assigned a unique Emergency Location Identification Number (ELIN), which is a public DID mapped at the carrier level to a specific Emergency Response Location (ERL).

   Rule Logic Summary

   • Rule Priority: Emergency rules evaluate higher than standard outbound rules.
   • Outbound Caller ID: Dynamically replaced with the group or extension ELIN.
   • Route Redundancy: Primary and secondary SIP trunks configured for emergency fallback.
   textcopy

   3CX Emergency Rule Settings:
   --------------------------------------------------
   Emergency Number: 911
   Calls from Extensions: 100-199 (Floor 1)
   Outbound Caller ID: 15552341001 (ELIN - Floor 1)
   Route 1: Primary E911 SIP Trunk
   Route 2: Secondary Backup Carrier
   --------------------------------------------------
   Emergency Number: 911
   Calls from Extensions: 200-299 (Floor 2)
   Outbound Caller ID: 15552341002 (ELIN - Floor 2)
   Route 1: Primary E911 SIP Trunk

3. section #3

   Handling Remote Workers and Softphone Dynamic Locations

   Softphone and Off-Premise Challenges

   When employees use the 3CX Web Client or Mobile App off-premise, hardcoded ELINs can transmit inaccurate location data to emergency services. Addressing this requires integrating dynamic location tracking mechanisms or enforcing user location prompts.

   E911 Emergency Call Gateways

   Modern E911 providers offer specialized Emergency Call Gateways (ECG) that track off-premise clients via network telemetry (IP subnet, Wi-Fi BSSID, LLDP-MED) or user-reported client location. When a call is placed, the gateway intercepts the SIP INVITE and appends or translates location data prior to PSAP delivery.

   Recommended Best Practices

   • User Prompting: Require softphone users to confirm their location upon changing networks.
   • Nomadic E911 Routing: Route remote extension calls through carriers capable of dynamic HELD/PIDF-LO lookup.
   • Fallback Routing: Force unknown remote locations to an emergency screening center (National Call Center) for manual address verification.
4. section #4

   Structuring SIP Headers for Carrier Location Delivery

   Geolocation Header Architecture

   Some E911 carriers require a SIP Geolocation header pointing to a SIP URI or HTTP location resource. 3CX can be configured using customized SIP trunk templates to pass extension-specific values or custom SIP headers to the carrier.

   PIDF-LO XML Ingestion

   Presence Information Data Format Location Object (PIDF-LO) embeds detailed XML location data inside the SIP INVITE body (multipart/mixed). Advanced session border controllers (SBCs) or specialized gateways positioned between 3CX and the provider can inject PIDF-LO bodies into the outgoing SIP stream based on source IP or SIP user agent.

   Key SIP Header Constructs

   • Geolocation: Contains the URI referencing the location object.
   • P-Asserted-Identity / From: Populated with the precise ELIN DID.
   • User-Agent: Used by downstream SBCs to apply device-specific location rules.
   sipcopy

   INVITE sip:911@e911.carrier.com:5060 SIP/2.0
   Via: SIP/2.0/UDP 192.168.1.10:5060;branch=z9hG4bK-3cx-e911
   From: "Floor 2 Suite 200" <sip:15552341002@e911.carrier.com>;tag=a1b2c3d4
   To: <sip:911@e911.carrier.com>
   Call-ID: 84739201734918234@192.168.1.10
   CSeq: 101 INVITE
   Contact: <sip:101@192.168.1.10:5060>
   Geolocation: <http://e911-provider.com/loc/loc_id_98234>;inserted=by-network
   Content-Type: application/sdp

5. section #5

   Testing, Validation, and Maintenance Workflows

   Utilizing 933 Automated Test Services

   To comply with regulatory standards and ensure call flows function without disturbing emergency personnel, administrators should utilize 933 automated testing numbers provided by E911 carriers. Calling 933 plays back the caller ID, detected ELIN, and associated address on file.

   Scheduling Periodic Audits

   Physical office moves, extension reassignments, and subnet updates can create discrepancies between internal endpoints and registered ERLs. Implementing quarterly audit workflows ensures location database integrity.

   Operational Verification Steps

   • Dial 933: Test from every phone subnet and extension group to confirm correct ELIN delivery.
   • Verify Notifications: Confirm administrative email and chat alerts trigger instantly upon dialing.
   • Carrier Database Sync: Reconcile national Master Street Address Guide (MSAG) records against internal network maps.

Further reading

• 3CX Official Documentation: Configuring Emergency Numbers
• FCC Advisory: Implementation of Kari's Law and RAY BAUM'S Act
• RFC 5139: Revised Civic Location Format for Internet Protocol Location Objects (PIDF-LO)
• RFC 6442: Location Conveyance in SIP