Cisco Emergency Responder 9.0(2) Hardware and Software Components
Cisco Emergency Responder 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 Emergency Responder MCS Platforms and Scalability
Note
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.
Note
Cisco Unified Communications Manager 9.1(1) is not compatible with versions of Cisco Emergency Responder earlier than 9.0(2). To maintain compatibility of Cisco Emergency Responder and Cisco Unified Communications Manager, upgrade Cisco Emergency Responder to Release 9.0(2) before upgrading Cisco Unified Communications Manager to Release 9.1(1).
The following table lists required software that you must install to use Emergency Responder.
Table 1 Required Software
Item
Supported Software Release
Description
Cisco Unified Communications Manager
Cisco Unified Communications Manager 9.1(x)
Cisco Unified Communications Manager 9.0(x)
Cisco Unified Communications Manager 8.6(x)
Cisco Unified Communications Manager 8.5(x)
Cisco Unified Communications Manager 8.0(x)
Cisco Unified Communications Manager 7.1(x)
Cisco Unified Communications Manager 6.1(x)
The software that runs the telephony network.
Web browser
Microsoft Internet Explorer (IE) 10.0
Microsoft Internet Explorer (IE) 9.0
Microsoft Internet Explorer (IE) 8.0
Mozilla Firefox 10.0
Note
IE 8.0 is supported in Cisco Emergency Responder 9.0 and later when running on Microsoft Windows XP SP3 and Windows 7.
IE 9.0 is not supported in Windows XP.
The following table lists optional software that is recommended for use with Emergency Responder.
Table 2 Recommended Software
Item
Minimum Software Version
Description
Email server
Any SMTP email server
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 Prime Collaboration
Release 9.0
Used to monitor the health and functionality of Emergency Responder.
The following table 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.
Table 3 Supported Phones
Phones
Description
Phones that are automatically tracked using Cisco Discovery Protocol
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 on the switches.
Note
Although Cisco Analog Telephone Adapter (ATA) phones support Cisco Discovery Protocol 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.
Note
Cisco IP Communicator can be tracked using Cisco Discovery Protocol only when it is 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 that is connected to Cisco or third-party switches that are not discovered or supported by Emergency Responder
To track these phones, you must configure the subnet and then assign ERLs to the configured subnets.
Note
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 that are 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.
Note
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 supported for off-premises location confirmation and update
with the Remote Worker Emergency Calling feature in Unified Communications Manager 9.0
Cisco Unified IP Phone 9971, 9951,
8961,8945, 8941, 7975, 7971, 7970, 7965, 7962, 7961, 7945, 7942, and 7941
Cisco IP Communicator
When configured for off-premises use in Unified Communications Manager 9.0, these
phones present displays for off-premises users to confirm or update
their off-premises location.
Note
If the user dismisses the display before confirming
or updating the location, it can be recovered by selecting
Running Applications from the Services menu or by resetting the
phone.
The following table lists the LAN switch models that are 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.
Note
Emergency Responder requires SNMP Version 1, Version 2, or Version 2c for automatic tracking of Cisco Unified IP Phones by connected switch ports.
Table 4 Supported Voice-Ready LAN Switches
Series
(Ethernet ports only)
Device Supported
System Object ID from CISCO-PRODUCTS-MIB or CISCO-STACK-MIB
Catalyst 2940
2940-8TF
1.3.6.1.4.1.9.1.542
2940-8TT
1.3.6.1.4.1.9.1.540
Catalyst 2950
2950-12
1.3.6.1.4.1.9.1.323
2950-24
1.3.6.1.4.1.9.1.324
2950C-24
1.3.6.1.4.1.9.1.325
2950G-24-EI-DC
1.3.6.1.4.1.9.1.472
2950S-24
1.3.6.1.4.1.9.1.430
2950SX-24
1.3.6.1.4.1.9.1.480
2950SX-48
1.3.6.1.4.1.9.1.560
Catalyst 2960
2960-24LT-L
1.3.6.1.4.1.9.1.951
2960-24PC-L
1.3.6.1.4.1.9.1.950
2960-24-S
1.3.6.1.4.1.9.1.929
2960-24TC-L
1.3.6.1.4.1.9.1.694
2960-24TC-S
1.3.6.1.4.1.9.1.928
2960-24TT-L
1.3.6.1.4.1.9.1.716
2960-48PST-L
1.3.6.1.4.1.9.1.1016
2960-48TC-L
1.3.6.1.4.1.9.1.695
2960-48TC-S
1.3.6.1.4.1.9.1.927
2960-48TT-L
1.3.6.1.4.1.9.1.717
2960-48TT-S
1.3.6.1.4.1.9.1.1005
2960-8TC-L
1.3.6.1.4.1.9.1.798
2960-8TC-S
1.3.6.1.4.1.9.1.1006
2960G-24TC-L
1.3.6.1.4.1.9.1.696
2960G-48TC-L
1.3.6.1.4.1.9.1.697
2960G-8TC-L
1.3.6.1.4.1.9.1.799
2960PD-8TT-L
1.3.6.1.4.1.9.1.952
2960-48PST-S
1.3.6.1.4.1.9.1.1148
2960-24LC-S
1.3.6.1.4.1.9.1.1146
2960-24PC-S
1.3.6.1.4.1.9.1.1147
Catalyst 2960-C
2960CPD-8PT-L
1.3.6.1.4.1.9.1.1315
2960C-8PC-L
1.3.6.1.4.1.9.1.1366
2960C-12PC-L
1.3.6.1.4.1.9.1.1367
Catalyst 2960-S
2960S Stack
1.3.6.1.4.1.9.1.1208
2960S-24PD-L
1.3.6.1.4.1.9.1.1261
2960S-24PS-L
1.3.6.1.4.1.9.1.1265
2960S-48FPD-L
1.3.6.1.4.1.9.1.1258
2960S-48FPS-L
1.3.6.1.4.1.9.1.1263
2960S-48LPD-L
1.3.6.1.4.1.9.1.1259
2960S-48LPS-L
1.3.6.1.4.1.9.1.1264
Catalyst 2960-S-F
C2960S-F48LPS-L
1.3.6.1.4.1.9.1.1208
C2960S-F48FPS-L
1.3.6.1.4.1.9.1.1208
C2960S-F48TS-L
1.3.6.1.4.1.9.1.1208
C2960S-F48TS-S
1.3.6.1.4.1.9.1.1654
C2960S-F24TS-S
1.3.6.1.4.1.9.1.1655
C2960S-F24TS-L
1.3.6.1.4.1.9.1.1208
C2960S-F24PS-L
1.3.6.1.4.1.9.1.1652
Catalyst 2975
2975GS-48PS-L
1.3.6.1.4.1.9.1.1067
2975GS-48PS-L-Stack
1.3.6.1.4.1.9.1.1068
Catalyst 3550
3550-24-DC
1.3.6.1.4.1.9.1.452
Catalyst 3560
3560-12PC-S
1.3.6.1.4.1.9.1.1015
3560-24PS
1.3.6.1.4.1.9.1.563
3560-24TS
1.3.6.1.4.1.9.1.633
3560-48PS
1.3.6.1.4.1.9.1.564
3560-48TS
1.3.6.1.4.1.9.1.634
3560-8PC
1.3.6.1.4.1.9.1.797
3560G-24PS
1.3.6.1.4.1.9.1.614
3560G-24TS
1.3.6.1.4.1.9.1.615
3560G-48PS
1.3.6.1.4.1.9.1.616
3560G-48TS
1.3.6.1.4.1.9.1.617
3560V2-24PS
1.3.6.1.4.1.9.1.1021
3560V2-48PS
1.3.6.1.4.1.9.1.1025
Catalyst 3560-C
3560CG-8PC-S
1.3.6.1.4.1.9.1.1317
3560CPD-8PT-S
1.3.6.1.4.1.9.1.1368
3560C-8PC-S
1.3.6.1.4.1.9.1.1466
3560C-12PC-S
1.3.6.1.4.1.9.1.1465
Catalyst 3560-E
3560E-12D
1.3.6.1.4.1.9.1.930
3560E-12SD
1.3.6.1.4.1.9.1.956
3560E-24PD
1.3.6.1.4.1.9.1.795
3560E-24TD
1.3.6.1.4.1.9.1.793
3560E-48PD
1.3.6.1.4.1.9.1.796
3560E-48TD
1.3.6.1.4.1.9.1.794
Catalyst 3560-X
3560X-24P (-L/S/E)
1.3.6.1.4.1.9.1.1228
3560X-48PF (-L/S/E)
1.3.6.1.4.1.9.1.1229
3560X-48P (-L/S/E)
1.3.6.1.4.1.9.1.1229
Catalyst 3750
3750 Stack
1.3.6.1.4.1.9.1.516
3750-24FS
1.3.6.1.4.1.9.1.656
3750-24PS
1.3.6.1.4.1.9.1.536
3750-24TS
1.3.6.1.4.1.9.1.513
3750-48PS
1.3.6.1.4.1.9.1.535
3750-48TS
1.3.6.1.4.1.9.1.512
3750G-12S
1.3.6.1.4.1.9.1.530
3750G-12S-SD
1.3.6.1.4.1.9.1.688
3750G-16TD
1.3.6.1.4.1.9.1.591
3750G-24PS
1.3.6.1.4.1.9.1.602
3750G-24T
1.3.6.1.4.1.9.1.514
3750G-24TS
1.3.6.1.4.1.9.1.511
3750G-24TS-1U
1.3.6.1.4.1.9.1.624
3750G-24WS-S25
1.3.6.1.4.1.9.1.778
3750G-24WS-S50
1.3.6.1.4.1.9.1.779
3750G-48PS
1.3.6.1.4.1.9.1.603
3750G-48TS
1.3.6.1.4.1.9.1.604
3750V2-24PS
1.3.6.1.4.1.9.1.1023
3750V2-48PS
1.3.6.1.4.1.9.1.1027
Catalyst 3750-X
3750X-48P (-L/E)
1.3.6.1.4.1.9.1.1225
3750X-48PF (-L/S/E)
1.3.6.1.4.1.9.1.1225
3750X-48P (-L/S)
1.3.6.1.4.1.9.1.1225
3750X-24P (-L/S/E)
1.3.6.1.4.1.9.1.1224
Catalyst 3750 Metro
3750-24TE-M
1.3.6.1.4.1.9.1.574
Catalyst 3750-E
3750E-24PD
1.3.6.1.4.1.9.1.792
3750E-24TD
1.3.6.1.4.1.9.1.789
3750E-48PD
1.3.6.1.4.1.9.1.791
3750E-48TD-S
1.3.6.1.4.1.9.1.790
Catalyst 3850
3850-48P (-L/S/E)
1.3.6.1.4.1.9.1.1641
3850-24P (-L/S/E)
1.3.6.1.4.1.9.1.1642
3850-48T (-L/S/E)
1.3.6.1.4.1.9.1.1643
3850-24T (-L/S/E)
1.3.6.1.4.1.9.1.1644
Catalyst 4500
4503
1.3.6.1.4.1.9.5.58
4503-L3
1.3.6.1.4.1.9.1.503
4506
1.3.6.1.4.1.9.5.59
4506-L3
1.3.6.1.4.1.9.1.502
4507-L3
1.3.6.1.4.1.9.1.501
4510-L3
1.3.6.1.4.1.9.1.537
Catalyst 4500-E
4503-E
1.3.6.1.4.1.9.1.874
4506-E
1.3.6.1.4.1.9.1.875
4507R-E
1.3.6.1.4.1.9.1.876
4510R-E
1.3.6.1.4.1.9.1.877
4507R+E
1.3.6.1.4.1.9.1.1286
4510R+E
1.3.6.1.4.1.9.1.1287
Catalyst 4900
4948
1.3.6.1.4.1.9.1.626
4948-10GE
1.3.6.1.4.1.9.1.659
Catalyst 6500
6503
1.3.6.1.4.1.9.5.56
6503
1.3.6.1.4.1.9.1.449
6504
1.3.6.1.4.1.9.1.657
6506
1.3.6.1.4.1.9.5.45
6506
1.3.6.1.4.1.9.1.282
6509
1.3.6.1.4.1.9.5.44
6509
1.3.6.1.4.1.9.1.283
6509-NEB
1.3.6.1.4.1.9.5.61
6509-NEB-A
1.3.6.1.4.1.9.1.534
6509-V-E
1.3.6.1.4.1.9.1.832
6513
1.3.6.1.4.1.9.5.50
6513
1.3.6.1.4.1.9.1.400
Catalyst Express 500
500-24LC
1.3.6.1.4.1.9.1.725
500-24PC
1.3.6.1.4.1.9.1.726
500-24TT
1.3.6.1.4.1.9.1.724
500G-12TC
1.3.6.1.4.1.9.1.727
Catalyst Express 520
520-24LC
1.3.6.1.4.1.9.1.933
520-24PC
1.3.6.1.4.1.9.1.934
520-24TT
1.3.6.1.4.1.9.1.932
520-8PC
1.3.6.1.4.1.9.1.897
520G-24TC
1.3.6.1.4.1.9.1.935
Cisco ME 4900
ME 4924-10GE
1.3.6.1.4.1.9.1.788
The following table lists the Cisco routers that are supported by Emergency Responder.
Table 5 Supported Cisco Routers
Series
(Ethernet ports only)
Device Supported
System Object ID from CISCO-PRODUCTS-MIB or CISCO-STACK-MIB
Cisco 1800
Cisco 1861-SRST-B/K9
1.3.6.1.4.1.9.1.904
Cisco 1861-SRST-C-B/K9
1.3.6.1.4.1.9.1.939
Cisco 1861-SRST-C-F/K9
1.3.6.1.4.1.9.1.940
Cisco 1861-SRST-F/K9
1.3.6.1.4.1.9.1.905
Cisco 1861-UC-2BRI-K9
1.3.6.1.4.1.9.1.902
Cisco 1861-UC-4FXO-K9
1.3.6.1.4.1.9.1.903
Cisco1861
1.3.6.1.4.1.9.1.1065
Cisco 1900
Cisco 1905
1.3.6.1.4.1.9.1.1192
Cisco 1921
1.3.6.1.4.1.9.1.1191
Cisco 1941
1.3.6.1.4.1.9.1.1047
Cisco 2800
Cisco 2811
1.3.6.1.4.1.9.1.576
Cisco 2821
1.3.6.1.4.1.9.1.577
Cisco 2851
1.3.6.1.4.1.9.1.578
Cisco 2900
Cisco 2911
1.3.6.1.4.1.9.1.1045
Cisco 2921
1.3.6.1.4.1.9.1.1044
Cisco 2951
1.3.6.1.4.1.9.1.1043
Cisco 3800
Cisco 3825
1.3.6.1.4.1.9.1.543
Cisco 3845
1.3.6.1.4.1.9.1.544
Cisco 3900
Cisco 3925
1.3.6.1.4.1.9.1.1042
Cisco 3925E
1.3.6.1.4.1.9.1.1144
Cisco 3945
1.3.6.1.4.1.9.1.1041
Cisco 3945E
1.3.6.1.4.1.9.1.1145
The following table lists the switch and network modules that are supported in Emergency Responder.
Table 6 Supported Switch Modules and Network Modules
Switch Modules/Network Modules
System Object ID from CISCO-PRODUCTS-MIB
Cisco SM-ES2-16-P
1.3.6.1.4.1.9.1.1048
Cisco SM-ES3-16-P
1.3.6.1.4.1.9.1.1049
Cisco SM-ES3G-16-P
1.3.6.1.4.1.9.1.1050
Cisco SM-ES2-24-P
1.3.6.1.4.1.9.1.1052
Cisco SM-ES3-24-P
1.3.6.1.4.1.9.1.1053
Cisco SM-ES3G-24-P
1.3.6.1.4.1.9.1.1054
Cisco SM-D-ES3-48-P
1.3.6.1.4.1.9.1.1056
Cisco SM-D-ES3G-48-P
1.3.6.1.4.1.9.1.1057
NME-16ES-1G
1.3.6.1.4.1.9.1.702
NME-16ES-1G-P
1.3.6.1.4.1.9.1.663
NME-X-23ES-1G
1.3.6.1.4.1.9.1.703
NME-X-23ES-1G-P
1.3.6.1.4.1.9.1.664
NME-XD-24ES-2S-P
1.3.6.1.4.1.9.1.665
NME-XD-48ES-2S-P
1.3.6.1.4.1.9.1.666
Note
The Switch Modules and Network Modules use the System Object IDs of the routers into which they are inserted.
Support for ISR-G2 SM and NM requires installation of COP File.
Download the COP file from the Download Software page on Cisco.com
Supported Cisco MCS Platforms
The following list shows the supported Cisco Media Convergence Server (MCS) platforms:
MCS-7816-I5-IPC1
MCS-7825-I5-IPC1
MCS-7835-I3-IPC1
MCS-7845-I3-IPC1
The following list shows the supported Cisco MCS platforms that require a 4-GB RAM upgrade:
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.
Bridge Upgrade
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.
See the Cisco Unified Communications Manager Documentation Guide and other publications specific to your Cisco Unified Communications Manager release. Navigate from the following URL:
Upgrading Cisco Unified Communications Manager and Cisco Emergency Responder
Before you upgrade to the most recent version of Cisco Emergency Responder, you must ensure that the new version is compatible with your existing version of Cisco Unified Communications Manager. You can use Table 1 Required Software or the Cisco Unified Communications Compatibility Tool to research this issue.
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.
Note
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.
Direct upgrades to Cisco Emergency Responder 9.0(2) are supported only for Releases 7.1, 8.x. and 9.0(1). When you upgrade from Cisco Emergency Responder 7.1, 8.0, 8.5 or 8.6 , you must install the Refresh Upgrade Cisco Options Package (COP) before you upgrade.
Direct upgrades from Cisco Emergency Responder 8.7 and 9.0(1) do not require the Refresh Upgrade COP.
Upgrades to Emergency Responder 9.0(2) 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 9.0(2), you must first upgrade to Emergency Responder 7.1 and then upgrade to Emergency Responder 9.0(2).
To upgrade from Emergency Responder 2.x to Emergency Responder 9.0(2), you must first upgrade to Emergency Responder 7.1 or Emergency Responder 8.0 or Emergency Responder 8.7, and then upgrade to Emergency Responder 9.0(2).
To upgrade from Emergency Responder 7.0 to Emergency Responder 9.0(2), you must first upgrade to Emergency Responder 7.1 or Emergency Responder 8.0, and then upgrade to Emergency Responder 9.0(2).
Note
You must complete the upgrade of the Cisco Emergency Responder Publisher before you upgrade the Cisco Emergency Responder Subscriber. You cannot upgrade the Subscriber without first upgrading the Publisher.
Licensing
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
show status
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.
Procedure
Step 1
Bring the newly added phones out of Power Save Plus mode.
Step 2
Make sure that the phone is registered to Cisco Unified Communications Manager.
Step 3
Stop the Cisco Phone Tracking and Cisco Emergency Responder service on the secondary server.
Step 4
Restart the Cisco Phone Tracking and Cisco Emergency Responder service on the primary server.
Step 5
Run Phone discovery.
Step 6
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.
To look for information about a specific problem, enter the bug ID number in the Search for Bug ID field, then click Go.
Cisco Emergency Responder 9.0(2) Open Caveats
The following table lists severity 1, 2, and 3 defects that are open for
Cisco Emergency Responder 9.0(2).
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
this table 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 9.0(2)
CER Service Stops when Cisco IDS Service Starts or Stops.
Cisco Emergency Responder 9.0(2) Resolved Caveats
The following table lists severity 1, 2, and 3 defects that are resolved for Cisco Emergency Responder 9.0(2).
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 this table 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 9.0(2)
CER 8.5: Unable to edit Location field of IP Subnet.
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.