Configuring E911 Dynamic Location Tracking for Remote Softphone Users

How-To-Articles
1

Configuring E911 Dynamic Location Tracking for Remote Softphone Users

Executive Summary & Architectural Context

When a contact center agent sits in a corporate office, dialing 911 (or 112/999) is straightforward: the PBX sends the physical address of the office building to the PSAP (Public Safety Answering Point).

In a Work-From-Home (WFH) environment, emergency routing becomes a massive legal liability. If an agent working from their apartment in Texas suffers a medical emergency and dials 911 through their Genesys Cloud softphone, the call might route out of a centralized SIP trunk in New York. The 911 operator will see the New York corporate address and dispatch an ambulance 1,500 miles away from the dying agent. This is a direct violation of Kari’s Law and the RAY BAUM’S Act in the United States.

The architectural solution is Dynamic E911 Location Tracking. This masterclass details how to configure Genesys Cloud to dynamically force WFH agents to define their physical location, and how to pass that granular location metadata (PIDF-LO) to a certified Emergency Routing Service Provider (ERSP).

Prerequisites, Roles & Licensing

  • Licensing: Available on all Genesys Cloud CX tiers.
  • Roles & Permissions: Telephony > Location > Edit, Telephony > Site > Edit.
  • Platform Dependencies:
    • A certified E911 Provider (e.g., Intrado, Bandwidth, RedSky) integrated via BYOC, or Genesys Cloud Voice (which includes native E911 support).

The Implementation Deep-Dive

1. Activating the Location Feature

Genesys Cloud must be configured to prompt users for their address.

  1. Navigate to Admin > Telephony > Sites.
  2. Select the Site assigned to your remote workers.
  3. Go to the Location tab.
  4. Toggle Require users to define their location to ON.
  5. Logic: The next time the agent logs into the Genesys Cloud web app or desktop app, the UI will freeze. A modal window will appear demanding they enter their current street address, apartment number, and city. They cannot access the softphone until this is completed.

2. Validating the Address (MSAG Compliance)

A user cannot simply type “My House in Texas.” The address must be mathematically validated against the Master Street Address Guide (MSAG).

  1. When the agent types their address, Genesys Cloud performs an API dip against an address validation service.
  2. If the address is invalid (e.g., “123 Fake Street”), the system will prompt them to correct it.
  3. If valid, Genesys Cloud stores this physical address as a temporary Location object bound specifically to the agent’s WebRTC session.

3. Routing the Emergency Call (PIDF-LO)

When the agent dials 911, standard Outbound Routing takes over, but the signaling changes drastically.

  1. Create a Number Plan that matches ^911$ as an Emergency Number.
  2. Create an Outbound Route for Emergency calls, pointing to your E911-capable SIP Trunk (e.g., Intrado).
  3. The SIP Signaling (PIDF-LO): When Genesys Cloud fires the SIP INVITE to the trunk, it does not just send the Caller ID. It injects a highly complex XML payload into the SIP headers called a PIDF-LO (Presence Information Data Format Location Object).
  4. This XML contains the exact validated street address the agent entered in Step 1.
  5. The E911 SIP carrier receives the INVITE, extracts the XML, ignores the Caller ID, and routes the call to the precise municipal PSAP responsible for that specific street address.

Validation, Edge Cases & Troubleshooting

Edge Case 1: The Nomad Agent (Coffee Shop Working)

An agent logs in at their apartment at 9:00 AM (entering their apartment address). At 12:00 PM, they take their laptop to a coffee shop. If they dial 911 at 1:00 PM, the ambulance will go to their apartment.

  • The Trap: The Genesys Cloud browser client does not continuously poll the laptop’s GPS. It relies entirely on the location the agent typed during their initial login session.
  • Mitigation: Agents must be explicitly trained via corporate policy to update their Emergency Location in the Genesys Cloud UI settings (Top right corner > Profile > Emergency Location) every time they change physical locations.

Edge Case 2: BYOC Premise / Local Edges

If you are using physical Genesys Edges deployed in your own data center (BYOC Premise) instead of the Cloud, you have a massive routing problem.

  • Troubleshooting: Local Edges connect to your local telecom carrier (e.g., a PRI or SIP trunk provided by AT&T). Standard local carriers often do not support PIDF-LO XML payloads. If the Edge sends the XML, the carrier drops it, and defaults to the billing address of the data center.
  • Solution: For BYOC Premise environments with WFH agents, you must purchase a dedicated, specialized E911 SIP trunk (like RedSky) that is explicitly engineered to parse PIDF-LO data, and route all 911 traffic out that specific trunk, bypassing your standard local carrier.

Official References