Cisco Emergency Responder 8.7 supports a variety of hardware and software components, as shown in the following tables:
Table 1: Required Software
Table 2: Recommended Software
Table 3: Supported Phones
Table 4: Supported Voice-Ready LAN Switches
Table 5: Supported Network Modules
Table 6 Supported Cisco ER MCS Platforms and Scalability
The type of support can differ between types of hardware; read the tables carefully to determine how Emergency Responder will work with the devices you use.
Cisco Emergency Responder 8.7 is compatible with Cisco Unified Communications Manager 8.6(2) and earlier. To maintain compatibility of Cisco Emergency Responder and Cisco Unified Communications Manager, upgrade Cisco Emergency Responder to Release 8.7 before upgrading Cisco Unified Communications Manager to Release 8.6(2).
Used to send email notifications to onsite alert (security) personnel. If you use an SMTP email paging server, personnel are paged instead of emailed.
Cisco Unified Operations Manager
Used to monitor the health and functionality of Emergency Responder.
Table 3: Supported Phones lists the different types of phones that support Emergency Responder. The type of support Emergency Responder supplies differs depending on the type of phone and the type of switch port to which the phone is attached.
Session Initiation Protocol (SIP) on Cisco Unified IP Phone 9971, 9951, 8961, 8945, 8941, 7975, 7971, 7970, 7965, 7962, 7961, 7960, 7945, 7942, 7941, 7940, 7912, 7911, 7906, 7905, 6961, 6945, 6941, 6921, 6911, 6901, 3911, 3905; Cisco IP Video Phone E20; Cisco TelePresence EX60, EX90, and MX200; Cisco TelePresence System Quick Set C20 and Cisco TelePresence Codec C40, C60, and C90
Cisco IP Communicator
These phones do not require any special Emergency Responder configuration. However, you must enable Cisco Discovery Protocol (CDP) on the switches.
Although Cisco Analog Telephone Adapter (ATA) phones support CDP and SCCP, Emergency Responder cannot automatically track them. You can add ATA phones manually and assign them to an Emergency Response Location (ERL). Emergency Responder will route calls from ATA phones based on the assigned ERL.
Cisco IP Communicator can be tracked using CDP only when installed with Device ID containing the MAC address of wired network interface and operating over wired network interface.
Phones that you can track using IP subnet
Cisco Unified Wireless IP Phone 7920, 7921, 7925, 7925-EX, 7926, and Cisco Cius
Cisco IP Communicator running on 802.11b
Cisco UC Integration for Microsoft Office Communicator, Cisco UC Integration for Microsoft Lync, Cisco Jabber, Cisco Unified Personal
Communicator and third-party SIP phones
Any Cisco Unified IP Phone or third-party SIP phone connected to Cisco or third-party switches not discovered or supported by Emergency Responder
To track these phones, you must configure the subnet and then assign ERLs to the configured subnets.
Cisco IP Communicator can be tracked using IP subnet when installed with a Device ID containing the MAC of the wired network interface but operating over a wireless network interface.
Any IP endpoint can be tracked at call time using IP subnet provided that the Use IP Address from call signaling Telephony setting is enabled.
Phones that you can manually define or track using IP subnet
Phones connected to analog line gateways such as Cisco VG200 series or ATA 180 series
Any H.323 endpoints
These phones are supported only if their calls are routed by Cisco Unified Communications Manager.
Any IP endpoint can be tracked at call time using IP subnet
provided that the Use IP Address from call signaling Telephony
setting is enabled.
The following table lists the LAN switch models supported by Emergency Responder. A LAN switch model is supported only if the SNMP System Object ID appears in this table, irrespective of LAN switch configuration or software release.
Emergency Responder requires SNMP Release 1, Release 2, or Release 2c for automatic tracking of Cisco IP Phones by connected switch ports.
Table 4 Supported Voice-Ready LAN Switches
(Ethernet ports only)
System Object ID from CISCO-PRODUCTS-MIB or CISCO-STACK-MIB
Catalyst 3750 Metro
Catalyst Express 500
Catalyst Express 520
Cisco ME 4900
The following table lists the Cisco router models supported by Emergency Responder.
Table 5 Supported Cisco Routers
(Ethernet ports only)
System Object ID from CISCO-PRODUCTS-MIB or CISCO-STACK-MIB
For specific information about HP servers, see the HP Server solution overview for Cisco 7800 Series Media Convergence Servers on Cisco.com.
For specific information about support for IBM servers, see the IBM Server solution overview for Cisco 7800 Series Media Convergence Servers on Cisco.com.
The bridge upgrade provides a migration path for customers who use discontinued server models.
A bridge upgrade works on unsupported or discontinued hardware for the purpose of creating a Cisco Disaster Recovery System (DRS) backup. You can restore the Cisco DRS backup on new hardware after a fresh installation.
When the system boots the new version, a warning appears on the console informing the user that the system functionality has been limited to making a DRS backup. Because of the restricted visibility of the console, the warning displays during both the CLI and GUI sessions. License upload will have no impact on the system services after the bridge upgrade on unsupported hardware.
Bridge upgrades result in a new entry being added to the system history log file.
If the Calling Party Modification is disabled on Emergency Responder, the number of ERLs that you can deploy depends on the number of route patterns and translation patterns configurable in Cisco Unified Communications Manager.
Before you upgrade Cisco Unified Communications Manager, you must ensure that the new version is compatible with your version of Emergency Responder. If not, you must upgrade Emergency Responder before upgrading Cisco Unified Communications Manager.
After you upgrade both Emergency Responder and Cisco Unified Communications Manager, you must then update the Cisco Unified Communications Manager release on Emergency Responder.
The default filename is not acceptable when you perform a remote upgrade using SFTP. You must remove Bootable_ from the filename before upgrading Emergency Responder.
Supported Upgrades for Cisco Emergency Responder 8.7
Direct upgrades to Cisco Emergency Responder 8.7 are supported only for Releases 7.1 and 8.x. When upgrading from Cisco Emergency Responder 7.1, 8.0, 8.5 or 8.6, you must install the Refresh Upgrade COP before you perform the upgrade.
Upgrades to Emergency Responder 8.7 from Release 1.x, 2.x or 7.0 require a multiple-stage upgrade process:
To upgrade from Emergency Responder 1.x to Emergency Responder 8.7, you must first upgrade to Emergency Responder 7.1 and then upgrade to Emergency Responder 8.7.
To upgrade from Emergency Responder 2.x or 7.0 to Emergency Responder 8.7, you must first upgrade to Emergency Responder 7.1 or Emergency Responder 8.0, and then upgrade to Emergency Responder 8.7. Emergency Responder 8.0 software is included for this purpose when you order an upgrade from Emergency Responder 2.x to Emergency Responder 8.7.
You must complete the upgrade of the Cisco Emergency Responder Publisher before upgrading the Cisco Emergency Responder Subscriber. You cannot upgrade the Subscriber without first upgrading the Publisher.
Cisco Emergency Responder Licensing is associated with a License MAC. For Cisco MCS platforms, the License MAC is identical to the MAC address of the Network Interface Card (NIC). But for VMware installations, the License MAC is not the MAC address of the NIC.
In both cases, you can obtain the Licence Mac from two locations:
OS Administrator CLI: use command
Cisco Unified OS Administration:
show > network
If the system License MAC changes, the system starts running on a 30-day grace period. Customers must upload new license files with a changed License MAC address within this 30-day period or Emergency Responder service stops.
View Phone Location Tables
The phone location tables can become unresponsive. You cannot initiate manual discovery, and when you try to view location tables, you see the following error message:
Phone location tables are being modified. Please wait and try again.
This issue occurs when you reboot the primary and secondary Cisco Emergency Responder servers at the same time. It also occurs when a new phone is added to a switch that has entered into Power Save Plus mode before a major Cisco Emergency Responder discovery happens.
To avoid this issue, ensure the following:
Reboot the primary Emergency Responder server and make sure it is completely online before you reboot the secondary server.
Emergency Responder must discover all newly deployed phones that use Power Save Plus at least once before they enter Power Save Plus mode.
If you encounter this issue, perform the following procedure.
Bring the newly added phones out of Power Save Plus mode.
Make sure that the phone is registered to Cisco Unified Communications Manager.
Stop the Cisco Phone Tracking and Cisco Emergency Responder service on the secondary server.
Restart the Cisco Phone Tracking and Cisco Emergency Responder service on the primary server.
Run Phone discovery.
Start the Cisco Phone Tracking and Cisco Emergency Responder service on the secondary node.
show memory CLI Command on Cisco MCS Servers
The show memory CLI command on a Cisco MCS server may result in a core dump. The affected servers are Cisco MCS 7835-H3 and Cisco MCS 7845-H3. For more information, see CSCtb40865.
Restarting the Integrated Management Module on a Cisco MCS Server
Cisco MCS-7845-I3 servers can be unresponsive if the Integrated Management Module (IMM) is restarted while the operating system is active. This is a Cisco Unified Communications Manager issue but it can affect the operation of Cisco Emergency Responder. For more information, see CSCtd94318 .
ERL Switch Port Associations
Cisco Emergency Responder includes support for retaining the ERL switch port associations when upgrading to specific versions. For more information, see CSCsl02108.
Location Discovery of IP Phones
Cisco Emergency Responder supports location discovery of IP phones by an IP subnet even when they are not connected to a supported Cisco LAN switch.
Cisco Emergency Responder Tracking with Extension Mobility Cross Cluster
Using Extension Mobility Cross Cluster (EMCC) between two
Unified Communications Manager clusters enables Cisco Emergency Responder to
provide enhanced support for 911 calls.
In the case of a 911 call, when an Emergency Responder server is shared
by both a user's home and visited Unified Communications Manager cluster, the Unified Communications Manager cannot use
an Adjunct Calling Search Space (CSS) to direct the 911 call from the
user's home Unified Communications Manager cluster to the user's visited cluster. Instead, the
shared Emergency Responder servers that support both Unified Communications Manager clusters must process the
911 call in the user's home Unified Communications Manager cluster. Also, the Emergency Responder servers that
support the user's home cluster must receive the correct name (SEP<MAC>)
for the calling party device from Unified Communications Manager.
For more information about an individual defect, you can
access the online record for the defect by clicking the Identifier or going to
the URL shown. You must be a registered Cisco.com user to access this online
Because defect status continually changes, be aware that
Table 7 reflects a snapshot of the defects that were open at the time this
report was compiled. For an updated view of open defects, access Bug Toolkit as
described in Access Cisco Software Bug Toolkit.
Table 8 Open Caveats for Cisco Emergency Responder
For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.
Because defect status continually changes, be aware that Table 8 reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in Access Cisco Software Bug Toolkit.
Table 9 Resolved Caveats for Cisco Emergency Responder
CER- Intermediate status msg not printed in CLI for Cisco CDP Stop/Start
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a
service request, and gathering additional information, see the monthly
What's New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product
Documentation as a Really Simple Syndication (RSS) feed and set content to be
delivered directly to your desktop using a reader application. The RSS feeds
are a free service and Cisco currently supports RSS Version 2.0.