Avaya E911
How E911 works with Avaya environments
Avaya E911 planning has to cover classic phone system estates, cloud contact center agents, Workspaces emergency-location selection, and third-party routing or notification tools.
Workspaces
Agent-selected location
Avaya documents emergency location selection at login for Workspaces users with voice capability.
Callback
Emergency callback
Emergency service callback should reach the user even if their agent state changes.
Hybrid
Legacy plus cloud
Many Avaya estates combine legacy phone system, cloud, gateways, and external E911 platforms.
Avaya Workspaces emergency calling
Avaya documentation says Workspaces users with voice capability can call emergency services without additional prefix digits, and that users select the emergency location that matches their current address from administrator-configured options. The documentation also describes callback behavior if the emergency call disconnects.
- Confirm emergency calling is available for the target region.
- Build administrator-approved emergency locations.
- Train users to select the correct location during activation/login.
- Test callback behavior after agent state changes.
- Document how emergency calls affect agent readiness state.
Avaya phone system and cloud migration issues
Avaya environments often carry long histories: station numbers, sites, analog gateways, contact-center agents, and old emergency routes. When cloud migrations start, those assumptions need to be retested.
- Inventory analog lines, elevator phones, fax/security/alarm lines, and common-area phones.
- Map station/location assumptions before moving to cloud phone.
- Confirm emergency routes for SIP, PRI, and failover trunks.
- Review third-party E911 provider compatibility.
- Test remote-agent and Workspaces behavior separately from desk phones.
Where 911inform and other tools fit
Some Avaya-oriented E911 architectures extend beyond call routing into connected-building and situational-awareness workflows. 911inform positions itself around emergency notification, location discovery, maps, connected building controls, and first-responder context.
- Use routing providers for 911 answering center delivery and dispatchable location.
- Use notification/situational platforms when security teams need richer building context.
- Separate emergency call compliance from incident-response enrichment.
- Validate what the 911 answering center actually receives versus what internal teams receive.