Cisco Emergency Responder (Cisco ER) helps you manage emergency calls in your telephony network so that you can respond to these calls effectively and so that you can comply with local ordinances concerning the handling of emergency calls. In North America, these local ordinances are called "enhanced 911," or E911. Other countries and locales might have similar ordinances.
Because emergency call ordinances can differ from location to location within a country, region, state, or even metropolitan area, Cisco ER includes the flexibility you need to fit your emergency call configuration to specific local requirements.
To track phones, Cisco ER queries Cisco Unified Communications Manager for a list of phones registered with the cluster. Then, Cisco ER queries the switches on the network (the ones you have identified to Cisco ER) to determine the port to which the phones are connected. Cisco ER does this tracking at regular intervals during the day so that it can identify when a phone moves.
Cisco ER can send emergency calls to the correct PSAP based on port and phone location.
Optionally, you can have an SMTP email server in your network or with a service provider. You can configure Cisco ER to send email to your onsite alert (security) personnel to notify them of emergency calls. If the server is set up as an email-based paging service, the personnel are paged.
Finally, you need a gateway with a PRI or CAMA link to the service provider's network so that Cisco ER can route emergency calls to the local public safety answering point (PSAP).
This configuration report contains the configuration objects for the Cisco Emergency Responder (Cisco ER) cluster.
This section describes system settings of Cisco Emergency Responder.
This section contains the following chapters:
1 Report Summary
Report Info Report Date Report generated for Description Server Info CER version CER IP Report Settings Report Type Visual Style Report Content Template HTML Template Word Report Tool Info Report Tool Version Report Tool License 2 System
Cisco Emergency Responder (Cisco ER) groups form a Cisco ER cluster.
A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled. Consider placing the two servers in a group in separate physical locations not separated by a WAN link so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption.
Deploy Cisco Emergency Responder (Cisco ER) in your network as a pair of redundant servers. One server is designated as the Publisher server and the other as the Subscriber server. Each Cisco ER Publisher server and Subscriber server make up a Cisco ER Server Group. Configuration data for the server groups is stored in a database on the Publisher. This data is replicated to the Subscriber.
A Cisco ER cluster is a set of Cisco ER server groups that share data to provide correct emergency call handling capabilities. Cisco ER cluster information is stored in a central location in the cluster called the cluster database. A Cisco ER server group is considered part of a cluster when the group points to the same cluster database as the other server groups in that cluster.
A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled. Consider placing the two servers in a group in separate physical locations not separated by a WAN link so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption.
The following Cisco ER Server Groups are present in the cluster:
| CER Servers and Server Group | |||
A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled.
The following settings are configured for the a Cisco Emergency Responder (Cisco ER) server groups:
| Cisco ER Group Settings | |
| Cisco ER Group Name | |
| Peer TCP Port | |
| Heart beat Count | |
| Heart beat Interval (in sec) | |
| Active Call Time out (in min) | |
| SMTP Mail Server | |
| Source Mail ID | |
| System Administrator Mail ID | |
| Calling Party Modification | |
| SysLog | |
| Syslog Server | |
| Notes | |
| Dynamic Tracking of Switch IP Address | |
| Security end user web interface language | |
| Limit Concurrent Sessions | |
| Max. number of concurrent sessions | |
The Telephony Settings page defines telephone numbers and telephony ports used by the Cisco ER group.
| Telephony Settings | |
| Route Point for Primary Cisco ER Server | |
| Route Point for Standby Cisco ER Server | |
| PSAP Callback Route Point Pattern | |
| ELIN Digit Strip Pattern | |
| UDP Port Begin | |
| Inter Cisco ER Group Route Pattern | |
| IP Type of service ( 00-FF ) | |
| Onsite Alert Prompt Repeat Count | |
| Use IP Address from call signaling | |
| Intrado Route Pattern Settings | |
Cisco ER servers are inserted in the Cisco ER group when the Cisco ER services are started
Different levels of privilege exist for each application. For the Cisco Unified Communications Manager Administration application, two levels of privilege exist: read privilege and update privilege.
| Server | |||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||
Cisco ER requires server and user licenses.
You must purchase a separate server license for each Cisco ER server in a server group. Cisco generates the server license based on the MAC Address on the server. You must use the MAC Address of the ethernet card on the publisher server to generate a server license for the Publisher. Order two server licenses for each server in a Cisco ER group: one server license for the primary (Publisher) server and a separate server license for the secondary (Subscriber) server. You cannot share a server license between the Publisher server and the Subscriber server.
You must purchase a separate user license for each Cisco ER group. User licenses can be shared between Publisher and Subscriber servers within each Cisco ER group. This includes both implicit 100-user licenses that are provided by the primary and secondary server license. You cannot share Cisco ER user licenses between different Cisco ER groups in a Cisco ER cluster, or between different Cisco ER clusters.
The following licenses are present:
< Not Available >The Email Alert Settings page is used to specify the parameters under which Cisco ER will send email alerts. The checkbox to the right of each parameter is used to enable (check) or disable (uncheck) email alerts for that parameter. Check the Include event viewer contents in mail checkbox if you want to include the details from the event viewer in the email message.
Different levels of privilege exist for each application. For the Cisco Unified Communications Manager Administration application, two levels of privilege exist: read privilege and update privilege.
| Email Alert Settings | ||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||
This section describes system settings of Emergency Responder Locations (ERLs).
The Emergency Responder Locations (ERL) is an area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Cisco ER, you assign switch ports and phones to ERLs, and ERL definitions include Automatic location information (ALI) data.
Automatic location information (ALI) ties an ELIN to a location and is used to route emergency calls from that ELIN to the correct local PSAP, and is presented to the PSAP to help the PSAP locate the emergency caller. In Cisco ER, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
Emergency location identification number (ELIN) is a phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call.
The Public safety answering point (PSAP) is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.
This section contains the following sub chapters:
Onsite Alert Settings contain information about your onsite alert personnel. When you configure ERLs, you assign these personnel to them. Cisco ER will alert the assigned personnel when an emergency call is made within the zone.
The following Onsite Alert Settings are configured:
Use the Pager Alert Configurations page to limit the size of system-wide pager messages by selecting the fields that are sent to the pager and by editing the labels for those fields.
You can limit the size of the pager message that is sent by selecting the following fields and editing the labels are associated with those fields: Extension, ERL, Location, Time, Server.
| Pager and Email Alert Settings | ||
| Pager Alert Settings | ||
| Email Alert Settings | ||
Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create will be used by emergency response teams to locate the emergency, so the ERL should be small enough that these teams can locate the caller within a reasonable time.
You must configure the Default ERL before configuring any other ERLs. The default ERL is the system-defined ERL that will be used to route calls if no other ERL configuration is found.
| Conventional ERL | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cisco Emergency Responder (Cisco ER) uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Cisco ER must use the Content Addressable Memory (CAM) table on the switch to track phones. Using the CAM table is less efficient than using CDP.
If some of the phones on your network do not use CDP, Cisco ER tracks them using the CAM table.
To track phones successfully, Cisco Emergency Responder (Cisco ER) must periodically contact switches to obtain port and device information.
Cisco ER updates network information using two processes:
The Public safety answering point (PSAP) is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.
This section contains the following chapters:
Emergency Responder supports SNMP V1/V2C and V3. You can use the Serviceability web interface to configure SNMP V1/V2C (Community String and Notification Destination) and SNMP V3 (User and Notification Destination).
Each SNMP version has security models and security levels. Users are assigned to groups that are defined by a security model and specified security levels. Each group also has a defined security access level to a set of MIB objects for reading and writing, which are known as views. The switch has a default view (all MIB objects) and defaults groups defined for SNMP V1 and V2C security models. SNMP V3 provides additional security features that cover message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree
Emergency Responder supports SNMP V1/V2C and V3. You can use the Serviceability web interface to configure SNMP V1/V2C (Community String and Notification Destination) and SNMP V3 (User and Notification Destination).
Each SNMP version has security models and security levels. Users are assigned to groups that are defined by a security model and specified security levels. Each group also has a defined security access level to a set of MIB objects for reading and writing, which are known as views. The switch has a default view (all MIB objects) and defaults groups defined for SNMP V1 and V2C security models. SNMP V3 provides additional security features that cover message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree
To track phones successfully, Cisco Emergency Responder (Cisco ER) must periodically contact switches to obtain port and device information. Cisco ER updates network information using two processes:
Phone Tracking: A periodic comparison of the phones registered with Cisco Unified Communications Manager to the location information obtained from the switches. If a phone moves, Cisco ER updates the phone's ERL. Phones that cannot be located are classified as unlocated phones
Note: If you do not configure a switch port phone update schedule, the default schedule will run at midnight.
Switch-Port and Phone Update: The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.
| Switch-Port and Phone Update Schedule | ||||||||
Use the Cisco Unified Communications Manager Clusters page to identify the Cisco Unified Communications Manager clusters whose emergency calls this Cisco Emergency Responder (Cisco ER) group will handle. Only assign a Cisco Unified Communications Manager cluster to a single Cisco ER group. Cisco ER gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones.
You must tell Cisco Emergency Responder (Cisco ER) which switches to manage. Cisco ER tracks port changes, including changes to the devices connected to those ports, and can recognize which ports have phones connected to them. Identify all switches that might have phones attached to them, essentially all edge switches.
The following LAN switches are defined:
In Cisco ER, you assign switch ports and phones to ERLs, and ERL definitions include Automatic location information (ALI) data. The Emergency response location (ERL) defines an area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area
To track phones, Cisco ER queries Cisco Unified Communications Manager for a list of phones registered with the cluster. Then, Cisco ER queries the switches on the network (the ones you have identified to Cisco ER) to determine the port to which the phones are connected. Cisco ER does this tracking at regular intervals during the day so that it can identify when a phone moves.
This section contains the following chapters:
Use the Switch Port Details page to assign switch ports to Emergency Responder Locations (ERLs). This assignment allows Cisco Emergency Responder (Cisco ER) to assign the correct ERL to phones that connect to the network through the configured ports.
After the network administrator adds switches to the Cisco Emergency Responder (Cisco ER) configuration, and runs the switch-port and phone update process, you can assign the switch ports to emergency response locations (ERLs). When you assign a port to an ERL, make sure that you assign the ERL based on the location of the device attached to the port, not the location of the port itself.
IP Subnet configurations are used to automatically assign phones to Emergency Responder Locations (ERLs). You need to manually define an IP Subnet if any of these conditions apply:
Cisco Emergency Responder (Cisco ER) cannot automatically track the type of phone, for example, if the phone is wireless.
Use the CiscoWorks IP Telephony Environment Monitor (ITEM) 2.0 to monitor the health of your Cisco ER system. You create subnets, configure test ERLs and associate them to the subnet, and configure synthetic phones to belong to the test ERLs.
The following IP Subnets are configured:
Use the Unlocated Phones page to identify phones that are registered with Cisco Unified Communications Manager, but which Cisco Emergency Responder (Cisco ER) cannot locate. This can happen for several reasons:
Because Cisco ER cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Cisco ER from locating these phones on your network. If you cannot resolve the problems by defining switches in Cisco ER, or by moving phones to supported switch ports, you might have to manually assign a phone to an ERL.
The following unlocated phones have been found by CER:
The following manual phones and associated ERL are defined. You need to manually define a phone if any of these conditions apply:
For manually defined phones, Cisco ER cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure they are correct.
The following manual phones are defined:
You must configure synthetic phones in the subnet for testing ERL configurations. You can use the CiscoWorks IP Telephony Environment Monitor 2.0 (ITEM) in conjunction with Cisco ER's test ERLs.
For synthetic phones, Cisco ER cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure they are correct.
The following synthetic phones are defined:
The following chapters contain the configuration of users, roles and user groups. Cisco ER uses a role based user management mechanism.
You can add additional users. Once the additional users are added, you assign them to user groups. The new user then inherits the roles that were defined for that user group.
On installation, the system creates one default user, CERAdministrator. The CERAdministrator has access to all system administration screens except the Platform Administration and Disaster Recovery System screens. By default, the CERAdministrator user is assigned to the CER System Administrator, CER Serviceability, CER Admin Utility, and CER User user groups and has access to the resources defined for the CER System Admin, CER Serviceability, CER Admin Utility, and CER User roles.
Note: The default CERAdministrator user cannot be deleted.
You can add additional users. Once the additional users are added, you assign them to user groups. The new user then inherits the roles that were defined for that user group
The following users are defined:
| User | ||||
CER Serviceability CER System Administrator CER User | CER Serviceability CER System Admin CER User | |||
Roles define privileges which allow functionality within the application. Roles are assigned to user groups which are assigned to users.
Four default roles are created during installation and are listed here. They are:
You can only modify information for roles that you create. After you create additional roles, they will also be listed along with the default roles.
The following roles are defined:
| Role | |||||||||||
| |||||||||||
| |||||||||||
| |||||||||||
| |||||||||||
| |||||||||||
| |||||||||||
Cisco ER 2.0 uses a role-based user management mechanism. When you create a user group, you assign roles and add users to the group. Multiple roles can be assigned to a single group. The users in the group will have access to all the resources defined by the roles assigned to the group.
Six default user groups are created during installation and are listed here. They are:
The following user groups are defined:
| User Group | ||
The following chapters contain additional reports.
The Call History page lists the history of emergency calls made from your network. Cisco Emergency Responder (Cisco ER) maintains the most recent 10,000 call history records. There is no restriction on when these calls were placed.
System administrator, ERL administrator, network administrator, or user authority have access to this page.
The audit trail lists for an ERL when, and by whom an ERL was created or changed.
System administrator, ERL administrator, or network administrator authority can view the audit trail.
| ERL Audit Trail | |||||||||||
| |||||||||||
This section contains status and configuration objects obtained via the command line.
This section contains status and configuration objects obtained via the command line.
Date : Mon Apr 13, 2020 11:02:19 Time Zone : Pacific Daylight Time (America/Los_Angeles) Locale : en_US.UTF-8 Product Ver : 10.5.1.20000-3 Unified OS Version : 6.0.0.0-2 License MAC : 71cffb44872e Uptime: 11:02:21 up 4 days, 5:50, 2 users, load average: 0.35, 0.10, 0.03 CPU Idle: 58.59% System: 05.05% User: 36.36% IOWAIT: 00.00% IRQ: 00.00% Soft: 00.00% Memory Total: 3926064K Free: 2015432K Used: 1910632K Cached: 531044K Shared: 0K Buffers: 301536K Total Free Used Disk/active 13711708K 2596908K 10975496K (81%) Disk/inactive 13711708K 12850088K 165096K (2%) Disk/logging 47708064K 44246172K 1038444K (3%) |
remote refid st t when poll reach delay offset jitter ============================================================================== *10.5.1.100 95.81.173.8 3 u 885 1024 377 1.333 -0.082 0.410 synchronised to NTP server (10.5.1.100) at stratum 4 time correct to within 177 ms polling server every 1024 s Current time in UTC is : Mon Apr 13 18:02:21 UTC 2020 Current time in America/Los_Angeles is : Mon Apr 13 11:02:21 PDT 2020 |
Processors : 1 Type : Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz CPU Speed : 3400 Memory : 4096 MBytes Object ID : 1.3.6.1.4.1.9.1.1348 OS Version : UCOS 6.0.0.0-2.i386 Serial Number : VMware-56 4d 25 3c 24 bc eb f5-64 dd 63 42 0e 74 72 3a RAID Version : No RAID controller information is available BIOS Information : PhoenixTechnologiesLTD 6.00 04/05/2016 RAID Details : No RAID information is available ----------------------------------------------------------------------- Physical device information ----------------------------------------------------------------------- Number of Disks : 1 Hard Disk #1 Size (in GB) : 75 Partition Details : Disk /dev/sda: 9790 cylinders, 255 heads, 63 sectors/track Units = sectors of 512 bytes, counting from 0 Device Boot Start End #sectors Id System /dev/sda1 * 2048 27863039 27860992 83 Linux /dev/sda2 27863040 55724031 27860992 83 Linux /dev/sda3 55724032 56248319 524288 83 Linux /dev/sda4 56248320 157286399 101038080 5 Extended /dev/sda5 56250368 60346367 4096000 82 Linux swap / Solaris /dev/sda6 60348416 157286399 96937984 83 Linux |
DHCP : disabled Status : up IP Address : 10.5.1.104 IP Mask : 255.255.255.000 Link Detected: yes Mode : Auto disabled, Full, 10000 Mbits/s Duplicate IP : no DNS Not configured. Gateway : 10.5.1.1 on Ethernet 0 |
Active Version Installed Software Options: No Installed Software Options Found. |
Timezone version: 2015a |
0.57 0.01 0.53 0.12 0.00 98.77 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn sda 11.51 2.18 91.83 796506 33600652 |