# Cisco Emergency Responder Canonical: https://warmtransfer.net/knowledge/cucm-emergency-responder Last verified: 2026-09-24 Cisco Emergency Responder's purpose is to make Cisco Unified Communications Manager (Unified CM) send each emergency call to the Public Safety Answering Point (PSAP) that serves the caller's location[^37]. An emergency response location (ERL) defines the area in which an emergency call is made, and Emergency Responder assigns phone locations to ERLs[^20]. ## How it works An emergency location identification number (ELIN) is a phone number that routes the emergency call to the local PSAP and that the PSAP can use to call the emergency caller back[^17]. By default, Emergency Responder keeps the mapping between the caller's extension and the ELIN used for up to 3 hours, so that a PSAP callback to the ELIN reaches the caller[^18]. In the traditional ELIN deployment, 1 Unified CM route pattern is created for every ERL, and the ELINs are direct inward dialing (DID) numbers obtained from the service provider[^40]. In the traditional ELIN/ALI model, for Emergency Responder to route emergency calls to the local PSAP, the deployment needs a gateway with a Primary Rate Interface (PRI) or Centralized Automatic Message Accounting (CAMA) link to the service provider's network[^34]. Emergency Responder exports Automatic Location Identification (ALI) data files in National Emergency Number Association (NENA) formats[^27]. Emergency Responder can notify configured onsite security users about an emergency call by phone call, web alert, email, and text[^33]. It uses Unified CM Computer Telephony Integration (CTI) ports, configured with consecutive extensions, to call onsite alert (security) personnel when an emergency call is made[^12]. Emergency Responder must be added as a Unified CM application user that controls its CTI ports, CTI route points, and ELIN route points[^8]. For call routing, Emergency Responder requires Unified CM CTI route points for the local emergency number (for example 911), for a number the standby server listens on (for example 912), and for incoming PSAP callbacks (for example 913XXXXXXXXXX)[^13]. The example Unified CM configuration uses an E911 partition for Emergency Responder objects and an E911CSS calling search space that contains the E911 and Phones partitions[^16]. Where the external access code is 9, Cisco warns that a 911 or 9.911 CTI route point can interfere with secondary dial-tone timing, and recommends translation patterns that send 9 plus 911 to the single 911 pattern[^7]. ## National E911 service providers and off-premises users Emergency Responder integrates with 2 approved National E911 Service Providers, RedSky and Intrado, to automate location conveyance and call completion[^26]. Cisco's Webex Calling enhanced-emergency-calling article also states that RedSky integrates with Cisco Emergency Responder and Unified CM[^54]. For National E911 Service Provider calls, connection redundancy comes from Unified CM route lists and route groups, so extra provider route patterns are not required[^36]. From Release 14SU2 onward, the provider-issued certificate that Emergency Responder uses for the National E911 Service Provider connection must be in BCFKS format[^9]. With RedSky as the National E911 Service Provider, Emergency Responder supports neither queries from the provider nor level of service[^38]. With a National E911 Service Provider, Emergency Responder sends ERL and ELIN information for on-premises phones; for off-premises users the calling party number is the user's own number, which the provider uses to identify the caller and location[^35]. E911 for remote teleworkers and off-premises users on Emergency Responder requires an arrangement with a National Emergency Service Provider for location updates, Master Street Address Guide (MSAG) address validation, and call completion[^29]. Off-premises users set their location on the phone display or on the Emergency Responder Off-Premises User page at `https:///ofpuser`, and each saved location needs a unique name[^31]. If an off-premises user has not set a location, they are sent to the Off-Premises User page, and a disclaimer asks them to acknowledge that calls may be restricted until the location is updated[^28]. Extension Mobility is not supported for Emergency Responder off-premises users[^30]. Unified CM's Emergency Call Handling with RedSky can also be used without Cisco Emergency Responder emergency call routing, and Emergency Responder can optionally complement it by tracking devices and passing ALI/ELIN information to RedSky[^46]. Unified CM's native Emergency Call Handling with RedSky is available from Releases 12.5(1)SU6 and 14SU2 onward[^45]. In that native RedSky mode, endpoints obtain a location URI from RedSky through HELD, and Unified CM routes the emergency call to RedSky with that URI in the Geolocation header of the outgoing INVITE[^44]. ## Client tracking Emergency Responder tracks Cisco Jabber clients by wireless access point (BSSID), and falls back to IP subnet tracking, if configured, for Jabber devices on undefined access points[^23]. Enhanced location tracking for Jabber requires Cisco Jabber 12.6, and Unified CM and Emergency Responder at Release 12.5.1SU1 or later[^24]. Off-premises ERLs do not support Cisco Jabber Administrative XML Layer (AXL) discovery tracking[^25]. ## Deployment models and architecture Emergency Responder is deployed as a redundant pair of servers, 1 designated Publisher and the other Subscriber[^39]. The Emergency Responder Subscriber must be installed only after the Publisher installation, including its reboot, has completed[^42]. The primary and standby Emergency Responder servers must run the same Emergency Responder version[^41]. Only 1 Emergency Responder group can support a given Unified CM cluster, but 1 Emergency Responder group can support more than 1 Unified CM cluster[^32]. All Unified CM clusters supported by 1 Emergency Responder cluster must have unique dial plans[^47]. The Release 15 administration guide does not state the capacity of an Emergency Responder group itself; it sends readers to the current release notes[^10]. Emergency Responder 15 runs only as a virtual machine; supported platforms are VMware vSphere ESXi, Cisco NFVIS-for-UC, and Nutanix AHV[^21]. The Release 15 guide documents 3 installation methods: attended installation, touchless installation, and fresh installation with data import[^22]. Emergency Responder 15SU4 adds support for Cisco NFVIS-for-UC (minimum 4.18.2a), Cisco Compute Hyperconverged with Nutanix (Acropolis 10.0 / AOS 7.0), and VMware vSphere ESXi 8.0, while ESXi 7.0 and earlier have reached end of support[^4]. Emergency Responder 15SU4 introduces fresh install with data import: data is exported from an existing cluster to an SFTP server and imported into a fresh installation, allowing a version upgrade and a hardware migration to happen together[^3]. In Webex Calling Dedicated Instance, the add-on bundles Unified CM, optional Cisco Unified IM and Presence, Cisco Unity Connection, Cisco Expressway, Cisco Emergency Responder in the Americas region only, and optionally Cisco Session Management Edition[^55][^14]. Cisco's Dedicated Instance E911 article directs administrators to 2 PDF guides: National E911 for Dedicated Instance (Emergency Responder with RedSky) and a National E911 Webex App admin guide for nomadic E911[^15]. In Webex Contact Center Enterprise for Government, Cisco Emergency Responder is offered as an optional addition, enhancing the emergency calling functionality of Unified CM[^56]. Enhanced emergency calling for multi-tenant Webex Calling uses RedSky (with Intrado also named) and is available in the U.S., its territories, and Canada, while other locations use the PSTN for emergency calls[^53]. In Webex Calling, HELD-capable MPP phones and the Webex App discover their location via upstream LLDP switch, WAP BSSID, IP, or MAC, whereas non-HELD devices are located from caller ID[^52]. WarmTransfer's reading of the sources is that in multi-tenant Webex Calling, the discovery and PSAP routing tasks performed on premises by Emergency Responder are handled by RedSky network discovery through HELD rather than a customer-run Emergency Responder server, with no reviewed source indicating Emergency Responder is deployed in multi-tenant Webex Calling[^11]. ## Upgrades and lifecycle The Emergency Responder 15SU4 release notes were first published on 2026-02-05 and last updated on 2026-05-04[^2]. Emergency Responder 15SU4 is compatible with Unified CM 15, Unified CM 14 and its SUs, and Unified CM 12.5(x)[^1]. Direct upgrades to Emergency Responder 15 and later are supported only from Release 12.5(1) through 12.5(1)SU9 and from Release 14 through 14SU5; earlier releases require intermediate upgrades[^5]. Emergency Responder 14 has no standalone end-of-life notice; it is retired under the shared Version 14 On-premises Calling notices (Perpetual and Flex subscriptions)[^51]. That perpetual notice announced milestone dates for Emergency Responder 14: announced 2024-10-07, end of sale 2025-04-07, end of software maintenance releases 2026-04-07, and last date of support 2027-04-30[^48]. The notice directs customers to migrate to the latest On-premises Calling release or to Cloud Calling under Collaboration Flex Plan 3.0, and names no specific Emergency Responder replacement part[^49]. WarmTransfer's reading of the sources is that because Emergency Responder 14 passed its end of software maintenance releases on 2026-04-07, sites on 14 that need fixes must upgrade to 15, which is documented as a direct upgrade only from 14 through 14SU5[^50]. As of 2026-09-24, Cisco's end-of-life listing had notices for releases up to 14, but none for Release 15 and none retiring the product as a whole[^19]. ## See also - See also [Cisco Emergency Responder setup](https://warmtransfer.net/knowledge/cisco-emergency-responder-setup). - See also [Webex Calling enhanced emergency calling](https://warmtransfer.net/knowledge/webex-calling-emergency-calling). - See also [US emergency calling regulatory requirements](https://warmtransfer.net/knowledge/e911-us-regulatory). - See also [Dispatchable location and nomadic user handling](https://warmtransfer.net/knowledge/dispatchable-location). - See also [Teams emergency calling and location policies](https://warmtransfer.net/knowledge/teams-emergency-calling). - See also [NG911 and i3 architecture transition](https://warmtransfer.net/knowledge/ng911-transition). - See also [International emergency calling requirements](https://warmtransfer.net/knowledge/emergency-calling-international). ## Applicability Applies to: Cisco Webex Calling Dedicated Instance, Cisco Webex Contact Center Enterprise for Government, Cisco Emergency Responder, Cisco Unified Communications Manager, and Cisco Webex Calling. Deployments: on-premises, multi-tenant, dedicated instance, and cisco-hosted-dedicated. Sources checked 2026-09-24. In Dedicated Instance, Cisco Emergency Responder is bundled only for the Americas region[^55][^14]. Supported hypervisors for Release 15 and 15SU4 are VMware vSphere ESXi 8.0 (with ESXi 7.0 and earlier reaching end of support), Cisco NFVIS-for-UC (minimum 4.18.2a), and Cisco Compute Hyperconverged with Nutanix AHV (Acropolis 10.0 / AOS 7.0)[^21][^4]. Compatibility for Emergency Responder 15SU4 covers Unified CM 15, Unified CM 14 and its SUs, and Unified CM 12.5(x)[^1]. ## What remains uncertain The specific numerical capacity of a Cisco Emergency Responder group is not published in the Release 15 administration guide and is directed to current release notes[^10]. Whether Emergency Responder can be used in regions outside the Americas under Dedicated Instance is not covered by the sources below. ## Sources [^1]: Emergency Responder 15SU4 is compatible with Unified CM 15, Unified CM 14 and its SUs, and Unified CM 12.5(x). Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), Supported Cisco Unified Communications Manager versions. Checked 2026-09-24. [^2]: The Emergency Responder 15SU4 release notes were first published on 2026-02-05 and last updated on 2026-05-04. Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), page header > First Published / Last Updated. Checked 2026-09-24. [^3]: Emergency Responder 15SU4 introduces fresh install with data import: data is exported from an existing cluster to an SFTP server and imported into a fresh installation, so a version upgrade and a hardware migration can happen together. Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), New and Changed Features > Fresh Install with Data Import. Checked 2026-09-24. [^4]: Emergency Responder 15SU4 adds support for Cisco NFVIS-for-UC (minimum 4.18.2a), Cisco Compute Hyperconverged with Nutanix (Acropolis 10.0 / AOS 7.0) and VMware vSphere ESXi 8.0; ESXi 7.0 and earlier have reached end of support. Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), New and Changed Features > New hypervisor support. Checked 2026-09-24. [^5]: Direct upgrades to Emergency Responder 15 and later are supported only from Release 12.5(1) through 12.5(1)SU9 and from Release 14 through 14SU5; releases before 12.5 need intermediate upgrades. Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), Upgrade paths. Checked 2026-09-24. [^6]: The 15SU4 VM configurations are 20,000 users on 2 vCPU, 6 GB RAM and 80 GB disk; 30,000 users on 2 vCPU, 6 GB RAM and 110 GB disk; and 40,000 users on 4 vCPU, 6 GB RAM and 110 GB disk. Source: [Cisco Emergency Responder Version 15SU4 Release Notes](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15su4/english/release_notes/guide/cer0_b_cisco-emergency-responder-release-notes-15SU4.html), System requirements > virtual machine configuration. Checked 2026-09-24. [^7]: Where the external access code is 9, Cisco warns that a 911 or 9.911 CTI route point can interfere with secondary dial-tone timing, and recommends translation patterns that send 9 plus 911 to the single 911 pattern. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > 9.911 translation patterns. Checked 2026-09-24. [^8]: Emergency Responder must be added as a Unified CM application user that controls its CTI ports, CTI route points and ELIN route points. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > Emergency Responder user. Checked 2026-09-24. [^9]: From Release 14SU2 onward, the provider-issued certificate that Emergency Responder uses for the National E911 Service Provider connection must be in BCFKS format. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html), Configure Emergency Responder and National E911 Service Provider > prerequisites. Checked 2026-09-24. [^10]: The Release 15 administration guide does not state the capacity of an Emergency Responder group itself; it sends readers to the current release notes. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > Emergency Responder group capacity. Checked 2026-09-24. [^11]: Inference: in Webex Calling multi-tenant, the job Emergency Responder does on premises (discovering where a device is and choosing the PSAP route) falls to RedSky network discovery through HELD rather than to a customer-run Emergency Responder server. No source reviewed says Emergency Responder is deployed in Webex Calling multi-tenant (inferred). Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling for Webex Calling > location determination; compared with Plan for Cisco Emergency Responder > phone location identification. Checked 2026-09-24. [^12]: Emergency Responder uses Unified CM CTI ports, configured with consecutive extensions, to call onsite alert (security) personnel when an emergency call is made. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > CTI ports. Checked 2026-09-24. [^13]: Emergency Responder needs Unified CM CTI route points for the local emergency number (for example 911), for a number the standby server listens on (for example 912), and for incoming PSAP callbacks (for example 913XXXXXXXXXX). Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > CTI route points. Checked 2026-09-24. [^14]: In Webex Calling Dedicated Instance, Cisco Emergency Responder is offered for the Americas region only. Source: [Introduction to Dedicated Instance](https://help.webex.com/en-us/article/dk3o5r/Introduction-to-Dedicated-Instance), Introduction to Dedicated Instance > list of Dedicated Instance applications. Checked 2026-09-24. [^15]: Cisco's Dedicated Instance E911 article sends administrators to two PDF guides: National E911 for Dedicated Instance (Emergency Responder with RedSky) and a National E911 Webex App admin guide for nomadic E911. Source: [Configure E911 for Dedicated Instance](https://help.webex.com/en-us/article/xolesu/Configure-E911-for-Dedicated-Instance), Configure E911 for Dedicated Instance > document links. Checked 2026-09-24. [^16]: The example Unified CM configuration uses an E911 partition for Emergency Responder objects and an E911CSS calling search space that contains the E911 and Phones partitions. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > partitions and calling search spaces. Checked 2026-09-24. [^17]: An emergency location identification number (ELIN) is a phone number that routes the emergency call to the local PSAP and that the PSAP can use to call the emergency caller back. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > ELIN definition. Checked 2026-09-24. [^18]: By default Emergency Responder keeps the mapping between the caller's extension and the ELIN used for up to three hours, so that a PSAP callback to the ELIN reaches the caller. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > ELIN and PSAP callback. Checked 2026-09-24. [^19]: As of 2026-09-24, Cisco's Emergency Responder end-of-life listing had notices for releases up to 14 but none for Release 15 and none retiring the product as a whole. Source: [Cisco Emergency Responder - End-of-Life and End-of-Sale Notices](https://www.cisco.com/c/en/us/products/unified-communications/emergency-responder/eos-eol-notice-listing.html), English notices list. Checked 2026-09-24. [^20]: In Cisco Emergency Responder an emergency response location (ERL) defines the area in which an emergency call is made, and Emergency Responder assigns phone locations to ERLs. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > emergency response locations. Checked 2026-09-24. [^21]: Emergency Responder 15 runs only as a virtual machine; supported platforms are VMware vSphere ESXi, Cisco NFVIS-for-UC and Nutanix AHV. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Cisco Emergency Responder Installation and Upgrade](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_cisco-emergency-responder-administration-installation.html), Cisco Emergency Responder Installation and Upgrade > virtualization. Checked 2026-09-24. [^22]: The Release 15 guide documents three installation methods: attended installation, touchless installation, and fresh installation with data import. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Cisco Emergency Responder Installation and Upgrade](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_cisco-emergency-responder-administration-installation.html), Cisco Emergency Responder Installation and Upgrade > installation methods. Checked 2026-09-24. [^23]: Emergency Responder tracks Cisco Jabber clients by wireless access point (BSSID), and falls back to IP subnet tracking, if configured, for Jabber devices on undefined access points. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Enhanced Location Tracking For Jabber Clients](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01001.html), Enhanced Location Tracking For Jabber Clients > tracking. Checked 2026-09-24. [^24]: Enhanced location tracking for Jabber requires Cisco Jabber 12.6, and Unified CM and Emergency Responder at Release 12.5.1SU1 or later. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Enhanced Location Tracking For Jabber Clients](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01001.html), Enhanced Location Tracking For Jabber Clients > prerequisites. Checked 2026-09-24. [^25]: Off-premises ERLs do not support Cisco Jabber AXL discovery tracking. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Enhanced Location Tracking For Jabber Clients](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01001.html), Enhanced Location Tracking For Jabber Clients > limitations. Checked 2026-09-24. [^26]: Emergency Responder integrates with two approved National E911 Service Providers, RedSky and Intrado, to automate location conveyance and call completion. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html), Configure Emergency Responder and National E911 Service Provider > overview. Checked 2026-09-24. [^27]: Emergency Responder exports ALI data files in NENA formats. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > ALI data. Checked 2026-09-24. [^28]: If an off-premises user has not set a location, they are sent to the Off-Premises User page, and a disclaimer asks them to acknowledge that calls may be restricted until the location is updated. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Remote Teleworker and Off-Premises User—E911](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_enhanced-e911-teleworkers-and-off-premises.html), Remote Teleworker and Off-Premises User—E911 > location not set. Checked 2026-09-24. [^29]: E911 for remote teleworkers and off-premises users on Emergency Responder requires an arrangement with a National Emergency Service Provider for location updates, MSAG address validation and call completion. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Remote Teleworker and Off-Premises User—E911](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_enhanced-e911-teleworkers-and-off-premises.html), Remote Teleworker and Off-Premises User—E911 > overview. Checked 2026-09-24. [^30]: Extension Mobility is not supported for Emergency Responder off-premises users. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Remote Teleworker and Off-Premises User—E911](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_enhanced-e911-teleworkers-and-off-premises.html), Remote Teleworker and Off-Premises User—E911 > limitations. Checked 2026-09-24. [^31]: Off-premises users set their location on the phone display or on the Emergency Responder Off-Premises User page at https:///ofpuser, and each saved location needs a unique name. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Remote Teleworker and Off-Premises User—E911](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_enhanced-e911-teleworkers-and-off-premises.html), Remote Teleworker and Off-Premises User—E911 > Off-Premises User page. Checked 2026-09-24. [^32]: Only one Emergency Responder group can support a given Unified CM cluster, but one Emergency Responder group can support more than one Unified CM cluster. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > Emergency Responder group capacity. Checked 2026-09-24. [^33]: Emergency Responder can notify configured onsite security users about an emergency call, by phone call, web alert, email and text. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > onsite security users. Checked 2026-09-24. [^34]: For Emergency Responder to route emergency calls to the local PSAP, the deployment needs a gateway with a PRI or CAMA link to the service provider's network. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > network hardware requirements. Checked 2026-09-24. [^35]: With a National E911 Service Provider, Emergency Responder sends ERL and ELIN information for on-premises phones; for off-premises users the calling party number is the user's own number, which the provider uses to identify the caller and location. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html), Configure Emergency Responder and National E911 Service Provider > call completion. Checked 2026-09-24. [^36]: For National E911 Service Provider calls, connection redundancy comes from Unified CM route lists and route groups, so extra provider route patterns are not required. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html), Configure Emergency Responder and National E911 Service Provider > route patterns. Checked 2026-09-24. [^37]: Emergency Responder's purpose is to make Unified CM send each emergency call to the PSAP that serves the caller's location. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > overview. Checked 2026-09-24. [^38]: With RedSky as the National E911 Service Provider, Emergency Responder supports neither queries from the provider nor level of service. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Emergency Responder and National E911 Service Provider](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_configure-emergency-responder-and-redskynational.html), Configure Emergency Responder and National E911 Service Provider > limitations. Checked 2026-09-24. [^39]: Emergency Responder is deployed as a redundant pair of servers, one designated Publisher and the other Subscriber. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > server groups. Checked 2026-09-24. [^40]: In the traditional ELIN deployment, one Unified CM route pattern is created for every ERL, and the ELINs are DID numbers obtained from the service provider. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Configure Cisco Unified Communications Manager](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_011.html), Configure Cisco Unified Communications Manager > route patterns for ERLs. Checked 2026-09-24. [^41]: The primary and standby Emergency Responder servers must run the same Emergency Responder version. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Cisco Emergency Responder Installation and Upgrade](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_cisco-emergency-responder-administration-installation.html), Cisco Emergency Responder Installation and Upgrade > requirements. Checked 2026-09-24. [^42]: The Emergency Responder Subscriber must be installed only after the Publisher installation, including its reboot, has completed. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Cisco Emergency Responder Installation and Upgrade](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_m_cisco-emergency-responder-administration-installation.html), Cisco Emergency Responder Installation and Upgrade > install Subscriber. Checked 2026-09-24. [^43]: Emergency Responder decides a phone's ERL using methods in this order of precedence: synthetic phones by MAC address, switch-port tracking, access-point tracking, IP subnet, remote Emergency Responder server group, manually configured phones, and finally the default ERL. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > phone location identification precedence. Checked 2026-09-24. [^44]: In Unified CM's native RedSky mode, endpoints get a location URI from RedSky through HELD, and Unified CM routes the emergency call to RedSky with that URI in the Geolocation header of the outgoing INVITE. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_emergency-call-handling-with-redsky.html), Emergency Call Handling with RedSky > call flow. Checked 2026-09-24. [^45]: Unified CM's native Emergency Call Handling with RedSky is available from Releases 12.5(1)SU6 and 14SU2 onward. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_emergency-call-handling-with-redsky.html), Emergency Call Handling with RedSky > feature applicability. Checked 2026-09-24. [^46]: Unified CM's Emergency Call Handling with RedSky can be used without Cisco Emergency Responder emergency call routing; Emergency Responder can optionally complement it by tracking devices and passing ALI/ELIN information to RedSky. Source: [Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Emergency Call Handling with RedSky](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/cucm_b_feature-configuration-guide-for-15/cucm_m_emergency-call-handling-with-redsky.html), Emergency Call Handling with RedSky > overview. Checked 2026-09-24. [^47]: All Unified CM clusters supported by one Emergency Responder cluster must have unique dial plans. Source: [Cisco Emergency Responder Administration Guide, Release 15 and SUs - Plan for Cisco Emergency Responder](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cer/15/english/administration/guide/cer0_b_cisco-emergency-responder-administration-guide-15/cer0_b_cisco-emergency-responder-administration-guide-1401_chapter_01.html), Plan for Cisco Emergency Responder > Emergency Responder clusters. Checked 2026-09-24. [^48]: The Version 14 On-premises Calling (Perpetual) notice covers Emergency Responder 14: announced 2024-10-07, end of sale 2025-04-07, end of software maintenance releases 2026-04-07, last date of support 2027-04-30. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-14-premises-calling-applications-eol.html), Milestones table; applicable releases list. Checked 2026-09-24. [^49]: The Version 14 On-premises Calling notice tells customers to migrate to the latest On-premises Calling release or to Cloud Calling under Collaboration Flex Plan 3.0; it names no specific Emergency Responder replacement part. Source: [End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-14-premises-calling-applications-eol.html), Product migration options. Checked 2026-09-24. [^50]: Inference: because Emergency Responder 14 passed its end of software maintenance releases on 2026-04-07, sites on 14 that need fixes have to upgrade to 15. A direct upgrade is documented only from 14 through 14SU5 (inferred). Source: [End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager) — Perpetual](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-14-premises-calling-applications-eol.html), Milestones table (End of SW Maintenance Releases Date); combined with CER 15SU4 release notes > Upgrade paths. Checked 2026-09-24. [^51]: Emergency Responder 14 has no standalone end-of-life notice; it is retired under the shared Version 14 On-premises Calling notices (Perpetual and Flex subscriptions), which the Emergency Responder listing links. Source: [Cisco Emergency Responder - End-of-Life and End-of-Sale Notices](https://www.cisco.com/c/en/us/products/unified-communications/emergency-responder/eos-eol-notice-listing.html), English notices list > Version 14 On-premises Calling entries. Checked 2026-09-24. [^52]: In Webex Calling, HELD-capable MPP phones and the Webex App find their location by network discovery (upstream LLDP switch, WAP BSSID, IP or MAC); devices that cannot use HELD are located from the caller ID asserted on the call. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling for Webex Calling > location determination. Checked 2026-09-24. [^53]: Enhanced emergency calling for Webex Calling uses RedSky (with Intrado also named) and is available in the U.S., its territories and Canada; other locations continue to use the PSTN for emergency calls. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling for Webex Calling > overview and availability. Checked 2026-09-24. [^54]: Cisco's Webex Calling enhanced-emergency-calling article states that RedSky also integrates with Cisco Emergency Responder and Unified CM. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling for Webex Calling > RedSky integration. Checked 2026-09-24. [^55]: The Dedicated Instance add-on bundles Cisco Unified Communications Manager, optional Cisco Unified IM and Presence, Cisco Unity Connection, Cisco Expressway, Cisco Emergency Responder in the Americas region only, and optionally Cisco Session Management Edition. Source: [Introduction to Dedicated Instance](https://help.webex.com/en-us/article/dk3o5r/Introduction-to-Dedicated-Instance), Overview bullet list. Checked 2026-09-04. [^56]: Cisco Emergency Responder is offered as an optional addition to the government edition, enhancing the emergency calling functionality of Unified Communications Manager. Source: [Webex Contact Center Enterprise for Government Data Sheet](https://www.cisco.com/c/en/us/products/collateral/contact-center/webex-contact-center-enterprise/webex-cc-enterprise-govt-ds.html), Table 1, emergency responder row. Checked 2026-09-05.