Implementing E911 Dynamic Location Management for Hybrid Remote Workers across EMEA

How-To-Articles
1

Implementing E911 Dynamic Location Management for Hybrid Remote Workers across EMEA

What This Guide Covers

  • Architecting a dynamic emergency services (E911/112) routing solution for remote and hybrid workers.
  • Implementing Dynamic Location Mapping in Genesys Cloud using IP address and LLDP (Link Layer Discovery Protocol) data.
  • Designing a compliant emergency routing strategy that meets Ray Baum’s Act (US) and similar EECC (European Electronic Communications Code) requirements.

Prerequisites, Roles & Licensing

  • Licensing: Genesys Cloud CX 1/2/3.
  • Connectivity: Genesys Cloud Voice or BYOC Cloud with an E911-compliant carrier (e.g., Bandwidth, West, or regional P-CSCF).
  • Permissions:
    • Telephony > Location > Add/Edit
    • Security > Division > View

The Implementation Deep-Dive

1. The Strategy: The “Dispatchable Location” Challenge

When a remote worker dials 911 (or 112/999 in EMEA), the emergency dispatcher must receive their specific physical location (e.g., “123 Main St, Floor 4, Suite 201”) rather than just the corporate headquarters address. For hybrid workers who move between the office and home, this location must update automatically.

The Strategy:

  1. The Registry: Create a database of “Static Locations” (Offices).
  2. The Discovery: Use the Genesys Cloud Desktop App or WebRTC to capture the agent’s current network metadata.
  3. The Mapping: If the IP matches an office range, use the specific Office Location. If the IP is unrecognized (Home), prompt the user or use their pre-registered “Home Location.”

2. Implementing Network-Based Location Mapping

For users inside the office, you can automate location detection using the network infrastructure.

The Implementation:

  1. Navigate to Admin > Telephony > Locations.
  2. Define your IP Address Ranges for each site/floor.
  3. The Workflow:
    • Agent logs in.
    • Genesys Cloud detects the agent is coming from 10.40.1.0/24.
    • The system automatically associates the interaction with the “London - Level 4” location profile.
  4. The Benefit: If the agent moves their laptop to Level 2, the next emergency call will automatically include the “Level 2” dispatchable address without manual intervention.

3. Handling Remote/Home Workers and Personal Emergency Addresses

For users at home, IP ranges are dynamic and cannot be mapped to physical addresses reliably.

The Strategy:

  1. The Policy: Implement a “Home Location” field in the User Profile.
  2. The Verification: Use an E911 Emergency Routing Service (ERS) like Bandwidth. When the user sets their address, the ERS validates it against the MSAG (Master Street Address Guide).
  3. The Workflow:
    • Agent dials 112.
    • Genesys Cloud sees the user is not in a known “Office” IP range.
    • The system retrieves the user’s homeAddress attribute and passes it as a PIDF-LO (Presence Information Data Format Location Object) in the SIP header to the carrier.

4. Designing Emergency Call Notification Workflows

Regulations often require that on-site security is notified whenever an emergency call is placed from the premises.

The Implementation:

  1. Create a Special Number object for 911/112.
  2. In the Emergency Routing section, configure a “Notification List.”
  3. The Action: Send an immediate SMS or Email to the building security team: “EMERGENCY CALL: Agent John Smith (Ext 5001) has dialed 112 from Level 4, London Office.”
  4. Architectural Reasoning: This allows local first responders to meet the ambulance at the door and direct them to the exact floor, potentially saving critical minutes.

Validation, Edge Cases & Troubleshooting

Edge Case 1: VPN “Location Tunneling”

Failure Condition: A remote worker in Paris is connected via VPN to the London HQ. When they dial 112, the system thinks they are in London because they have a London IP.
Solution: Configure your VPN Client to use “Split Tunneling” for Genesys Cloud traffic, or ensure the Genesys Cloud app is configured to use Native OS Location Services (GPS/Wi-Fi positioning) which overrides the VPN IP.

Edge Case 2: Incomplete Address Data (Missing Unit/Floor)

Failure Condition: The dispatcher receives the street address but doesn’t know the caller is in “Apartment 4B,” causing a delay in entry.
Solution: Enforce Address Validation Rules at the UI level. Do not allow a user to save a “Remote Location” unless the “Unit/Suite” field is populated for multi-dwelling units.

Edge Case 3: Public Wi-Fi (Coffee Shops)

Failure Condition: A user dials emergency services from a public Starbucks.
Solution: This is the most difficult scenario. Most carriers will route these to a National Emergency Call Center (ECRC) where a live operator will verbally ask the caller for their location before transferring to the local PSAP. Ensure your carrier supports this “Fallback VCRC” routing.

Official References