Cisco Emergency Responder Administration Guide 2.0: Americas Headquarters

Cisco Emergency Responder Administration Guide 2.
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
Text Part Number: OL-12376-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0704R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco Emergency Responder Administration Guide 2.0 2007 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
Preface
xvii xvii xvii xviii xix xix
Overview Audience
Organization
Related Documentation Acknowledgements

1
xx
Obtaining Documentation, Obtaining Support, and Security Guidelines
CHAPTER
Planning for Cisco Emergency Responder 2.0
1-1
Understanding Enhanced 911 (E911) 1-1 Overview of Enhanced 911 Requirements 1-1 Understanding E911 and Cisco Emergency Responder Terminology
1-2
Understanding Cisco Emergency Responder 1-3 Cisco Emergency Responder 2.0 Features 1-4 Network Hardware and Software Requirements 1-4 Licenses for Cisco Emergency Responder 2.0 1-4 How Cisco Emergency Responder Fits Into Your Network 1-7 What Happens When an Emergency Call Is Made 1-8 Understanding Cisco Emergency Responder Clusters and Groups 1-12 Moving Phone Between Clusters 1-14 Determining the Required Number of Cisco Emergency Responder Groups Data Integrity and Reliability Considerations 1-16 Preparing Your Network For Cisco Emergency Responder 1-17 Obtain CAMA or PRI Trunks to the PSTN 1-17 Obtain DID Numbers from Your Service Provider 1-18 Negotiate ALI Submission Requirements With Your Service Provider Upgrade Switches and Phones 1-19 Preparing Your Staff for Cisco Emergency Responder
1-20
1-15
1-19
Deploying Cisco Emergency Responder 1-21 Deploying Cisco Emergency Responder in One Main Site with One PSAP 1-21 Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs 1-22 Deploying Cisco Emergency Responder In One Main Site with Satellite Offices 1-23 Deploying Cisco Emergency Responder In Two Main Sites 1-25
Cisco Emergency Responder Administration Guide 2.0 OL-12376-01
iii
Contents
CHAPTER
Installing Cisco Emergency Responder 2.0 Hardware and Software Prerequisites Before You Install or Upgrade
2-1 2-1
2-1
Installing Cisco Emergency Responder 2.0 on a New System 2-3 Installing the Cisco Emergency Responder Publisher 2-4 Installing the Cisco Emergency Responder Subscriber 2-8 Using the DMA Tool
2-9 2-9
Upgrading from Cisco Emergency Responder 1.3 to Cisco Emergency Responder 2.0 Upgrading from Cisco Emergency Responder 2.0 to a Later Version
3
2-11
CHAPTER
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Setting Up Phone Route Plans 3-1 Creating a Phone Partition 3-2 Creating a Phone Calling Search Space 3-2 Assigning the Partition and Calling Search Space to Phones
3-1
3-3
Setting Up Cisco Emergency Responder to Handle Emergency Calls 3-4 Creating a Cisco Emergency Responder Partition 3-4 Creating a Cisco Emergency Responder Calling Search Space 3-5 Creating the Emergency Call Route Points 3-6 Creating the Required CTI Ports 3-8 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks 3-9 Creating Alternate Emergency Call Numbers 3-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP 3-16 Creating Route Patterns for Inter-Cisco Emergency Responder Group Communications 3-17 Creating a Cisco Emergency Responder Cisco Unified CallManager User
4
3-19
CHAPTER
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 4-1 Setting Up Phone Route Plans 4-2 Creating a Phone Partition 4-2 Creating a Phone Calling Search Space 4-2 Assigning the Partition and Calling Search Space to Phones
4-3
Setting Up Cisco Emergency Responder to Handle Emergency Calls 4-4 Creating a Cisco Emergency Responder Partition E911 4-4 Creating a Cisco Emergency Responder Calling Search Space 4-5 Creating the Emergency Call Route Points 4-6 Creating the Required CTI Ports 4-8 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks
4-9
Cisco Emergency Responder Administration Guide 2.0
iv
OL-12376-01
Contents
Creating Alternate Emergency Call Numbers 4-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP 4-16 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications 4-17 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User Configuring JTAPI Security
5
4-20 4-19
CHAPTER
Configuring Cisco Emergency Responder 2.0
5-1
Overview of Cisco Emergency Responder Configuration 5-1 Cisco Emergency Responder Website Interfaces 5-2 Role-Based User Management 5-2 Using the Upload and Download Utilities 5-6 Cisco Emergency Responder 2.0 Configuration Task Checklist Managing Cisco Emergency Responder Users Adding Users 5-9 Modifying Users 5-10 Deleting Users 5-10 Managing Cisco Emergency Responder Roles Adding Roles 5-11 Modifying Roles 5-12 Deleting Roles 5-12
5-9
5-7
5-11
Managing Cisco Emergency Responder User Groups Adding User Groups 5-13 Modifying User Groups 5-14 Deleting User Groups 5-15 Logging Into and Out of Cisco Emergency Responder
5-13
5-15
Configuring Servers and Server Groups 5-16 Configuring a Cisco Emergency Responder Server Group 5-16 Configuring Group Telephony Settings For the Cisco Emergency Responder Server Modifying the Emergency Number 5-19 Configuring Cisco Emergency Responder Servers 5-19 Uploading the Cisco Emergency Responder License File 5-20 Identifying the Cisco Unified Communications Manager Clusters 5-21 Configuring the Cisco Emergency Responder Cluster and Cluster DB Host
5-23
5-18
Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder 5-24 Working with Emergency Response Locations Understanding ERLs 5-25 Overview of ERL Management 5-26
5-24
Contents
Identifying Security Personnel (Onsite Alert Personnel) 5-27 Creating ERLs 5-28 Configuring IP Subnet-based ERLs 5-33 Configuring Test ERLs 5-34 Exporting ERL Information 5-36 Exporting ALI Information for Submission to Your Service Provider Viewing the Audit Trail for an ERL 5-38
5-37
Configuring Switches for Cisco Emergency Responder 5-39 Understanding Switch Requirements for Cisco Emergency Responder Configuring the SNMP Connection 5-39 Defining the Phone Tracking and Switch Update Schedules 5-41 Identifying the LAN Switches 5-42 Manually Running the Switch-Port and Phone Update Process 5-45 Managing Phones 5-47 Configuring Switch Ports 5-47 Identifying Unlocated Phones 5-52 Manually Defining a Phone 5-53 Adding Synthetic Phones 5-57 Viewing the Emergency Call History 5-57
6
5-39
CHAPTER
Configuring Cisco Emergency Responder 2.0 Serviceability Using the Serviceability Tools 6-1 Using the Control Center 6-1 Using the Event Viewer 6-2 Configuring SNMP 6-3 Configuring the SNMP Community String 6-3 Configuring the SNMP V1/V2C Notification String 6-4 Configuring SNMP Users 6-5 Configuring the SNMP V3 Notification Destination 6-5 Configuring MIB2 6-6 Using the System Monitor Tools 6-6 Using the CPU and Memory Usage Tool Using the Processes Tool 6-8 Using the Disk Usage Tool 6-8 Using Cisco Emergency Responder Logs
6-9 6-7
6-1
vi
OL-12376-01
Contents
CHAPTER
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Displaying Cisco Unified OS Information 7-1 Viewing ServerGroup Information 7-1 Viewing Hardware Status 7-2 Viewing Network Status 7-2 Viewing Installed Software 7-2 Viewing System Status 7-3 Displaying and Modifying Cisco Unified OS Settings 7-3 Configuring Ethernet Settings 7-3 Configuring NTP Servers 7-4 Configuring SMTP Settings 7-5 Configuring Time Settings 7-5 Restarting, Shutting Down, or Switching Software Versions Managing Security 7-6 Set Internet Explorer Security Options 7-6 Managing Certificates and Certificate Trust Lists Managing IPSec 7-12 Performing Software Upgrades 7-13 Upgrading and Installing Software Using Cisco Unified OS Services 7-16 Using the Ping Utility 7-16 Setting Up Remote Support 7-17
7-13
7-1
7-5
7-7
CHAPTER
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System What is the Disaster Recovery System?
8-1 8-2
8-1
Quick-Reference Tables for Backup and Restore Procedures Backup Quick Reference 8-2 Restore Quick Reference 8-3 Supported Features and Components System Requirements
8-4 8-4 8-4
How to Access the Disaster Recovery System Master Agent Duties and Activation Local Agents
8-4 8-5 8-6 8-4
Adding Backup Devices
Creating and Editing Backup Schedules Starting a Manual Backup

8-7
Enabling, Disabling, and Deleting Schedules
8-7
vii
Contents
Checking Backup Status Restoring a Backup

8-8
8-7
Restoring a Cluster 8-9 Restoring the Publisher 8-9 Restoring Subsequent Cluster Nodes Viewing the Restore Status 8-11 Viewing the Backup and Restore History Backup History 8-12 Restore History 8-12 Trace Files
8-12 8-13
8-10
8-11
Command Line Interface

9
CHAPTER
Using the Cisco Emergency Responder 2.0 Admin Utility Pointing Subscriber Servers to a Different Publisher Updating the Cisco ER Cluster Database Host Details
9-1
9-1
Changing the Cisco Unified Communications Manager Version

9-3
9-2
CHAPTER
10
Preparing Users for Cisco Emergency Responder Understanding the ERL Administrators Role
10-2
10-1 10-1
Preparing Onsite Alert (Security) Personnel for Cisco Emergency Responder Understanding the Network Administrators Role
10-3
Understanding the Cisco Emergency Responder System Administrators Role

11
10-4
CHAPTER
Troubleshooting Cisco Emergency Responder
11-1
Troubleshooting Phone-Related Problems 11-1 Undiscovered Phones 11-2 Too Many Unlocated Phones 11-2 Phone Sometimes Disappears in Cisco Emergency Responder Wrong ERL is Used for a Shared Line 11-4 802.11b Endpoints Using Wrong ERL 11-4
11-4
Troubleshooting Emergency Call Problems 11-5 Emergency Calls are Not Being Intercepted by Cisco Emergency Responder 11-5 ELIN not Transmitted to the PSAP 11-6 ELIN For Default ERL Used For Calls From Other ERLs 11-6 Emergency Calls Not Routed to the Correct PSAP 11-7 Emergency Callers Sometimes Get Busy Signal and Emergency Calls Are Sometimes Not Routed 11-7 PSAP Call Back Errors 11-8
viii
OL-12376-01
Contents
Onsite Alert Personnel Are Not Getting Telephone Alerts 11-8 Onsite Alert Phone Does Not Ring When Emergency Call is Placed 11-9 Prompts for Phone Alerts Not Getting Played 11-9 Onsite Alert Personnel Not Getting Email (or Paging) Notifications 11-9 Incorrect Location Information Sent To Onsite Alert Personnel 11-9 Emergency Call History Problems 11-10 Troubleshooting Email Alerts 11-10 Emergency Call Alert 11-11 Transition Alert 11-11 Tracking Failure 11-12 Failed To Get Provider 11-12 Failed to Establish Communication with Cisco Emergency Responder Phone Tracking Engine 11-12 Lost Communication with Cisco Emergency Responder Phone Tracking Engine 11-13 Failed to Send Unlocated Phone Details to Remote Cisco Emergency Responder Server Group 11-13 Emergency Call Could Not be Routed 11-13 Calling Party Modification Failed 11-14 Troubleshooting Web Alerts
11-14
Troubleshooting Cisco Emergency Responder System and Administration Problems 11-15 Cannot Validate Publisher 11-15 Troubleshooting Login Problems 11-15 Using Cisco Unified Operations Manager 11-16 Troubleshooting Cisco Emergency Responder Switch and Port Configuration Problems 11-16 Using The ERL Debug Tool to Verify Cisco Emergency Responder Configuration 11-17 Replacing the Publisher Server and Subscriber Servers 11-18 Using the Cisco Emergency Responder Admin Utility 11-19 Troubleshooting the Database and Enterprise Replication 11-20 Troubleshooting Cisco Emergency Responder System Problems 11-21 Troubleshooting Cisco Unified Communications Manager Configuration Problems
11-21
Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster 11-22 Phones Moving Between Clusters
11-23 11-23
Starting and Stopping a Cisco Emergency Responder Server Troubleshooting ALI Data Uploads 11-24 Fixing ALI Data Records 11-25 Editing NENA 2.0 and 2.1 File Formats Editing NENA 3.0 File Formats 11-26 Collecting Call History Logs
11-27
11-25
ix
Contents
Collecting Trace and Debug Information 11-27 Enabling Detailed Trace and Debug Information for Cisco Emergency Responder Enabling Syslog 11-29 Viewing Event Messages Managing Performance
11-29 11-29
11-28
Integrating with Network Management Systems 11-29 Understanding CDP Support 11-30 Monitoring Cisco Emergency Responder Subsystem Status Collecting Information from Syslog 11-31 Backing Up and Recovering Data
11-31 11-32
11-30
Troubleshooting the Data Migration Assistant Troubleshooting Windows Upgrades Troubleshooting Linux Upgrades
12
11-33 11-33
CHAPTER
Using the ALI Formatting Tool ALI Formatting Tool Overview
12-1 12-1
Generating Files Using the ALI Formatting Tool 12-2 Using the ALI Formatting Tool Interface 12-2 Generating a Formatted ALI File 12-3
A
APPENDIX
Administration Web Interface For Cisco Emergency Responder Cisco ER Server Groups in Cluster Cisco ER Group Settings Telephony Settings License Manager Email Alert Settings Add Subscriber
A-9 A-10 A-4 A-6 A-3 A-2
A-1
Server Settings for CERServerGroup

A-7 A-8
Onsite Alert Settings
Find ERL Data A-12 Add New ERL A-14 ALI Information (for ERL Name) Export ERL Data A-21 Import ERL Data A-21 SNMP Settings
A-22 A-24
A-17
Phone Tracking Schedule
Cisco Unified Communications Manager Clusters

A-25
OL-12376-01
Contents
LAN Switch Details A-28 Export LAN Switch A-29 Import LAN Switch A-30 Run Switch-Port and Phone Update Switch Port Details A-31 Export Switch Ports A-33 Import Switch Ports A-34 Find and List IP Subnets A-35 Configure IP Subnet A-36 IP Subnet Phones A-37 Export IP Subnets A-37 Import IP Subnets A-38 Unlocated Phones
A-39 A-41 A-31
Find and List Manually Configured Phone Add New Manual Phone A-42 Export Manual Phones A-43 Import Manual Phones A-44 Find and List Synthetic Phones Add New Synthetic Phone Find and List Users A-46 Modify User A-47 Add User A-48 Find and List Roles A-49 Modify Role A-50 Add Role A-50 Find and List User Groups A-51 Modify User Group A-52 Add User Group A-53 Call History
A-54 A-55 A-56 A-45 A-45
ERL Audit Trail PS-ALI Converter ERL Debug Tool
Export PS-ALI Records

A-58 A-59
ALI Formatting Tool
A-60 A-61
File Management Utility
xi
Contents
APPENDIX
Serviceability Web Interface For Cisco Emergency Responder Control Center Event Viewer
B-1 B-2 B-4 B-6
B-1
SNMP Community String Configuration SNMP User Configuration

B-7
SNMP V1/V2c Notification Destination Configuration SNMP V3 Notification Destination Configuration MIB2 SystemGroup Configuration CPU and Memory Usage Processes Disk Usage
B-13 B-15 B-15 B-11 B-11 B-9
System Logs Menu

C
APPENDIX
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder C-1 ServerGroup
C-1 C-2 C-3
Hardware Status Software Packages System Status NTP Server List SMTP Settings Time Settings Version Settings Certificate List IPSec Policy List Ping Configuration Certificate Monitor
Network Configuration
C-4 C-4
Ethernet Configuration
C-6 C-7 C-8 C-8 C-9
C-5
C-13 C-13 C-15
Software Installation/Upgrade
C-16
Remote Access Configuration

D
C-17
APPENDIX
Disaster Recovery System Web Interface For Cisco Emergency Responder Backup Device List Schedule List Manual Backup
D-2 D-4 D-1
D-1
xii
OL-12376-01
Contents
Backup History and Restore History Backup Status Restore Wizard Restore Status
E
D-6 D-7 D-8
D-5
APPENDIX
Admin Utility Web Interface For Cisco Emergency Responder Point to a New Publisher Update CCM Version Update Cluster DB Host
E-2 E-3 E-1
E-1
APPENDIX
Command Line Interface Starting a CLI Session
F-1 F-1
CLI Basics F-2 Completing Commands F-2 Getting Help on Commands F-3 Ending a CLI Session F-4 Cisco Unified OS CLI Commands F-4 delete account F-4 delete dns F-4 delete ipsec F-5 delete process F-5 delete smtp F-6 file check F-6 file delete F-6 file dump F-7 file get F-8 file list F-9 file search F-10 file tail F-11 file view F-11 run sql F-12 set account F-12 set commandcount F-13 set ipsec F-13 set logging F-14 set network dhcp F-14 set network dns F-14 set network dns options F-15
xiii
Contents
set network domain F-15 set network failover F-16 set network gateway F-16 set network ip F-16 set network mtu F-17 set network max_ip_contrack set network nic F-17 set network pmtud F-18 set network status F-18 set password F-19 set smtp F-19 set timezone F-19 set trace F-20 set web-security F-21 set workingdir F-21 show account F-22 show cert F-22 show firewall list F-22 show hardware F-23 show ipsec F-23 show logins F-24 show myself F-24 show network F-24 show open F-25 show packages F-26 show process load F-26 show process list F-27 show registry F-28 show smtp F-28 show stats io F-28 show status F-29 show tech all F-29 show tech database F-30 show tech dbintegrity F-30 show tech dbinuse F-30 show tech dbschema F-31 show tech dbstateinfo F-31 show tech network F-31 show tech prefs F-31 show tech runtime F-32
F-17
xiv
OL-12376-01
Contents
show tech systables F-32 show tech system F-32 show tech table F-33 show tech version F-33 show timezone F-33 show trace F-34 show version F-34 show web-security F-35 show workingdir F-35 unset ipsec F-35 unset network F-36 utils core list F-36 utils core analyze F-36 utils csa disable F-37 utils csa enable F-37 utils csa status F-37 utils dbreplication status F-38 utils dbreplication repair F-38 utils dbreplication reset F-38 utils disaster_recovery backup tape F-38 utils disaster_recovery backup network F-38 utils disaster_recovery cancel_backup F-39 utils disaster_recovery restore tape F-39 utils disaster_recovery restore network F-40 utils disaster_recovery show_backupfiles tape F-40 utils disaster_recovery show_backupfiles network F-40 utils disaster_recovery show_registration F-41 utils disaster_recovery show_tapeid F-41 utils disaster_recovery status F-41 utils fior status F-42 utils fior enable F-42 utils fior disable F-42 utils fior start F-43 utils fior stop F-43 utils fior list F-43 utils fior top F-44 unset ipsec F-44 utils iothrottle enable F-45 utils iothrottle disable F-45 utils iothrottle status F-45
xv
Contents
utils netdump client F-45 utils netdump server F-46 utils network arp F-47 utils network capture eth0 F-47 utils network host F-48 utils network ping F-48 utils network tracert F-49 utils ntp F-49 utils remote_account F-49 utils reset_ui_administrator_password utils service list F-50 utils service F-51 utils snmp get F-51 utils snmp getnext F-52 utils snmp walk F-52 utils system F-52 utils system upgrade F-53
G
F-50
APPENDIX
Using the AFT for Specific Service Providers Using the ALI Formatting Tool for Bell-Canada Modifying the Transaction Code G-1 Entering Bell-Canada-Specific Data G-2
G-1 G-1
Using the ALI Formatting Tool for SBC-Ameritech Using the ALI Formatting Tool for SBC-PacBell Enabling Call Back For This ELIN G-3 Changing the Function Code G-3
G-2 G-3
Using the ALI Formatting Tool for SBC-Southwestern Bell Modifying PS Code for SBC-Southwestern Bell G-4 Changing the Function Code G-4 Using the ALI Formatting Tool for Qwest
G-5
G-4
Using the ALI Formatting Tool for Verizon G-5 Changing the Function Code G-5 Modifying the Disability Indicator for Verizon New England States Modifying the Customer Name for Verizon West States G-6 Modifying the Location for New Jersey G-7
INDEX
G-6
xvi
OL-12376-01
Preface
This preface describes who should read this publication and its document conventions. The preface includes the following topics:

Overview, page xvii Audience, page xvii Organization, page xviii Related Documentation, page xix Obtaining Documentation, Obtaining Support, and Security Guidelines, page xix Acknowledgements, page xx
Overview
The Cisco Emergency Responder Administrator Guide 2.0 provides you with the information you need to understand, install, configure, manage, and use Cisco Emergency Responder (Cisco ER) 2.0.
Audience
Network engineers, system administrators, and telecom engineers should review this guide to learn the steps required to properly set up Cisco ER in the network. Because of the close interaction of Cisco ER with Cisco Unified Communications Manager, you should be familiar with Cisco Unified Communications Manager before deploying Cisco ER. Security personnel should read the Cisco Emergency Responder User Guide 2.0.
xvii
Preface Organization
Organization
The following table shows how this guide is organized: Topic Chapter 1, Planning for Cisco Emergency Responder 2.0 Description Provides information to help you understand emergency call ordinances, how Cisco ER helps you meet the ordinances, and what you need to do to deploy Cisco ER successfully. Provides detailed information on installing or upgrading to Cisco ER 2.0. Describes procedures for configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco ER 2.0. Describes procedures for configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco ER 2.0. Describes how to configure Cisco ER so that it begins managing emergency calls. Describes how to configure and use Cisco ER 2.0 Serviceability features. Describes how to configure and use the Cisco Unified Communications Operating System, which is bundled with Cisco ER 2.0. Describes how to configure the Cisco ER 2.0 Disaster Recovery System.
Chapter 2, Installing Cisco Emergency Responder 2.0 Chapter 3, Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Chapter 4, Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 Chapter 5, Configuring Cisco Emergency Responder 2.0 Chapter 6, Configuring Cisco Emergency Responder 2.0 Serviceability Chapter 7, Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Chapter 8, Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System
Chapter 9, Using the Describes how to use the Cisco ER Admin Utility. Cisco Emergency Responder 2.0 Admin Utility Chapter 10, Preparing Users for Cisco Emergency Responder Chapter 11, Troubleshooting Cisco Emergency Responder Describes the various roles for Cisco ER users. Addresses problems you might encounter with Cisco ER and provides ways to resolve them; also includes other tasks associated with problem identification and resolution. Describes the ALI Formatting Tool (AFT) and provides information on how to use and troubleshoot the AFT. Describes the fields on the pages of the Cisco ER administrators web interface. Describes the fields on the pages of the Cisco ER serviceability web interface. Describes the fields on the pages of the Cisco Unified Operating System (OS) Administration web interface.
Chapter 12, Using the ALI Formatting Tool
Appendix A, Administration Web Interface For Cisco Emergency Responder Appendix B, Serviceability Web Interface For Cisco Emergency Responder Appendix C, Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder
xviii
OL-12376-01
Preface Related Documentation
Topic Appendix D, Disaster Recovery System Web Interface For Cisco Emergency Responder Appendix E, Admin Utility Web Interface For Cisco Emergency Responder Appendix F, Command Line Interface
Description Describes the fields on the pages of the Cisco ER Disaster Recovery System Administration web interface. Describes the fields on the pages of the Cisco ER Admin Utility web interface. Provides information on the Cisco Unified OS Administration command-line interface, including available commands, command syntax, and parameters. Provides service-provider specific information for use in conjunction with the AFT.
Appendix G, Using the AFT for Specific Service Providers
Related Documentation
For additional information about Cisco Emergency Responder (Cisco ER), Cisco Unified CallManager, and Cisco Unified Communications Manager, refer to the following publications.
All Cisco ER documents are available at: http://www.cisco.com/en/US/products/sw/voicesw/ps842/tsd_products_support_series_home.html
Cisco Unified Communications Manager and Cisco Unified CallManager installation documents are available at: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guides_list.html Cisco Unified Communications Manager and Cisco Unified CallManager operating system installation documents and backup and restore documents are available at: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html Information about Cisco Unified Operations Manager 1.0 is available at: http://www.cisco.com/en/US/products/ps6535/index.html
Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly Whats New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
xix
Preface Acknowledgements
Acknowledgements
This product includes software developed by Justin Wells and Semiotek Inc. for use in the WebMacro Servlet Framework (http://www.webmacro.org). You may use WebMacro for use under the GNU General Public License. You may also use WebMacro under the terms of the Semiotek Public License. The terms of the Semiotek Public License are as follows: Copyright (c) 1997, 1998, 1999, 2000 Semiotek Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. 2. 3.
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by Justin Wells and Semiotek Inc. for use in the WebMacro Servlet Framework (http://www.webmacro.org). The names Semiotek Inc. and WebMacro must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact justin@webmacro.org Products derived from this software may not be called WebMacro nor may WebMacro appear in their names without prior written permission of Justin Wells. Redistributions of any form whatsoever must retain the following acknowledgment: This product includes software developed by Justin Wells and Semiotek Inc. for use in the WebMacro Servlet Framework (http://www.webmacro.org).
4.
5. 6.
THIS SOFTWARE IS PROVIDED BY SEMIOTEK INC. ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES OR CONDITIONS, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SEMIOTEK INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
xx
OL-12376-01
CH A P T E R

Cisco Emergency Responder Administration Guide 2.0 (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. However, because ordinances do differ from location to location, and because security requirements differ from company to company, you need to do extensive planning and research before you can deploy Cisco ER in a manner that fits your legal and security needs. These topics help you understand emergency call ordinances, how Cisco ER helps you meet the ordinances, and what you need to do to deploy Cisco ER successfully:

Understanding Enhanced 911 (E911), page 1-1 Understanding Cisco Emergency Responder, page 1-3 Preparing Your Network For Cisco Emergency Responder, page 1-17 Preparing Your Staff for Cisco Emergency Responder, page 1-20 Deploying Cisco Emergency Responder, page 1-21
Understanding Enhanced 911 (E911)

Enhanced 911, or E911, is an extension of the basic 911 emergency call standard in North America. These topics describe E911 requirements and terminology.

Overview of Enhanced 911 Requirements, page 1-1 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Overview of Enhanced 911 Requirements

Enhanced 911 (E911) extends the basic 911 emergency call standard to make it more reliable. When using basic 911 in North America, if a caller dials 911, the call is routed to a Public Safety Answering Point (PSAP), also called the 911 operator. The PSAP is responsible for talking to the caller and arranging the appropriate emergency response, such as sending police, fire, or ambulance teams.
1-1
Chapter 1 Understanding Enhanced 911 (E911)
E911 extends this standard with these requirements:

The emergency call must be routed to the local PSAP based on the location of the caller. (In basic 911, the call simply needs to be routed to some PSAP, not necessarily the local one.) The callers location information must be displayed at the emergency operators terminal. This information is obtained by querying an automatic location information (ALI) database.
In E911, the location of the caller is determined by the Emergency Location Identification Number (ELIN), which is a phone number the PSAP can dial to reconnect to the emergency caller if the emergency call is cut off for any reason, or if the PSAP simply needs to talk to the caller again. The emergency call is routed to the PSAP based on the location information associated with this number. For multi-line phone systems, such as an office system, the ELIN can be associated with more than one telephone by grouping the phones in an Emergency Response Location (ERL). In this case, the location the PSAP receives would be the address of an office building. For large buildings, the location would include additional information such as floor or region on a floor. Each ERL requires a unique ELIN. In addition to these general E911 requirements, each locality can further extend or limit these requirements. For example, a city ordinance might include specific limitations on the size of an ERL (such as, no larger than 7,000 square feet), or on the number of phones that can be included in an ERL (such as, no more than 48 phones). You must work with your service provider and local government to determine the exact E911 requirements in your area.
Related Topics

Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Understanding Cisco Emergency Responder, page 1-3
Understanding E911 and Cisco Emergency Responder Terminology

Table 1-1 defines some of the key terminology used in this document.
Table 1-1 E911 and Cisco Emergency Responder Terminology
Term ALI
Definition 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 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. Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI. Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN). 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. 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. A call made to the local emergency number, such as 911. Cisco ER routes the call to the service providers network, where the call is routed to the local PSAP.
ANI CAMA DID ELIN
emergency call
1-2
OL-12376-01
Chapter 1
Planning for Cisco Emergency Responder 2.0 Understanding Cisco Emergency Responder
Table 1-1
E911 and Cisco Emergency Responder Terminology (continued)
Term emergency caller ERL
Definition 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). 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 Cisco ER, you assign switch ports and phones to ERLs, and ERL definitions include ALI data. Emergency service number. 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. Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Cisco ER, 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 providerit is not a service provided directly through Cisco ER. National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Cisco ER uses the NENA formats for ALI data export files. Your service provider might have additional restrictions on data format, so ensure that your ALI entries abide by your service providers rules. 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.
Related Topics

ESN ESZ
MSAG
NENA
PSAP
Overview of Enhanced 911 Requirements, page 1-1 Understanding Cisco Emergency Responder, page 1-3
Understanding Cisco Emergency Responder

These topics provide an overview of Cisco Emergency Responder and how you can use it in your network.

Cisco Emergency Responder 2.0 Features, page 1-4 Network Hardware and Software Requirements, page 1-4 Licenses for Cisco Emergency Responder 2.0, page 1-4 How Cisco Emergency Responder Fits Into Your Network, page 1-7 What Happens When an Emergency Call Is Made, page 1-8 Understanding Cisco Emergency Responder Clusters and Groups, page 1-12 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Data Integrity and Reliability Considerations, page 1-16
1-3
Chapter 1 Understanding Cisco Emergency Responder
Cisco Emergency Responder 2.0 Features

These are the major new and enhanced features of Cisco Emergency Responder (Cisco ER) 2.0:

Installation and upgrade uses a single DVD FLEXlm licensing Role-based user management Disaster recovery Data migration Cisco ER 2.0 clusters can include both Cisco ER 2.0 and Cisco ER 1.3 server groups HTTPS supported in Cisco ER 2.0 server groups Support for additional IP phones Unlocated phone search allows user to search for a specific unlocated phone Ability to download the results of a Call History search
See the Release Notes for Cisco Emergency Responder 2.0 for a list of hardware and software supported in Cisco ER 2.0.
Related Topics

Understanding Enhanced 911 (E911), page 1-1 Network Hardware and Software Requirements, page 1-4 How Cisco Emergency Responder Fits Into Your Network, page 1-7 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Data Integrity and Reliability Considerations, page 1-16 Understanding ERLs, page 5-25
Network Hardware and Software Requirements

Cisco ER 2.0 supports a variety of hardware and software components. For the complete list of supported hardware and software, see the Release Notes for Cisco Emergency Responder 2.0.
Licenses for Cisco Emergency Responder 2.0

Cisco ER 2.0 uses a web-based system for requesting, creating, and delivering product licenses. Once you register your Cisco ER product through the Cisco.com website, a file containing the server license will be sent to you as a text-file email attachment. This section describes the following topics:

Licenses for Initial Installation, page 1-5 Migrating Licenses, page 1-5 Uploading License Files, page 1-5 Server Licenses, page 1-5
1-4
OL-12376-01
Chapter 1
User Licenses, page 1-6 Determining Your License Requirements, page 1-6
Licenses for Initial Installation

Cisco ER 2.0 does not require a license key for initial installation. Unlicensed Cisco ER 2.0 software will operate normally for 60 days after it is installed, with a capacity of 100 phones. Additional user licenses are not effective until a server license is installed. If you do not install a server license within 60 days, the Cisco ER 2.0 system shuts down.
Migrating Licenses
When migrating from Cisco ER 1.3 to Cisco ER 2.0, you will need to order upgraded licenses using the procedures given later in this section. Existing Cisco ER 1.3 licenses cannot be converted to Cisco ER 2.0 licenses.
Uploading License Files

You can upload license files to the Cisco ER servers using the Cisco ER Administration web interface. To do so, follow these steps:
Procedure
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Log in to the Cisco ER Administration website. Select System > License Manager. The License Manager page appears. In the Details of Cisco ER Licenses section, select the server to which you will upload the license file from the pulldown menu. Click Upload license. The Upload File page appears. Use the Browse... button to select the license file to upload from your local system. Click Upload. The selected license file is uploaded to the Cisco ER server.
Related Topics
License Manager, page A-7
Server Licenses
You must purchase a server license for each Cisco ER server in a server group. Each server license includes an implicit user license for 100 users. To order Cisco ER server licenses, follow these steps:
Procedure
Step 1
Order Cisco ER 2.0 using your preferred ordering method. You will receive a Product Authorization Key (PAK) along with Cisco ER 2.0.
1-5
Step 2
Go to https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet and register your Cisco ER by supplying the PAK and the Media Access Control (MAC) address of your Cisco ER server. To obtain the MAC address of the server, follow these steps:
a. b. c.
Log in to the Cisco Unified OS Administration website. Go to Show > Network. The MAC address displays in the Ethernet Details section.
After processing, you will receive the server license file as a text-file email attachment.
Step 3 Step 4
Save the server license file to a local server so that it can be uploaded to the Cisco ER server. Upload the server license file using the Cisco ER Administration web interface. See the Uploading the Cisco Emergency Responder License File section on page 5-20 for instructions on how to upload the server license file.
User Licenses
Each Cisco ER server license includes 100 user licenses. User licenses are shared by both primary and secondary Cisco ER servers irrespective of where they are installed. The total number of user licenses available in a server group at any given time is the sum of the user licenses available on both servers in the server group. To order additional or upgraded Cisco ER user licenses, perform these steps:
Procedure
Step 1 Step 2
Order additional or upgraded user licenses. You will receive a Product Authorization Key (PAK) for each additional user license. Go to Cisco.com and register your Cisco ER by supplying the PAK and the Media Access Control (MAC) address of your Cisco ER server. User licenses are usually installed on the primary Cisco ER server. After processing, you will receive the user license as a text-file email attachment.
Step 3 Step 4
Save the user license file to a local server so that it can be uploaded to the Cisco ER server. Upload the user license file. See the Uploading the Cisco Emergency Responder License File section on page 5-20 for instructions on how to upload the user licenses.
Determining Your License Requirements

For server licenses:

Order two server licenses for each 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.
1-6
OL-12376-01
Chapter 1
For user licenses:

Order one 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 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. (See the Understanding Cisco Emergency Responder Clusters and Groups section on page 1-12for more information on clusters.)
Example
If your Cisco ER configuration supports 500 users, you need to purchase:

One service license for your Cisco ER Publisher server; this license also provides for 100 users One service license for your Cisco ER Subscriber server; this license provides for another 100 users. Three additional user licenses for 100 users each.
How Cisco Emergency Responder Fits Into Your Network

Figure 1-1 shows how Cisco Emergency Responder (Cisco ER) fits into your network.
Figure 1-1 How Cisco ER Fits Into Your Network
IP phones IP IP Ethernet Switch SMTP mail server
Cisco Unified CM
PRI or CAMA gateway
Cisco ER group
Cisco ER depends on Cisco Unified Communications Manager for the corporate dial plan, which you must modify to send emergency calls to the Cisco ER group. See Chapter 3, Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 or Chapter 4, Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, for complete information about the required Cisco Unified Communications Manager configuration.
182287
Service Provider's Network
1-7
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. See the Configuring Switches for Cisco Emergency Responder section on page 5-39 for more information about setting up switches for Cisco ER. See the Managing Phones section on page 5-47 for information on how to configure switch ports so that 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 providers network so that Cisco ER can route emergency calls to the local public safety answering point (PSAP). Figure 1-1 shows one Cisco ER group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Cisco ER group, as long as the Cisco Unified Communications Managers are running the same software version. If you have a larger network, you can install multiple Cisco ER groups and create a Cisco ER cluster. See the Understanding Cisco Emergency Responder Clusters and Groups section on page 1-12 for a discussion of this more complex installation. See the What Happens When an Emergency Call Is Made section on page 1-8 for an explanation of the path an emergency call takes when managed by Cisco ER.
Related Topics

Understanding Cisco Emergency Responder Clusters and Groups, page 1-12 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Deploying Cisco Emergency Responder, page 1-21
What Happens When an Emergency Call Is Made

This topic describes the process Cisco Emergency Responder (Cisco ER) uses to handle emergency calls. Understanding this process can help you set up Cisco ER correctly and troubleshoot problems you might encounter. Figure 1-2 illustrates how Cisco ER routes an emergency call.
1-8
OL-12376-01
Chapter 1
Figure 1-2
How Cisco Emergency Responder Routes Emergency Calls

ALI database Service Provider's Network
Cisco Unified CM cluster

M
Gateway PSAP
Internal Network
ext. 3003
When someone uses extension 3003 to make an emergency call:

1. 2.
Cisco Unified Communications Manager routes the call to Cisco ER. Cisco ER gets the route pattern configured for the emergency response location (ERL) of the caller. Refer to the Cisco Emergency Responders Call Routing Order section on page 1-10 for information on the order of call routing. Cisco ER converts the calling partys number to the route pattern configured for the callers ERL. This route pattern is configured to pass the appropriate emergency location identification number (ELIN) to the public safety answering point (PSAP). The ELIN is a telephone number the PSAP can use to call back the emergency caller. Cisco ER saves a mapping between the callers extension and the ELIN, by default, for up to three hours. The mapping might be overwritten by subsequent calls before the entry times-out. You can also configure the time-out to be longer or shorter than three hours (see the Cisco ER Group Settings section on page A-3). Cisco ER routes the call using the route pattern configured for the caller's ERL. This route pattern in turn uses the configured route list to send the emergency call to the appropriate service provider's network. The service provider looks up the ELIN in the automatic location information (ALI) database, and routes the call to the appropriate local PSAP. The PSAP receives the phone call and looks up the ALI in the ALI database. Concurrently, Cisco ER sends web alerts to the Cisco ER user. In addition, Cisco ER calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Cisco ER also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails. If an emergency call is cut off unexpectedly, the PSAP can call back the emergency caller using the ELIN. The call to the ELIN is routed to Cisco ER, and Cisco ER converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.
3.
4.
5.
6.
7.
182288
Cisco ER group
IP
1-9
To ensure proper performance and eliminate major points of failure, verify the following:

For the emergency call to be routed correctly, the callers phone must be assigned to the correct ERL. To check the correctness of the ERL associated with the phones, use the ERL debug tool. Another potential problem in routing the call correctly lies with the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network. This can send the emergency call to the wrong PSAP. Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service providers network topology more than on your networks topology. In the United States, the emergency call network is tandem to the PSTN, so simply connecting to the PSTN does not ensure the correct routing of emergency calls.
The call might be routed incorrectly in the service providers network if the information in the ALI database is incorrect. Ensure that you export your ALI data and submit it to the service provider, and resubmit it whenever you change ELIN or location information. The PSAP might not be able to successfully call back an emergency caller if a lot of emergency calls are made from an ERL. Cisco ER caches the ELIN-to-extension mapping for up to three hours. If you have two ELINs defined for an ERL, and three emergency calls are made in a three-hour window, the first ELIN is used twice: once for the first caller, then reused for the third caller. If the PSAP calls the first ELIN, the PSAP will reach the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs you define for an ERL and the typical rate of emergency calls in the ERL.
Cisco Emergency Responders Call Routing Order

Cisco ER directs emergency calls based on the location of the phone from which the call is placed. The location of the phone is determined by the following methods, in order of precedence:
Synthetic phonesThe MAC address of the phone matches that of a synthetic phone and is assigned to a test Emergency Response Location (ERL). See the Adding Synthetic Phones section on page 5-57 and the Configuring Test ERLs section on page 5-34. IP Phones tracked behind a switch portThe MAC address of the IP phone is tracked behind a switch port assigned to an ERL. See the Configuring Switch Ports section on page 5-47. IP Phones tracked using IP subnetThe IP address of an IP phone belongs to an IP subnet assigned to an ERL. See the Configuring IP Subnet-based ERLs section on page 5-33. IP Phones tracked by another (remote) Cisco ER server group in the same Cisco ER clusterThe remote server group tracks an IP phone behind a switch port or by IP subnet. When an emergency call is received, it is forwarded to the Cisco Unified Communications Manager cluster served by the remote Cisco ER server group. See the Phones Moving Between Clusters section on page 11-23. Manually configured phonesThe line number of the phone is manually assigned to an ERL. See the Manually Defining a Phone section on page 5-53. Unlocated PhonesThe MAC address of an IP phone is assigned to an ERL. See the Identifying Unlocated Phones section on page 5-52. Default ERLNone of the above criteria is used to determine the phone location. The call is routed to the default ERL. See the Setting Up the Default ERL section on page 5-28.
Note
MAC and/or IP address tracking is recommended for Cisco Unified IP Phones. IP phones which are not tracked by MAC or IP address will appear as unlocated phones, even if they are assigned a location by manual line number configuration.
1-10
OL-12376-01
Chapter 1
Customers should resolve problems that prevent IP phones from being tracked by MAC or IP address (see the Too Many Unlocated Phones section on page 11-2) so that IP phones will be not removed from the Unlocated Phones page. An ERL may be assigned directly to an IP phone on the Unlocated Phones page, but this assignment will not take effect if the phone is assigned a location by manual line number configuration. Use the ERL Debug Tool to determine the ERL assignment in effect for an IP phone that appears on the Unlocated Phones page.
Identifying Unlocated Phones
Cisco ER defines unlocated phones as those Cisco Unified IP Phones which meet all of the criteria below:

The IP phone is registered to a Cisco Unified Communications Manager known to the Cisco ER group. The MAC address of the IP phone is not tracked behind a switch port. The IP address of the IP phone is not tracked using IP subnets. The MAC address of the IP phone is not defined as a synthetic phone in Cisco ER.
Note
Cisco Unified IP Phones tracked by a remote Cisco ER server group and IP phones having line numbers manually assigned to an ERL will also appear in the Unlocated Phones screen.
Assigning ERLs to Unlocated Phones
Cisco ER provides a procedure to assign an ERL to IP phones that are displayed on the Unlocated Phones screen. This assignment associates the MAC address of the unlocated phone with an ERL that is selected by the administrator. These rules apply to this association:
The association of an ERL with an IP phone on the Unlocated Phones page does not change the status of the IP phone; it remains on the Unlocated Phones page due to the fact that the IP phone will continue to match the criteria for unlocated phones described above. The ERL association is used only when the IP phone is unlocated, as determined by Cisco ER, using the above rule.
For example, Phone A is currently unlocated and appears on the Unlocated Phones page. Using the ERL assignment feature for unlocated phones, Location A is assigned as the ERL for this phone. A subsequent phone tracking cycle finds Phone A behind a switch port and it no longer appears in the Unlocated Phones page. The Phone A-to-Location-A assignment is no longer valid. Because the association is persistent, if the IP phone is unlocated at any future time, the assignment will be valid.
Location Information for Calls Forwarded by CTI Applications

If emergency calls are forwarded to 911 by computer telephony integration (CTI) applications, such as Cisco Unity, then the location used for call routing and PSAP reporting will be the location of the application server, not the location of the original caller. This remains true even if the application retains the original calling line number, as is made possible in Cisco Unified CallManager 4.2(3) and 4.3, and in Cisco Unified Communications Manager 5.1 and 6.0. For this reason, you should dial 911 directly.
Related Topics

Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Data Integrity and Reliability Considerations, page 1-16 Understanding ERLs, page 5-25
1-11
Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 4-16 Preparing Your Network For Cisco Emergency Responder, page 1-17
Understanding Cisco Emergency Responder Clusters and Groups

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. Cisco ER 2.0 uses two separate databases:

One database stores Cisco ER configuration information. The second database stores Cisco ER cluster information.
During installation, both databases are created on each Cisco ER server. However, only one Cisco ER server contains cluster data.
Note
You cannot deploy different versions of Cisco ER in the same Cisco ER group. If you are upgrading to Cisco ER 2.0, make sure to upgrade both Cisco ER servers to version 2.0. Figure 1-3 shows how Cisco Emergency Responder (Cisco ER) groups can be joined in a single Cisco ER cluster.
1-12
OL-12376-01
Chapter 1
Figure 1-3
Cisco Unified CM cluster A
M M
Understanding the Relationship between Cisco ER Groups and Cisco ER Clusters

Cisco Unified CM cluster B
M M
Cisco ER Cluster Information C isco ER Server Group 2 C isco ER Server Group 1 Cisco ER2 subscriber Cisco ER1 subscriber DB Cisco ER2 publisher Cisco ER1 publisher DB DB
MSDE DB
Cisco ER Cluster DB empty Cisco ER Cluster DB Containing Cisco ER cluster data Cisco ER DB Containing Cisco ER configuration data
182289
In this example:

There are two Cisco Unified Communications Manager clusters, CUCM cluster A and CUCM cluster B. Cisco ER Server Group 1 and Cisco ER Server Group 2 form a single Cisco ER cluster. Cisco ER Server Group 1 supports CUCM cluster A and Cisco ER Server Group 2 supports CUCM cluster B. Cisco ER1 Publishers cluster database stores the Cisco ER cluster information for both Cisco ER server groups. Dotted lines show the Cisco ER servers communications with the cluster database host. Each Cisco ER server has a database containing the Cisco ER configuration information.
Note
For Cisco ER intra-cluster phone tracking to work accurately, a Cisco ER server in the cluster must be able to be found by its hostname and must be able to be reached on the network from all other Cisco ER servers.
1-13
Note
If you enter the system administrators e-mail account in the System Administrator Mail ID field when you configure the Cisco ER Server Group Settings, the system administrator receives an e-mail notification when the standby server handles a call or when the standby server takes over for the primary server. (See the Configuring a Cisco Emergency Responder Server Group section on page 5-16.) To complete the creation of the Cisco ER cluster, you must create inter-cluster trunks and route patterns to allow the Cisco ER groups to hand off emergency calls between the groups (see the Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications section on page 4-17) and configure these route patterns in Cisco ER (see the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18).
Caution
Before you create a Cisco ER cluster, be aware that the dial plans in all Cisco Unified Communications Manager clusters supported by the Cisco ER cluster must be unique. For example, extension 2002 can only be defined in one Cisco Unified Communications Manager cluster. If you have overlapping dial plans, you must have separate Cisco ER clusters, which means you cannot support dynamic phone movement between those Cisco Unified Communications Manager clusters.
Moving Phone Between Clusters

The following scenario illustrates how Cisco ER treats phones moving between clusters:
Server Group A (SGA) has a phone (Phone_1) that is moving out of SGA.
Cisco ER discovers Phone_1 in Server Group B (SGB). The Unlocated Phones page in SGA will display the phone in SGB.
If both the Cisco ER servers (Publisher and Subscriber) in SGB go down, SGA will still display Phone_1 in SGB.
Calls made from Phone_1 during this time will be redirected to SGB and Cisco ER will take the
same steps to route this emergency call when Cisco ER servers are not there in SGB.
Phone_1 will also be treated like any other phone in SGB when both the SGB Cisco ER servers
are down.
If Phone_1 moves to Server Group C (SGC):

It will be discovered after the next incremental phone tracking on SGA and then in SGC. The Unlocated Phones page will change the association of Phone_1 to SGC.
If Phone_1 moves back to SGA, it will be discovered in the next incremental phone tracking and displayed under the corresponding switch port. A single Cisco ER group cannot support clusters with a mix of Cisco Unified Communications Manager versions. For example, Cisco ER can support all Cisco Unified CallManager 4.2 clusters or all Cisco Unified CallManager 5.1 clusters. However, a Cisco ER cluster can contain Cisco ER groups that support different versions of Cisco Unified Communications Manager. In this way, Cisco ER can support a mix of Cisco Unified Communications Manager versions in your telephony network.
Be aware of the following when planning your Cisco ER system:
A Cisco ER 2.0 server group can operate with other Cisco ER 2.0 server groups or with Cisco ER 1.3 server groups.
1-14
OL-12376-01
Chapter 1
Related Topics

How Cisco Emergency Responder Fits Into Your Network, page 1-7 What Happens When an Emergency Call Is Made, page 1-8
Determining the Required Number of Cisco Emergency Responder Groups

To ensure efficient Cisco Emergency Responder (Cisco ER) performance, you should take the limits each Cisco ER group can support into account when planning your Cisco ER deployment. Keep in mind that a single Cisco Unified Communications Manager cluster can only be supported by one Cisco ER group, although a single Cisco ER group can support more than one Cisco Unified Communications Manager cluster. Refer to the Release Notes for Cisco Emergency Responder 2.0 for the capacities of a single Cisco ER group with your configuration. Be aware that you might meet the maximum figures for one limitation without reaching the figures for another. For example, you might define 1,000 switches, but have fewer than 30,000 switch ports. You can install additional groups to manage larger networks. Each Cisco ER group can work with one or more Cisco Unified Communications Manager clusters. In addition to these per group limits, you must also consider the territories covered by the service providers ALI database providers. If your network extends into more than one ALI database providers territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats. To have a single Cisco ER group support multiple LECs, follow these steps:
Procedure
Step 1 Step 2 Step 3
Obtain an ALI record file output from Cisco ER in standard NENA format. This file contains the records destined for multiple LECs. Make a copy of the original file for each required ALI format (one copy per LEC). Using the AFT of the first LEC (for example, LEC-A), load a copy of the NENA-formatted file and delete the records of all the ELINs associated with the other LECs. (For information on using the AFT, see Chapter 12, Using the ALI Formatting Tool.) The information to delete can usually be identified by NPA (or area code). Save the resulting file in the required ALI format for LEC-A, and name the file accordingly. Repeat steps 3 and 4 for each LEC.
Step 4 Step 5
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.
Related Topics

Understanding Cisco Emergency Responder Clusters and Groups, page 1-12 Deploying Cisco Emergency Responder, page 1-21 Negotiate ALI Submission Requirements With Your Service Provider, page 1-19 Exporting ALI Information for Submission to Your Service Provider, page 5-37
1-15
Chapter 12, Using the ALI Formatting Tool ALI Formatting Tool, page A-60
Data Integrity and Reliability Considerations

The correct routing of emergency calls to the local PSAP is based on your ERL configuration. Inside your network, correct identification of the ERL for a phone determines which gateway is used to connect to the service providers network. In the service providers network, the routing is based on the ELIN, which is also used to look up the ALI for the caller. Thus, your ERL configuration must be reliable so that the correct ELIN is assigned to the emergency call. These are the things to consider to maintain the reliability of your ERL configuration:
ERLs are assigned to switch ports based on the location of the device attached to the port, not the location of the port itself. Thus, if you change the wire plugged into a port (for example, by switching wires between two or more ports), there is the potential that the device now plugged into the port is actually in a different ERL. If you do not change the ERL assigned to the port, the incorrect ELIN will be used for the port, and the wrong ALI sent to the PSAP. This type of change will not normally result in an incorrectly routed call, because it is unlikely that a single LAN switch will connect to ERLs serviced by separate PSAPs. However, the ALI sent will be incorrect, with the possibility that your security staff will search the third floor for an emergency when the caller is actually on the fourth floor. To prevent this problem, ensure that your wiring closets are secure, and train your networking staff to avoid swapping wires between switch ports.
If you have phones that Cisco ER cannot automatically track, ensure that any moves, adds, or changes to these phones also result in an update to the Cisco ER configuration. See the Manually Defining a Phone section on page 5-53 for information on defining these types of phones.
Note
If the switch port mapping changes, an email alert is sent. Prior to Cisco ER 1.2, if registered phones were not found behind a switch port, Cisco ER would list the phone in the Unlocated Phones page. Cisco ER 1.2 and later locates these phones as follows:
If a registered phone is not found behind a switch port, it may be found in one of the configured
IP subnets.
If a registered phone is not behind a switch port, or the IP Subnet of the phone is not configured,
or the phone is not configured as a synthetic phone, Cisco ER lists the phone in the Unlocated Phones page. To determine the ERL that Cisco ER will use for call routing, use the ERL Debug Tool to search for the phone. The search yields the current ERL that will be used in routing the emergency call from this phone and also why Cisco ER chose that ERL. For more information, see the Using the Cisco Emergency Responder Admin Utility section on page 11-19.
1-16
OL-12376-01
Chapter 1
Planning for Cisco Emergency Responder 2.0 Preparing Your Network For Cisco Emergency Responder
When you install Cisco ER 2.0, you install a Publisher server (primary) and a Subscriber server (backup) that points to the Publisher. The Publisher server and the Subscriber server make up a Cisco ER Server Group. This redundancy helps to ensure that the failure of one server does not affect the ability to make emergency calls. Consider installing the standby server in a physically separate location from the primary server, and on a separate subnet not separated by a WAN link. This separation can protect against some types of disruption, for example, a fire in the building housing the primary server, or the loss of connectivity to the subnet hosting the primary server. Ensure that the Cisco ER configuration is regularly updated as switches are added, removed, or upgraded (for example, by adding or changing modules). When you change a switch, run the switch-port and phone update process on the switch by viewing the switch in Cisco ER and clicking Locate Switch Ports. See the Identifying the LAN Switches section on page 5-42 for more information. Any phones connected to undefined switches are listed as unlocated phones in Cisco ER. If you changed a defined switch, new or changed ports become ports without any ERL association. You should assign ERLs for the new or changed switch ports. See the Understanding the Network Administrators Role section on page 10-3 and the Understanding the ERL Administrators Role section on page 10-2 for information on the recurring tasks involved in network changes.
As you change your ERL/ALI configuration, you must export the information and send it to your service provider for inclusion in the ALI database. This ensures that emergency calls are routed to the correct PSAP, and that the PSAP is presented with the correct ALI. See the Exporting ERL Information section on page 5-36 and Exporting ALI Information for Submission to Your Service Provider section on page 5-37 for more information.
Related Topics

What Happens When an Emergency Call Is Made, page 1-8 Understanding Cisco Emergency Responder Clusters and Groups, page 1-12 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Preparing Users for Cisco Emergency Responder, page 10-1
Preparing Your Network For Cisco Emergency Responder

These topics describe the steps you should take to prepare your network before deploying Cisco Emergency Responder.

Obtain CAMA or PRI Trunks to the PSTN, page 1-17 Obtain DID Numbers from Your Service Provider, page 1-18 Negotiate ALI Submission Requirements With Your Service Provider, page 1-19 Upgrade Switches and Phones, page 1-19
Obtain CAMA or PRI Trunks to the PSTN

To handle emergency calls, you must obtain PRI or CAMA trunks to connect to your service provider. Your service provider might support only one type of trunk. If you have an option, work with your service provider to decide on the type of connection that works best for you.
1-17
Chapter 1 Preparing Your Network For Cisco Emergency Responder
Consider these issues:
PRIIf you use a PRI connection for emergency calls, you can share the connection with regular telephone traffic. If you use the trunk for regular traffic, monitor trunk usage to ensure there is sufficient available bandwidth to handle emergency calls. If your capacity is inadequate, an emergency caller might get a busy signal when trying to make the call. Ensure you do capacity planning based on emergency call requirements. When you configure the PRI trunk, you must configure it so that it sends the actual calling partys number rather than a generic number (such as the main number of the site). Otherwise, the PSAP will not receive the expected ELIN, and the emergency call might not be routed to the right PSAP.
CAMACAMA trunks are dedicated to emergency calls, and are available in most areas. You do not need to do any capacity planning for CAMA trunks, because they are never used by regular voice traffic.
Work with your service provider to determine how many trunks are required for your network. For example, some service providers use a guideline of two CAMA trunks for 10,000 phones. Also, the number of trunks can differ depending on the distribution of your offices with respect to the local PSAPs. For example, if you have offices in New York and Chicago, you would need trunks in both cities, even if your total number of telephones would require fewer trunks if your office was only in New York. Your service provider, who knows the layout of the emergency call network, can direct you on trunk requirements that are based on PSAP accessibility.
Related Topics
Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 4-16
Obtain DID Numbers from Your Service Provider

You must obtain direct inward dial (DID) numbers from your service provider for use as emergency location identification numbers (ELIN) for your emergency response locations (ERL). In general, you must have at least one unique number per ERL. Emergency calls are routed to the local PSAP based on the ELIN of the ERL, so if you do not have unique ELINs, the call cannot be routed properly. The ALI database provider also might not accept ALIs that include duplicate ELINs. You might want to have more than one ELIN per ERL. If your ERLs include more than one phone, you might have more than one emergency call made from an ERL in a short time (less than three hours). If you assign only one ELIN to the ERL, that ELIN is reused for each emergency call. Thus, if four people make emergency calls in the space of an hour, if the PSAP calls the ELIN, the PSAP will connect to the last caller. This might be a problem if the PSAP was trying to contact one of the earlier callers. If you define more than one ELIN per ERL, Cisco Emergency Responder (Cisco ER) uses those ELINs in sequence until all are used, then reuses the ELINs in order. Cisco ER maintains the link between the ELIN and the extension of the actual emergency caller for up to three hours. Because you need to purchase these DIDs from your service provider, you must balance the needs of your budget with the needs of maintaining the capability of the PSAP to reach the correct caller.
Note
The number of DIDs you obtain is not related to the number of emergency calls Cisco ER can handle. Because Cisco ER reuses the ELINs you define, every emergency call gets handled and routed to the correct PSAP. The number of ELINs only influences the success rate of the PSAP calling back the desired emergency caller.
1-18
OL-12376-01
Chapter 1
Planning for Cisco Emergency Responder 2.0 Preparing Your Network For Cisco Emergency Responder
Related Topics

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Creating ERLs, page 5-28
Negotiate ALI Submission Requirements With Your Service Provider

Emergency calls are routed to the appropriate PSAP based on the emergency location identification number (ELIN) of the emergency caller. To route the call, the telephony network must have your automatic location information (ALI) that maps these ELINs to a location. Besides routing the call appropriately, the ALI database also supplies the location information that appears on the PSAPs screens to help them locate the caller. Cisco ER includes features to create ALIs and to export them in a variety of formats that should be acceptable to your service provider. After you create your ERL/ALI configuration, you must export the ALI data and send it to the ALI database provider. How you send the data can vary from location to location or service provider to service provider. You must work with your service provider to determine the services you can select for submitting ALI data. At a minimum, you must know the data format they expect, and the transmission method they require. Cisco ER does not include any automated capability for submitting ALIs.
Tip
Before deploying Cisco ER throughout your network, test the ALI submission process with your service provider. With your service providers help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider can have slightly different rules concerning ALI information. Cisco ER allows you to create ALI data according to the general NENA standards, but your service provider or database provider might have stricter rules.
Related Topics

Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Creating ERLs, page 5-28 Exporting ERL Information, page 5-36
Upgrade Switches and Phones

The most powerful capability of Cisco Emergency Responder (Cisco ER) is the ability to automatically track the addition or movement of telephones in your network. This dynamic capability helps ensure that emergency calls are routed to the local PSAP, even if a user moves a phone between cities. This can reduce the cost of maintaining your telephone network, simplifying moves, adds, or changes. However, Cisco ER can only automatically track telephone movement for certain types of phones, and for phones attached to certain types of switch ports. See Network Hardware and Software Requirements section on page 1-4 for a list of these phones and switches. To achieve full automation, update your switches to supported models or software versions, and replace your telephones with supported models.
1-19
Chapter 1 Preparing Your Staff for Cisco Emergency Responder
Related Topics

Configuring Switches for Cisco Emergency Responder, page 5-39 Managing Phones, page 5-47
Preparing Your Staff for Cisco Emergency Responder

Cisco Emergency Responder (Cisco ER) does not replace your existing emergency procedures. Instead, Cisco ER is a tool you can use to augment those procedures. Before deploying Cisco ER, consider how it fits into your procedures and how you want to use the Cisco ER systems capabilities. These are the main things to consider when deciding how to use Cisco ER:
When someone makes an emergency call, Cisco ER notifies the assigned onsite alert (security) personnel (your emergency response teams) of the location of the caller. This information is, for the most part, the ERL name. Consider working with your emergency response teams to come up with an ERL naming strategy that will help them respond quickly to emergencies. Incorporating building names, floor numbers, and other readily understood location information in the name are the types of things to consider. Cisco ER lets you define three types of administrative user, so you can divide responsibilities for overall Cisco ER system administration, network administration, and ERL administration. The skills and knowledge necessary for these tasks might be rare to find in one person. Consider dividing Cisco ER configuration responsibilities according to these skills. The routing of emergency calls, and the transmission of the correct ALI, is only as good as the reliability of the ALI definitions you submit to your service provider and in the stability of your network topology. Ensure that your ERL administrator understands the importance of keeping the ALI data up-to-date, and that your network administrator understands the importance of maintaining a stable network. See the Data Integrity and Reliability Considerations section on page 1-16 for more information about maintaining data integrity.
Related Topics

Preparing Onsite Alert (Security) Personnel for Cisco Emergency Responder, page 10-1 Understanding the ERL Administrators Role, page 10-2 Understanding the Network Administrators Role, page 10-3 Understanding the Cisco Emergency Responder System Administrators Role, page 10-4
1-20
OL-12376-01
Chapter 1
Planning for Cisco Emergency Responder 2.0 Deploying Cisco Emergency Responder
Deploying Cisco Emergency Responder

These topics describe deployment models for various types of networks. You can use these examples as modules, combining them to form a larger, more complex network.

Deploying Cisco Emergency Responder in One Main Site with One PSAP, page 1-21 Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs, page 1-22 Deploying Cisco Emergency Responder In One Main Site with Satellite Offices, page 1-23 Deploying Cisco Emergency Responder In Two Main Sites, page 1-25
Deploying Cisco Emergency Responder in One Main Site with One PSAP
To support a simple telephony network consisting of a single Cisco Unified Communications Manager cluster, install two Cisco ER servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher. Because there is only one local PSAP, you only need one gateway to the service providers network, although capacity planning for your telephony network might require more than one gateway. Configure all route patterns to use this gateway. Figure 1-4 shows how Cisco Emergency Responder (Cisco ER) fits into a simple telephony network where you have a single Cisco Unified Communications Manager cluster.
Figure 1-4 Deploying Cisco ER in One Main Site with One PSAP
IP phones IP IP
Gateway Service Provider's Network
M
182290
Cisco ER group
Cisco Unified CM
PSAP
See these examples to extend this example to more complex networks:

Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs, page 1-22 Deploying Cisco Emergency Responder In One Main Site with Satellite Offices, page 1-23 Deploying Cisco Emergency Responder In Two Main Sites, page 1-25
1-21
Chapter 1 Deploying Cisco Emergency Responder
Related Topics

What Happens When an Emergency Call Is Made, page 1-8 How Cisco Emergency Responder Fits Into Your Network, page 1-7 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0, page 3-1 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Overview of Cisco Emergency Responder Configuration, page 5-1
Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs
Figure 1-5 illustrates the Cisco Emergency Responder (Cisco ER) configuration if you have one main site that is served by two or more PSAPs. This example assumes you have one Cisco Unified Communications Manager cluster. If you have more than one, the setup is logically the same as the one discussed in the Deploying Cisco Emergency Responder In Two Main Sites section on page 1-25.
Figure 1-5 Deploying Cisco ER in One Main Site with Two or More PSAPs
PSAP-A
PSAP-B
Building A IP phones IP IP Gateway A Building B
Gateway B
Cisco Unified CM IP IP
182291
Cisco ER group
IP phones
To support this type of network, install two Cisco ER servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher.
1-22
OL-12376-01
Chapter 1
Because there are two PSAPs serving the location, you probably need more than one gateway connecting to different parts of the service providers network. However, this depends on the layout of the service providers network: you might only need one gateway if the PSAPs are served by a selective router that can intelligently route emergency calls to more than one PSAP. Consult with your service provider to determine the requirements for your buildings. In this example, we assume you will need two gateways. Of course, capacity planning for your telephony network might require more than one gateway for each link. After setting up the gateways to correctly connect to the service providers network, configure all route patterns used in Building A ERLs to use gateway A, and all route patterns used in Building B ERLs to use gateway B. As phones move between buildings, Cisco ER dynamically updates their ERLs so that emergency calls get routed out of the desired gateway. See these examples to extend this example to other networks:

Deploying Cisco Emergency Responder in One Main Site with One PSAP, page 1-21 Deploying Cisco Emergency Responder In One Main Site with Satellite Offices, page 1-23 Deploying Cisco Emergency Responder In Two Main Sites, page 1-25
Related Topics

What Happens When an Emergency Call Is Made, page 1-8 How Cisco Emergency Responder Fits Into Your Network, page 1-7 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Overview of Cisco Emergency Responder Configuration, page 5-1
Deploying Cisco Emergency Responder In One Main Site with Satellite Offices
Figure 1-6 illustrates the Cisco Emergency Responder (Cisco ER) configuration if you have one main site that serves one or more satellite offices, that is, where the phones in the satellite office are run from the Cisco Unified Communications Manager cluster on the main site. If the satellite office has its own Cisco Unified Communications Manager cluster, see the Deploying Cisco Emergency Responder In Two Main Sites section on page 1-25.
1-23
Figure 1-6
Deploying Cisco ER in One Main Site with Satellite Offices
Chillicothe PSAP
Columbus Cisco ER group Gateway COL Chillicothe
Columbus PSAP
Router
IP IP IP phones
IP IP IP phones
Caution
In this configuration, if the WAN link between the offices goes down, the people in the satellite office cannot make emergency calls. To support this type of network, install two Cisco ER servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher. Install both servers in the main office. Most likely, there are separate PSAPs serving the main (Columbus) and satellite (Chillicothe) offices. Thus, you probably need more than one gateway connecting to different parts of the service providers network (you might even have different service providers). However, this depends on the layout of the service providers network: you might only need one gateway if the PSAPs are served by a shared switch. Consult with your service provider to determine the requirements for your buildings. In this example, we assume you will need two gateways. Of course, capacity planning for your telephony network might require more than one gateway for each link. After setting up the gateways to correctly connect to the service providers network, configure all route patterns used in Columbuss ERLs to use gateway COL, and all route patterns used in Chillicothes ERLs to use gateway CHIL. As phones move between sites, Cisco ER dynamically updates their ERLs so that emergency calls get routed out of the desired gateway. You might also need to tune SNMP performance to account for the WAN link. Cisco ER must do SNMP queries of the remote sites switches to track phone movements there, and you might run into SNMP time-out problems if you do not allow enough time or retries to make a successful SNMP query. See the Configuring the SNMP Connection section on page 5-39 for more information.
1-24
182292
Cisco Unified CM (All)
Gateway CHIL
OL-12376-01
Chapter 1
See these examples to extend this example to other networks:

Deploying Cisco Emergency Responder in One Main Site with One PSAP, page 1-21 Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs, page 1-22 Deploying Cisco Emergency Responder In Two Main Sites, page 1-25
Tip
If the satellite office is small (fewer than 50 phones) and you are using survivable remote site telephony (SRST), it is probably easier to support emergency calls directly by configuring the gateway in the remote office to send 911 calls to an FXO port that has a CAMA trunk to the local PSAP rather than to Cisco ER in the main office.
Related Topics

What Happens When an Emergency Call Is Made, page 1-8 How Cisco Emergency Responder Fits Into Your Network, page 1-7 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Overview of Cisco Emergency Responder Configuration, page 5-1
Deploying Cisco Emergency Responder In Two Main Sites

Figure 1-7 illustrates the Cisco Emergency Responder (Cisco ER) configuration if you have two (or more) main sites, each served by a separate PSAP.
1-25
Figure 1-7
Deploying Cisco ER in Two Main Sites
Chicago Cisco ER group Gateway CHI Chicago PSAP
New York Gateway NYC Cisco ER group
NewYork PSAP Cisco Unfified CM-CHI

M
Inter-cluster trunk
Cisco Unified CM-NYC
IP IP IP phones
IP IP phones
182293
IP
You can adapt this example to a more complex setup by combining this discussion with these examples:
If some of your main sites have satellite offices, see the Deploying Cisco Emergency Responder In One Main Site with Satellite Offices section on page 1-23 for information on deploying Cisco ER in those offices.
If a main site is served by more than one PSAP, see the Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs section on page 1-22 for information on deploying Cisco ER in that site.To support this type of network:
Install two Cisco ER servers in Chicago and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher. After installation, select the Cisco ER Publisher server in the Chicago Cisco ER group for use as the cluster database. See Configuring the Cisco Emergency Responder Cluster and Cluster DB Host section on page 5-23. Install two Cisco ER servers in New York and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher. After installation, select the Cisco ER Publisher server in the Chicago Cisco ER group for use as the cluster database. See Configuring the Cisco Emergency Responder Cluster and Cluster DB Host section on page 5-23.
Most likely, there are separate PSAPs serving your main offices. In this example, Chicago and New York use different PSAPs. You need at least one gateway in Chicago, and one in New York, to connect to different parts of the service providers network (you might even have different service providers). Consult with your service provider to determine the requirements for your buildings. Of course, capacity planning for your telephony network might require more than one gateway in each site. After setting up the gateways to correctly connect to the service providers network, configure all route patterns used in Chicagos ERLs to use gateway CHI, and all route patterns used in New Yorks ERLs to use gateway NYC.
1-26
OL-12376-01
Chapter 1
To enable phone movement between Chicago and New York, you must also configure an inter-cluster trunk to link the Cisco Unified Communications Manager clusters, and create an inter-Cisco ER group route pattern so that Cisco ER can transfer calls between Cisco Unified Communications Manager clusters served by separate Cisco ER groups. The Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications section on page 4-17 goes into more details about how Cisco ER handles phone movement in this situation. As phones move between sites, Cisco ER dynamically updates their ERLs so that emergency calls get routed out of the desired gateway. However, if the WAN link becomes unavailable, Cisco ER can not track phone movement between the sites. See these examples to extend this example to other networks:

Deploying Cisco Emergency Responder in One Main Site with One PSAP, page 1-21 Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs, page 1-22 Deploying Cisco Emergency Responder In One Main Site with Satellite Offices, page 1-23
Related Topics

What Happens When an Emergency Call Is Made, page 1-8 How Cisco Emergency Responder Fits Into Your Network, page 1-7 Determining the Required Number of Cisco Emergency Responder Groups, page 1-15 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0, page 3-1 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Overview of Cisco Emergency Responder Configuration, page 5-1
1-27
1-28
OL-12376-01
C H A P T E R
Installing Cisco Emergency Responder 2.0

Cisco Emergency Responder (Cisco ER) 2.0 is distributed on an installation DVD that contains everything that is required to install Cisco ER 2.0, including the Cisco Unified Communications Operating System software. You must upgrade Cisco ER 2.0 from Cisco ER 1.3.x only. You cannot upgrade directly to Cisco ER 2.0 from earlier versions of Cisco ER, or download Cisco ER 2.0 from the Cisco.com website. These topics cover the hardware and software requirements and upgrade instructions for Cisco ER:

Hardware and Software Prerequisites, page 2-1 Before You Install or Upgrade, page 2-1 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Upgrading from Cisco Emergency Responder 1.3 to Cisco Emergency Responder 2.0, page 2-9 Upgrading from Cisco Emergency Responder 2.0 to a Later Version, page 2-11
Hardware and Software Prerequisites

Cisco Emergency Responder (Cisco ER) requires specific hardware and software to run properly. Review the following sections before you proceed with the installation or upgrade to Cisco ER 2.0:
See the Release Notes for Cisco Emergency Responder 2.0 to verify that you have all the hardware and software, and in the supported versions, that you must install for Cisco ER and to check that your Cisco MCS Unified Communications Manager Appliance platform provides the Cisco ER capabilities to meet your configuration needs. (You can also use equivalent Cisco-certified servers.) See the Determining Your License Requirements section on page 1-6 to make sure that you have all the required license keys available before you begin the installation process.
Before You Install or Upgrade

The Cisco ER 2.0 installation process installs both the platform software and the Cisco ER 2.0 software. During the installation, you will be prompted to enter information needed by the system to complete the installation.
2-1
Chapter 2 Before You Install or Upgrade
Note
Cisco recommends that you perform the installation or upgrade during off-peak hours. The installation/upgrade procedure completely reformats the hard disk, so Cisco ER will be unavailable for the duration of the installation or upgrade. Review the following information before you install or upgrade your system to Cisco ER 2.0:
Cisco ER Versions:
Different versions of Cisco ER cannot be deployed in the same Cisco ER group. The primary
and the standby Cisco ER servers must be running the same version of Cisco ER. If you are upgrading to Cisco ER 2.0, make sure to upgrade both Cisco ER servers to version 2.0.
Note
Cisco ER 2.0 supports interoperability between two server groups in a cluster running different versions of Cisco ER. One server group in a cluster may be running Cisco ER 2.0 while another server group in the cluster is running Cisco ER 1.3. However, Cisco ER 2.0 will not interoperate with versions earlier than Cisco ER 1.3. Determine and list your Cisco ER hostname and passwords.
Decide on a permanent hostname for the Cisco ER server before you install Cisco ER. Changing
the hostname of a Cisco ER server after installation may cause problems.

The hostname for the Cisco ER 2.0 Publisher and Subscriber must not contain the underscore
character (_). If you have an existing Cisco ER server with an underscore in its hostname, change the hostname of the server prior to installing Cisco ER 2.0.
Decide on a password for the local CERAdministrator. If you encounter problems with the
Subscriber database setup, go to the Admin Utility web interface and use the Update > Publisher page to fix the problem. For more information, see the Using the Cisco Emergency Responder Admin Utility section on page 11-19.
Note
The CERAdministrator password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores. It must start with an alphanumeric character. Ethernet NIC speed and duplex mode:
Decide if you want to enable autonegotiation of Ethernet NIC speed and duplex If yes, you dont need any additional information If no, determine what Ethernet NIC speed and duplex mode you will use
DHCP Configuration
Decide if you want to use the Dynamic Host Configuration Protocol (DHCP) to allocate IP
addresses
If yes, you dont need any additional information If no, you will need to know the hostname, IP address, IP mask, and gateway address to enter
for the Static Network Configuration
2-2
OL-12376-01
Chapter 2
Installing Cisco Emergency Responder 2.0 Installing Cisco Emergency Responder 2.0 on a New System
NTP Client information

The system will ask if you want to set up external Network Time Protocol (NTP) servers. Cisco
recommends that you use external NTP servers to ensure that the system time is accurate.
If you decide to use external NTP servers, you will need to enter the IP address or hostname of
the servers.
If you do not choose to use external NTP servers, you will need to enter the system date and
time clock information manually.
Decide on a Database Access Security password

The system requires a database access security password to allow the nodes in a servergroup to
communicate. The password is shared with all nodes in the servergroup.

The password must be at least six characters long and can contain alphanumeric characters,
hyphens, and underscores. It must start with an alphanumeric character.
SMTP Host Configuration (optional)

Decide if you want to use an SMTP host. If yes, determine the hostname or IP address of the SMTP host.
Caveats:
Once you upgrade your system to Cisco ER 2.0, you cannot downgrade your system to earlier
Cisco ER versions.
Review the release notes for Cisco ER 2.0 before installation:
http://www.cisco.com/en/US/products/sw/voicesw/ps842/prod_release_notes_list.html Install the components for Cisco ER 2.0 in the order shown in Table 2-1.
Table 2-1 Installation Tasks
Installation Task
1. 2. 3.
For More Information
Cisco Unified Communications Manager http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_suppo rt_series_home.html Cisco ER 2.0 as a new installation Cisco ER 2.0 as an upgrade Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Upgrading from Cisco Emergency Responder 1.3 to Cisco Emergency Responder 2.0, page 2-9.
Installing Cisco Emergency Responder 2.0 on a New System

This procedure describes how to install Cisco Emergency Responder (Cisco ER) 2.0 as a new installation. You enter Cisco ER group configuration through the Cisco ER Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following topics:

Installing the Cisco Emergency Responder Publisher, page 2-4 Installing the Cisco Emergency Responder Subscriber, page 2-8
2-3
Chapter 2 Installing Cisco Emergency Responder 2.0 on a New System
Installing the Cisco Emergency Responder Publisher

To install Cisco ER 2.0, you install the Publisher (primary) first, then you install the Subscriber (backup) on a separate server. You must install Cisco ER on separate servers from Cisco Unified Communications Manager or any Cisco Unified Communications applications. Allow approximately 1 hour to perform a new installation. To install the Publisher, follow these steps:
Procedure
Step 1
Insert the Cisco ER 2.0 Installation DVD. If the system finds the DVD, you are asked if you want to perform a media check prior to installation to determine if there are any problems with the DVD. The system displays the checksum of the DVD and instructs you to verify this checksum on the Cisco ER 2.0 website. At the bottom of the screen you will see instructions for moving between elements and for selecting elements, as follows:

Use the Tab key to advance to the next element Use the Alt-Tab key combination to return to the previous element Use the Space bar to select a highlighted element
If you choose to perform the media check, the system performs the media check and displays the results. If the result of the media check is PASS, click OK. The system install begins the installation. Skip to Step 2. If the result of the media check is FAIL, obtain a new installation DVD from Cisco Systems.
Step 2
The Cisco Unified Communications system installer starts. The Product Deployment Selection screen displays a message saying the Cisco Emergency Responder product suite will be installed. Click OK to continue. The Proceed with Install page displays the current software version on the hard drive (if any) and the software version on the installation DVD. If you are performing a fresh installation, there will be no software on the hard drive and the system asks if you want to proceed with the installation. Click Yes to proceed. If you are performing an upgrade, the system displays the current software version and asks it you want to overwrite the hard drive. Click Yes to proceed. If you click Yes, the system continues with the installation and the Platform Configuration Wizard appears. If you click No, the installation is terminated.
Step 3
Step 4
On the Platform Configuration Wizard page, click Proceed to continue with the platform installation. The Import Windows Data page appears. Skip to Step 5. If you click Skip, the system will install both the platform and Cisco ER software without prompting you to provide any information during the installation. Once the installation is completed and the system reboots, you will be prompted to enter the required configuration details.
Step 5
The Import Windows Data page prompts you to import data from a Windows version of Cisco ER. This page does not apply to fresh installations or to upgrades from earlier Linux-based versions of Cisco ER. Click No to proceed with the fresh installation. The Basic Install page appears. Click Continue to proceed. The Timezone Configuration page appears.
Step 6
2-4
OL-12376-01
Chapter 2
Step 7
Choose the correct timezone to use from the list provided. Use the following keys to move between elements on the Timezone Configuration page:

Arrow Up or Arrow Down to select a timezone from the list Tab to move to another field
After selecting the correct timezone, click OK. The Auto Negotiation Configuration page appears.
Step 8
Click Yes to enable autonegotiation of the Ethernet NIC speed and duplex mode. The DHCP Configuration page appears. If you click Yes, skip to Step 10. If you click No, the NIC Speed and Duplex Configuration page appears. On the NIC Speed and Duplex Configuration page, do the following:
a. b. c.
Step 9
Select the NIC Speed. The available options are 10 Megabit, 100 Megabit, or 1000 Megabit. Select the NIC Duplex setting. The available options are Full or Half. Click OK. The DHCP Configuration page appears.
Step 10
Click Yes if you want to use Dynamic Host Configuration Protocol (DHCP). The Administration Login Configuration page appears. Skip to Step 14. If you click No, the Static Network Configuration page appears. If you chose not to use DHCP, enter the following information on the Static Network Configuration page:

Step 11
Host Name IP Address IP Mask Gateway (GW) Address
Note
When upgrading from a Windows-based version of Cisco ER, the Host Name and IP Address must be the same as the Cisco ER 1.3.x server that is being upgraded.
Click OK. The DNS Client Configuration page appears.

Step 12
On the DNS Client Configuration page, you are asked if you want to configure the Domain Name System (DNS) client.
Note
Click the Help button for details on configuring DNS.
If you select Yes, a second DNS Client Configuration page appears. If you select No, the Administration Login Configuration page appears. Skip to Step 14.
Step 13
On the second DNS Client Configuration page, you are prompted to enter the following information:

Primary Secondary DNS (optional) Domain
Click OK. The Administration Login Configuration page appears.

Step 14
On the Administration Login Configuration page, enter an ID and password for the Administrator account. This password is used to access the CLI and the Cisco Unified OS Administration and Disaster Recovery System (DRS) websites. Click Help to display guidelines for creating this password.
2-5
When you have finished, click OK. The Certificate Information page appears.
Step 15
Enter the following information on the Certificate Information page:

Organization Unit Location State Country (select from the scroll-down menu).
Click OK. The Publisher Configuration page appears.

Step 16
Based on the type of installation you are performing, do one of the following:

If the server you are configuring is the Publisher in the server group, click Yes. The Network Time Protocol Client Configuration page appears. Proceed to Step 17. If the server you are installing is not the Publisher in the server group, you must first configure this server on the Publisher before you can proceed. Also, this server must have network access to the Publisher, which must be in service for the installation to complete successfully. Click No only if you are configuring the Subscriber. See the Installing the Cisco Emergency Responder Subscriber section on page 2-8 for information on installing the Subscriber. If you are performing an upgrade from Cisco ER 1.3.x, click Yes. Upgrades from Cisco ER 1.3.x can only be done on a Publisher. If you click No, you will receive an error message.
Step 17
On the Network Time Protocol Client Configuration page, you are asked if you want to set up external Network Time Protocol (NTP) servers.
Note
Cisco strongly recommends that you use external NTP servers to ensure that the system time is kept accurate.
If you click Yes, the system displays a second Network Time Protocol Client Configuration page. In the fields provided, enter the IP address or hostname of the external NTP servers, then click OK. The Database Access Security Configuration page displays. Skip to Step 18. If you click No, the Hardware Clock Configuration page appears. Enter the following information:

Year [yyyy] Month [mm] Day [dd] Hour [hh] Minute [mm] Second [ss]
When you have finished entering this information, click OK. The Database Access Security Configuration page appears.
Step 18
On the Database Access Security Configuration page, enter the security password and then confirm the password in the fields provided.
2-6
OL-12376-01
Chapter 2
Note
The security password must be at least six characters long and can contain alphanumeric characters, hyphens, and underscores. It must start with an alphanumeric character. The security password is used for secure communications between Cisco ER server groups when performing installation/upgrade, DRS backup or restore, and Point to a new Publisher operations.
Click Help to display guidelines. When you have finished, click OK. The SMTP Host Configuration page appears.
Step 19
You are asked if you want to configure a Simple Mail Transport Protocol (SMTP) host. This step is optional.
If you click Yes, a second SMTP Host Configuration page appears. Click Help for guidelines, then enter the SMTP hostname or IP address in the field provided. When you are finished, click OK. The Platform Configuration Confirmation page appears. If you click No, the Platform Configuration Confirmation page appears. Select OK to save the platform configuration information and continue with the installation. The Cisco Emergency Responder Configuration page appears.
Step 20
On the Platform Configuration Confirmation page, do one of the following:
Note Step 21
Once you select OK, you will not be able to modify the platform configuration information.
Select Back if you want to return to the previous page to make modifications. Continue to select Back to scroll through each platform configuration page. Select Cancel to cancel the installation. Enter the emergency number (for example, 911). Select the Cisco Unified Communications Manager version. Use the Up or Down arrows to select the version number, the select OK.
On the Cisco Emergency Responder Configuration page, do the following:

The Application User Password Configuration page appears.

Step 22
On the Application User Password Configuration page, enter and then confirm the application user password. This password is associated with the default CERAdministrator account and is used to log in to the Cisco ER Administration webpage. Click Help for guidelines. When you are finished, click OK. The Cisco Emergency Responder Configuration Confirmation page appears.
Step 23
On the Cisco Emergency Responder Configuration Confirmation page, do one of the following:
Select OK to save the Cisco Emergency Responder configuration information and continue with the installation. The system continues the installation process and then reboots.
Caution
Once you select OK, you will not be able to modify the Cisco Emergency Responder configuration information.

Select Back if you want to return to the previous page to make modifications. Continue to select Back to scroll through each Cisco ER configuration page. Select Cancel to cancel the installation.
2-7
Step 24
After the system reboots, it checks the status of various system components. If the system finds any problems, you will be prompted to correct the problem. If the system does not find any problems, the installation process continues. The system will eject the installation DVD, reboot, and then finish the installation. When the installation is complete, a command-line interface prompt appears.
Note
During this process, the system will display the MAC address of the Publisher. Write down the MAC address when it displays; you will use the MAC address later to acquire Cisco ER licenses. If you are not able to capture the MAC address during installation, you can look it up later. See the Server Licenses section on page 1-5 for information on looking up the server MAC address.
Step 25
To bring up the Cisco ER 2.0 websites, go to any Windows system on the network, start a supported web browser, and enter the following URL: http://your CER hostname/ or http://your CER IP address/
Installing the Cisco Emergency Responder Subscriber

After you install the Publisher, you must install the Cisco Emergency Responder (Cisco ER) Subscriber. You must install the Subscriber on a separate server from the Cisco ER Publisher.
Caution
You must complete the installation of the Publisher, which includes a system reboot, before you start to install the Subscriber. To install the Cisco ER 2.0 Subscriber, follow these steps:
Procedure
Step 1
On the Publisher server, add the details about the Subscriber server by doing the following:
a. b. c. d.
Log in the Publishers Cisco ER Administration website. Select System > Add Subscriber. The Add Server page appears. Enter the hostname and IP address of the new Subscriber and click Insert. The Add Subscriber appears again. In the Configured Servers list, check that the hostname/IP address of the new Subscriber is listed.
Step 2 Step 3
Follows Step 1 through Step 15 in the Installing Cisco Emergency Responder 2.0 on a New System section. After you complete Step 15, the Publisher Configuration page appears. On the Publisher Configuration page, select No to indicate that you are installing a Subscriber, not a Publisher. The system displays a warning saying that if this is not the Publisher, you must first configure this server using the Publishers Administration web interface before you can proceed (see Step 1 of this procedure for more information). Also, this server being added must have network access to the Publisher, which must be in service for the installation to complete successfully. Click OK to close the warning.
2-8
OL-12376-01
Chapter 2
Installing Cisco Emergency Responder 2.0 Using the DMA Tool
Step 4
The Publisher Access Configuration page appears. Enter the following:

Publishers hostname Publishers IP address Publishers Database/Security password
Step 5 Step 6
Verify the that Publisher information is correct and click OK. The Platform Configuration Complete page appears. Select one of the following options:

If the Publisher information is correct, click OK. If the information is not correct, click the Back button and make the needed corrections on the Publisher Access Configuration page. Then, click OK.
The installation of the Cisco ER Subscriber begins and will take an additional 20 to 30 minutes to complete.
Step 7
When the installation completes, go to the Cisco ER Administration website on the Subscriber to verify that the Subscriber was installed successfully. If the installation succeeded, a message saying Primary Cisco Emergency Responder is active will appear. This message indicates that the Subscriber was installed successfully.
Note
If the Subscriber installation cannot validate the Publisher, see the Cannot Validate Publisher section on page 11-15 in the Troubleshooting chapter.
Using the DMA Tool

Before you can upgrade from Cisco ER 1.3 to Cisco ER 2.0, you must use the Data Migration Assistant (DMA) tool to create a migration file containing your Cisco ER 1.3 configuration information. As part of the upgrade process, you will be prompted to provide the location of this migration file. For information on using the DMA tool, see the Data Migration Assistant Administration Guide, Release 5.1(1) or later.
Upgrading from Cisco Emergency Responder 1.3 to Cisco Emergency Responder 2.0
This procedure describes how to upgrade from Cisco Emergency Responder (Cisco ER) 1.3 to Cisco ER 2.0.
Note
The following upgrade procedure applies to upgrading only the Publisher node from Cisco ER 1.3 to Cisco ER 2.0. For Subscriber nodes, you must perform a fresh installation of Cisco ER 2.0. See the Installing the Cisco Emergency Responder Subscriber section on page 2-8 for further information. In addition, upgrades to Cisco ER 2.0 can be performed only from Cisco ER 1.3(1a) and 1.3(2).
2-9
Chapter 2 Upgrading from Cisco Emergency Responder 1.3 to Cisco Emergency Responder 2.0
Before You Begin
To migrate your existing data from a Cisco ER 1.3 system to Cisco ER 2.0, you must use the Data Migration Assistant (DMA) tool before beginning the upgrade process. See the Using the DMA Tool section on page 2-9 for information on using the DMA tool. In addition, you should perform a backup of your CER 1.3.x system using Cisco IP Telephony Backup and Restore System (BARS) before starting the upgrade. For information on performing a backup using BARS, go to the following URL and scroll down to find the Cisco IP Telephony Backup and Restore System (BARS) Administration Guide for your release version: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html To upgrade from Cisco ER 1,3 to Cisco ER 2.0, follow these steps:
Procedure
Step 1 Step 2 Step 3 Step 4
Follows Step 1 through Step 4 in the Installing the Cisco Emergency Responder Publisher section. After you complete Step 4, the Select Type of Installation page appears. On the Select Type of Installation page, select Windows Upgrade and click OK. Follow Step 7 through Step 19 in the section Installing the Cisco Emergency Responder Publisher. After you finish Step 19, the DMA Retrieval Mechanism Configuration page appears. The DMA Retrieval wizard prompts you to choose one of the DMA retrieval methods. The options are as follows:

SFTP FTP TAPE
Select the retrieval mechanism and click OK. If you chose SFTP or FTP, proceed to Step 5. If you chose TAPE, proceed to Step 6.
Step 5
The wizard displays the DMA Backup Configuration page.
Note
The installation wizard prompts you for the location of the tar ball that is created by the DMA tool. See the Using the DMA Tool section on page 2-9 for information on using the DMA tool.
Enter the following information:

Hostname/IP address of the sftp or ftp server on which the tar ball is located Remote file path Remote File Name of the tar ball Remote Login ID for the ftp/sftp server Remote password for the ftp/sftp server
Click OK.
Step 6 Step 7
If you chose TAPE in Step 4, insert the tape containing the tar ball file into the tape drive. Follow Step 20 through Step 25 in the Installing the Cisco Emergency Responder Publisher section on page 2-4 section to complete the upgrade from Cisco ER 1.3 to Cisco ER 2.0.
2-10
OL-12376-01
Chapter 2
Installing Cisco Emergency Responder 2.0 Upgrading from Cisco Emergency Responder 2.0 to a Later Version
Upgrading from Cisco Emergency Responder 2.0 to a Later Version

To upgrade from one version of Cisco ER 2.0 to a later version of Cisco ER 2.0, you use the Cisco Unified OS Administration web interface. See the Performing Software Upgrades section on page 7-13 for information on upgrading from one version of Cisco ER 2.0 to a later version of Cisco ER 2.0.
2-11
Chapter 2 Upgrading from Cisco Emergency Responder 2.0 to a Later Version
2-12
OL-12376-01
C H A P T E R
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0
This chapter describes procedures for configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder (Cisco ER) 2.0. If you are running Cisco Unified Communications Manager 5.0, 5.1, or 6.0, follow the procedures in Chapter 4, Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0. These topics describe the items you must configure in Cisco Unified CallManager 4.2 and 4.3 so that Cisco ER can work in your telephone network. These topics describe a sample Cisco Unified CallManager setupthe names chosen (for example, partition and calling search space names) are not required.

Setting Up Phone Route Plans, page 3-1 Setting Up Cisco Emergency Responder to Handle Emergency Calls, page 3-4 Creating a Cisco Emergency Responder Cisco Unified CallManager User, page 3-19
Understanding the Cisco Unified CallManager Examples
These sections represent an example setup, with sample values included for reference only. Your particular configuration depends on the needs of your network and your naming strategy. For these examples, you will be working with the following calling search spaces and partitions:

PhoneCSSincludes the Phones partition. E911CSSincludes the E911 and Phones partitions.
The examples are based on a single Cisco Unified CallManager cluster. If you have more than one cluster, you must repeat the configuration in each cluster, except for the emergency location identification number (ELIN) translation patterns. The ELIN translation patterns are only defined in the Cisco Unified CallManager cluster to which the gateway will send incoming calls from the public safety answering point (PSAP).
Setting Up Phone Route Plans

Before configuring Cisco ER, you must ensure that the phones that might be used to make emergency calls (typically all phones) are added and registered with Cisco Unified CallManager. Refer to the documentation and online help included with Cisco Unified CallManager if you need assistance completing this.
3-1
Chapter 3 Setting Up Phone Route Plans
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0
These sections provide an example setup for your network before adding Cisco ER:

Creating a Phone Partition, page 3-2 Creating a Phone Calling Search Space, page 3-2 Assigning the Partition and Calling Search Space to Phones, page 3-3
Creating a Phone Partition

If you have not already created a partition for the phones, do so now. To create a phone partition, follow these steps:
Procedure
Step 1
Select Route Plan > Partition in Cisco Unified CallManager. The Find and List Partitions page appears.
Step 2
Click Add a New Partition. The Partition Configuration page appears. Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description. Click Insert to add the new partition.
Step 3 Step 4
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Phone Calling Search Space, page 3-2 Assigning the Partition and Calling Search Space to Phones, page 3-3
Creating a Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one. To create a defined calling search space, follow these steps:
Procedure
Step 1
Select Route Plan > Calling Search Space in Cisco Unified CallManager. The Find and List Calling Search Spaces page appears. Click Add a New Calling Search Space. The Calling Search Space Configuration page appears. Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.
Step 2
Step 3
3-2
OL-12376-01
Chapter 3
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Setting Up Phone Route Plans
Step 4 Step 5
Select the Phones partition in the Available Partitions list box, and click the arrow buttons between the two list boxes to add it to the Selected Partitions list box. Click Insert to add the new calling search space.
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Phone Partition, page 3-2 Assigning the Partition and Calling Search Space to Phones, page 3-3
Assigning the Partition and Calling Search Space to Phones

After you have created the Phones partition (Creating a Phone Partition, page 3-2) and PhonesCSS calling search space (Creating a Phone Calling Search Space, page 3-2), configure the phones to use them.
Before You Begin
You can use the Bulk Administration Tool (BAT) to change the partition and calling search space on telephones in much less time than it takes to make the changes to each phone individually. This procedure describes the phone-by-phone procedure. To use BAT to change the partition and calling search space, follow these steps:
Procedure
Step 1
Select Device > Phone. Cisco Unified CallManager displays the Find and List Phones page.
Step 2
Select Device name is not empty in the search fields and click Find. Cisco Unified CallManager lists all of the phones in the bottom frame. Click the phone whose configuration you want to change. Cisco Unified CallManager displays the Phone Configuration page. Change the calling search space to PhoneCSS and click Update. Click the line number you want to configure in the left-hand column. Cisco Unified CallManager displays the Directory Number Configuration page. Change the partition to Phones, and the calling search space to PhoneCSS. Click Insert to save your changes.
Step 3
Step 4 Step 5
Step 6 Step 7
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Phone Partition, page 3-2 Creating a Phone Calling Search Space, page 3-2
3-3
Chapter 3 Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Setting Up Cisco Emergency Responder to Handle Emergency Calls
Setting Up Cisco Emergency Responder to Handle Emergency Calls

To handle emergency calls, you must configure the emergency call numbers (such as 911) so that Cisco Emergency Responder (Cisco ER) intercepts them. Cisco ER can then route the calls to the correct public safety answering point (PSAP) and transform the call as required to route the call and to enable the PSAP operator to call back the emergency caller if the initial call is disconnected. These topics describe how to define the Cisco Unified CallManager elements required for Cisco ER:

Creating a Cisco Emergency Responder Partition, page 3-4 Creating a Cisco Emergency Responder Calling Search Space, page 3-5 Creating the Emergency Call Route Points, page 3-6 Creating the Required CTI Ports, page 3-8 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 3-9 Creating Alternate Emergency Call Numbers, page 3-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 3-16 Creating Route Patterns for Inter-Cisco Emergency Responder Group Communications, page 3-17
Creating a Cisco Emergency Responder Partition

You must create the Cisco Emergency Responder (Cisco ER) partition E911. This partition contains the numbers used by the PSAP to call into the network, and certain other CTI route points.
Caution
When configuring Cisco Unified CallManager 4.2 and 4.3 with Cisco ER, you must not set the Time of Day feature in the E911 partition used for emergency calls. To create the Cisco ER partition E911, follow these steps:
Procedure
Step 1
Select Route Plan > Partition in Cisco Unified CallManager. The Find and List Partitions page appears. Click Add a New Partition. The Partition Configuration page appears.
Step 2
Step 3 Step 4
Enter a descriptive name, such as E911, in the Partition Name field. Click Insert to add the new partition.
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Cisco Emergency Responder Calling Search Space, page 3-5 Setting Up Phone Route Plans, page 3-1
3-4
OL-12376-01
Chapter 3
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Setting Up Cisco Emergency Responder to Handle Emergency Calls
Creating the Emergency Call Route Points, page 3-6 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 3-9 Creating Route Patterns for Inter-Cisco Emergency Responder Group Communications, page 3-17
Creating a Cisco Emergency Responder Calling Search Space

To create the Cisco Emergency Responder (Cisco ER) calling search space, follow these steps:
Procedure
Step 1
Select Route Plan > Calling Search Space from Cisco Unified CallManager. The Find and List Calling Search Spaces page appears. Click Add a New Calling Search Space. The Calling Search Space Configuration page appears.
Step 2
Step 3 Step 4
Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field. In the Available Partitions list box, select the E911 partition and then select the Phones partition in that order; click the arrow buttons between the two list boxes to add them to the Selected Partitions list box. Arrange the partitions so that E911 is at the top of the list. If you are using any other partitions, add them to this list after the E911 partition.
Note
You must list the E911 partition before the Phones partition for the following reason: When the user configures the translation pattern 911 or 9.911 (see the Creating the Translation Patterns for 9.911 section on page 3-12), the 911 Route Point will be in the E911 partition; phones cannot look into the E911 Partition. The 911 Translation Pattern is in the phones partition and gets the E911CSS. When the E911 partition is listed first, it matches the 911 Route Point and the call goes to the Cisco ER server as intended. If you make the error of listing the Phones partition first, the Translation Pattern keeps searching, resulting in a fast busy signal.
Step 5
Click Insert to add the new calling search space.
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Cisco Emergency Responder Partition, page 3-4 Setting Up Phone Route Plans, page 3-1 Creating the Emergency Call Route Points, page 3-6 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 3-9 Creating Alternate Emergency Call Numbers, page 3-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 3-16
3-5
Creating the Emergency Call Route Points

You must configure CTI route points in Cisco Unified CallManager for:
The emergency call number for your locale, such as 911.
Note
If you use 9 as the access code, see the Creating the Translation Patterns for 9.911 section on page 3-12 to configure Cisco ER.
The number that your standby Cisco Emergency Responder (Cisco ER) server should listen to, such as 912. The number that incoming calls from the public safety answering point (PSAP) will use. Cisco ER modifies these calls based on your ELIN configuration to route the call to the person who initiated the emergency call, if the PSAP gets disconnected and needs to call the calling party. See the Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks section on page 3-9 for information about the rest of the ELIN configuration.
Before You Begin
This procedure assumes you are using 911 as the main emergency call number. If a different number is used in your locale, substitute it for 911, and make similar substitutions for other numbers based on 911, such as 912. For example, if the emergency call number in your locale is 112, use 112, and perhaps 113, 114. When you install Cisco ER, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation. Table 3-1 describes the emergency call route points.
Table 3-1 Emergency Call Route Points
Route Points Route Point Setting Device Name Description Primary Number (911) RP911 The emergency call number for the area. Cisco ER handles all calls to this number. Backup Number (912) RP912 Route point for the Cisco ER standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point. ELIN (913) RPELIN913 The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan. The number can only consist of numbers and Xs. Directory Number Partition 911 Phones 912 E911 E911CSS 913XXXXXXXXXX E911 E911CSS
Calling Search Space E911CSS
3-6
OL-12376-01
Chapter 3
Table 3-1
Emergency Call Route Points (continued)
Route Points Route Point Setting Forward Busy Primary Number (911) Destination: 912 CSS: E911CSS Backup Number (912) Destination: One of:

1
ELIN (913) Destination: Onsite security number.2 CSS: E911CSS
Route pattern for default ERL. Onsite security number.
CSS: E911CSS Forward No Answer Destination: 912 CSS: E911CSS Destination: One of:

Destination: Onsite security number. CSS: E911CSS
CSS: E911CSS Forward On Failure Destination: 912 CSS: E911CSS Destination: One of:

CSS: E911CSS
1. Configuring call-forwarding numbers for the standby server ensures that calls are either routed to the PSAP servicing the default ERL, or onsite security, if the standby server cannot handle the call. If you do not install a standby server, use these settings for the primary server. 2. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Cisco ER cannot handle the call.
To create the emergency call route points described in Table 3-1, follow these steps:
Procedure
Step 1
In Cisco Unified CallManager, select Device > CTI Route Point. The Find and List CTI Route Points page appears.
Step 2
Click Add a new CTI Route Point. The CTI Route Point Configuration page appears. Fill in the CTI route point properties:

Step 3
Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. Table 3-1 shows suggested names, but you can use any name you choose. Select the appropriate device pool from the Device Pool menu. Select the calling search space for the route point, as listed in Table 3-1.
Step 4
Click Insert to add the new CTI route point. Cisco Unified CallManager adds the route point and asks if you want to configure line 1. Click OK to configure line 1.
3-7
Cisco Unified CallManager opens the Directory Number configuration page.

Step 5 Step 6
Enter the configuration for the line you are creating using the information in Table 3-1. Click Insert. Cisco Unified CallManager adds the line to the device. Repeat this procedure until all devices described in Table 3-1 are configured. For additional assistance, refer to the documentation and online help included with Cisco Unified CallManager.
Related Topics

Creating a Cisco Emergency Responder Partition, page 3-4 Creating a Cisco Emergency Responder Calling Search Space, page 3-5 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 3-9 Creating Route Patterns for Inter-Cisco Emergency Responder Group Communications, page 3-17 Creating Alternate Emergency Call Numbers, page 3-15 Creating a Cisco Emergency Responder Cisco Unified CallManager User, page 3-19 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3
Creating the Required CTI Ports

Cisco Emergency Responder (Cisco ER) uses CTI ports to call onsite alert (security) personnel when someone makes an emergency call. You should have enough CTI ports so that each person assigned to an ERL can receive a call. The number of ports you configure is the number of simultaneous calls Cisco ER can make to these personnel. It does not relate to the number of emergency calls Cisco ER can handle or forward to the PSAPthere is no configurable limitation to the number of simultaneous emergency calls that Cisco ER can handle.
Before You Begin
Cisco ER requires that the CTI port extension numbers be in succession, so you must find a block of unused extensions. For example, if you want to create four CTI ports starting at 3001, then 3001, 3002, 3003, and 3004 must all be available. To create the required CTI ports, follow these steps:
Procedure
Step 1
Select Device > Phone. Cisco Unified CallManager opens the Find and List Phones page. Click Add a New Phone. Cisco Unified CallManager opens the Add a New Phone page. Select CTI Port for Phone Type and click Next. Cisco Unified CallManager opens the Phone Configuration page.
Step 2
Step 3
3-8
OL-12376-01
Chapter 3
Step 4
Configure the CTI Port, entering this information:

Device NameEnter something meaningful to you, for example, CTI3001. Device PoolSelect an appropriate device pool. This device pool must use the G.711 region. Calling Search SpaceSelect PhoneCSS.
Step 5
Click Insert. Cisco Unified CallManager creates the CTI port and asks if you want to configure line 1. Click OK. Cisco Unified CallManager opens the Directory Number Configuration page.
Step 6
Configure line 1 for the CTI port, entering this information:

PartitionSelect Phones. Calling Search SpaceSelect PhoneCSS.
Note
Configure only one line for each CTI port. Onsite security alert prompts may not get from one or more of these lines when the online alert notification is initiated through these ports.
Step 7
Click Insert. Cisco Unified CallManager adds the line to the device. Repeat the procedure to create each CTI route port that you require.
Note
All subsequent CTI ports you create must be consecutive from the first CTI port DN.
Related Topics

Creating a Cisco Emergency Responder Partition, page 3-4 Creating a Cisco Emergency Responder Calling Search Space, page 3-5 Creating a Cisco Emergency Responder Cisco Unified CallManager User, page 3-19 Identifying the Cisco Unified Communications Manager Clusters, page 5-21 Creating ERLs, page 5-28
Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks
Emergency calls are routed based on the calling party number, not the called party number. If an emergency call is disconnected for some reason (for example, the caller hangs up), the PSAP needs to be able to call back the emergency caller using the calling party number. The PSAP might also want to call back to obtain updated information after ending an emergency call normally. Cisco Emergency Responder (Cisco ER) converts a callers extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Cisco ER reuses the same set of numbers, and keeps track of the internal extension of the phone from which the call was made for up to three hours.
3-9
To set up the ELIN numbers, you must first obtain direct inward dial (DID) numbers from your service provider. Because you must pay for each number, you might want to limit the number of DIDs you obtain to two or three per ERL. The DIDs must be unique for each ERL. Cisco ER will reuse the ELIN numbers assigned to an ERL if necessary. For example, if you configure two numbers for an ERL, and three emergency calls are made within a three hour window, the first emergency callers ELIN mapping is replaced by the third callers extension. Thus, if the PSAP tries to call the first caller, the PSAP will reach the third caller. Keep this in mind as you determine the number of DIDs you will obtain for each ERL. These topics describe how to set up the route patterns and translation patterns required to set up the ELIN numbers:

Creating the Route Patterns for ELINs, page 3-10 Creating the Translation Patterns for ELINs, page 3-11
See the Creating ERLs section on page 5-28 for information on how to configure the ERLs with these numbers.
Creating the Route Patterns for ELINs

Cisco Emergency Responder (Cisco ER) uses route patterns to route emergency calls to the local public safety answering point (PSAP). In the route pattern, you are associating a pattern with a gateway that will connect to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you will assign the route pattern. You must create one route pattern for every ELIN in your network. These are the direct inward dial (DID) numbers you obtain from your service provider for the purpose of allowing the PSAP to call into your network.
Before You Begin
Each ERL requires unique route patterns for the ELINs. Work with the ERL administrator to get an idea of how many route patterns are needed, and the locale of the ERLs so that you can select an appropriate gateway. The ERL administrator must enter the route patterns you create into the ERL definition. See the Creating ERLs section on page 5-28 for information about ERLs. To create the route patterns for ELINs, follow these steps:
Procedure
Step 1
Select Route Plan > Route Pattern. Cisco Unified CallManager opens the Find and List Route Patterns page. Click Add a New Route Pattern. Cisco Unified CallManager opens the Route Pattern Configuration page. Enter the information for the route pattern:
Step 2
Step 3
Route PatternA pattern that you can transform to the emergency call number, typically a number, a dot, and the emergency call number. For example, 10.911, 11.911, and so forth. The pattern can only contain numbers and dots. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Gateway/Route ListSelect the gateway to use for connecting to the local PSAP.
3-10
OL-12376-01
Chapter 3
Route OptionSelect Route this pattern. Use Calling Partys External Phone Number MaskSelect this. Discard DigitsSelect PreDot if you use the suggested pattern, such as 10.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).
Step 4
Click Insert. Cisco Unified CallManager saves the route pattern. To add additional route patterns, return to Step 2.
Tip
Consider developing a detailed naming strategy for the route patterns, because you might end up with a large number of them. For example, you could use a pattern such as xyzzaaab.911, where x is a Cisco ER cluster identifier; y is a Cisco ER group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and, b is the ELIN identifier (within the ERL).
Related Topics

Creating the Translation Patterns for ELINs, page 3-11 Creating a Cisco Emergency Responder Partition, page 3-4 Understanding the Cisco Unified CallManager Examples, page 3-1 Understanding ERLs, page 5-25 Creating ERLs, page 5-28
Creating the Translation Patterns for ELINs

Create translation patterns that cover the direct inward dial (DID) numbers you are using for ELIN numbers. The PSAP uses these ELINs to call into your network. Cisco Emergency Responder (Cisco ER) needs to intercept these calls so it can route the call to the correct emergency caller. The translation pattern is required so that a number prefixed to the ELIN becomes the route point you configured for PSAP callbacks, as explained in the Creating the Emergency Call Route Points section on page 3-6.
Before You Begin
Ensure you have a list of all the DIDs you are using for ELINs. To create the translation patterns for ELINs, follow these steps:
Procedure
Step 1
Select Route Plan > Translation Pattern. Cisco Unified CallManager opens the Find and List Translation Patterns page.
Step 2
Click Add a New Translation Pattern. Cisco Unified CallManager opens the Translation Pattern Configuration page.
3-11
Step 3
Create the translation pattern:
Translation PatternThe DID you are using as an ELIN. If you can, use X variables to create a pattern that covers more than one DID (for example, 5555551XXX). If you cannot create a pattern, define translation patterns for each DID separately. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Called Party Transformations, Prefix Digits (Outgoing Calls)Enter the digits to prefix to the number. Enter the digits you used when creating the PSAP callback route point.
Step 4
Click Insert. Cisco Unified CallManager saves the translation pattern. To add additional translation patterns, return to Step 2.
Related Topics

Creating the Route Patterns for ELINs, page 3-10 Understanding the Cisco Unified CallManager Examples, page 3-1 Understanding ERLs, page 5-25 Creating ERLs, page 5-28
Creating the Translation Patterns for 9.911

In systems where the external access code is 9, a CTI Route Point of 911 or 9.911 may interfere with the timing of secondary dialtone for users when they are attempting to dial external destinations. The creation of a translation pattern for 911 and 9.911 will eliminate the secondary dialtone timing. Create translation patterns so that when users dial the local system external access code of 9 plus 911, the calls will be directed to the single 911 pattern previously created in theCreating the Emergency Call Route Points section on page 3-6.
Before You Begin
This procedure applies to systems where the external access code is 9. If the external access code is something other than 9, this procedure may not apply. To complete this procedure, you must have already added the partitions and the calling search space for the Cisco Emergency Responder installation. Table 3-2 provides translation patterns for external access code of 9.
Table 3-2 Translation Patterns for External Access Code of 9
Translation Pattern Partition Calling Search Space Route Option
911 Phones E911CSS Route this pattern
9.911 Phones E911CSS Route this pattern
3-12
OL-12376-01
Chapter 3
Table 3-2
Translation Patterns for External Access Code of 9
Translation Pattern Provide outside dial tone Called Party Transformations, Discard Digits (Outgoing Calls)
911 Check this box None
9.911 Check this box PreDot
To create the translation patterns described in Table 3-2, follow these steps:
Procedure
Step 1
Select Route Plan > Translation Pattern. Cisco Unified CallManager opens the Find and List Translation Patterns page.
Step 2
Click Add a New Translation Pattern. Cisco Unified CallManager opens the Translation Pattern Configuration page. Create the translation pattern:

Step 3
Translation Pattern911 PartitionPhones Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Provide Outside Dial ToneMake sure this box is checked. Called Party Transformations, Discard DigitsSelect <none>.
Step 4
Click Insert. Cisco Unified CallManager saves the translation pattern. Repeat Step 2 to Step 4 with the following changes:

Step 5
Translation Pattern9.911 Called Party Transformations, Discard Digits (Outgoing Calls)PreDot
After you have configured the 9.911 translation patterns, you must create the route points. Table 3-3 provides emergency call route points for 9.911.
Note
These route points are similar to the route points that you created in the Creating the Emergency Call Route Points section on page 3-6. In this case, you enter E911 for the partition instead of RP911.
3-13
Table 3-3
Emergency Call Route Points for 9.911
Route Points Route Point Setting Device Name Description Primary Number (911) RP911 The emergency call number for the area. Cisco ER handles all calls to this number. Backup Number (912) RP912 Route point for the Cisco ER standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point. ELIN (913) RPELIN913 The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan. The number can only consist of numbers and Xs. Directory Number Partition Forward Busy 911 E911 Destination: 912 CSS: E911CSS 912 E911 E911CSS Destination: One of:

1
913XXXXXXXXXX E911 E911CSS Destination: Onsite security number.2 CSS: E911CSS


CSS: E911CSS
3-14
OL-12376-01
Chapter 3
To create the route points for 9.911, follow these steps:

Procedure
Step 1
In Cisco Unified CallManager, select Device > CTI Route Point. The Find and List CTI Route Points page appears. Click Add a new CTI Route Point. The CTI Route Point Configuration page appears. Fill in the CTI route point properties:

Step 2
Step 3
Step 4
Click Insert to add the new CTI route point. Cisco Unified CallManager adds the route point and asks if you want to configure line 1. Click OK to configure line 1. Cisco Unified CallManager opens the Directory Number configuration page. Enter the configuration for the line you are creating using the information in Table 3-3. Click Insert. Cisco Unified CallManager adds the line to the device. Repeat this procedure until all devices described in Table 3-3 are configured. For additional assistance, refer to the documentation and online help included with Cisco Unified CallManager.
Step 5 Step 6
Related Topics

Creating the Route Patterns for ELINs, page 3-10 Understanding the Cisco Unified CallManager Examples, page 3-1 Understanding ERLs, page 5-25
Creating Alternate Emergency Call Numbers

If your users are used to dialing 9 (or another number) to get an outside line, they might try to dial the emergency number by first dialing the outside line access number. For example, if the emergency number is 911, they might try to dial 9911. If you want to accommodate these possibilities, configure translation patterns for the numbers you think are likely to be used. This procedure shows how to set up 9911 as an alternate emergency call number.
3-15
To create alternate emergency call numbers, follow these steps:

Procedure
Step 1
Select Route Plan > Translation Pattern. Cisco Unified CallManager opens the Find and List Translation Patterns page. Click Add a New Translation Pattern. Cisco Unified CallManager opens the Translation Pattern Configuration page. Create the translation pattern:

Step 2
Step 3
Translation PatternThe number you want to support as an emergency number. In this example, 9.911 PartitionSelect Phones. Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Provide Outside Dial ToneSelect this. Called Party Transformations, Discard Digits (Outgoing Calls)Select PreDot.
Step 4
Click Insert. Cisco Unified CallManager saves the translation pattern. To add additional translation patterns, return to Step 2.
Related Topics

Understanding the Cisco Unified CallManager Examples, page 3-1 Creating a Phone Partition, page 3-2 Creating a Phone Calling Search Space, page 3-2
Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP
You must set up a gateway to use a CAMA or PRI connection to the emergency network or PSTN so that emergency calls can be routed to the local PSAP. See the documentation for your gateway for information on setting up the gateway, and the Cisco Unified CallManager documentation for configuring the gateway. After you set up the gateway, you can follow this procedure to set up the calling search space for the gateway. To configure the calling search space for gateways used to connect to the PSAP, follow these steps:
Procedure
Step 1
Select Device > Gateway. Cisco Unified CallManager opens the Find and List Gateways page.
3-16
OL-12376-01
Chapter 3
Step 2
Click Find without entering search criteria to list all of the gateways, or enter the search criteria required to list the gateway you want to configure and click Find. Cisco Unified CallManager lists the gateways that match your criteria.
Step 3
Click the gateway you want to configure. Cisco Unified CallManager opens the Gateway Configuration page. Select E911CSS for Calling Search Space. Click Update. Cisco Unified CallManager saves your changes.
Step 4 Step 5
Related Topics

Creating a Cisco Emergency Responder Calling Search Space, page 3-5 Obtain CAMA or PRI Trunks to the PSTN, page 1-17 Deploying Cisco Emergency Responder, page 1-21 How Cisco Emergency Responder Fits Into Your Network, page 1-7
Creating Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Cisco Emergency Responder (Cisco ER) group in a Cisco ER cluster, you must configure route patterns to enable each Cisco ER group to route emergency calls to another Cisco ER group if a callers phone homes to a Cisco Unified CallManager cluster outside the current location of the phone. See the Understanding Cisco Emergency Responder Clusters and Groups section on page 1-12 for a detailed explanation of how Cisco ER groups communicate within a Cisco ER cluster. This procedure explains how to create the route pattern for one Cisco ER group. You must create this pattern in the Cisco Unified CallManager clusters that are not supported by the Cisco ER group. Consider the network setup in Figure 3-1. For inter-group communications to work:
You must define inter-cluster trunks in each Cisco Unified CallManager cluster to enable communications between the Cisco Unified CallManager clusters. See the Cisco Unified CallManager documentation for information on creating these types of gateways. You must define the route pattern 1000.911 in Cisco Unified CallManager clusters CCM-C and CCM-D. You must define the route pattern 2000.911 in Cisco Unified CallManager clusters CCM-A and CCM-B. In Cisco ER group 1, define 1000.911 as the Inter Cisco ER Group Route Pattern. In Cisco ER group 2, define 2000.911 as the Inter Cisco ER Group Route Pattern.
These definitions allow a call in an ERL managed by Cisco ER group 2 to be routed to Cisco ER group 2 even though the phone homes to Cisco Unified CallManager cluster CCM-B, which is serviced by Cisco ER group 1.
3-17
Figure 3-1
Chicago
Understanding Inter Cisco Emergency Responder Group Route Patterns

New York Cisco Unified CM-B
M
Cisco Unified CM-A

M
Cisco Unified CM-C

M
Cisco Unified CM-D

M
IP
182294
Cisco ER group 1 1000.911
ext.3003
Before You Begin
The dial plans must be unique between all Cisco Unified CallManager clusters supported by a Cisco ER cluster. For example, in the network shown in Figure 3-1, the extension 3003 can only be defined in Cisco Unified CallManager cluster CCM-B. To create route patterns for inter-Cisco Emergency Responder group communications, follow these steps:
Procedure
Step 1
Select Route Plan > Route Pattern. Cisco Unified CallManager opens the Find and List Route Patterns page.
Step 2
Click Add a New Route Pattern. Cisco Unified CallManager opens the Route Pattern Configuration page. Enter the information for the route pattern:
Step 3
Route PatternA pattern that you can transform to the emergency call number, typically a number, a dot, and the emergency call number. For example, 1000.911 or 2000.911. The pattern can only consist of numbers and dots. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Gateway/Route ListSelect the inter-cluster trunk gateway to use for connecting to the Cisco Unified CallManager cluster supported by the Cisco ER group whose inter Cisco ER group route pattern you are defining. Route OptionSelect Route this pattern. Called Party Transformations, Discard DigitsSelect PreDot if you use the suggested pattern, such as 1000.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).
3-18
OL-12376-01
Chapter 3
Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Creating a Cisco Emergency Responder Cisco Unified CallManager User
Step 4
Click Insert. Cisco Unified CallManager saves the route pattern. To add additional route patterns, return to Step 2.
Step 5
Ensure you define the route pattern in all other Cisco Unified CallManager clusters serviced by Cisco ER groups other than the Cisco ER group whose inter Cisco ER group route pattern you are defining.
Related Topics

Creating a Cisco Emergency Responder Partition, page 3-4 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3
Creating a Cisco Emergency Responder Cisco Unified CallManager User

You need to add Cisco ER as a Cisco Unified CallManager user. The settings you enter here are used when you configure the Cisco Unified CallManager settings for Cisco ER. To add Cisco ER as a Cisco Unified CallManager user, follow these steps:
Procedure
Step 1
In Cisco Unified CallManager, select User > Add a New User. Cisco Unified CallManager opens the User Information page.
Step 2
Complete the following required fields:

First NameUse a descriptive name such as Emergency Last NameUse a descriptive name such as Responder UserIDUse a descriptive name such as CER User Password and Confirm PasswordEnter a password and enter it again for confirmation PIN and Confirm PINEnter a PIN and enter it again for confirmation Enable CTI Application UseSelect this check-box. Enable Calling Party Modification - Select this if you plan to use Calling Party Modification for Cisco ER.
Step 3
Click Insert to create the user. Cisco Unified CallManager adds the user. Click Device Association in the left-hand column. Cisco Unified CallManager opens the Assign Devices subpage of the User Information page.
Step 4
Step 5
Enter search criteria to list the desired route points and CTI ports, or enter nothing to list all devices, and click Select Devices to list the devices.
3-19
Chapter 3 Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0 Creating a Cisco Emergency Responder Cisco Unified CallManager User
Step 6
In the list that Cisco Unified CallManager produces, select these devices:

All CTI ports created for Cisco Emergency Responders use. See the Creating the Required CTI Ports section on page 3-8 for more information. The primary emergency call number, for example, 911. Also, select this number as the users primary extension. The backup emergency call number, for example, 912. The route point used for ELINs, for example, 913XXXXXXXXXX.
Step 7
Click Update to save your changes.
Related Topics

Creating the Emergency Call Route Points, page 3-6 Creating the Required CTI Ports, page 3-8
3-20
OL-12376-01
C H A P T E R
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0
This chapter describes procedures for configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder (Cisco ER) 2.0. If you are running Cisco Unified CallManager 4.2 or 4.3, follow the procedures in Chapter 3, Configuring Cisco Unified CallManager 4.2 and 4.3 for Cisco Emergency Responder 2.0. These topics describe the items you must configure in Cisco Unified Communications Manager 5.0, 5.1, and 6.0 so that Cisco ER can work in your telephone network. These topics describe a sample Cisco Unified Communications Manager setupthe names chosen (for example, partition and calling search space names) are not required.

Setting Up Phone Route Plans, page 4-2 Setting Up Cisco Emergency Responder to Handle Emergency Calls, page 4-4 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Configuring JTAPI Security, page 4-20
Understanding the Cisco Unified Communications Manager Examples
These sections represent an example setup, with sample values included for reference only. Your particular configuration depends on the needs of your network and your naming strategy. For these examples, you will be working with the following calling search spaces and partitions:

PhoneCSSincludes the Phones partition. E911CSSincludes the E911 and Phones partitions.
The examples are based on a single Cisco Unified Communications Manager cluster. If you have more than one cluster, you must repeat the configuration in each cluster, except for the emergency location identification number (ELIN) translation patterns. The ELIN translation patterns are only defined in the Cisco Unified Communications Manager cluster to which the gateway will send incoming calls from the public safety answering point (PSAP).
4-1
Chapter 4 Setting Up Phone Route Plans
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for
Setting Up Phone Route Plans

Before configuring Cisco ER, you must ensure that the phones that might be used to make emergency calls (typically all phones) are added and registered with Cisco Unified Communications Manager. Refer to the documentation and online help included with Cisco Unified Communications Manager if you need assistance completing this. These sections provide an example setup for your network before adding Cisco ER:

Creating a Phone Partition, page 4-2 Creating a Phone Calling Search Space, page 4-2 Assigning the Partition and Calling Search Space to Phones, page 4-3
Creating a Phone Partition

If you have not already created a partition for the phones, do so now. To create a phone partition, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select Call Routing > Class of Control > Partition. The Find and List Partitions page appears.
Step 2
Click Add New. The Partition Configuration page appears. In the Name field, enter a descriptive name, such as Phones. You can include a description (optional). Click Save to add the new partition.
Step 3 Step 4
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Phone Calling Search Space, page 4-2 Assigning the Partition and Calling Search Space to Phones, page 4-3
Creating a Phone Calling Search Space

If you do not already have a calling search space defined for the phones, define one now. To define a calling search space for the phones, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select Call Routing > Class of Control > Calling Search Space. The Find and List Calling Search Spaces page appears.
Step 2
Click Add New.
4-2
OL-12376-01
Chapter 4
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 Setting Up Phone Route Plans
The Calling Search Space Configuration page appears.

In the Calling Search Space Name field, enter a descriptive name, such as PhoneCSS. In the Route Partitions for this Calling Search Space list box, select the Phones partition and click the arrow buttons between the two list boxes to add it to the Selected Partitions list box. Click Save to add the new calling search space.
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Phone Partition, page 4-2 Assigning the Partition and Calling Search Space to Phones, page 4-3
Assigning the Partition and Calling Search Space to Phones

After you have created the Phones partition (Creating a Phone Partition, page 4-2) and PhonesCSS calling search space (Creating a Phone Calling Search Space, page 4-2), configure the phones to use them.
Before You Begin
You can use the Bulk Administration Tool (BAT) to change the partition and calling search space on telephones in much less time than it takes to make the changes to each phone individually. This procedure describes the phone-by-phone procedure. To assign the partition and calling search space to phones, follow these steps:
Procedure
Step 1
Select Device > Phone. Cisco Unified Communications Manager displays the Find and List Phones page. In the search fields, select Device Name and click Find. Cisco Unified Communications Manager lists all of the phones in the bottom frame. Click the phone whose configuration you want to change. Cisco Unified Communications Manager displays the Phone Configuration page.
Step 2
Step 3
Step 4 Step 5
Change the calling search space to PhoneCSS and click Update. Click the line number you want to configure in the left-hand column. Cisco Unified Communications Manager displays the Directory Number Configuration page.
Step 6 Step 7
Change the partition to Phones, and the calling search space to PhoneCSS. Click Save to save your changes.
4-3
Chapter 4 Setting Up Cisco Emergency Responder to Handle Emergency Calls
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Phone Partition, page 4-2 Creating a Phone Calling Search Space, page 4-2
Setting Up Cisco Emergency Responder to Handle Emergency Calls

To handle emergency calls, you must configure the emergency call numbers (such as 911) so that Cisco Emergency Responder (Cisco ER) intercepts them. Cisco ER can then route the calls to the correct public safety answering point (PSAP) and transform the call as required to route the call and to enable the PSAP operator to call back the emergency caller if the initial call is disconnected. These topics describe how to define the Cisco Unified Communications Manager elements required for Cisco ER:

Creating a Cisco Emergency Responder Partition E911, page 4-4 Creating a Cisco Emergency Responder Calling Search Space, page 4-5 Creating the Emergency Call Route Points, page 4-6 Creating the Required CTI Ports, page 4-8 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Creating Alternate Emergency Call Numbers, page 4-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 4-16 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17
Creating a Cisco Emergency Responder Partition E911

You must create the Cisco ER partition E911. This partition contains the numbers used by the PSAP to call into the network, and certain other CTI route points. To create the Cisco ER partition E911, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select Call Routing > Class of Control > Partition. The Find and List Partitions page appears. Click Add New. The Partition Configuration page appears.
Step 2
Step 3 Step 4
Enter a descriptive name, such as E911, in the Partition Name field. Click Save to add the new partition.
4-4
OL-12376-01
Chapter 4
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 Setting Up Cisco Emergency Responder to Handle Emergency Calls
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Cisco Emergency Responder Calling Search Space, page 4-5 Setting Up Phone Route Plans, page 4-2 Creating the Emergency Call Route Points, page 4-6 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17
Creating a Cisco Emergency Responder Calling Search Space

You must create a Cisco ER calling search space. To create a Cisco ER calling search space, follow these steps:
Procedure
Step 1
Select Call Routing > Calling Search Space from Cisco Unified Communications Manager. The Find and List Calling Search Spaces page appears. Click Add New. The Calling Search Space Configuration page appears. In the Calling Search Space Information Name field, enter a descriptive name, such as E911CSS. In the Available Partitions list box, select the E911 partition and then select the Phones partition in that order; click the arrow buttons between the two list boxes to add them to the Selected Partitions list box. Arrange the partitions so that E911 is at the top of the list. If you are using any other partitions, add them to this list after the E911 partition.
Step 2
Step 3 Step 4
Note
You must list the E911 partition before the Phones partition for the following reason: When the user configures the translation pattern 911 or 9.911 (see the Creating the Translation Patterns for 9.911 section on page 4-12), the 911 Route Point will be in the E911 partition; phones cannot look into the E911 Partition. The 911 Translation Pattern is in the phones partition and gets the E911CSS. When the E911 partition is listed first, it matches the 911 Route Point and the call goes to the Cisco ER server as intended. If you make the error of listing the Phones partition first, the Translation Pattern keeps searching, resulting in a fast busy signal.
Step 5
Click Save to add the new calling search space.
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Cisco Emergency Responder Partition E911, page 4-4 Setting Up Phone Route Plans, page 4-2 Creating the Emergency Call Route Points, page 4-6 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9
4-5
Creating Alternate Emergency Call Numbers, page 4-15 Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP, page 4-16
Creating the Emergency Call Route Points

You must configure CTI route points in Cisco Unified Communications Manager for:
The emergency call number for your locale, such as 911.
Note
If you use 9 as the access code, see the Creating the Translation Patterns for 9.911 section on page 4-12 to configure Cisco ER.
The number that your standby Cisco Emergency Responder (Cisco ER) server should listen to, such as 912. The number that incoming calls from the public safety answering point (PSAP) will use. Cisco ER modifies these calls based on your ELIN configuration to route the call to the person who initiated the emergency call, if the PSAP gets disconnected and needs to call the calling party. See the Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks section on page 4-9 for information about the rest of the ELIN configuration.
Before You Begin
This procedure assumes you are using 911 as the main emergency call number. If a different number is used in your locale, substitute it for 911, and make similar substitutions for other numbers based on 911, such as 912. For example, if the emergency call number in your locale is 112, use 112, and perhaps 113, 114. When you install Cisco ER, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation. Table 4-1 describes the emergency route point settings.
Table 4-1 Emergency Call Route Points
Route Points Route Point Setting Device Name Description Primary Number (911) RP911 The emergency call number for the area. Cisco ER handles all calls to this number. Backup Number (912) RP912 Route point for the Cisco ER standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point. ELIN (913) RPELIN913 The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan. The number can only consist of numbers and Xs. Directory Number Partition 911 Phones 912 E911 E911CSS 913XXXXXXXXXX E911 E911CSS
4-6
OL-12376-01
Chapter 4
Table 4-1
Emergency Call Route Points (continued)
Route Points Route Point Setting Forward Busy Primary Number (911) Destination: 912 CSS: E911CSS Backup Number (912) Destination: One of:

1
ELIN (913) Destination: Onsite security number.2
Route pattern for default CSS: E911CSS ERL. Onsite security number. Destination: Onsite security number.

Route pattern for default CSS: E911CSS ERL. Onsite security number. Destination: Onsite security number.

Route pattern for default CSS: E911CSS ERL. Onsite security number.
CSS: E911CSS
To create the route points described in Table 4-1, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select Device > CTI Route Point. The Find and List CTI Route Points page appears.
Step 2
Click Add New. The CTI Route Point Configuration page appears. Fill in the CTI route point properties:

Step 3
Step 4
Click Save to add the new CTI route point. Cisco Unified Communications Manager adds the route point and asks if you want to configure line 1. Click OK to configure line 1. Cisco Unified Communications Manager opens the Directory Number configuration page.
Step 5
Enter the configuration for the line you are creating using the information in Table 4-1.
4-7
Step 6
Click Save. Cisco Unified Communications Manager adds the line to the device. Repeat this procedure until all devices described in Table 4-1 are configured. For additional assistance, refer to the documentation and online help included with Cisco Unified Communications Manager.
Related Topics

Creating a Cisco Emergency Responder Partition E911, page 4-4 Creating a Cisco Emergency Responder Calling Search Space, page 4-5 Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17 Creating Alternate Emergency Call Numbers, page 4-15 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3
Creating the Required CTI Ports

Cisco ER uses CTI ports to call onsite alert (security) personnel when someone makes an emergency call. You should have enough CTI ports so that each person assigned to an ERL can receive a call. The number of ports you configure is the number of simultaneous calls Cisco ER can make to these personnel. It does not relate to the number of emergency calls Cisco ER can handle or forward to the PSAPthere is no configurable limitation to the number of simultaneous emergency calls that Cisco ER can handle.
Before You Begin
Cisco ER requires that the CTI port extension numbers be in succession, so you must find a block of unused extensions. For example, if you want to create four CTI ports starting at 3001, then 3001, 3002, 3003, and 3004 must all be available. To create the required CTI ports, follow these steps:
Procedure
Step 1
Select Device > Phone. Cisco Unified Communications Manager opens the Find and List Phones page.
Step 2
Click Add New. Cisco Unified Communications Manager opens the Add a New Phone page. Select CTI Port for Phone Type and click Next.
Step 3
4-8
OL-12376-01
Chapter 4
Step 4
Configure the CTI Port, entering this information:

Device NameEnter something meaningful to you, for example, CTI3001. Device PoolSelect an appropriate device pool. This device pool must use the G.711 region. Calling Search SpaceSelect PhoneCSS.
Step 5
Click Save. Cisco Unified Communications Manager creates the CTI port and asks if you want to configure line 1. Click OK. Cisco Unified Communications Manager opens the Directory Number Configuration page.
Step 6
Configure line 1 for the CTI port, entering this information:

Directory NumberEnter an unused extension number for the port, such as 3001. PartitionSelect Phones. Calling Search SpaceSelect PhoneCSS.
Note
Configure only one line for each CTI port. Onsite security alert prompts may not get from one or more of these lines when the online alert notification is initiated through these ports.
Step 7
Click Save. Cisco Unified Communications Manager adds the line to the device. Repeat the procedure to create each CTI route port that you require.
Note
All subsequent CTI ports you create must be consecutive from the first CTI port DN.
Related Topics

Creating a Cisco Emergency Responder Partition E911, page 4-4 Creating a Cisco Emergency Responder Calling Search Space, page 4-5 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Identifying the Cisco Unified Communications Manager Clusters, page 5-21 Creating ERLs, page 5-28
Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks
Emergency calls are routed based on the calling party number, not the called party number. If an emergency call is disconnected for some reason (for example, the caller hangs up), the PSAP needs to be able to call back the emergency caller using the calling party number. The PSAP might also want to call back to obtain updated information after ending an emergency call normally. Cisco Emergency Responder (Cisco ER) converts a callers extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Cisco ER reuses the same set of numbers, and keeps track of the internal extension of the phone from which the call was made for up to three hours.
4-9
To set up the ELIN numbers, you must first obtain direct inward dial (DID) numbers from your service provider. Because you must pay for each number, you might want to limit the number of DIDs you obtain to two or three per ERL. The DIDs must be unique for each ERL. Cisco ER will reuse the ELIN numbers assigned to an ERL if necessary. For example, if you configure two numbers for an ERL, and three emergency calls are made within a three hour window, the first emergency callers ELIN mapping is replaced by the third callers extension. Thus, if the PSAP tries to call the first caller, the PSAP will reach the third caller. Keep this in mind as you determine the number of DIDs you will obtain for each ERL. These topics describe how to set up the route patterns and translation patterns required to set up the ELIN numbers:

Creating the Route Patterns for ELINs, page 4-10 Creating the Translation Patterns for ELINs, page 4-11
See the Creating ERLs section on page 5-28 for information on how to configure the ERLs with these numbers.
Creating the Route Patterns for ELINs

Cisco ER uses route patterns to route emergency calls to the local public safety answering point (PSAP). In the route pattern, you are associating a pattern with a gateway that will connect to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you will assign the route pattern. You must create one route pattern for every ELIN in your network. These are the direct inward dial (DID) numbers you obtain from your service provider for the purpose of allowing the PSAP to call into your network.
Before You Begin
Each ERL requires unique route patterns for the ELINs. Work with the ERL administrator to get an idea of how many route patterns are needed, and the locale of the ERLs so that you can select an appropriate gateway. The ERL administrator must enter the route patterns you create into the ERL definition. See the Creating ERLs section on page 5-28 for information about ERLs. To create the route patterns for ELINs, follow these steps:
Procedure
Step 1
Select Call Routing > Route/Hunt > Route Pattern. Cisco Unified Communications Manager opens the Find and List Route Patterns page. Click Add New. Cisco Unified Communications Manager opens the Route Pattern Configuration page. Enter the information for the route pattern:
Step 2
Step 3
Route PatternA pattern that you can transform to the emergency call number, typically a number, a dot, and the emergency call number. For example, 10.911, 11.911, and so forth. The pattern can only contain numbers and dots. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Gateway/Route ListSelect the gateway to use for connecting to the local PSAP.
4-10
OL-12376-01
Chapter 4
Route OptionSelect Route this pattern. Use Calling Partys External Phone Number MaskSelect this. Calling Party Transform MaskEnter the direct inward dial (DID) number you obtained to allow the PSAP in this locale to dial into your network. This is the ELIN number the ERL administrator enters for this route pattern when creating the ERL. Discard DigitsSelect PreDot if you use the suggested pattern, such as 10.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).
Step 4
Click Save. Cisco Unified Communications Manager saves the route pattern. To add additional route patterns, return to Step 2.
Tip
Consider developing a detailed naming strategy for the route patterns, because you might end up with a large number of them. For example, you could use a pattern such as xyzzaaab.911, where x is a Cisco ER cluster identifier; y is a Cisco ER group identifier; zz is the PSAP identifier; aaa is the ERL identifier; b is the ELIN identifier (within the ERL).
Related Topics

Creating the Translation Patterns for ELINs, page 4-11 Creating a Cisco Emergency Responder Partition E911, page 4-4 Understanding the Cisco Unified Communications Manager Examples, page 4-1 Understanding ERLs, page 5-25 Creating ERLs, page 5-28
Creating the Translation Patterns for ELINs

Create translation patterns that cover the direct inward dial (DID) numbers you are using for ELIN numbers. The PSAP uses these ELINs to call into your network. Cisco Emergency Responder (Cisco ER) needs to intercept these calls so it can route the call to the correct emergency caller. The translation pattern is required so that the a number is prefixed to the ELIN so that it becomes the route point you configured for PSAP callbacks, as explained in the Creating the Emergency Call Route Points section on page 4-6.
Before You Begin
Ensure you have a list of all the DIDs you are using for ELINs. To create the transition patterns for ELINs, follow these steps:
Procedure
Step 1
Select Call Routing > Translation Pattern. Cisco Unified Communications Manager opens the Find and List Translation Patterns page. Click Add New.
Step 2
4-11
Cisco Unified Communications Manager opens the Translation Pattern Configuration page.
Step 3
Translation PatternThe DID you are using as an ELIN. If you can, use X variables to create a pattern that covers more than one DID (for example, 5555551XXX). If you cannot create a pattern, define translation patterns for each DID separately. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Use Calling Partys External Phone Number MaskSelect this. Called Party Transformations, Prefix Digits (Outgoing Calls)Enter the digits to prefix to the number. Enter the digits you used when creating the PSAP callback route point.
Step 4
Click Save. Cisco Unified Communications Manager saves the translation pattern. To add additional translation patterns, return to Step 2.
Related Topics

Creating the Route Patterns for ELINs, page 4-10 Understanding the Cisco Unified Communications Manager Examples, page 4-1 Understanding ERLs, page 5-25 Creating ERLs, page 5-28
Creating the Translation Patterns for 9.911

In systems where the external access code is 9, a CTI Route Point of 911 or 9.911 may interfere with the timing of secondary dialtone for users when they are attempting to dial external destinations. The creation of a translation pattern for 911 and 9.911 will eliminate the secondary dialtone timing. You must create translation patterns so that when users dial the local system external access code of 9 plus 911, the calls will be directed to the single 911 pattern previously created in the Creating the Emergency Call Route Points section on page 4-6.
Before You Begin
This procedure applies to systems where the external access code is 9. If the external access code is something other than 9, this procedure may not apply. To complete this procedure, you must have already added the partitions and the calling search space for the Cisco ER installation. Table 4-2 describes the translation patterns for systems where the external access code is 9.
Table 4-2 Translation Patterns for External Access Code of 9
Translation Pattern Partition Calling Search Space
911 Phones E911CSS
9.911 Phones E911CSS
4-12
OL-12376-01
Chapter 4
Table 4-2
Translation Patterns for External Access Code of 9
Translation Pattern Route Option Provide outside dial tone Called Party Transformations, Discard Digits (Outgoing Calls)
911 Route this pattern Check this box None
9.911 Route this pattern Check this box PreDot
To create the translation patterns described in Table 4-2, follow these steps:
Procedure
Step 1
Select Call Routing > Translation Pattern. Cisco Unified Communications Manager opens the Find and List Translation Patterns page. Click Add New. Cisco Unified Communications Manager opens the Translation Pattern Configuration page.
Step 2
Step 3

Translation Pattern911 PartitionPhones Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Provide Outside Dial ToneMake sure this box is checked. Called Party Transformations, Discard DigitsSelect <none>.
Step 4
Click Save. Cisco Unified Communications Manager saves the translation pattern. Repeat Step 2 to Step 4 with the following changes:

Step 5
Translation Pattern9.911 Called Party Transformations, Discard Digits (Outgoing Calls)PreDot
After you have configured the 9.911 translation patterns, you must create the route points. Table 4-3 describes the route points for systems where the external access code is 9.
Note
These route points are similar to the route points that you created in the Creating the Emergency Call Route Points section on page 4-6. In this case, you enter E911 for the partition instead of RP911.
4-13
Table 4-3
Emergency Call Route Points for 9.911
Route Points Route Point Setting Device Name Description Primary Number (911) RP911 The emergency call number for the area. Cisco ER handles all calls to this number. Backup Number (912) RP912 Route point for the Cisco ER standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point. ELIN (913) RPELIN913 The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan. The number can only consist of numbers and Xs. Directory Number Partition Forward Busy 911 E911 Destination: 912 CSS: E911CSS 912 E911 E911CSS Destination: One of:

1
913XXXXXXXXXX E911 E911CSS Destination: Onsite security number.2 CSS: E911CSS


CSS: E911CSS
To create the route points described in Table 4-3, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select Device > CTI Route Point. The Find and List CTI Route Points page appears.
4-14
OL-12376-01
Chapter 4
Step 2
Click Add New. The CTI Route Point Configuration page appears.
Step 3
Fill in the CTI route point properties:

Step 4
Click Insert to add the new CTI route point. Cisco Unified Communications Manager adds the route point and asks if you want to configure line 1. Click OK to configure line 1. Cisco Unified Communications Manager opens the Directory Number configuration page.
Step 5 Step 6
Enter the configuration for the line you are creating using the information in Table 4-3. Click Save. Cisco Unified Communications Manager adds the line to the device. Repeat this procedure until all devices described in Table 4-3 are configured. For additional assistance, refer to the documentation and online help included with Cisco Unified Communications Manager.
Related Topics

Creating the Route Patterns for ELINs, page 4-10 Understanding the Cisco Unified Communications Manager Examples, page 4-1 Understanding ERLs, page 5-25
Creating Alternate Emergency Call Numbers

If your users are used to dialing 9 (or another number) to get an outside line, they might try to dial the emergency number by first dialing the outside line access number. For example, if the emergency number is 911, they might try to dial 9911. If you want to accommodate these possibilities, configure translation patterns for the numbers you think are likely to be used. To set up 9911 as an alternate emergency call number, follow these steps:
Procedure
Step 1
Select Call Routing > Translation Pattern. Cisco Unified Communications Manager opens the Find and List Translation Patterns page. Click Add New. Cisco Unified Communications Manager opens the Translation Pattern Configuration page.
Step 2
4-15
Step 3

Translation PatternThe number you want to support as an emergency number. In this example, 9.911 PartitionSelect Phones. Numbering PlanSelect the numbering plan for your area. Calling Search SpaceSelect E911CSS. Route OptionSelect Route this pattern. Provide Outside Dial ToneSelect this. Use Calling Partys External Phone Number MaskSelect this. Called Party Transformations, Discard Digits (Outgoing Calls)Select PreDot.
Step 4
Click Save. Cisco Unified Communications Manager saves the translation pattern. To add additional translation patterns, return to Step 2.
Related Topics

Understanding the Cisco Unified Communications Manager Examples, page 4-1 Creating a Phone Partition, page 4-2 Creating a Phone Calling Search Space, page 4-2
Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP
You must set up a gateway to use a CAMA or PRI connection to the emergency network or PSTN so that emergency calls can be routed to the local PSAP. See the documentation for your gateway for information on setting up the gateway, and the Cisco Unified Communications Manager documentation for configuring the gateway. To set up the calling search space for the gateway, follow these steps:
Procedure
Step 1
Select Device > Gateway. Cisco Unified Communications Manager opens the Find and List Gateways page. Click Find without entering search criteria to list all of the gateways, or enter the search criteria required to list the gateway you want to configure and click Find. Cisco Unified Communications Manager lists the gateways that match your criteria. Click the gateway you want to configure. Cisco Unified Communications Manager opens the Gateway Configuration page.
Step 2
Step 3
4-16
OL-12376-01
Chapter 4
Step 4 Step 5
Select E911CSS for Calling Search Space. Click Save. Cisco Unified Communications Manager saves your changes.
Related Topics

Creating a Cisco Emergency Responder Calling Search Space, page 4-5 Obtain CAMA or PRI Trunks to the PSTN, page 1-17 Deploying Cisco Emergency Responder, page 1-21 How Cisco Emergency Responder Fits Into Your Network, page 1-7
Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

If you have more than one Cisco Emergency Responder (Cisco ER) group in a Cisco ER cluster, you must configure route patterns to enable each Cisco ER group to route emergency calls to another Cisco ER group if a callers phone homes to a Cisco Unified Communications Manager cluster outside the current location of the phone. See the Understanding Cisco Emergency Responder Clusters and Groups section on page 1-12 for a detailed explanation of how Cisco ER groups communicate within a Cisco ER cluster. This procedure explains how to create the route pattern for one Cisco ER group. You must create this pattern in the Cisco Unified Communications Manager clusters that are not supported by the Cisco ER group. Consider the network setup in Figure 4-1. For inter-group communications to work:
You must define inter-cluster trunks in each Cisco Unified Communications Manager cluster to enable communications between the Cisco Unified Communications Manager clusters. See the Cisco Unified Communications Manager documentation for information on creating these types of gateways. You must define the route pattern 1000.911 in Cisco Unified Communications Manager clusters CCM-C and CCM-D. You must define the route pattern 2000.911 in Cisco Unified Communications Manager clusters CCM-A and CCM-B. In Cisco ER group 1, define 1000.911 as the Inter Cisco ER Group Route Pattern. In Cisco ER group 2, define 2000.911 as the Inter Cisco ER Group Route Pattern.
These definitions allow a call in an ERL managed by Cisco ER group 2 to be routed to Cisco ER group 2 even though the phone homes to Cisco Unified Communications Manager cluster CCM-B, which is serviced by Cisco ER group 1.
4-17
Figure 4-1
Chicago
Understanding Inter Cisco Emergency Responder Group Route Patterns

New York Cisco Unified CM-B
M
Cisco Unified CM-A

M
Cisco Unified CM-C

M
Cisco Unified CM-D

M
IP
182294
ext.3003
Before You Begin
The dial plans must be unique between all Cisco Unified Communications Manager clusters supported by a Cisco ER cluster. For example, in the network shown in Figure 4-1, the extension 3003 can only be defined in Cisco Unified Communications Manager cluster CCM-B. To create the route pattern for one Cisco ER group, follow these steps:
Procedure
Step 1
Select Call Routing > Route/Hunt > Route Pattern. Cisco Unified Communications Manager opens the Find and List Route Patterns page.
Step 2
Click Add New. Cisco Unified Communications Manager opens the Route Pattern Configuration page. Enter the information for the route pattern:
Step 3
Route PatternA pattern that you can transform to the emergency call number, typically a number, a dot, and the emergency call number. For example, 1000.911 or 2000.911. The pattern can only consist of numbers and dots. PartitionSelect E911. Numbering PlanSelect the numbering plan for your area. Gateway/Route ListSelect the inter-cluster trunk gateway to use for connecting to the Cisco Unified Communications Manager cluster supported by the Cisco ER group whose inter Cisco ER group route pattern you are defining. Route OptionSelect Route this pattern. Called Party Transformations Discard DigitsSelect PreDot if you use the suggested pattern, such as 1000.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).
Step 4
Click Save. Cisco Unified Communications Manager saves the route pattern. To add additional route patterns, return to Step 2.
4-18
OL-12376-01
Chapter 4
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User
Step 5
Ensure you define the route pattern in all other Cisco Unified Communications Manager clusters serviced by Cisco ER groups other than the Cisco ER group whose inter Cisco ER group route pattern you are defining.
Related Topics

Creating a Cisco Emergency Responder Partition E911, page 4-4 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Installing Cisco Emergency Responder 2.0 on a New System, page 2-3
Creating a Cisco Emergency Responder Cisco Unified Communications Manager User

You must add Cisco ER as a Cisco Unified Communications Manager user. The settings you enter here are used when you configure the Cisco Unified Communications Manager settings for Cisco ER. To add Cisco ER as a Cisco Unified Communications Manager user, follow these steps:
Procedure
Step 1
In Cisco Unified Communications Manager, select User Management > Application User. Click the Add New button. Cisco Unified Communications Manager displays the Application User Configuration page. Complete the following required fields:

Step 2
User IDUse a descriptive name such as CER_User. PasswordEnter a password for this user. Confirm PasswordRe-enter the password for this user.
Step 3
In the Device Information section, select the desired route point(s) and CTI port(s) and then click the down arrow to add the selected devices to the users control list. The list of devices appears in the Controlled Devices area. Select the following devices.
Step 4
Note a. b. c. d. Step 5 Step 6
You may need to use Find Phones or Find Route Points to select the desired devices. All CTI ports created for Cisco Emergency Responders use. For more information, see the Creating the Required CTI Ports section on page 4-8. The primary emergency call number, for example, 911. Also, select this number as the users primary extension. The backup emergency call number, for example, 912. The route point used for ELINs, for example, 913XXXXXXXXXX.
Click Save. In the Cisco Unified Communications Manager menu at the top, click User Management > User Group.
4-19
Chapter 4 Configuring JTAPI Security
The user group search page appears.

Step 7
At search criterion, enter standard and click Find. The list of user groups starting with the name standard appears. Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page. Click Add Application Users to Group. The Find and List Application Users pop-up window appears. Enter the User ID created in Step 2 as the search criterion and click Find. The list of Applications users appears.
Step 8 Step 9
Step 10
Step 11
Click the checkbox next to the user ID and click Add Selected. Cisco Unified Communications Manager adds the selected user to the Standard CTI Allow Calling Number Modification user group.
Step 12
Click User Management > User Group. The user group search page appears.
Step 13
Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears. Click on the Standard CTI Enabled group. Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.
Step 14 Step 15
Related Topics

Creating the Emergency Call Route Points, page 4-6 Creating the Required CTI Ports, page 4-8
Configuring JTAPI Security

Cisco ER 2.0 allows you to enable secure JTAPI communications between Cisco ER cluster servers and the Cisco Unified Communications Manager CTI Manager. To configure secure JTAPI communications, follow these steps:
Procedure
Step 1
Verify that the Cisco Unified Communications Manager cluster is in secure mode by doing the following:
a. b.
In Cisco Unified Communications Manager, go to System > Enterprise Parameters. Under Security Parameters, verify that Cluster Mode Security is set to 1.
Note
The Cluster Mode Security value is configured using the Cisco Unified Communications Manager CTL client. For more information on setting this value, see the Cisco Unified Communications Manager Security Guide.
Step 2
Add the Cisco ER application user to the Standard CTI Secure Connection group.
4-20
OL-12376-01
Chapter 4
Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0 Configuring JTAPI Security
Step 3
Create two CAPF profiles for the Cisco ER application usersone for the Publisher and one for the Subscriberby doing the following:
a. b.
In Cisco Unified Communications Manager, go to User Management > Application User CAPF Profile. Add the new CAPF profile, making sure that the Certificate Operation Required field is in the Install/Upgrade mode. For detailed information on adding a CAPF profile, see the Cisco Unified Communications Manager Security Guide.
Step 4
If you are using Cisco Unified Communications Manager 6.0, follow these steps:
a. b. c. d.
Choose User Management > Application User. The Find and List Application User CAPF Profiles page appears. Perform a search for the application user and select the application user from the results list. The Application User Configuration page appears. Click on the Edit Credential button. The Credential Configuration page appears. Ensure that the User Must Change at Next Login box under Credential Information is not checked. If it is checked, uncheck it.
Step 5
You must also enable JTAPI security in Cisco ER 2.0. See the Identifying the Cisco Unified Communications Manager Clusters section on page 5-21 for details.
Related Topics

Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Identifying the Cisco Unified Communications Manager Clusters, page 5-21
4-21
Chapter 4 Configuring JTAPI Security
4-22
OL-12376-01
C H A P T E R

After you install Cisco Emergency Responder (Cisco ER) and configure Cisco Unified Communications Manager, you can configure Cisco ER so that it begins managing emergency calls. These topics describe how to configure Cisco Emergency Responder 2.0:

Overview of Cisco Emergency Responder Configuration, page 5-1 Managing Cisco Emergency Responder Users, page 5-9 Managing Cisco Emergency Responder Roles, page 5-11 Managing Cisco Emergency Responder User Groups, page 5-13 Logging Into and Out of Cisco Emergency Responder, page 5-15 Configuring Servers and Server Groups, page 5-16 Configuring the Cisco Emergency Responder Cluster and Cluster DB Host, page 5-23 Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder, page 5-24 Working with Emergency Response Locations, page 5-24 Configuring Switches for Cisco Emergency Responder, page 5-39 Managing Phones, page 5-47
Overview of Cisco Emergency Responder Configuration

Cisco ER 2.0 provides several new features, including expanded administrative website interfaces, role-based user management, and upload/download utilities. These topics provide an overview of configuring the Cisco ER:

Cisco Emergency Responder Website Interfaces, page 5-2 Role-Based User Management, page 5-2 Using the Upload and Download Utilities, page 5-6 Cisco Emergency Responder 2.0 Configuration Task Checklist, page 5-7
5-1
Chapter 5 Overview of Cisco Emergency Responder Configuration
Cisco Emergency Responder Website Interfaces

Cisco ER 2.0 provides several websites from which you can access and use different parts of the system. From the main Cisco ER 2.0 web page, you can access the following areas:

Cisco ER Serviceability Cisco ER Administration (default home) Cisco Unified OS Administration Disaster Recovery System Cisco ER User Cisco ER Admin Utility
Each of these websites allows a user access to different parts of the system and requires a separate login and password. Access to these websites is controlled through the role-based user management mechanism (for more information, see the Role-Based User Management section on page 5-2). When the Cisco ER 2.0 system is first installed, a default CERAdministrator user is created. The default CERAdministrator has full access to all websites except the Cisco Unified OS Administration and Disaster Recovery System websites, and has the ability to create users, roles, and user groups. The default CERAdministrator cannot be deleted from the system.
Related Topics

Appendix A, Administration Web Interface For Cisco Emergency Responder Appendix B, Serviceability Web Interface For Cisco Emergency Responder Appendix C, Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Appendix D, Disaster Recovery System Web Interface For Cisco Emergency Responder
Role-Based User Management

Cisco ER 2.0 uses a role-based user management mechanism. The following topics describe this mechanism:

User Management, page 5-2 Role Management, page 5-3 User Group Management, page 5-5
User Management
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.
5-2
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Overview of Cisco Emergency Responder Configuration
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.
Related Topics

Managing Cisco Emergency Responder Users, page 5-9 Find and List Users, page A-46
Role Management
On installation, the system creates six default roles. Table 5-1 lists and describes the default roles.
Note
Default roles cannot be deleted.

Table 5-1 Default Roles
Role CER System Admin CER Serviceability CER Admin Utility CER Network Admin
Description Has access to all system administration screens Has access to all serviceability screens. Has access to all Admin Utility screens. Has access to Cisco Unified Communications Manager, LAN switch, and SNMP settings screens Has access to all ERL-related screens Has access to the user screens
CER ERL Admin CER User
When creating a new role or modifying an existing role, you specify which system resources will be assigned to the role. A resource is the same thing as a web page or a menu item within the Cisco ER 2.0 administration website. For example, the Find and List Roles web page is a resource, as is the User Management > Role menu item. Table 5-2 shows the resources that are available to each default role.
Note
Some resources are groups of menu items. For example, the Logs menu in the Cisco ER Serviceability website is one resource but it contains many sub-menus.
Table 5-2
Resources Assigned to Default Roles
Resource Add Subscriber Admin Utility ALI Formatting Tool All Logs Application User
CER System Admin x x x
CER Network Admin
CER ERL Admin
CER Serviceability
CER Admin Utility
CER User
x x
5-3
Table 5-2
Resources Assigned to Default Roles (continued)
Resource Call History CallManager Details CER Groups in Cluster Change CUCM Version Cluster DBHost Setting Control Center CPU and Memory Usage Device SNMP Settings Disk Usage ERL ERL Audit Trail ERL Debug Tool Event Viewer File Management Utility Functional role IP Subnet License Management Mail Alert Configurations Manually Configured Phones MIB2 System Group Configuration OnsiteContact Phone Search Point to New Publisher Processes PS ALI Convert PS ALI Export Run Tracking Tracking Schedule Server Server Group LAN Switches SNMP V1/V3c Configuration SNMP V3 Configuration Switch Port
CER System Admin x x x
CER Network Admin x
CER ERL Admin
CER Serviceability
CER Admin Utility
CER User
x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x
5-4
OL-12376-01
Chapter 5
Table 5-2
Resources Assigned to Default Roles (continued)
Resource Synthetic Phone Telephony Unlocated Phones User Call History User Group Web Alert
CER System Admin x x x x
CER Network Admin
CER ERL Admin x x
CER Serviceability
CER Admin Utility
CER User
x x
Related Topics

Managing Cisco Emergency Responder Roles, page 5-11 Find and List Roles, page A-49
User Group Management

On installation, the system creates six default user groups. Table 5-3 lists and describes the default user groups.
Note
Default user groups cannot be deleted.

Table 5-3 Default User Groups
User Group CER System Administrator CER Network Administrator CER ERL Administrator CER Serviceability CER Admin Utility CER User
Description Assigned System Administration roles Assigned Network Administration role Assigned ERL Administration role Assigned Serviceability role Assigned Admin Utility role Assigned User role
You can create additional user groups. 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.
Related Topics

Managing Cisco Emergency Responder User Groups, page 5-13 Find and List User Groups, page A-51
5-5
Using the Upload and Download Utilities

Cisco ER 2.0 includes download and upload utilities that allow you to transfer bulk data in the form of csv files from a Cisco ER server to a local system (download) and from a local system to a Cisco ER server (upload). For example, you can export database details to a csv file and then download the csv file to a local system. On the local system, you can modify the csv file, upload it the Cisco ER server, and import the data in the csv file into the Cisco ER database. Table 5-4 lists the Cisco ER administrative web pages from which you can use the upload and download utilities and gives the navigation path to each page.
Note
You can upload only four file types: xml, csv, lic, and txt. Filenames must not contain spaces.
Table 5-4 Administrative Web Pages Containing the Upload and Download Utilities
Page Name Find and List ERLs LAN Switch Details Switch Port Details Find and List IP Subnets
Navigation Path ERL > ERL Details Phone Tracking > LAN Switch Details ERL Membership > Switch Ports ERL Membership > IP Subnets
Find and List Manually Configured Phones ERL Membership > Manually Configured Phones
Downloading a File
To download a file from a Cisco ER 2.0 server to a local system, follow these steps:
Procedure
Step 1 Step 2
From one of the pages listed in Table 5-4, click Export. The Export page appears. If you have previously exported the data to a file, skip to Step 3. If you have not previously exported data to a file, use the Select Export Format pulldown menu to select the file format, then enter the name of the file to be created in the Enter Export File Name field. Click Export. The data is exported to the specified file. Use the Select a File to Download pulldown menu to select the file that you want to download, then click Download. The file is downloaded to your local system.
Step 3
Uploading a File
To upload a file from a local system to a Cisco ER 2.0 server, follow these steps:
Before You Begin
Before beginning the procedure, make sure the file to be uploaded exists on your local system. The file can be one that was previously downloaded from a Cisco ER 2.0 server, or one that you created.
5-6
OL-12376-01
Chapter 5
Procedure
Step 1 Step 2 Step 3 Step 4 Step 5
From one of the pages listed in Table 5-4, click Import. The Import page appears. Click Upload. The Upload File page appears. Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system. Select the file to be uploaded and click Open. The pathname of the file to be uploaded appears in the Select the file to be uploaded field of the Upload File page. Click Upload. The file is uploaded to the Cisco ER server. You can then import the data from the file.
Related Topics

Find ERL Data, page A-12 LAN Switch Details, page A-28 Switch Port Details, page A-31 Find and List IP Subnets, page A-35 Find and List Manually Configured Phone, page A-41 File Management Utility, page A-61
Cisco Emergency Responder 2.0 Configuration Task Checklist

This checklist provides information on the tasks that need to be completed to configure Cisco ER and indicates which user types can complete the tasks, with pointers to more detailed information.
Note
Some of the tasks listed below can be done in parallel.
Table 5-5
Configuration Task Checklist
Task
System Administrator Tasks
Description and Location Information Create and configure Cisco ER users and groups. See the Managing Cisco Emergency Responder Users section on page 5-9 and the Logging Into and Out of Cisco Emergency Responder section on page 5-15. See the Configuring a Cisco Emergency Responder Server Group section on page 5-16. See the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18. See the Configuring Cisco Emergency Responder Servers section on page 5-19. See the Uploading the Cisco Emergency Responder License File section on page 5-20.
Create the users your organization requires for Cisco ER administration. Create the Cisco ER group. Configure the Cisco ER groups telephony settings. Update Cisco ER servers to the Cisco ER group. Upload the product license key.
5-7
Table 5-5
Configuration Task Checklist (continued)
Task Identify and configure the Cisco Unified Communications Manager clusters whose emergency calls this Cisco ER group will handle.
Note
Description and Location Information See the Identifying the Cisco Unified Communications Manager Clusters section on page 5-21.
The network administrator can also perform this step. See the Understanding the Cisco Emergency Responder System Administrators Role section on page 10-4. Identify the switches and configure the connection to them. See the Configuring the SNMP Connection section on page 5-39. See the Defining the Phone Tracking and Switch Update Schedules section on page 5-41.
Understand recurring system administration tasks.

Network Administrator Tasks
Enter the SNMP read community strings. Define the schedule Cisco ER should use for updating information from the switches.
Identify the switches that can have phones connected See the Identifying the LAN Switches section on page 5-42. to them. Run the switch-port and phone update process so that See the Manually Running the Switch-Port and Phone Update Cisco ER can identify the ports on the switches and Process section on page 5-45. whether phones are attached to them. Understand recurring network administration tasks.
ERL Administrator Tasks
See the Understanding the Network Administrators Role section on page 10-3. Identify your onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. See the Understanding ERLs section on page 5-25 and Overview of ERL Management section on page 5-26 for a more detailed overview of ERL management. See the Identifying Security Personnel (Onsite Alert Personnel) section on page 5-27. See the Creating ERLs section on page 5-28. See the Configuring Switch Ports section on page 5-47.
Identify the onsite alert (security) personnel that should receive alerts from Cisco ER Create the ERLs. Assign the ERLs to switch ports.
Note
The network administrator must add the switches and run the switch-port and phone update process before you can do this task. Cisco ER does not automatically track the movement of these phones. See the Identifying Unlocated Phones section on page 5-52.
Add phones that Cisco ER does not directly support. See the Manually Defining a Phone section on page 5-53.
Note
Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Cisco ER from locating these phones. Assign ERLs to the phones that remain. Export the ALI data and transmit it to your service provider. Work with your service provider to determine transmission requirements. Understand recurring ERL administration tasks.
See the Exporting ERL Information section on page 5-36 and the Exporting ALI Information for Submission to Your Service Provider section on page 5-37. Understanding the ERL Administrators Role section on page 10-2.
5-8
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Managing Cisco Emergency Responder Users
Managing Cisco Emergency Responder Users

When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines one default CERAdministrator user (see the User Management section on page 5-2 for more information). You can also define additional users or modify existing users. These topics describe how to add new users and how to modify and delete existing users:

Adding Users, page 5-9 Modifying Users, page 5-10 Deleting Users, page 5-10
Adding Users
You can add additional users to the system and then assign them to user groups. The security levels for new users are determined by which user groups you assign them to. You can add users to either the primary and standby servers within a single Cisco ER group. Since access is allowed based on the combination of the user groups defined on the two servers, a user that is defined only on the primary server will still be able to log into the backup server.
Before You Begin
Develop a list of users for each security level. You need to know the user names of all onsite alert personnel, and you should determine who should have access to each of the administration security levels. To add users, follow these steps:
Note
You can always add additional users or remove current users later using this procedure. You cannot remove the default CERAdministrator user.
Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User. The Find and List Users page appears.
Click the Add New User button. The User Configuration page appears. Enter the required information in the User Name, Password, and Confirm Password fields. Click Insert. Repeat these steps to add additional users. To assign security levels to the new users, you must add them to one or more user groups. See the Managing Cisco Emergency Responder User Groups section on page 5-13 for details. Repeat this procedure on the other Cisco ER server in the Cisco ER server group.
Note
To remove a user from a group, you must remove the user from groups on both the primary and standby servers.
5-9
Chapter 5 Managing Cisco Emergency Responder Users
Modifying Users
Once you have created a user, you can modify the users password. To modify the users password, follow these steps:
Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User. The Find and List Users page appears. Enter search criteria to find the specific user you want to modify and click Find, or click Find without any search criteria to display all configured users. The search results will display. Click the user name. The User ConfigurationModify User page appears. In the Password text box, enter the new password. In the Confirm Password text box, reenter the new password. Click Update.
Deleting Users
To delete a user, follow these steps:
Note
You cannot delete the CERAdministrator user.

Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User. The Find and List Users page appears. Enter search criteria to find the specific user you want to delete and click Find, or click Find without any search criteria to display all configured users. The search results appear. Find the user you want to delete and click on the Delete icon for that user. The system displays a warning prompting you to confirm the deletion. Click OK. The user is removed from the system and all User Group associations to the user are deleted.
Step 2 Step 3
Step 4
Related Topics

Logging Into and Out of Cisco Emergency Responder, page 5-15 Preparing Users for Cisco Emergency Responder, page 10-1
5-10
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Managing Cisco Emergency Responder Roles
Managing Cisco Emergency Responder Roles

When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines six default roles (see the Role Management section on page 5-3 for more information on the default roles). You can also define additional roles or modify existing roles. These topics describe how to add new roles and how to modify and delete existing roles:

Adding Roles, page 5-11 Modifying Roles, page 5-12 Deleting Roles, page 5-12
Adding Roles
You can add additional roles to the system and assign resources to them.
Note
The default roles cannot be removed or modified.

Before You Begin
Before you begin, you should decide what additional roles you want to create and determine if any existing default role meets your needs. To add new roles, follow these steps:
Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > Roles. The Find and List Roles page appears. Click Add a New Role. The Role Configuration page appears. Enter the Role Name (required) and Description (optional) in the text boxes. From the list of resources, click the check box next to the resources to which the new role should have access. Click Insert to add the new role to the system. To verify that you successfully added the new role, go back to the User Management > Roles page and perform a role search. Enter search criteria to find the specific role you just created and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Verify that the new role is listed.
Step 2
5-11
Chapter 5 Managing Cisco Emergency Responder Roles
Modifying Roles
To modify existing roles, follow these steps:
Note
You cannot modify default roles.

Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > Roles. The Find and List Roles page appears.
Step 2 Step 3
Enter search criteria to find the specific role you want to modify and click Find, or click Find without any search criteria to display all configured roles. The search results appears. Click the role name. The Role ConfigurationModify Role page appears.
If desired, modify the Role Name and Description (if one is listed) in the text boxes. From the list of resources, click or unclick the check boxes next to the resources to which the modified role should have access. Click Update to add the updated role information to the system. To verify that you successfully modified the new role, go back to the User Management > Roles page and perform a role search. Enter search criteria to find the specific role you just modified and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Click the role name and verify that the modified role information appears on the Role ConfigurationModify Role page.
Deleting Roles
To delete an existing role, follow these steps:
Note
You cannot delete a default role.

Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > Roles. The Find and List Roles page appears. Enter search criteria to find the specific role you want to delete and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Click the Delete icon for the role to be deleted. A warning message displays asking you to verify that you want to delete the role. Click OK to delete the role.
Step 2 Step 3
Step 4
5-12
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Managing Cisco Emergency Responder User Groups
The Find and List Roles page will be refreshed and the role will no longer be listed in the Role Names list.
Managing Cisco Emergency Responder User Groups

When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines six default user groups (see the User Group Management section on page 5-5 for more information on the default user groups). You can also define additional user groups or modify existing user groups. These topics describe how to add new user groups and how to modify existing user groups:

Adding User Groups, page 5-13 Modifying User Groups, page 5-14 Deleting User Groups, page 5-15
Adding User Groups

You can add user groups to the system and assign users and roles to each new user group.
Before You Begin
Before you begin, you should decide what additional user groups you want to create and determine if any existing default user groups meets your needs. To add new user groups, follow these steps:
Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User Group. The Find and List User Groups page appears. Click Add a User Group. The User Group ConfigurationAdd User Group page appears. Enter the User Group Name (required) and Description (optional) in the text boxes. Click Add Users. The User Names page appears. Enter search criteria to find a specific user and click Find, or click Find without any search criteria to display all configured users. The search results appear. Click the check box to the left of the user name(s) to be added and click Add. The User Name page closes and the added name(s) appears in the Add User to Group text box on User Group ConfigurationAdd User Group page.
Step 2
Step 3 Step 4
Step 5 Step 6
Note Step 7
To delete users from this list, select the user name and click Remove Users.
Click Add Roles.
5-13
Chapter 5 Managing Cisco Emergency Responder User Groups
The Role Names page appears.

Step 8 Step 9
Enter search criteria to find a specific role and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Click the check box to the left of the role(s) to be added and click Add. The Role Names page closes and the added role(s) appears in the Add Roles to Group text box on User Group Configuration page.
Note Step 10
To delete roles from this list, select the user name and click Delete Roles.
Click Insert to add the new role to the system.
Modifying User Groups

To modify existing user groups, follow these steps:
Note
You cannot modify default user groups.

Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User Group. The Find and List User Groups page appears. Enter search criteria to find the specific user group you want to modify and click Find, or click Find without any search criteria to display all configured user groups. The search results appear. Click the user group name. The User Group ConfigurationModify User Group page appears. If desired, modify the description of the User Group (if one is listed) in the Description text box. The Add Users to Group text box displays the names of the users currently assigned to the user group. To add additional users, follow the procedure given in the Adding User Groups section on page 5-13. To remove users, highlight the name of the user(s) and click Remove Users. The Assign Roles to Group text box displays the names of the roles currently assigned to the user group. To add additional roles, follow the procedure given in the Adding Roles section on page 5-11. To remove roles, highlight the name of the role(s) and click Remove Roles. When you are finished, click Update to save the updated user group information to the system. To verify that you successfully modified the user group, go back to the User Management > User Group page and perform a search. Enter search criteria to find the specific user group you just modified and click Find, or click Find without any search criteria to display all configured user groups. The search results appear. Click the user group name and verify that the modified user group information appears on the User Group ConfigurationModify User Group page.
Step 2 Step 3
Step 4 Step 5
Step 6
Step 7 Step 8
5-14
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Logging Into and Out of Cisco Emergency Responder
Deleting User Groups

To delete an existing user group, follow these steps:
Note
You cannot delete the default user groups. You can only delete user groups that you have created.
Procedure
Step 1
From the Cisco ER Administration web interface, select User Management > User Group. The Find and List User Groups page appears.
Step 2 Step 3
Enter search criteria to find the specific user group you want to delete and click Find, or click Find without any search criteria to display all configured user groups. The search results appear. Click the Delete icon for the user group to be deleted.
Note
You cannot delete the default user groups. You can only delete user groups that you have created.
A warning message appears asking you to verify that you want to delete the user group.
Step 4
Click OK to delete the user group. The Find and List Roles page will be refreshed and the deleted user group will no longer be listed in the User Groups list.
Logging Into and Out of Cisco Emergency Responder

You must log into the Cisco Emergency Responder (Cisco ER) web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See the Role-Based User Management section on page 5-2 for more information.
Before You Begin
You must have a valid user ID and password before you can log into Cisco ER. Contact the main Cisco ER administrator if you cannot log into the interface and you are supposed to have administrative access. To log into Cisco ER, follow these steps:
Procedure
Step 1
From an Internet Explorer 6.0 / 7.0 or Mozilla Firefox 2.0 browser, open this URL, where servername is the DNS name or IP address of the Cisco ER server: http://servername/ceradmin. The browser opens the Cisco ER Server Administration page.
5-15
Chapter 5 Configuring Servers and Server Groups
Step 2
Use the Navigation pulldown menu to select the website you wish to log into. The Cisco ER websites are as follows:

Cisco ER Serviceability Cisco ER Administration Cisco Unified OS Administration Disaster Recovery System Cisco ER User Cisco ER Admin Utility
To open the Log-in page, click one of these links.

Step 3
Click Go. The login screen for the selected website appears. Enter your user name and password, and click Login. Cisco ER logs you into the selected website. Unless you log in as a system administrator, some commands in the menus may have lock icons. These locks indicate pages you cannot view because of your authorization level. When you are finished, click Logout above the menu bar to log out.
Step 4
Related Topics

Managing Cisco Emergency Responder Users, page 5-9 Managing Cisco Emergency Responder Roles, page 5-11 Managing Cisco Emergency Responder User Groups, page 5-13 Preparing Users for Cisco Emergency Responder, page 10-1
Configuring Servers and Server Groups

These topics describe how to configure Cisco Emergency Responder (Cisco ER) servers and server groups, and the telephony connection between the Cisco ER groups and Cisco Unified Communications Manager:

Configuring a Cisco Emergency Responder Server Group, page 5-16 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Configuring Cisco Emergency Responder Servers, page 5-19 Uploading the Cisco Emergency Responder License File, page 5-20 Identifying the Cisco Unified Communications Manager Clusters, page 5-21
Configuring a Cisco Emergency Responder Server Group

To configure a Cisco Emergency Responder (Cisco ER) server group, you must connect to the administration interface on one of the servers that will be part of the 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.
5-16
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Configuring Servers and Server Groups
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. See the Data Integrity and Reliability Considerations section on page 1-16 for more information.
Before You Begin
You must have system administrator authority to configure a Cisco ER server group. To configure a Cisco ER server group, follow these steps:
Procedure
Step 1
Select System > Cisco ER Group Settings. Cisco ER opens the Cisco ER Group Settings page.
Step 2
Fill in the group settings, as described in the Cisco ER Group Settings section on page A-3. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

Cisco ER Group NameEnter a name for the group. This name is mainly for your use, so choose a name you find meaningful. SMTP Mail Server and Source Mail IDIf you want Cisco ER to send email alerts to your Cisco ER system administrator and/or onsite alert personnel (security), enter the IP address or DNS name of a mail server, and the name of an account on that server to use for sending email. If you configure email addresses for onsite alert personnel (see the Identifying Security Personnel (Onsite Alert Personnel) section on page 5-27), they receive email alerts from this account when an emergency call is made in their assigned area. If their email address is for an email-based paging system, they are paged. System Administrator Mail IDIf you want Cisco ER to send email alerts in the case of critical errors, enter the email account information for the system contact. Enable Syslog and Syslog ServerIf you are using CiscoWorks2000 as your network management software, you can configure Cisco ER to send log messages to the Syslog Collector. To use Syslog Collector, select Enable Syslog and enter the fully-qualified DNS name of the Syslog server.
Step 3
When you are satisfied with your settings, click Update Settings. Cisco ER creates the Cisco ER group.
Related Topics

Configuring Cisco Emergency Responder Servers, page 5-19 Cisco ER Group Settings, page A-3 Collecting Information from Syslog, page 11-31
5-17
Configuring Group Telephony Settings For the Cisco Emergency Responder Server
You must configure the telephony settings to tell Cisco Emergency Responder (Cisco ER) the phone numbers it should use for emergency calls and ELINs.
Before You Begin
You must have system administrator authority to configure the telephony settings. Before you configure these settings, create the required route points and route patterns in Cisco Unified Communications Manager. See these topics for more information:

Creating the Emergency Call Route Points, page 4-6 Creating the Route Patterns for ELINs, page 4-10 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17
To configure telephony settings, follow these steps:

Procedure
Step 1
Select System > Telephony Settings. Cisco ER opens the Telephony Settings page.
Step 2
Enter the telephony settings, as described in the Telephony Settings section on page A-4:

UDP Port BeginThe first UDP port Cisco ER can use for telephone calls. For example, 32000. Inter Cisco ER Group Route PatternThe route pattern that other Cisco ER groups will use to route emergency calls to this group, for example, 1000.911. PSAP Callback Route Point PatternThe CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs). ELIN Digit Strip PatternThe digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913. Route Point for Primary Cisco ER ServerThe route point you created for the Cisco ER primary server to use. For example, 711. You may change this number. See the Modifying the Emergency Number section on page 5-19. Route Point for Standby Cisco ER ServerThe route point you created for the Cisco ER standby server to use. For example, 912. IP Type of Service (00-FF)The value of the Type of Service (TOS) byte in the IP header. The default 0xB8 implies a TOS class of Priority Queue. It is recommended that this default value be used for Cisco ER. Onsite Alert Prompt Repeat CountThe number of times a prompt is given on the onsite security phone.
Step 3
Click Update Settings to save your changes.
5-18
OL-12376-01
Chapter 5
Modifying the Emergency Number

You can configure or modify the emergency number that was automatically set at installation time by entering the number in the Route Point for Primary Cisco ER Server field. Before you configure or change the emergency number, you must configure the new route point and associate it with the Cisco ER user in Cisco Unified Communications Manager.
Caution
Modify the emergency number during off-peak hours. To modify the emergency number, follow these steps:
Procedure
Step 1
Associate the new route point with the Cisco ER user in Cisco Unified Communications Manager. See Creating a Cisco Emergency Responder Cisco Unified Communications Manager User section on page 4-19. Modify the route point for the new number: enter the number in the field Route Point for Primary Cisco ER Server. Click Update Settings.
Step 2 Step 3
Note
Cisco ER can still support only one emergency number; once you change it, Cisco ER will start routing calls received at the new emergency number route point.
Related Topics

Telephony Settings, page A-4 Creating the Emergency Call Route Points, page 4-6 Creating the Route Patterns for ELINs, page 4-10 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17 Identifying the Cisco Unified Communications Manager Clusters, page 5-21
Configuring Cisco Emergency Responder Servers

After you create a Cisco Emergency Responder (Cisco ER) group (see the Configuring a Cisco Emergency Responder Server Group section on page 5-16), you can use the Server Settings page to update Cisco ER server settings (for example, to change the server name or to change the trace and debug settings) and to delete servers.
Before You Begin
You must have system administrator authority to update or delete a Cisco ER server.
5-19
To configure Cisco ER servers, follow these steps:

Procedure
Step 1
Select System > Server Settings. Cisco ER opens the Server Settings page. To change the server settings (Server Name or Debug Package List, or Trace Package List settings), select the server name in the left-hand Servers list. Cisco ER loads the servers settings into the edit boxes. Make your changes and click Update. To remove a server from the group, select the server and click Delete. If you are permanently removing the server from your network, ensure that you make any required changes to your telephony network so that calls are not misdirected or dropped. When you are satisfied with your settings, click Update. Cisco ER saves your changes and displays them in the list of servers at the top of the page.
Step 2
Step 3
Step 4
Related Topics

Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring a Cisco Emergency Responder Server Group, page 5-16 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Identifying the Cisco Unified Communications Manager Clusters, page 5-21 Server Settings for CERServerGroup, page A-6
Uploading the Cisco Emergency Responder License File

You must upload a valid server license file for the Publisher and a second server license file for the Subscriber in order to use Cisco Emergency Responder (Cisco ER) 2.0. Each server license file also provides for 100 users. For all users over the 200 provided for by the server licenses, you must order and upload additional user licenses. For more information, see the Licenses for Cisco Emergency Responder 2.0 section on page 1-4. You must have all server and user license files on hand before you begin this procedure.
Note
If you are unsure about which license files you require, see the Determining Your License Requirements section on page 1-6.
Before You Begin
You must have system administrator authority to access the License Manager page. To upload the Cisco ER license file, follow these steps:
Procedure
Step 1
From the Cisco ER Administration website, select System > License Manager. Cisco ER opens the License Manager page. The details of the license for the server appear.
5-20
OL-12376-01
Chapter 5
Step 2
Based on the server to which you will be uploading the license file, select the server name from the pulldown menu and click Upload License to upload the additional license file. The Upload File page appears.
Step 3
Use the Browse button to navigate to the license file to be uploaded (which you received as an email attachment after registering your Cisco ER system on Cisco.com), highlight the file name, and click Open. The name of the selected file appears in the Select file to be uploaded text box.
Step 4
Click Upload. Cisco ER uploads and installs the additional license file.
Note
The License Manager page displays the following information:

License information for the server being accessed (either Publisher or Subscriber) Consolidated user license information (Publisher and Subscriber)
Related Topics

Licenses for Cisco Emergency Responder 2.0, page 1-4 License Manager, page A-7
Identifying the Cisco Unified Communications Manager Clusters

You must identify one Cisco Unified Communications Manager server per Cisco Unified Communications Manager cluster that you want to manage with the Cisco ER group you are configuring. Cisco ER gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones Cisco ER 2.0 provides three levels of CTI failover. To enable the three levels of CTI failover, enter an IP address or DNS name for the primary CTI Manager; the Backup CTI Manager 1; and the Backup CTI Manager 2.
Before You Begin
You must have system administrator or network administrator authority to identify the Cisco Unified Communications Manager clusters. Every Cisco Unified Communications Manager server in the Cisco Unified Communications Manager cluster must be running SNMP services so that Cisco ER can obtain the required information from the server. Before configuring these settings, create the required users and CTI ports. This information must be complete before Cisco ER tries to create a provider with the Cisco ER cluster. Cisco ER only registers the CTI ports and route points that are associated with the user when the provider is created. See these topics for more information:

Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Creating the Required CTI Ports, page 4-8
5-21
To identify one Cisco Unified Communications Manager server per Cisco Unified Communications Manager cluster that you want to manage with the Cisco ER group you are configuring, follow these steps:
Procedure
Step 1
Select Phone Tracking > Cisco Unified Communications Manager Details. Cisco Emergency Responder opens the Cisco Unified Communications Manager Details page. Enter the details for the Cisco Unified Communications Manager server:
Step 2
Cisco Unified Communications ManagerThe IP address or DNS name of the server. This server must be running Cisco Unified Communications Manager and SNMP services. Do not define more than one Cisco Unified Communications Manager server within the same Cisco Unified Communications Manager cluster in the Cisco ER configuration. CTI ManagerThe IP address or DNS name of the CTI manager for the cluster to which the server belongs. CTI Manager User NameThe user you created for Cisco Emergency Responder. See the Creating a Cisco Emergency Responder Cisco Unified Communications Manager User section on page 4-19 for more information. CTI Manager PasswordThe users password. Backup CTI 1 ManagerThe IP address or DNS name of the first backup CTI manager for the cluster. Backup CTI 2ManagerThe IP address or DNS name of the second backup CTI manager for the cluster. Telephony Port Begin AddressThe first CTI port address in the sequence of ports you created for Cisco ERs use. See the Creating the Required CTI Ports section on page 4-8 for more information. Number of Telephony PortsThe number of CTI ports in the sequence you created for Cisco ERs use.
Step 3
To establish secure JTAPI communications, do the following:

a. b.
Click the Enable Secure Connection checkbox. Enter the following required information:
TFTP Server IP Address TFTP Server Port
Note
The TFTP Server Port field is pre-populated with a default value. If in Cisco Unified Communications Manager you entered a different value for the TFTP Server Port, you must enter that value here, replacing the default value.
CAPF Server IP Address CAPF Server Port
5-22
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Configuring the Cisco Emergency Responder Cluster and Cluster DB Host
Note
The CAPF Server Port field is pre-populated with a default value. If in Cisco Unified Communications Manager you entered a different value for the CAPF Server Port, you must enter that value here, replacing the default value.
Instance ID for Publisher Secure Authentication String for Publisher Instance ID for Subscriber Secure Authentication String for Subscriber
Note
You must also configure secure JTAPI communications on your Cisco Unified Communications Manager cluster. See the Configuring JTAPI Security section on page 4-20 for details.
Step 4
Click Insert. Cisco ER adds the Cisco Unified Communications Manager server to the list of servers. Repeat this procedure if you are supporting other Cisco Unified Communications Manager clusters with this Cisco ER group.
Tip
To view or change a Cisco Unified Communications Manager servers settings, click the server in the list of servers. The settings are loaded into the edit boxes. To change a setting, edit it and click Update. To remove a Cisco Unified Communications Manager server from the Cisco ER configuration, click it in the list of servers, then click Delete.
Related Topics
Cisco Unified Communications Manager Clusters, page A-25
Configuring the Cisco Emergency Responder Cluster and Cluster DB Host

To configure the Cisco ER cluster and the Cluster DB Host, follow these steps:
Procedure
Step 1
Identify the following:

All the Cisco ER groups participating in the Cisco ER cluster One of the Cisco ER publishers as Cluster DB Host A password that will be the same across the Cluster as Cluster password
5-23
Chapter 5 Configuring Cisco Emergency Responder 2.0 Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder
Using the Cisco ER Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1. Repeat steps 1 and 2 for each Cisco ER server group in the cluster. Restart Cisco ER services.
Note
Cisco ER 2.0 server groups are able to communicate with Cisco ER 1.3 server groups in a Cisco ER cluster.
Related Topics

Update Cluster DB Host, page E-3 Updating the Cisco ER Cluster Database Host Details, page 9-3
Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder
If you change or upgrade the Cisco Unified Communications Manager cluster identified in Cisco Emergency Responder (Cisco ER) to a later version, you must use the Admin Utility to identify Cisco ER with the later Cisco Unified Communications Manager version.
Note
Cisco ER does not support migration to a lower version of Cisco Unified Communications Manager once a higher version has been applied. To change or upgrade the Cisco Unified Communications Manager cluster identified in Cisco ER to a later version, see the Changing the Cisco Unified Communications Manager Version section on page 9-2.
Working with Emergency Response Locations

An emergency response location (ERL) defines the area in which an emergency call is made. Security personnel and emergency response teams use ERL information to locate an emergency caller.
Note
Cisco Unified Communications Manager 6.0 introduces a new Do-Not-Disturb feature for IP phones. If this feature is enabled for phones identified as onsite security phones, emergency alerts from Cisco ER to those phones will not alert the onsite security personnel. It is important that the Do-Not-Disturb feature be disabled for phones used with the onsite alert feature. Cisco Emergency Responder (Cisco ER) system administrators or ERL administrators can create and modify ERLs. These sections explain ERLs in greater detail and explain how to work with them in Cisco ER:

Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
5-24
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Working with Emergency Response Locations
Identifying Security Personnel (Onsite Alert Personnel), page 5-27 Creating ERLs, page 5-28 Exporting ERL Information, page 5-36 Exporting ERL Information, page 5-36 Viewing the Audit Trail for an ERL, page 5-38
Understanding ERLs
An emergency response location (ERL) is a building, area within a building, or outside area (if you extend phone service outdoors) that is to be treated as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location. Thus, when someone makes an emergency call, the public safety answering point (PSAP) and your onsite alert (security) team are notified of the ERL. If the emergency requires locating the individual who placed the emergency call, the response teams will have to find the person within the ERL. You can include more specific information using the Phone Location field for individual switch ports. This level of detail is only available for automatically tracked phones, and only appears on the Web Alert screen for onsite alert personnel. This is similar to the way emergency calls are handled for individual home users: emergency response teams know the house from which the call was placed, but have to search from room to room until they find the caller. The bigger the house, the longer the potential search. Likewise, the larger you make your ERLs, the longer it might take a response team to find an emergency caller. The laws relating to size of ERLs can vary for different cities, states, and countries. You are responsible for learning your local statutes and developing ERLs that satisfy those statutes. Work with your telephone service provider; they can help you understand the laws. Ultimately, you will have to submit the automatic location information (ALI) for your ERLs to your service provider so that calls from your ERLs are routed to the appropriate PSAPs. Here are some examples of possible ERLs:

You have a 25-story building, each floor has 10,000 square feet of office space. You might create 25 ERLs, one per floor. Better, you could divide each floor in half and create 50 ERLs, two per floor. You have 5 buildings. Each building was a former home, and they are approximately 3000 square feet. You might create 5 ERLs, one per building, even though some of the buildings are multi-story. You have a 5 story building, but the building is very large, so that each floor has 100,000 square feet of office space. You might create 20 ERLs per floor for a total of 100 ERLs, each ERL covering approximately 5,000 square feet. You have a high concentration of telephones, and local standards require that an ERL have no more than 48 telephones. In this case, you will have to define zones based on telephone coverage, rather than on physical space. Try to create zones that are recognizable as a physical location, for example, BldJFloor5Row3.
Related Topics

Overview of ERL Management, page 5-26 Creating ERLs, page 5-28 Exporting ERL Information, page 5-36 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 What Happens When an Emergency Call Is Made, page 1-8
5-25
Chapter 5 Working with Emergency Response Locations
Overview of ERL Management

To establish a useful set of ERLs, consider following these steps:
1.
Become familiar with local statutes on emergency call requirements. Local laws might have specific requirements or recommendations on the maximum size of an ERL (for example, no larger than 7,000 square feet). Talk to your service provider to learn about their rules or recommendations. Work with the security personnel in your organization to determine what they feel is required for them to effectively respond to an emergency call. Besides having suggestions about the size of the various zones, security personnel should also review the ERL naming strategy you propose to use, because the ERL name will be one of the major data points they will use to locate the emergency caller. Security personnel also can use these fields to help locate a caller:
The Location field in the ALI, which you can use to clarify ERL names, for example, by
2. 3.
including the complete street address of the building. Although security can also view the ALI from the Cisco Emergency Responder (Cisco ER) user interface, it takes a few extra steps to view the entire ALI, so including a complete address in the Location field can expedite response.
The Phone Location field associated to the switch port. You can use this field to fine-tune the
location, for example, by specifying the office or cube number that the port serves.
4.
Use Cisco ER to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition, you will assign personnel to each ERL. See the Identifying Security Personnel (Onsite Alert Personnel) section on page 5-27 for more information. Use Cisco ER to define the ERLs and their ALI. See the Creating ERLs section on page 5-28 for more information. Assign switch ports to the correct ERL and define the phone location for the port. See the Configuring Switch Ports section on page 5-47 for more information. Someone with network administrator authority must first add the switches to the Cisco ER configuration before you can complete this task. Define any phones that are not directly supported by Cisco ER. See the Manually Defining a Phone section on page 5-53, for more information. After you are satisfied with the ERL and ALI definitions, export the ALI information and submit it to your service provider. Work with your service provider to determine the file format and submission requirements. You must submit this information so that emergency calls from your ERLs can be routed to the correct public safety answering point (PSAP). See the Exporting ERL Information section on page 5-36 and the Exporting ALI Information for Submission to Your Service Provider section on page 5-37 for more information. After you complete this task, emergency calls from your ERLs should result in the correct onsite response personnel receiving notification of an emergency call, and the correct local PSAP receiving the actual emergency call.
5. 6.
7. 8.
Note
Ensure that you submit each ALI export file as you create it. The ALI export records include an indication that the record is either new or modified. If you do not submit an ALI export file, the subsequent file you submit might have incorrect status indications, which can result in your service provider rejecting some, or possibly all, of your submitted records.
5-26
OL-12376-01
Chapter 5
9.
Ensure you update the ERL, ALI, and switch port information as you:
Add or remove switches or ports Add or remove manually defined phones Add or remove ERLs Update ALIs
Any time you update the ELINs for an ERL, or the ALI, you should re-export ALI data and submit it to your service provider.
Related Topics

Understanding ERLs, page 5-25 Understanding the ERL Administrators Role, page 10-2
Identifying Security Personnel (Onsite Alert Personnel)

You must identify your security, or onsite alert, personnel so that you can assign them to your emergency response locations (ERLs). If an emergency call is made from an ERL, the associated onsite alert personnel receive:

A web-based alert on the Cisco Emergency Responder (Cisco ER) end-user interface. An email message. If you use an email-based paging address, the message will result in a page. A telephone call indicating that an emergency call was made.
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority. Collect information about all of your onsite alert personnel, including names, telephone numbers, and email addresses. Also, develop a unique identification name for each, if you do not already have one readily available (such as badge number). To onsite security personnel, follow these steps:
Procedure
Step 1
Select ERL > Onsite Alert Settings. Cisco ER opens the Onsite Alert Settings page.
Step 2
Enter the unique ID, name, telephone number, and email address of a security or onsite alert person. Unique ID might be a badge number, email name, or other site-specific unique name. You will use this ID to assign the person to an ERL, so ensure that you use a naming strategy useful to you. You can use an email-based paging address for the email address, so that onsite alert personnel receive a page rather than an email.
Step 3
Click Insert. Cisco ER adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.
5-27
Tip
To delete a person, first remove the person from all ERL definitions. Then, in the Available Onsite Alerts list on the Onsite Alerts Settings page, click the Delete icon corresponding to that persons record. To modify onsite alert settings, click on the persons Onsite Alert ID, Onsite Alert Name, Onsite Alert Number, or Onsite Alert Email Address in the Available Onsite Alerts list. The information for that person displays in the Modify Onsite Alert Contact section of the page. Modify the information as needed and then click Update. You cannot change a persons Onsite Alert ID: to change the Onsite Alert ID, delete the persons entry and create a new one.
Related Topics

Onsite Alert Settings, page A-10 Creating ERLs, page 5-28
Creating ERLs
These sections describe how to create emergency response locations (ERLs):

Setting Up the Default ERL, page 5-28 Setting up ERLs for Non-PSAP Deployment, page 5-29 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Importing Several ERLs at Once, page 5-32
Setting Up the Default ERL

Cisco Emergency Responder (Cisco ER) does not automatically assign new switch ports and unlocated phones to the Default emergency response location (ERL). New switch ports and unlocated phones are treated as ERL not configured. You must not configure the Default ERL to any of the Switch Ports, Unlocated Phones, Manually Configured Phones or IP Subnets. The Default ERL is used internally by Cisco ER only if no other ERL is configured for that phone. Cisco ER also uses the Default ERL for all emergency calls when the Cisco ER server is first started (or restarted when there is no standby Cisco ER server) until the initial switch port update is finished. (This process is started immediately.)
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority. You must first configure the required ELINs in Cisco Unified Communications Manager (see the Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks section on page 4-9).
5-28
OL-12376-01
Chapter 5
To set up the default ERL, follow these steps:

Procedure
Step 1
Select ERL > ERL Details. Cisco ER opens the Find and List ERLs page. Click Configure Default ERL. Cisco ER opens the ERL Information for Default window. Fill in the ERL Information for Default window. The Add New ERL section on page A-14 contains detailed explanations of each field. Click ALI Details. Cisco ER opens the ALI Information window. Fill in the ALI Information window. The ALI Information (for ERL Name) section on page A-17 contains detailed explanations of each field. When finished filling in the ALI, click Update ALI Info. Cisco ER saves your ALI. Click Close to close the window.
Step 2
Step 3 Step 4
Step 5
Step 6
Make the ERL Information for Default window the active window if it is not, and click Update. Cisco ER saves the ERL and its ALI. Click Close to close the window.
Step 7
Tip
You cannot delete the default ERL. In addition, you cannot configure other ERLs unless the default ERL has been configured.
Related Topics

Find ERL Data, page A-12 Add New ERL, page A-14 ALI Information (for ERL Name), page A-17 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
Setting up ERLs for Non-PSAP Deployment

You may want to deploy Cisco ER for on-site alerts only. That is, instead of routing emergency calls to a public safety answering point (PSAP), you route emergency calls to a specified security phone. There are two ways to set up non-PSAP deployments: Configure Security IDs OnlyIn this scenario, you configure security IDs for the zones for any ERL; you do not configure route/translation patterns. All emergency calls are routed to the ERL security. If this fails, the calls are routed to the default ERL security. Cisco ER then initiates a call to the configured security phone and plays prompts to alert security personnel to the emergency call.
5-29
To configure Security IDs only, follow these steps:

Procedure
Step 1
Identify the security personnel to be notified in case of an emergency call (see the Identifying Security Personnel (Onsite Alert Personnel) section on page 5-27). For example, configure security A with directory number 1000. Add an ERL with no route pattern/ELIN but only with security IDs for that ERL (see the Creating ERLs section on page 5-28). For example, add ERL X with security A. Go to the switch port screen and assign discovered switch ports to the already configured ERLs (see the Configuring Switch Ports section on page 5-47). For example, associate switch ports of switch IP Y to ERL X. All emergency calls from any phone connected to switch IP Y will use ERL X and ring on the security A directory number 1000.
Step 2
Step 3
Note
If you use Layer 3 (IP) roaming for wireless IP phones and/or wireless phones register using their Wireless Access Point's IP address, then Cisco ER will not be able to automatically track movement of these phones. This is because Cisco ER uses the IP address of the phone to determine the phone's location. Do not use Layer 3 roaming if you need Cisco ER to automatically track movement of wireless phones in your network. Configure Security IDs and Route/Translation PatternsIn this scenario, you configure security IDs for the zones for any ERL and you also configure a route/translation pattern without an ELIN number. Cisco ER displays a popup warning message alerting you that this zone will not have an ELIN. The emergency call is routed using the route/translation pattern; If this fails, the default pattern is used. Cisco ER then initiates a call to the configured security phone and plays prompts to alert security personnel to the emergency call.
Note
In this scenario, you must use a different route/translation pattern for each zone.
Setting Up an Individual ERL and Its Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see the Importing Several ERLs at Once section on page 5-32 section for strategies for simplifying the definition of similar ERLs.
Before You Begin
You must log into Cisco Emergency Responder (Cisco ER) with system administrator or ERL administrator authority.
5-30
OL-12376-01
Chapter 5
To define a single ERL, follow these steps:

Procedure
Step 1
Select ERL > ERL Details. Cisco ER opens the Find and List ERLs page. Click Add New ERL. Cisco ER opens the Add New ERL window. Fill in the Add New ERL window. The Add New ERL section on page A-14 contains detailed explanations of each field. Click the Add ALI button. Cisco ER opens the ALI Information window. Fill in the ALI Information window. The ALI Information (for ERL Name) section on page A-17 contains detailed explanations of each field. When finished filling in the ALI, click Save and Close.
Step 2
Step 3 Step 4
Step 5
Step 6
Make the Add New ERL window the active window if it is not, and click Insert. Cisco ER saves the ERL and its ALI. Click Close to close the window.
Step 7
Tip
To create an ERL that is similar to an existing ERL, click Find to list the existing ERLs, then click copy for the similar ERL. Cisco ER creates a copy of some ERL and all ALI information, which you can modify for the new ERL. You can create or update tags to simplify the ALI definition process. Navigate to the ALI Information window, and look for information about the location of the samplevalidate.txt file. The sample file explains how to set up tags. When you have created or updated the desired tags, select the tag name on the ALI Information window and the ALI fields are loaded with the settings associated with the tag.
Related Topics

Find ERL Data, page A-12 Add New ERL, page A-14 ALI Information (for ERL Name), page A-17 Importing Several ERLs at Once, page 5-32 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
5-31
Importing Several ERLs at Once

Rather than defining ERLs one at a time, as described in the Setting Up an Individual ERL and Its Automatic Location Information (ALI) section on page 5-30, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Cisco Emergency Responder (Cisco ER) configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Cisco ER configuration using ERL data exported from Cisco ER.
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority. Prepare an import file. Cisco ER includes detailed information about the required file format on the Import ERL Data page. The page also includes the location in which you must place the file in order to import it. Use the procedure below to go to the page and view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file. To import several ERLs at once, follow these steps:
Procedure
Step 1
Select ERL > ERL Details. Cisco ER opens the Find and List ERLs page.
Step 2
Click Import. Cisco ER opens the Import ERL Data page. Select the format of your import file (csv or xml) from the pulldown menu. Click Upload to upload the file from your local machine. See the Uploading a File section on page 5-6 for information on using the Upload utility. Select your import file. Click Import. Cisco ER imports your ERL and associated ALI data, and displays the status of the import as it proceeds. The imported data overwrites existing conflicting data in the Cisco ER configuration.
Step 7
Click Close to close the Import ERL Data window.
Related Topics

Import ERL Data, page A-21 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
Converting ALI Data

Use the PS-ALI Converter tool to generate an ERL csv (Comma Separated Value) text file that can be accepted by the Cisco ER ERL. You must first upload an existing ALI file in NENA 2.0 format to Cisco ER before converting it.
5-32
OL-12376-01
Chapter 5
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority. To convert ALI data, follow these steps:
Procedure
Step 1
Select Tools > PS-ALI Converter. Cisco ER displays the PS-ALI Converter page. Click the Upload PSALI file button to upload an ERL file in NENA 2.0 format. The Upload File page appears. Follow the instructions in the Uploading a File section on page 5-6 to upload the ERL file. Select the uploaded file from pulldown menu. In the Output file (in csv format) Name field, enter the name of the converted csv file you want to create. Click Convert to create the csv file. The generated csv file is located in the following folder:
%cerroot%/import
Step 2 Step 3 Step 4 Step 5 Step 6
You can import the file or download the file using the File Manager utility.
Step 7 Step 8
Modify the converted csv file as needed. For example, add the ERL name, route pattern, and security details to update the ERL. Click Close to close the window.
Related Topics

Import ERL Data, page A-21 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
Configuring IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Cisco Emergency Responder (Cisco ER) 2.0 supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco ER then routes the emergency calls based on the configured IP subnet and ERL associations. This is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.
Note
Be aware that subnet-based tracking covers only to the IP subnet level, not to the cubicle level.
5-33
Use IP subnet-based ERLs to locate and track 802.11b endpoints, such as Cisco Unified Wireless IP Phone 7920 devices and Cisco IP SoftPhones running on 802.11b. Cisco ER cannot locate or track 802.11b wireless endpoints to a Cisco Access Point. It is recommended that:

You configure a subnet-ERL for each access point. You identify the switch port to which the access point is connected and you assign the 802.11b wireless endpoint to the subnet ERL that is configured for that access point.
Before You Begin
You must have system administrator or ERL administrator authority to access this page. To configure IP subnet-based ERLs, follow these steps:
Procedure
Step 1
Select ERL Membership > IP Subnets and click the Add new IP Subnet link on the Find and List IP Subnets page. Cisco ER opens the Configure IP Subnets page. At the Subnet ID field, enter the IP address of the subnet you want to define, for example,10.76.35.0. At the Subnet Mask field, enter the mask of the subnet you want to define, for example, 255.255.255.224. To select the ERL you want to assign to the subnet, click the Search ERL button next to the ERL Name field. The Find ERL page appears. Enter the ERL Search Parameters and click Find. The search results appear. Click the radio button next to the ERL you want to assign to the subnet and click Select ERL. The Find ERL page closes. On the Configure IP Subnet page, click Insert to add the subnet. A popup message requests that you force a switch port update. You can do this after all the IP subnets have been added.
Step 8 Step 9
To change the fields on this page back to the last saved settings, click Cancel Changes. To return to the Find and List IP Subnets page, click Back to IP Subnet Search.
Related Topics

Find and List Synthetic Phones, page A-45 Add New Synthetic Phone, page A-45
Configuring Test ERLs

You can use Cisco Unified Operations Manager 2.01 to monitor the health and functionality of Cisco ER. To use Cisco Unified Operations Manager with Cisco ER, you configure a test ERL, then add a synthetic phone and associate the synthetic phone to the test ERL. When a synthetic phone makes an emergency call, Cisco ER uses the associated test ERL to route the call.
Note
You can configure test ERLs only to synthetic phones.
5-34
OL-12376-01
Chapter 5
All synthetic phones used for Cisco ER testing must belong to one of the configured test ERLs. For phones used for test ERLs, you enter the MAC address or address range allotted for synthetic phones. The following conditions apply to test ERLS:

Calls from synthetic phones will not be logged in Call History logs. Web alerts will not be generated for emergency calls from synthetic phones. Email alerts will not be generated for emergency calls from synthetic phones. PS-ALI records for test ERLS will not be exported in NENA export files.
Tip
You do not need to enter ALI data for test ERLs. Non-test ERLs must contain ALI data.
Before You Begin
You must have system administrator or ERL administrator authority to reach this page. To configure test ERLs, follow these steps:
Procedure
Select ERL > ERL Details and click Add New ERL on the ERL Configuration page. At the ERL field, enter a name for the test ERL. At the Test ERL field, check the box to select it.
Note
This setting is not available on the ERL Information for Default; default ERLs may not be used as test ERLs.
Note
Do not click ALI Details to enter ALI data. You do not need to enter ALI data for test ERLs; only non-test ERLs must contain ALI data.
Click Insert to save the test ERL and click Close to close the window. Select ERL Membership > Synthetic Phones and click Add New Synthetic phone on the Find and List Synthetic Phones page. At the MAC Address field, enter the MAC address or the range of MAC addresses allotted for synthetic phone. Enter the MAC address in this format: xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx The synthetic MAC address must be within the following range: 00059a3b7700 - 0059a3b8aff At the ERL Name field, enter the test ERL that you want to assign to the synthetic phone. Select the configured test ERL from the drop-down list or type in a valid test ERL name. Click Insert to add the phone to the list of defined synthetic phones.
Step 7 Step 8
5-35
Step 9
To change the fields on this page back to the last saved settings, click Cancel Changes.
Related Topics

Find and List Synthetic Phones, page A-45 Add New Synthetic Phone, page A-45
Exporting ERL Information

Use the Export ERL page to create ERL export files for your own use, for example, to back up or move an ERL configuration. Do not submit ERL export files to your service providerthey are not exported in a format your service provider can use. For information on exporting ALI information, refer to the Exporting ALI Information for Submission to Your Service Provider section on page 5-37. For information on how to reformat ALI data to be accepted by the ERL, see the Exporting ALI Information for Submission to Your Service Provider section on page 5-37.
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority. To export ERL information, follow these steps:
Procedure
Step 1
Select ERL > ERL Details. Cisco ER opens the Find and List ERLs page.
Step 2
Click Export ERL Data at the top of the window. Cisco ER opens the Export ER Data window. Select the Export Format (csv or xml) from the pulldown menu. Enter the name of the file to be exported in the Enter Export File Name field. Click Export. Cisco ER creates the export file, and tells you the location where the file was created and how many records were exported.
Step 6 Step 7
Select the exported file from the pulldown menu and click Download to download it to your local machine. Click Close to close the Export ERL Data window.
Related Topics

Export ERL Data, page A-21 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
5-36
OL-12376-01
Chapter 5
Exporting ALI Information for Submission to Your Service Provider

Your service provider and their database provider need your automatic location information (ALI) so that emergency calls from your ERLs can be routed to the correct public safety answering point (PSAP). The PSAP can also use this information to dispatch emergency response teams (such as police, fire, medical) to deal with the emergency. As you create and update your ERLs and their ALIs, make sure that you export the data and send it to your service provider or the database provider they identify. See the Using the ALI Formatting Tool chapter for information on sending ALI details to your service provider.
Before You Begin
You must log into Cisco Emergency Responder (Cisco ER) with system administrator or ERL administrator authority.
Caution
Ensure that you submit each ALI export file as you create it. The ALI export records include an indication that the record is either new or modified. If you do not submit an ALI export file, the subsequent file you submit might have incorrect status indications, which can result in your service provider rejecting some, or possibly all, of your submitted records. To export ALI information for submission to your service provider, follow these steps:
Procedure
Step 1
Select Tools > Export PS-ALI Records. Cisco ER opens the Export PS-ALI Records page. At the Select the NENA Format field, choose the format required by your service provider from the drop-down list. At the File to Export field, enter the name of the file to export. At the Company Name field, enter your company name. Cisco ER automatically increments the Cycle Counter each time you export data. You do not need to change this counter unless you are redoing or correcting a previous exportation. However, changing the sequence number does not affect the data placed in the fileif you are redoing an export, you will have to manually edit the export file to change the record status fields. Click Export. Cisco ER creates the export file and tells you how many records were exported. Click Download to download the file to your local machine. Click Close to close the Export ALI Records window. Use your service providers method of transmitting the file to the service provider.
Step 6
5-37
Related Topics

ALI Information (for ERL Name), page A-17 Export ERL Data, page A-21 Export PS-ALI Records, page A-56 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
Viewing the Audit Trail for an ERL

You can view the audit trail for an ERL to determine how, when, and by whom an ERL was created or changed.
Before You Begin
You must have system administrator, ERL administrator, or network administrator authority to view the audit trail. To view the audit trail for an ERL, follow these steps:
Procedure
Step 1
Select Reports > ERL Audit Trail. Cisco Emergency Responder (Cisco ER) opens the ERL Audit Trail page. Enter search criteria to select the ERLs whose audit history you want to view. To view all ERLs, click Find without entering any criteria. To narrow your search:
a. b.
Step 2
Select the field you want to search on, select the search relationship, and enter the search string. For some fields, you can select valid strings from the right-most drop-down list. To search on a combination of fields, click More to add additional search fields. Select Any at the top of the list to indicate that ERLs that match any search criteria be selected (an OR search); select All to indicate that only ERLs that match every criteria be selected (an AND search). Click Find when you have entered all of the search criteria. Cisco ER lists the matching audit records. If there are a lot of matches, Cisco ER uses several pages to display them. Use the links at the bottom of the list to change pages.
c.
Tip
To view the audit trail of a specific ERL, click View in the Audit Trail column in a list of ERLs shown on the Find and List ERLs page.
Related Topics

ERL Audit Trail, page A-55 Working with Emergency Response Locations, page 5-24
5-38
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Configuring Switches for Cisco Emergency Responder
Configuring Switches for Cisco Emergency Responder

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Cisco Emergency Responder (Cisco ER). These topics describe the switch requirements and how to identify switches to Cisco ER.

Understanding Switch Requirements for Cisco Emergency Responder, page 5-39 Configuring the SNMP Connection, page 5-39 Defining the Phone Tracking and Switch Update Schedules, page 5-41 Identifying the LAN Switches, page 5-42 Manually Running the Switch-Port and Phone Update Process, page 5-45
Understanding Switch Requirements for Cisco Emergency Responder

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. Ensure that the switches to which phones are attached are supported by Cisco ER, and that the switches are running the required software version. The Network Hardware and Software Requirements section on page 1-4 lists the supported switches and software versions. If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Cisco ER cannot work with a switch unless the switch has an IP address.
Related Topics

Configuring the SNMP Connection, page 5-39 Defining the Phone Tracking and Switch Update Schedules, page 5-41 Identifying the LAN Switches, page 5-42 Manually Running the Switch-Port and Phone Update Process, page 5-45
Configuring the SNMP Connection

Cisco Emergency Responder (Cisco ER) uses SNMP to obtain information about the ports on a switch. Cisco ER must obtain this port information so that you can assign the ports to ERLs, and so that Cisco ER can identify phones that are attached to the ports and update their ERL assignments. Cisco ER only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.
Before You Begin
You must have system administrator or network administrator authority to define the SNMP settings. Obtain the read community strings from all of the switches you will define in Cisco ER. If you use different strings for different sets of switches, see if you can define an IP address pattern for these sets. For example, if you use the same string for all switches that begin with 10.1, and another string for switches that begin with 10.2, you can use the patterns 10.1.*.* and 10.2.*.*.
5-39
Chapter 5 Configuring Switches for Cisco Emergency Responder
If two or more patterns match an IP address, Cisco ER uses the SNMP string associated with the most closely matching pattern. For example, if you define *.*.*.* and 10.1.*.*, and the IP address is 10.1.12.24, Cisco ER uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection. When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Cisco Unified Communications Manager servers. Cisco ER must be able to make SNMP queries of all Cisco Unified Communications Manager servers in the cluster that it supports. To configure the SNMP connection, follow these steps:
Procedure
Step 1
Select Phone Tracking > SNMP Settings. Cisco ER opens the SNMP Settings page. Enter an IP address pattern to which you want to associate an SNMP read community string. Use the asterisk (*) as a wildcard character. You can also use number ranges for octets, such as 15-30. Because Cisco ER only tries to contact the switches you identify on the LAN Switch Details page (see the Identifying the LAN Switches section on page 5-42 for more information), it does not matter if the IP address patterns cover devices other than switches.

Step 2
If all of your switches use the same read community string, enter *.*.*.*. You will only need to create one entry. If subsets of your switches use the same strings, create a mask that covers those subsets, if possible. For simplicity, try to create the fewest number of patterns. If you use a separate string for each switch, you must enter each switch on this page.
Step 3
Enter the timeout and retries values. These values work together to determine how often and how long Cisco ER tries to obtain SNMP information from a switch before giving up. The first attempt lasts as long as the timeout value. If you enter 1 or higher for retries, Cisco ER tries again, and each retry lasts twice as long as the previous try. For example, if you specify 10 for timeout, the first retry lasts for 20 seconds, the second retry lasts for 40 seconds, and so forth. The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries. Enter the read community string, for example, public. Click Insert. Cisco ER adds the SNMP setting to the list of settings. If you need to create more than one setting, return to Step 2.
Step 4 Step 5
Step 6
5-40
OL-12376-01
Chapter 5
Tip
Whenever you change the SNMP read community string on a switch, you must update the associated setting in Cisco ER. To change an SNMP setting, select it in the list. Cisco ER loads the setting in the edit boxes. Make your changes and click Update. Then, run the switch-port and phone update process on the switch after you update the SNMP setting. Select Phone Tracking > LAN Switch Details, select the switch in the LAN Switches list, and then click Locate Switch Ports. If you are changing the setting for a large number of switches, run the process on all switches by selecting Phone Tracking > Run Switch-Port & Phone Update. To delete a setting, click the delete icon on the settings entry.
Related Topics

SNMP Settings, page A-22 Identifying the LAN Switches, page 5-42
Defining the Phone Tracking and Switch Update Schedules

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 TrackingA 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 phones ERL. Phones that cannot be located are classified as unlocated phones (see the Identifying Unlocated Phones section on page 5-52).
Note
If you do not configure a switch port phone update schedule, the default schedule will run at midnight. Switch-Port and Phone UpdateThe 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.
Before You Begin
You must have system administrator or network administrator authority to define the schedule. To define the phone tracking and switch update schedules, follow these steps:
Procedure
Step 1
Select Phone Tracking > Schedule. Cisco ER opens the Schedule page. Enter the incremental phone tracking schedule in minutes and click Update. Cisco ER will run the phone tracking process this number of minutes after finishing the previous phone tracking process.
Step 2
5-41
Step 3
Enter the schedule for the switch-port and phone update process. You should run this process at least once per day (but not more than four times per day). For example, if you want to run the process at midnight Monday through Friday, but at 6 PM on Saturday and Sunday, create two schedule entries:

Select Mon, Tue, Wed, Thu, and Fri, and 00 for Hour, 00 for Minute, then click Insert. Cisco ER adds the schedule to the list. Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Cisco ER adds the schedule to the list.
If you define schedules that overlap, Cisco ER only runs one process.
Tip
To change a switch-port and phone update schedule, click the schedule in the list. Cisco ER loads the schedules settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedules list entry.
Related Topics

Phone Tracking Schedule, page A-24 Manually Running the Switch-Port and Phone Update Process, page 5-45
Identifying the LAN Switches

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. Because Cisco ER must obtain information from the switches, you must ensure that the information you supply to Cisco ER is correct and kept up-to-date. After you have created the initial switch list, you can make mass changes to switch definitions by exporting the switch definitions, editing the export file, and reimporting the file. These topics describe how to identify switches to Cisco ER, and how to export switch information:

Identifying LAN Switches One At a Time, page 5-42 Importing a Group of Switches, page 5-44 Exporting Switch Information, page 5-45
Identifying LAN Switches One At a Time

You can enter switches into the Cisco Emergency Responder (Cisco ER) configuration one at a time. If you have a large number of switches to add, consider creating an import file to add them instead of using this procedure. See the Importing a Group of Switches section on page 5-44 for more information.
Before You Begin
You must have system administrator or network administrator authority to add, remove, or change switch definitions.
5-42
OL-12376-01
Chapter 5
Determine if your network includes phones that do not use the Cisco Discovery Protocol (CDP) to announce themselves to the network. For non-CDP phones, Cisco ER must use the CAM information on the switch to identify phones. See the Network Hardware and Software Requirements section on page 1-4 for information on which phones require CAM access. Ensure that you configure the SNMP read community strings before adding switches. See the Configuring the SNMP Connection section on page 5-39 for more information. To identify LAN switches one at a time, follow these steps:
Procedure
Step 1
Select Phone Tracking > LAN Switch Details. Cisco ER opens the LAN Switch Details page. Enter information about the switch:

Step 2
Enter the IP address or DNS name of the switch. If there might be non-CDP-enabled phones attached to the switch, select Enable CAM-based Phone Tracking.
Step 3
Click Insert to add the switch to the Cisco ER configuration. Cisco ER asks if you want to run the switch-port and phone update process. You must run this process so that Cisco ER can identify the ports on the switch and so that your ERL administrator can then assign the ports to the right ERLs. If you are adding more than one switch, you can skip running the process until you add the last switch. When you select to run the process, Cisco ER runs the process on all switches added since the last time the switch-port and phone update process was run. If you do not choose to run the process, you can run it later by selecting Phone Tracking > Run Switch-Port & Phone Update. In either case, newly discovered ports are assigned to the Default ERL.
Tip
Click a switch in the LAN Switches list to view the switchs Cisco ER configuration. To change the configuration, make your changes and click Update. Click Add LAN Switch to add another switch if you are viewing an existing switchs configuration. To delete a switch, select it from the LAN Switches list and click Delete. If you do not remove the switch from the network, Cisco ER will identify any phones connected to the switch as unlocated phones.
Related Topics

Importing a Group of Switches, page 5-44 Exporting Switch Information, page 5-45 LAN Switch Details, page A-28 Understanding Switch Requirements for Cisco Emergency Responder, page 5-39
5-43
Importing a Group of Switches

You can define a large number of switches at one time by importing a file that contains the required switch information. You might be able to create this file by exporting switch information from your network management software, and then using a spreadsheet program to modify the records to match the Cisco Emergency Responder (Cisco ER) file format requirements (that is, by deleting columns, adding columns, rearranging columns, and so forth). If you have a large network, importing switch definitions can save you a lot of time.
Before You Begin
You must have system administrator or network administrator authority to import switch definitions. Prepare an import file. Cisco ER includes detailed information about the required file format on the Import LAN Switch page. The page also includes the location in which you must place the file in order to import it. Use the procedure below to go to the page and view the format, create your file, copy the file to the required location, and then follow the procedure to import the file. Ensure that you configure the SNMP read community strings before adding switches. See the Configuring the SNMP Connection section on page 5-39 for more information. To import a group of switches, follow these steps:
Procedure
Step 1
Select Phone Tracking > LAN Switch Details. Cisco ER opens the LAN Switch Details page. Click Import in the left-hand switch list. Cisco ER opens the Import LAN Switch page. Select the file format, and the name of the file you want to import. Then, select one of these:
Step 2
Step 3
Override with imported dataTrust the data in the import file, and use it to overwrite conflicting data in the Cisco ER configuration. This is valuable if you are importing a file that you exported from Cisco ER and then updated. Using this technique, you can update many entries at once. Leave current dataTrust the Cisco ER configuration, and do not overwrite configuration data with conflicting data from the import file. This is the default.
Step 4
Click Import. Cisco ER asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Cisco ER imports the switches but does not run the phone tracking process. After you make your selection, Cisco ER adds the switch configurations and shows you the status of the import.
Step 5 Step 6
Click Close to close the window. If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update. Cisco ER contacts each switch to discover the ports on the switch and any phones attached to the ports. Alternatively, you can view each switchs configuration on the LAN Switch Details page and click Locate Switch Ports. This runs the process only on the selected switch.
5-44
OL-12376-01
Chapter 5
Related Topics

Identifying LAN Switches One At a Time, page 5-42 Exporting Switch Information, page 5-45 LAN Switch Details, page A-28 Understanding Switch Requirements for Cisco Emergency Responder, page 5-39
Exporting Switch Information

You can export your Cisco Emergency Responder (Cisco ER) configuration. This can help you back up your data, or help you create a file you can use to update a large number of switch definitions in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.
Before You Begin
You must have system administrator or network administrator authority to export switch definitions. To export switch information, follow these steps:
Procedure
Step 1
Select Phone Tracking > LAN Switch Details. Cisco ER opens the LAN Switch Details page. Click Export in the switch list. Cisco ER opens the Export LAN Switch page. Select the file type and enter the file name for the export file. Do not include a file extension. Click Export. Cisco ER creates the export file. Click Close to close the window.
Step 2
Step 3 Step 4
Related Topics

Identifying LAN Switches One At a Time, page 5-42 Importing a Group of Switches, page 5-44 LAN Switch Details, page A-28 Understanding Switch Requirements for Cisco Emergency Responder, page 5-39
Manually Running the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Cisco Emergency Responder (Cisco ER) must identify the ports on the switch using the switch-port and phone update process. Although Cisco ER runs this process according to the schedule you set (see the Defining the Phone Tracking and Switch Update Schedules section on page 5-41 for more information), you might want to run it manually when you make a lot of changes to the switch configuration without running phone tracking on individual switches.
5-45
Because the switch-port and phone update process does extensive checking, only run it if you are trying to refresh the entire Cisco ER-tracking results. Alternatively, if you are only trying to update the results for a limited number of switches, you can run phone tracking on individual switches. Select Phone Tracking > LAN Switch Details and select the switch in the left-hand column; then click Locate Switch Ports. These are some reasons you would run phone tracking on an individual switch:
You add a switch to Cisco ER. When you add a switch, Cisco ER asks if you want to run the process. If you select to run it at that time, you do not have to click Locate Switch PortsCisco ER runs the process for all switches you added to the Cisco ER configuration since the last time the full switch-port and phone update process was run. You add, remove, or change a module in a switch already defined to Cisco ER. You can add and delete IP subnet-based ERLs.
Manually run the switch-port and phone update process as described below if:

You want to refresh the Cisco ER-tracking results. You add switches to Cisco ER by importing switch definitions, as described in the Importing a Group of Switches section on page 5-44, but you did not run phone tracking during the importation. If you find a large number of entries in the unlocated phones list (see the Identifying Unlocated Phones section on page 5-52), run this process to see if Cisco ER can find some of those phones. See the Too Many Unlocated Phones section on page 11-2 for issues you should address to help resolve these problems before running the switch-port and phone update process.
Before You Begin
You must have system administrator or network administrator authority to manually run the switch-port and phone update process. To manually run the switch-port and phone update process, follow these steps:
Procedure
Step 1
Select Phone Tracking > Run Switch-Port & Phone Update. Cisco ER runs the process without changing the page you are viewing. Any newly-discovered ports are assigned to the Default ERL.
Related Topics

Defining the Phone Tracking and Switch Update Schedules, page 5-41 Identifying Unlocated Phones, page 5-52 Understanding Switch Requirements for Cisco Emergency Responder, page 5-39
5-46
OL-12376-01
Chapter 5
Configuring Cisco Emergency Responder 2.0 Managing Phones
Managing Phones
These topics describe how to assign switch ports and phones to the appropriate emergency response locations (ERLs), and how to view the history of emergency calls handled by Cisco Emergency Responder (Cisco ER):

Configuring Switch Ports, page 5-47 Identifying Unlocated Phones, page 5-52 Manually Defining a Phone, page 5-53 Viewing the Emergency Call History, page 5-57
Configuring Switch 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. For example, your wiring closet is on Floor 1. Half of its ports serve Floor 1, the other half serve Floor 2. Also, you have defined two ERLs, Floor1 and Floor2. Although the switch is on Floor 1, only half its ports belong in the Floor1 ERL; the other half belong in the Floor2 ERL. Before you assign ports to ERLs, ensure you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments will only be reliable if this map is kept static, that is, so long as wires are not indiscriminately moved from port to port on the switch. Work with your network administrator to ensure the integrity of the wiring closet. See the Data Integrity and Reliability Considerations section on page 1-16 for more information. These topics describe how to assign switch ports to ERLs:

Configuring a Few Switch Ports at a Time, page 5-47 Configuring a Large Number of Ports at Once, page 5-49 Exporting Switch Port Information, page 5-50 Switch-port Change Reporting for Wired Cisco Unified IP Phones, page 5-50
Configuring a Few Switch Ports at a Time

You can assign switch ports to ERLs a few at a time. If you have a large number of ports to map, it is much easier to create an import file to add them instead of using this procedure. See the Configuring a Large Number of Ports at Once section on page 5-49 for more information.
Before You Begin
You must have system administrator or ERL administrator authority to assign ports to ERLs. You can only configure ports defined for the Cisco Emergency Responder (Cisco ER) group to which you are logged in.
5-47
Chapter 5 Managing Phones
To configure a few switch ports at a time, follow these steps:

Procedure
Step 1
Select ERL Membership > Switch Ports . Cisco ER opens the Switch Port Details page. This page has two tabs, Find and Configure. Before you can configure a port, you must list it in the bottom frame using the Find tab.
Step 2
On the Find tab, enter search criteria to list the ports you want to configure.

Find will display a maximum of 1,000 records. Refine your search accordingly. If you want to list all ports on a specific switch, select Switch IP Address or Switch Host Name, enter the IP address or host name, and click Find. Cisco ER lists all ports discovered on the switch. If you want to narrow your search by using multiple criteria, click More to add search fields. Select Any at the top of the list to indicate that ports that match any search criteria be selected (an OR search); select All to indicate that only ports that match every criteria be selected (an AND search). For all searches, select the Cisco ER group you want to search. If your initial search does not list the ports you are looking for, it might be because the ports are managed by a different Cisco ER group. You can only search one Cisco ER group at a time.
Step 3
Click Configure. Cisco ER opens the Configure tab.
Step 4
Assign ports to ERLs:

a.
In the list of ports in the bottom frame, select the ports you want to assign to a single ERL. If you want to assign all listed ports, select the check box in the title row. You can only assign ports on one page at a time, so if there is more than one page of ports in the listing, complete this task for each page separately. Select the ERL you want to assign to the ports. Optionally, enter more specific location information in the Phone Location field. Click view to open a window so that you can enter information. For example, you could enter the cubical or office number that the port serves. This information is sent to the onsite alert (security) personnel to help them locate the emergency caller. You can only update the phone location information if you are logged into the primary Cisco ER server in the Cisco ER group. Click Configure Ports. Cisco ER assigns the ERL to the selected ports. You can continue assigning ports on this page of the ports list, but do not change the search results page before completing these steps.
b. c.
d.
e.
Click OK when you are finished configuring ports on the displayed list. Cisco ER commits your ERL assignments. From here, you can continue to the another page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.
Tip
Click Edit Table View to change the fields and arrangement of fields in the port list. The phone location information is saved on the primary Cisco ER server. Back up this data regularly. See the Backing Up and Recovering Data section on page 11-31.
5-48
OL-12376-01
Chapter 5
Related Topics

Switch Port Details, page A-31 Import Switch Ports, page A-34 Configuring a Large Number of Ports at Once, page 5-49 Exporting Switch Port Information, page 5-50 Working with Emergency Response Locations, page 5-24
Configuring a Large Number of Ports at Once

You can assign a large number of ports to ERLs at one time by importing a file that contains the required information. If you have a large network, importing port-to-ERL mappings can save you a lot of time.
Before You Begin
You must have system administrator or ERL administrator authority to import switch port definitions. Prepare an import file. The easiest way to create this file is to first export the switch port details from Cisco ER (see the Exporting Switch Port Information section on page 5-50), and then use a spreadsheet program to change the ERL to the desired ERL and add phone location information. Ensure that the switch-port and phone update process is run before creating the export file, so that the file includes records for every switch port. Before you import the file, you must copy it to the location identified on the Import Switch Port page. The procedure below explains how to get to this page. Links on the page also will display the detailed information about the required file format for the import file if you need it. Cisco ER must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Cisco ER. You can only configure ports defined for the Cisco ER group to which you are logged in. To configure a large number of ports at once, follow these steps:
Procedure
Step 1
Select ERL Membership > Switch Ports . Cisco ER opens the Switch Port Details page. Click Import. Cisco ER opens the Import Switch Ports page. Select the format of your import file (csv) from the pulldown menu. Click Upload to upload the file from your local machine. See the Uploading a File section on page 5-6 for information on using the Upload utility. Select your import file using the Select File to Import pulldown menu. Click Import. Cisco ER imports the file and shows you the import results. The ERL-to-port mappings and port location information in the import file overwrite any existing data in the Cisco ER configuration.
Step 2
Step 7
Click Close to close the Import Switch Port page.
5-49
Related Topics

Switch Port Details, page A-31 Export Switch Ports, page A-33 Configuring a Few Switch Ports at a Time, page 5-47 Exporting Switch Port Information, page 5-50 Working with Emergency Response Locations, page 5-24
Exporting Switch Port Information

You can export your Cisco Emergency Responder (Cisco ER) port configuration. This can help you back up your data, or help you create a file you can use to update a large number of switch port mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.
Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions. To export switch port information, follow these steps:
Procedure
Step 1
Select ERL Membership > Switch Ports . Cisco ER opens the Switch Port Details page.
Step 2
Click Export. Cisco ER opens the Export Switch Ports page. Select the file format and enter the desired file name, and click Export. Cisco ER exports the file to the export location. To download the exported file to your local system, select the file name from the Select file to download pulldown menu and click Download. Click Close to close the Export Switch Port page.
Step 3
Step 4 Step 5
Related Topics

Switch Port Details, page A-31 Configuring a Few Switch Ports at a Time, page 5-47 Configuring a Large Number of Ports at Once, page 5-49 Working with Emergency Response Locations, page 5-24
Switch-port Change Reporting for Wired Cisco Unified IP Phones

Cisco ER detects changes in the switch-port association of wired Cisco Unified IP Phones. An incremental or full discovery cycle detects Cisco Unified IP Phones that have changed switch-port associations or are newly discovered. Cisco Unified IP Phones that become missing during a complete discovery are also reported. Cisco ER notifies the system administrator of these changes by email.
5-50
OL-12376-01
Chapter 5
Note
A missing Cisco Unified IP Phone is one that is registered in Cisco Unified Communications Manager but is not found behind a switch port of any switch tracked by Cisco ER. Cisco Unified IP Phones that appear on the Unlocated Phones page in Cisco ER Administration web interface are also included in the missing list. Switch-port Change Reporting reports the location changes for Cisco Unified IP Communicator when it is connected to a switch that is tracked by Cisco ER. The change notification email contains the following information:

The time at which the change was detected. This is the approximate completion time of the discovery cycle that detected the change. The previous switch IP and port number of the Cisco Unified IP Phone. If the Cisco Unified IP Phone is new, this field is blank. The current switch IP and port number of the Cisco Unified IP Phone. If the Cisco Unified IP Phone is missing, this field is blank. The details of the Cisco Unified IP Phone, including the MAC address, device name, Phone Type, IP address and IP phone extension(s).
Note
Configure the email client settings to allow line breaks in the email to improve readability. For more information on configuring the email client, see the Configuring a Cisco Emergency Responder Server Group section on page 5-16. Supported Cisco Unified IP PhonesThis feature supports only wired Cisco Unified IP Phones that meet both of these conditions:

Wired Cisco Unified IP Phones discovered behind a LAN switch port using Cisco Discovery Protocol (CDP) tracking or Content-Addressable Memory (CAM) tracking. Wired Cisco Unified IP Phones actively registered in Cisco Unified Communications Manager. The only exception for this rule is Cisco Unified IP Phones previously registered in Cisco Unified Communications Manager. These Cisco Unified IP Phones are reported as missing.
Cluster ScenarioThe active server in each server group within a cluster sends separate notifications for the Cisco Unified IP Phones it discovers and tracks. Server Group ScenarioWithin a server group, Cisco ER performs change detection and notification on the active Cisco ER server only. Feature ActivationThe change detection and notification feature requires manual activation. To activate the feature change detection and notification, follow these steps:
Procedure
Step 1
Select System > Mail Alert Configurations. The Email Alert Settings page appears.
Step 2 Step 3
In the Misc parameters section, use the pulldown menu to set the Switch Port location change reporting parameter to True. Click Update Settings.
5-51
Change Notification conditionsCisco ER sends change notification email when a full discovery cycle completes under any of these circumstances:

During a normally scheduled discovery. After a manual start from the Cisco ER Administrator web interface. As a result of a Cisco Unified Communications Manager addition from the web interface by the system administrator.
Similarly, a partial discovery cycle sends email notifications under these circumstances:

During a normally scheduled discovery. As a result of a LAN switch addition to Cisco ER; the system administrator starts the discovery process. As a result of the system administrator selecting the Locate Switch Ports button on the LAN switch details page.
Note
An incremental discovery does not locate missing Cisco Unified IP Phones from Cisco Unified Communications Manager if no phone registrations take place during the discovery cycle. A full discovery detects all missing Cisco Unified IP Phones that are located since the previous full discovery. The following events do not result in a change notification:

When the CERServer starts following the first discovery cycle. When a Publisher returns to an online state following the first discovery cycle. When no phone location changes occur following a discovery cycle.
Identifying Unlocated Phones

If Cisco Emergency Responder (Cisco ER) cannot locate a phone, it places the phone in the Default ERL and puts it in a list of unlocated phones. Using this list, you can reassign the phones to a different ERL, or you can use the list to help identify the problems that are preventing Cisco ER from locating the phones. These are some things that can prevent Cisco ER from locating a phone:

The phone is attached to a switch that is not defined in Cisco ER. The phone is connected to an unsupported device, such as a router port, a hub connected to a router, or an unsupported switch. The switch to which the phone is connected is currently unreachable, for example, it does not respond to SNMP queries. The phone has moved to a switch served by a different Cisco ER group. If this is the case, the Cisco ER group name is shown for the phone in the unlocated phones list. No IP subnet is configured for the phone.
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 can manually assign a phone to an ERL. See the Too Many Unlocated Phones section on page 11-2 for more detailed information on resolving these problems.
5-52
OL-12376-01
Chapter 5
Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones. To identify unlocated phones, follow these steps:
Procedure
Step 1
Select ERL Membership > Unlocated Phones. Cisco ER opens the Unlocated Phones page and lists all unlocated phones. To assign a phone to an ERL, select or enter the ERL, select the phone, and click Assign to ERL. Cisco ER assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Cisco ER from locating this phone, Cisco ER removes it from the list and assigns it the correct ERL based on port assignment.
Step 2
Tip
You can select all the phones on the displayed page by selecting the check box in the list title. You can only assign phones to ERLs on a single page at a time. If there is more than one page of phones, use the links at the bottom of the list to move from page to page.
Note
Cisco ER does not automatically discover analog phones or phones connected to PBXs. As a result, these phones do not appear on the Unlocated Phones list. These phones need to be manually configured. See the Manually Defining a Phone section on page 5-53 for more information.
Related Topics

IP Subnet Phones, page A-37 Configuring Switch Ports, page 5-47 Manually Defining a Phone, page 5-53
Manually Defining a Phone

To manage all emergency calls in your network, Cisco Emergency Responder (Cisco ER) must know about every phone whose calls are routed by Cisco Unified Communications Manager, even if Cisco ER does not directly support the phone. Cisco ER handles emergency calls from these manually-defined phones in the same way it handles calls from phones attached to supported switch ports. The only difference is that Cisco ER cannot dynamically change the ERL of a manually-defined phone if that phone is moved. You need to manually define a phone if any of these conditions apply:

Cisco ER does not support automatic tracking of that type of phone, for example, if the phone is analog. The phone is hosted on an unsupported port, such as a router port, a hub connected to a router, or a port on an unsupported switch.
5-53
No IP subnet is configured for the phone.
For any phones you must manually define, you should regularly audit the location of those phones to determine if you need to update the ERL assignment for the phone in Cisco ER.
Note
New switch ports and unlocated phones will NOT be associated to Default ERLs automatically. They will be treated as ERL not configured. The Default ERL is used only internally by Cisco ER if no other ERL is configured for that phone. Cisco ER will not allow the Default ERL to be configured to Switch Ports; Unlocated Phones; Manually Configured Phones; or IP Subnets.
Note
You cannot manually add a phone that is used with Cisco Unified Communications Manager Extension Mobility. With Cisco Unified Communications Manager Extension Mobility, a user can log into a phone and the phone is assigned the users extension. However, with manually-defined phones, you are defining the phone based on extension, not on device, so the extension of the logged-in person does not get assigned the appropriate ERL. Ensure that all phones used with Cisco Unified Communications Manager Extension Mobility are connected to supported switch ports.
Before You Begin
You must have system administrator or ERL administrator authority to manually define phones. To define a phone manually, follow these steps:
Procedure
Step 1
Select ERL Membership > Manually Configured Phones . Cisco ER opens a new page, the Find and List Manually Configured Phones page. To search for phones that you need to modify, enter the extension and click Find. Cisco ER performs a search and displays the results of your search. From the search result on the Find and List Manually Configured Phones page, you can remove a phone, change an existing phone or add a new phone:
Step 2
Step 3 Step 4
To remove a phone, click the delete icon on the phones entry. To change an existing phone:
a. b. c.
Click the phones entry in the list. Cisco ER opens the Add/Modify Phones page with the phones information displayed in the edit boxes. Make your changes and click Update. Cisco ER updates the phone. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.
Step 5
To add a new phone:

a. b.
Click Add a new phone. Cisco ER opens the Add/Modify Phones page. Enter information about the phone you want to define. You must enter the phones extension and select an ERL. If the phone is an IP phone, you must also enter the IP address and MAC address for the phone. Other fields are optional and are mainly for your information. Click Insert. Cisco ER adds the phone to the list of manually defined phones. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.
c. d.
5-54
OL-12376-01
Chapter 5
Related Topics

Add New Manual Phone, page A-42 Identifying Unlocated Phones, page 5-52 Network Hardware and Software Requirements, page 1-4 Assigning a Large Number of Manually Configured Phones to ERLs at Once, page 5-55 Exporting Manually Configured Phone Information, page 5-56
Assigning a Large Number of Manually Configured Phones to ERLs at Once

You can assign a large number of manually configured phones to ERLs at one time by importing a file that contains the required information. If you have a large network, importing manually-configured phone to ERL mappings can save you a lot of time.
Before You Begin
You must have system administrator or ERL administrator authority to import switch port definitions. Prepare an import file. The easiest way to create this file is to first export the manually configured phone details from Cisco ER (see the Exporting Manually Configured Phone Information section on page 5-56), and then use a spreadsheet program to change the ERL to the desired ERL and add phone location information. Ensure that the manual phone configuration and phone update process is run before creating the export file, so that the file includes records for every manually configured phone. Before you import the file, you must copy it to the location identified on the Import Manual Phones page. The procedure below explains how to get to this page. Links on the page also will display the detailed information about the required file format for the import file if you need it. Cisco ER must already be aware of the manually configured phones before you import the file. Ensure that all manually configured phones you are importing have been located by Cisco ER. You can only configure manually configured phones defined for the Cisco ER group to which you are logged in. To assign a large number of manually-configured phones to ERLs at one time, follow these steps:
Procedure
Step 1
Select ERL Membership > Manually Configured Phones. The Find and List Manually Configured Phones page appears. Click Import. The Import Manually Configured Phones page appears. Select the Import Format (csv) using the pulldown menu. Click Upload to upload the file from your local machine. See the Uploading a File section on page 5-6 for information on using the Upload utility. Select the import file using the Select File to Import pulldown menu. Click Import. Cisco ER imports the file and shows you the import results. The ERL-to-port mappings and the location information for manually configured phones in the import file overwrite any existing data in the Cisco ER configuration.
Step 2
5-55
Step 7
Click Close to close the Import Manually Configured Phone page.
Related Topics

Switch Port Details, page A-31 Export Switch Ports, page A-33 Configuring a Few Switch Ports at a Time, page 5-47 Exporting Switch Port Information, page 5-50 Working with Emergency Response Locations, page 5-24
Exporting Manually Configured Phone Information

You can export your Cisco Emergency Responder (Cisco ER) manually configured phone configuration. This can help you back up your data, or help you create a file you can use to update a large number of manually configured phone mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.
Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions. To export information about manually configured phones, follow these steps:
Procedure
Step 1
Select ERL Membership > Manually Configured Phones. Cisco ER opens the Find and List Manually Configured Phones page.
Step 2
Click Export. Cisco ER opens the Export Manual Phones page. Select the export format (csv) from the Select Export Format pulldown menu. Enter the desired file name in the Enter Export File Name field and click Export. Cisco ER exports the file to the export location. To download the exported file to your local system, select the file name from the Select file to download pulldown menu and click Download. Click Close to close the Export Manual Phones page.
Step 3 Step 4
Step 5 Step 6
Related Topics

Manually Defining a Phone, page 5-53 Assigning a Large Number of Manually Configured Phones to ERLs at Once, page 5-55 Working with Emergency Response Locations, page 5-24 Adding Synthetic Phones, page 5-57
5-56
OL-12376-01
Chapter 5
Adding Synthetic Phones

With Cisco Emergency Responder (Cisco ER) 2.0, you can use Cisco Unified Operations Manager 1.0 to monitor the health and functionality of Cisco ER. To use Cisco Unified Operations Manager with Cisco ER, you configure a synthetic phone in Cisco ER and associate the synthetic phone to an ERL that will be used as a test ERL. When a synthetic phone makes an emergency call, Cisco ER uses the associated test ERL to route the call. For more information, refer to the Configuring Test ERLs section on page 5-34.
Viewing the Emergency Call History

You can view the history of emergency calls made in your network that are handled by Cisco Emergency Responder (Cisco ER). Cisco ER sends emergency call notifications to the onsite alert personnel you identify in your ERLs, and these people react to the notifications. From the administrators interface, you can view the same call history your onsite alert personnel can view, and see the comments they make about the calls. You might need to review the call history to report on usage or to troubleshoot call routing problems.
Tip
From the Call History page, you can view detailed information on the 10,000 most recent calls. You can find records of older calls in Cisco ERs raw call log files. See the Collecting Call History Logs section on page 11-27 for more information. To view the emergency call history, follow these steps:
Procedure
Step 1
Select Reports > Call History. Cisco ER opens the Call History page. Click Find. All call summary information appears.
Step 2
Step 3
Enter the search criteria you want to use to create a list of emergency calls. To view a list of all calls, click Find without entering any search criteria. To narrow your search, select the item you on which you want to search, and click Find. For example, you can view calls that were made in a specific ERL, or calls that were made from a specific phone extension. If you want to search on more than one criteria, click More to add additional search fields. Then, select All at the top of the list to perform an AND search (a call only matches the search if each of the criteria is met), or Any for an OR search (a call matches the search if it matches one or more of the criteria).
5-57
Step 4
From the list of calls that Cisco ER shows you in response to your search criteria, you can:

View the call characteristics. Click on the ERL name to view the ERL details. From the ERL details, you can also view the ALI for the call. Click edit in the comment field to change the comment. Cisco ER opens a separate window where you make your editorial changes.
Tip
If a large number of calls match your search criteria, Cisco ER uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.
Related Topics
Collecting Call History Logs, page 11-27
5-58
OL-12376-01
C H A P T E R
Configuring Cisco Emergency Responder 2.0 Serviceability

Cisco Emergency Responder (Cisco ER) 2.0 includes a Serviceability interface that allows you to access the Cisco ER 2.0 Serviceability features. These features are grouped under four main menus on the Serviceability web interface: Tools, SNMP, System Monitor, and CER Logs. For details on all Serviceability web pages, see Appendix B, Serviceability Web Interface For Cisco Emergency Responder. These topics describe how to configure and use Cisco Emergency Responder (Cisco ER) 2.0 Serviceability features:

Using the Serviceability Tools, page 6-1 Configuring SNMP, page 6-3 Using the System Monitor Tools, page 6-6 Using Cisco Emergency Responder Logs, page 6-9
Using the Serviceability Tools

These topics describe the Cisco ER 2.0 Serviceability tools:

Using the Control Center, page 6-1 Using the Event Viewer, page 6-2
Using the Control Center

The Control Center allows you to perform actions on the services running on the selected Cisco ER 2.0 system. To perform actions on the services running on the selected Cisco ER 2.0 system, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select Tools > Control Center. The Control Center page appears.
6-1
Chapter 6 Using the Serviceability Tools
Step 2
To change the status of a service, click the radio button to the left of the Service Name and click the button corresponding to the desired action. Available actions are:

Start Stop Restart
Note
Cisco Tomcat and Cisco IDS services cannot be started, stopped, or restarted from the Cisco ER Serviceability website. These services can only be started, stopped, or restarted using the command line interface (CLI). See Appendix F, Command Line Interface for further information.
Step 3
Click Refresh to refresh the page.
Related Topics
Control Center, page B-1
Using the Event Viewer

The Event Viewer allows you to view events for the prior six months. To view events for the prior six months, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select Tools > Event Viewer. The Event Viewer page appears. To find all events that occurred over the prior six months, click Find without entering any search criteria. To find events that match specific criteria, enter search criteria:

Step 2
Select a specific month to view events from the month only. If you select Type, you can then select the type on which to search from the pulldown menu to the right. If you select Module, you can then select the module on which to search from the pulldown menu to the right.
Note
For a list of available Types and Modules, see the Event Viewer section on page B-2.
When you have entered your search criteria, click Find.

Step 3
You can perform an ascending or descending sort of the results. To perform a sort, click the up arrow or down arrow next to the Time, Type, or Module column headings.
Related Topics
Event Viewer, page B-2
6-2
OL-12376-01
Chapter 6
Configuring Cisco Emergency Responder 2.0 Serviceability Configuring SNMP
Configuring SNMP
Cisco ER 2.0 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. These topics describe how to configure SNMP V1/V2C and V3:

Configuring the SNMP Community String, page 6-3 Configuring the SNMP V1/V2C Notification String, page 6-4 Configuring SNMP Users, page 6-5 Configuring the SNMP V3 Notification Destination, page 6-5 Configuring MIB2, page 6-6
Configuring the SNMP Community String

By configuring SNMP, you can control SNMP access to the Cisco ER SNMP agent. A management station must first submit a valid community string for authentication. You configure a community string by entering the Community String Name, the IP addresses of host that can be authenticated using the community string, and the access privileges allowed. The available access privileges are as follows:

ReadOnly ReadWrite ReadWriteNotify NotifyOnly None
To configure the SNMP community string, follow these steps:

Procedure
Step 1
From the Cisco ER Serviceability web interface, select SNMP > V1/V2C Configuration > Community String. The SNMP Community String Configuration page appears.
Step 2 Step 3
In the Community String Name text box, enter the name of the community string. To specify specific hosts whose SNMP packets will be accepted, click the Accept SNMP Packets only from these hosts radio button, enter the IP addresses in the text box, and click Insert. To accept SNMP packets from any host, click the Accept SNMP Packets from any host radio button.
6-3
Chapter 6 Configuring SNMP
Step 4 Step 5
To remove an existing host, select the hosts IP address and click Remove. From the Access Privileges pulldown menu, select the access privilege for the host, then click Insert.
Related Topics
SNMP Community String Configuration, page B-4
Configuring the SNMP V1/V2C Notification String

Using the SNMP V1/V2C notification string, you can select the host and port destination to which SNMP V1/V2C trap messages are sent. Every notification string must authenticated. When using SNMP V1/V2C, authentication is done using the community string. To configure the SNMP V1/V2C notification string, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select SNMP > V1/V2C Configuration > Notification Destination. The SNMP Notification Destination Configuration page appears.
To add a new SNMP Notification Destination, click Add New. From the Host IP Addresses pulldown menu, select Add New. Additional fields appear. Enter the Host IP Address and Port Number in the text boxes. Click either the V1 or V2C radio button to select the SNMP version. If you click V1, the Community String pulldown menu appears. Proceed to Step 7. If you click V2C, the Notification Type pulldown menu appears. From the Notification Type pulldown menu, select Inform or Trap. The Community String pulldown menu appears. From the Community String pulldown menu, select the community string to use. Click Insert. You will see a message saying that the SNMP master agent needs to be restarted for the changes to take effect. Click OK to restart the SNMP master agent or Cancel to continue without restarting the master agent. The notification destination is added to the list of destinations on the SNMP Notification Destination Configuration page.
Step 9
To add additional notification destinations, repeat Step 2 through Step 8.
Related Topics
SNMP V1/V2c Notification Destination Configuration, page B-6
6-4
OL-12376-01
Chapter 6
Configuring Cisco Emergency Responder 2.0 Serviceability Configuring SNMP
Configuring SNMP Users

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 configure SNMP users, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select SNMP > V3 Configuration > User. The SNMP User Configuration page appears. To add a new SNMP User, click Add New. In the User Name text box, enter the name of the new user. To require authentication, click the Authentication Required checkbox, enter a password in the Password text box, reenter the password in the Reenter Password textbox, and click either the MD5 or SHA radio button to select the Protocol to be used. Click Insert to add the user. To require information privacy, click the Privacy Required checkbox, enter a password in the Password textbox, reenter the password in the Reenter Password textbox, and click the DES checkbox.
Step 5
Note
You will see a message saying that the SNMP master agent needs to be restarted for the changes to take effect. Click OK to restart the SNMP master agent or Cancel to continue without restarting the master agent.
The new user is added to the list of users on the SNMP User Configuration page.
Step 6
To add additional users, repeats Step 2 through Step 4.
Related Topics
SNMP User Configuration, page B-7
Configuring the SNMP V3 Notification Destination

The SNMP V3 Notification Destination String provides a greater amount of security because each notification string is associated with a user. When configuring a user, you can specify the desired level of authentication and security. To configure the SNMP V3 notification string, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select SNMP > V3 Configuration > Notification Destination. The SNMP Notification Destination Configuration page appears.
Step 2 Step 3
To add a new SNMP Notification Destination, click Add New. From the Host IP Addresses pulldown menu, select Add New. Additional fields appear.
6-5
Chapter 6 Using the System Monitor Tools
Step 4 Step 5
Enter the Host IP Address and Port Number in the text boxes. From the Notification Type pulldown menu, select Inform or Trap. If you select Trap, the Security Level pulldown menu appears. Proceed to Step 7. If you select Inform, you are prompted to enter a remote engine ID. Enter the remote engine ID. From the Security Level pulldown menu, select the desired security level. Click the radio button to the left of the User Name to select a user to be associated with the notification destination. To add additional notification destinations, repeat Step 2 through Step 8.
Related Topics
SNMP V3 Notification Destination Configuration, page B-9
Configuring MIB2
The SNMP MIB2 tool lets you specify a contact person for a MIB2 managed node and the physical location of the managed node. To configure MIB2, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select SNMP > System Group Configuration > MIB2 System Group Configuration. The SNMP MIB2 Configuration page appears.
In the System Contact text box, enter the name of the contact. In the Location text box, enter the location of the managed node. Click the Update icon in the upper left corner of the page. To modify the information, click the Clear icon in the upper left corner of the page, enter new information in the System Contact and Location text boxes, and click the Update icon again.
Related Topics
MIB2 SystemGroup Configuration, page B-11
Using the System Monitor Tools

These topics describe how to use the System Monitor tools:

Using the CPU and Memory Usage Tool, page 6-7 Using the Processes Tool, page 6-8 Using the Disk Usage Tool, page 6-8
6-6
OL-12376-01
Chapter 6
Configuring Cisco Emergency Responder 2.0 Serviceability Using the System Monitor Tools
Using the CPU and Memory Usage Tool

You can use the CPU and Memory Usage tool to monitor and log this information. By default, the information is refreshed every 30 seconds. You change how often the information refreshes, or you can disable the auto-refresh feature. To use the CPU and Memory Usage tool, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select System Monitor > CPU & Memory Usage. The CPU and Memory Usage page appears. The page is divided into two sections, Processors and Memory. For details on the information that is displayed, see Table B-12 on page B-11.
To change the rate at which the page refreshes, enter a value (in seconds) in the Set the screen refresh value text box and click Set. The minimum value you can enter is 5 seconds. To disable the auto-refresh feature, click the Disable Auto-Refresh check box in the upper left corner. To create a log file of the CPU usage, click the Start Log button in the Processors section of the page. Similarly, to create a log file of the Memory usage, click the Start Log button in the Memory section of the page. You can create up to 25 log files. The default interval for logging is 10 seconds. To change the logging interval, follow these steps:
a. b.
To change the CPU logging interval, enter a value between 5 seconds and 600 seconds in the Set CPU Logging Interval text box and click Set. To change the Memory logging interval, enter a value between 5 seconds and 600 seconds in the Set Memory Logging Interval text box and click Set.
Step 5
To download the log files, click Download CPU Log File or Download Memory Log File. The system displays a Log Files page that shows all the current log files. Thereafter, log files are recycled; when a new log file is added, the oldest log file is deleted.
Step 6
To download individual files, click the check box to the left of the log file name(s) you want to download. To download all log files, click the check box to the left of the File Name column heading. When you have selected the files, click Download. If you select multiple files for download, the system will create and download a zipped folder called CPULogs (for Processor log files) and MemoryLogs (for Memory log files). You can also view the log files online without downloading them. To do so, click the file name. The system displays the contents of the log file.
Step 7
Related Topics
CPU and Memory Usage, page B-11
6-7
Chapter 6 Using the System Monitor Tools
Using the Processes Tool

You can use the Processes tool to monitor and log process information. By default, the information is refreshed every 30 seconds; the minimum refresh value is 5 seconds. You change how often the information refreshes, or you can disable the auto-refresh feature. To use the Processes tool, follow these steps:
Procedure
Step 1
From the Cisco ER Serviceability web interface, select System Monitor > Processes. The Processes page appears. For details on the information that is displayed, see Table B-13 on page B-13. You can perform an ascending or descending sort of the results. To perform a sort, click the up arrow or down arrow next to the column heading that you want to sort by. For example, to perform a descending sort based on the process, click the down arrow next to the Process column heading. Similarly, to perform an ascending sort based on the process ID, click the up arrow next to the PID column heading.
To change the rate at which the page refreshes, enter a value in the Set the screen refresh value text box in the upper right corner and click Set. The minimum value you can enter is 5 seconds. To disable the auto-refresh feature, click the Disable Auto-Refresh check box in the upper left corner. To view the details of a process, click the check box to the left of the process name and click View Selected Processes. You can select a maximum of ten processes. The Selected Processes displays the details of the process. On this page you can also set the refresh rate and disable the auto-refresh feature. To start a log of the process, click Start Log. To end logging, click Stop Log. To change the Process logging interval, enter a value between 5 seconds and 600 seconds in the Set Process Logging Interval text box and click Set.
Step 5 Step 6
To download the log files, click Download Process Logs from the Process Log Files page. (To download log files. click Download Log File from the Processes page.) To download individual files, click the check box to the left of the log file name(s) you want to download. To download all log files, click the check box to the left of the File Name column heading. When you have selected the files, click Download. If you select multiple files for download, the system will create and download a zipped folder called ProcessLogs. You can also view the log files online without downloading them. To do so, click the file name. The system displays the contents of the log file in a separate window.
Step 7
Related Topics
Processes, page B-13
Using the Disk Usage Tool

The Disk Usage tool displays the percentage of available disk space used by the different partitions in the system.
6-8
OL-12376-01
Chapter 6
Configuring Cisco Emergency Responder 2.0 Serviceability Using Cisco Emergency Responder Logs
To use the Disk Usage tool, follow these steps:

Procedure
Step 1
From the Cisco ER Serviceability web interface, select System Monitor > Disk Usage. The Disk Usage page appears. For details on the Disk Usage page, see Table B-17 on page B-15. To perform an ascending or descending sort, click the up arrow or down arrow next to the column heading that you want to sort by. For example, to perform a descending sort based on the partition, click the down arrow next to the Partition column heading. Similarly, to perform an ascending sort based on the available disk space, click the up arrow next to the Available Space column heading.
Step 2
Related Topics
Disk Usage, page B-15
Using Cisco Emergency Responder Logs

Cisco ER 2.0 provides an interface to collect system and application logs. These logs share the same user interface and log files can be viewed and downloaded in the same manner. The following procedure applies to all of the CER logs. Cisco ER 2.0 logs are organized into three types. The three types, and the logs within these types, are as follows:
CER Logs
CER Admin CER Server CER Phone Tracking JTAPI Tomcat Event Viewer Audio Driver
Platform Logs
CLI CLM Certificate Management/IPSec DRS Install/Upgrade Remote Support Syslog Servm
6-9
Chapter 6 Using Cisco Emergency Responder Logs
DB Logs
Cerdbmon Install DB
To view the Cisco ER logs, follow these steps:

Procedure
Step 1
From the Cisco ER Serviceability web interface, select System Logs > Log Type > Log Name. The selected Log Files page appears. See the Related Topics section below for details on each of these page. You can perform an ascending or descending sort of the results. To perform a sort, click the up arrow or down arrow next to the column heading that you want to sort by.
Step 2
You can download the log files to your local system using the Download button. To select individual files, click the check box to the left of the log file name you want to download. To select all log files, click the check box to the left of the File Name column heading. When you have selected the files, click Download. If you select multiple files for download, the system will create and download a zipped folder called CPULogs. The names of the zipped folders are based on the type of logs they contain, as follows:

CERAdmin CERServer CER Phone Tracking Syslog JTAPI Tomcat Install DRS CLILogs CMILogs ServmLogs RemoteSupportLogs InstallDBLogs CertificateManagement&IPSecLogs CerdbmonLogs
Step 3
You can also view the log files online without downloading them. To do so, click the file name. The system displays the contents of the log file in a separate window. Click Reload Log File to refresh the log file you are viewing. Click Download Log to download the log file you are viewing.
Related Topics
System Logs Menu, page B-15
6-10
OL-12376-01
C H A P T E R
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0
The following topics describe how to configure and use the Cisco Unified Communications Operating System, which is bundled with Cisco Emergency Responder 2.0:

Displaying Cisco Unified OS Information, page 7-1 Displaying and Modifying Cisco Unified OS Settings, page 7-3 Restarting, Shutting Down, or Switching Software Versions, page 7-5 Managing Security, page 7-6 Performing Software Upgrades, page 7-13 Using Cisco Unified OS Services, page 7-16
Displaying Cisco Unified OS Information

Using the Cisco Unified OS Administration web pages, you can view the status of the operating system, platform hardware, or the network. The following topics describe how to display this information.

Viewing ServerGroup Information, page 7-1 Viewing Hardware Status, page 7-2 Viewing Network Status, page 7-2 Viewing Installed Software, page 7-2 Viewing System Status, page 7-3
Viewing ServerGroup Information

To view cluster information, follow these steps:
Procedure
Step 1
From the main Cisco Unified OS Administration web page, select Show > ServerGroup. The ServerGroup page appears.
7-1
Chapter 7 Displaying Cisco Unified OS Information
Step 2
For descriptions of the fields on the ServerGroup page, see Table C-1 on page C-2.
Viewing Hardware Status

To view the hardware status, follow these steps:
Procedure
Step 1
From the main Cisco Unified OS Administration web page, select Show > Hardware. The Hardware Status page appears.
Step 2
For descriptions of the fields on the Hardware Status page, see Table C-2 on page C-2.
Viewing Network Status

The network status information that appears depends on whether Network Fault Tolerance is enabled. When Network Fault Tolerance is enabled, Ethernet port 1 automatically takes over network communications if Ethernet port 0 fails. If Network Fault Tolerance is enabled, network status information appears for the network ports Ethernet 0, Ethernet 1, and Bond 0. If Network Fault Tolerance is not enabled, status information appears only for Ethernet 0. To view the network status, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Show > Network. The Network Settings page appears.
Step 2
See Table C-3 on page C-3 for descriptions of the fields on the Network Settings page.
Viewing Installed Software

To view the software versions and installed software options, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Show > Software. The Software Packages page appears.
Step 2
For a description of the fields on the Software Packages page, see Table C-4 on page C-4.
7-2
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Displaying and Modifying Cisco Unified OS Settings
Viewing System Status

To view the system status, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Show > System. The System Status page appears.
Step 2
See Table C-5 on page C-4 for descriptions of the fields on the System Status page.
Displaying and Modifying Cisco Unified OS Settings

Use the Settings options to display and modifying IP settings, host settings, and Network Time Protocol (NTP) settings. These topics describe how to display and modify Cisco Unified OS settings:

Configuring Ethernet Settings, page 7-3 Configuring NTP Servers, page 7-4 Configuring SMTP Settings, page 7-5 Configuring Time Settings, page 7-5 Restarting, Shutting Down, or Switching Software Versions, page 7-5
Configuring Ethernet Settings

The Ethernet Settings options allow you to view and change Dynamic Host Configuration Protocol (DHCP), port, and gateway information. The Ethernet Configuration page allows you to enable or disable DHCP, to specify the Ethernet ports IP address and subnet mask, and to specify the IP address for the network gateway.
Note
All Ethernet settings apply only to Eth0. You cannot configure any settings for Eth1. The Maximum Transmission Unit (MTU) on Eth0 defaults to 1500. To view or change the Ethernet settings, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Settings > IP > Ethernet. The Ethernet Configuration page appears. To modify the Ethernet settings, enter the new values in the appropriate fields. For a description of the fields on the Ethernet Configuration page, see Table C-6 on page C-5.
Step 2
7-3
Chapter 7 Displaying and Modifying Cisco Unified OS Settings
Note
If you enable DHCP, then the Port Information and Gateway Information settings are disabled and cannot be changed.
Step 3
To preserve your changes, click Save.
Configuring NTP Servers

Ensure that external NTP server is stratum 9 or higher (1-9). To add, delete, or modify an external NTP server, follow these steps:
Note
You can only configure the NTP server settings on the Publisher.
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Settings > NTP Servers. The NTP Server List page appears. For details on the NTP Server List page, see the NTP Server List section on page C-6.
Step 2
You can add, delete, or modify an NTP server:

To delete an NTP server, check the check box in front of the appropriate server and click Delete
Selected.
To add an NTP server, click Add. The NTP Server Configuration page appears. Enter the
hostname or IP address, and then click Save.

To modify an NTP server, click the IP address. The NTP Server Configuration page appears.
Modify the hostname or IP address, and then click Save.
Note
Any change you make to the NTP servers can take up to five minutes to complete. Whenever you make any change to the NTP servers, you must refresh the page to display the correct status.
Step 3
To refresh the NTP Server Settings page and display the correct status, choose Settings > NTP Servers.
Note
After deleting, modifying, or adding NTP server, you must restart all both the Publisher and Subscriber for the changes to take affect.
7-4
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Displaying and Modifying Cisco Unified OS Settings
Configuring SMTP Settings

To configure the SMTP host settings, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Settings > SMTP. The SMTP Settings page appears. For details on the SMTP Settings page, see the SMTP Settings section on page C-7.
Step 2 Step 3
Enter the hostname or IP address of the SMTP host. Click Save.
Configuring Time Settings

To manually configure the time, follow these steps:
Note
Before you can manually configure the server time, you must delete any NTP servers that you have configured. See the Configuring NTP Servers section on page 7-4 for information about deleting NTP servers.
Procedure
From the Cisco Unified OS Administration web page, select Settings > Time. The Time Settings page appears. For details on the Time Settings page, see the Time Settings section on page C-8. Enter the date and time for the system. Click Save.
Restarting, Shutting Down, or Switching Software Versions

To restart, shutdown, or switch Cisco ER software versions, follow these steps:
Procedure
Step 1 Step 2
From the Cisco Unified OS Administration web page, select Settings > Version. The Version Settings page appears. For details on the Version Settings page, see the Version Settings section on page C-8. To restart the version running on the active partition, click Restart.
Caution Step 3
This procedure causes the system to restart and become temporarily out of service. To shut down the system, click Shutdown.
7-5
Chapter 7 Managing Security
Note
The hardware does not power down automatically.
Caution Step 4
If you press the power button on the server, the system will immediately shut down. To shut down the system that is running on the active disk partition and then automatically restart the system using the software version on the inactive partition, click Switch Versions.
Note
The Switch Version button only appears if there is software installed on the inactive partition.
Note
You can use this option when you are upgrading to a newer software version or when you need to fall back to an earlier software version.
Managing Security
These topics describe how to perform security and IPSec management tasks:

Set Internet Explorer Security Options, page 7-6 Managing Certificates and Certificate Trust Lists, page 7-7 Managing IPSec, page 7-12
Set Internet Explorer Security Options

To ensure that your Internet Explorer security settings are configured correctly so that you can download certificates from the server, follow these steps:
Procedure
Start Internet Explorer. Navigate to Tools > Internet Options. Click the Advanced tab. Scroll down to the Security section on the Advanced tab. If necessary, clear the Do not save encrypted pages to disk check box. Click OK.
7-6
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Managing Security
Managing Certificates and Certificate Trust Lists

The following topics describe the functions you can perform using the Certificate Management menu options:

Displaying Certificates, page 7-7 Downloading a Certificate or CTL, page 7-7 Deleting and Regenerating a Certificate, page 7-8 Uploading a Certificate or Certificate Trust List, page 7-9 Using Third Party CA Certificates, page 7-10 Downloading a Certificate Signing Request, page 7-11 Monitoring Certificate Expiration Dates, page 7-11
Displaying Certificates
To display existing certificates, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. For details on the Certificate List page, see the Certificate List section on page C-9.
Step 2 Step 3
Use the Find controls to filter the certificate list. To view details of a certificate or trust store, click the file name. The Certificate Configuration page displays information about the certificate.
Step 4
To return to the Certificate List page, select Back To Find/List in the Related Links list, then click Go.
Downloading a Certificate or CTL

To download a certificate or CTL from Cisco ER to your local system, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Click the file name of the certificate or CTL. Use the Find controls to filter the certificate list. Click the file name of the certificate or CTL. The Certificate Configuration page appears. Click Download. In the File Download dialog box, click Save.
Step 2 Step 3
Step 4 Step 5
7-7
Deleting and Regenerating a Certificate

These sections describe deleting and regenerating a certificate:

Deleting a Certificate, page 7-8 Regenerating a Certificate, page 7-8
Deleting a Certificate
To delete a trusted certificate, follow these steps:
Caution
Deleting a certificate can affect your system operations.

Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Use the Find controls to filter the certificate list. Click the file name of the certificate or CTL. The Certificate Configuration page appears. Click Delete.
Step 2 Step 3
Step 4
Regenerating a Certificate
To regenerate a certificate, follow these steps:
Caution
Regenerating a certificate can affect your system operations.

Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Click Generate New. The Generate Certificate dialog box opens.
Step 2
Step 3 Step 4
Choose a certificate name from the Certificate Name list. Click Generate New.
7-8
OL-12376-01
Chapter 7
Uploading a Certificate or Certificate Trust List

Caution
Uploading a new certificate or certificate trust list (CTL) file can affect your system operations.
Note
The system does not distribute trust certificates to other cluster servers automatically. If you need to have the same certificate on more than one server, you must upload the certificate to each server individually. These sections describe how upload a CA root certificate, application certificate, or CTL file to the server:

Upload a Certificate, page 7-9 Upload a Trusted Certificate, page 7-9
Upload a Certificate
To upload a CA root certificate, application certificate, or CTL file to the server, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.
Step 2
Click Upload Certificate. The Upload Certificate dialog box opens. Select the certificate name from the Certificate Name list. If you are uploading an application certificate that was issued by a third party CA, enter the name of the CA root certificate in the Root Certificate text box. If you are uploading a CA root certificate, leave this text box empty. Select the file to upload by doing one of the following steps:

Step 3 Step 4
Step 5
In the Upload File text box, enter the path to the file. Click the Browse button and navigate to the file; then, click Open.
Step 6
To upload the file to the server, click the Upload File button.
Upload a Trusted Certificate

To upload a trusted certificate, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Click Upload CTL. The Upload Certificate Trust List dialog box opens.
Step 2
7-9
Step 3 Step 4
Select the certificate name from the Certificate Name list. If you are uploading an application certificate that was issued by a third party CA, enter the name of the CA root certificate in the Root Certificate text box. If you are uploading a CA root certificate, leave this text box empty. Select the file to upload by doing one of the following steps:

Step 5
In the Upload File text box, enter the path to the file. Click the Browse button and navigate to the file; then, click Open.
Step 6
To upload the file to the server, click the Upload File button.
Using Third Party CA Certificates

Cisco Unified OS supports certificates that a third party Certificate Authority (CA) issues with PKCS # 10 Certificate Signing Request (CSR). The following table provides an overview of this process, with references to additional documentation: Task
For More Information See the Generating a Certificate Signing Request section on page 7-10. See the Downloading a Certificate Signing Request section on page 7-11. Get information about obtaining application certificates from your CA. See Obtaining Third-Party CA Certificates section on page 7-11 for additional notes. Get information about obtaining a root certificate from your CA. See Obtaining Third-Party CA Certificates section on page 7-11 for additional notes. See the Uploading a Certificate or Certificate Trust List section on page 7-9.
Generate a CSR on the server. Download the CSR to your PC. Use the CSR to obtain an application certificate from a CA. Obtain the CA root certificate.
Step 4
Upload the CA root certificate to the server.
Upload the application certificate to the See the Uploading a Certificate or Certificate Trust List section on server. page 7-9. Restart the services that are affected by For all certificate types, restart the corresponding service (for example, the new certificate. restart the Tomcat service if you updated the Tomcat certificate). In addition, if you updated the certificate for CAPF or Cisco Unified CM, restart the TFTP service. For information about restarting services, see the Using the Control Center section on page 6-1.
Generating a Certificate Signing Request

To generate a Certificate Signing Request (CSR), follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.
7-10
OL-12376-01
Chapter 7
Step 2
Click Generate CSR. The Generate Certificate Signing Request dialog box opens.
Step 3 Step 4
Select the certificate name from the Certificate Name list. Click Generate CSR.
Downloading a Certificate Signing Request

To download a Certificate Signing Request, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Download Certificate Signing Request page appears.
Step 2
Click Download CSR. The Download Certificate Signing Request dialog box opens. Select the certificate name from the Certificate Name list. Click Download CSR. In the File Download dialog box, click Save.
Obtaining Third-Party CA Certificates

To use an application certificate that a third party CA issues, you must obtain from the CA both the signed application certificate and the CA root certificate. Get information about obtaining these certificates from your CA. The process varies among CAs. CAPF and Cisco ER CSRs include extensions that you must include in your request for an application certificate from the CA. If your CA does not support the ExtensionRequest mechanism, you must enable the X.509 extensions that are listed on the final page of the CSR generation process. Cisco Unified OS generates certificates in DER and PEM encoding formats and generates CSRs in PEM encoding format. It accepts certificates in DER and DER encoding formats. Cisco has verified third-party certificates that were obtained from Microsoft, Keon, and Verisign CAs. Certificates from other CAs might work but have not been verified.
Monitoring Certificate Expiration Dates

The system can automatically send you an e-mail when a certificate is close to its expiration date. To view and configure the Certificate Expiration Monitor, follow these steps:
Note
In order to update information on the Certificate Expiration Monitor page, the Cisco Certificate Expiry Monitor service must be running.
7-11
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate Monitor page appears.
Step 2 Step 3
Enter the required configuration information. See Table C-19 on page C-13 for a description of the Certificate Monitor Expiration fields. To save your changes, click Save.
Managing IPSec
These topics describe how to manage IPSec:

Displaying or Changing an Existing IPSec Policy, page 7-12 Setting Up a New IPSec Policy, page 7-13
Note
IPSec does not get automatically set up between nodes in the cluster during installation.
Displaying or Changing an Existing IPSec Policy

To display or change an existing IPSec policy, follow these steps:
Note
Because any changes that you make to an IPSec policy during a system upgrade will get lost, do not modify or create IPSec policies during an upgrade.
Caution
IPSec, especially with encryption, will affect the performance of you system.
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > IPSEC Configuration. The IPSEC Policy Configuration page appears.
Caution Step 2
Any changes that you make to the existing IPSec policies can impact your normal system operations. Click the Display Detail link. The Association Details page appears. For an explanation of the fields in this page, see Table C-21 on page C-14.
7-12
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Performing Software Upgrades
Setting Up a New IPSec Policy

To set up a new IPSec policy and association, follow these steps:
Note
Because any changes you make to an IPSec policy during a system upgrade will get lost, do not modify or create IPSec policies during an upgrade.
Caution
IPSec, especially with encryption, will affect the performance of you system.
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Security > IPSEC Management. The IPSEC Policy List page appears.
Step 2
Click Add New. The IPSEC Policy Configuration page appears. Click Next. The Setup IPSEC Policy and Association page appears.
Step 3
Step 4 Step 5
Enter the appropriate information on the IPSEC Policy Configuration page. For a description of the fields on this page, see Table C-21 on page C-14. To set up the new IPSec policy, click Save.
Performing Software Upgrades

This topic describes how to perform software upgrades:
Upgrading and Installing Software, page 7-13
Upgrading and Installing Software

The Software Upgrade pages enable you to upgrade Cisco ER software from either a local or a remote source. The software upgrade process also enables you to back out of an upgrade if problems occur. You install the software for the upgrade on the systems inactive partition and perform a restart to switch the system to the newer version of the software. During this process, the upgraded software becomes the active partition, and your current software becomes the inactive partition. Your configuration information migrates automatically to the upgraded version in the active partition. If for any reason you decide to back out of the upgrade, you can restart the system to the inactive partition that contains the older version of the software. However, any configuration changes that you made since upgrading the software will be lost.
7-13
Chapter 7 Performing Software Upgrades
Note
When upgrading from Cisco ER 2.0 to a later version, the Publisher must be upgraded first, followed by the Subscriber.
Installing and Upgrading Software From a Local Source

You can install software from a DVD that is located in the local disc drive and then start the upgrade process.
Note
Be sure to back up your system data before starting the software upgrade process. For more information, see the Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System chapter. To install or upgrade software from a DVD, follow these steps:
Procedure
Step 1
If you plan to download the upgrade file, create a DVD by performing these steps:
a.
Download the appropriate upgrade file from Cisco.com.
Note b. Step 2 Step 3
Do not unzip or untar the file. If you do, the system may not be able to read the upgrade files.
Copy the upgrade file to a writable DVD.
Insert the DVD into the disc drive on the local server that is to be upgraded. From the Cisco Unified OS Administration web page, select Software Upgrades > Install/Upgrade. The Software Installation/Upgrade page appears. Choose DVD/CD from the Source list. Enter the path to the patch file on the DVD in the Directory field. If the file is in the root directory, enter a slash (/). To continue the upgrade process, click Next. Choose the upgrade version that you want to install and click Next. On the next page, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred. When the download completes, verify the checksum value against the checksum for the file you that downloaded that is shown on Cisco.com.
Step 4 Step 5
Caution
The two checksum values must match to ensure the authenticity and integrity of the upgrade file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again. Choose whether you want the system to automatically reboot to the upgraded partition after installing the upgrade software:
To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to
Step 10
upgraded partition.
7-14
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Performing Software Upgrades
To install the upgrade and then manually reboot to the upgraded partition at a later time, choose
Do not reboot after upgrade.

Step 11
Click Upgrade. The Upgrade Status page appears the Upgrade log. When the installation completes, click Install Another. To restart the system and activate the upgrade, choose Settings > Versions, then click Restart. The system restarts running the upgraded software.
Step 12 Step 13
Installing and Upgrading Software From a Remote Source

To install software from a network drive or remote server, follow these steps:
Note
Be sure to back up your system data before starting the software upgrade process. For more information, see the Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System chapter.
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Software Upgrades > Install/Upgrade. The Software Installation/Upgrade page appears. Choose Remote Filesystem from the Source list. Enter the path to the patch file on the remote system in the Directory field. If the upgrade file is located on a Linux or UNIX server, you must enter a forward slash at the beginning of the directory path you want to specify. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.
Step 2 Step 3
Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11
Enter the server name in the Server field. Enter your user name in the User Name field. Enter your password in the User Password field. Select the transfer protocol from the Transfer Protocol field. To continue the upgrade process, click Next. Choose the upgrade version that you want to install and click Next. On the next page, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred. When the download completes, verify the checksum value against the checksum for the file you that downloaded that is shown on Cisco.com.
Caution
The two checksum values must match to ensure the authenticity and integrity of the upgrade file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try the upgrade again.
7-15
Chapter 7 Using Cisco Unified OS Services
Step 12
Choose whether you want the system to automatically reboot to the upgraded partition after installing the upgrade software:
To install the upgrade and automatically reboot to the upgraded partition, choose Reboot to
upgraded partition.
To install the upgrade and then manually reboot to the upgraded partition at a later time, choose
Do not reboot after upgrade.

Step 13
Click Next. The Upgrade Status pages displays the Upgrade log.
Step 14 Step 15
When the installation completes, click Install Another. To restart the system and activate the upgrade, choose Settings > Versions, then click Restart. The system restarts running the upgraded software.
Using Cisco Unified OS Services

These topics describe how to use Cisco Unified OS services:

Using the Ping Utility, page 7-16 Setting Up Remote Support, page 7-17
Using the Ping Utility

The Ping Configuration page enables you to send ping requests to test if other systems are reachable over the network. To ping another system, follow these steps:
Procedure
Step 1
From the Cisco Unified OS Administration web page, select Services > Ping. The Ping Configuration page appears. For details on the Ping Configuration page, see the Ping Configuration section on page C-16.
Enter the IP address or network name for the system that you want to ping. Enter the ping interval in seconds. Enter the packet size. Enter the ping count, the number of times that you want to ping the system.
Note
When you specify multiple pings, the ping command does not display the ping date and time in real time. Be aware that the ping command displays the data after the number of pings that you specified complete.
Step 6
Choose whether you want to validate IPSec.
7-16
OL-12376-01
Chapter 7
Configuring the Cisco Unified Operating System for Cisco Emergency Responder 2.0 Using Cisco Unified OS Services
Step 7
Click Ping. The Ping Results text box displays the ping statistics.
Setting Up Remote Support

From the Remote Support page, you can set up a remote account that Cisco support personnel can use to access the Cisco ER system for a specified period of time. The remote support process works as follows:
1. 2. 3. 4. 5. 6.
The customer sets up a remote support account. This account includes a configurable time limit on how long Cisco personnel can access it. When the remote support account is set up, a pass phrase gets generated. The customer calls Cisco support and provides the remote support account name and pass phrase. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase. Cisco support logs into the remote support account on the customer system by using the decoded password. When the account time limit expires, Cisco support can no longer access the remote support account.
To set up remote support, follow these steps:

Procedure
Step 1
From the Cisco Unified OS Administration web page, select Services > Remote Support. The Remote Access Configuration page appears.
Step 2 Step 3
If no remote support account is configured, click Add. Enter an account name for the remote account and the account life in days.
Note Step 4
Ensure the account name at least six-characters long and all lowercase, alphabetic characters.
Click Save. The Remote Access Configuration page redisplays. For descriptions of fields on the Remote Access Configuration page, see Table C-25 on page C-18.
Step 5
To access the system by using the generated pass phrase, contact your Cisco personnel.
7-17
Chapter 7 Using Cisco Unified OS Services
7-18
OL-12376-01
C H A P T E R
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System

These topics describe how to configure the Cisco Emergency Responder (Cisco ER) 2.0 Disaster Recovery System:

What is the Disaster Recovery System?, page 8-1 Quick-Reference Tables for Backup and Restore Procedures, page 8-2 Supported Features and Components, page 8-4 System Requirements, page 8-4 How to Access the Disaster Recovery System, page 8-4 Master Agent Duties and Activation, page 8-4 Local Agents, page 8-4 Adding Backup Devices, page 8-5 Creating and Editing Backup Schedules, page 8-6 Enabling, Disabling, and Deleting Schedules, page 8-7 Starting a Manual Backup, page 8-7 Checking Backup Status, page 8-7 Restoring a Backup, page 8-8 Restoring a Cluster, page 8-9 Viewing the Backup and Restore History, page 8-11 Trace Files, page 8-12 Command Line Interface, page 8-13
What is the Disaster Recovery System?

The Disaster Recovery System (DRS), which can be invoked from the main Cisco Emergency Responder (Cisco ER) 2.0 web interface, provides full data backup and restore capabilities for all servers in a Cisco ER cluster. The Disaster Recovery System allows you to perform a regularly scheduled automatic or user-invoked data backup. DRS supports multiple backup schedules.
8-1
Chapter 8 Quick-Reference Tables for Backup and Restore Procedures
The Cisco Disaster Recovery System performs a cluster-level backup, which means that it collects backups for all servers in a Cisco ER cluster to a central location and archives the backup data to physical storage device. When performing a system data restoration, you can choose which servers in the cluster you want to restore. The Disaster Recovery System includes the following capabilities:

A user interface for performing backup and restore tasks A distributed system architecture for performing backup and restore functions Scheduled backups Archive backups to a physical tape drive or remote sftp server
Note
The tape device must be attached to the Publisher.
The Disaster Recovery System contains two key functions, Master Agent (MA) and Local Agent (LA). The Master Agent coordinates backup and restore activity with all the Local Agents. The system automatically activates both the Master Agent and the Local Agent on all nodes in the cluster.
Note
The Disaster Recovery System does not migrate data from Windows to Linux or from Linux to Linux. You must run a restore on the same product version as the backup. For information on data migration from a Windows-based platform to a Linux-based platform, refer to the Data Migration Assistant User Guide. The following is a list of supported/recommended SFTP servers (freeware) that can be used as backup storage locations:
Note
This list is not comprehensive and is offered as a recommendation only. You may use any other SFTP server of your choosing.

OpenSSH (for UNIX) Sygwin (http://sshwindows.sourceforge.net/) freeFTPD (http://www.freeftpd.com/?ctt=download)
Quick-Reference Tables for Backup and Restore Procedures

The following tables provide a quick reference for the backup and restore procedures.
Backup Quick Reference

Table 8-1 provides a quick, high-level reference to the major steps, in chronological order, that you must perform to do a backup procedure using the Disaster Recovery System.
8-2
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Quick-Reference Tables for Backup and Restore Procedures
Note
The Disaster Recovery System does not migrate data from Windows to Linux or from Linux to Linux. A restore must run on the same product version as the backup. For information on data migration from a Windows-based platform to a Linux-based platform, refer to the Data Migration Assistant User Guide before following the steps in Table 8-1.
Table 8-1 High-Level Tasks for Performing a Backup Procedure
Task Create backup devices on which to back up data.
Reference Adding Backup Devices section on page 8-5
Create and edit backup schedules to back up data Creating and Editing Backup Schedules section on a schedule. on page 8-6
Note
Either a manual or a scheduled backup backs up the whole cluster. Enabling, Disabling, and Deleting Schedules section on page 8-7 Starting a Manual Backup section on page 8-7
Enable and disable backup schedules to back up data. Optionally, run a manual backup.
Check the Status of the BackupWhile a backup Checking Backup Status section on page 8-7 is running, you can check the status of the current backup job.
Restore Quick Reference

Table 8-2 provides a quick, high-level reference to the major steps, in chronological order, that you must follow to perform a restore procedure using the Disaster Recovery System.
Table 8-2 High-Level Tasks for Performing a Restore Procedure
Task
Reference
Choose Storage LocationYou must first choose Restoring a Backup section on page 8-8 the storage location from which you want to restore a backup file. Choose the Backup FileFrom a list of available Restoring a Backup section on page 8-8 files, choose the backup file that you want to restore. Choose FeaturesFrom the list of available features, choose the features that you want to restore. Restoring a Backup section on page 8-8
Choose NodesIf the feature was backed up from Restoring a Backup section on page 8-8 multiple nodes, you must choose the nodes that you want to restore. Check the Status of the RestoreWhile the restore process is running, you can check the status of the current restore job. Viewing the Restore Status section on page 8-11
8-3
Chapter 8 Supported Features and Components
Supported Features and Components

For the Cisco ER 2.0 release, you can back up and restore the following feature:
CER
When you choose a feature for backup, the system backs up all of its subcomponents automatically.
System Requirements
Make sure that Cisco ER 2.0 is running on all servers in the cluster.
How to Access the Disaster Recovery System

To access the Disaster Recovery System, select Disaster Recover System from the pulldown Navigation menu on the main Cisco ER 2.0 web interface. Log in to the Disaster Recovery System by using the same Administrator username and password that you use for the Cisco Unified OS Administration web interface.
Master Agent Duties and Activation

The system automatically activates the Master Agent on all nodes in the cluster, but only the Master Agent running on the publisher server is fully active. The Master Agent (MA) performs the following duties:

The MA stores systemwide component registration information. The MA maintains a complete set of scheduled tasks in the Cisco ER database. When it receives updates from the user interface, the MA sends executable tasks to the applicable Local Agents, as scheduled. (Local Agents execute immediate-backup tasks without delay.) You access the MA through the Disaster Recovery System user interface to perform activities such as scheduling backups, adding a new backup task for a specific server or a defined cluster, updating or reviewing an existing entry, displaying status of executed tasks, and performing system restoration. The MA stores backup sets on a locally attached tape drive or a remote network location.
Local Agents
Each server in a Cisco ER cluster, including the server that contains the Master Agent, must have its own Local Agent to perform backup and restore functions for its server.
Note
By default, a Local Agent automatically gets activated on each node of the cluster. The Local Agent runs backup and restore scripts on each node in the cluster.
8-4
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Adding Backup Devices
Adding Backup Devices

Before using the Disaster Recover System, you must configure the locations where you want the backup files to be stored. You can configure up to 10 backup devices. To configure backup devices, follows these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > Backup Device. The Backup Device List page appears. To configure a new backup device, click Add New. The Backup Device window appears. Enter the backup device name in the Backup device name field. Choose one of the following backup devices and enter the appropriate field values in the Select Destination area:
Step 2
Step 3 Step 4
Tape DeviceStores the backup file on a locally attached tape drive. Choose the appropriate tape device from the list.
Note
You cannot span tapes or store more than one backup per tape.
Network DirectoryStores the backup file on a networked drive that is accessed through an SFTP connection. Enter the following required information:
Server name: Name or IP address of the network server Path name: Path name for the directory where you want to store the backup file User name: Valid username for an account on the remote system Password: Valid password for the account on the remote system Number of backups to store on Network Directory: The number of backups to store on this
network directory.
Note
You must have access to an SFTP server to configure a network storage location. The SFTP path must exist prior to the backup. The account that is used to access the SFTP server must have write permission for the selected path.
Step 5
To update these settings, click Save.
Note
For network directory backups, after you click the Save button, the DRS Master Agent will validate the selected SFTP server. If the user name, password, server name, or directory path is invalid, the save will fail.
8-5
Chapter 8 Creating and Editing Backup Schedules
Creating and Editing Backup Schedules

You can create up to 10 backup schedules. Each backup schedule has its own set of properties, including a schedule for automatic backups, the set of features to back up, and a storage location. To manage backup schedules, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > Scheduler. The Schedule List window appears. Do one of the following steps to add a new schedule or edit an existing schedule:
a. b.
Step 2
To create a new schedule, click Add New. To configure an existing schedule, click its name in the Schedule List column.
The scheduler window appears.

Step 3
Enter a schedule name in the Schedule Name field.
Note Step 4 Step 5 Step 6 Step 7
You cannot change the name of the default schedule.
Select the backup device in the Select Backup Device area. Select the features to back up in the Select Features area. You must choose at least one feature. Choose the date and time when you want the backup to begin in the Start Backup at area. Choose the frequency at which you want the backup to occur in the Frequency area: Once, Daily, Weekly, or Monthly. If you choose Weekly, you can also choose the days of the week when the backup will occur.
Tip Step 8 Step 9
To set the backup frequency to Weekly, occurring Tuesday through Saturday, click Set Default.
To update these settings, click Save. To enable the schedule, click Enable Schedule. The next backup occurs automatically at the time that you set.
Note
Ensure that all servers in the cluster are running the same version of Cisco ER and are reachable through the network. Servers that are not running at the time of the scheduled backup will not be backed up.
Step 10
To disable the schedule, click Disable Schedule.
8-6
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Enabling, Disabling, and Deleting Schedules
Enabling, Disabling, and Deleting Schedules

To enable, disable, or delete schedules, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > Scheduler. The Schedule List window appears. Select the check boxes next to the schedules that you want to modify:

Step 2
To select all schedules, click Select All. To clear all check boxes, click Clear All.
To enable the selected schedules, click Enable Selected Schedules. To disable the selected schedules, click Disable Selected Schedules. To delete the selected schedules, click Delete Selected.
Starting a Manual Backup

To start a manual backup, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > Manual Backup. The Manual Backup page appears.
Select a backup device in the Select Backup Device area. Select the features to back up in the Select Features area. To start the manual backup, click Start Backup.
Checking Backup Status

You can check the status of the current backup job and cancel the current backup job. To view the backup history, see the Viewing the Backup and Restore History section on page 8-11. To check the status of the current backup job, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > Current Status. The Backup Status page appears. To view the backup log file, click the log filename link.
Step 2
8-7
Chapter 8 Restoring a Backup
Step 3
To cancel the current backup, click Cancel Backup.
Note
The backup is canceled after the current component has completed its backup operation.
Restoring a Backup
The Restore Wizard leads you through the steps that are required to restore a backup.
Tip
To restore all servers in a cluster, see the Restoring a Cluster section on page 8-9.
Caution
Before you restore Cisco ER, ensure that the Cisco ER version that is installed on the server matches the version of the backup file that you want to restore. To perform a restore, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Restore > Restore Wizard. The first page of the Restore Wizard (Step1 RestoreChoose Backup Device) appears.
Step 2 Step 3
Choose the backup device from which to restore in the Select Backup Device area. Click Next. The Step2 RestoreChoose the Backup Tar File page appears.
Step 4
Choose the backup file that you want to restore.
Note Step 5
The backup filename indicates the date and time that the system created the backup file.
Click Next. The Step3 RestoreSelect the Type of Restore page appears. Choose the features that you want to restore.
Step 6
Note Step 7 Step 8
Only the features that were backed up to the chosen file display.
Click Next. The Step4 RestoreFinal Warning for Restore page appears. To start restoring the data, click Restore. You are prompted to choose the node to restore.
Step 9
Choose the appropriate node.
8-8
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Restoring a Cluster
Caution
After you choose the node to which you want the data restored, any existing data on that server gets overwritten. Your data is restored on the nodes that you chose. To view the status of the restore, see the Viewing the Restore Status section on page 8-11. Restart the server.
Step 10 Step 11
Note
Depending on the size of your database and the components that you choose to restore, the system can require one hour or more to restore.
Restoring a Cluster
If a major failure or a hardware upgrade occurs, you may need to restore all nodes in the cluster. To restore a whole cluster, you must first restore the Publisher server and then restore the Subscriber server. The following procedures describe how to perform full-cluster restore process.
Restoring the Publisher

To restore the Publisher server, follow these steps:
Procedure
Step 1
Perform a fresh installation of Cisco ER 2.0 on the Publisher server. See the Installing the Cisco Emergency Responder Publisher section on page 2-4 for more information.
Caution
Before you restore Cisco ER 2.0, ensure that the Cisco ER version that is installed on the Publisher server matches the version of the backup file to be restored. From the main Disaster Recovery System web page, select Restore > Restore Wizard. The first page of the Restore Wizard (Step1 RestoreChoose Backup Device) appears. Choose the backup device from which to restore in the Select Backup Device area. Click Next. The Step2 RestoreChoose the Backup Tar File page appears. Choose the backup file that you want to restore.
Step 2
Step 3 Step 4
Step 5
Note Step 6
The backup filename indicates the date and time that the system created the backup file.
Click Next. The Step3 RestoreSelect the Type of Restore page appears.
8-9
Chapter 8 Restoring a Cluster
Step 7
Choose the features that you want to restore.
Note Step 8
Click Next. The Step4 RestoreFinal Warning for Restore page appears. To start restoring the data, click Restore. When you are prompted to choose the nodes to restore, choose only the first node (the Publisher). Your data is restored on the Publisher server. To view the status of the restore, see the Viewing the Restore Status section on page 8-11.
Note
During the restore process, do not perform any tasks with Cisco ER Administration or User Pages.
Step 12
Restart the server.
Note
Step 13
After the first node restarts, continue with the Restoring Subsequent Cluster Nodes section on page 8-10.
Restoring Subsequent Cluster Nodes

To restore subsequent nodes in the cluster, follow these steps:
Procedure
Step 1
Perform a fresh installation of Cisco ER 2.0 on the Subscriber server. See the Installing the Cisco Emergency Responder Subscriber section on page 2-8 for more information.
Caution
Before you restore Cisco ER, ensure that the Cisco ER version that is installed on the server matches the version of the backup file to restore. From the main Disaster Recovery System web page, select Restore > Restore Wizard. The first page of the Restore Wizard (Step 1 RestoreChoose Backup Device) appears.
Step 2
Step 3 Step 4
Choose the backup device from which to restore in the Select Backup Device area: Click Next. The Step2 RestoreChoose the Backup Tar File page appears.
Step 5
Choose the backup file that you want to restore.
8-10
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Viewing the Backup and Restore History
Caution
To restore Subscriber nodes in the cluster, you must choose the same backup file that you used to restore the Publisher. Click Next. The Step3 RestoreSelect the Type of Restore page appears. Choose the features that you want to restore.
Step 6
Step 7
Note Step 8
Click Next. The Step4 RestoreFinal Warning for Restore page appears. To start restoring the data, click Restore. When you are prompted to choose the nodes to restore, choose only the subsequent (Subscriber) nodes. Your data is restored on the subsequent nodes. To view the status of the restore, see the Viewing the Restore Status section on page 8-11. Restart the server.
Note
Viewing the Restore Status

To check the status of the current restore job, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Restore > Status. The Restore Status page appears. To view the restore log file, click the log filename link.
Step 2
Viewing the Backup and Restore History

These topics describe how you can see the last 20 backup and restore jobs:

Backup History Restore History
8-11
Chapter 8 Trace Files
Backup History
To view the backup history, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Backup > History. The Backup History page appears.
Step 2
From the Backup History page, you can view the backups that you have performed, including filename, storage location, completion date, result, and features that are backed up.
Note
The Backup History page displays only the last 20 backup jobs.
Restore History
To view the restore history, follow these steps:
Procedure
Step 1
From the main Disaster Recovery System web page, select Restore > History. The Restore History page appears.
Step 2
From the Restore History page, you can view the restores that you have performed, including filename, storage location, completion date, result, and the features that were restored.
Note
The Restore History page displays only the last 20 restore jobs.
Trace Files
Trace files for the Master Agent, the GUI, and each Local Agent are written to the following locations:

For the Master Agent, the trace file is platform/drf/trace/drfMA0* For each Local Agent, the trace file is platform/drf/trace/drfLA0* For the GUI, the trace file is platform/drf/trace/drfConfLib0* For completed backups, the trace files are platform/drf/log/<timestamp>_b.log For completed restores, the trace files are platform/drf/log/<timestamp>_r.log
You can view trace files by using the command line interface. For more information, see Appendix F, Command Line Interface.
8-12
OL-12376-01
Chapter 8
Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System Command Line Interface

The Disaster Recovery System also provides command-line access to a subset of backup and restore functions, as shown in Table 8-3. For detailed information on these commands and for information on using the command line interface, see the Appendix F, Command Line Interface.
Table 8-3 Disaster Recovery System Command Line Interface
Command utils disaster_recovery backup utils disaster_recovery restore utils disaster_recovery status utils disaster_recovery show_backupfiles utils disaster_recovery cancel_backup utils disaster_recovery show_registration utils disaster_recovery show_tapeid
Description Starts a manual backup by using the features that are configured in the Disaster Recovery System interface Starts a restore and requires parameters for backup location, filename, features, and nodes to restore Displays the status of ongoing backup or restore job Displays existing backup files Cancels an ongoing backup job Displays the currently configured registration Displays the tape identification information
8-13
Chapter 8 Command Line Interface
8-14
OL-12376-01
C H A P T E R
Using the Cisco Emergency Responder 2.0 Admin Utility

In Cisco Emergency Responder (Cisco ER) 2.0, the Admin Utility is integrated into the Cisco ER itself. The Admin Utility has its own web interface that you can access from the main Cisco ER web page. As with the other Cisco ER administration web interfaces, the Admin Utility web interface is password protected. These topics describe how to use the Cisco ER Admin Utility:

Pointing Subscriber Servers to a Different Publisher, page 9-1 Changing the Cisco Unified Communications Manager Version, page 9-2 Updating the Cisco ER Cluster Database Host Details, page 9-3
Pointing Subscriber Servers to a Different Publisher

To use the Admin Utility to point a subscriber server to a different publisher server, follow these steps:
Note
In the following procedure, P1 is the current Publisher of the Subscriber. P2 is the other Publisher, to which the Subscriber needs to be pointed.
Procedure
Step 1
Delete the Subscriber from the current Publisher by following these steps:
a. b. c. d.
Log in to the Cisco ER Administration web interface of the current Publisher (P1). Select System > Server Settings. Click on the Subscriber. Click Delete. This action deletes the Subscriber's entry from its Publisher's (P1) database.
Step 2
Add the Subscriber to its new Publisher by following these steps:

a. b. c. d.
Log in to the Cisco ER Administration web interface of the new publisher (P2). Select System > Add Subscriber. Enter the hostname/IP address of the Subscriber. Click Insert.
9-1
Chapter 9 Changing the Cisco Unified Communications Manager Version
Step 3
Point the Subscriber to its new Publisher by following these steps:

a. b. c.
Log in to the Cisco ER Admin Utility web interface of the Subscriber. From the main Cisco ER Admin Utility page, select Update > Publisher. The Point to a New Publisher page appears. Enter the Host Name, IP Address, and Security Password of the new Publisher (P2) in the text boxes, then click Go.
Note Step 4
Changing the Publisher will delete all the associations with the current Publisher.
After the operation has completed, reboot the Subscriber.
Related Topics
Point to a New Publisher, page E-1
Note
This feature can be used on a Subscriber server.
Add Subscriber, page A-9 Server Settings for CERServerGroup, page A-6
Changing the Cisco Unified Communications Manager Version

To use the Admin Utility to change the Cisco Unified Communications Manager version, follow these steps:
Procedure
Log in to the Cisco ER Admin Utility web interface. From the main Cisco ER Admin Utility page, select Update > CCM Version. The Upgrade CCM Version page appears. From the Choose the CCM Version to Upgrade pulldown menu, select the new version of Cisco Unified Communications Manager, then click Go.
Note
You must change the Cisco Unified Communications Manager version separately for the Publisher and Subscriber nodes.
Once the system makes the change, the Status area of the Upgrade CCM Version page displays the new version number.
Related Topics
Update CCM Version, page E-2
9-2
OL-12376-01
Chapter 9
Using the Cisco Emergency Responder 2.0 Admin Utility Updating the Cisco ER Cluster Database Host Details
Updating the Cisco ER Cluster Database Host Details

By default, each server in a cluster considers its own database to be the cluster database host. Since each cluster should have only one database host, you must update the cluster configuration accordingly. For example, if you have two servergroups (Servergroup A and Servergroup B) each containing a Publisher and a Subscriber, you would do the following to update the cluster database host details:
1. 2. 3.
Update the cluster database host password for Servergroup A using Servergroup As own host name. Update the cluster database host password for Servergroup B by entering the IP address and cluster database password for Servergroup A. Repeat Step 2 for other servergroups in the cluster.
Note
If you use hostnames, then the hostname must be resolvable using DNS. If DNS is not configured or DNS is unavailable for any reason, hostname resolution will fail and cluster functionality will be impaired. It is recommended that the DNS configuration include redundant entries to prevent unavailability. Alternatively, the IP address of the cluster database host can be configured on this screen. To use the Admin Utility to update the Cisco ER cluster database host details, follow these steps:
Note
Cisco ER services will have to be restarted for this change to take effect. This action will update Cisco ER Cluster DB host details only for this server group. Other servers in this Cisco ER cluster will not be updated automatically.
Procedure
Log in to the Cisco ER Admin Utility web interface. From the main Cisco ER Admin Utility page, select Update > Cluster DBHost. The Update Cluster DB Host page appears. Enter the new Cluster DBHost name (if DNS is configured) or IP address in the text box. If the cluster is spread across domains, enter a fully qualified host name. Enter the password for the new Cluster DBHost in the Password text box. Reenter the password for the new Cluster DBHost in the Confirm Password text box. Click Go.
Related Topics
Update Cluster DB Host, page E-3
9-3
Chapter 9 Updating the Cisco ER Cluster Database Host Details
9-4
OL-12376-01
C H A P T E R
10
Preparing Users for Cisco Emergency Responder

These topics describe the various roles for Cisco Emergency Responder (Cisco ER) users. The topics describe not only the use of the software, but help you understand the larger policy and procedure decisions your organization must make to determine how Cisco ER fits into your organizations emergency response needs.

Preparing Onsite Alert (Security) Personnel for Cisco Emergency Responder, page 10-1 Understanding the ERL Administrators Role, page 10-2 Understanding the Network Administrators Role, page 10-3 Understanding the Cisco Emergency Responder System Administrators Role, page 10-4
Preparing Onsite Alert (Security) Personnel for Cisco Emergency Responder

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Cisco ER) fits into these policies and procedures, and work with your emergency response teams (onsite alert or security personnel) to update these procedures if necessary. Consider training these personnel on these aspects of Cisco ER:
How to use the Cisco ER web interface. See the Cisco ER user web interfaces online help for information on these topics. The online help includes a users guide in PDF format that you can print out and distribute to your users. The information in the users guide is the same as the information in the online help. Train users on these areas:
How to log into the user web interface. How alerts show up on the screen. How to obtain more information about the location of the call. Summary information includes
the actual extension of the caller; the ELIN, which is the phone number the PSAP gets as the number of the emergency caller; the phone location associated with the switch port; and the location field of the ALI. Users can also view the entire ALI.
How to acknowledge the call and add comments to it. Consider developing rules for these
procedures to ensure consistent behavior from your emergency response teams.

How to look up emergency calls in the emergency call history.
10-1
Chapter 10 Understanding the ERL Administrators Role
Explain how they will receive notification of an emergency call.

A web alert appears for everyone logged into the Cisco ER user web interface. All personnel assigned to an ERL receive a telephone call when an emergency call is made from
the ERL. The telephone call includes information about the extension of the caller.
If you configure email addresses for the personnel, they also receive an email, which includes
more information than the phone call, including ERL name and phone location. If the email address is for an email-based pager, they are paged. Paging is the most efficient way of getting information to users who are not at their desks. If the standby Cisco ER server handles an emergency call, all onsite alert personnel get notified of the call, and of the fact that the standby server handled the call. Decide how you want people to respond to these notifications.

Explain the ERL naming and phone location you are using. This is the primary information the personnel will have for identifying the location of the emergency caller. Explain the organizations policy for responding to emergency calls. Work with the emergency response teams to develop an acceptable policy if you do not already have one.
Related Topics
Preparing Your Staff for Cisco Emergency Responder, page 1-20
Understanding the ERL Administrators Role

Table 10-1 lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.
Table 10-1 Cisco Emergency Responder ERL Administration Recurring Tasks
Recurring Task Assign ERLs to new or changed switch ports
Description If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.
More Information Configuring Switch Ports, page 5-47
Create ERLs as required As your business expands, create new ERLs as required. Work with the telephony administrators to obtain ELINs for the ERLs, and with the network administrator to get the new switches defined in Cisco ER. Export ALI data and submit to your service provider If you make changes to ALI data, add or remove ERLs, or change the ELINs assigned to an ERL (for example, by adding or removing them), export the ALI and resubmit it to your service provider.
Creating ERLs, page 5-28 Configuring Switch Ports, page 5-47
Exporting ERL Information, page 5-36 Exporting ALI Information for Submission to Your Service Provider, page 5-37 Creating ERLs, page 5-28 Negotiate ALI Submission Requirements With Your Service Provider, page 1-19
10-2
OL-12376-01
Chapter 10
Preparing Users for Cisco Emergency Responder Understanding the Network Administrators Role
Table 10-1
Cisco Emergency Responder ERL Administration Recurring Tasks (continued)
Recurring Task Audit the manually defined phones
Description Regularly check your manual phone definitions to ensure each phone is still assigned to the correct ERL. Work with the telephony administrator to get notification of any adds, moves, or changes that involve these phones. Add phones as required. Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco ER cannot locate the phones and to resolve the problems. As onsite alert personnel are added, define them in Cisco ER and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco ER. Update phone numbers, e-mail address, and other contact information as they change.
More Information
Manually Defining a Phone, page 5-53
Audit the unlocated phones list
Identifying Unlocated Phones, page 5-52 Too Many Unlocated Phones, page 11-2
Add new onsite personnel or remove old ones; update phone numbers
Identifying Security Personnel (Onsite Alert Personnel), page 5-27 Creating ERLs, page 5-28
Add IP subnet for the IP If there is a new IP subnet that needs to be subnets to be tracked discovered by Cisco ER, then perform the following tasks:

Configuring IP Subnet-based ERLs, page 5-33
Configure an ERL spanning the new IP subnets geographical location. Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL,
Related Topics

Working with Emergency Response Locations, page 5-24 Managing Phones, page 5-47 Troubleshooting Cisco Emergency Responder, page 11-1
Understanding the Network Administrators Role

Table 10-2 lists the recurring tasks for which a network administrator is responsible. A system administrator can also perform these tasks.
10-3
Chapter 10 Understanding the Cisco Emergency Responder System Administrators Role
Table 10-2
Cisco Emergency Responder Network Administration Recurring Tasks
Recurring Task Add new switches
Description Add any switches you add to the network to the Cisco Emergency Responder (Cisco ER) configuration. A switch is considered new if it has an IP address not defined in Cisco ER. Remove switches from the Cisco ER configuration if you remove them from the network. Non-existent switches in the Cisco ER configuration do not create problems, but they do increase the time required to do phone tracking, because Cisco ERs attempts to connect to the switch must time out before moving on to the next switch. If you change the read community string on any defined switch, you must update the SNMP settings in Cisco ER. Until the setting is updated, Cisco ER will be unable to track phones attached to the switch. If a Cisco Unified Communications Manager cluster is added to the network, or one is removed, update the configuration for the Cisco ER group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco ER system administrator. Use the ERL Debug Tool to check that the correct and expected ERL is used for a selected phone.
More Information

Identifying the LAN Switches, page 5-42 Manually Running the Switch-Port and Phone Update Process, page 5-45 Identifying the LAN Switches, page 5-42
Remove old switches
Update the SNMP read community if it changes
Configuring the SNMP Connection, page 5-39
Update or remove Cisco Unified Communications Manager servers
Identifying the Cisco Unified Communications Man ager Clusters, page 5-21
Check ERL assignments
Using the Cisco Emergency Responder Admin Utility, page 11-19
Related Topics

Configuring Switches for Cisco Emergency Responder, page 5-39 Troubleshooting Cisco Emergency Responder, page 11-1
Understanding the Cisco Emergency Responder System Administrators Role

Table 10-2 lists the recurring tasks for which a system administrator is responsible. A system administrator might also be responsible for some or all of the ERL and network administrators tasks, as explained in the Understanding the ERL Administrators Role section on page 10-2 and the Understanding the Network Administrators Role section on page 10-3.
10-4
OL-12376-01
Chapter 10
Preparing Users for Cisco Emergency Responder Understanding the Cisco Emergency Responder System Administrators Role
Table 10-3
Cisco Emergency Responder System Administration Recurring Tasks
Recurring Task Add additional Cisco Emergency Responder (Cisco ER) groups
Description As telephones are added to the network, you might need additional Cisco ER groups. Install and define them and their telephony settings. Work with the telephony administrator to complete the required Cisco Unified Communications Manager configuration.
More Information
Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Configuring a Cisco Emergency Responder Server Group, page 5-16 Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Configuring Cisco Emergency Responder Servers, page 5-19 Uploading the Cisco Emergency Responder License File, page 5-20 Identifying the Cisco Unified Communications Manag er Clusters, page 5-21 Troubleshooting Cisco Emergency Responder, page 11-1 Managing Cisco Emergency Responder Users, page 5-9 Identifying the Cisco Unified Communications Manag er Clusters, page 5-21
Monitor the system and troubleshoot any problems
Help resolve any problems that arise. Work with the network and ERL administrators, and the telephony administrator, as appropriate. As onsite alert personnel change, or as Cisco ER system, network, and ERL administrators change, add or remove them as required. If a Cisco Unified Communications Manager cluster is added to the network, or one is removed, update the configuration for the Cisco ER group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco ER network administrator. If your email ID is configured in the server group settings, Cisco ER sends email alerts about critical errors to you. You are expected to understand the error and take action to correct the problem. Refer to the Troubleshooting Email Alerts section on page 11-10 for information to help you understand the email alerts and resolve problems.
Create new Cisco ER users; remove old users
Add or remove Cisco Unified Communications Manager servers
Monitor the email alerts that Cisco ER generates
Configuring a Cisco Emergency Responder Server Group, page 5-16
10-5
Chapter 10 Understanding the Cisco Emergency Responder System Administrators Role
Related Topics

Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Configuring Servers and Server Groups, page 5-16 Troubleshooting Email Alerts, page 11-10
10-6
OL-12376-01
C H A P T E R
11

These topics address problems you might encounter with Cisco Emergency Responder (Cisco ER), and provide ways to resolve them; also included are other tasks associated with problem identification and resolution.

Troubleshooting Phone-Related Problems, page 11-1 Troubleshooting Emergency Call Problems, page 11-5 Troubleshooting Cisco Emergency Responder System and Administration Problems, page 11-15 Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster, page 11-22 Starting and Stopping a Cisco Emergency Responder Server, page 11-23 Troubleshooting ALI Data Uploads, page 11-24 Collecting Call History Logs, page 11-27 Collecting Trace and Debug Information, page 11-27 Viewing Event Messages, page 11-29 Managing Performance, page 11-29 Integrating with Network Management Systems, page 11-29 Backing Up and Recovering Data, page 11-31 Troubleshooting the Data Migration Assistant, page 11-32 Troubleshooting Windows Upgrades, page 11-33 Troubleshooting Linux Upgrades, page 11-33
Troubleshooting Phone-Related Problems

These topics help you troubleshoot problems related to assigning phones to ERLs and managing the phones:

Undiscovered Phones, page 11-2 Too Many Unlocated Phones, page 11-2 Phone Sometimes Disappears in Cisco Emergency Responder, page 11-4 Wrong ERL is Used for a Shared Line, page 11-4 802.11b Endpoints Using Wrong ERL, page 11-4
11-1
Chapter 11 Troubleshooting Phone-Related Problems
Undiscovered Phones
If Cisco ER is not discovering the phones homing to Cisco Unified Communications Manager, check that all Cisco Unified Communications Managers are SNMP-reachable and that the SNMP settings are correct. Cisco ER will log an event if Cisco Unified Communications Manager is SNMP-unreachable. To verify the Cisco Unified Communications Manager SNMP settings, follow these steps:
Procedure
Step 1
Log in to the Cisco ER Administration command line interface and use the following command to ping the Cisco Unified Communications Manager server:
utils network ping <ipaddress of CUCM>
Step 2
If you successfully ping the Cisco Unified Communications Manager, verify that the SNMP settings are correct on Cisco Unified Communications Manager, as follows:
If you are using a Linux-based version of Cisco Unified Communications Manager (version 6.0 or higher), log in to the Cisco Unified Communications Manager Serviceability web interface and use the SNMP web pages to check the SNMP community string settings. If you are using a Windows-based version of Cisco Unified CallManager, open the services on Cisco Unified Communications Manager. Go to: Start > Settings > Control Panel > Administrative Tools > Services Properties > SNMP > Properties > Security Tab
Step 3
Check to see if Cisco Unified CM is SNMP reachable by running the following CLI command on the Cisco ER server:
utils snmp get <ccm ip-address/host name> <snmp-read-community-string> .1.3.6.1.2.1.1.2.0
If the Cisco Unified CM is SNMP reachable, then the output of the above command should be similar to the following:
Variable = .1.3.6.1.2.1.1.2.0 value = OBJECT IDENTIFIER <sys-oid-of-ccm>
Too Many Unlocated Phones

Cisco ER obtains a list of registered phones from Cisco Unified Communications Manager and tries to locate all phones. If Cisco ER cannot locate a phone behind a switch port or in any configured IP subnets, and the phone is not a configured synthetic phone, the phone will be placed in the list of unlocated phones. If there are a lot of unlocated phones, first try running the switch port and phone update process to see if Cisco ER can resolve some of the problems automatically. See the Manually Running the Switch-Port and Phone Update Process section on page 5-45 for more information. These are some things that can prevent Cisco ER from locating a phone:
If more than one switch port reports the phone as a CDP (Cisco Discovery Protocol) neighbor, then the phone will be placed in unlocated phones. This condition will be corrected in the next phone tracking when only one switch port reports this phone as its CDP neighbor.
11-2
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Phone-Related Problems
The phone is attached to a switch that is not defined in Cisco ER. See the Identifying the LAN Switches section on page 5-42 for information on defining switches. The phone is connected to an unsupported device, such as a router port, a hub connected to a router, or an unsupported switch. See the Network Hardware and Software Requirements section on page 1-4 for a list of supported switches. See the Manually Defining a Phone section on page 5-53 for information on configuring these types of phones if you cannot connect them to a supported device. The phone is connected to a hub, which is connected to a supported switch port, but it does not support CDP. Cisco ER can consistently discover CDP-enabled phones attached to hubs (which are attached to supported switch ports), but cannot always track non-CDP phones attached in this manner. For non-CDP phones, ensure the phones are attached directly to supported switch ports. The switch to which the phone is connected is currently unreachable, for example, it does not respond to SNMP queries. This could be for several reasons:
The SNMP read community string on the switch does not match the string configured in
Cisco ER. Correct the Cisco ER configuration. See the Configuring the SNMP Connection section on page 5-39.
The phone requires CAM table access, but CAM tracking is not enabled for the switch in
Cisco ER. See the Identifying the LAN Switches section on page 5-42.
There is a network outage preventing communication between the Cisco ER server and the
switch. Locate and resolve the network outage problem. Unreachable switches are not retried until Cisco ER runs the next full switch-port and phone update process, unless you run it against the individual switch (see below).
The phone has moved to a switch served by a different Cisco ER group. If this is the case, the Cisco ER group name is shown for the phone in the unlocated phones list. If the phone is not locatable in the next incremental phone tracking process after it is moved, the phone remains unlocated in any Cisco ER group until a full switch-port and phone update process is run. The phone requires CAM-based tracking, but CAM-based tracking is not enabled on the switch to which the phone is connected. Cisco IP SoftPhone and some other phone models require CAM-based tracking. See the Identifying the LAN Switches section on page 5-42 for information on enabling CAM-based tracking, and Network Hardware and Software Requirements section on page 1-4 for a list of phones that require CAM-based tracking.
After fixing the problems that are preventing Cisco ER from locating phones, run the switch-port and phone update process on the affected switches, or on all switches:

To run the process on a specific switchSelect Phone Tracking > LAN Switch Details and select the switch in the left-hand column; then click Locate Switch Ports. To run the process on all switchesSelect Phone Tracking > Run Switch-Port & Phone Update.
Related Topics

Identifying Unlocated Phones, page 5-52 IP Subnet Phones, page A-37 Cisco Unified OS CLI Commands, page F-4
11-3
Chapter 11 Troubleshooting Phone-Related Problems
Phone Sometimes Disappears in Cisco Emergency Responder

If Cisco ER is in the middle of a phone tracking process, and a phone is in the middle of homing to a different Cisco Unified Communications Manager cluster, no Cisco Unified Communications Manager cluster has a record of the phone. Thus, Cisco ER does not know the phone exists, and you will not be able to look up the phone in the Cisco ER interface. However, assuming the phone successfully connects to a Cisco Unified Communications Manager cluster, Cisco ER tracks the phone during the next incremental phone tracking process, and the phone should then appear in the Cisco ER interface. This problem can also occur if phones are reconnecting to a primary Cisco Unified Communications Manager server from a backup server during the Cisco ER phone tracking process.
Wrong ERL is Used for a Shared Line

When two or more phones with a shared line appearance move from switches that are monitored by one Cisco ER group to switches that are monitored by a different Cisco ER group, then Cisco ER may assign an incorrect ERL to these phones during an emergency call. This can occur when the phones move to a different campus that has a different Cisco Unified Communications Manager cluster (although the moved phones are still registered with the original Cisco Unified Communications Manager cluster), and it can also occur when the phones move within a single large campus that is served by multiple Cisco Unified Communications Manager clusters. Because the moved phones are still registered to their original Cisco Unified Communications Manager cluster, emergency calls from these phones are routed to the original Cisco ER group. In this case, the Cisco ER group detects that the calling phone is connected to a switch that is monitored by a different Cisco ER group, and the call is forwarded to the appropriate Cisco ER group through an H.323 inter-cluster trunk. Because the inter-cluster trunk does not pass the MAC address of the calling phone, the receiving Cisco ER group does not know the MAC address of the calling phone and must associate the phone to an ERL based on the calling party number. In cases with a single phone connected to the switches monitored by the receiving Cisco ER group, this is not a problem. However, when multiple phones with a shared line appearance connect to switches monitored by the receiving Cisco ER group, then Cisco ER must guess which phone has placed the emergency call. If all of the phones with a shared line appearance are in the same ERL, the guess is correct. If the phones span multiple ERLs, then the guess might be incorrect.
Related Topics

Deploying Cisco Emergency Responder In Two Main Sites, page 1-25 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17
802.11b Endpoints Using Wrong ERL

802.11b endpoints (such as Cisco Wireless IP 7920 Phones and Cisco IP SoftPhones running on 802.11b) are using switch port-based ERL instead of the configured subnet-based ERL. Cisco Emergency Responder (Cisco ER) give a higher priority to switch port association for call routing. If Cisco ER finds a switch port mapping for any endpoint (including 802.11b endpoints), it uses the switch port mapping to route emergency calls. If the switch port mapping is not found or if the ERL is not configured for the corresponding switch port, Cisco ER 1.2 routes emergency calls using subnet-ERL configuration.
11-4
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Emergency Call Problems
Be aware that Cisco ER 2.0 will locate 802.11b endpoints behind a switch port under the following conditions:

CDP (Cisco Discovery Protocol) is disabled on the access point or the switch port on which it is connected; and CAM tracking is enabled in Cisco ER for that particular switch.
See the switch port screen or the ERL debug tool (see Using The ERL Debug Tool to Verify Cisco Emergency Responder Configuration, page 11-17) to check if the 802.11b endpoint is associated with a switch port. It is recommended that you track 802.11b endpoints using subnet-based ERLs. Therefore, enable CDP on the switch port and the access points to route emergency calls from 802.11b endpoints using subnet-based ERLS.
Related Topics
Configuring IP Subnet-based ERLs, page 5-33
Troubleshooting Emergency Call Problems

These topics help you troubleshoot problems related to the routing of emergency calls and the information supplied with the calls:

Emergency Calls are Not Being Intercepted by Cisco Emergency Responder, page 11-5 ELIN not Transmitted to the PSAP, page 11-6 ELIN For Default ERL Used For Calls From Other ERLs, page 11-6 Emergency Calls Not Routed to the Correct PSAP, page 11-7 Emergency Callers Sometimes Get Busy Signal and Emergency Calls Are Sometimes Not Routed, page 11-7 PSAP Call Back Errors, page 11-8 Onsite Alert Personnel Are Not Getting Telephone Alerts, page 11-8 Onsite Alert Personnel Not Getting Email (or Paging) Notifications, page 11-9 Incorrect Location Information Sent To Onsite Alert Personnel, page 11-9 Emergency Call History Problems, page 11-10
Emergency Calls are Not Being Intercepted by Cisco Emergency Responder

If Cisco ER is not intercepting emergency calls, there is probably a mistake in your Cisco Unified Communications Manager configuration or its representation in the Cisco ER configuration. Check these items (based on the names used in the examples in Chapter 4, Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0).
The emergency call number (911) is in the Phones partition and uses the E911CSS calling search space. Ensure this number was identified during Cisco ER installation (see the Installing Cisco Emergency Responder 2.0 on a New System section on page 2-3). This ensures that users can dial the emergency number. See the Creating the Emergency Call Route Points section on page 4-6 for information on setting up the Cisco Unified Communications Manager configuration for this number.
11-5
Chapter 11 Troubleshooting Emergency Call Problems
The standby Cisco ER servers route point (912) is in the E911 partition and uses the E911CSS calling search space. See the Creating the Emergency Call Route Points section on page 4-6 for information on setting up the Cisco Unified Communications Manager configuration for this number. Ensure this number is defined as the standby servers route point in the Cisco ER configuration (see the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18). The PSAP callback route point pattern (913XXXXXXXXXX) is in the E911 partition and uses the E911CSS calling search space. See the Creating the Emergency Call Route Points section on page 4-6 for information on setting up the Cisco Unified Communications Manager configuration for this number. Ensure this number is defined as the PSAP callback route point pattern in the Cisco ER configuration, and that the strip prefix (913) is also identified (see the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18). All ELIN route patterns are in the E911 partition. See the Creating the Route Patterns for ELINs section on page 4-10 for information on setting up the Cisco Unified Communications Manager configuration for these numbers. All phones and CTI ports (both device and line) are in the Phones partition and use the PhoneCSS calling search space. You can use additional partitions, but they must be set up with relationship to the Cisco ER partitions and calling search spaces in the same manner as these partitions in the examples described in the Setting Up Cisco Emergency Responder to Handle Emergency Calls section on page 4-4. All gateways to the service providers network use the E911CSS calling search space. See the Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP section on page 4-16 for more information. The Cisco Unified CM Version (JTAPI jar) being configured is proper. To check the Cisco Unified CM version, follow these steps:
1. 2. 3.
Login to the Cisco ER Admin Utility website. Select Update > CCM Version In the Status section, check the Current Version of CCM.
ELIN not Transmitted to the PSAP

If the ELIN is not transmitted to the PSAP, and you are using a PRI connection to route emergency calls to the PSAP, check the configuration of the gateway. The PRI must be configured to send the real calling party number (which will be the ELIN) rather than a static number, such as the main site number. See the Obtain CAMA or PRI Trunks to the PSTN section on page 1-17.
ELIN For Default ERL Used For Calls From Other ERLs
If an emergency call is assigned an ELIN defined for the Default ERL rather than an ELIN assigned to the ERL whence the call was made:

Check the Cisco Unified Communications Manager configuration for the route pattern for the ELIN you expected to be used. See the Creating the Route Patterns for ELINs, page 4-10. Check the ERL definition in Cisco ER to ensure that the ELIN is correctly configured for the ERL. See the Setting Up an Individual ERL and Its Automatic Location Information (ALI) section on page 5-30.
If the route pattern for an ERL fails, Cisco ER uses the route pattern defined for the Default ERL.
11-6
OL-12376-01
Chapter 11
Emergency Calls Not Routed to the Correct PSAP

If an emergency call is not routed to any PSAP, check whether the route patterns used for the ERL from which the call was made and for the default ERL are configured and use the correct partitions and calling search spaces (see the Creating the Route Patterns for ELINs section on page 4-10). Ensure that the partitions and calling search spaces for the gateways are correct (see the Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP section on page 4-16). If an emergency call successfully leaves your network but does not get routed to the correct PSAP, look at these possible points of failure:
Is Cisco ER configured to assign the correct ELIN to the ERL assigned to the phone? Emergency calls are routed based on the ELIN, so if you assign the wrong ELIN, the call will not be routed correctly. See the Creating ERLs section on page 5-28. If the ELIN is correct, is the ELINs route pattern configured to use the correct gateway? If you select the wrong gateway, the call might be routed to a part of the service providers network that cannot connect to the desired PSAP. Consult with your service provider to determine gateway requirements. See these topics:
Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks, page 4-9 Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs, page 1-22
Does the service providers ALI database contain the correct information for the ELIN? Emergency call routing outside your network is based on the information in the service providers database, not on the information in your local network. See the Exporting ERL Information section on page 5-36. Does the emergency callers phone register with a Cisco Unified Communications Manager cluster supported by a different Cisco ER group than the Cisco ER group that supports the originating switch port? Then you might have a miss-configured Cisco ER cluster. See these topics:
Installing Cisco Emergency Responder 2.0 on a New System, page 2-3 Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page
4-17
Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18
Note
If the call reaches the PSAP, but the PSAP cannot talk to the caller, ensure that the Cisco Unified Communications Manager for the remote Cisco ER group has the Cisco Unified Communications Manager for the local Cisco ER group defined as a gateway.
Emergency Callers Sometimes Get Busy Signal and Emergency Calls Are Sometimes Not Routed
If callers hear a busy signal when calling the emergency call number, or if emergency calls sometimes do not get routed, there is probably a problem with the configuration of your standby Cisco ER server:
If you have only configured a primary Cisco ER server, install and configure a standby Cisco ER server. If CPU utilization on the primary server reaches 100%, Cisco ER cannot handle emergency calls. In this case, the standby server handles the calls.
11-7
Chapter 11 Troubleshooting Emergency Call Problems
Check the route point configuration for the standby server. Ensure the emergency call route points call forward settings are configured to forward calls to this number. See the Creating the Emergency Call Route Points section on page 4-6 for information on the Cisco Unified Communications Manager configuration, and the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18 for the Cisco ER configuration.
PSAP Call Back Errors

You might encounter these problems if a PSAP operator tries to call back an emergency caller using the ELIN provided by caller ID:
Symptom PSAP could not reach the original emergency call extension. Recommended Action Cisco ER caches a mapping between the callers true extension and the ELIN
you define for an ERL. If more calls get made than the number of ELINs you define for an ERL, Cisco ER must reuse these numbers and thus overwrites the original callers extension. You can view the call history to determine the extension of the original caller. See the What Happens When an Emergency Call Is Made section on page 1-8. If this is not the problem, check the configuration of the PSAP callback route point in Cisco Unified Communications Manager and Cisco ER (see the Creating the Emergency Call Route Points section on page 4-6 and the Configuring Group Telephony Settings For the Cisco Emergency Responder Server section on page 5-18), and the ELIN translation patterns in Cisco Unified Communications Manager (see the Creating the Translation Patterns for ELINs section on page 4-11).
Symptom Onsite alert (security) personnel get callbacks from the PSAP. Recommended Action Cisco ER routes PSAP callbacks to the onsite alert personnel for the default
ERL if ELIN-to-extension mapping for the emergency call has expired from the cache. By default, this is three hours, although you can configure expiration to be a longer or shorter time. See the Cisco ER Group Settings section on page A-3.
Onsite Alert Personnel Are Not Getting Telephone Alerts

If the onsite alert personnel are not getting telephone alerts when an emergency call is made in an ERL they are covering, ensure that all phones and CTI ports (both device and line) are in the Phones partition and use the PhoneCSS calling search space. You can use additional partitions, but they must be set up with relationship to the Cisco ER partitions and calling search spaces in the same manner as these partitions in the examples described in the Setting Up Cisco Emergency Responder to Handle Emergency Calls section on page 4-4. Also, ensure that the Cisco ER configuration for the Cisco Unified Communications Manager clusters is correct. The Cisco ER configuration should show the correct begin address for the telephony ports you defined as CTI ports in Cisco Unified Communications Manager, and the number of telephony ports should be the correct number and it must be greater than 0 for any calls to occur. Cisco ER uses this CTI ports to place the telephone calls to onsite alert personnel.
11-8
OL-12376-01
Chapter 11
If the Event Viewer in the Cisco ER Serviceability web interface displays the error message No port to place call, then there were not enough CTI ports defined to initiate all the calls to onsite alert personnel. Therefore, you must define additional ports. To access the Event Viewer, log in to the Cisco ER Serviceability web interface and select Tools > Event Viewer.
Onsite Alert Phone Does Not Ring When Emergency Call is Placed
You might encounter this problem if the onsite alert phone does not ring when an emergency call is placed:
Symptom The onsite alert phone does not ring when an emergency call is placed. Possible Cause The onsite alert phone will not ring if the Do Not Disturb (DND) feature is enabled
on the phone and if Cisco ER is configured with Cisco Unified Communications Manager 6.0.
Recommended Action Do not enable DND on an onsite alert phone.
Prompts for Phone Alerts Not Getting Played

You might encounter this problem if prompts for phone alerts are not getting played:
Symptom Prompts do not get played at the onsite alert phone when the call is initiated from the CTI ports. Explanation This problem can occur when a single CTI port is configured with multiple lines.
Prompts may not get played from one or more of these lines when the onsite alert notifications call is initiated through them.
Recommended Action To avoid this problem, configure only one line per CTI port in the
Cisco Unified Communications Manager that is configured for Cisco ER.
Onsite Alert Personnel Not Getting Email (or Paging) Notifications

If the onsite alert personnel are not getting email, or email-based pages, even though you configure email addresses for them (see the Onsite Alert Settings section on page A-10), check the Cisco ER configurations SMTP settings. Ensure that the SMTP server address and source mail ID are correct (see the Cisco ER Group Settings section on page A-3), and that there is an account for the mail ID in the SMTP server.
Incorrect Location Information Sent To Onsite Alert Personnel

If your onsite alert (security) personnel are receiving incorrect location information for an emergency call, consider these potential problems:

Is the ALI data for the ERL correct? See the Creating ERLs section on page 5-28. Is the phone location data for the switch port correct? See the Configuring Switch Ports section on page 5-47.
11-9
Chapter 11 Troubleshooting Email Alerts
Is the correct ERL assigned to the switch port to which the phone is connected? If not, there could be two problems:
Someone switched wires on the switch, so your formerly correct configuration is no longer
correct. Wires cannot be moved from port to port without potentially invalidating the ERL assignment. See the Data Integrity and Reliability Considerations section on page 1-16.
The wiring closet is secure, the ERL assignment is simply incorrect. See the Configuring
Switch Ports section on page 5-47.
Did the call come from the Default ERL (assuming you do not use the Default ERL for any permanent ERL)? This could indicate these problems:
The phone is connected to an unsupported port and is not defined as a manual phone. See the
Manually Defining a Phone section on page 5-53.

The phone is not supported and it is not defined as a manual phone. See the Manually Defining
a Phone section on page 5-53.

The phone is supported but Cisco ER could not locate it. You might have to manually assign the
phone to an ERL if you cannot resolve the problem. See the Too Many Unlocated Phones section on page 11-2.
Did the call come from a manually-defined phone extension? If so, it is likely the incorrect ERL is assigned, perhaps because the phone moved. See the Manually Defining a Phone section on page 5-53.
Emergency Call History Problems

These are some issues you might encounter when viewing the emergency call history information (see the Viewing the Emergency Call History section on page 5-57):
Symptom Emergency call information does not show up in call history right away. Recommended Action Cisco ER writes call history information to the database every 15 seconds. You
should be able to view history information after 15 seconds.
Symptom The call history does not show the ELIN and route pattern used for a call. Recommended Action If the call could not be routed to the PSAP, you will not see an ELIN or route
pattern. Check to determine why the call could not be routed. See the Emergency Calls Not Routed to the Correct PSAP section on page 11-7.
Troubleshooting Email Alerts

These topics help you troubleshoot problems related to the email alerts that Cisco ER generates:

Emergency Call Alert, page 11-11 Transition Alert, page 11-11 Tracking Failure, page 11-12 Failed To Get Provider, page 11-12
11-10
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Email Alerts
Failed to Establish Communication with Cisco Emergency Responder Phone Tracking Engine, page 11-12 Lost Communication with Cisco Emergency Responder Phone Tracking Engine, page 11-13 Failed to Send Unlocated Phone Details to Remote Cisco Emergency Responder Server Group, page 11-13 Emergency Call Could Not be Routed, page 11-13 Calling Party Modification Failed, page 11-14
Emergency Call Alert

Whenever a user makes a 911(Emergency) call, Cisco ER generates an email alert. Cisco ER sends the email alert to all of the onsite alert (security) personnel whose email ids are configured for the ERL from which the call was made. (See the Configuring a Cisco Emergency Responder Server Group section on page 5-16.) Security personnel are expected to respond to that user. For detailed call information, refer to the following URL: http://<<CERServer HostName>>/ceruserreports When a 911 call is made and the backup Cisco ER server handles the call, an alert similar to the following is sent:
Subject: Emergency Call Alert -- Extn # 332101 (Generated by Backup Cisco ER) Message: EMERGENCY CALL DETAILS (Generated by Cisco ER) Caller Extension:332101 Zone/ERL :Z1 Location :ddd Call Time :June 2, 2003 3:47:30 PM IST
Transition Alert
When the standby Cisco ER server takes control and becomes the active server, a Transition Alert is sent to the Cisco ER administrator. This situation occurs under any of the following circumstances:

If the primary Cisco ER server is stopped. If the Cisco ER service is stopped on that server. If the connectivity between primary and standby Cisco ER servers is broken.
The administrator should diagnose the cause and fix the problem as soon as possible. When the Cisco ER backup server takes control, an alert similar to the following is sent:
Subject: Transition Alert: Cisco ER Backup is active Message: Backup Cisco ER <<CERServer HostName>> has taken control as Active Cisco ER. Transition Time :June 2, 2003 3:57:12 PM IST
When the master Cisco ER server takes control, an alert similar to the following is sent:
Subject: Transition Alert: Cisco ER Master is active Message: Master Cisco ER <<CERServer HostName>> has taken control as Active Cisco ER. Transition Time :June 2, 2003 3:57:12 PM IST
11-11
Chapter 11 Troubleshooting Email Alerts
Tracking Failure
At the end of a switch-port and phone tracking process, if there are any devices that could not be tracked, Cisco ER sends a Tracking Failure email to the Cisco ER administrator. The administrator should look at the event log on the Cisco ER server to find the list of devices that were not tracked. Then the administrator should check the following and make any required corrections:
1. 2. 3. 4.
Make sure that the correct SNMP Community String is configured in Cisco ER. Check that the device is connected. Check that the host name for the Cisco ER server is resolvable, that is, it can be found. Check that the SNMP service is enabled on that particular device (Switch / Cisco Unified Communications Manager).
Here is an example of a tracking failure alert.

Subject: CER Phone Tracking failed to track some devices Message: CER Phone Tracking could not get information [using SNMP] from 2 Cisco CallManager(s) and 1 Switch(es) Check Event Viewer on CER Server for details.
Failed To Get Provider

Cisco ER sends a Failed to Get Provider Alert to the Cisco ER administrator if Cisco ER is not able register to one of the configured Cisco Unified Communications Manager clusters. Cisco ER will continue trying registration until it succeeds. Cisco ER sends the Failed to Get Provider email after a few retries. The message provides information on how to clear the problem, as shown in the following example.
Subject: Failed to get JTAPI Provider for Cisco CallManager <<CCM IP/Host Name>> (Generated by Backup CiscoER) Message: Please check the following: 1) Check if the Cisco CallManager is connected to the CER server. 2) Check if the configured Call Manager is running a version supported by the CER server. 3) Check if the given login credentials are correct: CTI Manager Host Name:<<CCM IP/HostName>>
Failed to Establish Communication with Cisco Emergency Responder Phone Tracking Engine
Cisco ER sends this email alert to the Cisco ER administrator if the Cisco ER server fails to establish communication with the Phone Tracking Engine for some time. This can occur if the Cisco ER Phone Tracking Engine service is down. The administrator should perform the following steps:
1. 2.
If the Cisco ER Phone Tracking Engine service is down, start the service. Make sure that the Host Name of the Cisco ER server does not contain any underscore (_) characters.
Here is an example of a tracking failure alert.

Subject: CER Server failed to establish communication with CER Phone Tracking Engine. Message: CER Server could not communicate with CER Phone Tracking Engine.
11-12
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Email Alerts
Lost Communication with Cisco Emergency Responder Phone Tracking Engine

Cisco ER sends this email alert to the Cisco ER administrator if the Cisco ER server loses communication with the CER Phone Tracking Engine. This is most liked to occur if the Cisco ER Phone Tracking Engine service goes down when the Cisco ER server is running. The administrator should restart the Cisco ER Phone Tracking Engine service. The following shows an example of a tracking failure alert.
Subject: CER Server lost communication with CER Phone Tracking Engine Message: CER Server could not communicate with CER Phone Tracking Engine.
Failed to Send Unlocated Phone Details to Remote Cisco Emergency Responder Server Group
If Cisco ER fails to send unlocated entries to a server group because it is already in the process of sending entries to that server group, this alert is sent. This alert will occur very rarely. It can occur when a Cisco ER server is found in more than one Cisco ER server group. To resolve this problem, check to see which server group is an old configuration and remove that server group.
Subject: CER Server failed to send Unlocated Phones details to Remote CER Server Group. Message: CERServer failed to send Unlocated Phones to Remote CER Server Group. Please ensure that the CER servers are not found under more than one CER Server Group. CER Servers in Remote Server Group:<< CERServer HostNames >>
Emergency Call Could Not be Routed

If the emergency call routing to some route patterns configured in the ERL fails, Cisco ER sends an email to the system administrator. Subject: Emergency call could not be routed using some route patterns (CERServer:<server hostname>) Message Body: Emergency call from :<Caller Extn> could not be routed using some Route Patterns. Check Event Log. The Event Log displays the following message:
Emergency call from <extn> could not be routed using the following route patterns <RoutePattern1> <RoutePattern2> ***************** Call Routed to <RoutePattern-X> Please check the availability of the above routes. Also, check for the following error conditions: 1. If FAC and/or CMC are configured on the route patterns used for Cisco ER, please disable them. 2. If the Calling Party Number Modification flag on the CER user page in the CallManager is not enabled, please enable it.
11-13
Chapter 11 Troubleshooting Web Alerts
Solution 1. 2. 3.
If you are running Cisco Unified CallManager 4.2 or 4.3, check to make sure that the Calling Party Number checkbox on the Cisco ER User page is checked. If you are running Cisco Unified CallManager 5.x or Cisco Unified Communications Manager 6.0, check to make sure that the routes are available. Add the Cisco ER Application User to the Standard CTI Allow Calling Number Modification user group.
Calling Party Modification Failed

If the calling party modification was not successful, Cisco ER sends the following email to the system administrator: Subject: Emergency Calling Party Modification Failed (CERServer: <server>) Message Body: Emergency call from :<Caller Extn> cannot be routed with calling party modification. Check Event Log. The Event Log displays the following message:
Emergency Call from <Caller Extn> has been modification failed. Please make sure that the checkbox Enable on the Cisco CallManager user page for the correctly. The CER service will need to be CallManager User page. routed to default ERL because the calling party Calling Party Number Modification: is checked CER user. PSAP callbacks MAY NOT work restarted once the flag is checked on the
Solution Check the box for the Enable Calling Party Number Modification in the Cisco ER user page
in Cisco Unified CallManager 4.2 or 4.3 Administration. After you enable this flag, restart the Cisco ER service for the changes to take effect.
Troubleshooting Web Alerts

You might encounter this problem when receiving web alerts:
Symptom Web alert continues to refresh every 30 seconds. You can see this problem by checking the status in the browser. The status will display the seconds remaining before refresh if it is in this mode. Recommended Action Check if there are other web alert screens open on the same client machine.
Only one browser from a client machine can operate in the real-time mode. Remove any extra browsers.
11-14
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Cisco Emergency Responder System and Administration Problems
Troubleshooting Cisco Emergency Responder System and Administration Problems

These topics help you troubleshoot problems related to the Cisco ER system and its administration, such as server and web server problems:

Cannot Validate Publisher, page 11-15 Troubleshooting Login Problems, page 11-15 Using Cisco Unified Operations Manager, page 11-16 Troubleshooting Cisco Emergency Responder Switch and Port Configuration Problems, page 11-16 Using The ERL Debug Tool to Verify Cisco Emergency Responder Configuration, page 11-17 Replacing the Publisher Server and Subscriber Servers, page 11-18 Using the Cisco Emergency Responder Admin Utility, page 11-19 Troubleshooting the Database and Enterprise Replication, page 11-20 Troubleshooting Cisco Emergency Responder System Problems, page 11-21 Troubleshooting Cisco Unified Communications Manager Configuration Problems, page 11-21
Cannot Validate Publisher

If the installation cannot validate the Publisher (Step 5 of the Installing the Cisco Emergency Responder Subscriber section on page 2-8), check the following:
1. 2. 3. 4.
Verify that the Publisher hostname is correct and that the Publisher is reachable by hostname. Verify that the Publisher and Subscriber servers are running the same version of Cisco ER. Verify that the database password that you entered is correct. This password was specified on the Database Access Security Configuration page during installation. Make sure that the Subscriber has been configured correctly on the Publisher.
Troubleshooting Login Problems

These are some issues you might encounter while logging into Cisco ER:
Symptom You cannot log in to the Cisco ER Administration website. Recommended Action Log in to CLI and run the utils service list command. Check if the status
Cisco IDS is STARTED. If not, start the service using the utils service start service name command.
Symptom You cannot open multiple Cisco ER sessions using Netscape Navigator. Recommended Action Netscape/Mozilla Navigator uses the same session ID across multiple
windows. This creates problems if you try to log into Cisco ER using different IDs. Normally, you can open multiple windows when logged in as system administrator. With Internet Explorer, if you
11-15
Chapter 11 Troubleshooting Cisco Emergency Responder System and Administration Problems
open separate IE session by starting a new IE instance (rather than by opening a new window from an existing session), IE uses different session IDs, and you should be able to log in using separate IDs (for example, as a user and an administrator, or as LAN switch and ERL administrators).
Related Topics
Using The ERL Debug Tool to Verify Cisco Emergency Responder Configuration, page 11-17
Using Cisco Unified Operations Manager

Use Cisco Unified Operations Manager 2.01 to continuously monitor the health of the Cisco ER system. For information on setting up Cisco ER to use Cisco Unified Operations Manager, see the Configuring Test ERLs section on page 5-34. For information on installing and using Cisco Unified Operations Manager, see the documentation at: http://www.cisco.com/en/US/products/sw/cscowork/index.html
Troubleshooting Cisco Emergency Responder Switch and Port Configuration Problems

Some issues that you might encounter while configuring switches or switch ports in Cisco ER are shown below:
Symptom Cisco ER is configured with Cisco Unified Communications Manager information, but no phones get discovered. Recommended Action Ensure that the Cisco Unified Communications Manager servers are reachable on the network. Then, ensure that the SNMP read community strings are configured correctly for the switches and Cisco Unified Communications Manager servers (see the Configuring the SNMP Connection section on page 5-39.) Then, manually run the switch port and phone update process (see the Manually Running the Switch-Port and Phone Update Process section on page 5-45.) Use the CLI-based utils snmp command to determine if the Cisco Unified Communications Manager is SNMP reachable.
Symptom Cisco ER does not show the ports on a switch configured in Cisco ER. Recommended Action If you add a supported switch to Cisco ER and run phone tracking on the switch after adding it, you should be able to view the list of Ethernet ports on the switch. If Cisco ER does not list the ports, check the SNMP settings in Cisco ER for the switch (see the Configuring the SNMP Connection section on page 5-39.) Also, verify that the switch is reachable over the network. Retry the selective phone tracking process on the switch (click Locate Switch Ports when viewing the switch details; see the LAN Switch Details section on page A-28.)
If the problem persists, ensure that the switch is supported (see the Network Hardware and Software Requirements section on page 1-4.) Also, check the Event Viewer for error messages.
11-16
OL-12376-01
Chapter 11
Symptom Some phones do not appear in the switch port list. Recommended Action Check if the phone is found under configured IP subnets or in synthetic phones.
If it is not found in either of those places, then they will be place un unlocated phones. See the Too Many Unlocated Phones section on page 11-2 for a list of reasons that a phone could not be located.
Symptom Cannot delete a switch from the Cisco ER configuration. Recommended Action You cannot delete a switch when a phone tracking process is in progress. Retry the deletion after the process has ended. If this is not the problem, the Cisco ER server might not be running. Check the control center and restart the server (see the Starting and Stopping a Cisco Emergency Responder Server section on page 11-23.)
Symptom Import or export of the switch port details fails. Recommended Action If a switch port import or export attempt fails, it might be due to these reasons:
the first switch-port and phone update process has not yet ended (wait for it to finish); the Cisco ER server is not running (use the control center to restart it, see the Starting and Stopping a Cisco Emergency Responder Server section on page 11-23); the Cisco ER server is not completely initialized (wait for it to initialize).
Symptom The import of some switch port configurations fail. Recommended Action To import switch port configurations, Cisco ER must already be configured
with the switch and Cisco ER must first discover the ports on the switch using the switch-port and phone update process. If you try to import a configuration for ports not yet discovered in Cisco ER, the importation of those settings fails. See the Manually Running the Switch-Port and Phone Update Process section on page 5-45 for information on the process. Run it on the switches whose port configurations you could not import, then retry the import.
Symptom Phones moved from other Cisco ER groups to this Cisco ER group, and then moved back, are still showing up in the switch port details for the Cisco ER group. Recommended Action This types of phones are not removed from the switch port details until the next
full switch-port and phone update process is run. If this is an issue for you, you can run the process on the switch (or on all switches) manually. See the Manually Running the Switch-Port and Phone Update Process section on page 5-45.
Using The ERL Debug Tool to Verify Cisco Emergency Responder Configuration
The ERL Debug Tool takes a phone extension as the search criteria and displays the ERL(s) currently being used for routing emergency calls for the phone(s). Use this diagnostic tool to verify the Cisco ER configuration during the ERL creation and the ERL assignment phase, and to troubleshoot calls directed to incorrect ERLs. For example, you configured the phone in ERL_1 as a manually configured phone, however a misconfigured IP subnet matches this phone's IP address, and associates it with ERL_2. Now that you have found the configuration problem using the Debug Tool, you can correct it.
11-17
To use the ERL Debug Tool, follow these steps.

Procedure
Step 1
Select Tools > ERL Debug Tool. Cisco ER displays the ERL Debug Tool page. At the Find Phones field, to list specific phones, select the search criteria and click Find. Cisco ER displays the ERL currently being used for routing emergency calls for the phone. If the configurations are not correct, make the required changes.
Step 2
Step 3
Note
Cisco ER displays a maximum of 1,000 records.
Replacing the Publisher Server and Subscriber Servers

If you need to replace a faulty Publisher server or a faulty Subscriber server, perform the appropriate procedure:

Replacing a Faulty Subscriber, page 11-18 Replacing a Faulty Publisher, page 11-18
Replacing a Faulty Subscriber

To replace a faulty Subscriber, go to Cisco ER administration and delete the faulty Subscriber. Install a new Cisco ER Subscriber for the Publisher (see the Installing Cisco Emergency Responder 2.0 on a New System section on page 2-3).
Note
If the same host name is not going to be used by the replacement Subscriber server, you must delete the faulty Subscriber using the Cisco ER administration screen on the Publisher server.
Replacing a Faulty Publisher

You can restore the Publisher only if you have backed up the Publisher using the Disaster Recovery System available as part of the Cisco ER. See the Backing Up and Recovering Data section on page 11-31. To replace a faulty Publisher, follow these steps:
Procedure
Step 1 Step 2
Install the same version of the Cisco ER Publisher on a server with the same host name as the one you used previously. Choose the same configuration options (such as the Cisco Unified Communications Manager version, and so on) during the installation.
11-18
OL-12376-01
Chapter 11
Step 3
Restore the old configuration data using the Disaster Recovery System.
Using the Cisco Emergency Responder Admin Utility

You can use the Cisco ER Admin Utility tool to perform the following tasks:

To point a Subscriber to a different Publisher To update Cisco ER cluster database host details To upgrade the CCM version
This section describes the following topic:
How to Use the Cisco ER Admin Utility Tool, page 11-19
How to Use the Cisco ER Admin Utility Tool

To use the Cisco ER Admin Utility tool, follow these steps:
Procedure
Step 1 Step 2
Log in to the Cisco ER Admin Utility web interface. Using the menu bar, choose a task to perform:
a. b. c.
To change the Publisher that the Subscriber server points to, select Update > Publisher. To update the Cisco Unified Communications Manager version, select Update > CCM Version. To update the cluster settings on both the Publisher and Subscriber servers, select Cluster > DBHost.
Note
This action updates the Cisco ER cluster DB details for this server group only. Other servers in this Cisco ER cluster will NOT be updated automatically.
Step 3
To save the changes that you have made, restart both the Publisher and the Subscriber servers.
Troubleshooting the Subscriber Database Setup

To configure the Publisher-Subscriber setup again if you have an issue with the Subscriber (apart from DB replication), follow these steps:
Procedure
Log in to the Cisco ER Admin Utility web interface on the Subscriber server. Select Update > Publisher. Specify the same Publisher Host Name, IP address (already being pointed to) and database access security password. Click Go.
11-19
This step might a take a while setup.
Troubleshooting the Database and Enterprise Replication

Use the following CLI commands for troubleshooting the Informix Dynamic Server (IDS) database:

utils service listUsed to check whether the IDS service is running or not show tech dbstateinfoGives the DB state information which is helpful in debugging database issues show tech dbinuseDisplays the currently used database show tech dbintegrityShows database integrity information show tech databaseCreates a .csv file with contents of all the tables in the database utils dbreplication statusUsed to show the status of the database replication utils dbreplication resetResets and restarts the database replication between the Publisher and Subscriber utils dbreplication repairCompares the data on replication servers (Publisher and Subscriber) and create a report listing data inconsistencies and repairs the data inconsistencies. This command also tries to repair replication by rebuilding the corrupted .rhosts file if it is corrupted for some reason.
Use the following CLI commands for troubleshooting Enterprise Replication:

For troubleshooting database problems using logs, download logs from the Cisco ER Serviceability website or through CLI. The following logs provide information for debugging database related issues

Install/Upgrade logs/var/log/install/ Install DB logs/var/log/active/er/trace/dbl/sdi/ CERDbMon logs/var/log/active/er/trace/dbl/sdi/cerdbmon/ CLI logs/var/log/active/platform/log/
Symptom Replication fails to start after the Subscriber is installed with DNS and the CLI command utils dbreplication status shows replication not working. Possible Cause The .rhosts will have the Host Name for the Subscriber instead of FQDN (Fully Qualified Domain Name) of the Subscriber. Recommended Action Use the CLI command utils dbreplication repair to repair the replication
issue. This command tries to repair replication by rebuilding the corrupted .rhosts file.
11-20
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Cisco Emergency Responder System Problems
Troubleshooting Cisco Emergency Responder System Problems

These are some issues you might encounter with general operation of the Cisco ER system and the configuration screens that involve the Cisco ER server, group, and cluster:
Symptom Cisco ER intra-cluster call routing fails or Cisco ER does not discover phones correctly. Recommended Action Ensure that all the Cisco ER servers in a Cisco ER cluster can be found by their
host name, and ensure that all are reachable on the network by all the other Cisco ER servers.
Recommended Action Ensure that all the Cisco ER servers can reach the Cisco ER cluster DB host
and that the cluster DB password is the same across all servers in the cluster.
Symptom Cisco ER exits after starting. Possible Cause You have configured Cisco ER to use a TCP port that is already in use. Recommended Action Check the Windows Event Viewer for the message Cisco ER could not open
socket at port peer-tcp-port, Exiting. If you see this message, change the Cisco ER group configuration to use a different TCP port. See the Configuring a Cisco Emergency Responder Server Group section on page 5-16 for instructions.
Symptom The Cisco ER Groups in Cluster screen does not load, and exhibits the error Cannot connect to cluster DB host. Recommended Action Ensure that the cluster DB host can be found by host name.
Ensure that the specified cluster db host password is the same across all Cisco ER server groups in the cluster. For more information, see the Configuring the Cisco Emergency Responder Cluster and Cluster DB Host section on page 5-23.
Related Topics

Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster, page 11-22 Starting and Stopping a Cisco Emergency Responder Server, page 11-23 Viewing Event Messages, page 11-29 Managing Performance, page 11-29 Backing Up and Recovering Data, page 11-31
Troubleshooting Cisco Unified Communications Manager Configuration Problems

These are some issues that you might encounter with Cisco ERs communications with Cisco Unified Communications Manager. Additional problems with symptoms that involve emergency call failures are discussed in the Troubleshooting Emergency Call Problems section on page 11-5.
11-21
Chapter 11 Troubleshooting Cisco Emergency Responder Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster
Symptom Cisco ER does not register with the route points and CTI ports configured for its use. Recommended Action Ensure that the route points and CTI ports are associated with the
Cisco Unified Communications Manager Cisco ER user (see the Creating a Cisco Emergency Responder Cisco Unified Communications Manager User section on page 4-19.) Ensure that the CTI Manager on the Cisco Unified Communications Manager server (or the DC Directory on a Windows-based Cisco Unified CallManager server) is running properly.
Symptom When trying to delete a Cisco Unified Communications Manager from the Cisco ER configuration, Cisco ER prevents me and displays the message Phone tracking in progress. Recommended Action You cannot delete a Cisco Unified Communications Manager server from the
Cisco ER configuration while a phone tracking process is in progress. Retry the deletion after the process has ended.
Updating Cisco Emergency Responder After You Add Devices
You must create a Cisco Unified Communications Manager user for Cisco ERs use and CTI ports and route points that need to be assigned to the user before Cisco ER tries to create a provider with the Cisco ER cluster. Cisco ER only registers the CTI ports and route points that are associated with the user when the provider is created. Thus, any devices you add to the user after starting Cisco ER will not be registered by Cisco ER. If you add devices to the Cisco ER user in Cisco Unified Communications Manager, you can force Cisco ER to recreate the provider using any of these techniques:

Restart the Cisco ER server. Delete the Cisco Unified Communications Manager server from the Cisco ER configuration and re-enter it. Change the backup CTI Manager setting for the Cisco Unified Communications Manager server in the Cisco ER configuration and click Update. This forces Cisco ER to log off the provider and recreate it. Change the name of the user in Cisco Unified Communications Manager, or create a new user, and associate all devices with it. Then update the Cisco ER configuration to use the new user.
Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster
If you are connected to the administrators interface on a Cisco ER server, you can view the details of the server and the Cisco ER groups standby server by selecting System > Cisco ER Group Settings. You can also identify the Cisco ER groups and their Cisco ER servers that are in the same Cisco ER cluster. To view the other Cisco ER groups in the cluster, select System > Cisco ER Groups in Cluster. From the Cisco ER Groups in Cluster page, select the group you want to view; and Cisco ER displays the Cisco ER servers that are in the group. To view the details for these servers, you must log in t to the Cisco ER Administration interface running on one of the servers, select System > Cisco ER Groups in Cluster, then select the group you want to view from the list of groups.
11-22
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Phones Moving Between Clusters
If you need to uninstall a Cisco ER group, first delete the group from the Cisco ER cluster using this page. You must log in as a system administrator to delete the group. Deleting the group from the cluster simply removes the entries for the group from the Cisco ER Cluster DB; it does not remove Cisco ER from the groups servers.
Related Topics
Cisco ER Server Groups in Cluster, page A-2
Phones Moving Between Clusters

The following scenario illustrates how Cisco ER clusters work and how Cisco ER treats phones moving between clusters:
Server Group A (SGA) has a phone (Phone_1) that is moving out of SGA.
Cisco ER discovers Phone_1 in Server Group B (SGB). The Unlocated Phones page in SGA will display the phone in SGB.
If both the Cisco ER servers (Publisher and Subscriber) in SGB go down, SGA will still display Phone_1 in SGB.
Calls made from Phone_1 during this time will be redirected to SGB and Cisco ER will take the
same steps to route this emergency call when Cisco ER servers are not there in SGB.
Phone_1 will also be treated like any other phone in SGB when both the SGB Cisco ER servers
are down.
If Phone_1 moves to Server Group C (SGC):

It will be discovered after the next incremental phone tracking on SGA and then in SGC. The Unlocated Phones page will change the association of Phone_1 to SGC.
If Phone_1 moves back to SGA, it will be discovered in the next incremental phone tracking and displayed under the corresponding switch port.
Starting and Stopping a Cisco Emergency Responder Server

When you install Cisco ER, the Cisco ER server is set up to automatically start whenever the computer is powered up or rebooted. However, you can stop and then restart a Cisco ER server through the Cisco ER Serviceability web interface without powering down or rebooting the computer. You might find this helpful if you are trying to debug a problem. To start or stop a Cisco ER server, follow these steps:
Procedure
Step 1
Log in to the Cisco ER Serviceability web interface and select Tools > Control Center. The Control Center Services page displays, showing all Cisco ER services and the current status of each one.
Step 2
Click the radio button to the left of the service name, then click Start, Stop, or Restart to perform the desired action on the service. Click Refresh to refresh the screen with updated information.
11-23
Chapter 11 Troubleshooting ALI Data Uploads
Note
The buttons only appear if the action is possible; for example, Start only appears if the service is currently stopped.
Note
The Cisco Tomcat and Cisco IDS services cannot be started or stopped from the Control Center. These services can only be started or stopped using the utils service command. For additional information, see the utils service section on page F-51. Table 11-1 explains the meaning of the icons you see on the Control Center Services page.
Table 11-1 Cisco Emergency Responder Control Center Icons
Icon
Meaning The Cisco ER server or the CER Phone Tracking Engine is started and functioning normally. The Cisco ER server CER Phone Tracking Engine was stopped by the administrator.
Related Topics
Control Center, page B-1
Troubleshooting ALI Data Uploads

Periodically, you must export your ALI data and submit it to your service provider. The ALI data is used to route emergency calls from your network to the correct PSAP, and provide the PSAP with information about the location of the emergency call. Cisco ER lets you export the ALI data in a variety of NENA formats. Ask your service provider which format you should use. During the upload process, you might find that some ALI data records did not upload correctly. Your service provider should be able to provide you with a list of errors, or you might see these when using your service providers data upload software. You must fix any mistaken records and resubmit the ALI data export file. To fix the records, you might need to manually edit the records in error. These sections describe the general procedure for fixing ALI data records, and explain how to edit the various types of NENA formatted files:

Fixing ALI Data Records, page 11-25 Editing NENA 2.0 and 2.1 File Formats, page 11-25 Editing NENA 3.0 File Formats, page 11-26
11-24
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting ALI Data Uploads
Fixing ALI Data Records

To correct data errors you might receive when uploading ALI records to your service provider, follow these steps:
Before You Begin
Obtain NENA Doc 02-010, Recommended Formats and Protocols for Data Exchange, from NENA or your service provider. This document explains the various NENA formats in detail.
Procedure
Step 1 Step 2
Look through the error reports to determine the problems you encountered. Cisco ER web interface, change the fields that were in error for the ERL/ALI records that failed. For example, if the Street Suffix was an unacceptable abbreviation, change it to an acceptable one. Save all of your changes. Export the ALI data again (see the online help). If any of the records in error were new, you must change the database function for the records. Because Cisco ER has already exported these records, Cisco ER will label them as updates rather than new insertions. However, because these records failed on upload, the service providers database will view them as new. Open the ALI export file in a text editor and change the function code for the records that you are fixing. Use an editor that will not add formatting or other extra characters. See these sections for details about editing the files:

Step 3 Step 4
Editing NENA 2.0 and 2.1 File Formats, page 11-25 Editing NENA 3.0 File Formats, page 11-26
Step 5
Submit the edited file to your service provider.
Editing NENA 2.0 and 2.1 File Formats

The NENA 2.0 and 2.1 file formats have these characteristics:

Fixed-length records Fields are in a specific order Unused fields are filled with blanks End of record is indicated by an asterisk (*)
Use NENA Doc 02-010, Recommended Formats and Protocols for Data Exchange, to determine the byte location and length of each field. When you edit the file, ensure that you are not lengthening the records. Delete any extra spaces that get added. If the length of an item is less than the length of a field, pad the field with blanks. Depending on the field, padding might be on the right or the left. The file contains one header and one trailer record. The ALI data records are contained between these records. Table 11-2 describes the fields you are most likely to edit. You should use the Cisco ER web interface to change the other fields.
11-25
Chapter 11 Troubleshooting ALI Data Uploads
Table 11-2
NENA 2.0 and 2.1 Common Fields
Field Function Code
Description Location: Byte 1. Length: 1 character. Description: The database function for the record. One of:

IInsert new ALI record CChange existing record. You must have successfully uploaded the record once before you can use C. If you are correcting a record that has never been successfully uploaded, change the C to an I. DDelete the record. Cisco ER only generates a deletion record once, in the export file created after you deleted the ALI from the Cisco ER configuration. If you need to regenerate the record, cut and paste it from the previous export file (and adjust the record count), or recreate the ALI in Cisco ER, save it, export the data, then delete the ALI and export the data again.
Cycle Counter (sequence Location: Byte 62 to 67. number) Length: 6 characters. Description: The sequence number of the file you are submitting to the service provider (for example, 1, 2, etc.) The number is right-aligned with leading spaces. Your service provider might ignore this field. Record count Location: Byte 62 to 70 in the trailer record. Length: 9 characters. Description: The total number of records in the file you are submitting to the service provider (for example, 1, 2, etc.) The number is right-aligned with leading spaces.
Editing NENA 3.0 File Formats

The NENA 3.0 file format has these characteristics:

Variable-length records. Fields are a tag and data combination, and can be in any order. Unused fields are not included. The presence or absence of a tag has this effect:
If the tag is not included, the previous value of the element, if any, is left unchanged. If the tag is included with a blank value, any previous value for the element is removed. If the tag is include with a non-blank value, the value of the element is changed to the new value.
Tags are separated by a vertical bar (|). End of record is indicated by a pre-defined character.
Use NENA Doc 02-010, Recommended Formats and Protocols for Data Exchange, to determine tag name and values for each field. Ensure that your values do not exceed the maximum length for the field. You do not need to pad fields with extra blanks.
11-26
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Collecting Call History Logs
The file contains one header and one trailer record. The ALI data records are contained between these records. Table 11-3 describes the fields you are most likely to edit. You should use the Cisco ER web interface to change the other fields.
Table 11-3 NENA 3.0 Common Fields
Field Function Code
Description Tag: FOC. Description: The database function for the record. One of:

IInsert new ALI record (FOCI) CChange existing record (FOCC). You must have successfully uploaded the record once before you can use C. If you are correcting a record that has never been successfully uploaded, change the C to an I. DDelete the record (FOCD). Cisco ER only generates a deletion record once, in the export file created after you deleted the ALI from the Cisco ER configuration. If you need to regenerate the record, cut and paste it from the previous export file (and adjust the record count), or recreate the ALI in Cisco ER, save it, export the data, then delete the ALI and export the data again.
Cycle Counter (sequence Tag: CYC. number) Description: The sequence number of the file you are submitting to the service provider (for example, CYC1, CYC2, etc.) Your service provider might ignore this field. Record count Tag: REC in the header and trailer records. Description: The total number of records in the file you are submitting to the service provider (for example, REC1, REC2, etc.)
Collecting Call History Logs

Cisco ER maintains extensive call history logs, which include entries for each emergency call handled. You can view call history information from the administration and user interfaces. Cisco ER maintains in its database a history of the emergency calls that have been placed. When the primary Cisco ER server (Publisher) is not active, emergency calls are handled by the backup Cisco ER server (Subscriber). Through replication, the call history records on both these servers are synchronized when they are active. For this reason, the call history can be viewed on either of the Cisco ER servers. To download these records, click on the Download button at the top of the table displaying the call history. These records are downloadable in Excel (.xls) format.
Collecting Trace and Debug Information

When you contact Cisco Technical Support for help with a problem that you are having with Cisco ER, Cisco might request that you collect trace and debug information.
11-27
Chapter 11 Collecting Trace and Debug Information
Because collecting trace and debug information will affect Cisco ERs performance, you should only turn on tracing and debugging at Ciscos request. The generated information is for Ciscos use in resolving product problems. Use the following sections to learn about:

Collecting Trace and Debug Information, page 11-27 Enabling Syslog, page 11-29
Enabling Detailed Trace and Debug Information for Cisco Emergency Responder
To enable detailed trace and debug information for Cisco ER, follow these steps:
Procedure
Step 1
From the Cisco ER web interface, select Cisco ER Group > Server Settings. Cisco ER opens the Server Settings page. From the left column, select the server from which you need to collect debug or trace information. Cisco ER displays the settings for the server.
Step 2
Step 3
Scroll down to the debug package and trace package sections and select the packages that Cisco Technical Support has requested. The lists in each section are identical; make sure that you select the package in the list that Cisco requested. Packages selected in the Debug list generate trace information plus extra debug data. If Cisco requests that you select all packages, click Select All for the appropriate list. The available packages include:

CER_DATABASEThe database subsystem, covers the log information generated by the database access code. CER_REMOTEUPDATEThe remote update subsystem, which manages updates between servers. CER_PHONETRACKINGENGINEThe phone tracking subsystem, which runs the phone tracking and switch-port and phone update processes. CER_ONSITEALERTThe onsite alert subsystem for notifying onsite alert personnel. CER_CALLENGINEThe call engine subsystem, which routes and processes calls. CER_SYSADMINThe system administration web interface subsystem. CER_TELEPHONYThe telephony subsystem, used for interactions with Cisco Unified Communications Manager. CER_AGGREGATORThe aggregator module covers all Cisco ER server communication and data handling with the phone tracking engine. The module includes the search and lookup of tracked data for the subsystems like cluster, Administration, Cisco IP SoftPhone and call routing. CER_GROUPThe Cisco ER server group subsystem, used for communicating between servers within a group. CER_CLUSTERThe server cluster subsystem, used for communicating between Cisco ER groups in a cluster.
Step 4
Click Update to save and activate your changes.
11-28
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Viewing Event Messages
Cisco ER begins generating the requested trace and debug information.
Note
The traces for Cisco ER can be collected from either Cisco ER Serviceability web interface or by using the command line interface.
Step 5
When you have finished generating debug and trace information, click Clear All for each section in which you have made a selection to turn off debug and trace. Then, click Update to complete the change.
Related Topics

Server Settings for CERServerGroup, page A-6 Appendix B, Serviceability Web Interface For Cisco Emergency Responder Appendix F, Command Line Interface
Enabling Syslog
To collect trace and debug information, you must enable syslog for Cisco ER). To enable syslog for Cisco ER, see the Collecting Information from Syslog section on page 11-31.
Viewing Event Messages

You can view Cisco ER event messages to help diagnose problems with the software by using the Cisco ER Serviceability web interface. For information on viewing Cisco ER events, see the Using the Event Viewer section on page 6-2. For details on the Find and List Events page, see the Event Viewer section on page B-2.
Managing Performance
Refer to the Release Notes for Cisco Emergency Responder 2.0 for supported Cisco MCS Unified Communications Manager Appliance platforms and their Cisco ER scalability. Cisco ER performance can be affected if Cisco ER is managing switches across a WAN link. Cisco ER must send SNMP requests to the managed switches, and WAN delays can lead to SNMP timeouts and increase the time needed to track phone and switch changes. You might need to tune the SNMP parameters. See the Configuring the SNMP Connection section on page 5-39 for more information.
Integrating with Network Management Systems

You can manage the status of the Cisco ER server remotely using CiscoWorks2000 or another SNMP-based network management system. CiscoWorks2000 is the standard Cisco network management system, but it is not bundled with Cisco ER. For more information about CiscoWorks2000, Campus Manager, and Topology Services, refer to the documentation, available at the following URL: http://www.cisco.com/en/US/products/sw/netmgtsw/tsd_products_support_category_home.html
11-29
Chapter 11 Integrating with Network Management Systems
These topics provide information to assist you in integrating Cisco ER with network management systems:

Understanding CDP Support, page 11-30 Monitoring Cisco Emergency Responder Subsystem Status, page 11-30 Collecting Information from Syslog, page 11-31
Understanding CDP Support

Cisco ER uses the Cisco Discovery Protocol (CDP) to periodically send out CDP messages, on the active interface, to a designated multicast address. These messages contain information such as device identification, interface name, system capabilities, SNMP agent address, and time-to-live. Any Cisco device with CDP support can locate a Cisco ER server by listening to these periodic messages. Using information provided through CDP, the CiscoWorks2000 Server can detect the Cisco ER server, and the Campus Manager application, Topology Services, can build topology maps displaying the Cisco ER server. In addition to sending out CDP messages, the Cisco ER server uses CDP to locate phones that support CDP. You must ensure CDP is enabled on your switches so that Cisco ER can obtain this information through SNMP queries to the switches. Table 11-4 shows the SNMP OIDs for the Cisco ER hardware platforms.
Table 11-4 Cisco ER Hardware Platform OIDs
Hardware Platform Cisco MCS-7815-I Cisco MCS-7825-H Cisco MCS-7825-I Cisco MCS-7835-H Cisco MCS-7835-I Cisco MCS-7845-H Cisco MCS-7845-I
SNMP OID 1.3.6.1.4.1.9.1.582 1.3.6.1.4.1.9.1.583 1.3.6.1.4.1.9.1.746 1.3.6.1.4.1.9.1.584 1.3.6.1.4.1.9.1.585 1.3.6.1.4.1.9.1.586 1.3.6.1.4.1.9.1.587
Monitoring Cisco Emergency Responder Subsystem Status

Cisco ER supports the SYSAPPL-MIB that allows you to use CiscoWorks2000 or a third-party SNMP browser to remotely access information about the following Cisco ER components:
Cisco ER Server
CERServer.exe
Cisco PhoneTrackingEngine
CERPhoneTracking.exe
MSQL Server-related Services
11-30
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Backing Up and Recovering Data
The SYSAPPL-MIB uses SNMP. Cisco ER supports the following SYSAPPL-MIB tables:
SysApplInstallPkgTableprovides installed application information such as Manufacturer, Product Name, Version installed, Date installed, and Location, which is a partial URL for accessing the associated Application Administration web page (when applicable). SysApplRunTabledescribes the application starting time and run-time status. SysApplInstallElmtTabledescribes the individual application elements, or associated executables, which comprise the applications defined in the SysApplInstallPkgTable. SysApplElmtRunTabledescribes the processes, or executables, that are currently running on the host system.
Collecting Information from Syslog

You can configure Cisco ER to use the Cisco Syslog Collector. Cisco Syslog Collector and Cisco Syslog Analyzer are offered with CiscoWorks2000 as part of the Resource Management Essentials package. You can also adapt Syslog output from Cisco ER for use with other network management systems. The Cisco Syslog Collector keeps common system logs of messages reported to Cisco ER. The Cisco Syslog Analyzer controls and displays all events efficiently so they can easily be read, interpreted, and used for system maintenance and problem solving. To install and configure the Cisco Syslog Collector, refer to the CiscoWorks2000 documentation. To enable syslog, follow these steps:
Procedure
Step 1
Select System > Cisco ER Group Settings. Cisco ER opens the Cisco ER Group Settings page. Select enable in Enable Syslog. Enter the fully-qualified DNS name of the server in the Syslog Server field, for example, server.domain.com. Click Update Settings to save your changes. Cisco ER immediately begins writing messages to syslog.
Related Topics
Cisco ER Group Settings, page A-3
Backing Up and Recovering Data

Cisco ER 2.0 uses the Disaster Recovery System to backup and restore system data. For information on using the Disaster Recovery System, see Chapter 8, Configuring the Cisco Emergency Responder 2.0 Disaster Recovery System.
11-31
Chapter 11 Troubleshooting the Data Migration Assistant
Related Topics
Collecting Call History Logs, page 11-27
Troubleshooting the Data Migration Assistant

The Data Migration Assistant (DMA) operates in two phases. In the first phase, Database, the following folders are backed up to a tar file:

export import etc nena_msag_records
In the second phase, the contents of the backed-up Cisco ER database are verified against the Cisco ER 2.0 database schema.
Symptom DMA backup and validation failed. Recommended Action Go through the following check list: Check if MSDE is running. If the database is not running, the backup will not succeed. Verify that the node being backed up is a Publisher node, not a Subscriber node. DMA backup
cannot be performed on a Subscriber node.

Verify that CSA is not running. If CSA is running, stop it before starting the backup.
Symptom DMA backup is successful but the validation failed. Recommended Action Go through the following check list: Verify that CSA is not running. If CSA is running, stop it before starting the backup. CSA
interferes with DMA operation.

Collect the data validation logs for further analysis. In this case, some changes may need to be
made to the data contained in the database before a migration to Cisco ER 2.0 can succeed. The DMA Logs are located in the following locations:

exportdb.log and migratecCERCSV.log are located in C:\CiscoWebs\DMA\Bin installdbw1.log, installdbw1.log.err, installdbccm.log, installdbccm.log.err, and dbl_INSTALLDBxxxxxx.txt are located under C:\Program Files\Cisco\Trace\DBL Log Files are located under C:\Program Files\Cisco\Trace\DMA exportdb.log installdbw1.log installdbw1.log.err dbl_INSTALLEDBxxxxxx.txt
The validation log files are as follows:

11-32
OL-12376-01
Chapter 11
Troubleshooting Cisco Emergency Responder Troubleshooting Windows Upgrades
Troubleshooting Windows Upgrades

If you receive an error stating DMA backup tar cannot be located during an upgrade from a Windows version to Cisco ER 2.0, perform the following checks:

Verify that the specified DMA retrieval details are accurate. If you have chosen sftp/ftp, verify that the sftp/ftp host is reachable, the username/password combination is correct, the remote path name is correct, and the name of tar file is correct. If you chose the Tape option, verify that the tape containing the DMA backup tar ball is present in the tape drive and the tape drive is connected to the Cisco ER Publisher being installed. Verify that the tape drive is recognized/mounted by the Cisco ER Publisher being installed.
Troubleshooting Linux Upgrades

You might encounter certain problems when upgrading to future versions of Cisco ER from Cisco ER 2.0. This section explains what could cause these problems and the provides recommended actions.
Symptom On the first page of the Install / Upgrade menu, after you enter the details for an upgrade patch, the error message No valid upgrade options found appears. Recommended Action Verify that you are not trying to upgrade the Subscriber before upgrading the
Publisher. When upgrading a Cisco ER servergroup, you must always upgrade the Publisher first.
Recommended Action Verify that the local/remote path that you have specified actually contains a
valid, signed ISO image, having the extension .sgn.iso.
Symptom On the first page of the Install / Upgrade menu, after you enter the details for an upgrade patch at a remote location, the error message Incorrect user name/password appears. Recommended Action Verify that the username and password entered for the remote SFTP/FTP
location are correct.
Symptom After downloading the ISO image onto the Cisco ER server, the checksum values do not match. Recommended Action Download a fresh ISO image from Cisco.com and try the upgrade again.
Symptom The upgrade was cancelled, but a warning message appears prompting you to reboot the
system.
Recommended Action During the upgrade, certain services on the Cisco ER server could have been
stopped, depending on when the upgrade was cancelled. In this case, it is highly recommended that you reboot the server.
11-33
Chapter 11 Troubleshooting Linux Upgrades
11-34
OL-12376-01
C H A P T E R
12
Using the ALI Formatting Tool

These topics describe the Automatic Location Information (ALI) Formatting Tool (AFT) and provide information on how to use and troubleshoot the AFT:

ALI Formatting Tool Overview, page 12-1 Generating Files Using the ALI Formatting Tool, page 12-2
Network engineers, system administrators, and telecommunications engineers should review these topics to learn the steps that are required to use and troubleshoot AFT. You should be familiar with Cisco Emergency Responder (Cisco ER) and with Cisco Unified Communications Manager (CallManager) before deploying AFT. For service provider-specific information, see Appendix G, Using the AFT for Specific Service Providers.
ALI Formatting Tool Overview

Cisco ER helps you manage emergency calls in your telephony network. Cisco ER tracks a systems phones and locations and exports this information in ALI records that conform to National Emergency Number Association (NENA) 2.0, 2.1, and 3.0 formats. However, many service providers do not use NENA standards. The AFT allows you to modify the ALI records that you create in Cisco ER to a format that is compatible with the one used by your service provider. The service provider then uses the reformatted file to update their ALI database. The AFT reads the ALI file generated by Cisco ER and displays all the ELIN records on the AFT web page. You can use AFT to:

Easily view the details of the ALI records. ALI files are difficult to read in the NENA fixed-length format. AFT reads the ALI files and presents the NENA fields in an interface that is easy to read. Select a record and update the value for ALI fields. AFT allows you to edit the ALI fields to customize them to meet the requirements of different service providers. Your service provider can then read the reformatted ALI files and use them to update their ELIN records. Perform bulk updates on multiple ALI records. Using the bulk update feature, you can apply common changes to all the records that you have selected, to one area code, or to one area code and one city code. Selectively export ALI records based on Area Code, City Code or a 4-digit Directory Number. By selecting to export all the ALI records in an Area Code, for example, you can quickly access all the ELIN records for each service provider allowing you to easily support multiple service providers.
12-1
Chapter 12 Generating Files Using the ALI Formatting Tool
Generating Files Using the ALI Formatting Tool

This section provides information about how to use the ALI Formatting Tool (AFT): Using the ALI Formatting Tool Interface Using AFT to Generate a Formatted ALI File
Using the ALI Formatting Tool Interface

You can edit the following fields using AFT:
The header and trailer fields. The ALI Formatting Tool (AFT) displays all the ALI record data in the ALI tab. The ALI file consists of one header record and one trailer record only; there is not an individual header and trailer record for each ELIN record. The Function/Transaction Code field. Any service provider-specific fields.
You cannot edit the following fields using AFT:

The ALI records fields that you configure and edit through Cisco ER. They are disabled in AFT. The record count field. This trailer field cannot be edited in AFT because AFT calculates this number internally based on the number of records selected to export.
Table 12-1 shows how to use the AFT interface to perform the main AFT tasks.
Table 12-1 Using the AFT Interface to Perform Main Tasks
Task Open AFT for your service provider Give a NENA files as input to AFT Go to a specific ELIN number
Procedure Go to Tools > ALI Formatting Tool. Click the name of your service provider in the pulldown menu. Select an Input File for the AFT from the list of files provided in the pulldown menu. All ELINs in the NENA file given as input for the AFT are displayed. To narrow down to a specific ELIN, perform an ELIN search.
Notes You must log in to the Cisco ER Administration website with the proper privileges. If no NENA files are listed, go to Tools > Export PS-ALI Record and export a NENA 2.0 file.
View ALI details for Each ELIN is a link. Click on the specific ELIN link to see the specific record. The ELIN details appear in the right pane of the an ELIN/Select an ELIN to edit its ALI screen. fields Perform a bulk update to the ALI files Review Changes Select the ELINs on which you want to perform a bulk update. Click the Bulk Update button above the list of ELINs. After you make some changes, click the Review Changes/Generate File button. A list of all the ELINs that have been changed appears.
You can then edit the ALI records by entering new values in the ALI editable fields.
Click the ELIN link on the Review Changes/Generate File page to view the changed information.
12-2
OL-12376-01
Chapter 12
Using the ALI Formatting Tool Generating Files Using the ALI Formatting Tool
Table 12-1
Using the AFT Interface to Perform Main Tasks (continued)
Task View/Edit Header Record View/Edit Trailer Record Add More ELIN(s)
Procedure Select any ELIN on the ALI Record Details for ELIN page and click the Header Record link. You can now edit the editable fields of the header record. Select any ELIN on the ALI Record Details for ELIN page and click the Trailer Record link. You can now edit the editable fields of trailer record. On the Review Changes/Generate File page, click the Add More ELIN(s) button. A list of unchanged ELINs appears. Select the ELIN(s) that you want to keep in the final generated file.
Notes Header record is common to the ALI file and not per ELIN. Trailer record is common to the ALI file and not per ELIN.
Remove ELIN(s)
On the Review Changes/Generate File page, select the ELIN to be The changes made on this record removed and click the Remove ELIN(s) button. will be lost and this ELIN will be added to the pool of unchanged ELIN(s). On the Review Changes/Generate File page, follow these steps:
1. 2. 3.
Generate Formatted File
Select the ELIN(s) that you want to include in the formatted file. Enter a Name for the Formatted File to be generated. Click the Generate File Button.
You can download the formatted file after it is successfully generated. If you want to download the file later, follow these steps:
1. 2.
Go to Tools > File Management Utility In the search parameters, select ALI Formatting Tool and then select the service provider. Formatted files are displayed. Select the formatted file and click Download.
3.
Generating a Formatted ALI File

To use AFT to generate a formatted file, follow these steps:
Procedure
Step 1
Provide a NENA 2.0 file generated by Cisco ER as input to AFT by following these steps:
a. b. c.
From the Cisco ER Administration web page, go to Tools > ALI Formatting Tool. Click on your service provider name in the menu. Select an Input File for the ALI Formatting Tool from the list of files provided in the pulldown menu. AFT displays all the ELINs from the NENA file.
12-3
To view details of the ALI files, click on an ELIN link. The ALI Record Details for ELIN are populated in the right pane of the screen. Edit the ALI fields by entering new values in the editable fields. Select the ELINs that you want to export to the service provider by clicking in the corresponding check boxes in the left side of the screen. Update the service provider fields in AFT. For details about the service provider-specific information required, see Appendix G, Using the AFT for Specific Service Providers.
Step 6
At this point, if you want to edit some fields in many ELINs simultaneously, you can use AFTs Bulk Update feature. To do so, follow these steps:
a. b. c.
Select the ELIN(s) to edit using Bulk Update. Click on the Bulk Update button. The Bulk Update form appears. For details about the service provider-specific information required, see Appendix G, Using the AFT for Specific Service Providers. Click on the Review Changes/Generate File button. The list of edited ELIN(s) are displayed. You can add unchanged ELIN(s) and/or remove edited ELIN(s) from the list.
Step 7
Generate a formatted file by following these steps:

a.
b. c.
Select the ELIN(s) which will be part of the final formatted file and enter the name for the formatted file. Click Generate File to generate the file. AFT generates an ALI file in a format specific to your service provider and prompts you to download the same.
Note Step 8
Before generating the formatted file, please verify the details entered.
Using the service providers preferred method of transmitting files, send the ALI file to your service provider so they can update their E911 database with the ELINs from the AFT ALI file.
Note
Be sure to keep a copy of the AFT ALI file for your records. This will be helpful if the service provider reports errors; you can make any required changes to the file without having to re-do all the AFT formatting changes.
Step 9
Your service provider returns the status of the ALI files. If your service provider reports that there are no errors, you can continue using AFT to generate more formatted records or you can quit the program. If your service provider reports that there are ALI errors, follow these steps:
a.
Make corrections to the formatted file that you sent to the service provider. All the error codes for the service providers are defined in the ALI format documentation for that service provider. Refer to their documentation to determine the errors in your file and correct the errors using AFT.
Note
If an error occurs in fields that cannot be edited using AFT, you must use Cisco ER to correct the fields. Then use AFT to regenerate the file.
12-4
OL-12376-01
Chapter 12
Using the ALI Formatting Tool Generating Files Using the ALI Formatting Tool
b. c.
Send the corrected file to your service provider. Be sure to keep a copy of your corrected file for your records. Repeat this process until your service provider can read the formatted files and can use them to update their ELIN records.
Related Topics

Converting ALI Data, page 5-32 ALI Formatting Tool, page A-60
12-5
12-6
OL-12376-01
A P P E N D I X
Administration Web Interface For Cisco Emergency Responder

These topics describe the fields on the pages of the Cisco Emergency Responder (Cisco ER) administrators web interface.

Cisco ER Server Groups in Cluster, page A-2 Cisco ER Group Settings, page A-3 Telephony Settings, page A-4 Server Settings for CERServerGroup, page A-6 License Manager, page A-7 Email Alert Settings, page A-8 Add Subscriber, page A-9 Onsite Alert Settings, page A-10 Find ERL Data, page A-12 SNMP Settings, page A-22 Phone Tracking Schedule, page A-24 Cisco Unified Communications Manager Clusters, page A-25 LAN Switch Details, page A-28 Run Switch-Port and Phone Update, page A-31 Switch Port Details, page A-31 Find and List IP Subnets, page A-35 Unlocated Phones, page A-39 Find and List Manually Configured Phone, page A-41 Find and List Synthetic Phones, page A-45 Find and List Users, page A-46 Find and List Roles, page A-49 Find and List User Groups, page A-51 Call History, page A-54 ERL Audit Trail, page A-55 Export PS-ALI Records, page A-56
A-1
Appendix A Cisco ER Server Groups in Cluster
PS-ALI Converter, page A-58 ERL Debug Tool, page A-59 ALI Formatting Tool, page A-60 File Management Utility, page A-61
Cisco ER Server Groups in Cluster

The Cisco ER Server Groups in Cluster page appears when you select System > Cisco ER Groups in Cluster.
Authorization Requirements
You must have system administrator, ERL administrator, or network administrator authority to access this page.
Description
Use the Cisco ER Server Groups in Cluster page to view the Cisco Emergency Responder (Cisco ER) groups that form a Cisco ER cluster. You can view which Cisco ER servers belong to each Cisco ER group within the cluster. You can click on the link for the remote server groups in a Cisco ER cluster (select either the primary server or the backup server) to go directly to the Cisco ER interface for these servers. Table A-1 describes the Cisco ER Server Groups in Cluster page.
Table A-1 Cisco ER Server Groups in Cluster Page
Field Cisco ER Groups Cisco ER Groups list
Description A list of the Cisco ER server groups that are pointing to the same cluster database host. Click a group name to view the servers in the group.
Notes The Cisco ER cluster consists of this set of Cisco ER groups. You create the cluster when installing Cisco ER servers. See the Installing Cisco Emergency Responder 2.0 on a New System section on page 2-3. Click the server group name to display the servers in that group in the Servergroup Details section of page.
Servergroup Details
Cisco ER Group Name
The name of the server group.
Primary Host Name
The DNS host name or IP address of the primary Click this host name (except for the local server server in the group. group) to open the Cisco ER administration page for that server in a new window. The DNS host name or IP address of the standby, or backup server in the group. Click this host name (except for the local Server Group) to open the Cisco ER administration page for that server in a new window.
Standby Host Name
Delete button
Click Delete to remove the Cisco ER group you Only system administrators can delete a are viewing from the Cisco ER cluster. Cisco ER group from the cluster. Delete a group from the cluster before you uninstall a Cisco ER group.
A-2
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Cisco ER Group Settings
Related Topics

Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster, page 11-22 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Cisco ER Group Settings

The Cisco ER Group Settings page appears when you select System > Cisco ER Group Settings.
You must have system administrator authority to access this page.

Description
Use the Cisco ER Group Settings page to define the operational characteristics of a Cisco Emergency Responder (Cisco ER) server group. Table A-2 describes the Cisco ER Server Group Settings page.
Table A-2 Cisco ER Group Settings Page
Field Cisco ER Group Name
Description The name of the server group. This name is used for your information only, so create a name you will find useful.
Notes
Peer TCP Port
The range is 1024 to 65535. The TCP port used for communications between Cisco ER servers within the server group. If you do not want to use the default port, ensure you select an unused port. The number of counts a Cisco ER server should wait The default number of counts is 3. The before declaring an unresponsive Cisco ER server range is 3 to 10. unavailable. The time between counts is defined in Heartbeat Interval. The number of seconds between sending heartbeat messages to the other Cisco ER server in the server group. How long to maintain a call route mapping so the PSAP can call back the emergency caller. The IP address or fully-qualified name of the mail server (for example, email.domain.com). The default is 30 seconds. The range is 30 to 300 seconds. The default is 180 minutes (3 hours). The range is 30 to 1440 minutes. Configure an email server if you want Cisco ER to send email or email-based pages to security officers when an emergency call is made. Emails or pages sent to security will come from this email account. Emails or pages sent to the system administrator by Cisco ER will come to this email account.
Heartbeat Count
Heartbeat Interval
Active Call Timeout SMTP Mail Server
Source Mail ID
If you configure a mail server, you must enter an email account on that server that can be used for sending email. Mail account where Cisco ER sends critical information about the system.
System Administrator Mail ID
A-3
Appendix A Telephony Settings
Table A-2
Cisco ER Group Settings Page (continued)
Field Syslog
Description Pulldown menu that enables/disables the writing of log messages to the CiscoWorks2000 Syslog Collector.
Notes
Syslog Server
The name of the server running the CiscoWorks2000 You can only enter a server name if you select Enable Syslog. Resource Manager Essentials Syslog Collector. Enter the fully-qualified DNS name of the server, for example, cw2k.domain.com.
Notes Update Settings button Cancel Changes button
Any notes you want to enter to help you understand the use of the server group. Click Update Settings to save and activate your changes. Click Cancel Changes to change the fields on this page back to the last saved settings.
Related Topics

Configuring a Cisco Emergency Responder Server Group, page 5-16 Collecting Information from Syslog, page 11-31 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Telephony Settings
The Telephony Settings page appears when you select System > Telephony Settings.

Description
Use the Telephony Settings page to define the telephone numbers and telephony ports used by the Cisco ER group. Table A-3 describes the Telephony Settings page.
Table A-3 Telephony Settings Page
Field
Description
Notes
Route Point for Primary The CTI route point that the primary server should use, See the Creating the Emergency Call Cisco ER Server such as 911. Route Points section on page 4-6 for more information. Route Point for Standby The CTI route point that the standby server should use, See the Creating the Emergency Call Cisco ER Server such as 912. Configure this number as the call forward Route Points section on page 4-6 for more number for the primary emergency number. information.
A-4
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Telephony Settings
Table A-3
Telephony Settings Page (continued)
Field PSAP Callback Route Point Pattern
Description CTI route point you defined to receive calls from the public safety answering point (PSAP). For example, 913XXXXXXXXXX (913 plus ten Xs). The number can only consist of numbers and Xs.
Notes For more information, see the Creating the Emergency Call Route Points section on page 4-6.
ELIN Digit Strip Pattern
This string must be part of the PSAP Digits to strip from the beginning of the PSAP Callback Route Point Pattern, for example, 913. The Callback Route Point Pattern. number that results from stripping the pattern should be the ELIN numbers that the PSAP can use to call into your network. Port numbers that are used by CTI ports during their registration. Route pattern that other Cisco ER groups will use to route emergency calls to this group, for example, 1000.911. The pattern can only consist of numbers and dots. The range is 1024 to 65535. For a more detailed explanation of this number. see the Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications section on page 4-17. The TOS value entered here only applies to the RTP packets sent by CER for the onsite audio alert feature.
UDP Port Begin Inter Cisco ER Group Route Pattern
IP Type of service (00-FF)
Value of the Type of Service (TOS) byte in the IP header. The default 0xB8 implies a TOS class of Priority Queue. It is recommended that this default value be used for Cisco ER. Number of times the prompt is played on the onsite alert phone.
Onsite Alert Prompt Repeat Count Use IP Address from call signaling
If this parameter is enabled, Cisco ER will obtain the This field is applicable only if Cisco ER is configured with Cisco Unified IP address of the phone from JTAPI. This parameter will be used to route the call. Thus, if an IP subnet is Communications Manager 6.0 and above. configured for the phone, this parameter setting will take precedence over any other manual configuration. If this parameter is disabled, Cisco ER will use the manual configuration of the phone to route the call.
Update Settings button Cancel Changes button
Click Update Settings to save and activate your changes. Click Cancel Changes to change the fields on this page back to the last saved settings.
Related Topics

Configuring Group Telephony Settings For the Cisco Emergency Responder Server, page 5-18 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-5
Appendix A Server Settings for CERServerGroup
Server Settings for CERServerGroup

The Server Settings for CERServerGroup page appears when you select System > Server Settings.

Description
Cisco ER servers are inserted in the Cisco ER group when the Cisco ER services are started. (See the Installing Cisco Emergency Responder 2.0 on a New System section on page 2-3.) Use the Server Settings for CERServerGroup page to update server settings, for example, to change the server name or to change the trace/debug settings; or to delete servers.
Note
You cannot modify the host name of the server. Table A-4 describes the Server Settings CERServerGroup page.
Table A-4
Server Settings for CERServerGroup Page
Field Status
Select Server
Description Displays the status of the Server Settings CERServerGroup page. List of servers you have already created. Click on a server name to see the settings for that server. The name of the server. The DNS name of the Cisco ER server.
Notes
Server
Modify Server Settings
You can configure a maximum of two servers per server group. Change this server name field to any desired value. This field cannot be modified.
Server Name Host Name Debug Package List
See the Collecting Trace and Debug A selection of subsystems for which you need to collect detailed debug information. Debug information Information section on page 11-27 for an explanation of each field. includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Ciscos use to help resolve problems that you cannot solve yourself. Selects all subsystems in the Debug Package List. Clear all selected subsystems in the Debug Package List. See the Collecting Trace and Debug A selection of subsystems for which you need to collect brief trace information. Only select subsystems Information section on page 11-27 for an explanation of each field. at the request of Cisco Technical Support; the trace information is for Ciscos use to help resolve problems that you cannot solve yourself. If you select a subsystem for debug, you do not have to select it for trace.
Select All button Clear All button

Trace Package List
A-6
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder License Manager
Table A-4
Server Settings for CERServerGroup Page (continued)
Field Select All button Clear All button Update Settings button Cancel Changes button
Description Selects all subsystems in the Trace Package List. Clear all selected subsystems in the Trace Package List. Click Update when viewing an existing servers settings to save changes you make to the settings. Click Cancel Changes to change the fields on this page back to the last saved settings.
Notes
Only available when viewing the settings of an existing server.
Related Topics

Configuring Cisco Emergency Responder Servers, page 5-19 Collecting Trace and Debug Information, page 11-27 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
License Manager
The License Manager page appears when you select System > License Manager.

Description
Use the License Manager page to view the details of the licenses on a server and to upload a license file to a server. For information on Cisco ER 2.0 license requirements, refer to the Licenses for Cisco Emergency Responder 2.0 section on page 1-4. Table A-5 describes the License Manager page.
Table A-5 License Manager Page
Field Status
Details of Cisco ER Licenses
Description Displays status messages
Server drop-down menu A list of the servers whose license details you can view Upload license button
Installation Date (MM/YY/DD) CER Server License
Allows you to upload a license file to the server selected in the drop-down menu Displays the date on which the server license was installed
A-7
Appendix A Email Alert Settings
Table A-5
License Manager Page (continued)
Field CER Server License Type
Description Displays the type of server license installed. There are two possible values for this field:

EvaluationNo server license is installed and Cisco ER is operating in 60-day mode PermanentThe server license is installed Number of user licenses Number of phones discovered Number of phones manually configured Total number of users being tracked currently
CER User License
Displays the following information about the installed CER user licenses:

Related Topics

Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Licenses for Cisco Emergency Responder 2.0, page 1-4 Uploading the Cisco Emergency Responder License File, page 5-20
Email Alert Settings

The Email Alert Settings page appears when you select System > Mail Alert Configurations.
You must have system administrator or ERL administrator authority to access this page.
Description
Use the Email Alert Settings page to specify the parameters under which Cisco ER will send email alerts. Use the pulldown menu to the right of each parameter to enable (True) or disable (False) email alerts for that parameter. Table A-6 describes the Email Alert Settings page.
Table A-6 Email Alert Settings Page
Field Discovery Parameters Discovery Engine Registration Failed Discovery Engine goes out of connection For unreachable devices during recovery
Emergency Call Routing Parameters
An email alert is sent when:
The Discovery Engine fails to register The Discovery Engine loses connection Devices such as switches and Cisco Unified Communications Managers become unreachable A 911 call is placed
Call information
A-8
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Add Subscriber
Table A-6
Email Alert Settings Page (continued)
Field Call routing session ended due to problems
An email alert is sent when:
Call routing is stopped due to any of these reasons:

Invalid CMC Invalid FAC FAC and CMC needed CMC needed FAC needed RESOURCE_BUSY
Re-Routing of call Routing failure Route Point out of Service Cluster Parameters Cluster DB Failure Intra Cluster Failure
Misc Parameters
An emergency call is re-routed Call routing fails The route point goes out of service The server is not able to communicate with the cluster database host The intra-cluster communication to a servergroup in the cluster fails The Subscriber becomes active The Publisher comes back online When Cisco ER is not able to get the JTAPI provider When the number of user licenses are exhausted during phone tracking When you enable switch port change reporting for phones When you filter Cisco Unified IP Communicator from the location change reporting email alerts Updates the email alert settings Cancels changes made to the email alert settings
Subscriber becomes active Publisher comes back online Not able to get the JTAPI Provider Available user licenses get exhausted during phone tracking Switch Port location change reporting Suppress IP Communicator location change reporting Update Settings button Cancel Changes button
Related Topics

Onsite Alert Settings, page A-10 Configuring a Cisco Emergency Responder Server Group, page 5-16
Add Subscriber
The Add Subscriber page appears when you select System > Add Subscriber.
A-9
Appendix A Onsite Alert Settings
Description
Use the Add Subscriber page to add a subscriber node to a Cisco ER cluster.
Before You Begin
You must first configure a Publisher node before configuring a subscriber node. Table A-7 describes the Add Subscriber page.
Table A-7 Add Subscriber Page
Field Add Subscriber HostName IP Address Insert button Cancel Changes button Configured Servers
Description Host name of the subscriber node IP address of the subscriber node Click Insert to add the new subscriber node Remove input form the Add Subscriber page A list of all currently configured servers, showing the host name and IP address of each server/
Related Topics

Installing the Cisco Emergency Responder Publisher, page 2-4 Installing the Cisco Emergency Responder Subscriber, page 2-8

The Onsite Alert Settings page appears when you select ERL > Onsite Alert Settings.
Description
Use the Onsite Alert Settings page to add 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. Table A-8 describes the Onsite Alert Settings page.
A-10
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Onsite Alert Settings
Table A-8
Onsite Alert Settings Page
Field Add New Onsite Alert Contact Onsite Alert ID
Description
Notes
Use a naming strategy meaningful to your The identifier for the onsite alert contact. The organization, but which will also be useful when identifiers you use should be based on your configuring zones in Cisco ER. sites identification strategy (for example, security ID or badge number). This field is used throughout Cisco ER to identify the contact; for example, you will select from Onsite Alert IDs when assigning contacts to zones. Once saved, the Onsite Alert ID cannot be modified. The name of the onsite alert contact. The telephone number for the onsite alert contact. This number must be a voice telephone number; do not enter the number of a voice-mail system or an automated attendant. The email address for the onsite alert contact, for example, email@domain.com. When Cisco ER gets an emergency call from an ERL, it calls the onsite alert number of the contact for the ERL and plays a pre-recorded message that includes the phone number from which the emergency call was placed. When Cisco ER gets an emergency call from an ERL, it emails the onsite alert contact associated with the ERL. If the email ID is for an email paging system, the contact receives a page instead of an email. The email or page includes the phone number from which the emergency call was placed.
Onsite Alert Name Onsite Alert Number
Onsite Alert Email Address
Insert button
Click Insert to add the contact to the list of contacts. The contact is then listed in the Available Onsite Alerts section of the page. Click Cancel Changes to cancel any changes made to this page. If no contacts have previously been configured, Section of the page that displays onsite alert contacts that have already been configured. For this section is blank. configured onsite alert contacts, the following You cannot modify a contacts Onsite Alert ID. information is displayed: Before you can delete the entry, you must update Onsite Alert ID the ERLs to which the person is assigned to remove the person from the ERL. Onsite Alert Name

Cancel Changes button

Available Onsite Alerts
Onsite Alert Number Onsite Alert Email Address
To change an entry, click the entry or click the Edit icon; the persons contact information is loaded in the edit boxes. Make your changes and click Update. To delete an entry, click the Delete icon on the same line as the entry.
A-11
Appendix A Find ERL Data
Table A-8
Onsite Alert Settings Page (continued)
Field Add New button Update button
Description Click Add New to add another contact.
Notes
Click Update when viewing an existing Only available when viewing the information contacts information to save changes you make for an existing contact. to the information.
Related Topics

Identifying Security Personnel (Onsite Alert Personnel), page 5-27 Creating ERLs, page 5-28 Preparing Onsite Alert (Security) Personnel for Cisco Emergency Responder, page 10-1 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Find ERL Data

The Find ERL Data page appears when you select ERL > ERL Details.
Description
Use the Find 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. Table A-9 describes the Find and List ERLs page.
A-12
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find ERL Data
Table A-9
Find and List ERLs Page
Field ERL Search Parameters Find ERL where...
Description Select search criteria and click Find to list existing ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down menu, you can select the number of records that display per page for each search. From the search results list, you can:

Notes When copying an ERL, information that must be unique in an ERL is not copied. See the Add New ERL section on page A-14 for more information.
Click an entry to view and update its characteristics. Click the Copy icon to create a new ERL with the same ALI data. Click the Delete icon to remove the ERL. Click view... in the Audit Trail column to view a history of changes made to that ERL. See the ERL Audit Trail section on page A-55 for more information. See the Add New ERL section on page A-14 for more information.
Configure Default ERL
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.
Note
During the migration of data in an upgrade scenario, if any manually configured phone is assigned to the Default ERL, it will remain there until it is modified. See the Add New ERL section on page A-14 for more information. See the Export ERL Data section on page A-21 for information on exporting ERL data.
Add New ERL Export
Click Add New ERL to create a new ERL. Click the Export link to create a file containing your ERL configuration.
Import
Click the Import link to create or update ERLs using See the Import ERL Data section on page A-21 for information on importing information stored in a separate file. By importing ERL data, you can create or update many ERLs at one ERL data. time.
Related Topics

Export PS-ALI Records, page A-56 Creating ERLs, page 5-28 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-13
Add New ERL

The Add New ERL and ERL Information for ERL Name pages are essentially the same, as follows:
Note
On the ERL Information for ERL Name page, the ERL Name variable is replaced with the name of the ERL associated with the page. For example, if you click on the Default ERL, the page that appears is titled ERL Information for Default. Likewise, if the ERL name is First Floor, the page that appears is titled ERL Information for First Floor.
The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you select ERL > ERL Details). The page also appears if you click Copy for an existing ERL. The ERL Information for Default page opens when you click Configure Default ERL on the Find ERL Data page. The ERL Information for ERL Name page also appears when you click any of the links associated with an existing ERL in the list on the Find ERL Data page (opened when you select ERL > ERL Details).
Note
You cannot use a default ERLs as a Test ERL. The Test ERLs check box is not available on the ERL Information for Default page.
Description
Use the Add New ERL page to create a new emergency response location (ERL). Alternatively, you can create or update many ERLs at once by importing predefined ERL information from a separate file. See the Import ERL Data section on page A-21 for more information. Cisco ER 2.0 allows you to select the ERL as a Test ERL. Use the Find ERL Data page to view or update an existing ERL. See the Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks section on page 4-9 for information on configuring the ELIN numbers in Cisco Unified Communications Manager. If you want to route emergency calls to onsite security instead of the PSAP, see the Setting up ERLs for Non-PSAP Deployment section on page 5-29 for the Route/Translation Pattern and ELIN settings. Table A-10 describes the Add New ERL and ERL Information pages.
A-14
OL-12376-01
Appendix A
Table A-10
Add New ERL and ERL Information Pages
Field ERL Settings ERL Name
Description The name of the ERL. The naming strategy you use is critical. The ERL name is one of the primary pieces of information your security team will see when alerted to an emergency call. If the name is easy to understand and very descriptive, it can help your team respond quickly to a call. For example, if you are creating an ERL for each floor in a three story building called Building J, your ERL names might be BldgJ-Floor1, BldgJ-Floor2, BldgJ-Floor3. Work with your security team to develop and ERL naming strategy.
Notes You cannot change the name of an existing ERL. To change an ERL name, create a new ERL, then delete the old ERL. Any leading and trailing spaces will be trimmed.
Description Test ERL (Used for Synthetic Testing)
Enter a description of the new ERL (optional). Click this checkbox if this ERL is used for testing. Test This setting is not available on the ERL ERLs can be used when Cisco ER is being monitored Information for Default; default ERLs may not be used as test ERLs. by CiscoWorks IP Telephony Environment Monitor (ITEM). See Configuring Test ERLs, page 5-34. The combination of a route pattern and a telephone number that jointly route the emergency call to the PSAP and provide the PSAP with a call-back number if the PSAP needs to call the emergency caller after disconnecting the call. Each ERL must have unique ELINs. The number of ELINs you define determines how many callbacks you can support. ELINs are used in order as emergency calls are made, and recycled as needed. For example, if you define two ELINs for an ERL, and three emergency calls are made, the PSAP will not be able to recontact the first emergency caller. However, concurrent emergency calls are not limited by the number of ELINs: you could have ten active emergency calls even if you only have two ELINs. The number of ELINs only controls PSAP callback capability.
ELIN Settings
Route/Translation Pattern
The phone number, defined as a route pattern in Cisco Unified Communications Manager, that is configured to use the gateway the call should be routed through to get to the correct PSAP. This number must include the external emergency number, such as 911 in the USA. For example, 10.911 or 10911. The pattern can only contain numbers and dots.
A-15
Table A-10
Add New ERL and ERL Information Pages (continued)
Field ELIN Number
Description The unique phone number that routes the call to the correct local PSAP and which the PSAP can use to recontact an emergency caller if the call is hung up. This number must be a DID (direct inward dial) number provided by your service provider; that is, it must be routeable on the PSTN. Enter the entire number, including area code, such as 4085551212, 408-555-1212, 408.5551212, or (408)555-1212. The number can only contain numbers, single hyphens, dots, or parentheses. To add a route point-ELIN combination, enter the information and click Add. To change an existing combination, select it in the list, change the information in the edit boxes, and click Update. To remove a combination, select it in the list and click Remove. Text box that displays the IDs of all available onsite alert personnel.
Notes
Add button Update button
Remove button
Available Onsite Alert IDs
You must first add the contact to the list of onsite alert personnel. See the Onsite Alert Settings section on page A-10 for more information.
Add button
Select the onsite alert (security) contacts to be assigned to the ERL. These contacts will be notified when an emergency call is made from the ERL. To add a contact, select an Onsite Alert ID from the Available Onsite Alert IDs list and click Add. The contacts ID then appears in the Onsite Alert IDs for the ERL text box. To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove. See the ALI Information (for ERL Click ALI Details to view or change the automatic Name) section on page A-17 for location information (ALI) of an ERL. The ALI provides detailed information about the location of the information about the ALI fields. ERL, such as street address and phone number. Click Insert to save your changes to the new ERL. Click Cancel Changes to change the fields on this page back to the last saved settings. The Insert button is only available when creating a new ERL.
Remove button
ERL Address
ALI Details button
Insert button Cancel Changes button
A-16
OL-12376-01
Appendix A
Table A-10
Add New ERL and ERL Information Pages (continued)
Field Update button Close button
Description Click Update to save your changes to the ERL. Click Close to close the window. You must click Update or Insert to save your changes before you click Close.
Related Topics

Notes The Update button is only available when changing an existing ERL.
Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Setting Up the Default ERL, page 5-28 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Configuring Test ERLs, page 5-34 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
ALI Information (for ERL Name)

The ALI Information (for ERL Name) page appears when you do one of these:
Note
On the ALI Information (for ERL Name) page, the ERL Name variable is replaced with the appropriate ERL name. For example, if you click on ALI Details on the ERL Information for Default page, the page that appears is titled ALI Information for Default. Likewise, if the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.
Click Add/Edit ALI in the ERL Address section on the Add New ERL page.
Note
The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you select ERL > ERL Details).
Click Add/Edit ALI on the ERL Information for ERL Name page. The ERL Information for ERL Name page appears when you click on an existing ERL name or on Configure Default ERL on the Find ERL Data page (opened when you select ERL > Details).
Description
Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). You will eventually send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs can get routed to the local PSAP and so that public safety answering points (PSAPs) can locate an emergency caller.
A-17
The data requirements for these fields might differ from service provider to service provider. Contact your service provider to determine their requirements. The descriptions of the fields in Table A-11 are based on the National Emergency Number Associations (NENA) Version 2 standards (USA).
Caution
The quality of the information you enter here is critical. This information is displayed to emergency call operators and to your local response team. They use this information to locate emergency callers. If the data is incorrect or difficult to understand, emergency response can be delayed, which might result in casualties that could have been prevented. Table A-11 describes the Enter ALI Information page.
Table A-11
Enter ALI Information Page
Field Find all prevalidated fields from validation file by selecting a tag Select a Tag
Description
Notes
Select the tag whose associated ALI data you want You can simplify the entry of ALI data by to load into the window. You can then edit the setting up tags in a file called validate.txt. information for this specific ALI. This page explains where to place the file, and where to find the samplevalidate.txt file, which explains the format of the file. When you create a tag, you enter information that will be common between several ALIs, such as company name, city, state, and so forth. For example, if you have a 25-story building, and you are creating an ERL for each floor, you could create a tag called 25story. Then, instead of retyping the information for the building 25 times, you simply select a tag and the ALI data is loaded with the data you defined for the tag.
ALI Data
House Number
The number from the postal street address for the The number can be up to 10 characters, but building (for example, the 170 in 170 West your service provider might only support 8 Tasman Dr.) character numbers. The number extension (such as /2) for the house number, if any. The street name from the postal address for the building. A leading directional indicator if the street name contains one, for example, N for North. The type of street. Select the type from the drop-down list, and the field is filled with one of the abbreviations accepted by the U.S. Postal Service Publication 28, for example, AVE for Avenue. You are limited to 60 characters. Can be one of: N, S, E, W, NE, NW, SE, SW. You can also type in the suffix. You are limited to 4 characters.
House Number Suffix Street Name Prefix Directional Street Suffix
A-18
OL-12376-01
Appendix A
Table A-11
Enter ALI Information Page (continued)
Field Post Directional Community Name State Main NPA Main Telephone No.
Description A trailing directional indicator if the street name contains one, for example, N for North. The community name for the address, for example, a city, town, or district name. The 2-digit state abbreviation. The 3-digit area code of the main number associated with the ERL.
Notes Can be one of: N, S, E, W, NE, NW, SE, SW. You are limited to 32 characters. You are limited to 2 characters.
The main phone number associated with the ERL. You are limited to 7 characters. This might be the number of the security office for the ERL. Select the class of service for the ERL. Select the type of service for the ERL. The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone. The subscriber name associated with the ERL, typically, your companys name. The service order number of the activity of establishing or updating this record. The date on which the record was created. If you do not know your class of service, ask your service provider. If you do not know your class of service, ask your service provider. You are limited to 4 characters. Ask your service provider for this identifier. You are limited to 32 characters. You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed. This is a read-only field.
Class of Service Type of Service Exchange
Customer Name Order Number
Extract Date County ID
The county identification code for the zone. In the You are limited to 4 characters. USA, use the FIPS code assigned to the county by the U.S. Census Bureau. Your NENA-registered company identification code. The postal zip code for the address. The postal zip code plus four number. You are limited to 5 characters. You are limited to 5 characters. You are limited to 4 digits.
Company ID Zip Code Zip Code Extension Customer Code
Your customer code. Ask your service provider if You are limited to 3 characters. you do not know your code. If you change this field, Cisco ER generates two records: a Delete record to remove the ALI with the old code, and an Insert record to add the ALI with the new code. This Delete/Insert sequence is only generated the next time you export ALI: you must ensure you submit this export file to the service provider. Optional comments. These comments might be displayed at the PSAP if an emergency call is made from this ERL. The longitude of the ERL. You are limited to 30 characters.
Comments
Longitude
You are limited to 9 digits.
A-19
Table A-11
Enter ALI Information Page (continued)
Field Latitude Elevation TAR Code Location
Description The latitude of the ERL. The elevation of the ERL. The taxing area rate code. Additional location information, in free form, to help identify the exact location of the phone. This information is displayed to your security personnel along with the ERL name when an emergency call is made, so use this field to help locate the caller. For example, you might repeat the street address that is defined in several separate fields elsewhere on this page.
Notes You are limited to 9 digits. You are limited to 5 digits. You are limited to 6 characters. You are limited to 60 characters.
Reserved
Information your service provider might require to Ask your service provider if you need to enter create a valid ALI file. anything in the reserved area. Be aware that NENA and CSV requirements may be different. For example, ERL Import does not require that you enter anything in the Reserved field. You can give an empty string in each of the ERL records and Cisco ER will accepts this file for importing. However, you must not delete the field itself from the file. The field must be there in the record; it can be an empty string delimited with a comma.
Save and Close button
Click Save and Close to save your changes and close the Enter ALI Information page.
This button is only available when entering information for a new ERL. This button is only available when viewing a previously configured ERL.
Update ALI Info button. Click Update ALI Info to save your changes. Cancel Changes button Close button Click Cancel Changes to change the fields on this page back to the last saved settings. Click Close to close the window.
Related Topics

Setting Up the Default ERL, page 5-28 Setting Up an Individual ERL and Its Automatic Location Information (ALI), page 5-30 Importing Several ERLs at Once, page 5-32 Export PS-ALI Records, page A-56 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-20
OL-12376-01
Appendix A
Export ERL Data

The Export ERL Data page appears when you click the Export link on the Find ERL Data page (opened when you select ERL > ERL Details).
Description
Use the Export ERL Data page to create ERL export files for your own use only; do not submit ERL export files to your service provider. For example, use an ERL export file to back up your configuration or to move it to another Cisco ER server. To create a file to send to your service provider to update their ALI data, see the Export PS-ALI Records section on page A-56. Table A-12 describes the Export ERL Data page.
Table A-12 Export ERL Data Page
Field Select Export Format
Description The file format to be used in the export file. For ERL data, either csv (comma separated value) or XML. Click Export to create the export file. Click Close to close the window.
Related Topics

Enter Export File Name The name of the file you want to create. Do not include a file extension. Export button Close button
Negotiate ALI Submission Requirements With Your Service Provider, page 1-19 Exporting ERL Information, page 5-36 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Import ERL Data

The Import ERL Data page appears when you click the Import link on the Find ERL Data page (opened when you select ERL > ERL Details).
Description
Use the Import ERL Data page to create or update many ERLs at once from a file in which you have defined the ERL data. Create this file using a spreadsheet that can save the information in one of the required formats (csv or xml). View the samples from this page before attempting to create an import file.
A-21
Appendix A SNMP Settings
If you need to update a lot of ERLs, you can export the ERL data, update the export file, and reimport the file. You can also use the Upload utility to upload a file containing ERL data from your local system; you can then import the ERL data. See the Uploading a File section on page 5-6 for more information. Table A-13 describes the Import ERL Data page.
Table A-13 Import ERL Data Page
Field Select Import Format
Description Select the format used in the file you are importing. After you select the format, click View sample file to see an example of the expected format and sequence of values. Use this sample information to create your import file in a spreadsheet.
Select File to Import Upload button Import button
Select the file from which you want to import ERL data. Click Upload to upload a file from your local system. See the Uploading a File section on page 5-6 for more information. Click Import to add ERL data from the import file to the Cisco ER database.
Note
The imported ERL data overwrites conflicting data in the Cisco ER database.
Close button
Related Topics

Click Close to close the window.
Importing Several ERLs at Once, page 5-32 Exporting ERL Information, page 5-36 Uploading a File, page 5-6 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Export PS-ALI Records, page A-56
SNMP Settings
The SNMP Settings page appears when you select Phone Tracking > SNMP Settings.
You must have system administrator or network administrator authority to access this page.
Description
Use the SNMP Settings page to define the SNMP read community string used by your switches. Table A-14 describes the SNMP Settings page.
A-22
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder SNMP Settings
Table A-14
SNMP Settings Page
Field Add SNMP Community Setting IP Address/Host Name
Description
Notes
The IP address or host name of a switch whose SNMP You are not defining your switches on this page, you are only associating IP address read community string you are defining. patterns to read community strings. If you use the same read community string for all Cisco Emergency Responder (Cisco ER) switches, you only need to define one entry: *.*.*.*. only tries to use the string with the specific If you use different read community strings for sets of switches you identify on the LAN Switch switches, you can define each set, using variables and Details page. See the LAN Switch Details ranges. For example, if you have 10 switches from section on page A-28 for more information. 10.1.115.0 to 10.1.125.0, you can use 10.1.115-125.0 If two or more patterns match an IP address, as the IP address. You can also mix ranges and Cisco ER uses the SNMP string associated variables, such as *.*.115-125.*. with the most closely matching pattern. Default is 10 seconds. The optimal value is The time, in seconds, in which Cisco ER should consider an attempted SNMP connection to a switch 10 to 15 seconds. to have failed. See the explanation of Retries for more information. Default is 2 retries. This number does not include the initial attempt; that is, if retries is 2, Cisco ER will attempt to contact a With each retry, the previous timeout is multiplied by switch up to 3 times (the initial attempt plus 2, to ensure the switch has enough time to respond. 2 retries). For example, if you specify 10 for timeout, the first attempt times out in 10 seconds, the second attempt The optimal value is 2 to 3 retries. times out in 20 seconds, the third attempt times out in 40 seconds, and so forth. The number of times Cisco ER should attempt to contact a switch. The SNMP read community string for the switch. Click Insert to add the entry to the list of SNMP settings. Click Cancel Changes to change the fields on this page back to the last saved settings. A list of SNMP settings that you have already defined. To change an entry, click any of the links associated with the entry to load the details into the edit boxes at the top of the page. Then make your changes and click Update. To delete an entry, click the Delete icon for the entry. Default is public for any IP address not covered in the SNMP settings list.
Timeout
Maximum Retry Attempts
Read Community Insert button Cancel Changes button

SNMP Settings
Add New button Update button
Click Add New to add another SNMP setting. Click Update to save changes you make to an existing SNMP setting. Only available when viewing an existing setting.
A-23
Appendix A Phone Tracking Schedule
Related Topics

Configuring the SNMP Connection, page 5-39 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Phone Tracking Schedule

The Phone Tracking Schedule page appears when you select Phone Tracking > Schedule.
Description
Use the Phone Tracking Schedule page to define Cisco Emergency Responders (Cisco ERs) schedule for updating phone and switch information from the network. Cisco ER updates network information using two processes:
Phone TrackingA 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 phones ERL. Switch Port and Phone UpdateThe phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Ensure that your ERL administrator updates the ERL assignment for new ports.
Table A-15 describes the Phone Tracking Schedule page.

Table A-15 Phone Tracking Schedule Page
Field
Incremental Phone Tracking
Description The time, in minutes, between making updates to the known phone locations. This periodic update ensures that phones that have moved are located and assigned to the correct ERL. Click Update to save your changes to this field. Enter the schedule you want to add:
Notes The default is 30 minutes. The range of the interval that can be defined is 5 - 300 minutes.
Incremental Phone Tracking Interval
Add New Schedule
Cisco recommends that you run the switch-port and phone update process at 1. Select the days of the week when you want to run least once per day. Because of the added the switch-port and phone update process. network traffic, it is best to run the 2. Select the time of day when you want the process process outside normal business hours. to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.
Insert button Cancel Changes button Update button
Click Insert to add the schedule to the list of schedules. Click Cancel Changes to change the fields on this page back to the last saved settings. Click Update when viewing an existing schedule to save changes you make to the schedule. Only available when viewing an existing schedule.
A-24
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Cisco Unified Communications Manager Clusters
Table A-15
Phone Tracking Schedule Page (continued)
Field Switch-Port and Phone Update Schedule
Description The list of schedules you have defined.
Notes
If any schedules overlap, only one To change a schedule, click the Hour link, the Minute schedule is run. link, or the Edit icon to load it into the Modify Schedule area above the list. Then, make your changes and click Update. To remove a schedule, click the Delete icon for the schedule.
Add New button
Click Add New to add another schedule.

Related Topics

Defining the Phone Tracking and Switch Update Schedules, page 5-41 Manually Running the Switch-Port and Phone Update Process, page 5-45 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2

The Cisco Unified Communications Manager Clusters page appears when you select Phone Tracking > Cisco Unified Communications Manager.
Description
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. Table A-16 describes the Cisco Unified Communications Manager Clusters page.
A-25
Appendix A Cisco Unified Communications Manager Clusters
Table A-16
Cisco Unified Communications Manager Clusters Page
Field Description Add New Cisco Unified Communications Manager Cluster Cisco Unified Communications Mana ger The IP address or DNS name of a Cisco Unified Communications Manager server that is running Cisco Unified Communications Manager and SNMP services.
Notes When viewing a previously defined Cisco Unified Communications Manager server, Cisco ER displays a CCM List link. Click CCM List to view a list of the Cisco Unified Communications Manager servers that belong to the same cluster as the selected server.
Only add one server per Cisco Unified Communications Manager cluster Cisco ER can identify the other servers in the cluster. The Cisco Unified Communications Manager server Once the IP address/DNS name has been you specify will represent the cluster in which it is a configured, it cannot be modified. member. CTI Manager The IP address or DNS name of the CTI Manager used by the specified Cisco Unified Communications Manager server. The name of the user created in the Cisco Unified Communications Manager server for Cisco ERs use.
CTI Manager User Name
This user must have specific characteristics and device assignments. See the Creating a Cisco Emergency Responder Cisco Unified Communications Manager User section on page 4-19 for specific information.
CTI Manager Password The password for the user. Backup CTI Manager 1 The IP address or DNS name of the backup CTI Manager used by the specified Cisco Unified Communications Manager server. Backup CTI Manager 2 The IP address or DNS name of the backup CTI Manager used by the specified Cisco Unified Communications Manager server. Telephony Port Begin Address The number of the first CTI port to use for calling onsite alert (security) personnel. When an emergency call is made, Cisco ER calls the onsite alert personnel for the originating ERL using the telephony ports you configure here. The number of CTI ports. Enter the number of CTI ports you created in Cisco Unified Communications Manager. The number of ports is the number of concurrent calls Cisco ER can make to onsite alert personnel. Click this checkbox to enable secure connection. You can enter data in the other fields of this section only if you have enabled Secure Connection. The port of the TFTP server. You must first create this port in Cisco Unified Communications Manager. See the Creating the Required CTI Ports section on page 4-8 for more information. The ports used are in sequence from the beginning port. For example, if you enter 3000 for the begin port, and 4 for number of ports, Cisco ER uses 3000, 3001, 3002, and 3003.
Number of Telephony Ports
Enable Secure Connection
Enable Secure Connection checkbox
TFTP Server IP Address The IP address of the TFTP server. TFTP Server Port
A-26
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Cisco Unified Communications Manager Clusters
Table A-16
Cisco Unified Communications Manager Clusters Page (continued)
Field
Description
Notes
Backup TFTP Server IP The IP address of the backup TFTP server, for the Address Cisco Unified CM node being added. CAPF Server IP Address CAPF Server Port Instance ID for Publisher Secure Authentication String for Publisher Instance ID for Subscriber Secure Authentication String for Subscriber Insert button The IP address of the CAPF server. The port of the CAPF server. The instance ID for the Publisher node. The secure authentication string for the Publisher node. The instance ID for the Subscriber node. The secure authentication string for the Subscriber node. Click Insert to add the new Cisco Unified Communications Manager server to the list of servers. Click Cancel Changes to change the fields on this page back to the last saved settings. Click Update when viewing an existing server to save changes you make to the server. Only available when viewing an existing server. Replaces the Insert button when viewing an existing server.
Cancel Changes button Update button
Add New button Cisco Unified Communications Manager list
Click Add New to add another Cisco Unified Communications Manager server. A list of Cisco Unified Communications Manager servers defined for this Cisco ER group. Click a server link or the Edit icon to view and modify the Cisco ER configuration for the server. Click the Delete icon to delete the server.
Related Topics

Identifying the Cisco Unified Communications Manager Clusters, page 5-21 Configuring Cisco Unified Communications Manager 5.0, 5.1, and 6.0 for Cisco Emergency Responder 2.0, page 4-1 Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-19 Creating the Required CTI Ports, page 4-8 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-27
Appendix A LAN Switch Details
LAN Switch Details

The LAN Switch Details page appears when you select Phone Tracking > LAN Switch Details.
Note
Cisco Emergency Responder supports SNMP Version 1, Version 2 and Version 2C of a LAN switch.
Description
Use the LAN Switch Details page to add, remove, or change the switches that Cisco Emergency Responder (Cisco ER) manages. Ensure you identify all switches that might have phones attached to them. You can only assign switch ports to ERLs if you enter the switches on this page. Any phones attached to unidentified switches or ports are listed as unlocated phones in Cisco ER, and are assigned to the Default ERL. Table A-17 describes the LAN Switch Details page.
Table A-17 LAN Switch Details Page
Field LAN Switch Details Switch Host Name/IP Address Description Enable CAM-based Phone Tracking
Description The IP address or DNS name of the switch. Description of this switch. Click this checkbox if there might be phones attached to this switch that do not use the Cisco Discovery Protocol (CDP) to announce themselves to the network. For non-CDP phones, Cisco ER must use the Content Addressable Memory (CAM) information on the switch to identify phones. Click Insert to add the switch to the list of switches. When you click Insert, Cisco ER asks if you want to run the switch-port and phone update process on the switch right away. Click OK to run the process now, or click Cancel to simply add the switch to the configuration without running the process immediately.
Note
Insert button
See the Manually Running the Switch-Port and Phone Update Process section on page 5-45 for information on running the process if you select not to run it immediately.
Update button Cancel Changes button

LAN Switches
Click Update when viewing an existing switch to save changes you make to the switch. Click Cancel Changes to change the fields on this page back to the last saved settings. A list of the switches you have already defined. Click on the IP address/DNS name of the switch or click the Edit icon to view and modify settings for the switch. Click the Delete icon to delete the switch.
LAN Switch list
Add LAN Switch button Click Add LAN Switch to add another switch.
A-28
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder LAN Switch Details
Table A-17
LAN Switch Details Page (continued)
Field Export Import
Description Click the Export link to export the switch definitions to another file. See the Export LAN Switch section on page A-29 for more information. Click the Import link to import a list of switches into the Cisco ER configuration. This list might be exported from your network management software. See the Import LAN Switch section on page A-30 for more information.
Related Topics

Identifying the LAN Switches, page 5-42 Manually Running the Switch-Port and Phone Update Process, page 5-45 Identifying Unlocated Phones, page 5-52 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Export LAN Switch

The Export LAN Switch page appears when you click Export in the LAN Switch Details page (opened when you select Phone Tracking > LAN Switch Details).
Description
Use the Export LAN Switch page to create a file containing the Cisco Emergency Responder (Cisco ER) switch configuration. If you need to update several switch entries in Cisco ER, you can export the switch information, make your changes in the export file using a spreadsheet, then reimport the file. You can also download a file to your local system using the Download utility. See the Downloading a File section on page 5-6 for more information. Table A-18 describes the Export LAN Switch page.
Table A-18 Export LAN Switch Page
Field Select Export Format Export button Close button Download Select a File to Download
Description The format to use for the file, such as CSV (comma separated values). Click Export to create the file. The Status box shows the status of the exportation. Click Close to close the window. Use the pulldown menu to select a LAN switches configuration file and click Download to download the file to your local system.
Enter Export File Name The name of the file you want to create. Do not include the file extension.
A-29
Appendix A LAN Switch Details
Related Topics

Exporting Switch Information, page 5-45 Downloading a File, page 5-6 Importing a Group of Switches, page 5-44 LAN Switch Details, page A-28 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Import LAN Switch

The Import LAN Switch page appears when you click Import in the LAN Switch Details page (opened when you select Phone Tracking > LAN Switch Details).
Description
Use the Import LAN Switch page to add several switches at once to the Cisco Emergency Responder (Cisco ER) configuration. You can import a previously exported file or a file that you created on your local system and uploaded using the Upload utility. See the Uploading a File section on page 5-6 for more information. Table A-19 describes the Import LAN Switch page.
Table A-19 Import LAN Switch Page
Description Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. Use this sample information to create your import file in a spreadsheet, or to determine if your network management software can create the required format.
Select File to Import Upload button Import button
Select the file from which you want to import data. Before you can import a file, you must place it in the folder mentioned on this page. Click Upload to upload a file from your local system. See the Uploading a File section on page 5-6 for more information. Click Import to add data from the information in the import file to your Cisco ER configuration. Cisco ER asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Cisco ER imports the switches but does not run the phone tracking process.
Note
If you elect not to run the phone tracking process, after importing the file, run the switch-port and phone update process. See the Manually Running the Switch-Port and Phone Update Process section on page 5-45.
Close button Import Status
Click Close to close the window. Text box that displays status information.
A-30
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Run Switch-Port and Phone Update
Related Topics

Importing a Group of Switches, page 5-44 Exporting Switch Information, page 5-45 Uploading a File, page 5-6 LAN Switch Details, page A-28 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Run Switch-Port and Phone Update

When you select Phone Tracking/Run Switch-Port & Phone Update, a dialog box appears that prompts you to Press Okay to run Switch-Port and Phone update process on Cisco Emergency Responder.
Description
Use the Run Switch-Port and Phone Update page to run manually the switch-port and phone update process.
Related Topics

Manually Running the Switch-Port and Phone Update Process, page 5-45 Defining the Phone Tracking and Switch Update Schedules, page 5-41 Identifying Unlocated Phones, page 5-52 Understanding Switch Requirements for Cisco Emergency Responder, page 5-39
Switch Port Details

The Switch Port Details page appears when you select ERL Membership > Switch Ports .
Description
Use the Switch Port Details page to assign switch ports to 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. To support switches such as the Cisco Catalyst 3750, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Cisco ER 2.0 uses the following port naming convention:
IfName: New field display name for port as given for the switch CLI (for example Fa1/5 or Gi2/0/1)
A-31
Appendix A Switch Port Details
Port Identifier: replaces the Module ID/Port ID.
It contains {optional} <<Switch ID (for stackable switches like the Cisco Catalyst 3750)>>/ {optional} <<relative position of the module in switch>> / <<relative position of port in the module>>
Search on Port IfName replaces the Module ID/Port ID search
Table A-20 describes the Switch Port Details page.

Table A-20 Switch Port Details Page
Field Find ports where...
Description Enter search criteria to select the ports you want to view or configure. To view all ports, click Find without entering any criteria. To narrow your search:
Notes If you are configuring ports, you must first generate a list of ports using the Find button.
Switch Port Search Parameters
Select All to indicate that only calls that match every criteria be selected (an AND search); select Any to indicate that calls that match any search criteria be selected (an OR search). From the pulldown menu, select the field you want to search on (ERL Name, Phone MAC Address, and so on), select the search relationship (contains, starts with, and so on), enter the search string, and select how many results per page are displayed. To search on a combination of fields, click the Plus icon (+) to add additional search parameters. (Click the Minus icon () to remove search parameters.) Click Find when you have entered all of the search parameters.
Switch Ports
The list of switch ports that match your search criteria, one line per port. Cisco ER displays a maximum number of To assign ERLs to selected ports, click the checkbox to the left of the 1,000 switch port records switch details, enter the ERL name in the text box or select the ERL at a time. If the search name from the pulldown menu, then click Assign ERL. results in more than To view and update the phone location for a port, click the View link in 1,000 switch ports, an the ports Location column. error message to refine the search is displayed. To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page: If a large number of ports To add a field, select it in the Available Fields list and click > (right match your search criteria, Cisco ER uses arrow). several pages to display To remove a field, select it in the Selected Fields list and click< (left them. Use the First, arrow). Previous, Next, and Last links at the bottom of the Note You cannot remove the ERL Name from the table view. page to move between Click Apply to save your changes on the Edit Table View page. Click pages. You can also enter Close to close the window. a specific page number in the Page field and press Enter to move to that page.
A-32
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Switch Port Details
Table A-20
Switch Port Details Page (continued)
Field
Export
Description Click Export to export the ERL to switch port configuration to another file. See the Export Switch Ports section on page A-33 for more information. Click Import to import a set of ERL-to-port mappings into the Cisco ER configuration. See the Import Switch Ports section on page A-34 for more information.
Related Topics

Notes
Import
Configuring Switch Ports, page 5-47 Identifying the LAN Switches, page 5-42 Manually Running the Switch-Port and Phone Update Process, page 5-45 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Export Switch Ports

The Export Switch Ports page appears when you click Export in the Switch Port Details page (opened when you select ERL Membership > Switch Ports ).
Description
Use the Export Switch Ports page to create a file containing the Cisco Emergency Responder (Cisco ER) switch port configuration. If you need to make changes to a large number of port-to-ERL assignments, you can export a file, make your changes in the file using a spreadsheet, and then reimport the file. You can also download a file using the Download utility, modify it on your local system, then upload it using the Upload utility. See the Downloading a File section on page 5-6 for more information. Table A-21 describes the Export Switch Ports page.
Table A-21 Export Switch Ports Page
Field Select Export Format Export button Close button Download Select a File to Download
Description The format to use for the file, such as CSV (comma separated values). Click Export to create the file. The Status box shows the status of the exportation. Click Close to close the window. Use the pulldown menu to select a file and click Download to download the file to your local system.
Enter Export File Name The name of the file you want to create. Do not include the file extension.
A-33
Appendix A Switch Port Details
Related Topics

Exporting Switch Port Information, page 5-50 Downloading a File, page 5-6 Configuring a Large Number of Ports at Once, page 5-49 Switch Port Details, page A-31 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Import Switch Ports

The Import Switch Ports page appears when you click Import in the Switch Port Details page (opened when you select ERL Membership > Switch Ports).
Description
Use the Import Switch Ports page to add or update several switch port configurations at once to the Cisco Emergency Responder (Cisco ER) configuration. Switch port configurations are mappings of ports to ERLs. To create the switch port import file, follow these steps:
Procedure
Export the switch port details. Modify the ERK field of these records and save the file. Import the file using switch port import.
You can also create the import file on your local system and then upload the file using the Upload utility. See the Uploading a File section on page 5-6 for more information. Table A-22 describes the Import Switch Ports page.
Table A-22 Import Switch Ports Page
Description Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. You can use this sample information to create your import file in a spreadsheet, but it is easier to export the switch port information from Cisco ER, modify the export file using a spreadsheet program, and then import the modified file.
Note
See the Exporting Switch Port Information section on page 5-50 for information on exporting switch port information.
Select File to Import
Select the file from which you want to import data.
A-34
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List IP Subnets
Table A-22
Import Switch Ports Page (continued)
Field Upload button Import button
Description Click Upload to upload a file from your local system. See the Uploading a File section on page 5-6 for more information. Click Import to add data from the information in the import file to your Cisco ER configuration. ERL assignments in the import file override assignments that already exist in the Cisco ER configuration.
Note
Port ERL configurations are only updated if Cisco ER has discovered the port before you import the port configuration.
Close button Import Status
Click Close to close the window. Text box that displays status information.
Related Topics

Configuring a Large Number of Ports at Once, page 5-49 Uploading a File, page 5-6 Exporting Switch Port Information, page 5-50 Switch Port Details, page A-31 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Find and List IP Subnets

The Find and List IP Subnets page appears when you select ERL Membership > IP Subnets.
Description
Use the Find and List IP Subnets page to locate and view IP subnets that you would like to modify or delete. You can also navigate to add new IP subnets from this page. Table A-23 describes the Find and List IP Subnets page.
Table A-23 Find and List IP Subnets Page
Field Description IP Subnet Search Parameters Find IP Subnets where...

IP Subnets
To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.
A-35
Appendix A Find and List IP Subnets
Table A-23
Find and List IP Subnets Page (continued)
Field IP Subnets list
Description Displays results of the IP subnet search. For IP subnet found, the system displays the Subnet ID, Subnet Mask, ERL Name, and Location Click on one of the records listed above or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field and/or the ERL Name field.
Note
When modifying an existing IP subnet, you cannot change the Subnet ID or the Subnet Mask.
Click Update to save your changes to the IP Subnet. Click the View Phones icon in any record to view all the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See the IP Subnet Phones section on page A-37. Click the Delete icon to remove an IP subnet. When you click Delete, Cisco Emergency Responder asks if you want to run the switch-port and phone update process right away. Click OK to run the process immediately or click Cancel to delete the IP subnet without running the process immediately. Cancel Changes button Add New IP Subnet Export Import Click Cancel Changes to cancel any changes made on the Configure IP Subnets page.
Note
The Cancel Changes button is viewable only on the Configure IP Subnets page.
Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See the Configure IP Subnet section on page A-36 for more information Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See the Export IP Subnets section on page A-37 for more information, Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See the Import IP Subnets section on page A-38 for more information,
Configure IP Subnet
To reach the Configure IP Subnet page, select ERL Membership > IP Subnets and click on the Add New IP Subnet link. The Configure IP Subnet page appears.
Description
Use the Configure IP Subnet page to manually define an IP Subnet and its ERL. 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. See the Network Hardware and Software Requirements section on page 1-4 for information on phone support. 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. See the Configuring IP Subnet-based ERLs section on page 5-33 and the Adding Synthetic Phones section on page 5-57
Table A-24 describes the Configure IP Subnet page.
A-36
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List IP Subnets
Table A-24
Configure IP Subnet Page
Field
Add New IP Subnet
Description The IP address of the subnet you want to define. The mask of the subnet you want to define The location of the new IP subnet. The ERL to assign to the subnet. Type in a valid ERL name or select the ERL from the drop-down list. Click Insert to add the subnet. When you click Insert, Cisco ER asks if you want to run the switch-port and phone update process on the switch right away. Click OK to run the process now, or click Cancel to simply add the IP subnet to the configuration without running the process immediately.
Subnet ID Subnet Mask Location (optional) ERL Name Insert button
Cancel Changes button
Click Cancel Changes to change the fields on this page back to the last saved settings.
Related Topics

Configuring IP Subnet-based ERLs, page 5-33 Adding Synthetic Phones, page 5-57 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
IP Subnet Phones
The IP Subnet Phones page appears when you select ERL Membership/ IP Subnets and click on the View Phones icon in any record s returned by the IP Subnet Search.
Description
Use the IP Subnet Phones to view all the IP Subnet phones discovered by Cisco Emergency Responder (Cisco ER). The IP Subnet Phones page displays the Subnet ID and the Subnet Mask for each IP subnet and lists all the phones tracked in that IP subnet and when the last phone was tracked.
Related Topics

Find and List IP Subnets, page A-35 Configure IP Subnet, page A-36
Export IP Subnets
To reach the Export IP Subnets page, select ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Export link. The Export IP Subnets page appears.
A-37
Appendix A Find and List IP Subnets
Description
Use the Export IP Subnets page to create a file containing the Cisco Emergency Responder (Cisco ER) Export IP Subnet configurations. If you need to update a large number of Export IP Subnets, you can export the phone data, make your changes in the file using a spreadsheet, and then reimport the file. You can also download a file using the Download utility, modify it on your local system, then upload it using the Upload utility. See the Downloading a File section on page 5-6 for more information. Table A-25 describes the Export IP Subnets page.
Table A-25 Export IP Subnets Page
Field Select Export Format
Description Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. Use this sample information to create your import file in a spreadsheet.
Enter Export File Name The name of the file you want to create. Do not include the file extension Export button Close button Download Select a File to Download
Related Topics

Click Export to add data from the import file to your Cisco ER configuration. Click Close to close the window. Use the pulldown menu to select a file and click Download to download the file to your local system.
Downloading a File, page 5-6 Find and List IP Subnets, page A-35 Import IP Subnets, page A-38
Import IP Subnets
To reach the Import IP Subnets page, select ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Import link. The Import IP Subnets page appears.
Description
Use the Import IP Subnet page to create or update many IP subnet phones at once from a file in which you have defined their data. Create this file using a spreadsheet that can save the information in one of the required formats. View the samples from this page before attempting to create or update an import file.
A-38
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Unlocated Phones
If you need to update many IP subnet phones, you can export the phone data, update the export file, and reimport the file. You can also upload a previously downloaded file that you have modified on your local system. See the Uploading a File section on page 5-6 for more information. Table A-26 describes the Import IP Subnets page.
Table A-26 Import IP Subnet s Page
Description Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. Use this sample information to create or update your import file in a spreadsheet.
Select File to Import Upload button Import button Close button Import Status
Related Topics

Select the file from which you want to import data. Click Upload to upload a file from your local system. See the Uploading a File section on page 5-6 for more information. Click Import to add data from the import file to your Cisco ER configuration. Click Close to close the window. Text box that displays status information.
Find and List IP Subnets, page A-35 Export IP Subnets, page A-37 Uploading a File, page 5-6
Unlocated Phones
The Unlocated Phones page appears when you select ERL Membership > Unlocated Phones.
Description
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:

The phone is attached to a switch that is not defined in Cisco ER. The phone is connected to an unsupported device, such as a router port, a hub connected to a router, or an unsupported switch. The switch to which the phone is connected is currently unreachable; for example, it does not respond to SNMP queries. The phone is not found under any configured IP subnet and the phone is not configured as a synthetic phone.
A-39
Appendix A Unlocated Phones
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 on this page. See the Too Many Unlocated Phones section on page 11-2 for troubleshooting information. Table A-27 describes the Unlocated Phones page.
Table A-27 Unlocated Phones Page
Field Description Unlocated Phone Search Parameters Find phones where... Enter search criteria to select the unlocated phones you want to find. To find all unlocated phones, click Find without entering any criteria. To narrow your search:
Select All to indicate that only phones that match every criteria be selected (an AND search); select Any to indicate that phones that match any search criteria be selected (an OR search). From the pulldown menu, select the field you want to search on (Phone Extension, Phone MAC Address, and so on), select the search relationship (is Exactly, Starts with, and so on), and enter the search string. To search on a combination of fields, click the Plus icon (+) to add additional search parameters. (Click the Minus icon to () remove search parameters.) Click Find when you have entered all of the search parameters.
Select an ERL Assign to ERL List of unlocated phones
Select the ERL you want to assign to the phones you select in the list of unlocated phones from the drop-down list, or type in the ERL name (the name you type must be an existing ERL). Click Assign to ERL to assign the selected phones to the specified ERL. A list of the phones Cisco ER could not assign to a specific ERL. If the phone has moved to a switch served by a different Cisco ER group, the Cisco ER group name is shown for the phone in the list.
Note
If there are a lot of unlocated phones, Cisco ER uses more than one page to list them. You can only assign phones to ERLs from one page at a time. Use the links at the bottom of the list to move from page to page.L
Related Topics

Identifying Unlocated Phones, page 5-52 Too Many Unlocated Phones, page 11-2 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Find and List Manually Configured Phone, page A-41
A-40
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List Manually Configured Phone
Find and List Manually Configured Phone

The Find and List Manually Configured Phones page appears when you select ERL Membership > Manually Configured Phones.
Description
Use the Find and List Manually Configured Phones page to locate and view phones that you would like to modify or delete. You can also navigate to add new phones from this page. Table A-28 describes the Find and List Manually Configured Phones page.
Table A-28 Find and List Manually Configured Phones Page
Field Description Manual Phone Search Parameters Find manual phones where Line Number... Enter search criteria to select the manually configured phones you want to find. To find all manually configured phones, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the line number in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
Manually Configure Phones
Manually Configured Phones list
Displays the search results. For each phone found, the system displays the Line Number, ERL Name, IP Address, and Location. Click on one of these records or click the Edit icon to view and modify the information for that phone. The Modify Manual Phone page appears. You can change the MAC Address, IP Address, Phone Type, Version, Location, and ERL Name.
Note
When modifying a manual phone, you cannot change the Subnet ID or the Line Number.
Click Update to save your changes. Add new Manual Phone Click Add new Manual Phone to add a manually configured phone. The Add New Manual Phone page appears. See the Add New Manual Phone section on page A-42 for more information.
Note
The Add new Manual Phone button is also available from the Modify Manual Phone page.
Export
To export Manually Configured Phone information to a file, click Export on the Find and List Manually Configured Phones page. See the Export Manual Phones section on page A-43 for more information. To import Manually Configured Phone information to a file, click Import on the Find and List Manually Configured Phones page. See the Import Manual Phones section on page A-44 for more information.
Related Topics

Import
IP Subnet Phones, page A-37 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2 Add New Manual Phone, page A-42
A-41
Appendix A Find and List Manually Configured Phone
Export Manual Phones, page A-43 Import Manual Phones, page A-44
Add New Manual Phone

To reach the Add New Manual Phone page, select ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Add new Manual Phone link. The Add New Manual Phone page appears.
Description
Use the Add New Manual Phone page to manually define a phones ERL. You need to manually define a phone if any of these conditions apply:
Cisco Emergency Responder (Cisco ER) cannot automatically track the type of phone, for example, if the phone is analog. See the Network Hardware and Software Requirements section on page 1-4 for information on phone support. The phone is hosted on an unsupported port, such as a router port, a hub connected to a router, or a port on an unsupported switch.
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. Table A-29 describes the Add New Manual Phone page.
Table A-29 Add New Manual Phone Page
Field
Add New Manual Phone
Description The extension of the phone you want to define. The MAC address of the phone, if it is an IP phone. The IP address of the phone, if it is an IP phone. The type of phone, such as analog. This field is for your information only. The version of the phones software, if any. This field is for your information only. The location of the phone. The ERL to assign to the phone. Select the ERL from the drop-down list or type in a valid ERL name. Click Insert to add the phone to the list of phones.
Note
Line Number MAC Address IP Address Phone Type Version Location ERL Name Insert button Cancel Changes button
The Insert button only appears when you are adding a phone.
Click Cancel Changes to change the fields on this page back to the last saved settings.
A-42
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List Manually Configured Phone
Related Topics

Manually Defining a Phone, page 5-53 Import Manual Phones, page A-44 Export Manual Phones, page A-43 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Export Manual Phones

To reach the Export Manual Phones page, select ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Export link. The Export Manual Phones page appears.
Description
Use the Export Manual Phones page to create a file containing the Cisco Emergency Responder (Cisco ER) manual phone configurations. If you need to update a large number of manually configured phones, you can export the phone data, make your changes in the file using a spreadsheet, and then reimport the file. You can also download a file to your local system using the Download utility, modify the file, and then upload it using the Upload utility. See the Downloading a File section on page 5-6 for more information. Table A-30 describes the Export Manual Phones page.
Table A-30 Export Manual Phones Page
Field Export Manual Phones Select Export Format
Enter Export File Name The name of the file you want to create. Do not include the file extension Export button Close button Download Select a file to download
Related Topics

Click Export to export the file to a file. Click Close to close the window. Use the pulldown menu to select a file and then click Download to download the file to your local system.
Manually Defining a Phone, page 5-53 Downloading a File, page 5-6
A-43
Appendix A Find and List Manually Configured Phone
Import Manual Phones, page A-44 Find and List Synthetic Phones, page A-45
Import Manual Phones

To reach the Import Manual Phones page, select ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.
Description
Use the Import Manual Phones page to create or update many manually configured phones at once from a file in which you have defined their data. Create this file using a spreadsheet that can save the information in one of the required formats. View the samples from this page before attempting to create or update an import file. If you need to update a lot of manually configured phones, you can export the phone data, update the export file, and reimport the file. You can also upload a file from a local system using the Upload utility and then import the data in the file. See the Uploading a File section on page 5-6 for more details. Table A-31 describes the Import Manual Phones page.
Table A-31 Import Manual Phones Page
Select File to Import Upload Import button Close button Import Status
Related Topics

Select the file from which you want to import data. Click Upload to upload a file from a local system. The Upload File page appears. See the Uploading a File section on page 5-6 for more details. Click Import to add data from the import file to your Cisco ER configuration. Click Close to close the window. Displays status messages.
Manually Defining a Phone, page 5-53 Uploading a File, page 5-6 Find and List Synthetic Phones, page A-45
A-44
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List Synthetic Phones
Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you select ERL Membership > Synthetic Phones.
Description
Use the Find and List Synthetic Phones page to locate and view phones that you would like to modify or delete. You can also navigate to add new synthetic phones from this page. Table A-32 describes the Find and List Synthetic Phones page.
Table A-32 Find and List Synthetic Phones Page
Field Description Synthetic Phone Search Parameters Find Synthetic phones where MAC Address Enter search criteria to select the synthetic phones you want to find. To find all synthetic phones, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the MAC address in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
Synthetic Phones
Synthetic Phones list
Displays the search results. For each phone found, the system displays the Line Number, ERL Name, IP Address, and Location. Click on one of these records or click the Edit icon to view and modify the information for that phone. The Modify Synthetic Phone page appears. You can change the MAC Address, IP Address, Phone Type, Version, Location, and ERL Name.
Note
When modifying a synthetic phone, you cannot change the Subnet ID or the Line Number.
Click Update to save your changes. Add new Synthetic Phone Click Add new Synthetic Phone to add a synthetic phone. The Add New Synthetic Phone page appears. See the Add New Synthetic Phone section on page A-45 for more information.
Note
The Add new Synthetic Phone button is also available from the Modify Synthetic Phone page.
Add New Synthetic Phone

To reach the Add New Synthetic Phone page, select ERL Membership > Synthetic Phones. On the Find and List Synthetic Phones page, click the Add new Synthetic Phone link. The Add New Synthetic Phone page appears.
A-45
Appendix A Find and List Users
Description
Use the Add New Synthetic Phone page to manually define a synthetic phones ERL. 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 ERs 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. Table A-33 describes the Add New Synthetic Phone page.
Table A-33 Add New Synthetic Phone Page
Field MAC Address
Description
Notes
The MAC address of the synthetic phone, or a range The synthetic MAC address must be within of MAC addresses. the following range: 00059a3b7700 0059a3b8aff Enter the MAC address in this format: xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx
ERL Name
The ERL to assign to the synthetic phone. Type in a valid ERL name or select the ERL from the drop-down list. Click Insert to add the synthetic phone to the list of The Insert button only appears when you phones. are adding a phone. Click New to add another phone. Click Update when viewing an existing phone to save changes you make to the phone. Click Cancel Changes to change the fields on this page back to the last saved settings. The New button only appears when you are viewing an existing phone. The Update button only appears when you are viewing an existing phone.
Insert button New button Update button Cancel Changes button
Related Topics

Adding Synthetic Phones, page 5-57 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Find and List Users

The Find and List Users page appears when you select User Management > User.
Description
Use the Find and List Users page to find and list current users, to add new users, and to modify and delete current users. Table A-34 describes the Find and List Users page.
A-46
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List Users
Table A-34
Find and List Users Page
Field User Search Parameters Find User where User Name
Description Enter search criteria to select the users you want to find. To find all users, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the user name in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
User
Users list
Section of the page in which the search results are displayed. To modify the user information, click the username. If after doing a search no usernames are displayed, then no users have been configured yet. Click the user name or the Edit icon to display the Modify User page, which allows you to change the users password. The Modify User page also displays which groups and roles have been assigned to the user. Click the Delete icon to delete the user from the system.
Note
Edit icon
Delete icon Add New User button Insert button Update button Cancel Changes button
You cannot delete the Administrator.
Click the Add New User button to open the Add User page. See Table A-36 for a description of the Add User page. Adds a new user from the Add User page.
Note
The Insert button is viewable only from the Add User page. The Update button is only viewable from the Modify Users page. The Cancel Changes button is viewable only from the Modify User and Add User pages.
Applies changes made from the Modify User page.

Note
Cancels changes made to the Modify User and Add User pages.
Note
Modify User
The Modify User page appears when you select User Management > User, search for a user, and then click on a user name or on the Edit icon associated with the user on the Find and List Users page.
Description
Use the Modify User page to change a current users password. Table A-35 describes the Modify User page.
A-47
Appendix A Find and List Users
Table A-35
Modify User Page
Field User Name Password Confirm Password Update button Cancel Changes button Add new User
User Groups for this user User Roles for this user
Description Name of the user whose information is being modified.

Note
You cannot change the username on the Modify User page.
Enter the new password for the user. Re-enter the new password for the user. Applies changes made from the Modify User page. Cancels changes made to the Modify User page. Click this button to add a new user. The Add User page appears. See Table A-36 for more information. Displays the groups to which the user is assigned. Displays the roles to which the user is assigned.
Add User
The Add User page appears when you select User Management > User and click Add new User on the Find and List Users page. You can also access the Add User page from the Modify User page. See the Modify User section on page A-47 for more information.
Description
Use the Add User page to add a new user to the system. Table A-36 describes the Add User page.
Table A-36 Add User Page
Field User Name Password Confirm Password Insert button Cancel Changes button
Related Topics

Description Enter the username for the new user. Enter the password for the new user. Re-enter the password for the new user. Inserts the new user. Cancels changes made to the Add User page.
Role-Based User Management, page 5-2 Find and List Roles, page A-49 Find and List User Groups, page A-51
A-48
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List Roles
Find and List Roles

The Find and List Roles page appears when you select User Management > Role.
Description
Use the Find and List Role page to find, list, modify, and delete current roles, and to add new roles. Table A-37 describes the Find and List Roles page.
Table A-37 Find and List Roles Page
Field Role Search Parameters Find Role where Role Name is
Description Enter search criteria to select the role you want to find. To find all roles, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the role in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
Roles
Section of the page in which the search results are displayed. Four default roles are created during installation and are listed here. They are:

CER System Admin CER ERL Admin CER Network Admin CER User
When you click on the Role Name link or the Description link for any of the default roles, the Standard Role page for that role displays, which displays the following information:
Note
Role Name Description List of resources assigned to that role You cannot modify any of the information for default roles. 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. When you click on the role name, description, or Edit icon for a role that you have created, the Modify Role page appears. See Table A-38 for more information on the Modify Role page. Edit icon Delete icon Add New Role button Click the Edit icon to display the Modify Role page. See Table A-38 for information on the Modify Role page. Click the Delete icon to delete the role from the system.
Note
You cannot delete any of the default roles.
Click Add New Role to display the Add Role page. This button is also available on the Modify Role and Add Role pages. See Table A-39 for information on the Add Role page.
A-49
Appendix A Find and List Roles
Modify Role
The Modify Role page appears when you select User Management > Role, search for a role, and then click on a role name, description, or the Edit icon associated with the role on the Find and List Roles page.
Description
Use the Modify Role page to modify information for an existing role.
Note
You cannot modify any information for the four default roles. Table A-38 describes the Modify Role page.
Table A-38
Modify Role Page
Field Modify Role Role Name Description

Resource Permissions
Description The name of the new role you are modifying.

Note
The Role Name cannot be changed.
A description of the role you are modifying. Modify the description by adding new text in the text box. This section of the page displays a list of all available resources. The check boxes to the left of the resources indicate which resources have been assigned to this role. Modify the resource assignments by checking or unchecking the boxes. Click Select All to select all the listed resources. Click Clear All to deselect all currently selected resources. Click Update to save the changes made to the Modify Role page. Click Cancel Changes to cancel the changes made to the Modify Role page. Allows you to add a new role. See the Add Role section on page A-50 for information on adding new roles.
Select All button Clear All button Update button Cancel Changes button Add new Role button
Add Role
The Add Role page appears when you select User Management > Role and click Add new Role on the Find and List Roles page. You can also access the Add Role page from the Modify Role and Standard Role pages. See the Modify Role section on page A-50 for more information.
Description
Use the Add Role page to add a new role to the system.
A-50
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List User Groups
Table A-39 describes the Add Role page.

Table A-39 Add Role Page
Field Add Role Role Name Description Resource Permissions
Description The name of the new role you are adding. A description of the new role. This section of the page displays a list of all available resources. The check boxes to the left of each resource allow you to select or deselect the resource to be assigned to the new role. Click Select All to select all the listed resources. Click Clear All to deselect all currently selected resources. Click Insert to add the new role. Click Cancel Changes to cancel the Add Role operation.
Select All button Clear All button Insert button Cancel Changes button
Related Topics

Role-Based User Management, page 5-2 Find and List Users, page A-46 Find and List User Groups, page A-51
Find and List User Groups

The Find and List User Groups page appears when you select User Management > User Group.
Description
Use the Find and List User Groups page to find, list, modify, and delete current user groups, and to add new user groups. Table A-40 describes the Find and List User Groups page.
Table A-40 Find and List User Groups Page
Field Description User Group Search Parameters Find User Group where Enter search criteria to select the user group you want to find. User Group Name To find all user groups, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the user group in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
A-51
Appendix A Find and List User Groups
Table A-40
Find and List User Groups Page (continued)
Field User Groups
Description Section of the page in which the search results are displayed. When you click on the User Group Name link, the Description link, or the Edit icon, the Modify User Group page appears. See the Modify User Group section on page A-52 for information. Click the Edit icon to display the Modify User Group page. See the Modify User Group section on page A-52 for information. Click the Delete icon to delete the user group from the system.
Note
Edit icon Delete icon Add New User Group button
You cannot delete default user groups that were created during installation.
Click the Add New User Group button to display the Add User Group page. See Table A-42 for information on the Add User Group page.
Modify User Group

The Modify User Group page appears when you select User Management > User Group, search for a user group, and then click on a user group name, description, or the Edit icon associated with the user group on the Find and List User Groups page.
Description
Use the Modify Role page to modify information for an existing user group. Table A-41 describes the Modify User Group page.
Table A-41 Modify User Group Page
Field Modify User Group User Group Name Description

Add Users to the Group
Description The name of the user group you are modifying.

Note
The User Group Name cannot be changed.
A description of the User Group you are modifying. Modify the description by adding or changing text in the text box. This section of the page has a text box that displays the names of the users currently in the user group. Allows you to add more users to the group. When you click Add User, the Add User page appears. See the Add User section on page A-48 for more information. Allows you to remove users from the group. To do so, highlight the username in the text box and click Remove Users. This section of the page has a text box that displays the roles currently assigned to the user group.
Add Users button Remove Users button

Assign Roles to Group
A-52
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Find and List User Groups
Table A-41
Modify User Group Page (continued)
Field Add Roles button
Description Allows you to assign more roles to the group. When you click Add Roles, the Add Role page appears. See the Add Role section on page A-50 for more information.
Note
You cannot add roles to the default roles that were assigned to a default user group during installation. If the user group you are modifying is a default user group, then the Add Roles button is not visible.
Remove Roles button
Allows you to remove roles from the group. To do so, highlight the role name in the text box and click Remove Roles.
Note
You cannot remove the default roles that were assigned to a default user group during installation. If the user group you are modifying is a default user group, then the Remove Roles button is not visible.
Update button Add New User Group button
Click Update to save the changes made to the Modify User Group page. Allows you to a add new user group. See the Add User Group section on page A-53 for information.
Add User Group

The Add User Group page appears when select User Management > User Group and click Add new User Group on the Find and List User Groups page. You can also access the Add User Group page from the Modify User Group page. See the Modify User Group section on page A-52 for more information.
Description
Use the Add User Group page to add a new user group to the system. Table A-42 describes the Add User Group page.
Table A-42 Add User Group Page
Field Add User Group User Group Name Description Add Users to the Group Add Users button Remove Users button
Assign Roles to Group
Description The name of the new user group you are adding. A description of the new user group. This section of the page has a text box that displays the names of the users you add to the user group. Allows you to add users to the new group. When you click Add Users, the Add Users page appears. See the Add User section on page A-48 for more information. Allows you to remove users from the group. To do so, highlight the username in the text box and click Remove Users. This section of the page has a text box that displays the roles you assign to the new user group. Allows you to assign roles to the new group. When you click Add Roles, the Add Roles page appears. See the Add Role section on page A-50 for more information.
Add Roles button
A-53
Appendix A Call History
Table A-42
Add User Group Page (continued)
Field Remove Roles button Insert button
Description Allows you to remove roles from the group. To do so, highlight the role name in the text box and click Remove Roles. Click Insert to add the new role.
Related Topics

Role-Based User Management, page 5-2 Find and List Users, page A-46 Find and List Roles, page A-49
Call History
The Call History page appears when you select Reports > Call History.
You must have system administrator, ERL administrator, network administrator, or user authority to access this page.
Description
Use the Call History page to view the history of emergency calls made from your network. Cisco Emergency Responder (Cisco ER) 2.0 maintains the most recent 10,000 call history records. There is no restriction on when these calls were placed. Table A-43 describes the Call History page.
Table A-43 Call History Page
Field Description Call History Search Parameters Search criteria Enter search criteria to select the calls you want to find. To find all calls, click Find without entering any criteria. To narrow your search:
Select All to indicate that only calls that match every criteria be selected (an AND search); select Any to indicate that calls that match any search criteria be selected (an OR search). From the pulldown menu, select the field you want to search on (ERL Name, Callers Extension, and so on), select the search relationship (contains, begins with, and so on), and enter the search string. To search on a combination of fields, click the Plus icon (+) to add additional search parameters. Click the Minus icon () to remove search parameters. When you have entered all of the search parameters, click Find.
A-54
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder ERL Audit Trail
Table A-43
Call History Page (continued)
Field Call History Matching Records
Description A list of emergency calls that match your search criteria is displayed with the following information:

ERL NameClick the name to view details about the ERL and its ALI information. See the Find ERL Data section on page A-12 for descriptions of the configuration fields. Callers ExtensionThe extension used to place the emergency call. TimeThe time the call was made. DateThe date the call was made. Route Pattern-ELIN No.The route pattern and ELIN combination used for the call. See the Find ERL Data section on page A-12 for more detailed information about these fields. CommentsAny comments entered about the call. If you click the Edit icon, the Call Details page appears, on which you can enter or change comments about the call in the Comments about the call text box.
If a large number of calls match your search criteria, the system uses several pages to display them. Use the First, Previous, Next, and Last links at the bottom of the page to move between pages. You can also enter a specific page number in the Page field and press Enter to move to that page. Download Update Cancel Changes Close Click Download to save the call history data to a spreadsheet that you can view and/or download to your local system. Click Update to include your comments in the call history for the call.
Note
Only viewable from the Call Details page. Only viewable from the Call Details page. Only viewable from the Call Details page.
Click Cancel Changes to remove unsaved comments. You can then re-enter comments.
Note
Click Close to close the Call Details page.

Note
Related Topics

Viewing the Emergency Call History, page 5-57 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
ERL Audit Trail

The ERL Audit Trail page appears when you do one of these:

Select Reports > ERL Audit Trail. Click view in the Audit Trail column for an ERL displayed on the ERL Configuration page (opened by selecting ERL > ERL Details.)
You must have system administrator, ERL administrator, or network administrator authority to access this page.
A-55
Appendix A Export PS-ALI Records
Description
Use the ERL Audit Trail page to view the change history for ERLs. Table A-44 describes the ERL Audit Trail page.
Table A-44 ERL Audit Trail Page
Field ERL Audit Trail Search criteria
Description Enter search criteria to select the audit details you want to find. To find all audit details, click Find without entering any criteria. To narrow your search:
Select All to indicate that only audit details that match every criteria be selected (an AND search); select Any to indicate that audit details that match any search criteria be selected (an OR search). From the pulldown menu, select the field you want to search on (ERL Name, Modified By, and so on), select the search relationship (contains, begins with, and so on), and enter the search string. If searching by ERL Name, you can type in the ERL name or use the pulldown menu to select an ERL. To search on a combination of fields, click the Plus icon (+) to add additional search parameters. Click the Minus icon () to remove search parameters. When you have entered all of the search parameters, click Find.
Matching Records
A list of ERL change records that match your search criteria. Each change to an ERL is recorded in a separate record, so a single ERL may have many audit records. The list displays the following information for each record:
Note
ERL NameThe name of the ERL that was changed. Modified ByThe login ID of the user who changed the ERL. Modified TimeThe date and time the ERL was changed. Modification DetailsA list of the fields that were changed in the ERL or its ALI. Use the scroll bars to move up and down in the Modification Details text box. If there are a large number of records match your search, Cisco ER uses more than one page to list them. Use the links at the bottom of the list to move from page to page. You can also enter a page number in the Page field and press enter to go to a specific page.
Related Topics

Viewing the Audit Trail for an ERL, page 5-38 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
Export PS-ALI Records

The Export PS-ALI Records page appears when you select Tools > Export PS-ALI Records.
A-56
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder Export PS-ALI Records
Description
Use the Export PS-ALI Records page to create a file in a NENA format that you can send to your service provider. Your service provider uses this file to update their ALI data for your organization. Your service provider needs this information so that emergency calls from your ERLs can be routed to the correct public safety answering point (PSAP). Always submit an export file to your service provider. If you skip submitting an export file, subsequent export files might not have correct command information for the database update, and you will have to manually edit the export file to make it uploadable. Your service provider can provide you with error information if the database upload fails.
Note
If you change the customer code in your ALI record, Cisco ER generates two records when exporting ALI: a Delete record to remove the ALI with the old code, and an Insert record to add the ALI with the new code. This Delete/Insert sequence is only generated the first time you export ALI after changing the code. You must ensure you submit this export file to the service provider. See the ALI Information (for ERL Name) section on page A-17 for information about ALI fields. You can also use export files to back up your ERL configuration. Table A-45 describes the Export RS-ALI Records page.
Table A-45
Export PS-ALI Records Page
Field Export PS-ALI Records Select NENA Format File to Export
Description The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0. The name of the file you want to create. Do not include a file extension.
Company Name (NENA The name of your company. You cannot have spaces in the name. Header field) Note The data complies with NENA requirements. Cycle Counter (NENA Header field) The sequence in which this export is created. This field is automatically increased each time you export data. You can change it if it becomes unsynchronized with the sequence submitted to your service provider. However, changing the sequence number does not affect the data placed in the fileif you are redoing an export, you will have to manually edit the export file to change the record status fields.
Note
The data complies with NENA requirements.
Export button Cancel button
Click Export to create the export file. Click Cancel to cancel the export operation.
Related Topics

ALI Information (for ERL Name), page A-17 Negotiate ALI Submission Requirements With Your Service Provider, page 1-19 Exporting ERL Information, page 5-36 Exporting ALI Information for Submission to Your Service Provider, page 5-37 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-57
Appendix A PS-ALI Converter
PS-ALI Converter
The PS-ALI Converter page appears when you select Tools > PS-ALI Converter.
Description
Use the PS-ALI Converter tool to generate an ERL file that can be accepted by the Cisco Emergency Responder (Cisco ER) ERL. The PS-ALI Converter tool converts ALI files from a NENA 2.0 format into a csv (Comma Separated Value) text file. You can then modify the csv file (for example, to add or change an ERL name) and save the modified ERL details by importing the file into Cisco ER.
Note
If you change the customer code in your ALI record, Cisco ER generates two records when exporting ALI: a Delete record to remove the ALI with the old code, and an Insert record to add the ALI with the new code. This Delete/Insert sequence is only generated the first time you export ALI after changing the code. You must ensure you submit this export file to the service provider. See the ALI Information (for ERL Name) section on page A-17 for information about ALI fields. Table A-46 describes the PS-ALI Converter page.
Table A-46 PS-ALI Converter Page
Field Export PS-ALI Records Select PS-ALI file (NENA 2.0 format) Output File (in csv format) Name Convert button Cancel button
Related Topics

Description The name of the PS-ALI file to be converted. The file must be in the default format, NENA format 2.0. The name of the csv file you want to create. Click Convert to create the csv file. Click Cancel to stop the converting process. and close the window.
ALI Information (for ERL Name), page A-17 Negotiate ALI Submission Requirements With Your Service Provider, page 1-19 Exporting ERL Information, page 5-36 Exporting ALI Information for Submission to Your Service Provider, page 5-37 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26 Understanding E911 and Cisco Emergency Responder Terminology, page 1-2
A-58
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder ERL Debug Tool
ERL Debug Tool

The ERL Debug Tool page appears when you select Tools > ERL Debug Tool.
Description
The ERL Debug Tool takes the phone extension as input and displays the ERL(s) currently being used for routing emergency calls for the phone(s). Use this diagnostic tool to verify the Cisco ER configuration during the ERL creation and the ERL assignment phase and to troubleshoot calls directed to incorrect ERLs. Table A-47 describes the ERL Debug Tool page.
Table A-47 ERL Debug Tool Page
Field ERL Debug Tool Find Phones where extension
Description Enter search criteria to select the extensions you want to find. To find all extensions, click Find without entering any criteria. To narrow your search, use the pulldown menu to select the search condition (contains, Starts with, and so on) and enter the extension in the text box. You can also select how many results per page will be displayed from the pulldown menu. When you have specified your search criteria, click Find.
Matching records
Section of the page that displays the ERL(s) currently being used for routing emergency calls for the phone(s). For each extension found, the following information is displayed:

Phone extension ERL IP Address MAC Address Why this ERL is Used?
If the configurations are not correct, make any required changes.

Related Topics

How to Use the Cisco ER Admin Utility Tool, page 11-19 Understanding ERLs, page 5-25 Overview of ERL Management, page 5-26
A-59
Appendix A ALI Formatting Tool
ALI Formatting Tool

The ALI Formatting Tool page appears when you select Tools > ALI Formatting Tool.
Description
Use the ALI Formatting Tool page to customize the format of PS-ALI records to facilitate error-free PS-ALI record transactions with service providers. The ALI Formatting Tool (AFT) reads the NENA file generation by the Cisco ER and displays all ELIN records. You can then do one or more of the following:

View the details of the ALI records Select a record and update the value for ALI fields, which can be edited using the AFT Perform a bulk update operation on multiple ALI records Selectively export ALI records based on area code, city code, and so on
Table A-48 describes the ALI Formatting Tool page.

Table A-48 ALI Formatting Tool Page
Field Description Select a Service Provider Use the pulldown menu to select a service provider Select an Input File for the Use the pulldown menu to select an input file ALI Formatting Tool from the List Below Submit button Click the Submit button to display the Search for ELINs page, which is described in Table A-49.
Table A-49 describes the Search for ELINs page.

Table A-49 Search for ELINs Page
Field Use Search to Filter-out ELINs on Area, City and Local Code(last 4-digits). Add (+) button Remove (-) button
Description Allows you to search ELINs by Local Code, Area Code, or City Code.
Add more search parameters Remove search parameters
Table A-50 describes the Bulk Update page.
A-60
OL-12376-01
Appendix A
Administration Web Interface For Cisco Emergency Responder File Management Utility
Table A-50
Bulk Update Page
Field Remove Changes/Generate File button Search for ELIN
Description Shows all the ELINs that have been changed.
Displays the ELIN search page.
Table A-51 describes the Review Changes/Generate File page.

Table A-51 Review Changes/Generate File Page
Field Add More ELIN Remove ELIN Search for ELIN Generate File button
Description Displays the remaining ELIN(s) that have not been changed. Removes the selected ELIN(s) from the list Displays the ELIN search screen Generates the formatted file.
Table A-52 describes the Download Formatted File page.

Table A-52 Download Formatted File Page
Field Download Formatted File button

Related Topics

Description Displays a Download File dialog box so that the formatted file can be downloaded to the local system.
ALI Information (for ERL Name), page A-17 Exporting ALI Information for Submission to Your Service Provider, page 5-37
File Management Utility

The File Management Utility page appears when you select Tools > File Management Utility.
Description
Use the File Management Utility page to search for, download, or delete exported files. Table A-53 describes the File Management Utility page.
A-61
Appendix A File Management Utility
Table A-53
File Management Utility Page
Field Search Parameters

Please Select:
Description From the pulldown menu, select the type of file that you want to search for. Click Search to perform the search. Area of the page that displays the search results. Displays the File Name, Last Modified data, and File Size for each file found. Downloads the selected file.
Note
Search button Exported Files Download button
Before you click Download, click in the box next to the file name to select the file. To select all files listed, click in the box next to the File Name column heading. Before you click Delete, click in he box next to the file name to select the file. To select all files listed, click in the box next to the File Name column heading.
Delete button
Deletes the selected file.

Note
Related Topics
Using the Upload and Download Utilities, page 5-6
A-62
OL-12376-01
A P P E N D I X
Serviceability Web Interface For Cisco Emergency Responder

These topics describe the fields on the pages of the Cisco Emergency Responder (Cisco ER) serviceability web interface.

Control Center, page B-1 Event Viewer, page B-2 SNMP Community String Configuration, page B-4 SNMP V1/V2c Notification Destination Configuration, page B-6 SNMP User Configuration, page B-7 MIB2 SystemGroup Configuration, page B-11 CPU and Memory Usage, page B-11 Processes, page B-13 Disk Usage, page B-15 System Logs Menu, page B-15
Control Center
The Control Center page appears when you select Tools > Control Center.
You must have serviceability authority to access this page.

Description
Use the Control Center page to view the services running on the server and then start, stop, and restart these services. This page displays a list of services currently running on the server. Radio buttons in front of each service name allows you to select each service to perform the desired action. Table B-1 describes the Control Center page.
B-1
Appendix B Event Viewer
Table B-1
Control Center Page
Field Start button Stop button Restart button Refresh button Service Name Status
Related Topics
Description Start the selected service(s) Stop the selected service(s) Restart the selected service(s) Refresh the list of currently running services on the selected server Names of the currently running services on the selected server. To select a service, click the radio button next to the service name. Current status of the selected service
Starting and Stopping a Cisco Emergency Responder Server, page 11-23
Event Viewer
The Event Viewer page appears when you select Tools > Event Viewer.

Description
Use the Event Viewer page to view Cisco ER events for the previous six months. Table B-2 describes the Event Viewer page.
Table B-2 Event Viewer Page
Field Type pulldown menu
Description
Note
This pulldown menu contains two options: Type and Module. When you choose either Type or Module, the pulldown menu to the right changes to display the available Type or Module options.
Allows you to select which type of event you want to view. The available types are:

ALL INFO WARN ERROR
These options are displayed in the pulldown menu to the right of the Type pulldown menu.
B-2
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder Event Viewer
Table B-2
Event Viewer Page (continued)
Field
Description This pulldown menu contains two options: Type and Module. When you choose either Type or Module, the pulldown menu to the right changes to display the available Type or Module options.
Module pulldown menu Note
Allows you to select the Cisco ER module for which you want to view events. When you select Module from the pulldown menu, the menu to the right changes to show the available modules. The available options are:

All CER_DATABASE CER_SYSADMIN CER_REMOTEUPDATE CER_TELEPHONY CER_PHONETRACKINGENGINE CER_AGGREGATOR CER_ONSITEALERT CER_GROUP CER_CALLENGINE CER_CLUSTER
Items Per Page menu

Matching Records
Allows you to select the number of events displayed per page. Options are 10, 20, 30, 40, or 50 events. Displays search results.
Note
This area of the page is not visible until you perform a search operation. INFO WARN ERROR
Type column
Displays the type of event. The Type column will display one of the following:

Use the Up and Down arrows to perform an ascending or descending sort of the results. Time column Displays the time of the event. Use the Up and Down arrows to perform an ascending or descending sort of the results.
B-3
Appendix B SNMP Community String Configuration
Table B-2
Event Viewer Page (continued)
Field Module column
Description Displays the Cisco ER module to which the event applies. The modules are:

CER_DATABASE CER_SYSADMIN CER_REMOTEUPDATE CER_TELEPHONY CER_PHONETRACKINGENGINE CER_AGGREGATOR CER_ONSITEALERT CER_GROUP CER_CALLENGINE CER_CLUSTER
Use the Up and Down arrows to perform an ascending or descending sort of the results. Message column Displays the message associated with each event. Use the up and down arrows at the right of the text box to scroll through the message.
Related Topics
Using the Event Viewer, page 6-2
SNMP Community String Configuration

The SNMP Community String Configuration page appears when you select SNMP > V1/V2c Configuration > Community String.

Description
Use the SNMP Community String Configuration page to view, add, update, and delete community strings. Community strings control access to the Cisco ER by clients using SNMP V1 and V2c. Table B-3 describes the SNMP Community String Configuration page.
Table B-3 SNMP Community String Configuration Page
Field Community String Name column
Description Lists all community strings defined for the selected server. Click on the name of the community string to update the information for that community string.
Add New button or icon Add a new community string for the selected server. When you click on this button, Cisco ER opens a second SNMP Community String Configuration page.
Note
Clicking the Add New button brings up the same screen displayed when you click on the Add New icon.
B-4
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder SNMP Community String Configuration
Table B-3
SNMP Community String Configuration Page (continued)
Field Delete Selected button or icon
Description Deletes the selected community strings. To delete a community string, you must first select it from the list of community strings. Click in the box to the left of the community string name to select it. To delete all community strings from the selected server, click on the box to the left of the Community String Name column heading.
Note
Clicking the Delete Selected button initiates the same action as does clicking on the Delete icon at the top of the page.
Use the second SNMP Community String Configuration page to add new SNMP community strings and to update existing SNMP community strings. Table B-4 describes the second SNMP Community String Configuration page.
Table B-4 SNMP Community String Configuration Page2
Field Community String Name

Host IP Address Information
Description If you are adding a new community string, type the name of the new community string into this text box. If you are updating information for an existing community string, the name of community string being updated is displayed. Click this radio button to allow any host to access the Cisco ER using SNMP. Click this radio button to specify which hosts can access the Cisco ER using SNMP. To add hosts that you want to have SNMP access, enter the IP addresses of the new hosts and click Insert; to remove hosts that you no longer want to have SNMP access, enter the IP addresses of the hosts and click Remove. When adding a new community string, allows you to specify the access privilege for the new community string. When updating a community string, displays the current access privilege level. The available access privilege levels are as follows:

Accept SNMP Packets from any host Accept SNMP Packets only from these hosts
Access Privileges pulldown menu
Insert button or icon Clear button or icon
Inserts a new community string for the selected server. You must fill in the other fields on this page before you can insert the new community string. Clears the community string information displayed on the current page.
Related Topics
Configuring the SNMP Community String, page 6-3
B-5
Appendix B SNMP V1/V2c Notification Destination Configuration
SNMP V1/V2c Notification Destination Configuration

The SNMP Notification Destination Configuration page appears when you select SNMP > V1/V2c Configuration > Notification Destination.

Description
Use the SNMP Notification Destination Configuration page to identify the destination to which the Cisco ER SNMP agent will send trap messages. Table B-5 describes the SNMP Notification Destination Configuration page.
Table B-5 SNMP Notification Destination Configuration Page
Field Server pulldown menu
Description Name of the server for which you want to view, add, update, or delete SNMP notification destination information. After you select a server, Cisco ER displays the currently configured information in the following format:

Destination IP Address Port Number SNMP Version Community String Name Notification Type
Click on a Destination IP Address to update the information for the device at that address. Destination IP Address column Lists the IP addresses of all notification destinations defined for the selected server. When you click on an IP address in this list, Cisco ER opens the Add/Update Notification Destination page.
Add New button or icon Add a new notification destination for the selected server. When you click on this icon, Cisco ER opens the Add/Update Notification Destination page. Delete Selected button or icon Deletes the selected notification destinations. To delete a notification destination, you must first select it from the list of notification destinations. Click in the box to the left of the notification destination to select it. To delete all notification destinations from the selected server, click on the box to the left of the Destination IP Address column heading.
Use the second Add/Update Notification Destination page to add new notification destinations and to update existing notification destinations. Table B-6 describes the Add/Update Notification Destination page.
Table B-6 Add/Update Notification Destination Page
Field Host IP Addresses pulldown menu
Description Select Add New from this pulldown menu to add a new notification destination.
Note
If you reached this page by clicking on an existing Destination IP Address on the SNMP Notification Destination Configuration page, the Host IP Address and Port Number fields display the currently configured information.
B-6
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder SNMP User Configuration
Table B-6
Add/Update Notification Destination Page (continued)
Field Host IP Address field Port Number field SNMP Version Notification Type pulldown menu
Description IP address of the new notification-destination host Port number on the new notification-destination host that will receive the notifications from the Cisco ER SNMP agent Click on one of the radio buttons to specify SNMP V1 or V2c Select the SNMP message type for the new notification-destination host. The options are:

Trap Inform
Community String pulldown menu Insert button Clear button
Select the community string for the new notification-destination host. Insert the new notification destination for the selected server. Clears the notification destination information displayed on the current page.
Related Topics
Configuring the SNMP V1/V2C Notification String, page 6-4
SNMP User Configuration

The SNMP User Configuration page appears when you select SNMP > V3 Configuration > User.

Description
Use the SNMP User Configuration page to configure new SNMP V3 users. Table B-7 describes the SNMP User Configuration page.
Table B-7 SNMP User Configuration Page
Description Name of the server for which you want to view, add, update, or delete users. After you select a server, Cisco ER displays the currently configured information in the following format:

User Name Authentication Required Authentication Protocol Privacy Required Privacy Protocol Access Privileges
Click on a User Name to display the Add/Update SNMP User Configuration page, from which you can update the information for that user.
B-7
Appendix B SNMP User Configuration
Table B-7
SNMP User Configuration Page (continued)
Field
Description
Add New User button or Add a new user for the selected server. When you click on this icon, Cisco ER opens the icon Add/Update SNMP User Configuration page. Delete Selected button or icon Deletes the users. To delete a user, you must first select it from the list of users. Click in the box to the left of the user name to select it. To delete all users from the selected server, click on the box to the left of the User Name column heading.
Use the second SNMP User Configuration page to configure new SNMP V3 users. Table B-8 describes the Add/Update SNMP User Configuration page.
Table B-8 SNMP User Configuration Page2
Field User Name field
Description Enter the name of the new SNMP V3 user.

Note
If you reached this page by clicking on an existing user name on the SNMP User Configuration page, the fields on this page display the currently configured information. If authentication is required for this user, click on the check box labeled Authentication Required Enter the authentication password for the new user in the Password and Reenter Password text boxes To select the authentication protocol for the new user, click on radio button for either MD5 or SHA If privacy is required for this user, click on the check box labeled Privacy Required Enter the privacy password for the new user in the Password and Reenter Password text boxes To select the privacy protocol for the new user, click on radio button labeled DES Specify which hosts can access the Cisco ER using SNMP. You can insert IP addresses for new hosts that you want to have SNMP access to the Cisco ER, or you can remove IP addresses of hosts that you no longer want to have SNMP access to the Cisco ER. Allow any host to access the Cisco ER using SNMP.
Authentication Information
Use this section to configure the following information:

Privacy Information
Use this section to configure the following information:

Host IP Addresses Information
Use the radio buttons in this section of the page to do the following:
Access Privileges pulldown menu
When adding a new user, this pulldown menu allows you to specify the access privilege for the new user. When updating a users information, this field displays the current access privilege level. The available access privilege levels are as follows:

Insert button or icon
Insert the new user information for the selected server.
B-8
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder SNMP V3 Notification Destination Configuration
Table B-8
SNMP User Configuration Page2 (continued)
Field Clear button or icon
Description Clears the user information displayed on the current page.

Related Topics
Configuring SNMP Users, page 6-5
SNMP V3 Notification Destination Configuration

The SNMP Notification Destination Configuration page appears when you select SNMP > V3 Configuration > Notification Destination.

Description
Use the SNMP V3 Notification Destination Configuration page to identify the destination to which the Cisco ER SNMP agent will send trap messages. The SNMP V3 Notification Destination information provides enhanced security since each notification string is associated with a specific user. Table B-9 describes the SNMP V3 Notification Destination Configuration page.
Table B-9 SNMP V3 Notification Destination Configuration Page
Description Name of the server for which you want to view, add, update, or delete SNMP notification destination information. After you select a server, Cisco ER displays the currently configured information in the following format:

Destination IP Address Port Number Security Model Security Name Security Level Notification Type
Click on a Destination IP Address to update the information for the device at that address. When you click on an IP address in this list, Cisco ER opens the Add/Update Notification Destination page. Destination IP Address column Lists the IP addresses of all notification destinations defined for the selected server. When you click on an IP address in this list, Cisco ER opens the Add/Update Notification Destination page.
Add New button or icon Add a new notification destination for the selected server. When you click on this icon, Cisco ER opens the Add/Update Notification Destination page. Delete Selected button or icon Deletes the selected notification destinations. To delete a notification destination, you must first select it from the list of notification destinations. Click in the box to the left of the notification destination to select it. To delete all notification destinations from the selected server, click on the box to the left of the Destination IP Address column heading.
B-9
Appendix B SNMP V3 Notification Destination Configuration
Use the second SNMP V3 Notification Destination page to add new notification destinations and to update existing notification destinations. Table B-10 describes the second SNMP V3 Notification Destination Configuration page.
Table B-10 SNMP V3 Notification Destination Configuration Page2
Field Host IP Addresses pulldown menu
Description Select Add New from this pulldown menu to add a new notification destination.
Note
If you reached this page by clicking on an existing Destination IP Address on the SNMP V3 Notification Destination Configuration page, the Host IP Address and Port Number fields display the currently configured information.
Host IP Address field Port Number field Notification Type pulldown menu
IP address of the new notification-destination host Port number on the new notification-destination host that will receive the notifications from the Cisco ER SNMP agent Select the SNMP message type for the new notification-destination host. The options are:

Trap Inform
Remote SNMP Engine ID
Select Add New from this pulldown menu to add a new remote SNMP engine ID. When you select Add New, a new Remote SNMP Engine ID field displays. Enter the new Remote SNMP Engine ID in this field.
Note
Displays only if you selected Inform as the notification type from the Notification Type pulldown. If you reached this page by clicking on an existing Destination IP Address on the SNMP V3 Notification Destination Configuration page, the Remote SNMP Engine ID field displays the currently configured information.
Note
Security Level pulldown menu
Allows you to select the security level for the new V3 notification destination. The available options are:

noAuthNoPriv AuthNoPriv authPriv
User Information
Displays information about the users currently configured and allows you to associate a user with the new V3 notification destination. This section of the page includes the following:

User Name Authentication Protocol Privacy Protocol
Click on the radio button to the left of the User Name column to select a user to be associated with the new V3 notification destination. Insert button or icon Clear button or icon Inserts the new notification destination for the selected server. Clears the notification destination information displayed on the current page.
Related Topics
Configuring the SNMP V3 Notification Destination, page 6-5
B-10
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder MIB2 SystemGroup Configuration
MIB2 SystemGroup Configuration

The MIB2 SystemGroup Configuration page appears when you select SNMP > System Group Configuration > MIB2 System Group Configuration.

Description
Use the MIB2 System Group Configuration page to specify the name and physical location of the contact person for MIB2 managed mode. Table B-11 describes the MIB2 System Group Configuration page.
Table B-11 MIB2 System Group Configuration Page
Field Server pulldown menu System Contact System Location Update button or icon Clear button or icon
Description Name of the server for which you want to update the MIB2 contact information. After you select a server, Cisco ER displays fields in which you enter the name and physical location of the contact. The name of the MIB2 contact. The physical location of the managed node. Saves the updated MIB2 contact information. Clears the MIB2 contact information displayed on the current page.
Related Topics
Configuring MIB2, page 6-6
CPU and Memory Usage

The CPU and Memory Usage page appears when you select System Monitor > CPU & Memory Usage.

Description
Use the CPU and Memory Usage page to view the CPU and memory usage for the Cisco ER system. Table B-12 describes the CPU and Memory Usage page.
Table B-12 CPU and Memory Usage Page
Field Disable Auto-Refresh Set the screen reset value Set CPU Logging Interval
Description Click this check box to disable auto-refresh of the information displayed on this page. Specify in seconds how often this page should be refreshed. Specify in seconds how often CPU usage is logged. The interval must be between 5 and 600 seconds.
B-11
Appendix B CPU and Memory Usage
Table B-12
CPU and Memory Usage Page (continued)
Field Processors Download CPU Log File Processor %User %System %Nice
Description This section displays the percentage of CPU time being used by various system components. Click on this link to download to a file the currently displayed CPU and memory usage information. When you click on this link, a new page opens that lists all the saved CPU log files. For more information about this screen, see Table B-13. Name of the processor. Percentage of processor time being used by the User mode. Percentage of processor time being used by the System mode. Percentage of processor time being used by nice tasks.
Note
Nice is a value associated with a process that determines when the process is executed. Nice tasks are only those tasks whose nice value is positive.
%Idle %Irq %Softirq %I/O Wait %CPU Start Log button

Memory
Percentage of time in which the processor is idle. Percentage of processor time being used by interrupt requests (IRQ). Percentage of processor time being used by soft IRQs.
Note
A soft IRQ is an interrupt request that can be deferred.
Percentage of time that the processor is executing read or write operations. The processor's share of the elapsed CPU time (excluding idle time) since last update, expressed as a percentage of CPU time. Starts a log file of the current CPU usage.
Note
You can create a maximum of 25 CPU log files.
This section displays the percentage of memory allocated for different uses.
Download Memory Log Click on this link to download to a file the currently displayed CPU and memory usage File information. When you click on this link, a new page opens that lists all the saved CPU log files. For more information about this screen, see Table B-14. Total (KB) Used (KB) Free (KB) Shared (KB) Buffers (KB) Cached (KB) Total Swap (KB) Used Swap (KB) Free Swap (KB) %VM Used Start Log button The amount of memory available, in kilobytes. Amount of memory currently being used, in kilobytes. Amount of memory that is available for use, in kilobytes. Amount of memory used by shared processes, in kilobytes. Amount of memory used by buffers, in kilobytes. Amount of memory used for caching, in kilobytes. Amount of total swap space, in kilobytes Amount of swap space currently being used, in kilobytes. Amount of available swap space, Amount of virtual memory being used. Starts a log file of the current memory usage. Use the CPU Log Files page to view and download the CPU log files. Table B-13 describes the CPU Log Files page.
B-12
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder Processes
Table B-13
CPU Log Files Page
Field Download button
Description Download the selected log files. You must first select the file to be downloaded. To do so, click the box to the left of the File Name. If you click the box to the left of the File Name column heading, all files are selected for download. This section displays the details of the saved CPU log files. Name of the saved CPU log file. If you click on the file name, a new screen opens and displays the contents of the log file. Date and time of the last modification to the CPU log file. Size of the CPU log file, in kilobytes. Use the Memory Log Files page to view and download the memory log files. Table B-14 describes the Memory Log Files page.
CPU Log Files
File Name Last Modified File Size (KB)
Table B-14
Memory Log Files Page
Description Download the selected log files. You must first select the file to be downloaded. To do so, click the box to the left of the File Name. If you click the box to the left of the File Name column heading, all files are selected for download. This section displays the details of the saved Memory log files. Name of the saved Memory log file. If you click on the file name, a new screen opens and displays the contents of the log file. Date and time of the last modification to the Memory log file. Size of the Memory log file, in kilobytes.
Related Topics
Memory Log Files
File Name Last Modified File Size (KB)
Using the CPU and Memory Usage Tool, page 6-7
Processes
The Processes page appears when you select System Monitor > Processes.

Description
Use the Processes page to view and download information on currently running processes.
Note
Use the up and down arrows next to each column heading on the Processes page to sort the information by each category. Table B-15 describes the Processes page.
B-13
Appendix B Processes
Table B-15
Processes Page
Field Disable Auto-Refresh Refresh Rate Download Log File Select Process PID %CPU Status Nice (Level) Vm RSS (KB) Vm Size (KB) Vm Data (KB) Thread Count Data Stack (KB) Page Fault Count
Description Click this check box to disable auto-refresh of the information displayed on this page. To specify in seconds how often this page should be refreshed, enter a number in the text box, then click the Set button to the right of the text box. Click on this link to download log files you have created. You cannot download log files until you have first created them. Check boxes that allow you to select files to be viewed or downloaded. Name of the process. ID number of the process. Percentage of processor time being used by the process. Task's process status: Running (R), Sleeping (S), Uninterruptible disk sleep (D), Zombie (Z), 4 Traced (T), Paging (P) Represents scheduling priority for the process. A nice value of 20 is the highest priority and 19 is the lowest priority. The default nice value for most processes is 0. Resident set currently in physical memory in Kilobytes (KB), including Code, Data and Stack. Size of virtual memory, in kilobytes. Amount of data currently stored in virtual memory, in kilobytes. Number of program threads currently running Size of the data stack, in kilobytes. Number of major page faults the task has made requiring loading of memory. Use the View Selected Processes page to view the selected processes and download the processes log files. Table B-16 describes the View Selected Processes page.
Table B-16 View Selected Processes Page
Field Disable Auto-Refresh Refresh Rate View All Processes button Start Log button
Description Click this check box to disable auto-refresh of the information displayed on this page. To specify in seconds how often this page should be refreshed, enter a number in the text box, then click the Set button to the right of the text box. Returns you to the previous Processes screen, which displays all running processes. Creates a log of the selected processes displayed on this page.
Download Log File link Download the selected processes log file.
Processes
This section displays the details of the selected processes. The details are the same as those listed in Table B-15.
B-14
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder Disk Usage
Related Topics
Using the Processes Tool, page 6-8
Disk Usage
The Disk Usage page appears when you select System Monitor > Disk Usage.

Description
Use the Disk Usage page to list the percentage of disk space used by the different partitions in the system.
Note
Use the up and down arrows next to each column heading on the Disk Usage page to sort the information by each category. Table B-17 describes the Disk Usage page.
Table B-17 Disk Usage Page
Field Disk Usage Details Partition Size Percentage Used Available Space Used Space
Related Topics
Description Name of the partition. Size of the partition. How much disk space is the partition using, as a percentage of total allocated disk space. How much disk space is currently available on the partition. How much disk space is the partition using.
Using the Disk Usage Tool, page 6-8
System Logs Menu

The System Logs menu contains three submenus under which all system logs are grouped. The three submenus are as follows:

System Logs > CER Logs System Logs > Platform Logs System Logs > DB Logs
You must have serviceability authority to access the System Logs pages.
B-15
Appendix B System Logs Menu
Note
Use the up and down arrows next to each column heading to sort the information by each category. Table B-18 describes the System Logs pages.
Table B-18
General Description of System Logs Pages
Description Download the selected log files. You must first select the file to be downloaded. To do so, click the box to the left of the File Name. If you click the box to the left of the File Name column heading, all files are selected for download.
Note
If you select multiple log files, the system will create a Zip file that contains the log files to be downloaded.
File Name
Name of the log file. If you click on the file name, the contents of the log file display on a new screen.
Note
After viewing the contents, click the Back button in your browser to return to the log file page. This button is only available when you have clicked on a file name and are viewing the contents of particular log file.
Reload Log File button
Reloads the log file currently being viewed, so that any updates can be seen.
Note
Last Modified File Size (KB)
Date the log file was last modified. Size of the log file, in kilobytes. Table B-19 lists and describes each log under the three System Logs submenus.
Table B-19
Descriptions of Individual System Log File Pages
Menu/Log File Page CER Logs > CER Admin CER Logs > CER Server CER Logs > CER Phone Tracking CER Logs > JTAPI CER Logs > Tomcat CER Logs > Event Viewer CER Logs > Audio Driver Platform Logs > CLI Platform Logs > CLM Platform Logs > DRS Platform Logs > Install/Upgrade Platform Logs > Remote Support Platform Logs > Syslog Platform Logs > Servm
Description View or download Cisco ER Admin logs View or download Cisco ER Server logs View or download Cisco ER Phone Tracking logs View or download JTAPI logs View or download Tomcat logs View or download Cisco ER Event logs View or download Cisco ER Audio Driver logs View or download CLI operations logs View or download CLM (Cluster Manager) logs View or download DRS (Disaster Recovery System) logs View or download Installation and Upgrade logs View or download Remote Account creation and operations logs View or download Syslog logs View or download Servm (Services Manager) logs
Platform Logs > Certificate Management/IPSec View or download Certificate Management and IPSec logs
B-16
OL-12376-01
Appendix B
Serviceability Web Interface For Cisco Emergency Responder System Logs Menu
Table B-19
Descriptions of Individual System Log File Pages (continued)
Menu/Log File Page DB Logs > Cerdbmon DB Logs > Install DB

Related Topics
Description View or download Cerdbmon logs View or download InstallDB Utility logs
Using Cisco Emergency Responder Logs, page 6-9
B-17
Appendix B System Logs Menu
B-18
OL-12376-01
A P P E N D I X
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder
These topics describe the Cisco Unified Operating System (OS) Administration web interface for Cisco Emergency Responder (Cisco ER).

ServerGroup, page C-1 Hardware Status, page C-2 Network Configuration, page C-3 Software Packages, page C-4 System Status, page C-4 Ethernet Configuration, page C-5 NTP Server List, page C-6 SMTP Settings, page C-7 Time Settings, page C-8 Version Settings, page C-8 Certificate List, page C-9 Certificate Monitor, page C-13 IPSec Policy List, page C-13 Software Installation/Upgrade, page C-15 Ping Configuration, page C-16 Remote Access Configuration, page C-17
ServerGroup
The ServerGroup page appears when you select Show > ServerGroup.
You must have platform administrator authority to access this page.

Description
Use the ServerGroup page to view information about the Cisco ER servers in the servergroup.
C-1
Appendix C Hardware Status
Table C-1 describes the ServerGroup page.

Table C-1 ServerGroup Page
Field Hostname IP Address Alias Type of Node

Related Topics
Description Displays the name of the host. Displays the IP address of the host. Displays the alias of the host Displays the node type of the host.
Viewing Hardware Status, page 7-2
Hardware Status
The Hardware Status page appears when you select Show > Hardware.

Description
Use the Hardware Status page to view information about the Cisco ER hardware. Table C-2 describes the Hardware Status page.
Table C-2 Hardware Status Page
Field Hardware Resources Platform Type Processor Speed CPU Type Memory Object ID OS Version RAID Details
Related Topics
Description Model identity of the platform server Speed of the processor Type of processor in the platform server Total amount of memory in Mbytes Object ID of the platform server Operating system version running on the platform server Detailed summary of the platform hardware
Viewing Hardware Status, page 7-2
C-2
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Network Configuration
Network Configuration
The Network Configuration page appears when you select Show > Network.

Description
Use the Network Configuration page to view information about the network settings.
Note
The network status information that displays depends on whether Network Fault Tolerance is enabled. When Network Fault Tolerance is enabled, Ethernet port 1 automatically takes over network communications if Ethernet port 0 fails. If Network Fault Tolerance is enabled, network status information displays for the network ports Ethernet 0, Ethernet 1, and Bond 0. If Network Fault Tolerance is not enabled, status information displays only for Ethernet 0. Table C-3 describes the Network Configuration page.
Table C-3 Network Configuration Page
Field Status DHCP Status IP Address IP Mask Link Detected Mode Queue Length MTU MAC Address RX Stats TX Stats Primary DNS Secondary DNS Domain Gateway
Related Topics
Description Indicates whether the port is Up or Down for Ethernet ports 0 and 1. Indicates whether DHCP is enabled for Ethernet port 0. Shows the IP address of Ethernet port 0 (and Ethernet port 1 if Network Fault Tolerance (NFT) is enabled). Shows the IP mask of Ethernet port 0 (and Ethernet port 1 if NFT is enabled). Indicates whether there is an active link. Indicates the speed (in MB/s), half/full duplex, and whether the network interface is auto-enabled. Displays the length of the queue. Displays the maximum transmission unit. Displays the hardware address of the port. Displays information on received bytes and packets. Displays information on transmitted bytes and packets. Displays the IP address of the primary domain name server. Displays the IP address of the secondary domain name server. Displays the domain of the server. Displays the IP address of the network gateway on Ethernet port 0.
Viewing Network Status, page 7-2
C-3
Appendix C Software Packages
Software Packages
The Software Packages page appears when you select Show > Software.

Description
Use the Software Packages page to view the software versions and installed software options. Table C-4 describes the Software Packages page.
Table C-4 Software Packages Page
Field Partition Versions
Description Displays the software version that is running on the active and inactive partitions.
Active Version Installed Displays the versions of installed software options that are installed on the Software Options active version. Inactive Version Installed Software Options
Related Topics
Displays the versions of installed software options that are installed on the inactive version.
Viewing Installed Software, page 7-2
System Status
The System Status page appears when you select Show > System.

Description
Use the System Status page to view the status of the Cisco ER system. Table C-5 describes the System Status page.
Table C-5 System Status Page
Field Host Name Date Time Zone Locale Product Ver
Description Name of the Cisco MCS host where the Cisco ER system is installed Date and time based on the continent and region that were specified during operating system installation Time zone that was chosen during installation Locale of the system Operating system version
C-4
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Ethernet Configuration
Table C-5
System Status Page (continued)
Field Platform Ver
Description Platform version

Related Topics
Viewing System Status, page 7-3
Ethernet Configuration
The Ethernet Configuration page appears when you select Settings > IP > Ethernet.

Description
Use the Ethernet Configuration page to view or change Ethernet settings.
Note
All Ethernet settings apply only to Eth0. You cannot configure any settings for Eth1. The Maximum Transmission Unit (MTU) on Eth0 defaults to 1500. Table C-6 describes the Ethernet Configuration page.
Table C-6
Ethernet Configuration Page
Field DHCP Information DHCP

Port Information
Description Indicates whether DHCP is enabled or disabled and allows you to change the DHCP setting using the pulldown menu. Shows the IP address of the system. You can change the IP address by entering a new IP address in the text box. Shows the IP subnet mask address. You can change the mask by entering a new subnet mask in the text box. Shows the IP address of the default network gateway. You can change the gateway IP address by entering a new IP address in the text box. Saves any changes made to the Ethernet Configuration page.
IP Address Subnet Mask

Gateway Information
Default Gateway Save button or icon
Caution
If you click Save, the machine will reboot. Do not click Save unless you want to shut down and reboot your system. To recognize any new IP addresses, both servers in the servergroup must be manually rebooted.
Note
C-5
Appendix C NTP Server List
Related Topics
Configuring Ethernet Settings, page 7-3
NTP Server List

The NTP Server List page appears when you select Settings > NTP Servers.

Description
Use the NTP Server List page to add, modify, or delete an NTP server. You can only configure the NTP server settings on the Publisher.
Note
Ensure that the external NTP server is stratum 9 or higher (1-9).
Note
Any change you make to the NTP servers can take up to five minutes to complete. Whenever you make any change to the NTP servers, you must refresh the page to display the correct status.
Caution
If you add, modify, or delete an NTP server, you must reboot both the Publisher and the Subscriber. Table C-7 describes the NTP Server List page.
Table C-7
NTP Server List Page
Field Status
NTP Server
Description Displays how many configured NTP server were found.
Hostname or IP Address Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or field IP address, click it, enter the new hostname or IP address, and click Save. Add New button or icon Adds a new NTP server. After you click Add New, enter the hostname of IP address of the new NTP server and click Save. Select All button or icon Selects all NTP servers listed. When you click this button or icon, a check mark appears in the boxes to the left of each NTP hostname or IP address and to the left of the Hostname or IP Address column heading.
Note
The Select All button or icon is only visible if you have previously configured one or more NTP servers. The Clear All button or icon is only visible if you have previously configured one or more NTP servers.
Clear All button or icon Deselects all NTP servers listed. When you click this button or icon, all check marks disappear.
Note
C-6
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder SMTP Settings
Table C-7
NTP Server List Page (continued)
Field Delete Selected button or icon
Description Deletes the selected NTP server. To delete an NTP server, you must first select it from the list of NTP servers. Click in the box to the left of the NTP server name to select it. To select all listed NTP servers, click the box to the left of the Hostname or IP Address column heading or click Select All.
Note
The Delete Selected button or icon is only visible if you have previously configured one or more NTP servers.
Table C-8 describes the NTP Server Configuration page.

Table C-8 NTP Server Configuration Page
Field Status
NTP Server Settings
Description Displays how many configured NTP server were found.
Hostname or IP Address Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or field IP address, click it, enter the new hostname or IP address, and click Save. Save button or icon Saves the information about the new NTP server.
Related Topics
Configuring NTP Servers, page 7-4
SMTP Settings
The SMTP Settings page appears when you select Settings > SMTP.

Description
Use the SMTP Settings page to manually configure the SMTP host. Table C-9 describes the SMTP Settings page.
Table C-9 SMTP Settings Page
Field Status
SMTP Host
Description Displays the status of the SMTP Settings page.
Hostname or IP Address Enter the hostname or IP address of the SMTP server in the text box. Host Status Save button or icon Displays the status of the SMTP host server. Saves changes made to the SMTP Settings page.
C-7
Appendix C Time Settings
Related Topics
Configuring the SNMP Connection, page 5-39
Time Settings
The Time Settings page appears when you select Settings > Time.

Description
Use the Time Settings page to manually configure the server time.
Note
Before you can manually configure the server time, you must delete any NTP servers that you have configured. See the NTP Server List section on page C-6 for more information.
Caution
If you change the server time, you must reboot both the Publisher and the Subscriber. Table C-10 describes the Time Settings page.
Table C-10 Time Settings Page
Field Date Save button or icon

Related Topics

Description Allows you to set the month, day, year, hours, minutes, and seconds using the pulldown menus. Saves changes made to the Time Settings page.
NTP Server List, page C-6 Configuring NTP Servers, page 7-4 Configuring Time Settings, page 7-5
Version Settings
The Version Settings page appears when you select Settings > Version.

Description
Use the Version Settings page to restart or shutdown the system and to switch software versions.
C-8
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Certificate List
Note
You must have a different software version installed on the inactive partition in order to switch versions.
Caution
Initiating this action causes the system to restart and become temporarily unavailable. Table C-11 describes the Version Settings page.
Table C-11 Version Settings Page
Field Status
Installed Versions
Description Displays the current status. Displays the version running on the active partition. Display the version on the inactive partition. Restarts the system. Shuts down the system. Actives the software version on the inactive partition.
Note
Active Version Inactive Version Restart button or icon Shutdown button or icon Switch Versions button or icon
The Switch Versions button or icon is only visible if there is a software version installed on the inactive partition.
Related Topics
Restarting, Shutting Down, or Switching Software Versions, page 7-5
Certificate List
The Certificate List page appears when you select Security > Certificate Management.

Description
Use the Certificate List page to do the following:

Search for existing certificates Generate a new certificates Upload a certificate Upload a CTL Generate a CSR
Table C-12 describes the Certificate List page.
C-9
Appendix C Certificate List
Table C-12
Certificate List Page
Field Status
Certificate List
Description Displays the current status. Enter search criteria for the certificate lists you want to find. To find all certificate lists by file name, select File Name from the pulldown menu and click Find without entering any criteria. To find all certificate lists by certificate name, select Certificate Name from the pulldown menu and click Find without entering any criteria. To narrow your search:

Find certificate list where
Select the search relationship (begins with, contains, and so on) from the pulldown menu, and enter the search string in the text box. To search on a combination of fields, click the Plus icon (+) to add additional search parameters. Click the Minus icon () to remove search parameters. Click Clear Filter to remove all additional search parameters. Use the Rows per Page pulldown menu to select how many rows are displayed per page.
When you have entered all of the search parameters, click Find. If the search finds existing certificates, the information about the certificates (File Name, Certificate Name, and Certificate Type) displays in the Certificate List. Click the File Name link to display the Certificate Configuration page. See Table C-18 for information about the Certificate Configuration Page. Generate New button or Allows you to generate a new certificate. When you click Generate New, the icon Generate Certificate page appears. See Table C-13 for a description of the Generate Certificate page. Upload Certificate button or icon Upload CTL button or icon Allows you to upload a certificate from a remote server. When you click Upload Certificate, the Upload Certificate page appears. See Table C-14 for a description of the Upload Certificate page. Allows you to upload a Certificate Trust List (CTL) from a remote server. When you click Upload CTL, the Upload Certificate Trust List page appears. See Table C-15 for a description of the Upload Certificate Trust List page.
Generate CSR button or Allows you to generate a new Certificate Signing Request (CSR). When you icon click Generate CSR, the Generate Certificate Signing Request page appears. See Table C-16 for a description of the Generate New page. Download CSR button or icon Allows you to download a CSR. When you click Download CSR, the Download Certificate Signing Request page appears. See Table C-17 for a description of the Download Certificate Signing Request page.
Table C-13 describes the Generate Certificate page.
C-10
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Certificate List
Table C-13
Generate Certificate Page
Field Status
Generate Certificate
Description Displays the current status of the Generate Certificate page. Allows you to choose a certificate name from the pulldown menu.
Certificate Name
Generate New button or Generates a new certificate. You must first select a Certificate Name from the icon pulldown menu. Close button or icon Closes the Generate Certificate page.
Table C-14 describes the Upload Certificate page.

Table C-14 Upload Certificate Page
Field Status
Upload Certificate
Description Displays the current status of the Upload Certificate page. Use the pulldown menu to select the name of the certificate to upload. Enter the name of the root certificate. Use the Browse button to select the file to be uploaded. Uploads the certificate file specified in the Upload Certificate section. Closes the Update Certificate page.
Certificate Name Root Certificate Upload File Upload File button or icon Close button or icon
Table C-15 describes the Upload CTL page.

Table C-15 Upload CTL Page
Field Status
Upload Certificate
Description Displays the current status of the Upload CTL page. Use the pulldown menu to select the name of the CTL file to upload. Enter the name of the root certificate. Use the Browse button to select the file to be uploaded. Uploads the certificate file specified in the Upload Certificate Trust List section. Closes the Update CTL page.
Certificate Name Root Certificate Upload File Upload File button or icon Close button or icon
Table C-16 describes the Generate CSR page.
C-11
Appendix C Certificate List
Table C-16
Generate CSR Page
Field Status
Generate Certificate Signing Request
Description Displays the current status of the Generate CSR page.
Certificate Name
Use the pulldown menu to select the name of the CTL file to generate.
Generate CSR button or Generates a new CSR. icon Close button or icon Close the Generate CSR page.
Table C-17 describes the Download CSR page.

Table C-17 Download CSR Page
Field Status
Download Certificate Signing Request
Description Displays the current status of the Download CSR page.
Certificate Name Download CSR button or icon Close button or icon
Use the pulldown menu to select the name of the CTL file to download. Downloads the CSR specified in the Download Certificate Signing Request section. Closes the Download CSR page.
Table C-18 describes the Certificate Configuration page.

Table C-18 Certificate Configuration Page
Field Status Certificate Settings
Description Displays the current status of the Certificate Configuration page. Displays the following information about the certificate:

File Name Certificate Name Certificate Type Certificate Group
Certificate File Data Regenerate button or icon Download button or icon
Displays the contents of the certificate file. Regenerates the current certificate. Downloads the certificate to your local system.
Generate CSR button or Generates a Certificate Trust Request (CSR). icon
C-12
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Certificate Monitor
Related Links
Managing Certificates and Certificate Trust Lists, page 7-7
Certificate Monitor
The Certificate Monitor page appears when you select Security > Certificate Monitor.

Description
Use the Certificate Monitor page to do the following:

Specify the start time Specify the frequency Enable email notification and provide email addresses of those to be notified
Table C-19 describes the Certificate Monitor page.

Table C-19 Certificate Monitor Page
Field Status
Certificate Monitor Configuration
Description Displays the current status of the Certificate Monitor page.
Notification Start Time Notification Frequency Enable Email Notification Email IDs Save button or icon
Related Topics
Enter the number of days before the certificate expires that you want to be notified. Enter the notification frequency and click one of the radio buttons to indicate days or hours. Check the box the enable email notification.
Note
For the system to send notifications, you must configure an SMTP host.
Enter the email addresses of those to be notified in the text box. Saves the information entered on the Certificate Monitor page.
Managing Certificates and Certificate Trust Lists, page 7-7
IPSec Policy List

The IPSec Policy List page appears when you select Security > IPSec Configuration.
C-13
Appendix C IPSec Policy List
Description
Use the IPSec Policy List page to display existing IPSec policies, add an additional IPSec policy, or modify an existing IPSec policy. Table C-20 describes the IPSec Policy List page.
Table C-20 IPSec Policy List Page
Field Status
IPSec Policy List
Description Displays the current status of the IPSec Policy List page. Displays the currently configured IPSec policies. Click on the Policy Name link to IPSec Policy Configuration page for that policy.
Add New button or icon Adds a new IPSec policy. When you click Add New, the IPSec Policy Configuration page appears. See Table C-21 for information about the IPSec Policy Configuration page. Table C-21 describes the IPSec Policy Configuration page.
Table C-21 IPSec Policy Configuration Page
Field Status
IPSec Policy Details
Description Displays the current status of the IPSec Policy Configuration page. Specifies the name of the IPSec policy. Specifies the association name that is given to each IPSec association. Specifies the authentication method. Specifies the preshared key if you selected Pre-shared Key in the Authentication Name field. Specifies whether the peer is the same type or different. Specifies the IP address or FQDN of the destination. Specifies the port number at the destination. Specifies the IP address or FQDN of the source. Specifies the port number at the source. Specifies Tunnel or Transport mode Specifies the port number to use at the destination. Specifies the specific protocol, or Any:

Policy Name Association Name Authentication Method Preshared Key Peer Type Destination Address Destination Port Source Address Source Port Mode Remote Port Protocol
TCP UDP Any DES 3DES
Encryption Algorithm
From the drop-down list, choose the encryption algorithm. Choices include:

C-14
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Software Installation/Upgrade
Table C-21
IPSec Policy Configuration Page (continued)
Field Hash Algorithm
Description Specifies the hash algorithm:

SHA1Hash algorithm that is used in phase 1 IKE negotiation MD5Hash algorithm that is used in phase 1 IKE negotiation NULL_ENC DES 3DES BLOWFISH RIJNDAEL
ESP Algorithm
From the drop-down list, choose the ESP algorithm. Choices include:

Phase 1 DH Group
Phase One Life Time Phase One DH

Phase 1 DH Group
Specifies the lifetime for phase One, IKE negotiation, in seconds. From the drop-down list, choose the phase One DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18. Specifies the lifetime for phase Two, IKE negotiation, in seconds. From the drop-down list, choose the phase Two DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18.
Phase Two Life Time Phase Two DH

IPSec Policy Configuration
Enable Policy Save button or icon

Related Topics
Select the check box to enable the policy. Saves the changes made to the IPSec Policy List page.
Managing IPSec, page 7-12
Software Installation/Upgrade
The Software Installation/Upgrade page appears when you select Software Upgrades > Install/Upgrade.

Description
Use the Software Installation/Upgrade page to install or upgrade software from a DVD/CD or from a filesystem on a remote server. Table C-22 describes the Software Installation/Upgrade page.
C-15
Appendix C Ping Configuration
Table C-22
Software Installation/Upgrade Page
Field Status
Software Location
Description Displays the current status of the Software Installation/Upgrade page. Pulldown menu used to specify the source for the installation/upgrade. Options are DVD/CD or Remote Filesystem. The name of the directory containing the files.
Note
Source Directory
If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path you want to specify. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your system administrator for the correct directory path.
Server User Name User Password Transfer Protocol
The hostname or IP address of the remote server from which the software will be downloaded. The name of a user who is configured on the remote server. Password that is configured for this user on the remote server. Pulldown menu used to specify which transfer protocol to use. Options are ftp or sftp.
Note
These options are available only if you selected Remote Filesystem from the Source pulldown menu. If you selected DVD/CD, this pulldown menu is grayed out.
Cancel Install button or Cancels the installation/upgrade procedure. icon Next button or icon Continues with the installation/upgrade procedure.
Related Topics
Upgrading and Installing Software, page 7-13
Ping Configuration
The Ping Configuration page appears when you select Services > Ping.

Description
Use the Ping Configuration page to send ping requests to test if other systems are reachable over the network. Table C-23 describes the Ping Configuration page.
Table C-23 Ping Configuration Page
Field Status
Ping Settings
Description Displays the current status of the Ping Configuration page.
C-16
OL-12376-01
Appendix C
Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder Remote Access Configuration
Table C-23
Ping Configuration Page (continued)
Field
Description
Hostname or IP Address Text box into which you enter the IP address or network name for the system that you want to ping. Ping Interval Packet Size Ping iterations Text box in which you enter the amount of time between ping requests, in seconds. Text box into which you enter the packet size of the ping request. Pulldown menu that allows you to choose the number of times you want to send ping requests to the other system. Available options are 1, 5, 25, or 100 times
Note
When you specify multiple pings, the ping command does not display the ping date and time in real time. Be aware that the ping command displays the data after the number of pings that you specified are complete.
Validate IPSec Ping Results Ping button or icon

Related Topics
Select the check box to have the system validate IPSec. Text box in which the ping results are displayed. Sends the ping request.
Using the Ping Utility, page 7-16
Remote Access Configuration

The Remote Access Configuration page appears when you select Services > Remote Support.

Description
Use the Remote Access Configuration page to set up a remote account that Cisco support personnel can use to access the system for a specified period of time. Once the account duration limit expires, Cisco support will no longer be able to access the remote support account. When you establish a remote account, the system generates a pass phrase. Follow this procedure to complete the remote account setup:
Call Cisco support and provide them with the remote support account name and pass phrase. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase. Cisco support logs into the remote support account on the customer system by using the decoded password.
If you have not already created a remote account, when you navigate to the Remote Access Configuration page you will have the option of creating a new account.
C-17
Appendix C Remote Access Configuration
Table C-24 describes the Remote Access Configuration page.

Table C-24 Remote Access Configuration Page
Field Status
Remote Access Account Information
Description Displays the current status of the Remote Access Configuration page.
Account Name Account Duration Save button or icon
Name for the new remote account. Account names must be at least six-characters long and consist of all lowercase, alphabetic characters The amount of time that the remote account will exist, in days. Creates a new remote account. You must provide the Account Name and Account Duration before you click Add. Remote Access Configuration page redisplays. See Table C-25 for a description of the fields on the Remote Access Configuration page. Deletes the currently configured remote account.
Note
Delete button or icon
The Delete button or icon is only visible if there is an existing remote account.
If you have already created a remote account, when you navigate to the Remote Access Configuration page you view and delete the remote account. Table C-25 describes the Remote Access Configuration page.
Table C-25 Remote Access Configuration Page
Field Remote Access Account Information Account Name Expiration Passphrase Decode Version Delete button or icon
Related Topics
Description
Displays the name of the remote support account. Displays the date and time when access to the remote account expires. Displays the generated pass phrase. Indicates the version of the decoder in use. Deletes the remote access account information.
Setting Up Remote Support, page 7-17
C-18
OL-12376-01
A P P E N D I X
Disaster Recovery System Web Interface For Cisco Emergency Responder

These topics describe the fields on the pages of the Cisco Emergency Responder (Cisco ER) Disaster Recovery System Administration web interface.

Backup Device List, page D-1 Schedule List, page D-2 Manual Backup, page D-4 Backup History and Restore History, page D-5 Backup Status, page D-6 Restore Wizard, page D-7 Restore Status, page D-8
Backup Device List

The Backup Device List page appears when you select Backup > Backup Device.

Description
Use the Backup Device List page to list, add, and delete backup devices. Table D-1 describes the Backup Device List page.
Table D-1 Backup Device List Page
Field Backup Device List
Description Lists the configured backup devices and displays the Device Name, Device Type, and Device Path. Click on the Device Name link to bring up the Backup Device page for that device. Adds a new backup device. When you click the Add icon, the Backup Device page appears. See Table D-2 for information on the Backup Device page.
Add New button
D-1
Appendix D Schedule List
Table D-1
Backup Device List Page (continued)
Field Select All button and icon Clear All button and icon Delete Selected button and icon
Description Selects all the listed backup devices. Deselects all selected backup devices. Deletes the selected backup device(s).
Table D-2 describes the Backup Device page, which you use to add new backup devices.
Table D-2 Backup Device Page
Field Backup device name

Select Destination
Description Enter the device name in the text box (required). To select the backup destination, click the Tape Device or Network Directory radio button (required). Select the name of the tape device from the pulldown menu. In the fields provided, enter the Server name, Path name, User name, and Password for the Network Directory. Select the number of backups using the pulldown menu.
Tape Device Network Directory Number of backups to store on the Network Directory Save button and icon Back button and icon
Related Topics
Saves the information on the new backup device. Returns to the Backup Device List page.
Adding Backup Devices, page 8-5
Schedule List
The Schedule List page appears when you select Backup > Scheduler.

Description
Use the Schedule List page to list currently scheduled backups, to add new schedules, to enable schedules, and to disable schedules. You can schedule a backup to start at a specified date and time and configure it either to run once or at a specified frequency, as well as specifying the features to be backed up. Table D-3 describes the Schedule List page.
D-2
OL-12376-01
Appendix D
Disaster Recovery System Web Interface For Cisco Emergency Responder Schedule List
Table D-3
Schedule List Page
Field Schedule List
Description Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click on the Schedule List name link to view the details of that schedule.
Note
After you have created a scheduled backup, you must enable the schedule. To do so, select the schedule in the Schedule List and click the Enable Selected Schedules button or icon.
Add New button or icon Adds a new schedule. When you click the Add button or icon, the Scheduler page appears. See Table D-2 for information on the Scheduler page. Select All button or icon Selects all the listed schedules.
Note
The Select All button only appears if no schedules have been configured. The Clear All button only appears if no schedules have been configured. The Delete Selected button only appears if no schedules have been configured. The Enable Selected Schedules icon only appears if no schedules have been configured.
Clear All button or icon Deselects all selected schedules.

Note
Delete Selected button or icon Enable Selected Schedules button or icon Disable Selected Schedules button or icon
Deletes the selected schedules.

Note
Enables the selected schedules.

Note
Disables the selected schedules.

Note
The Disable Selected Schedules button only appears if no schedules have been configured.
Table D-4 describes the Scheduler page.

Table D-4 Scheduler Page
Field Status
Schedule Name Select Backup Device Select Features Start Backup at
Description Displays the status of the Scheduler page. Enter the name of the schedule in the text box. Select the name of the backup device from the pulldown menu. Select CER as the feature to be backed up. From the pulldown menus, enter the year, month, and day on which the backup will start. From the pulldown menus, enter the hour and minute at which the backup will start. Click this radio button to schedule a single backup. Click this radio button to schedule a daily backup. Click this radio button to schedule a weekly backup. Click in the check boxes to specify the days on which the weekly backup will be scheduled. Click this radio button to schedule a monthly backup. Saves the backup schedule information.
Date Time Frequency Once Daily Weekly Monthly Save button or icon
D-3
Appendix D Manual Backup
Table D-4
Scheduler Page (continued)
Field Set Default button or icon
Description Saves the information entered as the default for scheduled backups.
Disable Schedule button Disables the Schedule. If the Schedule is currently disabled, this button will be grayed out. or icon Enable Schedule button Enables the Schedule. If the Schedule is currently enabled, this button will be grayed out. or icon Back button or icon Returns to the Scheduler List page.
Related Topics

Backup History and Restore History, page D-5 Backup Status, page D-6 Creating and Editing Backup Schedules, page 8-6 Enabling, Disabling, and Deleting Schedules, page 8-7
Manual Backup
The Manual Backup page appears when you select Backup > Manual Backup.

Description
Use the Manual Backup page to start a manual backup.
Note
Before starting a manual backup, make sure that all servers in the clusters are running and are reachable over the network. Servers that are not running or are not reachable over the network will not be backed up.
Table D-5 describes the Manual Backup page.

Table D-5 Manual Backup Page
Field Select Backup Device

Select Features
Description Select the name of the backup device from the pulldown menu. Check CER as the feature to be backed up. Starts a manual backup.
Start Backup button or icon
Select All button or icon Selects all the listed features. Clear All button or icon Deselects all selected features.
D-4
OL-12376-01
Appendix D
Disaster Recovery System Web Interface For Cisco Emergency Responder Backup History and Restore History
Related Topics

Schedule List, page D-2 Starting a Manual Backup, page 8-7
Backup History and Restore History

The Backup History page appears when you select Backup > History. The Restore History page appears when you select Restore > History.

Description
Use the Backup History page to view information on past backups. Use the Restore History page to view information on past restore operations. Table D-6 describes the Backup History page.
Table D-6 Backup History Page
Field Backup History information
Description The following information about past backups is displayed:

Tar Filename Backup Device Completed On Result Features Backed Up
Refresh button or icon
Refreshes the information in the Backup History page.
Table D-7 describes the Restore History page.

Table D-7 Restore History Page
Field Restore History information
Description The following information about past backups is displayed:

Tar Filename Backup Device Completed On Result Features Restored
Refreshes the information in the Restore History page.
D-5
Appendix D Backup Status
Related Topics

Schedule List, page D-2 Manual Backup, page D-4 Backup Status, page D-6 Restore Wizard, page D-7 Restore Status, page D-8 Viewing the Backup and Restore History, page 8-11
Backup Status
The Backup Status page appears when you select Backup > Current Status.

Description
Use the Backup Status page to view status information about the current backup. Table D-8 describes the Backup Status page.
Table D-8 Backup Status Page
Field Status Backup Details
Description Provides information on the status of the current backup. The following information about the current backup is displayed:

Tar Filename Backup Device Operation Percentage Complete Feature Server Component Status Result1 Start Time Log File2
Refresh button or icon Cancel Backup button or icon
Refreshes the information about the current backup. Cancels the current backup.
1. Result column indicates results of staging of individual components. Status section indicates the entire Backup Status 2. Click on the filename to view the log file
D-6
OL-12376-01
Appendix D
Disaster Recovery System Web Interface For Cisco Emergency Responder Restore Wizard
Related Topics

Schedule List, page D-2 Checking Backup Status, page 8-7
Restore Wizard
The Restore Wizard page appears when you select Restore > Restore Wizard.

Description
Use the Restore Wizard page to restore a backup file to a server or to restore all servers in a cluster. The Restore Wizard consists of four web pages. Use the Step1 RestoreChoose Backup Device page to select the backup device to be used for the backup. Table D-9 describes the Step1 RestoreChoose Backup Device page.
Table D-9 Step1 RestoreChoose Backup Device Page
Field Status Select Backup Device Next button or icon Cancel button or icon
Description Indicates the current status of the recovery operation. Select the backup device using the pulldown menu. Advances to the next page in the Restore Wizard. Cancels the restore operation.
Use the Step2 RestoreChoose the Backup Tar File page to select the backup tar file to be restored. Table D-10 describes the Step2 RestoreChoose the Backup Tar File page.
Table D-10 Step2 RestoreChoose the Backup Tar File Page
Field Status Select Backup File Back button or icon Next button or icon Cancel button or icon
Description Indicates the current status of the restore operation. Use the pulldown menu to select the tar file for backup Returns to the previous page in the Restore Wizard. Advances to the next page in the Restore Wizard. Cancels the restore operation.
Use the Step3 RestoreSelect the Type of Restore page to select the features to be restored. Table D-11 describes the Step3 RestoreSelect the Type of Restore page.
D-7
Appendix D Restore Status
Table D-11
Step3 RestoreSelect the Type of Restore Page
Field Status
Select Features
Description Indicates the current status of the restore operation. Click in the box to the left of the CER feature name to select the CER feature for backup. Returns to the previous page in the Restore Wizard. Advances to the next page in the Restore Wizard. Cancels the restore operation.
Back button or icon Next button or icon Cancel button or icon
Use the Step4 RestoreFinal Warning for Restore page to select the server(s) to be restored. Table D-12 describes the Step4 RestoreFinal Warning for Restore page.
Table D-12 Step4 RestoreFinal Warning for Restore Page
Field Status
Warning Select the Servers to be restored for each Feature
Description Indicates the current status of the restore operation. Displays a warning message stating that the restore operation will overwrite all existing data on the selected server(s). Under the CER feature name, select the servers to be restored. To do so, click in the check box to the left of the server name. Returns to the previous page in the Restore Wizard. Initiates the restore operation. Before you click Restore, you must first select the server to be restored. You can select a Publisher or a Subscriber to be restored, but not both.
Back button or icon Restore button or icon
Caution
The restore operation will overwrite any existing data on the selected server(s).
Cancel button or icon

Related Topics

Cancels the restore operation.
Backup History and Restore History, page D-5 Restore Status, page D-8 Restoring a Backup, page 8-8 Restoring a Cluster, page 8-9
Restore Status
The Restore Status page appears when you select Restore > Status.
D-8
OL-12376-01
Appendix D
Disaster Recovery System Web Interface For Cisco Emergency Responder Restore Status
Description
Use the Restore Status page to view the status of restore operations. Table D-13 describes the Restore Status page.
Table D-13 Restore Status Page
Field Status
Restore Details
Description Provides information on the status of the current restore operation. The following information about the current restore operation is displayed:

Tar Filename Backup Device Operation Percentage Complete Feature Server Component Status Result1 Start Time Log File2
Refreshes the information about the current restore operation.
1. Result column indicates results of staging of individual components. Status section indicates the entire Restore Status. 2. Click on the filename to view the log file
Related Topics

Restore Wizard, page D-7 Backup History and Restore History, page D-5 Viewing the Restore Status, page 8-11 Viewing the Backup and Restore History, page 8-11
D-9
Appendix D Restore Status
D-10
OL-12376-01
A P P E N D I X
Admin Utility Web Interface For Cisco Emergency Responder

These topics describe the fields on the pages of the Cisco Emergency Responder (Cisco ER) Admin Utility web interface.

Point to a New Publisher, page E-1 Update CCM Version, page E-2 Update Cluster DB Host, page E-3
Point to a New Publisher

The Point to a New Publisher page appears when you select Update > Publisher.

Description
Use the Point to a New Publisher page to point the subscriber to a different publisher.
Caution
Choosing to change the publisher will delete all the current associations with the existing publisher. Table E-1 describes the Point to a New Publisher page.
Table E-1 Point to a New Publisher Page
Field Status
Publisher Details
Description Displays the current Publisher host Name of the new Publisher host IP address of the new Publisher host Password used to gain access to the Publisher host
HostName IP Address Security Password
E-1
Appendix E Update CCM Version
Table E-1
Point to a New Publisher Page (continued)
Field Go button
Description Click Go to change the Publisher host
Caution
Change the publisher deletes all the current associations with the existing publisher.
Cancel button
Related Topics

Cancels the Point to a New Publisher operation.
Before You Install or Upgrade, page 2-1 Pointing Subscriber Servers to a Different Publisher, page 9-1
Update CCM Version

The Update CCM Version page appears when you select Update > CCM.

Description
Use the Upgrade CCM Version page to upgrade to a different version of Cisco Unified Communications Manager. Table E-2 describes the Upgrade CCM Version page.
Table E-2 Upgrade CCM Version Page
Field Status
CCM Version Details
Description Displays the current Cisco Unified Communications Manager version. Use the pulldown menu to select the Cisco Unified Communications Manager version to which you want to upgrade Click Go to initiate the upgrade process.
Note
Choose the Cisco Unified Communications Manager Version to Upgrade Go button
Change the CCM version separately on the Publisher and Subscriber nodes.
Cancel button
Cancels the Cisco Unified Communications Manager upgrade.
Related Topics
Changing the Cisco Unified Communications Manager Version, page 9-2
E-2
OL-12376-01
Appendix E
Admin Utility Web Interface For Cisco Emergency Responder Update Cluster DB Host
Update Cluster DB Host

The Update Cluster DB Host page appears when you select Update > Cluster DB Host.

Description
Use the Update Cluster DB Host page to designate a new server as the Cisco ER clusters database host server. Table E-3 describes the Update Cluster DB Host page.
Table E-3 Update Cluster DB Host Page
Field Status
Cluster DB Host Details
Description Displays the name of the current cluster database host
ClusterDB Hostname/IP Enter the hostname (if DNS is configured) or the IP address of the new Address cluster database host.
Note
If the cluster is spread across domains, then enter a fully qualified hostname.
Password Confirm Password Go button
Enter the password for the new cluster database host Re-enter the password for the new cluster database host. Click the Go button to designate the new server as the new cluster database host.
Note
The Cisco ER Cluster DB host details will be updated. Cisco ER services will have to be restarted for this change to take effect.This will update Cisco ER Cluster DB host details for this server group only. Other servers in this Cisco ER cluster will NOT be updated automatically. For further details, see the Updating the Cisco ER Cluster Database Host Details section on page 9-3.
Cancel button
Related Topics

Cancels the Update Cluster DB Host operation.
Configuring the Cisco Emergency Responder Cluster and Cluster DB Host, page 5-23 Updating the Cisco ER Cluster Database Host Details, page 9-3
E-3
Appendix E Update Cluster DB Host
E-4
OL-12376-01
A P P E N D I X

This appendix describes Cisco Unified Operating System (OS) commands that you can use on the Cisco ER platform to perform basic operating system functions. The Cisco Unified OS Administration web interface also makes these functions available. Typically, you would use the command-line interface (CLI) only when a problem occurs while you are using the Cisco Unified OS Administration web interface. These topics describe how to use the CLI:

Starting a CLI Session, page F-1 CLI Basics, page F-2 Cisco Unified OS CLI Commands, page F-4
Starting a CLI Session

You can access the CLI remotely or locally using the following methods:

You can access the CLI remotely from a web client workstation, such as the workstation that you use for Cisco ER administration, by using SSH Secure Shell to connect securely to the Cisco ER. You can access the CLI locally by using the monitor and keyboard that you used during installation or by using a terminal server that is connected to the serial port. Use this method if a problem exists with the IP address.
Before You Begin
Ensure you have the following information, which is defined during installation:

A primary IP address and hostname An administrator ID An administrator password
You will need this information to log in to the Cisco ER platform.
F-1
Appendix F CLI Basics
To start a CLI session, follow these steps:

Procedure
Step 1
Depending on your method of access, do one of the following actions:
From a remote system, use SSH Secure Shell to connect securely to the Cisco ER platform. In your SSH client, enter ssh adminname@hostname where adminname specifies the Administrator ID and hostname specifies the hostname that was defined during installation. For example, ssh admin@cer-1. From a direct connection, you receive this prompt automatically:
cer-1 login:
where cer-1 represents the host name of the system. Enter the administrator ID that was defined during installation. In either case, the system prompts you for a password.
Step 2
Enter the password that was defined at installation. The CLI prompt appears. The prompt represents the Administrator ID; for example:
admin:
You can now use any CLI command.
CLI Basics
The following topics describe how to perform basic functions using the command line interface.

Completing Commands, page F-2 Getting Help on Commands, page F-3 Ending a CLI Session, page F-4
Completing Commands
To complete commands, use Tab:

Enter the start of a command and press Tab to complete the command. For example, if you enter se and press Tab, se is expanded to the set command. Enter a full command name and press Tab to display all the commands or subcommands that are available. For example, if you enter set and press Tab, you see all the set subcommands. An asterisk (*) identifies the commands that have subcommands. If you reach a command, keep pressing Tab, and the current command line repeats; this indicates that no additional expansion is available.
F-2
OL-12376-01
Appendix F
Command Line Interface CLI Basics
Getting Help on Commands

You can get two kinds of help on any command:

Detailed help that includes a definition of the command and an example of its use Short query help that includes only command syntax
To get help on commands, follow these steps:

Procedure
Step 1
To get detailed help, at the CLI prompt, enter help command where command specifies the command name or the command and parameter. See Example F-1.
Step 2
To query only command syntax, at the CLI prompt, enter command? where command represents the command name or the command and parameter. See Example F-2.
Note
If you enter a question mark (?) after a menu command, such as set, it functions like the Tab key and lists the commands that are available.
Example F-1
Detailed Help Example:
admin:help file list activelog activelog help: This will list active logging files options are: page - pause output detail - show detailed listing reverse - reverse sort order date - sort by date size - sort by size file-spec can contain '*' as wildcards Example: admin:file list activelog platform detail 02 Dec,2004 12:00:59 <dir> drf 02 Dec,2004 12:00:59 <dir> log 16 Nov,2004 21:45:43 8,557 enGui.log 27 Oct,2004 11:54:33 47,916 startup.log dir count = 2, file count = 2
Example F-2
Query Example:
admin:file list activelog? Syntax: file list activelog file-spec [options] file-spec mandatory file to view options optional page|detail|reverse|[date|size]
F-3
Appendix F Cisco Unified OS CLI Commands
Ending a CLI Session

To end a CLI session, enter quit at the CLI prompt. If you are logged in remotely, you are logged off and the ssh session is dropped. If you are logged in locally, you are logged off and the login prompt returns.
Cisco Unified OS CLI Commands

The following sections list and describe the CLI commands that are available for the Cisco Unified OS running on the Cisco ER platform.
Note
The File I/O Reporting Service (FIOR) provides a kernel-based daemon for collecting file I/O per process. It must be enabled from the CLI; it is disabled by default.
delete account
This command allows you to delete an administrator account.
Command Syntax
delete account account-name

Parameters
account-name represents the name of an administrator account.
Requirements
Command privilege level: 4 Allowed during upgrade: No
delete dns
This command allows you to delete the IP address for a DNS server.
Command Syntax
delete dns ip-address

Parameters
ip-address represents the IP address of the DNS server you want to delete.
Usage Guidelines
The system asks whether you want to continue to execute this command.
Caution
If you continue, this command causes a temporary loss of network connectivity.
F-4
OL-12376-01
Appendix F
Command Line Interface Cisco Unified OS CLI Commands
Requirements
delete ipsec
This command allows you to delete IPSec policies and associations.
Command Syntax
delete ipsec policy {ALL | policy-name} association policy-name {ALL | association-name}

Parameters

policy-name represents an IPSec policy. association-name represents an IPSec association.
Requirements
delete process
This command allows you to delete a particular process.
Command Syntax
delete process process-id [force | terminate | crash]

Parameters
process-id represents the process ID number.
Options

forceTells the process to stop terminateTells the operating system to terminate the process crashCrashes the process and produces a crash dump
Usage Guidelines
Note
Use the force option only if the command alone does not delete the process and use the terminate option only if force does not delete the process.
Requirements
Command privilege level: 1 Allowed during upgrade: Yes
F-5
delete smtp
This command allows you to delete the SMTP host.
Command Syntax
delete smtp
Requirements
Command privilege level: 1 Allowed during
file check
This command checks the /usr directory tree to see whether any files or directories have been added, removed, or changed in size since the last fresh installation or upgrade and displays the results.
Command Syntax
file check [detection-size-kb]

Options
detection-size-kb specifies the minimum file size change that is required for the command to display the file as changed.
Usage Guidelines
The command notifies you about a possible impact to system performance and asks you whether you want to continue.
Caution
Because running this command can affect system performance, Cisco recommends that you run the command during off-peak hours. The display includes both deleted and new files.
Defaults
The default value of detection-size-kb is 100 KB.

Requirements
file delete
This command deletes one or more files.
Command Syntax
file delete
F-6
OL-12376-01
Appendix F
activelog directory/filename [detail] [noconfirm] inactivelog directory/filename [detail] [noconfirm] install directory/filename [detail] [noconfirm]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. directory/filename specifies the path and filename of the file(s) to delete. You can use the wildcard character (*) for filename.
Options

detailDisplays a listing of deleted files with the date and time. noconfirmDeletes files without asking you to confirm each deletion.
Usage Guidelines
Caution
You cannot recover a deleted file except, possibly, by using the Disaster Recovery System. If you delete a TFTP data file on the inactive side, you may need to manually restore that file if you switch versions to the inactive side.
Requirements

Example
The following example deletes the install log.

file delete install install.log
file dump
This command dumps the contents of a file to the screen, a page at a time.
Command Syntax
file dump activelog directory/filename [detail] [hex] inactivelog directory/filename [detail] [hex] install directory/filename [detail] [hex] sftpdetails directory/filename [detail] [hex]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side.
F-7
install specifies an installation log. sftp specifies an SFTP file. directory/filename specifies the path and filename of the file to dump. You can use the wildcard character (*) for filename as long as it resolves to one file.
Options

detailDisplays listing with the date and time hexDisplays output in hexadecimal
Requirements
Command privilege level: 1 for logs, 0 for TFTP files Allowed during upgrade: Yes
Example
This command dumps contents of file _cdrIndex.idx.

file dump activelog cm/cdr/_cdrIndex.idx
file get
This command sends the file to another system by using SFTP.
Command Syntax
file get activelog directory/filename [reltime] [abstime] [match] [recurs] inactivelog directory/filename [reltime] [abstime] [match] [recurs] install directory/filename [reltime] [abstime] [match] [recurs]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. directory/filename specifies the path to the file(s) to delete. You can use the wildcard character (*) for filename as long as it resolves to one file.
Options

abstimeAbsolute time period, specified as hh:mm:MM/DD/YY hh:mm:MM/DD/YY reltimeRelative time period, specified as months | weeks | days | hours | minutes value matchMatch a particular string in the filename, specified as string value recursGet all files, including subdirectories
Usage Guidelines
After the command identifies the specified files, you get prompted to enter an SFTP host, username, and password.
F-8
OL-12376-01
Appendix F
Requirements

Examples
This command gets all files in the activelog operating system directory that match the string plat:
file get activelog platform match plat
This command gets all operating system log files for a particular time period:
file get activelog platform/log abstime 18:00:9/27/2005 18:00:9/28/2005
file list
This command lists the log files in an available log directory.
Command Syntax
file list activelog directory [page] [detail] [reverse] [date | size] inactivelog directory [page] [detail] [reverse] [date | size] install directory [page] [detail] [reverse] [date | size]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. directory specifies the path to the directory to list. You can use a wildcard character (*) for directory as long as it resolves to one directory.
Options

pageDisplays the output one screen at a time detailLong listing with date and time reverseReverse sort direction date | sizeSort by date or file size
Requirements
Examples
This example lists operating system log files with details.

file list activelog platform/log page detail
This example lists directories created for Cisco ER logs.

file list activelog er/logs
F-9
This example lists Cisco ER logs in a specified directory by size.

file list activelog er/logs size
file search
This command searches the content of a log and displays the matching lines a page at a time.
Command Syntax
file search activelog directory/filename reg-exp [abstime hh:mm:ss mm/dd/yyyy hh:mm:ss mm/dd/yyyy] [ignorecase] [reltime {days | hours | minutes} timevalue] inactivelog directory/filename reg-exp [abstime hh:mm:ss mm/dd/yyyy hh:mm:ss mm/dd/yyyy] [ignorecase] [reltime {days | hours | minutes} timevalue] install directory/filename reg-exp [abstime hh:mm:ss mm/dd/yyyy hh:mm:ss mm/dd/yyyy] [ignorecase] [reltime {days | hours | minutes} timevalue]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. reg-exp represents a regular expression. directory/filename represents the path to the file(s) to search. You can use the wildcard character (*) to represent all or part of the filename.
Options

abstimeSpecifies which files to search based on file creation time. Enter a start time and an end time. days|hours|minutesSpecifies whether the file age is in days, hours, or minutes. ignorecaseIgnores case when searching reltimeSpecifies which files to search based on file creation time. Enter the age of files to search. hh:mm:ss mm/dd/yyyyAn absolute time, in the format hours:minutes:seconds month/day/year. timevalueThe age of files to search. The unit of this value is specified with the {days | hours | minutes} option.
Usage Guidelines
Write the search term in the form of a regular expression, which is a special text string for describing a search pattern. If the search term is found in only one file, the filename appears at the top of the output. If the search term is found in multiple files, each line of the output begins with the filename in which the matching line was found.
Requirements
F-10
OL-12376-01
Appendix F
Example
file search activelog platform/log/platform.log Err[a-z] ignorecase
file tail
This command tails (prints the last few lines) of a log file.
Command Syntax
file tail activelog directory/filename [detail] [hex] [lines] inactivelog directory/filename [detail] [hex] [lines] install directory/filename [detail] [hex] [lines]
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. directory/filename specifies the path to the file to tail. You can use the wildcard character (*) for filename as long as it resolves to one file.
Options

detailLong listing with date and time hexHexadecimal listing linesNumber of lines to display
Requirements
Example
This example tails the operating system CLI log file.

file tail activelog platform/log/cli00001.log
file view
This command displays the contents of a file.
Command Syntax
file view activelog directory/filename inactivelog directory/filename install directory/filename
F-11
Parameters

activelog specifies a log on the active side. inactivelog specifies a log on the inactive side. install specifies an installation log. directory/filename specifies the path to the file to view. You can use the wildcard character (*) for filename as long as it resolves to one file.
Usage Guidelines
Caution
Do not use this command to view binary files because this can corrupt the terminal session.
Requirements

Examples
This example displays the install log:

file view install install.log
This example displays a particular CDR file:

file view activelog er/logs/CERAdmin01.log
run sql
This command allows you to run an SQL command.
Command Syntax
run sql sql_statement

Parameters
sql_statement represents the SQL command to run.
Requirements

Examples
This example runs an SQL command:

run sql select * from cerserver
set account
This command sets up a new account on the operating system.
F-12
OL-12376-01
Appendix F
Command Syntax
set account name

Parameters
name represents the username for the new account.
Usage Guidelines
After you enter the username, the system prompts you to enter the privilege level and password for the new account.
Requirements
set commandcount
This command changes the CLI command prompt, so it displays how many CLI commands have executed.
Command Syntax
set commandcount {enable | disable}

Parameters
unit-name represents the name of the certificate that you want to regenerate.
Requirements
set ipsec
This command allows you to set IPSec policies and associations.
Command Syntax
set ipsec policy {ALL | policy-name} association policy-name {ALL | association-name}

Parameters

policy-name represents an IPSec policy. association-name represents an IPSec association.
Requirements
F-13
set logging
This command allows you to enable or disable logging.
Command Syntax
set logging {enable | disable}

Requirements
set network dhcp

This command enables or disables DHCP for Ethernet interface 0. You cannot configure Ethernet interface 1.
Command Syntax
set network dhcp eth0 {enable | disable}

Parameters
eth0 specifies Ethernet interface 0.
Usage Guidelines
Caution
If you continue, this command causes the system to restart. Cisco also recommends that you restart all nodes whenever any IP address gets changed.
Requirements
set network dns

This command sets the IP address for the primary or secondary DNS server.
Command Syntax
set network dns {primary | secondary} ip-address

Parameters
ip-address represents the IP address of the primary or secondary DNS server.
Usage Guidelines
F-14
OL-12376-01
Appendix F
Caution

Requirements
set network dns options

This command sets DNS options.
Command Syntax
set network dns options [timeout seconds] [attempts number] [rotate]

Parameters

timeout sets the DNS request timeout. attempts sets the number of times to attempt a DNS request before quitting. rotate causes the system to rotate among the configured DNS servers, distributing the load. seconds specifies the DNS timeout period, in seconds. number specifies the number of attempts.
Requirements
set network domain

This command sets the domain name for the system.
Command Syntax
set network domain domain-name

Parameters
domain-name represents the system domain that you want to assign.
Usage Guidelines
Caution

Requirements
F-15
set network failover

This command enables and disables Network Fault Tolerance.
Command Syntax
failover {enable | disable}

Parameters

enable enables Network Fault Tolerance. disable disables Network Fault Tolerance.
Requirements
set network gateway

This command enables you to configure the IP address of the network gateway.
Command Syntax
set network gateway ip-address

Parameters
ip-address represents the IP address of the network gateway that you want to assign.
Usage Guidelines
Caution
If you continue, this command causes the system to restart.

Requirements
set network ip
This command sets the IP address for Ethernet interface 0. You cannot configure Ethernet interface 1.
Command Syntax
set network ip eth0 ip-address ip-mask

Parameters

eth0 specifies Ethernet interface 0. ip-address represents the IP address that you want assign.
F-16
OL-12376-01
Appendix F
ip-mask represents the IP mask that you want to assign.
Usage Guidelines
Caution
If you continue, this command causes the system to restart.

Requirements
set network mtu

This command sets the maximum MTU value.
Command Syntax
set network mtu mtu_max

Parameters
mtu_max specifies the maximum MTU value.
Usage Guidelines
Caution
If you continue, the system will temporarily lose network connectivity.
set network max_ip_contrack

This command sets the ip_conntrack_max value.
Command Syntax
set network max_ip_conntrack ip_conntrack_max

Parameters
ip_conntrack_max specifies the value for ip_conntrack_max.
set network nic

This command sets the properties of the Ethernet interface 0. You cannot configure Ethernet interface 1.
Command Syntax
set network nic eth0 [auto en | dis] [speed 10 | 100] [duplex half | full]
F-17
Parameters

eth0 specifies Ethernet interface 0. auto specifies whether auto negotiation gets enabled or disabled. speed specifies whether the speed of the Ethernet connection: 10 or 100 Mbps. duplex specifies half-duplex or full-duplex.
Usage Guidelines
Note
You can enable only one active NIC at a time.
Caution
If you continue, this command causes a temporary loss of network connections while the NIC gets reset.
Requirements
set network pmtud

This command enables and disables Path MTU Discovery.
Command Syntax
set network pmtud [enable | disable]

Parameters

enable enables Path MTU Discovery. disable disables Path MTU Discovery.
Usage Guidelines
Caution
set network status

This command sets the status of Ethernet 0 to up or down. You cannot configure Ethernet interface 1.
Command Syntax
set network status eth0 {up | down}

Parameters
F-18
OL-12376-01
Appendix F
Usage Guidelines
Caution

Requirements
set password
This command allows you to change the administrator password.
Command Syntax
set password admin

Usage Guidelines
The systems prompts you for the old and new passwords.
Caution
The password must contain at least six characters, and the system checks it for strength.
Requirements
set smtp
This command sets the SMTP server hostname.
Command Syntax
set smtp hostname

Parameters
hostname represents the SMTP server name.
Requirements
set timezone
This command lets you change the system time zone.
F-19
Command Syntax
set timezone timezone

Parameters
timezone specifies the new timezone.
Usage Guidelines
Enter enough characters to uniquely identify the new time zone. Be aware that the time-zone name is case-sensitive.
Caution
You must restart the system after you change the time zone.
Requirements

Example
This example sets the time zone to Pacific time.

set timezone Pac
set trace
This command sets trace activity for the specified task.
Command Syntax
set trace enable Error tname enable Special tname enable State_Transition tname enable Significant tname enable Entry_exit tname enable Arbitrary tname enable Detailed tname disable tname
Parameters

tname represents the task for which you want to enable or disable traces. enable Error sets task trace settings to the error level. enable Special sets task trace settings to the special level. enable State_Transition sets task trace settings to the state transition level. enable Significant sets task trace settings to the significant level. enable Entry_exit sets task trace settings to the entry_exit level.
F-20
OL-12376-01
Appendix F
enable Arbitrary sets task trace settings to the arbitrary level. enable Detailed sets task trace settings to the detailed level. disable unsets the task trace settings.
Requirements
set web-security
This command sets the web security certificate information for the operating system.
Command Syntax
set web-security orgunit orgname locality state country

Parameters

orgunit represents the organizational unit. orgname represents the organizational name. locality represents the organization location. state represents the organization state. country represents the organization country.
Requirements
set workingdir
This command sets the working directory for active, inactive, and installation logs.
Command Syntax
set workingdir activelog directory inactivelog directory

Parameters

activelog sets the working directory for active logs. inactivelog set the working directory for inactive logs. directory represents the current working directory.
Requirements
Command privilege level: 0 for logs, 1 for TFTP Allowed during upgrade: Yes
F-21
show account
This command lists current administrator accounts, except the master administrator account.
Command Syntax
show account
Requirements
show cert
This command displays certificate contents and certificate trust lists.
Command Syntax
show cert own filename trust filename list {own | trust}

Parameters

filename represents the name of the certificate file. own specifies owned certificates. trust specifies trusted certificates. list specifies a certificate trust list.
Requirements

Example
This command displays own certificate trust lists.

show cert list own
show firewall list

This command displays system aspects of the server.
Command Syntax
show firewall list [detail] [page] [file filename]

Options
detailDisplays detailed statistics on every available device on the system
F-22
OL-12376-01
Appendix F
pageDisplays the output one page at a time file filenameOutputs the information to a file
Note
The file option saves the information to platform/cli/filename.txt. Ensure the file name does not contain the . character.
Requirements
show hardware
This command displays the following information on the platform hardware.
Command Syntax
show hardware
Usage Guidelines
This command displays the following information on the platform hardware:

Platform Serial number BIOS build level BIOS manufacturer Active processors RAID controller status
Requirements
show ipsec
This command displays information on IPSec policies and associations.
Command Syntax
show ipsec policy association policy information policy association

Parameters
policy displays all IPSec policies on the node.
F-23
association displays the association list and status for the policy. information displays the association details and status for the policy. policy represents the name of a specific IPSec policy. association represents the association name.
Requirements
Command privilege level: 1 Allowed during upgrade: yes

Example
This example displays IPSec policies.

show ipsec policy
show logins
This command lists recent logins to the server.
Command Syntax
show logins number

Parameters
number specifies the number of most recent logins to display. The default is 20.
show myself
This command displays information about the current account.
Command Syntax
show myself
Requirements
show network
This command displays network information.
Command Syntax
show network eth0 [options] [detail] failover [detail] [page] route [detail]
F-24
OL-12376-01
Appendix F
status [detail] [listen] [process] [all] [nodns] [search stext] all [detail]
Parameters

eth0 specifies Ethernet 0. failover specifies Network Fault Tolerance information. route specifies network routing information. status specifies active Internet connections. all specifies all basic network information.
Options

optionsDisplays additional information detailDisplays more detailed additional information pageDisplays information 1 page at a time. listenDisplays only listening sockets processDisplays the process ID and name of the program to which each socket belongs allDisplays both listening and nonlistening sockets nodnsDisplays numerical addresses without any DNS information search stextSearches for the stext in the output
Usage Guidelines
The eth0 parameter displays Ethernet port 0 settings, including DHCP and DNS configurations and options.
Requirements

Example
This example displays active Internet connections.

show network status
show open
This command displays open files and ports on the system.
Syntax Description
show open files [all] [process processID] [regexp reg_exp] ports [all] [regexp reg_exp]
Parameters
files displays open files on the system.
F-25
ports displays open ports on the system.
Options

allDisplays all open files or ports processDisplays open files that belong to the specified process processIDSpecifies a process regexpDisplays open files or ports that match the specified regular expression reg_expA regular expression
show packages
This command displays the name and version for installed packages.
Command Syntax
show packages active name [page] inactive name [page]

Parameters
name represents the package name. To display all active or inactive packages, use the wildcard character (*).
Options
pageDisplays the output one page at a time
Requirements
show process load

This command displays the CPU load for each active process.
Command Syntax
show process load [cont] [clear] [noidle] [num xx] [thread] [cpu | memory | time] [page]
Options

contCommand repeats continuously clearClears screen before displaying output noidleIgnore idle or zombie processes num xxSets the number of processes to display (Default=10, all = all processes) threadDisplays threads cpuDisplays output by CPU usage
F-26
OL-12376-01
Appendix F
memorySorts output by memory usage timeSorts output by time usage pageDisplays one page at a time
Requirements

Example
This example shows the CPU load for each process one page at a time.
show process load page
show process list

This command displays all processes.
Command Syntax
list [page] [short] [detail] [thread] [fd] [cont] [clear] [process id] [argument name] [owner name]
Options

pageDisplays one page at a time shortDisplays short listing detailDisplays a detailed listing threadInclude thread processes in the listing fdShow file descriptors that are associated with a process contCommand repeats continuously clearClears screen before displaying output process idShows only specific process number or command name argument nameShow only specific process with argument name owner nameShow only specific process with owner name
Requirements

Example
This example shows detailed process listing one page at a time.

show process list detail page
F-27
show registry
This command displays the contents of the registry.
Command Syntax
show registry system component [name] [page]

Parameters

system represents the registry system name. component represents the registry component name. name represents the name of the parameter to show.
Note
To display all items, enter the wildcard character (*).

Options
pageDisplays one page at a time

Requirements

Example
This example shows contents of the cm system, dbl/sdi component.

show registry cm dbl/sdi
show smtp
This command displays the name of the SMTP host.
Command Syntax
show snmp
Requirements
show stats io
This command displays system IO statistics.
Command Syntax
show stats io [kilo] [detail] [page] [file filename]
F-28
OL-12376-01
Appendix F
Options

kiloDisplays statistics in kilobytes detailDisplays detailed statistics on every available device on the system and overrides the kilo option pageDisplays one page at a time file filenameOutputs the information to a file
Note
The file option saves the information to platform/cli/filename.txt. The file name cannot contain the . character.
Requirements
show status
This command displays basic platform status.
Command Syntax
show status
Usage Guidelines
This command displays the following basic platform status:

Host name Date Time zone Locale Product version Platform version CPU usage Memory and disk usage
Requirements
Command privilege level: 0
show tech all

This command displays the combined output of all show tech commands.
Command Syntax
all [page] [file filename]
F-29
Options

pageDisplays one page at a time file filenameOutputs the information to a file
Note
Requirements
show tech database

This command creates a CSV file of the entire database.
Command Syntax
show tech database

Requirements
show tech dbintegrity

This command displays the database integrity.
Command Syntax
show tech dbintegrity
show tech dbinuse

This command displays the database in use.
Command Syntax
show tech dbinuse

Requirements
F-30
OL-12376-01
Appendix F
show tech dbschema

This command displays the database schema in a CSV file.
Command Syntax
show tech dbschema

Requirements
show tech dbstateinfo

This command displays the state of the database.
Command Syntax
show tech dbstateinfo
show tech network

This command displays network aspects of the server.
Command Syntax
show tech network [page] [file filename]

Options

Note
Requirements
show tech prefs

This command displays all preferences files for Cisco ER and its database. This information is written to a file, which can be viewed subsequently using the file view CLI.
Command Syntax
show tech prefs
F-31
show tech runtime

This command displays runtime aspects of the server.
Command Syntax
show tech params runtime [page] [file filename]

Options

Note
Requirements
show tech systables

This command displays the name of all tables in the sysmaster database.
Command Syntax
show tech systables

Requirements
show tech system

This command displays system aspects of the server.
Command Syntax
show tech system [page] [file filename]

Options
Note
F-32
OL-12376-01
Appendix F
Requirements
show tech table

This command displays the contents of the specified database table.
Command Syntax
show tech table table_name [page] [csv]

Parameters
table_name represents the name of the table to display.

Options

pageDisplays the output one page at a time csvSends the output to a comma separated values file
Requirements
show tech version

This command displays the version of the installed components.
Command Syntax
show tech version [page]

Options

Requirements
show timezone
This command displays time zone information.
Command Syntax
show timezone config list [page]
F-33
Parameters

config displays the current time zone settings. list displays the available time zones.
Options
Requirements
show trace
This command displays trace information for a particular task.
Command Syntax
show trace [task_name]

Parameters
task_name represents the name of the task for which you want to display the trace information.
Note
If you do not enter any parameters, the command returns a list of available tasks.
Requirements

Example
This example displays trace information for CDP.

show trace cdps
show version
This command displays the software version on the active or inactive partition.
Command Syntax
show version active inactive

Parameters
active displays the version running on the active partition. inactive displays the version on the inactive partition.
F-34
OL-12376-01
Appendix F
Requirements
show web-security
This command displays the contents of the current web-security certificate.
Command Syntax
show web-security
Requirements
show workingdir
This command retrieves the current working directory for activelog, inactivelog, install, and TFTP.
Command Syntax
show workingdir
Requirements
unset ipsec
This command allows you to disable IPSec policies and associations.
Command Syntax
unset ipsec policy {ALL | policy-name} association policy-name {ALL | association-name}

Parameters

policy-name represents the name of an IPSec policy. association-name represents the name of an IPSec association.
Requirements
F-35
unset network
This command unsets DNS options.
Command Syntax
unset network dns options [timeout] [attempts] [rotate]

Parameters

timeout sets the wait time before the system considers a DNS query failed to the default. attempts sets the number of DNS attempts to make before failing to the default. rotate sets the method for selecting a nameserver to the default. This affects how loads are distributed across nameservers.
Usage Guidelines
Caution
utils core list

This command lists all existing core files.
Command Syntax
utils core list
utils core analyze

This command generates a backtrace for the specified core file, a thread list, and the current value of all CPU registers.
Command Syntax
utils core analyze core file name

Parameters
core file name specifies the name of a core file.
Usage Guidelines
The command creates a file of the same name as the core file, with a .txt extension, in the same directory as the core file. This command works only on the active partition.
F-36
OL-12376-01
Appendix F
utils csa disable

This command stops Cisco Security Agent (CSA).
Command Syntax
utils csa disable

Requirements
utils csa enable

This command enables Cisco Security Agent (CSA).
Command Syntax
utils csa enable

Usage Guidelines
The system prompts you to confirm that you want to enable CSA.
Caution
You must restart the system after you start CSA.

Requirements
utils csa status

This command displays the current status of Cisco Security Agent (CSA).
Command Syntax
utils csa status

Usage Guidelines
The system indicates whether CSA is running.

Requirements
F-37
utils dbreplication status

This command displays the status of database replication.
Command Syntax
utils dbreplication status
utils dbreplication repair

This command repairs database replication.
Command Syntax
utils dbreplication repair
utils dbreplication reset

This command resets and restarts database replication.
Command Syntax
utils dbreplication reset
utils disaster_recovery backup tape

This command starts a backup job and stores the resulting tar file on tape.
Command Syntax
utils disaster_recovery backup tape tapeid

Parameters
tapeid represents the ID of an available tape device.
Requirements
utils disaster_recovery backup network

This command starts a backup job and stores the resulting tar file on a remote server.
Command Syntax
utils disaster_recovery backup network path servername username

Parameters
path represents the location of the backup files on the remote server.
F-38
OL-12376-01
Appendix F
servername represents the IP address or host name of the server where you stored the backup files. username represents the username that is needed to log in to the remote server.
Usage Guidelines
Note
The system prompts you to enter the password for the account on the remote server.
Requirements
utils disaster_recovery cancel_backup

This command cancels the ongoing backup job.
Command Syntax
utils disaster_recovery cancel_backup

Usage Guidelines
The system prompts you to confirm that you want to cancel the backup job.
Requirements
utils disaster_recovery restore tape

This command starts a restore job and takes the backup tar file from tape.
Command Syntax
utils disaster_recovery restore tape server tarfilename tapeid

Parameters

server specifies the hostname of the server that you want to restore. tarfilename specifies the name of the file to restore. tapeid specifies the name of the tape device from which to perform the restore job.
Requirements
F-39
utils disaster_recovery restore network

This command starts a restore job and takes the backup tar file from a remote server.
Command Syntax
utils disaster_recovery restore network restore_server tarfilename path servername username

Parameters

restore_server specifies the hostname of the server that you want to restore. tarfilename specifies the name of the file to restore. path represents the location of the backup files on the remote server. servername represents the IP address or host name of the server where you stored the backup files. username represents the username that is needed to log in to the remote server.
Usage Guidelines
Note
The system prompts you to enter the password for the account on the remote server.
Requirements
utils disaster_recovery show_backupfiles tape

This command displays information about the backup files that are stored on a tape.
Command Syntax
utils disaster_recovery show_backupfiles tape tapeid

Parameters
tapeid represents the ID of an available tape device.
Requirements
utils disaster_recovery show_backupfiles network

This command displays information about the backup files that are stored on a remote server.
Command Syntax
utils disaster_recovery show_backupfiles network path servername username
F-40
OL-12376-01
Appendix F
Parameters

path represents the location of the backup files on the remote server. servername represents the IP address or host name of the server where you stored the backup files. username represents the username that is needed to log in to the remote server.
Requirements
utils disaster_recovery show_registration

This command displays the registered features and components on the specified server.
Command Syntax
utils disaster_recovery show_registration hostname

Parameters
hostname specifies the server for which you want to display registration information.
Requirements
utils disaster_recovery show_tapeid

This command displays a list of tape device IDs.
Command Syntax
utils disaster_recovery show_tapeid

Requirements
utils disaster_recovery status

This command displays the status of the current backup or restore job.
Command Syntax
utils disaster_recovery status operation

Parameters
operation specifies the name of the ongoing operation: backup or restore.
F-41
Requirements
utils fior status

This command will provide the status of the file I/O reporting service.
Command Syntax
utils fior status

Requirements
utils fior enable

This command will enable the file I/O reporting service to be started automatically when the machine boots. This command will not start the service without a reboot. Instead, use utils fior start.
Command Syntax
utils fior enable

Requirements
utils fior disable

This command will prevent the file I/O reporting service from being started automatically when the machine boots. This command will not stop a currently running service. Instead, use utils fior stop.
Command Syntax
utils fior disable

Requirements
F-42
OL-12376-01
Appendix F
utils fior start

This command will start a previously stopped file I/O reporting service. Once it is started, the service will remain in this state until it is stopped or the machine is rebooted.
Command Syntax
utils fior start

Requirements
utils fior stop

This command will stop the file I/O reporting service. Once stopped, the service will remain in this state either until it is started or the machine is rebooted.
Command Syntax
utils fior stop

Requirements
utils fior list

This command will provide a chronological list, oldest to newest, of file I/O events.
Command Syntax
utils fior list [start=date-time] [stop=date-time]

Parameters
date-time is the date and time of the event, in the form: %H:%M, %H:%M:%S, %a,%H:%M, %a,%H:%M:%S, %Y-%m-%d,%H:%M, %Y-%m-%d,%H:%M:%S
Requirements
F-43
utils fior top

This command will provide a list of top processes that create file I/O. This list can be sorted by either the total number of bytes read, the total number of bytes written, the rate of bytes read, or the rate of bytes written.
Command Syntax
utils fior top n sort_by [start=date-time] [stop=date-time]

Parameters
n is the number of processes sort_by is read, write, read-rate, write-rate date-time is of the form: %H:%M, %H:%M:%S, %a,%H:%M, %a,%H:%M:%S, %Y-%m-%d,%H:%M, %Y-%m-%d,%H:%M:%S
Requirements
unset ipsec
This command allows you to disable IPSec policies and associations.
Command Syntax
unset ipsec policy {ALL | policy-name} association policy-name {ALL | association-name}

Parameters

policy-name represents the name of an IPSec policy association-name represents the name of an IPSec association
Defaults
Optional. Default values the command uses.

Requirements
F-44
OL-12376-01
Appendix F
utils iothrottle enable

This command enables I/O throttling enhancements. When enabled, I/O throttling enhancements lower the impact of upgrades on an active system.
Command Syntax
utils iothrottle enable
utils iothrottle disable

This command disables I/O throttling enhancements. This could adversely affect the system during upgrades.
Command Syntax
utils iothrottle disable
utils iothrottle status

This command displays the status of I/O throttling enhancements.
Command Syntax
utils iothrottle status
utils netdump client

This command configures the netdump client.
Command Syntax
utils netdump client start ip-address-of-netdump-server status stop

Parameters

start starts the netdump client. status displays the status of the netdump client. stop stops the netdump client. ip-address-of-netdump-server specifies the IP address of the netdump server to which the client will send diagnostic information.
Usage Guidelines
In the event of a kernel panic crash, the netdump client sends diagnostic information about the crash to a netdump server.
F-45
Requirements
utils netdump server

This command configures the netdump server.
Command Syntax
utils netdump server add-client ip-address-of-netdump-client delete-client ip-address-of-netdump-client list-clients start status stop
Parameters

add-client adds a netdump client. delete-client deletes a netdump client. list-clients lists the clients that are registered with this netdump server. start starts the netdump server. status displays the status of the netdump server. stop stops the netdump server. ip-address-of-netdump-client specifies the IP address of a netdump client.
Usage Guidelines
In the event of a kernel panic crash, a netdump-enabled client system sends diagnostic information about the crash to the netdump server. netdump diagnostic information gets stored in the following location on the netdump server: crash/. The subdirectories whose names comprise a client IP address and a date contain netdump information. You can configure each Cisco ER server as both a netdump client and server. If the server is on another Cisco ER server, only the kernel panic trace signature gets sent to the server; otherwise, an entire core dump gets sent.
Requirements
F-46
OL-12376-01
Appendix F
utils network arp

This command lists, sets, or deletes Address Resolution Protocol (ARP) table entries.
Command Syntax
utils network arp list [host host] [page] [numeric] set {host} {address} delete host
Parameters

list lists the contents of the address resolution protocol table. set sets an entry in the address resolution protocol table. delete deletes an entry in the address resolution table. host represents the host name or IP address of the host to add or delete to the table. address represents the MAC address of the host to be added. Enter the MAC address in the following format: XX:XX:XX:XX:XX:XX.
Options

pageDisplays the output one page at a time numericDisplays hosts as dotted IP addresses
Requirements
utils network capture eth0

This command captures IP packets on the specified Ethernet interface.
Command Syntax
utils network capture eth0 [page] [numeric] [file fname] [count num] [size bytes] [src addr] [dest addr] [port num]
Parameters
Options
pageDisplays the output one page at a time When you use the page or file options, the complete capture of all requested packets must occur before the command completes.
numericDisplays hosts as dotted IP addresses file fnameOutputs the information to a file
F-47
The file option saves the information to platform/cli/fname.cap. The filename cannot contain the . character.
count numSets a count of the number of packets to capture For screen output, the maximum count equals 1000, and, for file output, the maximum count equals 10,000.
size bytesSets the number of bytes of the packet to capture For screen output, the maximum number of bytes equals 128, for file output, the maximum of bytes can be any number or ALL.
src addrSpecifies the source address of the packet as a host name or IPV4 address dest addrSpecifies the destination address of the packet as a host name or IPV4 address port numSpecifies the port number of the packet, either source or destination
Requirements
utils network host

This command resolves a host name to an address or an address to a host name.
Command Syntax
utils network host hostname [server server-name] [page] [detail] [srv]

Parameters
hostname represents the host name or IP address that you want to resolve.
Options

server-nameSpecifies an alternate domain name server pageDisplays the output one screen at a time detailDisplays a detailed listing srvDisplays DNS SRV records.
Requirements
utils network ping

This command allows you to ping another server.
Command Syntax
utils network ping destination [count]
F-48
OL-12376-01
Appendix F
Parameters
destination represents the hostname or IP address of the server that you want to ping.
Options
countSpecifies the number of times to ping the external server. The default count equals 4.
Requirements
utils network tracert

This command traces IP packets that are sent to a remote destination.
Command Syntax
utils network tracert destination

Parameters
destination represents the hostname or IP address of the server to which you want to send a trace.
Requirements
utils ntp
This command displays the NTP status or configuration.
Command Syntax
utils ntp {status | config}

Requirements
utils remote_account
This command allows you to enable, disable, create, and check the status of a remote account.
Command Syntax
utils remote_account status enable
F-49
disable create username life

Parameters

username specifies the name of the remote account. The username can contain only lowercase characters and must be more than six-characters long. life specifies the life of the account in days. After the specified number of day, the account expires.
Usage Guidelines
A remote account generates a pass phrase that allows Cisco Systems support personnel to get access to the system for the specified life of the account. You can have only one remote account that is enabled at a time.
Requirements

Example
utils remote_account status
utils reset_ui_administrator_password
This command resets the Cisco ER Administration password.
Command Syntax
utils reset_ui_administrator_password
utils service list

This command retrieves a list of all services and their status.
Command Syntax
utils service list [page]

Options
Requirements
F-50
OL-12376-01
Appendix F
utils service
This command stops, starts, or restarts a service.
Command Syntax
utils service start service-name stop service-name restart service-name

Parameters
service-name represents the name of the service that you want to stop or start:
System NTP System SSH Cisco IDS Cisco Tomcat Cisco Database Layer Monitor Cisco Emergency Responder Cisco Phone Tracking Engine Cisco Tomcat
enable enables auto-restart. disable disables auto-restart. show shows the auto-restart status.
Requirements
utils snmp get

This command queries values for the given OIDs from the specified device.
Command Syntax
utils snmp get ipaddress snmp_community_string oid [oid2] ... [oidN]

Parameters

ipaddress is the IP Address of the device which needs to be SNMP-queried. snmp_community_string is the SNMP Read community string configured on the device. oid, oid2, ... oidN are OIDs to be queried.
F-51
Requirements
utils snmp getnext

This command will query values for the lexicographical successors of the given OIDs from the specified device.
Syntax
utils snmp getnext ipaddress snmp_community_string oid [oid2] ... [oidN]

Parameters

Requirements
utils snmp walk

This command will query values in the entire sub-tree of the given OIDs from the specified device.
Syntax
utils snmp walk ipaddress snmp_community_string oid [oid2] ... [oidN]

Parameters

Requirements
utils system
This command allows you to restart the system on the same partition, restart the system on the inactive partition, or shut down the system.
Command Syntax
utils system {restart | shutdown | switch-version}
F-52
OL-12376-01
Appendix F
Usage Guidelines
The utils system shutdown command has a 5-minute timeout. If the system does not shut down within 5 minutes, the command gives you the option of doing a forced shutdown.
Requirements
utils system upgrade

This command allows you to upgrade the server.
Command Syntax
utils system upgrade start cancel list {local | remote] path get {local | remote} filename
Parameters

start starts an upgrade with the upgrade file obtained with the get parameter. cancel cancels the active upgrade. list lists the available upgrade files. local specifies that the upgrade files are on a local drive. remote specifies that the upgrade files are on a remote system. path is the path to the upgrade file(s). get gets an upgrade file from which to upgrade. filename is the name of the upgrade file.
F-53
F-54
OL-12376-01
A P P E N D I X
Using the AFT for Specific Service Providers

These topics describe how to use the ALI Formatting Tool (AFT) for specific service providers:

Using the ALI Formatting Tool for Bell-Canada, page G-1 Using the ALI Formatting Tool for SBC-Ameritech, page G-2 Using the ALI Formatting Tool for SBC-PacBell, page G-3 Using the ALI Formatting Tool for SBC-Southwestern Bell, page G-4 Using the ALI Formatting Tool for Qwest, page G-5 Using the ALI Formatting Tool for Verizon, page G-5
Using the ALI Formatting Tool for Bell-Canada

These topics describe how to use AFT for Bell-Canada:

Modifying the Transaction Code, page G-1 Entering Bell-Canada-Specific Data, page G-2
Modifying the Transaction Code

When using the AFT with Bell Canada as your service provider, ensure that the Transaction Code for Bell Canada is either A or D. Otherwise, Bell Canada will reject the record and return the record in an Error Return file with an error message. Table G-1 shows the values displayed in the Function Field in NENA records and the corresponding values for the Transaction Code in Bell Canada records.
Table G-1 NENA and Bell Canada Function/Transaction Fields
NENA Function Code Field I for Insert a new record C for Change a record
Bell Canada Transaction Code Field A for Add a new record A for Change a record.
Note
The NENA Function Code C is mapped to Bell Canadas Transaction Code A.
D for Delete a record
D for Delete a record
G-1
Appendix G Using the ALI Formatting Tool for SBC-Ameritech
Entering Bell-Canada-Specific Data

Table G-2 describes the remaining Bell Canada-specific fields. Some fields require data to generate ALI files in the format specified in Bell Canadas ALI data support documentation; other fields can remain blank. If there is an error in these fields, Bell Canada will reject the record and send back a Error Return file with an error code.
Note
You do not configure the Language Indicator field using AFT; AFT sets the field to E for English.
Table G-2
Modifying Bell Canada-Specific Fields
Field Service Class Postal Code Municipality Code Class of Service System Source Location Type
Description
Format
Notes Required field. Required field. The first character must be alphabetic. Required field. Required field. Required field. Optional field.
Type of telephone service of the 3 alphanumeric characters customers Terminal Number Postal code of the customers service address Unique code assigned to each municipality Code that identifies the grade, class, and type of service 6 alphanumeric characters 3 alphanumeric characters 5 alphanumeric characters
Identifies the source database of 1 alphabetic character the Transaction Record Type of location within a building (for example, apartment) Number of the location identified in the Location Type field (for example, apartment 2, floor 2) City, town, village, borough, or locality 15 alphanumeric characters
Location Number
6 alphanumeric characters
Optional field.
Service Municipality LSP ID
35 alphanumeric characters
Required field. Required field. Must be the valid LSP Identifier provided to the PS ALI customer by Bell Canada.
Unique code provided to the PS 5 alphanumeric characters ALI customer by Bell Canada that denotes the provider of local telephone service.
Using the ALI Formatting Tool for SBC-Ameritech

SBC Ameritech (Ameritech) does not have any service provider-specific fields that you must modify using the AFT. However, when using AFT to format records for Ameritech, you may need to modify the Function Code.
G-2
OL-12376-01
Appendix G
Using the AFT for Specific Service Providers Using the ALI Formatting Tool for SBC-PacBell
Cisco ER sets the Function Code to one of the following:

I for Inserting a new ALI record (the default) C for Updating an ALI record, such as changing a street name D for Deleting an ALI record
If you make changes to an ALI record in Cisco ER to correct errors reported by Ameritech, you may need to use AFT to change the Function Code for ELIN records. For example, Cisco ER initially generates ALI records with a function code of I, for Insert. After you format a file and export it to Ameritech using AFT, Ameritech may reject the file because of an error, such as the street suffix is incorrect. You cannot change the street suffix in AFT because this field is disabled. Instead, you must change the ALI record using Cisco ER. When Cisco ER generates the ALI record the second time after you make the change, it sets the Function Code to C because it assumes that the first file was accepted. Use AFT to change the Function Code for ELIN records from C to I. Then, generate the format using AFT and send the reformatted file to Ameritech.
Using the ALI Formatting Tool for SBC-PacBell

These topics describe how to use the AFT for SBC-PacBell:

Enabling Call Back For This ELIN, page G-3 Changing the Function Code, page G-3
Enabling Call Back For This ELIN

Cisco ER displays the ELIN at the PSAP. If the emergency call is cut off for any reason, or if the PSAP simply needs to talk to the caller again, the PSAP can then dial to reconnect to the emergency caller. The Call Back for this ELIN option allows you to specify a direct inward dial (DID) number that can be used by the PSAP when a call from a fictitious number is made to 911. The Call Back for this ELIN option performs two important functions:

It alerts the PSAP that the phone they are calling back may not have generated the 911 call. It enables the PSAP to call back to a phone that is located near the fictitious telephone number that did place the call.
Cisco recommends that you always enable this option by checking the Call Back for this ELIN field. (The default is to leave the field blank, which defaults to No.)
Changing the Function Code


If you make changes to an ALI record in Cisco ER to correct errors reported by your service provider, you may need to use AFT to change the Function Code for ELIN records.
G-3
Appendix G Using the ALI Formatting Tool for SBC-Southwestern Bell
For example, Cisco ER initially generates ALI records with a function code of I, for Insert. After you format a file and export it to SBC Pacific Bell (PacBell) using AFT, PacBell may reject the file. The error may be that the street suffix is incorrect, for example. You cannot change the street suffix in AFT because this field is disabled. You must change the ALI record using Cisco ER. When Cisco ER generates the ALI record the second time after you make the change, it sets the Function Code to C because it assumes that the first file was accepted. Use AFT to change the Function Code for ELIN records from C to I. Then, generate the format using AFT and send the reformatted file to PacBell.
Using the ALI Formatting Tool for SBC-Southwestern Bell

These topics describe how to use the AFT for SBC-Southwestern Bell:

Modifying PS Code for SBC-Southwestern Bell, page G-4 Changing the Function Code, page G-4
Modifying PS Code for SBC-Southwestern Bell

In order to make the ELIN records readable by Southwestern Bell, you may need to use AFT to update the PS Code field; this field is specific to Southwestern Bell. The PS Code is a four-digit code that the Southwestern Bell system assigns whenever the system configures a new PS site. This code is associated with the PS user's login and source. The PS Code is a feature that allows only records with the correct PS Code to be processed into tables for the PS Site. If the PS Code does not match the configured Source Name that is assigned to the PS Site, the record will not process. Before you generate a formatted file using AFT, make sure that PS Code and the Source Name match. For more information, refer to the Southwestern Bell documentation.


If you make changes to an ALI record in Cisco ER to correct errors reported by your service provider, you may need to use AFT to change the Function Code for ELIN records. For example, Cisco ER initially generates ALI records with a function code of I, for Insert. After you format a file and export it to Southwestern Bell using AFT, Southwestern Bell may reject the file. The error may be that the street suffix is incorrect, for example. You cannot change the street suffix in AFT because this field is disabled. You must change the ALI record using Cisco ER. When Cisco ER generates the ALI record the second time after you make the change, it sets the Function Code to C because it assumes that the first file was accepted. Use AFT to change the Function Code for ELIN records from C to I. Then, generate the format using AFT and send the reformatted file to Southwestern Bell.
G-4
OL-12376-01
Appendix G
Using the AFT for Specific Service Providers Using the ALI Formatting Tool for Qwest
Using the ALI Formatting Tool for Qwest

Qwest does not have any service provider-specific fields that you must modify using the AFT. However, when using AFT to format records for Qwest, you may need to modify the Function Code. Cisco Emergency Responder (Cisco ER) sets the Function Code to one of the following:

If you make changes to an ALI record in Cisco ER to correct errors reported by Qwest, you may need to use AFT to change the Function Code for ELIN records. For example, Cisco ER initially generates ALI records with a function code of I, for Insert. After you format a file and export it to Qwest using AFT, Qwest may reject the file because of an error. The error may be that the street suffix is incorrect, for example. You cannot change the street suffix in AFT because this field is disabled. You must change the ALI record using Cisco ER. When Cisco ER generates the ALI record the second time after you make the change, it sets the Function Code to C because it assumes that the first file was accepted. Use AFT to change the Function Code for ELIN records from C to I. Then, generate the format using AFT and send the reformatted file to Qwest
Using the ALI Formatting Tool for Verizon

These topics describe how to use the AFT for Verizon:

Changing the Function Code, page G-5 Modifying the Disability Indicator for Verizon New England States, page G-6 Modifying the Customer Name for Verizon West States, page G-6 Modifying the Location for New Jersey, page G-7

Verizon does not have any service provider-specific fields that you must modify using the AFT. However, when using AFT to format records for Verizon, you may need to modify the Function Code. Cisco ER sets the Function Code to one of the following:

IInserting a new ALI record (the default) CUpdating an ALI record, such as changing a street name DDeleting an ALI record UUnlocking an ALI Record (included to support Local Number Portability) MMigrating an ALI Record (included to support Local Number Portability)
If you make changes to an ALI record in Cisco ER to correct errors reported by Verizon, you may need to use AFT to change the Function Code for ELIN records. For example, Cisco ER initially generates ALI records with a Function Code of I, for Insert. After you format a file and export it to Verizon using AFT, Verizon may reject the file because of an error. The error may be that the street suffix is incorrect, for example. You cannot change the street suffix in AFT because this field is disabled. You must change the ALI record using Cisco ER.
G-5
Appendix G Using the ALI Formatting Tool for Verizon
When Cisco ER generates the ALI record the second time after you make the change, it sets the Function Code to C because it assumes that the first file was accepted. Use AFT to change the Function Code for ELIN records from C to I. Then, generate the format using AFT and send the reformatted file to Verizon.
Modifying the Disability Indicator for Verizon New England States

To make the ELIN records readable by Verizon's New England states (MA, ME, NH, RI, VT), you may need to use AFT to update the Disability Indicator field; this field is specific to Verizon. The Disability Indicator is a reserved 20-character field that the carrier can use to enter disability information. Table G-3 shows the Disability Indicator designations that you can use to populate the location field of an ALI record.
Table G-3 Disability Indicator Descriptions
Disability Indicator LSS MI B DHH TTY SI DD
Description Life Support System Mobility Impaired Blind Deaf and Hard of Hearing Teletypewriter Speech Impaired Developmentally Disabled
AFT intelligently identifies the New England states (from the state field of the ALI record) and allows you to update the Disability Indicator field individually (by selecting an New England ELIN record from the tree) or in bulk (through the Bulk Update feature).
Modifying the Customer Name for Verizon West States

The Verizon West states (CA, HI, ID, IL, IN, MI, NC, OH, OR, SC, TX, WA, WI) read the Customer Name field in the following format that uses a comma followed by a space between the last name and the first name: Last Name, First Name This format prevents display errors at the PSAP. You can use AFT to update the field so that it follows the format that is used by Verizon West states. AFT intelligently identifies the Verizon West states (from the state field of the ALI record) and allows you to update the Customer Name field individually (by selecting a Verizon West ELIN record from the tree) or in bulk (through the Bulk Update feature). When you use AFT to make updates, it creates two different entries for the Customer Name fieldone in the Cisco ER database and one in the Service Provider's database. To avoid future discrepancies, you should also make the same update in the Customer Name field in the Cisco ER GUI.
G-6
OL-12376-01
Appendix G
Using the AFT for Specific Service Providers Using the ALI Formatting Tool for Verizon
Modifying the Location for New Jersey

Verizon's New Jersey (NJ) system is a keyword-driven system that is based on a state requirement that location data be uniformly displayed at all PSAPs. Data is extracted from the location field only when one or more keywords, associated data, and delimiters are present in exact prescribed format. The NJ system location has four separate and distinct location type fields which can be simultaneously displayed at the PSAP. The location type fields are as follows:

Unit Type (APT, BOX, LOT, PIER, RM, ROOM, RU, SUIT, SUITE, UNIT, WING) Floor Number (FLR) Building Description (BLDG) Coin Location Description (DES)
AFT intelligently identifies the NJ system-specific requirement for Location (from the state field of the ALI record) and allows you to update the location individually (by selecting a New Jersey ELIN) as well as in bulk (through the Bulk Update feature). When you use AFT to make updates, it creates two different entries for the Customer Name fieldone in the Cisco ER database and one in the Service Provider's database. To avoid future discrepancies, you should also make the exact update in the Location field in Cisco ER GUI.
G-7
Appendix G Using the ALI Formatting Tool for Verizon
G-8
OL-12376-01
I N D EX
Numerics
802.11b endpoints configuring IP subnet-based ERLs troubleshooting
11-4 5-33
ALI Information page assigning calling search space phones to partition
A-17 1-2
ANI (automatic number identification)

3-3, 4-3
ERL to switch ports and phones

3-3, 4-3
5-47
A
adding ERLs
5-28 5-27
Audio Driver log audit trail, ERL
B-16 5-38
onsite alert (security) personnel switches

5-42 A-14 A-42 A-45
B
backing up configuration Backup Device List page Backup History page Backup Status page busy signal
11-7 D-5 D-6 G-1 11-31 D-1
Add New ERL page
Add New Manual Phone page Add New Synthetic Phone page Add Role page
A-50 A-9 A-53
Bell-Canada, using AFT for
Add Subscriber page Add User Group page Add User page
A-48
administration, troubleshooting administrative interfaces Admin Utility using

9-1 E-1 5-2
11-15
C
call history troubleshooting viewing
5-57 A-54 11-10
web interface definition exporting setting up

1-2 5-37 5-30
Call History page calling search space assigning creating

1-19
ALI (automatic location information)
3-3, 4-3 3-5, 4-5
Cisco Emergency Responder

3-2, 4-2
submission requirements ALI Formatting Tool
CAMA (centralized automated message accounting) definition

12-3 1-2 1-17 5-39 1-15
generating a formatted ALI file overview

12-1 A-60
obtaining CAM table use
ALI Formatting Tool page
capacity planning
IN-1
Index
CDP (Cisco Discovery Protocol) Cisco ER server CER Admin log Cerdbmon log CER Server log
B-16 B-17 B-16 11-30 5-39
features
1-4 1-8 2-3 5-15
how it routes calls
switch requirements
installation procedure logging into and out of network overview partition planning
B-16 3-4, 4-4 1-1 1-7
CER Phone Tracking log

B-16
Certificate Management/IPSec log Certificate Monitor page certificates deleting displaying

7-8 7-7 7-7 C-13
preparing network preparing users route points terminology

3-6, 4-6
1-17
10-1
serviceability settings reference

1-2 11-1 1-3
B-1, C-1
downloading managing
7-7
troubleshooting
7-11
downloading a signing request monitoring expiration dates regenerating uploading See CTL Cisco Emergency Responder Admin Utility web interface calling search space
3-5, 4-5 7-8 7-9
understanding users
5-9
updating after adding devices

7-11
11-22
Cisco ER cluster deleting group

11-22 11-22 3-17, 4-17
Certificate Trust List
identifying members
inter-Cisco ER-group route patterns phones moving between clusters

E-1 11-31
11-23
understanding Cisco ER Cisco ER group capacity planning

3-1 1-15
1-12
backing up and restoring configuration
Cisco Unified CallManager configuration Cisco Unified CallManager user

3-19
configuring
5-16 3-17, 4-17
creating inter-Cisco ER-group route pattern deleting from cluster

4-19 11-22 11-22
Cisco Unified Communications Manager configuration 4-1 Cisco Unified Communications Manager user clusters and groups
1-12 F-1 5-1 A-1
identifying cluster members telephony settings

5-18
understanding groups and clusters Cisco ER Group Settings page Cisco ER server configuring
5-19 11-23 A-3
1-12
command line interface configuration overview configuring

5-1
configuration settings reference configuring serviceability data integrity and reliability deploying
1-21 6-1 1-16
starting and stopping troubleshooting

11-15
Cisco ER Server Groups in Cluster page Cisco IP SoftPhone, supported version

D-1 3-4, 4-4
A-2 1-4
Disaster Recovery System web interface emergency call telephony configuration
IN-2
OL-12376-01
Index
Cisco Unified CallManager configuring

3-1 3-4
Cisco ER group telephony settings Cisco ER server

5-19 5-16 3-1
5-18
configuring emergency calls example setup

3-1
Cisco ER servers and groups Cisco Unified CallManager
Cisco Unified Communications Manager changing version configuring

4-1 4-4 9-2
Cisco Unified Communicaitions Manager Disaster Recovery System gateways

3-16, 4-16 3-1, 4-2 8-1
4-1
configuring emergency calls example setup troubleshooting CLI See command line interface CLI log CLM log clusters configuring restoring collecting emergency call history logs system logs
11-31 8-9 5-23 B-16 B-16 4-1
phone route plan SNMP

5-39 5-33
identifying supported clusters

11-21
5-21
subnet ERLs switches

5-39
CiscoWorks2000, integrating with
11-29
switch ports
5-47 5-47
switch ports a few at a time Control Center, using Control Center page
11-19 6-1 B-1 5-32
converting PS-ALI data CPU Log Files page creating
cluster database host, updating
CPU and Memory Usage page

B-13
B-11
alternate emergency call numbers calling search space

11-27
3-15, 4-15
3-2, 3-5, 4-2, 4-5 3-4, 4-4 3-6, 4-6
Cisco Emergency Responder partition Cisco ER cluster Cisco ER users

1-12 5-9 3-19
Cisco Emergency Responder route points

11-27 F-1
trace and debug information command line interface CLI basics

F-2 F-4 F-2 F-4
Cisco Unified CallManager user CTI ports

3-8, 4-8 3-10, 4-10
CLI commands
Cisco Unified Communications Manager user ELIN route patterns
4-19
completing commands ending a CLI session getting help commands, CLI

F-3
ELIN translation patterns

F-1
3-11, 3-12, 4-11, 4-12 5-28 3-17, 4-17
starting a CLI session

F-4
ERL (emergency response locations) inter-Cisco ER-group route pattern partition CTI applications, call forwarded by
5-1 5-1 6-1 1-11 3-2, 4-2
configuration, backing up Configure IP Subnet page configuring
11-31 A-36
creating ports
3-8, 4-8
Cisco Emergency Responder overview Cisco ER group

5-16
Cisco Emergency Responder Serviceability
IN-3
Index
CTL downloading managing uploading

7-7 7-9 7-7
DMA troubleshooting
11-32 2-9 5-6
using the DMA tool Download utility, using DRS log

B-16
D
database changing host details data integrity See DMA debug, setting defining phone manually schedule test ERLs
5-41 5-34 F-4 5-53 11-27 1-16 9-3 11-19
E
ELIN (emergency location identification number) creating route patterns definition
1-2 1-18 3-9, 4-9 11-6 3-10, 4-10 3-11, 3-12, 4-11, 4-12
updating the cluster database host Data Migration Assistant
creating translation patterns obtaining DIDs
setting up numbers Email Alert Settings page emergency call busy signal
F-4 F-5 F-5 11-7
troubleshooting not sent to PSAP

A-8
delete account command delete dns command delete ipsec command delete process command delete smtp command deploying one site, one PSAP deleting Cisco ER group
Cisco Unified CallManager configuration Cisco Unified Communications Manager configuration 4-4 collecting history
11-27 3-15, 4-15
3-4
F-6 11-22
creating alternate numbers creating route points definition

1-2 11-10
3-6, 4-6
1-21 1-23 1-22
history problems how routed

1-8
one site, satellite offices overview

1-21 1-25
one site, two or more PSAPs two or more sites definition

1-2 1-18
not intercepted troubleshooting
11-5 11-5 11-9
troubleshooting incorrect location information troubleshooting not sent to correct PSAP viewing history enhanced 911 (E911) overview
1-1 1-2 1-1 5-57 1-3 11-7
DID (direct inward dial) obtaining numbers configuring using

D-1 D-1 B-15 8-1
emergency caller, definition
Disaster Recovery System
terminology understanding
web interface Disk Usage page
IN-4
OL-12376-01
Index
ERL (emergency response locations) administrator role assigning to ports definition exporting identifying
1-3 5-36 5-50, 5-56 10-2 5-47
switches
5-45 5-50, 5-56
switch port/ERL configuration Export IP Subnets page Export LAN Switch page
A-37 A-29 A-43 A-56
Export Manual Phones page Export PS-ALI Records page Export Switch Ports page
5-28 5-27
exporting port/ERL configuration

5-28
A-33
identifying default importing

5-32
identifying onsite alert (security) personnel importing configuration management setting up

5-26 5-53 5-49, 5-55
F
features, Cisco Emergency Responder file check command file delete command file dump command file get command
F-8 F-4 F-6 F-6 F-7 1-4
manually-defined phones
5-29, 5-30 5-25 5-52 5-38
understanding
unlocated phones viewing audit trail working with

5-24
File I/O Reporting Service (FIOR) file list command

F-9 A-61
File Management Utility page

A-55 A-12 A-59 1-3
ERL Audit Trail page ERL Debug Tool page
file search command file tail command file view command

C-5
F-10
ERL Configuration page
F-11 F-11 A-35 A-41
ESZ (emergency service zone), definition Ethernet Configuration page events, viewing Event Viewer message No port to place call using
6-2 B-16 B-2 11-8 11-29
Find and List IP Subnets page Find and List Roles page
A-49
Find and List Maunally Configured Phones page Find and List Synthetic Phones page Find and List User Groups page Find and List Users page Find ERL Data page
A-12 A-46 A-51 A-45
Event Viewer log Event Viewer page example
one site, one PSAP
1-21 1-23 1-22
G
gateway, configuring
3-16, 4-16
one site, satellite offices two or more sites Export ERL Data page exporting ALI ERL
5-37 5-36 1-25 A-21
one site, two or more PSAPs
H
hardware prerequisites, for installation supported phones and switches
2-1 1-4
IN-5
Index
hardware status, viewing Hardware Status page history backup restore

D-5 D-5 C-2
7-2
IPSec changing policy displaying policy IPSec Policy List page IP Subnet Phones page
7-12 7-12 7-13
setting up new policy
C-13 A-37
I
icons, control center identifying Cisco Unified Communications Manager clusters 5-21 groups in Cisco ER cluster switches IDS See Informix Dynamic Server Import ERL Data page importing ERLs
5-32 5-44 5-49, 5-55 A-21 5-42 5-52 11-22 5-27 11-23
J
JTAPI log
B-16
L
LAN Switch Details page License Manager page
A-7 11-33 A-28
onsite alert (security) personnel unlocated phones
Linux upgrades, troubleshooting log, emergency call history login, troubleshooting logs system using
B-15 6-9 11-15 11-27
logging into Cisco Emergency Responder
5-15
switches
switch port and ERL configuration Import IP Subnets page Import LAN Switch page Import Switch Ports page Install/Upgrade log installation hardware and software prerequisites on new system overview Install DB log integrating with CiscoWorks2000
11-29 2-1 B-17 7-2 2-3 B-16 A-38 A-30 A-44
M
maintaining data integrity and reliability managing
11-20 1-16
Import Manual Phones page
A-34
Informix Dynamic Server, troubleshooting
ERLs phones
5-26 11-29
performance
5-47 2-1
Manual Backup page
D-4 A-41
Manually Configured Phones page Memory Log Files page Modify Role page Modify User page
11-29 A-50 A-52 B-13
installed software, viewing
MIB2 SystemGroup Configuration page Modify User Group page

A-47
B-11
with network management systems inter-Cisco ER-group route pattern
3-17, 4-17
IN-6
OL-12376-01
Index
monitoring subsystem status
11-30 1-3
P
partition
MSAG (master street address guide), definition
N
NENA (National Emergency Number Association), definition 1-3 network administrators role
10-3 1-7 11-29
assigning creating phone
3-3, 4-3 3-4, 4-4

3-2, 4-2 11-29
performance, managing assigning ERLs to configuring

3-3, 4-3
5-47
how Cisco ER fits into preparing

1-17
management systems, integrating with Network Configuration page network status, viewing non-PSAP deployment NTP Server List page NTP server settings
7-4 7-2 5-29 C-6 C-3
creating a partition defining manually managing supported

5-47
3-2, 4-2 5-53 5-52
identifying unlocated setting up route plan

1-4 11-1
3-1, 4-2
troubleshooting
troubleshooting disappearance
11-4 11-2
O
obtaining CAMA or PRI trunk DIDs for ELINs identifying
5-27 11-8 11-9 1-18 1-17
troubleshooting undiscovered troubleshooting unlocated upgrading

1-19
11-2
phone tracking, defining schedule Phone Tracking Schedule page ping

7-16 C-16
5-41
A-24
onsite alert (security) personnel not getting calls preparing users overview call routing deployment E911
1-1 1-4 2-1 1-8 1-12
Ping Configuration page planning capacity

1-15
not getting email or page

10-1

A-10
1-1
Onsite Alert Settings page
Point to a New Pubilsher page port, troubleshooting preparing

11-16
E-1
Cisco ER groups and clusters

1-21
Cisco Emergency Responder users network staff

1-20 1-17 B-13 A-58 5-32 1-17 10-1
10-1
onsite alert (security) users PRI, obtaining Processes page
features network
installation
1-7
PS-ALI Converter page PS-ALI data, converting
IN-7
Index
PSAP (public safety answering point) callback errors definition

1-3 11-6 11-7 11-8
route pattern alternate emergency call number creating ELIN

3-10, 4-10 3-17, 4-17 3-15, 4-15
troubleshooting ELIN not sent to Publisher, pointing to a different

9-1
inter-Cisco ER-group route plan, setting up run sql command

F-12
troubleshooting emergency call not sent to
3-1, 4-2 3-6, 4-6
route points, Cisco Emergency Responder Run Switch-Port and Phone Update page
Q
Qwest, using AFT for
G-5
A-31
S
SBC-Ameritech, using AFT for SBC-PacBell, using AFT for
G-2
R
read community string reliability
1-16 C-17 5-39
G-3 G-4
SBC-Southwestern Bell, using AFT for schedule, defining Schedule List page security
5-41 D-2
Remote Access Configuration page remote support overview setting up

7-17 7-17 B-16 D-5 D-8
identifying personnel preparing users ServerGroup page Serviceability tools Control Center
11-31 5-2 6-1 6-2 10-1 C-1
5-27
Remote Support log Restore History page Restore Status page Restore Wizard
D-7
Server Settings for CERServerGroup page
A-6
restoring configuration roles adding new creating default deleting modifying

5-11
Event Viewer using

6-1
role-based user management
Serviceability web interface service provider

10-4
B-1
Cisco ER system administrator

5-11 5-3 5-12 10-2
ALI submission DIDs for ELINs services ping

7-16
1-19 1-18
ERL administrator
5-12
remote support overview

7-17 7-17
network administrator Roles Configuration page
10-3 A-49
setting up Servm log

B-16
set account command set ipsec command set logging command

F-12 F-13
set commandcount command

F-13 F-14
IN-8
OL-12376-01
Index
set network dhcp command set network dns command
F-14 F-14 F-15
show process load command show registry command show smtp command show stats io command show status command show tech all command
F-17 F-28 F-28 F-28 F-29 F-29
F-26
set network dns options command set network domain command set network failover command set network gateway command set network ip command set network mtu command set network nic command set network pmtud command set network status command set password command set smtp command settings Ethernet time setting up ALI
5-30 5-28 3-9, 4-9 7-5 7-3 7-4 F-19 F-19 F-19 F-16 F-15 F-16
F-16
show tech ccm_service command show tech database command show tech dbintegrity command show tech dbinuse command show tech dbschema command show tech dbstateinfo command show tech network command show tech prefs command show tech runtime command show tech systables command show tech system command show tech table command show tech version command show timezone command show trace command show version command
F-34 F-34 F-35 F-35 F-33 F-33 F-31 F-32 F-30
F-30
set network max_ip_contrack command

F-17 F-17 F-18 F-18
F-30
F-30 F-31 F-31
F-31
set timezone command
F-32 F-32
NTP servers
F-33
default ERL ERL
ELIN numbers
5-29, 5-30
show web-security command show workingdir command SMTP, configuring SMTP Settings page
F-21 7-5 C-7
phone route plans set trace command
3-1, 4-2
F-20
set web-security command set workingdir command show account command show cert command
F-22
SNMP configuring
5-39 11-30 B-4 B-6
F-21 F-22
monitoring subsystems
F-22
SNMP Community String Configuration page

F-23
show firewall list command show hardware command show ipsec command show logins command show myself command show network command show open command show packages command show process list command
F-23 F-24 F-24
SNMP Notification Destination Configuration page SNMP Settings page

A-22 B-7
SNMP User Configuration page
SNMP V3 Notification Destination Configuration page B-9 software prerequisites, for installation
2-1
F-24
F-25 F-26 F-27
requirements
1-4
IN-9
Index
upgrades from local source from remote source

7-14 7-15 7-2 C-15
System Monitor tools CPU and Memory Usage using

6-6 7-3 6-7
viewing installed software Software Packages page staff, preparing status hardware
7-2 1-20 C-4
system status, viewing System Status page

C-4
Software Installation/Upgrade page
starting and stopping Cisco ER server
11-23
T
Telephony Settings page terminology
1-2 5-34 A-4
monitoring subsystems system, viewing submitting ALI switch adding one at a time administrators role configuring
5-39 5-47 1-19 A-9 7-3
11-30
test ERL, configuring time settings

7-5
viewing network status Subscriber node, adding
7-2
Time Settings page Tomcat log trace, setting

B-16 11-27
C-8
tracking 802.11b endpoints

5-42 10-3
5-33 3-11, 3-12, 4-11, 4-12
translation patterns, creating ELINs troubleshooting 802.11b endpoints administration

5-47 11-4 11-15
configuring ports exporting identifying

5-45
configuring ports a few at a time exporting port/ERL configuration

5-42
busy signal call history
11-7 11-10 1-8 11-1 11-23 11-21
5-50, 5-56
call routing overview

5-49, 5-55 5-44
importing port/ERL configuration importing switches supported

1-4 11-16 5-39
Cisco ER server status problem DMA

11-32
Cisco Unified Communications Manager ELIN for default ERL used for non-default ERLs 11-6 ELIN not transmitted to PSAP emergency call not intercepted emergency call problems ERL integrity
A-45 1-16 11-29 11-9 11-5 11-6 11-5
troubleshooting upgrading
1-19
understanding requirements switch-port and phone update defining schedule running manually
5-41 5-45 A-31
emergency call not routed to correct PSAP
11-7
Switch Port Details page Syslog Collector Syslog log system logs
B-16 B-15 11-31
Synthetic Phones page, Find and List
event viewer messages Linux upgrades login problems

11-33 11-15
incorrect location information
onsite alert (security) not getting calls

11-8
IN-10
OL-12376-01
Index
onsite alert (security) not getting email or page performance

11-29 11-4
11-9
Cisco Unified CallManager ERL administrators role preparing

10-1 A-46
3-19 4-19
Cisco Unified Communications Manager

10-2 10-3 11-1 11-8
phone disappears from Cisco ER phone-related problems PSAP callback errors shared line
11-4
network administrators role User Configuration page

11-16
switch and port configuration system and administration undiscovered phones unlocated phones Windows upgrades
11-2 11-2 11-33
user groups creating default

5-13 5-5 A-51
11-15
User Groups Configuration page user management

5-2 F-36
utils core analyze command
U
understanding CDP support in Cisco ER server Cisco Emergency Responder Cisco ER groups and clusters E911
1-1 1-8 5-25 1-3 1-12 10-4 11-30
utils core list command utils csa enable command utils csa status command
F-36 F-37 F-37 F-37 F-38 F-38 F-38 F-38
utils csa disable command
utils dbreplication repair command utils dbreplication reset command utils dbreplication status command
Cisco ER system administrators role emergency call routing ERL administrators role network administrator role switch requirements terminology
1-2 A-39 F-35 F-36 E-3 5-39
utils disaster_recovery backup network command utils disaster_recovery backup tape command
F-38
ERL (emergency response locations)

10-2 1-7
utils disaster_recovery cancel_backup command utils disaster_recovery restore network command utils disaster_recovery restore tape command
F-39 F-40
how Cisco ER fits into network

10-3
F-39
utils disaster_recovery show_backupfiles network command F-40 utils disaster_recovery show_backupfiles tape command F-40 utils disaster_recovery show_registration command utils disaster_recovery show_tapeid command utils disaster_recovery status command utils fior disable
11-22 F-42 F-42 F-41 F-41 F-41
Unlocated Phones page unset ipsec command unset network command
Update Cluster DB Host page Upgrade CCM Version page Upload utility, using user adding
5-9 5-6
updating Cisco ER after adding devices

E-2 1-19
utils fior enable utils fior list utils fior start utils fior status utils fior stop utils fior top
F-43 F-43 F-42 F-43 F-44 F-45
upgrading switches and phones
5-9 10-4
utils iothrottle disable command
Cisco ER system administrators role
IN-11
Index
utils iothrottle enable command utils iothrottle status command utils netdump client command utils netdump server command utils network arp command utils network host command utils network ping command utils network tracert command utils ntp command
F-49
F-45 F-45 F-45 F-46
F-47 F-47
utils network capture eth0 command

F-48 F-48 F-49
utils remote_account command utils service command utils snmp test command utils system command
F-51 F-50 F-51
F-49 F-50
utils reset_ui_administrator_password command utils service list command

F-52 F-53
utils system upgrade command
V
Verizon, using AFT for versions, configuring Version Settings page viewing emergency call history ERL audit trail events
11-29 B-14 5-38 5-57 G-5 7-5 C-8
View Selected Processes page
W
web interfaces
5-2 11-33
Windows upgrades, troubleshooting working with ERLs

5-24
IN-12
OL-12376-01

Cisco Emergency Responder Administration Guide 2.0: Americas Headquarters

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Cisco Emergency Responder Administration Guide 2.0: Americas Headquarters

Diunggah oleh

Hak Cipta:

Format Tersedia

Cisco Emergency Responder Administration Guide 2.

Text Part Number: OL-12376-01

xvii xvii xvii xviii xix xix

Related Documentation Acknowledgements

Obtaining Documentation, Obtaining Support, and Security Guidelines

Planning for Cisco Emergency Responder 2.0