Replacing Cisco Emergency Responder when moving to cloud calling

See also

Sources

1. 1
   ATA devices on Webex Calling do not talk to the RedSky service, so their emergency calls are routed to an emergency provider without HELD location.

   Enhanced Emergency Calling for Webex Calling · Supported devices section, devices not served · Checked 2026-10-14
2. 2
   The Cisco help article at help.webex.com article fwm1hy is titled E911 Emergency Calling in Webex for BroadWorks and applies to Webex for Cisco BroadWorks, not to CER or Webex Calling multi-tenant.

   E911 Emergency Calling in Webex for BroadWorks · Article title and first section · Checked 2026-10-14
3. 3
   Cisco Emergency Responder 12.0 reached its Last Date of Support on 31 August 2023 under EOL13304, with end of sale on 17 August 2020.

   End-of-Sale and End-of-Life Announcement for the Cisco Emergency Responder 12.0 · Table 1, End-of-Sale Date and Last Date of Support rows · Checked 2026-10-14
4. 4
   EOL13304 names Emergency Responder 12.5 software (ER12.5-SW-K9) as the replacement for ER12.0-SW-K9; it does not name a cloud service as the migration product.

   End-of-Sale and End-of-Life Announcement for the Cisco Emergency Responder 12.0 · Product Migration Options table, ER12.0-SW-K9 row · Checked 2026-10-14
5. 5
   Under EOL15245 the End of Software Maintenance Releases date for Version 14 on-premises calling application software was 7 April 2026.

   End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual · Table 1, End of SW Maintenance Releases (App SW) · Checked 2026-10-14
6. 6
   Cisco end-of-life bulletin EOL15245 (Version 14 on-premises calling applications, perpetual) lists Cisco Emergency Responder 14 among the affected applications.

   End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual · Product description / affected applications list · Checked 2026-10-14
7. 7
   Under EOL15245 the Last Date of Support for Version 14 on-premises calling application software, which includes CER 14, is 30 April 2027.

   End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual · Table 1, Last Date of Support (App SW) · Checked 2026-10-14
8. 8
   Cisco Emergency Responder 15 was released on 16 October 2023 and Cisco's support page listed it as Available with ordering open as of 2026-10-14.

   Cisco Emergency Responder 15 - Support · Product status / release date block at top of page · Checked 2026-10-14
9. 9
   As of 2026-10-14 the Cisco Emergency Responder 15 support page listed no end-of-sale notice for CER 15 itself; the Emergency Responder-specific notices listed cover 12.0 and earlier.

   Cisco Emergency Responder 15 - Support · End-of-Life and End-of-Sale Notices section · Checked 2026-10-14
10. 10
    Cisco publishes release notes for Emergency Responder 15SU4, dated 4 May 2026, on the CER 15 support page.

    Cisco Emergency Responder 15 - Support · Release Notes list: Version 15SU4 · Checked 2026-10-14
11. 11
    Webex Calling's Control Hub emergency call notification emails a specified address when a user calls emergency services; it is disabled by default and Cisco presents it as supporting Kari's Law.

    Configure emergency call notifications in Control Hub · Overview section · Checked 2026-10-14
12. 12
    Control Hub emergency call notifications can be set once for all locations at organisation level, or per location if the organisation-level setting allows location-specific notifications.

    Configure emergency call notifications in Control Hub · Configure at organization level; Configure at location level · Checked 2026-10-14
13. 13
    The Control Hub emergency call notification shows the location's main address, which may differ from where the call was actually placed.

    Configure emergency call notifications in Control Hub · Limitations section · Checked 2026-10-14
14. 14
    For CER in Dedicated Instance, the partner administrator must get the CER Account ID from the RedSky portal and enter it in CER's Intrado Account ID field.

    Dedicated Instance for Webex Calling — base configuration · Cisco Emergency Responder (CER) section: partner/customer configuration note · Checked 2026-10-14
15. 15
    For Dedicated Instance, Cisco documents CER integration with a National E911 Service Provider such as RedSky to automate on-premises location tracking and off-premises location updates.

    Configure E911 for Dedicated Instance · Article body, first option (CER with National E911 Service Provider) · Checked 2026-10-14
16. 16
    In Dedicated Instance, Cisco uploads the RedSky root certificate to CER and enables the Intrado VUI URL and an HTTP proxy hosted in Cisco's data centre.

    Dedicated Instance for Webex Calling — base configuration · Cisco Emergency Responder (CER) section: RedSky configuration (System > Intrado VUI Settings) · Checked 2026-10-14
17. 17
    In Dedicated Instance, Cisco pre-configures CER with SNMPv3 phone-tracking user details for all Unified CM nodes and with the Unified CM publisher details.

    Dedicated Instance for Webex Calling — base configuration · Cisco Emergency Responder (CER) section: SNMPv3 Settings; Cisco Unified Communications Manager Cluster · Checked 2026-10-14
18. 18
    The Webex Calling Dedicated Instance add-on includes Cisco Emergency Responder only in the Americas region.

    Introduction to Dedicated Instance · Overview, list of Dedicated Instance components · Checked 2026-10-14
19. 19
    An Americas customer moving to Webex Calling Dedicated Instance can keep a CER-based design, so a CER replacement is mainly needed for moves to Webex Calling multi-tenant or other cloud platforms.inferred

    Introduction to Dedicated Instance · Overview component list; Simple migration path section · Checked 2026-10-14
20. 20
    Cisco positions Nomadic E911 for Dedicated Instance as supporting RAY BAUM'S Act requirements by letting users update their location natively in the Webex App.

    Configure E911 for Dedicated Instance · Article body, second option (Nomadic E911) · Checked 2026-10-14
21. 21
    Because CER 15 is still orderable and maintained, the need to replace CER when moving to cloud calling comes from leaving Unified CM call control rather than from CER itself being withdrawn.inferred

    Cisco Emergency Responder 15 - Support · Product status block; Release Notes list · Checked 2026-10-14
22. 22
    Cisco recommends that a Webex Calling Emergency Callback Number reach a live person, not an auto attendant, IVR or other service.

    Emergency Callback Number (ECBN) in Control Hub · Requirements and recommendations · Checked 2026-10-14
23. 23
    Webex Calling does not natively support multiple fixed devices at different locations through ECBN alone; Cisco points to the RedSky integration for more accurate addresses.

    Emergency Callback Number (ECBN) in Control Hub · Specifications / limitations; Non-fixed (soft) devices and ECBN · Checked 2026-10-14
24. 24
    On Webex Calling multi-tenant, CER's three jobs map to separate pieces: location tracking to the RedSky wiremap with HELD, ELIN callback to Webex Calling ELIN and ECBN, and onsite alerts to Control Hub email notifications plus RedSky alerts.inferred

    Enhanced Emergency Calling for Webex Calling · Network discovery, HELD and Notifications sections (read with cisco-help-5oxx10-configure-elin and cisco-help-nj0abhbb-emergency-call-notifications) · Checked 2026-10-14
25. 25
    In Webex Calling's RedSky integration, Cisco MPP desk and conference phones, Cisco Room, Desk and Board devices, and the Webex App are HELD-capable and report network information to obtain a location.

    Enhanced Emergency Calling for Webex Calling · Supported devices section; HELD section · Checked 2026-10-14
26. 26
    A HELD-capable Webex Calling device gets a location token, which Webex Calling passes to RedSky when the user dials 911 or 933.

    Enhanced Emergency Calling for Webex Calling · HELD section · Checked 2026-10-14
27. 27
    Intrado is available as an alternative enhanced emergency calling provider for Webex Calling locations in the USA, Canada and US territories, and production use requires Intrado licences ordered through Cisco Commerce Workspace.

    Enhanced Emergency Calling for Webex Calling · Intrado section; licensing section · Checked 2026-10-14
28. 28
    47 CFR 9.16(b)(3)(i) required on-premises fixed MLTS telephones to provide automated dispatchable location no later than 6 January 2021.

    47 CFR part 9 — 911 Requirements · § 9.16(b)(3)(i) · Checked 2026-10-14
29. 29
    47 CFR 9.16(b)(3)(ii) and (iii) required on-premises non-fixed and off-premises MLTS devices, from 6 January 2022, to provide automated dispatchable location where technically feasible, or otherwise a location the user updates manually or an alternative or enhanced location.

    47 CFR part 9 — 911 Requirements · § 9.16(b)(3)(ii)-(iii) · Checked 2026-10-14
30. 30
    47 CFR 9.16(b)(2) requires MLTS operators, where possible without hardware or software upgrades, to send a 911 notification to a central location or person; it must be sent with the call where feasible, not delay it, and go where someone is likely to see or hear it.

    47 CFR part 9 — 911 Requirements · § 9.16(b)(2)(i)-(iii) · Checked 2026-10-14
31. 31
    The Webex App on a cellular-capable mobile device sends emergency calls through the native dialer, so Webex Calling does not see or process them.

    Emergency Callback Number (ECBN) in Control Hub · Non-fixed (soft) devices and ECBN section · Checked 2026-10-14
32. 32
    For non-HELD devices on Webex Calling, such as Poly VVX and Trio or Yealink T3, T4, T5 and CP phones, RedSky determines location from the caller ID.

    Enhanced Emergency Calling for Webex Calling · Supported devices section, non-HELD devices · Checked 2026-10-14
33. 33
    When an off-premises Webex App user connects from a new network, the app prompts for a dispatch address and reuses it on networks the user has already provided.

    Enhanced Emergency Calling for Webex Calling · Network discovery section, off-premises users · Checked 2026-10-14
34. 34
    RedSky can send emergency call notifications for Webex Calling by email, SMS or desktop application to multiple recipients, and alerts can be set for 933 test calls and for HELD requests from unknown locations.

    Enhanced Emergency Calling for Webex Calling · Notifications section · Checked 2026-10-14
35. 35
    Bridging enterprise personnel into emergency calls requires an enhanced RedSky subscription and is not part of the free Cisco licensing package for Webex Calling.

    Enhanced Emergency Calling for Webex Calling · Licensing / cost section · Checked 2026-10-14
36. 36
    Webex Calling customers in Canada must obtain a RedSky license through Cisco or a service partner.

    Enhanced Emergency Calling for Webex Calling · Licensing / cost section · Checked 2026-10-14
37. 37
    Enabling RedSky for Webex Calling requires allowing api.wxc.e911cloud.com and wxc.e911cloud.com on port 443.

    Enhanced Emergency Calling for Webex Calling · Requirements section · Checked 2026-10-14
38. 38
    RedSky for Webex Calling is a cloud service that needs no on-premises appliances or dedicated SIP trunks.

    Enhanced Emergency Calling for Webex Calling · Overview (what RedSky provides) · Checked 2026-10-14
39. 39
    RedSky enhanced emergency calling is enabled per Webex Calling location in Control Hub by a full administrator, and wiremaps and alerts are configured in the RedSky portal.

    Enhanced Emergency Calling for Webex Calling · Requirements section; location enablement steps · Checked 2026-10-14
40. 40
    Webex Calling users in the United States are entitled to RedSky enhanced emergency calling as part of their Webex Calling entitlement.

    Enhanced Emergency Calling for Webex Calling · Licensing / cost section · Checked 2026-10-14
41. 41
    During a phased Unified CM to Webex Calling move, CER sites and Webex Calling sites can both use RedSky as the downstream E911 provider, which may simplify running both during coexistence.inferred

    Enhanced Emergency Calling for Webex Calling · CER / Unified CM section; RedSky overview · Checked 2026-10-14
42. 42
    A Teams emergency calling policy can notify specified users and groups by Teams chat only, conference them in muted, or conference them in unmuted, and can dial a PSTN number into the emergency call.

    Manage emergency calling policies in Microsoft Teams · Create a custom emergency calling policy, step 6 (Notification mode) · Checked 2026-10-14
43. 43
    For Teams Direct Routing, emergency calling needs either a connection to an Emergency Routing Service provider (US and Canada) or an SBC set up for an ELIN application, plus PIDF/LO support enabled on the SBC.

    Configure dynamic emergency calling · Emergency calling prerequisites for Direct Routing; Set up an Emergency Routing Service provider · Checked 2026-10-14
44. 44
    Microsoft Calling Plans, Operator Connect partners and Teams Phone Mobile partners provide dynamic emergency routing for Teams users in the United States and Canada.

    Configure dynamic emergency calling · Plan for emergency calling, closing paragraph · Checked 2026-10-14
45. 45
    In Teams dynamic emergency calling the Location Information Service matches a client's network element in this order and uses the first match: WAP, Ethernet switch and port, Ethernet switch, subnet.

    Configure dynamic emergency calling · Plan for emergency calling, step 2 · Checked 2026-10-14
46. 46
    Teams dynamic emergency calling, including security desk notification, is not supported on the Teams web client; Microsoft suggests turning off Web PSTN calling for those users.

    Configure dynamic emergency calling · Supported clients, note · Checked 2026-10-14
47. 47
    RedSky locates Webex Calling devices on premises by matching their network connection to pre-provisioned wiremap data: wireless AP MAC or BSSID, LLDP switch and port, and IP subnets per location.

    Enhanced Emergency Calling for Webex Calling · Network discovery section · Checked 2026-10-14
48. 48
    Cisco's Unified CM to Webex Calling migration design guidance says all customers should deploy at least the basic emergency calling configuration, which needs a customer-owned +E.164 number for each location.

    Design to migrate from Unified CM to Webex Calling · Emergency calling section, basic emergency call routing · Checked 2026-10-14
49. 49
    Cisco's migration design guidance asks for each device's dispatchable location and its physical network location (switch and switch port, wireless AP BSSID, or on-premises IP subnet).

    Design to migrate from Unified CM to Webex Calling · Locations section, location information table · Checked 2026-10-14
50. 50
    Webex Calling administrators do not create ELINs directly; they convert eligible standard or service numbers to ELINs in Control Hub.

    Configure ELIN for Webex Calling · ELIN provisioning and management in Control Hub; Rules for modifying numbers to ELINs · Checked 2026-10-14
51. 51
    Webex Calling dynamically assigns an ELIN, a location-based number, to an emergency call so emergency services can call back the caller, including extension-only users; ELIN is on by default.

    Configure ELIN for Webex Calling · Overview; ELIN availability and automatic assignment · Checked 2026-10-14
52. 52
    If no ELIN is available or allowed, Webex Calling falls back to the Emergency Callback Number, and a callback to an expired ELIN goes to the assigned ECBN or is rejected with User Not Found.

    Configure ELIN for Webex Calling · ELIN fallback mechanism · Checked 2026-10-14
53. 53
    The Webex Calling ELIN expiry time is set per location from 10 to 1440 minutes, with a default of 60 minutes.

    Configure ELIN for Webex Calling · Configure ELIN expiry time · Checked 2026-10-14
54. 54
    Webex Calling ELIN does not support Webex Go mobile devices, network-originated calls such as Single Number Reach, blind transfers to emergency destinations, or trial organisations.

    Configure ELIN for Webex Calling · ELIN supported options and limitations; ELIN limitations · Checked 2026-10-14
55. 55
    Cisco designed Webex Calling's Enhanced Emergency call routing for US and Canada deployments that have specific regulatory requirements.

    Design to migrate from Unified CM to Webex Calling · Emergency calling section, Enhanced Emergency call routing · Checked 2026-10-14
56. 56
    Webex Calling locations outside the US, its territories and Canada keep using the PSTN for emergency calls rather than the E911 provider.

    Enhanced Emergency Calling for Webex Calling · Supported countries section · Checked 2026-10-14
57. 57
    For US deployments that need Enhanced Emergency calling, Webex Calling uses RedSky's Horizon Mobility, integrated into Webex Calling, to route emergency calls.

    Design to migrate from Unified CM to Webex Calling · Emergency calling section, RedSky paragraph · Checked 2026-10-14
58. 58
    In Webex Calling multi-tenant, emergency call routing is native to the platform and is based on the location defined in Control Hub.

    Design to migrate from Unified CM to Webex Calling · Emergency calling section · Checked 2026-10-14
59. 59
    Cisco advises administrators to always test location discovery before they activate routing of emergency calls to RedSky in Webex Calling.

    Design to migrate from Unified CM to Webex Calling · Emergency calling section, RedSky paragraph · Checked 2026-10-14

Documents

Cite this page

WarmTransfer. (2026, October 14). Replacing Cisco Emergency Responder when moving to cloud calling. WarmTransfer. https://warmtransfer.net/knowledge/cer-replacement-cloud

@misc{warmtransfer-cer-replacement-cloud,
  title  = {Replacing Cisco Emergency Responder when moving to cloud calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/cer-replacement-cloud},
  note   = {Verified 2026-10-14}
}