Cisco emergency calling
Cisco E911: CUCM, CER, Webex, and the provider layer
Cisco estates often mix CUCM, Cisco Emergency Responder, Webex Calling, desk phones, Jabber/Webex clients, gateways, and third-party E911 providers. The design has to account for all of them.
CUCM
Route plan matters
Emergency route points, partitions, calling search spaces, route patterns, and gateways must be intentionally designed.
CER
emergency response location and emergency callback identifier
Cisco Emergency Responder maps phones to Emergency Response Locations and callback identifiers.
Webex
Cloud integration
Webex Calling enhanced emergency calling can use E911 providers and dynamic location patterns.
CUCM and Cisco Emergency Responder
Cisco Emergency Responder augments CUCM by tracking caller location, routing emergency calls based on location, giving 911 answering centers location/callback context, and alerting on-site responders. In traditional Cisco environments, this usually means designing emergency response locations, emergency callback identifiers, route patterns, gateways, and inter-cluster behavior carefully.
- Create emergency partitions and calling search spaces.
- Map phones to emergency response locations using switch ports, subnets, or other network evidence.
- Configure emergency callback identifier callback handling so 911 answering center callbacks return correctly.
- Handle multi-cluster and inter-Emergency Responder group routes.
- Test off-premises/Jabber/Webex and remote-user scenarios separately.
Webex Calling enhanced emergency calling
Webex Calling’s enhanced emergency calling documentation describes location-based emergency routing to 911 answering centers using PIDF-LO and provider integrations. Cisco documentation also discusses E911 providers for Webex/BroadWorks contexts including RedSky, Intrado, and 9Line/Bandwidth.
- Enable E911 integration in Control Hub for locations.
- Define dispatchable addresses and network elements.
- Understand HELD and non-HELD device behavior.
- Configure alerts for emergency response teams.
- Know who supports the issue: Cisco TAC, the E911 provider, or the carrier.
Cisco migration risk areas
The biggest Cisco E911 risk is split ownership. Network teams own switch data. Voice teams own CUCM/CER/Webex. Facilities own room labels. The E911 provider owns validation and emergency routing. If those teams do not share a single operating model, the data decays.
- Audit old CER/CUCM records before Webex migration.
- Keep emergency response location names aligned with facilities labels responders understand.
- Do not reuse emergency callback identifiers without validating callback behavior.
- Retest after access-switch, wireless, subnet, session border controller, or Webex location changes.
- Document whether RedSky, Intrado, Bandwidth/9Line, or another provider owns final routing.