Posted by: Mudassir Ali | June 21, 2011

All About Cisco Emergency Responder

All About Cisco Emergency Responder
Cisco Emergency Responder enhances the existing emergency 9-1-1 functionality offered by Cisco Unified Communications Manager (previously known as Cisco Unified CallManager). It assures that Cisco Unified Communications Manager will send emergency calls to the appropriate Public Safety Answering Point (PSAP) for the caller’s location, and that the PSAP can identify the caller’s location and return the call if necessary. In addition, the system automatically tracks and updates equipment moves and changes. Deploying this capability helps ensure more effective compliance with legal or regulatory obligations, reducing the risk of liability related to emergency calls as a result.
Coupled with Cisco Unified Communications Manager, Cisco Emergency Responder surpasses traditional PBX capabilities by introducing user or phone moves and changes at no cost, and dynamic tracking of user and phone locations for emergency 9-1-1 safety and security purposes.

Design Guide: Cisco Emergency Responder Design Guide

Release Notes:
· Release Notes for Cisco Emergency Responder 8.6
· Release Notes for Cisco Emergency Responder 8.5(1)
· Release Notes for Cisco Emergency Responder 8.0(1a)
· Release Notes for Cisco Emergency Responder 7.1(1b)
· Release Notes for Cisco Emergency Responder 7.0(3b)
· Release Notes for Cisco Emergency Responder 2.0(4)

Data Sheets:
· Cisco Emergency Responder 8.5
· Cisco Emergency Responder 8.0
· Cisco Emergency Responder 7.1
· Cisco Emergency Responder 7.0
· Cisco Emergency Responder Version 2.0
· Cisco Emergency Responder Version 1.3
· Cisco Emergency Responder

Administration Guide
· Cisco Emergency Responder 8.6 Administration Guide
· Cisco Emergency Responder Administration Guide 8.5
· Cisco Emergency Responder Administration Guide 8.0
· Cisco Emergency Responder Administration Guide 7.1(1)
· Cisco Emergency Responder Administration Guide 7.0
· Cisco Emergency Responder Administration Guide 2.0
· Cisco Emergency Responder Administration Guide 1.3(1)
· Cisco Emergency Responder Administration Guide 1.2
· Cisco Emergency Responder Administration Guide 1.2(3)
· Cisco Emergency Responder Administration Guide 1.1
· Cisco Emergency Responder Administration Guide 1.1[4]

End User Guide:

· Cisco Emergency Responder 8.6 User Guide
· Cisco Emergency Responder User Guide 8.5
· Cisco Emergency Responder User Guide 8.0
· Cisco Emergency Responder User Guide for 7.1(1)
· Cisco Emergency Responder Off-Premise Location Management User Guide
· Cisco Emergency Responder User Guide 7.0
· Cisco Emergency Responder User’s Guide

ALI Formatting:
· ALI Formatting Tool User Guide for Bell Canada
· ALI Formatting Tool User Guide for SBC Ameritech
· ALI Formatting Tool User Guide for SBC Pacific Bell
· ALI Formatting Tool User Guide for SBC Southwestern Bell
· ALI Formatting Tool User Guide for Verizon

Troubleshooting Guide:
· Cisco Emergency Responder Troubleshooting Guide 8.6
· Cisco Emergency Responder Troubleshooting Guide 8.0

Integration & Interoperability:
· Avaya CM 2.0 PBX with Cisco Unified Communications Manager 4.01 and Cisco Emergency Responder 1.2(3)
· AVAYA Definity CM 2.0 to Cisco Unified Communications Manager 5.1.2 and Cisco Emergency Responder 2.0
· Avaya Definity CM2.0 using T1 QSIG to Cisco Unified Communications Manager 6.0 and Cisco Emergency Responder 2.0
· Avaya Definity G3 PBX with Cisco 3845 T1 QSIG as an MGCP Gateway
· Cisco Unified CallManager 5.0 and Cisco Emergency Responder 1.3 – PBX Interoperability:
· Cisco Unified CallManager 5.0 and Cisco Emergency Responder 1.3 – PBX Interoperability:
· Cisco Unified CallManager 5.0 and Cisco Emergency Responder 1.3 – PBX Interoperability:
· NEC IPX2400 PBX R15 to Cisco Unified Communications Manager 5.1.2 and Cisco Emergency Responder 2.0
· NEC IPX2400 PBX with Cisco 3845 T1 QSIG as an MGCP Gateway to Cisco Unified CallManager 4.2 and Cisco Emergency Responder 1.3
· NEC IPX2400 Release 15 using T1 QSIG to Cisco Unified Communications Manager 6.0 and Cisco Emergency Responder 2.0
· NEC 2400 ICS using a Cisco Catalyst 6608 Gateway with T1 PRI as MGCP to Cisco Communications Manager Release 4.01
· Nortel CS1000 R 4.0 to Cisco Unified Communications Manager 5.1.2 and Cisco Emergency Responder 2.0
· Nortel CS1000M Release 4.0 using T1 QSIG to Cisco Unified Communications Manager 6.0 and Cisco Emergency Responder 2.0
· Nortel Meridian PBX using a Cisco Catalyst 6608 Gateway with T1 PRI as MGCP to Cisco Communications Manager Release 4.01
· Nortel Succession PBX with Cisco 3845 T1 QSIG as an MGCP Gateway

CER Tech Tips on Cisco Support Community
· After a phone is moved by a user, Cisco Emergency Responder shows an incorrect ERL for the phone
· Cisco Emergency Responder login page takes a long time to load
· Emergency Responder GUI says it cannot connect to LDAP
· In Emergency Responder, emergency callers intermittently receive a busy signal and emergency calls are sometimes not routed
· Cisco Emergency Responder does not intercept emergency calls
· The user is unable to delete a switch from the Cisco Emergency Responder configuration
· Port location information is lost after the user restarts the Emergency Responder server
· In Emergency Responder, import or export of the switch port details fails
· In Cisco Emergency Responder, PSAP callback could not reach the original emergency call extension
· Emergency Responder does not show the switch port details of a configured switch
· User is unable to open multiple Emergency Responder sessions using Netscape Navigator
· Some phones do not appear in the Cisco Emergency Responder switch port list
· With Cisco Emergency Responder, the onsite alert personnel do not get email or email-based pages, even though they have configured email addresses
· Emergency Responder web alerts are not received by onsite alert personnel
· On Cisco Emergency Responder, emergency calls are not routed to the correct PSAP
· In Cisco CallManager, users intermittently cannot log in as Cisco Emergency Responder ERL administrators or Cisco Emergency Responder LAN administrators
· Within Cisco CallManager, the CER groups in the cluster screen does not load, and display the Cannot connect to primary LDAP error
· Users cannot import the switch-port configuration on to Cisco Emergency Responder
· Emergency Responder is not discovering the phones homing to CallManager
· Onsite alert personnel do not get telephone alerts when an emergency call is made in an Emergency Response Location
· When a Cisco Emergency Responder emergency call is made, incorrect ERL information is sent to the onsite alert personnel
· The Cisco Emergency Responder server cannot communicate with CERPhoneTrackingEngine and displays the CER Phone Tracking could not get information[using SNMP] from n Switch(es) Check EventViewer on CERServer for details error message
· Phones moved from a CER group to another CER group, and then moved back, still show up in the switch port details for the CER group
· The Cisco Emergency Responder server cannot import switch ports with interface names because of the issues in the correct identification of switch port information
· A previously registered IP phone is not being seen in the Emergency Responder known phones list
· Cisco Emergency Responder does not find all phones properly. Many are listed as unlocated
· After an upgrade to the Cisco CallManager, the route points configured for CER no longer function and the The JTAPI/TAPI application version is not compatible with this version of CTIManager,so received message has been rejected.error message appears
· Tech tip: CER requirement for 3500 switch cluster
· After upgrading to Cisco Emergency Responder version 1.3(1a), "Cannot drop the database ‘CERCluster01’, because it does not exist in the system catalog" error messages appear in the install log
· Even after all of the OS patches for the 2007 DST changes are applied, the CER report time and logs are still offset by an hour.
· With CER Server 1.2(2)SR1 and CER 1.2(3) releases, cannot locate all of the switch ports that the IP phones are plugged into after a switch upgrade from Cisco IOS to 12.2(20) or later. C4500 displays incorrect port information

Supported MCS Platforms

Supported MCS Platforms
Cisco MCS Server Equivalent OEM Server CPU
MCS-7816-H3-IPC1 3.2 GHz
MCS-7816-I3-IPC1 3.2 GHz
MCS-7816-I4-IPC1 3.0 GHz
MCS-7816-I5-IPC1 2.4 GHz
MCS-7825-H3-IPC1 HP DL320-G5 2.13 GHz
MCS-7825-I3-IPC1 IBM x3250 2.13 GHz
MCS-7825-H4-IPC1 HP DL320-G5P 3.0 GHz
MCS-7825-I4-IPC1 IBM x3250-M2 3.0 GHz
MCS-7825-I5-IPC1 IBM x3250-M3 2.4 GHz
MCS-7835-H2-IPC1 HP DL380-G5 (1 CPU) 2.33 GHz
MCS-7835-H2-IPC2 HP DL380-G5 (1 CPU) 2.33 GHz
MCS-7835-I2-IPC1 IBM x3650 (1 CPU) 2.33 GHz
MCS-7835-I2-IPC2 IBM x3650 (1 CPU) 2.33 GHz
MCS-7835-I3-IPC1 IBM x3650-M2 (1 E5504 CPU) 2.0 GHz
HP DL380-G6 (1 E5504 CPU) 2.0 GHz
MCS-7845-H2-IPC1 HP DL380-G5 (2 CPUs) 2.33 GHz
MCS-7845-H2-IPC2 HP DL380-G5 (2 CPUs) 2.33 GHz
MCS-7845-I2-IPC1 IBM x3650 (2 CPUs) 2.33 GHz
MCS-7845-I2-IPC2 IBM x3650 (2 CPUs) 2.33 GHz
MCS-7845-I3-IPC1 IBM x3650-M2 (1 E5540 CPU) 2.53 GHz
HP DL380-G6 (1 E5540 CPU) 2.53 GHz
Unsupported MCS Platforms
Cisco MCS Server Equivalent OEM Server CPU
MCS-7815I-3.0-IPC2 3.06 GHz
MCS-7815-I1-IPC1 3.4 GHz
MCS-7815-I1-IPC2 3.4 GHz
MCS-7815-I1-IPC3 3.4 GHz
MCS-7815-I1-IPC4 3.4 GHz
MCS-7815-I2-IPC1 2.8 GHz
MCS 7825I-3.0-IPC1 IBM x306 3.06 GHz
MCS-7825-I1-IPC1 IBM x306 3.4 GHz
MCS-7825H-3.0-IPC1 HP DL320-G2 3.06 GHz
MCS-7825H-3.0-IPC2 HP DL320-G2 3.06 GHz
MCS-7825-H1-IPC1 HP DL320-G3 3.4 GHz
MCS-7825-H2-IPC1 HP DL320-G4 2.8 GHz
MCS-7825-H2-IPC2 HP DL320-G4 3.4 GHz
MCS-7835-I1-IPC1 IBM x346 (1 CPU) 3.4 GHz
MCS-7835-H1-IPC1 HP DL380-G4 (1 CPU) 3.4 GHz
MCS-7845I-3.0-IPC1 IBM x345 (2 CPUs) 3.06 GHz
MCS-7845-I1-IPC1 IBM x346 (2 CPUs) 3.4 GHz
MCS-7845H-3.0-IPC1 HP DL380-G3 (2 CPUs) 3.06 GHz
MCS-7845-H1-IPC1 HP DL380-G4 (2 CPUs) 3.4 GHz
Supported UCS Platforms
Cisco UCS Server Supported Hypervisor Vendor, Product, Version
UCS-B200-M1 VMware ESXi 4.0 or higher Requires use of supported Virtual Machine Open Virtual Archive (OVA) templates downloaded from Cisco Emergency Responder 8.6 Virtual Machine Templates.
UCS-B200-M2 VMware ESXi 4.0 or higher Requires use of supported Virtual Machine Open Virtual Archive (OVA) templates downloaded from Cisco Emergency Responder 8.6 Virtual Machine Templates.
UCS-C200-M2 VMware ESXi 4.0 or higher Requires use of supported Virtual Machine Open Virtual Archive (OVA) templates downloaded from Cisco Emergency Responder 8.6 Virtual Machine Templates.
UCS-C210-M1 VMware ESXi 4.0 or higher Requires use of supported Virtual Machine Open Virtual Archive (OVA) templates downloaded from Cisco Emergency Responder 8.6 Virtual Machine Templates.
UCS-C210-M2 VMware ESXi 4.0 or higher Requires use of supported Virtual Machine Open Virtual Archive (OVA) templates downloaded from Cisco Emergency Responder 8.6 Virtual Machine Templates.
UCS B200 M1/M2 or UCS C210 M1/M2 ((Large OVA)) UCS B200 M1/M2 or UCS C210 M1/M2 (Small OVA) UCS C200 M2 (Small OVA)
Automatically tracked phones 30,000 20,000 12,000
Manually configured phones 10,000 5,000 2,500
Switches 2,000 1,000 500
Switch ports 120,000 60,000 30,000
ERLs 10,000 7,500 3,000
Supported Cisco ER 8.6(1) MCS Platforms and Scalability
Cisco 7816 Cisco 7825 Cisco 7835 Cisco 7845
Automatically tracked phones 6,000 12,000 20,000 30,000
Manually configured phones 1,000 2,500 5,000 10,000
Roaming phones (per Cisco Emergency Responder cluster) 600 1,200 2,000 3,000
Switches 200 500 1,000 2,000
Switch ports 12,000 30,000 60,000 120,000
ERLs 1,000 3,000 7,500 10,000

Installing and Migrating to Cisco Emergency Responder on the Cisco UCS Server

System Requirements
System Parameter System Parameter options
Supported Virtual Machine Configuration See the documentation at http://www.cisco.com/go/uc-virtualized
IOPS per virtual machine (VM) See the documentation at http://www.cisco.com/go/uc-virtualized
VMware version ESXi 4.0 Update 1
VMware—vMotion No
VMware—Site Recovery Manager Yes
VMware—High Availability Yes
VMware—Data Recovery (VDR) Yes
All other unlisted VMware features Not supported

ESXi Support for Call Processing and System Management Applications

Application VMware vSphere ESXi 4.0 and 4.0 Updates VMware vSphere ESXi 4.1 and 4.1 Updates
Cisco Emergency Responder 8.5(1)+, 8.6(1)+ Not supported

Emergency Responder Virtual Machine Templates-8.5(1)

E911 and Cisco Emergency Responder Terminology

Term Definition
ALI Automatic location information. Information that ties an ELIN to a location, 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 Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN Emergency location identification number. 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. See ALI.
emergency call A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider’s network, where the call is routed to the local PSAP.
emergency caller The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL Emergency response location. The 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 Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN Emergency service number.
ESZ Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures the MSAG is updated. You must negotiate this service with your service provider—it is not a service provided directly through Emergency Responder.
NENA National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries abide by your service provider’s rules.
PSAP Public safety answering point. The 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.

Advertisements

Responses

  1. arcc

  2. argentine

  3. thanks keep the post coming.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: