Part I. Deployment and Planning

Chapter 1. Plan for Cisco Emergency Responder

Plan for Cisco Emergency Responder Overview

Understanding Enhanced 911 (E911)

Overview of Enhanced 911 Requirements

E911 and Cisco Emergency Responder Terminology

Understanding Cisco Emergency Responder

Features

Network Hardware and Software Requirements

Emergency Responder Licensing

License Usage

License Compliance

Emergency Responder and Your Network

Emergency Responder and Your Local Service Provider

Emergency Call Process

Call Routing Order

CTI Application Call Forwarding

Cisco Emergency Responder Groups

Cisco Emergency Responder Clusters

Track Phone Movement Across a Cluster

Determine Required Cisco Emergency Responder Groups

Data Integrity and Reliability

Network Preparations

CAMA and PRI Trunks

DID Service Provider Numbers

ALI Submission and Service Provider Requirements

Switch and Phone Upgrades

Preparing Your Staff for Emergency Responder

Emergency Responder Deployment

Deployment in Main Site and PSAP

Deployment in Main Site with Two or More PSAPs

Deployment in Main Site with Satellite Offices

Deployment in Main Site Serving Multiple Sites

One Site Serving Multiple Sites with EMCC

Two Main Site Deployments

Deployment in Two Main Sites with Clustering Over the WAN

Support for CTI and JTAPI Over WAN

Cluster Deployment in Two Main Sites with EMCC

Configure a Local Route Group in a Wide Area Network

Part II. Installation and Upgrade

Chapter 2. Cisco Emergency Responder Installation

Cisco Emergency Responder Installation Overview

Hardware and Software Prerequisites

System Preparations

Installation and Migration on the Cisco UCS Server

System Requirements

Installation on Cisco UCS Server

Configuration Checklist for Installing and Configuring the Server

Install Preparations

Set Up RAID

vSphere Client Installation

Aligning the Datastore Used for VMs

Create Virtual Machines

Download Virtual Machine Templates (OVA Templates)

Install Emergency Responder on VM

Virtual Machine Configurations

Migrate to Emergency Responder on Cisco UCS Server

VMWare Support

Emergency Responder Daily Operations on Cisco UCS Server

Hardware Monitoring From the VM

Hardware Monitoring From CIMC

Hardware Monitoring From VSphere Client and VCenter

Related Documentation

Installation on a New System

Install Emergency Responder Publisher

Install Emergency Responder Subscriber

Emergency Responder Upgrade

Part III. Configuration

Chapter 3. Configure Cisco Unified Communications Manager

Configure Cisco Unified Communications Manager Overview

Set Up Phone Route Plans

Create Phone Partition

Create Phone Calling Search Space

Assign Partition and Calling Search Space to Phones

Set Up Cisco Unified Communications Manager for Emergency Responder

Create Emergency Responder Partition

Create Emergency Responder Calling Search Space

Create Emergency Call Route Points

Create Required CTI Ports

Create a Cisco Unified Communications Manager Group for Cisco Emergency Responder

Error and System Messages

ELIN Numbers Emergency Calls and PSAP Callbacks

Create Route Patterns for ERLs

Create Translation Patterns for ELINs

Create Translation Patterns for 9.911

Create Route Points for 9.911

Create Alternate Emergency Call Numbers

Set Up Calling Search Space for Gateway and PSAP Connection

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

Create Route Patterns on Unified CM

Create an Inter-Emergency Responder Group Route Pattern

Create Emergency Responder Cisco Unified Communications Manager User

Chapter 4. Configure Cisco Emergency Responder

Cisco Emergency Responder Configuration Overview

Configuration Overview

Website Interfaces

Role-Based User Management

User Management

Role Management

User Group Management

Upload and Download Utilities

Download File

Upload File

Emergency Responder Configuration

Set Up Users and Groups

Set Up Switch Connection

Manage Onsite Alerts, ERLs, and ALI Data

Set Up Emergency Responder with Intrado V9-1-1 for Enterprise Service

Emergency Responder User Management

Add Users

Modify Users

Change User Authentication Mode

Change Password for a Local User

Change a Unified CM Cluster for a Remote User

Delete Users

Changing Users to Remote in Bulk

Emergency Responder Role Management

Add Roles

Modify Roles

Delete Roles

Emergency Responder User Group Management

Add User Groups

Modify User Groups

Delete User Groups

Log In to Emergency Responder

Restrict Maximum Number of Concurrent Sessions

Server and Server Group Configuration

Set Up a Server Group

Set Up Group Telephony Settings for Server

Modify the Emergency Number

Configure Servers

Upload License File

Identify Cisco Unified Communications Manager Clusters

Set Up Emergency Responder Cluster and Cluster DB Host

Cisco Unified Communications Manager Cluster Changes

Work with Emergency Responder Locations

ERLs

ERL Management

Add Onsite Security Personnel

ERL Creation

Set Up Default ERL

Set Up ERLs for Non-PSAP Deployment

Set Up Individual ERL and Automatic Location Information (ALI)

Import Several ERLs

Convert ALI Data

Set Up IP Subnet-based ERLs

Set Up Test ERLs

Export ERL Information

Export ALI Information for Submission to Your Service Provider

View Audit Trail for ERL

Emergency Responder Switch Configuration

Switch Requirements for Emergency Responder

Set Up SNMP Connection

Set Up SNMPv2

Set Up SNMPv3

Define Phone Tracking and Switch Update Schedules

LAN Switch Identification

Identify LAN Switches One at a Time

Import a Group of Switches

Export Switch Information

Manually Run the Switch-Port and Phone Update Process

Track Change of Switch IP Address Dynamically

Phone Management

Switch Port Configuration

Set Up Individual Switch Ports

Set Up Large Number of Ports

Export Switch Port Information

Switch-Port Change Reporting for Wired Cisco Unified IP Phones

EnergyWise

Cisco EnergyWise Phone User Experience

Phone Discovery Scenarios Common to EnergyWise Users

Power Save Plus Mode Limitations

Identify Unlocated Phones

Manually Define Phones

Assign Large Number of Manually Configured Phones to ERLs

Export Manually Configured Phone Information

Synthetic Phones

View Emergency Call History

Chapter 5. Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Emergency Responder and Intrado V9-1-1Enterprise Services Overview

Intrado V9-1-1 for Enterprise Service

Emergency Call Flow

Set Up Support for Intrado V9-1-1 for Enterprise Service

Set Up Intrado VUI Settings

Set Up Intrado Route Patterns on Emergency Responder

Set Up Intrado ERLs

Intrado ERL Imports

Intrado ERL Information Export

Reconcile ALI Discrepancies

ERL Data Migration

Migrate Conventional ERL Data to Intrado ERL Data

Migrate Intrado ERL Data to Conventional ERL Data

Set Up Emergency Responder to Support Off-Premise Users

Set Up Emergency Responder Location Management in Cisco Unified Communications Manager

Set Up AXL Application User

Set Up AXL Authentication

Set Up Off-Premise ERL

Off-Premise ERL Imports

Off-Premise ERL Information Exports

Add Scheduled Intrado Updates

Update Scheduled Intrado Update

Chapter 6. Configure Cisco Emergency Responder Serviceability

Cisco Emergency Responder Serviceability Configuration Overview

Serviceability Tools

Use Control Center

Use Event Viewer

SNMP Configuration

Set Up SNMP Community String

Set Up SNMP Users

Set Up MIB2

System Monitor Tools

Use CPU and Memory Usage Tool

Use Processes Tool

Use Disk Usage Tool

Use Emergency Responder Logs

Chapter 7. Configure Cisco Unified Operating System

Access Cisco Unified Communications Operating System Administration

Recover Administrator and Security Passwords

View Cisco Unified OS Information

View ServerGroup Information

View Hardware Status

View Network Status

View Installed Software

View System Status

View IP Preferences

Display and Modify Cisco Unified OS Settings

Set Up Ethernet Settings

Set Up NTP Servers

Set Up SMTP Settings

Set Up Time Settings

Manage Software Versions

Change IP Addresses for Emergency Responder Servers

Change IP Address of Emergency Responder Publisher or Standalone Server

Change IP Address of Emergency Responder Subscriber

Change IP Address of Emergency Responder Publisher and Subscriber

Security Management

Set Internet Explorer Security Options

Certificate Management

Display Certificates

Download Certificate or CTL to Your Local System

Certificate Deletion or Regeneration

Certificate or Certificate Trust List Uploads

Use Third-Party CA Certificates

Set Up Certificate Expiration Monitor

IPsec Management

Display or Change Existing IPsec Policy

Set Up IPsec Policy

Manage Existing IPsec Policies

Software Upgrades

Software Upgrade Overview

Supported Upgrades

Upgrade Cisco Unified Operating System

Upgrade File

Install or Upgrade Software From DVD

Install Software From Network Drive or Remote Server

Troubleshoot Stalled Upgrades

Revert to Previous Version

Revert Publisher Server to Previous Version

Revert Subscriber Server to Previous Version

Upload Customized Logon Message

Cisco Unified OS Services

Ping Another System

Set Up Remote Support

Chapter 8. Configure Cisco Emergency Responder Disaster Recovery System

Disaster Recovery System Overview

Backup and Restore Procedures

Perform Backup Procedure

Perform Restore Procedure

Supported Features and Components

System Requirements

Access Disaster Recovery System

Master Agent Duties and Activation

Local Agents

Add Backup Devices

Create and Edit Backup Schedules

Manage Backup Schedules

Start Manual Backup

Check Backup Status

Restore Backup File

Restore Entire Server Group

Restore Publisher Server

Restore Subscriber Server

View Restore Status

Backup and Restore History

View Backup History

View Restore History

Trace Files

Use the CLI for Backup and Restore

Part IV. Administration

Chapter 9. Cisco Emergency Responder Admin Utility

Cisco Emergency Responder Admin Utility Overview

Change Cisco Unified Communications Manager Version

Update Emergency Responder Cluster Database Host Details

Chapter 10. Cisco Emergency Responder User Preparation

Cisco Emergency Responder User Preparation Overview

Emergency Responder Onsite Alert Personnel Preparations

Emergency Responder ERL Administrator Role

Emergency Responder Network Administrator Role

Emergency Responder System Administrator Role

Chapter 11. ALI Formatting Tool

ALI Formatting Tool Overview

Features

File Generation

ALI Formatting Tool Interface Capabilities

Generate Formatted ALI File

Part V. Troubleshooting

Chapter 12. Troubleshoot Cisco Emergency Responder

Troubleshoot Phone-Related Problems

Check Unified CM SNMP Settings

Unlocated Phones

Phones Not Located with SMNPv3

IP Subnet Marked as Non-trackable

Phone Disappears in Emergency Responder

Wrong ERL Used for Shared Line

Wireless Endpoints Using Unexpected ERL

Troubleshoot Emergency Call Problems

Emergency Calls Not Intercepted by Emergency Responder

ELIN Not Transmitted to PSAP

ELIN Default ERL Used for Calls From Other ERLs

Emergency Calls Not Routed to Correct PSAP

Emergency Calls Get Busy Signal and Not Routed

PSAP Call Back Errors

PSAP Cannot Reach Original Emergency Call Extension

Onsite Alert Security Personnel Get Callbacks From PSAP

Onsite Alert Personnel Not Getting Telephone Alerts

Onsite Alert Phone Does Not Ring When Emergency Call Placed

Prompts for Phone Alerts Not Getting Played

Onsite Alert Personnel Not Getting Email or Paging Notifications

Incorrect Location Information Sent to Onsite Alert Personnel

Emergency Call History Problems

Emergency Call Information Does Not Appear in Call History

Call History Does Not Show Call ELIN and Route Pattern

Troubleshoot Licensing

License Manager Status Messages

Cisco Prime License Manager Messages

Troubleshoot Email Alerts

JTAPI Incompatibility Warning

JTAPI Route Point Registration Failure Alarm

Emergency Call Alert

Transition Alert

Tracking Failure

Failed to Get Provider Alert

Failed to Establish Communication with Emergency Responder Phone Tracking Engine

Lost Communication with Emergency Responder Phone Tracking Engine

Failed to Send Unlocated Phone Details to Remote Emergency Responder Server Group

Emergency Call Could Not Be Routed

Calling Party Modification Failed

Troubleshoot Web Alerts

Web Alert Refreshes Every 30 Seconds

Troubleshoot Emergency Responder System and Administration Problems

Cannot Validate Publisher

Troubleshoot Login Problems

Cannot Access Emergency Responder Administration Website

HTTP Error 500

Cisco Unified Operations Manager

Troubleshoot Emergency Responder Switch and Port Configuration Problems

Phones Do Not Get Discovered

Emergency Responder Does Not Show Ports on Switch

Some Phones Do Not Appear in Switch Port List

Cannot Delete Switch From Emergency Responder Configuration

Import or Export of Switch Port Details Fails

Import of Some Switch Port Configurations Fail

Phones Moved To and From Various Emergency Responder Groups Incorrectly Display in Switch Port Details

Check Emergency Responder Configuration Using ERL Debug Tool

Publisher and Subscriber Server Replacement

Replace Faulty Subscriber

Replace Faulty Publisher

Emergency Responder Admin Utility

Use Emergency Responder Admin Utility Tool

Set Up Subscriber Database

Database and Enterprise Replication Troubleshooting Commands

Replication Fails to Start After Subscriber and DNS Installation

Troubleshoot Emergency Responder System Problems

Emergency Responder Intra-Cluster Call Routing Fails or Phones Not Discovered Correctly

Emergency Responder Exits After Starting

Emergency Responder Groups in Cluster Screen Does Not Load and Displays a Cannot Connect to Cluster DB Host Error

Troubleshoot Cisco Unified Communications Manager Configuration Problems

Emergency Responder Does Not Register with Route Points and CTI Ports

Cannot Delete Unified CM From Emergency Responder Configuration

Phone Moves Between Clusters

Identify Emergency Responder Groups and Servers in Cluster

Manage Emergency Responder Server

Troubleshoot ALI Data Uploads

Fix ALI Data Records

NENA 2.0 and 2.1 File Formats

NENA 3.0 File Formats

Call History Logs

Trace and Debug Information

Enable Emergency Responder Trace and Debug Information

Syslog Enablement

Event Messages

Performance Management

Network Management Systems Integration

Cisco Discovery Protocol Support

Emergency Responder Components

Collect Information From Syslog

Data Backup and Recovery

Troubleshoot Data Migration Assistant

DMA Backup and Validation Failed

DMA Backup Is Successful but Validation Failed

Troubleshoot Linux Upgrades

No Valid Upgrade Options Found Error Appears on the First Page of Install/Upgrade Menu

Incorrect User Name/Password Error Appears on the First Page of the Install/Upgrade Menu

Checksum Values Do Not Match After Downloading ISO Image on Emergency Responder Server

Upgrade Cancelled and Warning Message Appears Prompting You to Reboot System

Appendix A. Cisco Emergency Responder Administration Web Interface

Server Groups in Cluster

Group Settings

Telephony Settings

Server Settings for Emergency ResponderServerGroup

License Manager

Email Alert Settings

Add Subscriber

Intrado VUI Settings

Onsite Alert Settings

Pager Alert Settings

Conventional ERL

Add New ERL

ALI Information

Export ERL Data

Import ERL Data

Off-Premises ERL

Add New ERL

Off-Premise ERL - Secondary Status

Find Intrado ERL

Default ALI Values

Intrado ERL - Secondary Status

Intrado Schedule

View ALI Discrepancies

View ALI Discrepancies for a Specific ELIN

ERL Migration Tool

SNMP Settings

SNMP v2 Settings Page

SNMP v3 Settings Page

Phone Tracking Schedule

Cisco Unified Communications Manager Clusters

LAN Switch Details

Export LAN Switch

Import LAN Switch

Run Switch-Port and Phone Update

Switch Port Details

Export Switch Ports

Import Switch Ports

Find and List IP Subnets

Configure IP Subnet

IP Subnet Phones

Export IP Subnets

Import IP Subnets

Unlocated Phones

Export Unlocated Phones

Find and List Manually Configured Phone

Add New Manual Phone

Export Manual Phones

Import Manual Phones

Find and List Synthetic Phones

Add New Synthetic Phone

Find and List Users

Add User

Modify User

Change to Remote User

Find and List Roles

Add Role

Modify Role

Find and List User Groups

Add User Group

Modify User Group

Call History

ERL Audit Trail

Export PS-ALI Records

PS-ALI Converter

PS-ALI Records Download

ERL Debug Tool

ERL Debug Tool Export

ALI Formatting Tool

File Management Utility

Purge Call History

Appendix B. Change IP Address and Hostname

IP Address and Hostname Overview

Pre-Change Tasks and System Health Checks

Pre-Change Task List for Cisco Emergency Responder Nodes

Check System Health

Pre-Change Setup

Perform Pre-Change Setup Tasks for Cisco Emergency Responder Nodes

IP Address and Hostname Changes

Change IP Address and Hostname Task List

Change IP Address or Hostname Using Unified Operating System GUI

Change IP Address or Hostname Using CLI

Example CLI Output for Set Network Hostname: Changing Hostname Only of Publisher

Example CLI Output for Set Network Hostname: Changing IP Address and Publisher Hostname

Change IP Address Only

Post-Change Tasks and Verification

Post-Change Task List for Cisco Emergency Responder Nodes

Perform Post-Change Tasks for Cisco Emergency Responder Nodes

Troubleshooting

Troubleshoot Cluster Authentication

Troubleshoot Database Replication

Verify Database Replication

Repair Database Replication

Reset Database Replication

Troubleshoot Network

Troubleshoot Network Time Protocol

Troubleshoot NTP on Subscriber Nodes

Troubleshoot NTP on Publisher Nodes

Appendix C. Cisco Emergency Responder Serviceability Web Interface

Control Center

Event Viewer

SNMP Community String Configuration

SNMP User Configuration

MIB2 System Group Configuration

CPU and Memory Usage

Processes

Disk Usage

System Logs Menu

Appendix D. Cisco Unified Operating System Administration Web Interface

ServerGroup

Hardware Status

Network Configuration

Software Packages

System Status

IP Preferences

Ethernet Configuration

Publisher Settings

NTP Server List

SMTP Settings

Time Settings

Version Settings

Certificate List

Certificate Monitor

IPSec Policy List

Software Installation/Upgrade

Ping Configuration

Remote Access Configuration

Appendix E. Disaster Recovery System Web Interface

Backup Device List

Schedule List

Manual Backup

Backup History and Restore History

Backup Status

Restore Wizard

Restore Status

Appendix F. Admin Utility Web Interface for Cisco Emergency Responder

Update Cisco Unified Communications Manager Version

Update Cluster DB Host

Appendix G. Using AFT for Specific Service Providers

ALI Formatting Tool for Bell Canada

Transaction Code Modifications

Bell Canada Data

ALI Formatting Tool for SBC Ameritech

ALI Formatting Tool for SBC-PacBell

Call Back for ELIN Enablement

Function Code Modifications

ALI Formatting Tool for SBC-Southwestern Bell

PS Code for SBC-Southwestern Bell

Function Code Modifications

ALI Formatting Tool for Qwest

ALI Formatting Tool for Verizon

Function Code Modifications

Verizon New England State Disability Indicator Modifications

Customer Name for Verizon West State Modifications

New Jersey Location Modifications

Appendix H. Event Log Messages

CER_DATABASE

CER_SYSADMIN

CER_TELEPHONY

CER_AGGREGATOR

CER_GROUP

CER_CALLENGINE

CER_CLUSTER

CER_ONSITEALERT

Appendix I. Cisco Emergency Responder Port Usage

Preface

Overview

Audience

Organization

Related Documentation

Obtaining Documentation and Submitting a Service Request

Cisco Product Security Overview

Acknowledgments

Copyright Page

Part I. Deployment and Planning

Chapter 1. Plan for Cisco Emergency Responder

Plan for Cisco Emergency Responder Overview

Cisco Emergency Responder (Emergency Responder) 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 have similar ordinances.

Because emergency call ordinances can differ from location to location within a country, region, state, or even metropolitan area, Emergency Responder gives you the flexibility to configure your emergency call configuration to specific local requirements. However, ordinances differ from location to location, and security requirements differ from company to company, so you must research your security and legal needs before deploying Emergency Responder.

Understanding Enhanced 911 (E911)

Enhanced 911, or E911, is an extension of the basic 911 emergency call standard in North America. The information in the following sections describe E911 requirements and terminology.

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 talks to the caller and arranges the appropriate emergency response, such as sending police, fire, or ambulance teams.

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 is routed to a PSAP, but not necessarily the local one.

- The caller location information must be displayed at the emergency operator 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 or if the PSAP 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 multiline 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 that 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 7000 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.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Understanding Cisco Emergency Responder

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

Features

See the Release Notes for Cisco Emergency Responder for a list of the new and enhanced features. The Emergency Responder Release Notes are located at:

Click Here

Network Hardware and Software Requirements

Emergency Responder 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  located at Click Here .

Emergency Responder Licensing

Cisco Prime License Manager centralizes all of the licensing for Emergency Responder Release 10.0 and later releases.

Emergency Responder communicates the licensing requirements to Cisco Prime License Manager. Emergency Responder attempts to discover all phones on Unified Communications Manager, excluding subnets not tracked by Emergency Responder. Along with the manually configured phones, Emergency Responder builds and sends the corresponding license requirements to the Cisco Prime License Manager. The Cisco Prime License Manager then compares the Emergency Responder license requirements with the licenses installed and reports back license compliance or noncompliance.

For more information, refer to the Enterprise License Manager User Guide.

License Usage

An Emergency Responder license is of single type User and one license is required for each endpoint. Any endpoint capable of making an emergency call requires a Emergency Responder User License. For example, IP phones, analog phones, video endpoints and clients all require an Emergency Responder User License.

Note

Emergency Responder is not part of Cisco Unified Workspace Licensing (UWL) or Cisco User Connect Licensing (UCL).

The License Manager page shows information on Emergency Responder server group license requirements, as reported to the Cisco Prime License Manager. The License Manager page is updated daily when Cisco Prime License Manager communicates with the Emergency Responder.

For additional information, see License Manager.

License Compliance

When first installed, the Emergency Responder is fully operational in demonstration mode for a grace period of 60 days until it has successfully synchronized with the Cisco Prime License Manager and new licenses are installed on Cisco Prime License Manager. After the Cisco Prime License Manager is registered, licenses are installed, and synchronization with the Emergency Responder takes place, the Cisco Prime License Manager communicates with Emergency Responder daily.

Emergency Responder reports the total license requirements to the Cisco Prime License Manager. The Cisco Prime License Manager totals the license requirements for all connected Emergency Responder product instances and compares the total license requirements to the total available installed licenses. The Cisco Prime License Manager then reports the status back to the product instance as In compliance or as Noncompliance.

Noncompliance occurs when:

- There are an insufficient number of licenses.

- Synchronization with the Cisco Prime License Manager has failed.

Warning

You must install new licenses within 60 days of installation or upgrade. If you do not install new licenses within 60 days, the Emergency Responder system stops tracking and updating the Phone Location.

You must purchase user licenses for every endpoint controlled by Unified CM cluster and tracked by Emergency Responder, including hard IP phones, analog phones, video endpoints, and clients.

You can choose not to track the phones in an IP subnet. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones. For additional information, see Configure IP Subnet.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Emergency Responder and Your Local Service Provider

The following figure shows how Cisco Emergency Responder (Emergency Responder) interacts with your local service provider.

Emergency Responder and Your Local Service Provider shows how Cisco Emergency Responder in your network interacts with local service provider. You need to have PRI/CAMA Gateway to send the Calling Party Number to your local service provider.

Cisco Emergency Responder and a Local Service Provider

For more details on PRI/CAMA, see CAMA and PRI Trunks.

Instead of a local service provider, you can connect to a SIP Trunk service provider as shown in Emergency Responder and Your Local Service Provider or a dedicated National Emergency Call Delivery Service such as Intrado as shown in Emergency Responder and Your Local Service Provider.

Cisco Emergency Responder and a SIP Trunk Service Provider

Cisco Emergency Responder and Intrado

For more information on Cisco Unified Border Element, see Cisco Unified Border Element product page on Cisco.com.

For more information on Intrado, see Configure Emergency Responder and Intrado V9-1-1 Enterprise Services.

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Call Routing Order

Emergency Responder 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 phones—The MAC address of the phone matches that of a synthetic phone and is assigned to a test Emergency Response Location (ERL). See Synthetic Phones and Set Up Test ERLs.

- IP Phones tracked behind a switch port—The MAC address of the IP phone is tracked behind a switch port assigned to an ERL. See Switch Port Configuration.

- IP Phones tracked using IP subnet—The IP address of an IP phone belongs to an IP subnet assigned to an ERL.

- IP Phones tracked by another (remote) Emergency Responder server group in the same Emergency Responder cluster—The 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 Emergency Responder server group.

- Manually configured phones—The line number of the phone is manually assigned to an ERL. See Manually Define Phones.

- Unlocated Phones—The MAC address of an IP phone is assigned to an ERL. See Identify Unlocated Phones.

- Default ERL—None of the preceding criteria is used to determine the phone location. The call is routed to the default ERL. See Set Up Default ERL.

Note

MAC or IP address tracking is recommended for Cisco Unified IP Phones. IP phones that are not tracked by MAC or IP address appear as unlocated phones, even if they are assigned a location by manual line number configuration.

Note

Manually configured phones cannot be assigned a location by Emergency Responder based on a line number that includes a leading "+". If you want Emergency Responder to assign locations to analog telephones based on line number, do not configure them with a leading "+" on Unified CM.

Customers should resolve problems that prevent IP phones from being tracked by MAC or IP address (see Unlocated Phones) so that IP phones are 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 does 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

Emergency Responder defines unlocated phones as those Cisco Unified IP Phones that meet all of the following criteria:

- The IP phone is registered to a Cisco Unified Communications Manager known to the Emergency Responder 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 Emergency Responder.

Note

Cisco Unified IP Phones tracked by a remote Emergency Responder server group and IP phones having line numbers manually assigned to an ERL also appear in the Unlocated Phones screen.

Assigning ERLs to Unlocated Phones

Emergency Responder 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 because the IP phone continues to match the criteria for unlocated phones described previously.

- The ERL association is used only when the IP phone is unlocated, as determined by Emergency Responder, using the preceding 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 is valid.

CTI Application Call Forwarding

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 is the location of the application server, not the location of the original caller. This situation occurs even if the application retains the original calling line number. For this reason, you should dial 911 directly.

Cisco Emergency Responder Groups

Deploy Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder Publisher server and Subscriber server make up an Emergency Responder Server Group.

Configuration data for the server groups is stored in a database on the Publisher. This data is replicated to the Subscriber.

Note

Be aware of the following when planning your Emergency Responder system:

- A single Emergency Responder group cannot support clusters with a mix of Cisco Unified Communications Manager versions.

- An Emergency Responder cluster can contain Emergency Responder groups that support different versions of Cisco Unified Communications Manager. In this way, Emergency Responder can support a mix of Cisco Unified Communications Manager versions in your telephony network.

The following figure shows an Emergency Responder Server Group.

Cisco Emergency Responder Server Group

Cisco Emergency Responder Clusters

An Emergency Responder cluster is a set of Emergency Responder server groups that share data to provide correct emergency call-handling capabilities. Emergency Responder cluster information is stored in a central location in the cluster called the cluster database. An Emergency Responder 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.

Emergency Responder uses two separate databases:

- A database that stores Emergency Responder configuration information.

- A database that stores Emergency Responder cluster information.

During installation, both databases are created on each Emergency Responder server. However, only one Emergency Responder server contains cluster data.

Note

You cannot deploy different versions of Emergency Responder in the same Emergency Responder group. If you are upgrading to the latest version of Emergency Responder, make sure to upgrade both Emergency Responder servers to the same version. If phones registered with Unified CM are configured with EnergyWise Power Save Plus mode, then all the Emergency Responder Server Groups in a cluster need to be Emergency Responder Release 8.6 or later because earlier versions of Emergency Responder do not support EnergyWise. Major discovery in Emergency Responder Release 8.6 or later does not purge phones that are in EnergyWise Power Save Plus mode.

The following figure shows how Cisco Emergency Responder (Emergency Responder) groups can be joined in a single Emergency Responder cluster.

Understanding the Relationship Between Cisco Emergency Responder Groups and Cisco Emergency Responder Clusters

In this example:

- There are two Cisco Unified Communications Manager clusters, Unified CM cluster A and Unified CM cluster B.

- Emergency Responder Server Group 1 and Emergency Responder Server Group 2 form a single Emergency Responder cluster.

- Emergency Responder Server Group 1 supports Unified CM cluster A and Emergency Responder Server Group 2 supports Unified CM cluster B.

- Cisco ER1 Publisher cluster database stores the Emergency Responder cluster information for both Emergency Responder server groups. Dotted lines show the Emergency Responder servers communications with the cluster database host.

- Each Emergency Responder server has a database containing the Emergency Responder configuration information.

Note

For Emergency Responder intra-cluster phone tracking to work accurately, a Emergency Responder 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 Emergency Responder servers.

Note

If you enter the system administrator email account in the System Administrator Mail ID field when you configure the Emergency Responder Server Group Settings, the system administrator receives an email notification when the standby server handles a call or when the standby server takes over for the primary server.

To complete the creation of the Emergency Responder cluster, you must navigate to the Cisco Unified CM and create inter-cluster trunks and route patterns to allow the Emergency Responder groups to hand off emergency calls between the groups and configure these route patterns in Emergency Responder.

Caution

Before you create a Emergency Responder cluster, be aware that the dial plans in all Cisco Unified Communications Manager clusters supported by the Emergency Responder cluster must be unique. For example, extension 2002 can only be defined in one Cisco Unified Communications Manager cluster. With overlapping dial plans, you must have separate Emergency Responder clusters and you cannot support dynamic phone movement between those Cisco Unified Communications Manager clusters.

Track Phone Movement Across a Cluster

The following scenario illustrates how Emergency Responder clusters work and how Emergency Responder responds to phones moving between clusters:

- Cisco ER Group A has a phone (ext 3003) that is moving out to Cisco ER Group B.

- Cisco ER Group A discovers 3003 in Cisco ER Group B.

- The Unlocated Phones page in Cisco ER Group A display the phone in Cisco ER Group B.

- Calls made from 3003 during this time are redirected to Cisco ER Group B and Cisco ER Group B takes the necessary steps to route this call.

- If both the Emergency Responder servers (Publisher and Subscriber) in Cisco ER Group B go down, Cisco ER Group A still displays 3003 in Cisco ER Group B.

- Calls made from 3003 receive default Treatment as configured on Cisco UCM Cluster B.

- If 3003 moves to Cisco ER Group C:

- It is discovered after the next incremental phone tracking on Cisco ER Group A and then in Cisco ER Group C.

- The Unlocated Phones page changes the association of 3003 to Cisco ER Group C.

- Calls made from 3003 during this time are redirected to Cisco ER Group C and Cisco ER Group C takes the necessary steps to route this call.

- If 3003 moves back to Cisco ER Group A:

- It is discovered in the next incremental phone tracking and displayed under the corresponding switch port or IP subnet.

- Calls made from 3003 during this time receive treatment from Cisco ER Group A.

Note

If you make an emergency call from a Cisco Unified IP Phone using a shared line, the call may terminate on an incorrect ERL across the cluster.

Note

Moving of phones discovered and associated with an ERL to a different Unified CM cluster, and tracked by a different Emergency Responder Server Group belonging to the same Emergency Responder cluster, requires the deletion of the ERLs association from the current Emergency Responder Server Group. See Step 7 of Identify Unlocated Phones to unassign an ERL from the current Emergency Responder Server Group.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Data Integrity and Reliability

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 provider's network. In the service provider's network, the routing is based on the ELIN, which is also used to look up the ALI for the caller. Your ERL configuration must be reliable so that the correct ELIN is assigned to the emergency call.

The following information will help you 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. 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 is used for the port, and the wrong ALI is sent to the PSAP.

This type of change does not normally result in an incorrectly routed call, because it is unlikely that a single LAN switch connects 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.

- With phones that Emergency Responder cannot automatically track, you ensure that any moves, adds, or changes to these phones also result in an update to the Emergency Responder configuration. See Manually Define Phones for information about defining these types of phones.

Note

If the switch port mapping changes, an email alert is sent.

- Before Emergency Responder 1.2, if registered phones were not located behind a switch port, Emergency Responder would list the phone in the Unlocated Phones page.

Emergency Responder 1.2 and later locates these phones as follows:

- If a registered phone is not located behind a switch port, it may be located 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, Emergency Responder lists the phone in the Unlocated Phones page.

To determine the ERL that Emergency Responder will use for call routing, use the ERL Debug Tool to search for the phone. The search yields the current ERL used in routing the emergency call from this phone and why Emergency Responder chose that ERL. For more information, see Emergency Responder Admin Utility.

- When you install Emergency Responder, 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  Emergency Responder 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. 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 Emergency Responder 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 Emergency Responder and clicking Locate Switch Ports. See LAN Switch Identification for more information.

Phones connected to undefined switches are listed as unlocated phones in Emergency Responder. If you changed a defined switch, new or changed ports become ports without an ERL association. You should assign ERLs for the new or changed switch ports. See Emergency Responder Network Administrator Role and Emergency Responder ERL Administrator Role for information about 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 Export ERL Information and Export ALI Information for Submission to Your Service Provider for more information.

Network Preparations

The information in the following topics describe the steps you should take to prepare your network before deploying Cisco Emergency Responder.

CAMA and PRI Trunks

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. You should consult with your service provider and decide on the type of connection that works best for you.

Consider these issues:

- PRI—If 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 that 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 that 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-party number rather than a generic number (such as the main number of the site). Otherwise, the PSAP does not receive the expected ELIN, and the emergency call might not be routed to the right PSAP.

- CAMA—CAMA trunks are dedicated to emergency calls, and are available in most areas. You do not need to do 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, with 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.

DID Service Provider Numbers

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 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. For example, if four people make emergency calls within an hour, and if the PSAP calls the ELIN, the PSAP connects to the last caller. This situation 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, Emergency Responder uses those ELINs in sequence until all are used, then reuses the ELINs in order. Emergency Responder maintains the link between the ELIN and the extension of the actual emergency caller for up to three hours.

Because you must 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 Emergency Responder can handle. Because Emergency Responder reuses the ELINs that 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.

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Switch and Phone Upgrades

The most powerful capability of Emergency Responder 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. By automatically tracking phones, you can reduce the cost of maintaining your telephone network, and simplify moves, adds, or changes.

However, Emergency Responder only can 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 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.

Preparing Your Staff for Emergency Responder

Emergency Responder does not replace your existing emergency procedures. Instead, Emergency Responder is a tool you can use to augment those procedures. Before deploying Emergency Responder, consider how it fits into your procedures and how you want to use the Emergency Responder system's capabilities.

These are the main things to consider when deciding how to use Emergency Responder:

- When someone makes an emergency call, Emergency Responder 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 helps them respond quickly to emergencies. Incorporating building names, floor numbers, and other readily understood location information in the name are the types of factors to consider.

- Emergency Responder lets you define three types of administrative user, so you can divide responsibilities for overall Emergency Responder 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 Emergency Responder 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 Data Integrity and Reliability for more information about maintaining data integrity.

Emergency Responder Deployment

The information in the following sections describe deployment models for various types of networks. You can use these examples as modules, combining them to form a larger, more complex network.

Deployment in Main Site and PSAP

To support a simple telephony network consisting of a single Cisco Unified Communications Manager cluster, install two Emergency Responder 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 provider's network, although capacity planning for your telephony network might require more than one gateway. Configure all route patterns to use this gateway.

The following figure shows how Emergency Responder fits into a simple telephony network with a single Cisco Unified Communications Manager cluster.

Deploying Cisco Emergency Responder in One Main Site with One PSAP

See these examples to extend this example to more complex networks:

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

Deployment in Main Site with Two or More PSAPs

The following figure illustrates the Emergency Responder configuration with 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 Two Main Site Deployments.

Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs

To support this type of network, install two Emergency Responder servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher.

Because there are two PSAPs serving the location, you probably need more than one gateway connecting to different parts of the service provider's network. However, this depends on the layout of the service provider's 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 that you need two gateways; 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 provider's 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, Emergency Responder 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:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

Deployment in Main Site with Satellite Offices

The following figure illustrates the Emergency Responder configuration with 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 Two Main Site Deployments.

Deploying Cisco Emergency Responder in One Main Site with Satellite Offices

Caution

In this configuration, if the WAN link between the offices goes down, the people in the satellite office cannot make emergency calls with Emergency Responder support. SRST in the satellite office can provide basic support for emergency calls in case of WAN failure.

To support this type of network, install two Emergency Responder 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. You probably need more than one gateway connecting to different parts of the service provider's network (you might have different service providers). However, this depends on the layout of the service provider's 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 that you need two gateways; 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 provider's network, configure all route patterns used in Columbus's ERLs to use gateway COL, and all route patterns used in Chillicothe's ERLs to use gateway CHIL. As phones move between sites, Emergency Responder 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. Emergency Responder must do SNMP queries of the remote site 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 Set Up SNMPv2 for more information.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

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 Emergency Responder in the main office.

Deployment in Main Site Serving Multiple Sites

The following figure illustrates the Emergency Responder configuration with two or more main sites that are served by two or more PSAPs with one Unified CM cluster per site.

Deploying Emergency Responder in One Main Site Serving Two or More Sites

To support this type of network, install two Emergency Responder servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher.

Because there are two PSAPs serving the location, you probably need more than one gateway connecting to different parts of the service provider's network. However, this configuration depends on the layout of the service provider's 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, assume that you need one gateway per site; 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 provider's network, configure all route patterns used in Site A ERLs and all route patterns used in Site B ERLs to use local site gateway. As phones move between buildings, Emergency Responder dynamically updates their ERLs so that emergency calls get routed out of the desired gateway.

In this example, Emergency Responder serves two Unified CM Clusters and facilitate the movement of phone between sites, it is required that route patterns for Site A ERLs and Site B ERLs are configured in both Site A and Site B Unified CM Clusters.

One Site Serving Multiple Sites with EMCC

Using Extension Mobility Cross Cluster (EMCC) between two Unified CM clusters enables Emergency Responder to provide enhanced support for 911 calls.

Figure 1 illustrates how the Emergency Responder is deployed at one site and serves two or more sites with the Unified CM in each site.

In this scenario, the Emergency Responder server is shared by the EMCC user's home cluster and the visiting Unified CM cluster. For Emergency Responder to process a 911 call made by an EMCC logged-in user, the home Unified CM cluster must not use an Adjunct Calling Search Space (CSS) to direct the 911 call to the user's visiting cluster.

The shared Emergency Responder servers supporting both the clusters process the 911 call in the user's home cluster.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Two Main Site Deployments

Two Main Site Deployments

The following figure illustrates the Emergency Responder configuration with two (or more) main sites, each served by a separate PSAP.

Deploying Cisco Emergency Responder in Two Main Sites

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 Deployment in Main Site with Satellite Offices for information about deploying Emergency Responder in those offices.

If a main site is served by more than one PSAP, see Deployment in Main Site with Two or More PSAPs for information about deploying Emergency Responder in that site. To support this type of network:

- Install two Emergency Responder 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 Emergency Responder Publisher server in the Chicago Emergency Responder group for use as the cluster database. See Set Up Emergency Responder Cluster and Cluster DB Host.

- Install two Emergency Responder 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 Emergency Responder Publisher server in the Chicago Emergency Responder group for use as the cluster database. See Set Up Emergency Responder Cluster and Cluster DB Host.

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 provider's network (you might have different service providers). Consult with your service provider to determine the requirements for your buildings. 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 provider's network, configure all route patterns used in Chicago's ERLs to use gateway CHI, and all route patterns used in New York's ERLs to use gateway NYC.

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-Emergency Responder group route pattern so that Emergency Responder can transfer calls between Cisco Unified Communications Manager clusters served by separate Emergency Responder groups.

As phones move between sites, Emergency Responder dynamically updates their ERLs so that emergency calls get routed out of the desired gateway. However, if the WAN link becomes unavailable, Emergency Responder cannot track phone movement between the sites.

Deployment in Two Main Sites with Clustering Over the WAN

The following figure illustrates the Emergency Responder configuration with two main sites using Clustering over the WAN (CoW).

Deploying Cisco Emergency Responder in Two Main Sites with Clustering Over the WAN

To support this type of network, install one Emergency Responder server in each site and configure one server as the publisher and the other server as a subscriber. The ER publisher should be co-located with the primary Unified CM CTI manager, and the ER subscriber should be co-located with the secondary Unified CM CTI manager.

Note the following constraints:

- At least 1.544 Mbps available bandwidth between ER publisher and ER subscriber (for data replication)

- No more than 80 msec RTT between any Unified CM server and either ER server

Support for CTI and JTAPI Over WAN

The following figure shows JTAPI over the WAN during routine or normal operations.

In this topology, the primary CTI manager is running on Unified CM subscriber at Site 1. Emergency calls from the Unified CM subscriber in Site 2 will reach the ER publisher in Site 1 via the primary CTI manager in Site 1, using CTI over the WAN.

JTAPI Over the WAN During Normal Operations

The following figure shows JTAPI over the WAN during fail over operations.

During Emergency Responder failover operation, emergency calls from Unified CM subscriber in Site 1 will reach the Emergency Responder subscriber in Site 2 via the primary CTI manager running on Unified CM subscriber at Site 1, using JTAPI over the WAN.

JTAPI Over the WAN During Failover Operations

In Emergency Responder failover, the ER subscriber registers with the primary CTI manager. In Emergency Responder fallback the Emergency Responder publisher reregisters with the primary CTI manager. Emergency Responder failover and fallback takes four to five minutes. The time may vary according to the number of CTI ports configured.

Both CTI over the WAN and JTAPI over the WAN support network latency up to a 80-msec round-trip.

Cluster Deployment in Two Main Sites with EMCC

Emergency Responder can provide enhanced support for 911 calls when using Extension Mobility Cross Cluster (EMCC) between two Unified CM clusters.

Figure 1 illustrates the Emergency Responder configuration with two (or more) main sites, each served by a separate PSAP.

In this scenario, the two clusters must be configured for EMCC. When a 911 call is made by an EMCC logged-in user, the call is offered to Emergency Responder group in the users home cluster.

Emergency Responder groups in the user's home cluster and visiting cluster form an Emergency Responder cluster. Emergency Responder group in home cluster redirects the call to visiting Emergency Responder group by using Inter-Cluster Trunk (ICT) between the two Unified CM clusters and the visiting Emergency Responder routes the call to appropriate PSAP.

Note

In this scenario, the Unified CM does not have adjunct CSS configured.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

Configure a Local Route Group in a Wide Area Network

With an Emergency Responder and Cisco Unified Communications Manager deployment that spans multiple locations over a wide area network (WAN), you may want to configure a Local Route Group (LRG) to ensure that users can make emergency calls if the connection between Emergency Responder and Cisco Unified Communications manager goes down.

While there is a communication failure between Emergency Responder and Cisco Unified Communications Manager, the following Emergency Responder features are not supported:

- Onsite alerts

- Web alerts

- Email alerts

- PSAP callback

- Device mobility

To support device mobility, you must configure device mobility in Cisco Unified Communications Manager to route the 911 call to the new LRG location when the phones are moved from one location to another.

To configure LRG, follow these steps:

Procedure

Step 1

On Cisco Unified Communications Manager Administration, configure the LRG route pattern and route point for 911 emergency call routing.

Step 2

On Cisco Unified Communications Manager Administration, configure any destination route point that is being forwarded in the emergency call route point with the LRG route pattern.

Step 3

On Emergency Responder Administration, configure the LRG route pattern as the default ERL.

Part II. Installation and Upgrade

Chapter 2. Cisco Emergency Responder Installation

Cisco Emergency Responder Installation Overview

Cisco Emergency Responder (Emergency Responder) is distributed on an installation DVD that contains everything that is required to install Emergency Responder, including the Cisco Unified Communications Operating System software.

You can upgrade to Emergency Responder Release 10.0 from Emergency Responder Release 7.1 or later. You cannot directly upgrade to Emergency Responder Release 10.0 from Emergency Responder Release 7.0 or earlier.

Hardware and Software Prerequisites

Cisco Emergency Responder requires specific hardware and software to run properly. Review the following sections before you proceed with an installation or upgrade:

- See the latest version of the Release Notes for Cisco Emergency Responder to verify that you have all the hardware and software, and in the supported versions, that you must install for Emergency Responder and to check that your Cisco Unified Communications Manager Appliance platform provides the Emergency Responder capabilities to meet your configuration needs. (You can also use equivalent Cisco-certified servers.)

- See the License Requirements section to make sure that you have all the required license keys available before you begin the installation process.

System Preparations

The Emergency Responder installation process installs both the platform software and the Emergency Responder software. During the installation, you are prompted to enter information needed by the system to complete the installation.

Note

We recommend that you perform the installation or upgrade during off-peak hours. The installation or upgrade procedure completely reformats the hard disk, so Emergency Responder is unavailable for the duration of the installation or upgrade.

Review the following information before you install Cisco Emergency Responder or upgrade your system to the latest version:

- Upgrading Emergency Responder

- Before you upgrade to the latest version of Emergency Responder, you must ensure that it is compatible with your existing version of Unified CM. You can use the Cisco Unified Communications Compatibility Tool to research this issue: Click Here

- You must upgrade Emergency Responder before you upgrade Unified CM. Only after you have installed the new version of Emergency Responder can you then upgrade Unified CM.

- After you have upgraded both Emergency Responder and Unified CM, you must then update the Unified CM Version on Emergency Responder.

- See Table 1 for the correct upgrade order and additional information about this subject.

- Emergency Responder Versions

- Different versions of Emergency Responder cannot be deployed in the same Emergency Responder group. The primary and the standby Emergency Responder servers must be running the same version of Emergency Responder. If you are upgrading to the most recent version of Emergency Responder, also make sure to upgrade both Emergency Responder servers.

Note

Emergency Responder supports interoperability between two server groups in a cluster running different versions of Emergency Responder. For example, one server group in a cluster may be running the most recent version of Emergency Responder while another server group in the cluster is running Emergency Responder 1.3, Emergency Responder 2.x, Emergency Responder 7.x, and Emergency Responder 8.0. However, Emergency Responder will not interoperate with versions earlier than Emergency Responder 1.3.

- Determine and list your Emergency Responder hostname and passwords.

- Decide on a permanent hostname, user interface administrator name and password for the Emergency Responder server before you install Emergency Responder. Changing the hostname of a Emergency Responder server after installation may cause problems.

- The hostname for the Emergency Responder Publisher and Subscriber must not contain the underscore character (_). If you have an existing Emergency Responder server with an underscore in its hostname, change the hostname of the server before installing Emergency Responder.

- The hostname for the Emergency Responder Publisher and Subscriber must not begin with a numeric value.

- Decide on a password for the Cisco Emergency Responder administrative user.

Note

The Emergency Responder administrative users 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 auto-negotiation of Ethernet NIC speed and duplex.

- If yes, you do not 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 do not need any additional information.

- If no, you need the hostname, IP address, IP mask, and gateway address to enter for the Static Network Configuration.

- NTP Client information

- The system prompts you 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 must enter the IP address or hostname of the servers.

- If you do not choose to use external NTP servers, you must enter the system date and time clock information manually.

Note

Use of NTP server is mandatory when installing Emergency Responder on UCS servers.

- Database Access Security password

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

- 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

- Review the latest Release Notes for Emergency Responder before installation:

Click Here

Perform the installation tasks in the order shown in this table.

Upgrading Tasks

Installation Task

For More Information

Upgrade Emergency Responder.

- Software Upgrades

Upgrade Unified CM.

- Click Here

- Click Here

- Change Cisco Unified Communications Manager Version

Update Unified CM Version.

Update Cisco Unified Communications Manager Version

Install the components for Emergency Responder in the order shown in this table.

Installation Tasks

Installation Task

For More Information

Install Cisco Unified Communications Manager.

Click Here

Install Emergency Responder as a new installation.

Installation on a New System

Installation and Migration on the Cisco UCS Server

The information in the following sections describe the changes for installation, upgrade, and migration of the Cisco Emergency Responder on the Cisco UCS Server.

System Requirements

To run Cisco Emergency Responder on the Cisco UCS Server, your system must meet the requirements listed in the following table.

System Requirements

System Parameter

System Parameter options

Supported Virtual Machine Configuration

See the documentation at

Click Here

IOPS per virtual machine (VM)

See the documentation at

Click Here

VMware version

ESXi 4.0 Update 1

Note:
Ensure that you use ESXi, rather than ESX, to run Cisco Emergency Responder on the Cisco UCS Server. However, the server can be part of a VMware vCenter that includes ESX hosts.

VMware—vMotion

No

Note:
Cisco does not support vMotion on a VM that is running. However, Cisco does support powering-down a VM, then rebooting the VM on a different rack server. This may be helpful if you want to put a rack server into maintenance mode.

VMware—Site Recovery Manager

Yes

VMware—High Availability

Yes

VMware—Data Recovery (VDR)

Yes

All other unlisted VMware features

Not supported

To operate Cisco Emergency Responder on the Cisco UCS Server successfully, you should have the experience and skills to manage a host server running VMware ESXi. If you do not have this experience and want to obtain the required information quickly, consider using VMware GO, a Web-based application that facilitates VMware.

Note

Even if you use VMware GO, you still must use the supported VMware configuration on Cisco Emergency Responder on the Cisco UCS Server, which are documented at both Click Here and Click Here .

Installation on Cisco UCS Server

This following sections describe how to perform a fresh installation of a Cisco Emergency Responder on the Cisco UCS server:

- Configuration Checklist for Installing and Configuring the Server

- Install Preparations

- Set Up RAID

- vSphere Client Installation

- Aligning the Datastore Used for VMs

- Create Virtual Machines

- Download Virtual Machine Templates (OVA Templates)

- Install Emergency Responder on VM

Configuration Checklist for Installing and Configuring the Server

The following procedure provides the major steps required to install and configure Cisco Emergency Responder on the Cisco UCS Server.

Procedure

Step 1

Prepare to install the server. For more information, see Install Preparations.

Step 2

Physically install and connect the server.

Step 3

Power on the server and configure Cisco Integrated Management Controller (CIMC) for remote management.

Step 4

If you purchased the UCS server separately, configure the RAID settings to the following specification:

- The first two drives are configured as a RAID 1 (mirrored) drive. This drive is for ESXi installation.

- The next four drives are configured as a RAID 5 drive. This drive is for VMs.
Note:
Number of drives may be different in different versions of UCS servers.

For more information, see Set Up RAID

Step 5

If you purchased the UCS server separately, configure the BIOS to the following specification:

- Disable Quiet Mode.

- Enable Enhanced SATA for CDROM access.

- Configure the following boot order:

- SATA5:Optiarc DVD first

- PCI Raid Adapter second

Step 6

Install and configure VMware EXSi on the smaller of the two available disks. For more information, see the VMware ESXi documentation.

Step 7

Install vSphere Client. For more information, see vSphere Client Installation and the vSphere Client documentation.

Step 8

Align the datastores for the VMs. For more information, see Aligning the Datastore Used for VMs.

Step 9

If you use 802.1q trunking, set the MTU size to 1472.

Step 10

Install and configure a virtual machine (VM). For more information, see Create Virtual Machines and Download Virtual Machine Templates (OVA Templates).

Step 11

Install Cisco Emergency Responder on the VM. For more information, see Install Emergency Responder on VM.

Install Preparations

This section describes how to prepare to install a Cisco Emergency Responder on the Cisco UCS server in a standalone configuration, which indicates that it is not in a data center.

Allocate the following resources before installation:

- Space in a rack to receive a 2-RU UCS server

- Ethernet ports on a switch close to the UCS server:

- One port for the CIMC

- Two ports for the LAN on motherboard (LOM) NICs

- An IP address for the CIMC management port

- An IP address for the virtual host. The UCS server's IP address and is used by ESXi.

- A hostname, and optionally configured DNS for the virtual host's hostname

- IP addresses for the VMs

Set Up RAID

If you purchased the UCS server separately, configure the RAID settings to the following specifications:

- The first two drives are configured as a RAID 1 (mirrored) drive. This drive is for ESXi installation.

- The next four drives are configured as a RAID 5 drive. This drive is for VMs.

Note

Number of drives may be different in different versions of UCS servers.

Procedure

Step 1

During server bootup, press Ctrl+Y to enter the preboot CLI.

Step 2

Enter the following commands to determine the current RAID configuration:
-ldinfo -l0 -a0

-ldinfo -l1 -a0

The required configuration is two drives in a RAID 1 array for logical drive 0, and four drives in a RAID 5 array for Logical drive 1. If the RAID configuration is wrong, continue with this procedure.

Note:
Do not continue with this procedure if RAID is configured correctly.

Step 3

Enter the command -cfgclr -a0 to clear the RAID configuration.
Caution:
Clearing the RAID configuration deletes all data on the hard drives.

Step 4

Enter the following commands to configure RAID:
-cfgldadd -r1 [252:0, 252:1] -a0

-cfgldadd -r5 [252:2, 252:3, 252:4, 252:5] -a0

If the hard drives did not have a RAID configuration previously, you are done configuring RAID. If the hard drives had a RAID configuration before, continue with this procedure.

Step 5

Enter the following commands to initialize the logical volumes:
- ldinit -start -full -l0 -a0 (l0 is the letter l and the number 0, not the number 10)

- ldinit -start -full -l1 -a0 (l1 is the letter l and the number 1, not the number 11)

These commands clear data on the drives and initialize the new array.

Step 6

Allow these commands to finish running before exiting the Preboot CLI. Enter the following commands
to display the progress of the commands:

-ldinit -showprog -l0 -a0

-ldinit -showprog -l1 -a0

When both commands report that no initialization is running, it is safe to quit the Preboot CLI.

Step 7

After configuring the two logical volumes, you can exit the Preboot CLI by entering q.

vSphere Client Installation

When the virtual host is available on the network, you can browse to its IP address to bring up a web-based interface. The vSphere Client is Windows-based, so the download and install must be performed from a Windows PC.

After the vSphere Client is installed, you can run it and log into the virtual host using the virtual host's name or IP address, the root login ID, and the password you configured.

You can join the host to a vCenter if you want to manage it through vCenter.

Aligning the Datastore Used for VMs

When you install VMware ESXi, the second logical volume is automatically imported unaligned. VMs have better disk performance when all partitions (physical, ESXi, and VM) start on the same boundary and you will have fewer incidents of disk blocks being fragmented across the different boundaries.

To ensure that the ESXi partition used for VMs are aligned, delete the unaligned datastore (the larger disk partition, which is 407 GB), then recreate the datastore using vSphere client.

Create Virtual Machines

Cisco provides a VM template for you to download and transfer to your virtual host. Use this template to create the VM for Cisco Emergency Responder on the Cisco UCS Server installation.

Before you deploy the template and create the VM, you should have a hostname and IP address allocated for the new VM.

To create a VM and prepare to install Cisco Emergency Responder on the Cisco UCS Server, follow these steps.

Procedure

Step 1

Download the VM template for your application.
See Download Virtual Machine Templates (OVA Templates) for more information.

Step 2

Upload the template to a datastore on the UCS server.
We recommend that you use the smaller datastore (with ESXi installed on it).

Step 3

Make this template available to the UCS server.

Step 4

Deploy the template file using vSphere Client. Enter the following information for the new VM:

- hostname

- datastore - Select a datastore that has enough resource.

Step 5

Complete creating the VM.
At this point a new VM is created with the correct amount of RAM, number of CPUs, size and number of disks for the intended application.

Step 6

Install Cisco Emergency Responder on the Cisco UCS Server on the VM.
See Install Emergency Responder on VM for more information.

Download Virtual Machine Templates (OVA Templates)

The configuration of a Cisco Emergency Responder virtual machine must match a supported virtual machine template.

To obtain the virtual machine template for Cisco Emergency Responder on the Cisco UCS Server, follow these steps:

Procedure

Step 1

Select this URL in your browser:
Click Here

Step 2

If your browser prompts you to do so, type your Cisco.com User Name and Password in the text boxes, then click the Log In button.

Step 3

Select the desired version of Cisco Emergency Responder.

Step 4

Click the Emergency Responder Virtual Machine Templates link.

Step 5

Move your mouse over the filename and click the Readme link to view the virtual machine template's release information.

Step 6

Click the Download Now button. Follow the prompts and provide the required information to download the software.

Install Emergency Responder on VM

Procedure

Step 1

In vSphere Client, edit the VM to force entry into BIOS setup the next time the VM reboots.

Step 2

Make the Emergency Responder installation media available to the VM DVD-ROM drive.

Step 3

Power on the VM, then in BIOS setup, promote CD ROM to boot before the hard drive.

Step 4

Complete booting the VM.
The Cisco Emergency Responder installation program starts. For information about performing the installation, see the Installing Cisco Emergency Responder document.

Virtual Machine Configurations

With the virtual machine configuration for running Cisco Emergency Responder on the Cisco UCS Server, the VMware server must match the specifications described in the System Requirements to be supported by Cisco.

While Cisco Emergency Responder can be installed and licensed in other virtual machine configurations, Cisco does not support these configurations.

Migrate to Emergency Responder on Cisco UCS Server

Migrating from a Media Convergence Server (MCS server) to a Cisco Emergency Responder on the Cisco UCS Server follows a procedure that is very similar to replacing server hardware.

The following procedure outlines the migration process and references to other pertinent documentation.

Procedure

Step 1

Upgrade the MCS server to the most recent version of Cisco Emergency Responder.

Step 2

If the Emergency Responder VM uses a different IP address from the MCS server, change the IP address of the MCS server to the value used by the Emergency Responder VM.

Note:   The hostname on the Emergency Responder VM must remain the same as that on the MCS Server.

Step 3

Perform a DRS backup on the MCS server.

Step 4

Create the virtual machine (VM) on the Cisco UCS server used as the replacement for the MCS node. For more information, see Installation on Cisco UCS Server.

Step 5

Install the new version of Cisco Emergency Responder on the Cisco UCS server. For more information, see Installation on Cisco UCS Server.

Step 6

Perform a DRS restore to restore the data backed up from the MCS server to the Cisco UCS server.

Step 7

Upload the new licenses to the Cisco Emergency Responder on the Cisco UCS server.

VMWare Support

Consider the following, when using Cisco Emergency Responder on the Cisco UCS Server:

- Install, upgrade, and recovery procedures now use "soft media" such as ISO or FLP (virtual floppy) if the server does not have a DVD drive.

- USB tape backup is not supported.

- NIC teaming is configured at the VMware virtual switch.

- Hardware SNMP and syslog move to VMware and UCS Manager.

- Install logs are written only to the virtual serial port.

- Unattended installs use virtual floppy instead of USB.

- Basic UPS Integration is not supported.

- Boot order is controlled by the BIOS of the VMware VM.

- Hardware BIOS, firmware, and drivers must be the required level and configured for compatibility with Cisco Emergency Responder supported VMware product and version.

Note

Install logs require a empty tmp file to be attached on the serial port before dumping the logs. During boot-up of Linux, a few garbage characters (terminal escape sequences) are outputted to the serial port, which may corrupt the tar format of the file.

For more information about the UCS C-series server, go to the following URL:

Click Here

To view the list of product installation and configuration guides for Cisco UCS C-Series Integrated Management Controller, go to the following URL:

Click Here

To view the list of product installation and configuration guides for Cisco UCS Manager, go to following URL:

Click Here

Emergency Responder Daily Operations on Cisco UCS Server

Daily operations for Cisco Emergency Responder on the Cisco UCS Server software applications are identical to when the application is installed on an MCS server.

There are some differences in hardware management and monitoring because Cisco Emergency Responder on the Cisco UCS Server operates in a virtual environment.

Hardware Monitoring From the VM

Applications running in a VM have no ability to monitor the physical hardware. Hardware monitoring must be done from the CIMC, ESXi plugins, vCenter, or by physical inspection (for example, for flashing LEDs.).

Hardware Monitoring From CIMC

The CIMC provides the following hardware monitoring:

- An overview of CPU, memory, and power supply health

- An overview of hardware inventory, including CPUs, memory, power supplies, and storage

- Monitoring of sensors for power supplies, fans, temperature, and voltage

- A system event log that contains BIOS and sensor entries

Hardware Monitoring From VSphere Client and VCenter

The vSphere Client provides the following monitoring features:

- When you are logged in to vCenter, the vSphere Client displays hardware and system alarms defined on the Alarms tab.

- VM resource usage is displayed on the Virtual Machines tab and on the Performance tab for each VM.

- Host performance and resource usage is displayed on the Performance tab for the Host.

- When ESXi is used standalone (without vCenter), hardware status and resource usage are available, but alarming is not possible.

Related Documentation

The UCS RAID Controller SMI-S Reference Guide, which describes Storage Management Initiative Specification (SMI-S) support in the Cisco UCS Servers, is available at the following URL:

Click Here

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Install Emergency Responder Publisher

To install Emergency Responder, you install the Publisher (primary) first, then you install the Subscriber (backup) on a separate server. You must install Emergency Responder on separate servers from Cisco Unified Communications Manager or any Cisco Unified Communications applications.

Allow approximately 1 hour to perform a new installation.

- Insert the Emergency Responder Installation DVD.
If the system finds the DVD, you are asked if you want to perform a media check before installation to determine if there are problems with the DVD. The system displays the checksum of the DVD and instructs you to verify this checksum on the Emergency Responder 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.

- The Cisco Emergency Responder system installer starts. The Product Deployment Selection screen displays a message saying the Cisco Emergency Responder product suite is installing. Click OK to continue.

- The Proceed with Install page displays the current software version on the hard drive 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.

- On the Platform Configuration Wizard page, click Proceed to continue with the platform installation.
If you click Skip, the system installs both the platform and Emergency Responder software without prompting you to provide information during the installation. After the installation is completed and the system reboots, you are prompted to enter the required configuration details.

Note

For version 8.6 and earlier, the Cisco Emergency Responder Subscriber may fail to install with unrecoverable internal error indicated in the logs. If this happens, do a Skip install by skipping the configurations step initially, proceed with the installation, and then key in the configuration details when prompted at the end of the procedure.

- Click Continue to proceed. The Timezone Configuration page appears.

- Choose the correct time zone 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 time zone from the list

- After selecting the correct time zone, click OK. The Auto Negotiation Configuration page appears.

- 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:

1. Select the NIC Speed. The available options are 10 Megabit, 100 Megabit, or 1000 Megabit.

2. Select the NIC Duplex setting. The available options are Full or Half.

3. Click OK. The DHCP Configuration page appears.

- On the MTU Configuration page, you can set the maximum transmission unit (MTU) that can be sent in a network as follows:

- Click Yes if you want to configure a a MTU value of less than 1500 bytes.

- Click No to use the default MTU value of 1500 bytes.

- 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 about the Static Network Configuration page:

- Host Name

- IP Address

- IP Mask

- Gateway (GW) Address

Click OK. The DNS Client Configuration page appears.

- 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 about 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.

- 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.

- 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.
When you have finished, click OK. The Certificate Information page appears.

- Enter the following information about the Certificate Information page:

- Organization

- Unit

- Location

- State

- Country (select from the scroll-down menu).

Click OK. The Publisher Configuration page appears.

- 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. This server must also 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 Install Emergency Responder Subscriber for information about installing the Subscriber.

- On the Network Time Protocol Client Configuration page, you are asked if you want to set up external Network Time Protocol (NTP) servers.

Note

We strongly recommend that you use external NTP servers to ensure that the system time is kept accurate.

Caution

For Emergency Responder install on UCS servers, it is mandatory to configure NTP server.

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 appears. 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 finish entering this information, click OK. The Database Access Security Configuration page appears.

- On the Database Access Security Configuration page, enter the security password and then confirm the password in the fields provided.

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 Emergency Responder server groups when performing the installation or upgrade, DRS backup or restore, and "Point to a new Publisher" operations.

Click Help to display guidelines. When you finish, click OK. The SMTP Host Configuration page appears.

- 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.

- On the Platform Configuration Confirmation page, do one of the following:

- Select OK to save the platform configuration information and continue with the installation. The Cisco Emergency Responder Configuration page appears.

Note

After you select OK, you cannot 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.

- On the Cisco Emergency Responder Configuration page, do the following:

- 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 and then select OK.

- On the Security End User Language Selection page, choose a language for the Cisco Emergency Responder web pages. The system defaults to the English language.
The Application User Password Configuration page appears.

- On the Application User Configuration page, enter the username and password. This username and password is associated with the default administrative account and is used to log in to the Emergency Responder Administration web page. Click Help for guidelines.
When you are finished, click OK. The Cisco Emergency Responder Configuration Confirmation page appears.

- 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

After you select OK, you can not 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 Emergency Responder Application User Configuration page.

- Select Cancel to cancel the installation.

- After the system reboots, it checks the status of various system components. If the system finds any problems, you are prompted to correct the problem.
If the system does not find any problems, the installation process continues. The system ejects the installation DVD, reboot, and then finishes the installation. When the installation is complete, a CLI prompt appears.

Note

During this process, the system displays the MAC address of the Publisher. Write down the MAC address when it displays; you use the MAC address later to acquire Emergency Responder licenses. If you are not able to capture the MAC address during installation, you can look it up later. See the Server Licenses section for information about looking up the server MAC address.

- To bring up the Emergency Responder websites, go to any Windows system on the network, start a supported web browser, and enter the following URL:
http://your Emergency Responder hostname/

or

http://your Emergency Responder IP address/

Note

Make sure that the Emergency Responder is configured with DNS so that hostname is resolved to the IP address.

Install Emergency Responder Subscriber

You must install Subscriber only after you have installed the Publisher. You must install the Subscriber on a separate server from the Emergency Responder Publisher.

Caution

You must complete the installation of the Publisher, which includes a system reboot, before you start to install the Subscriber.

Procedure

Step 1

On the Publisher server, add the details about the Subscriber server by doing the following:

1. Log in the Publisher Emergency Responder Administration website.

2. Select System > Add Subscriber. The Add Server page appears.

3. Enter the hostname of the new Subscriber and click Insert. The Add Subscriber page appears again.

4. In the Configured Servers list, check that the hostname and IP address of the new Subscriber is listed.

Step 2

Follow Steps 1 through 15 in the Installation on a New System section. After you complete Step 15, the Publisher Configuration page appears.

Step 3

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 Publisher 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.

Step 4

The Network Connectivity Test Configuration page appears. The system attempts to verify system connectivity. Click No to continue the installation.

Step 5

The Publisher Access Configuration page appears. Enter the following:

- Publisher hostname

- Publisher IP address

- Publisher Database/Security password

Step 6

Verify that the Publisher information is correct and click OK.

Step 7

The SMTP Host Configuration page appears. Choose Yes if you want to configure the SMTP Host.

Step 8

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 Emergency Responder Subscriber begins and takes an additional 20 to 30 minutes to complete.

Step 9

When the installation completes, go to the Emergency Responder 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" appears. This message indicates that the Subscriber was installed successfully.
Note:
If the Subscriber installation cannot validate the Publisher, See Cannot Validate Publisher in the Troubleshooting chapter.

Emergency Responder Upgrade

To upgrade from version 7.1(1) or a later version of Cisco Emergency Responder to the most recent version of Emergency Responder, use the Cisco Unified OS Administration web interface. See Software Upgrades section for information about performing upgrades.

To upgrade from Emergency Responder version 7.0 to the most recent version of Emergency Responder, you must first complete an upgrade to Emergency Responder Release 7.1, using the software upgrade available for download from Cisco.com. See "Performing Software Upgrades" section of the Cisco Emergency Responder Administration Guide for Emergency Responder 7.1 for information about performing direct upgrades to Emergency Responder Release 7.1.

Part III. Configuration

Chapter 3. Configure Cisco Unified Communications Manager

Configure Cisco Unified Communications Manager Overview

This chapter describes procedures for configuring Cisco Unified Communications Manager (Unified CM) for Cisco Emergency Responder (Emergency Responder).

See the Release Notes for Unified CM versions that are compatible with Cisco Emergency Responder.

The procedures describe what you must configure in Unified CM so that Emergency Responder can work in your telephone network.

They also describe a sample Unified CM setup. The names that are chosen (for example, partition and calling search space names) are not required.

Sections with examples 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 work with the following calling search spaces and partitions:

- PhoneCSS - Includes the Phones partition.

- E911CSS - Includes the E911 and Phones partitions.

The examples are based on a single Unified CM 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 Unified CM cluster to which the gateway sends incoming calls from the public safety answering point (PSAP).

Set Up Phone Route Plans

Before configuring Emergency Responder, you must ensure that the phones that might be used to make emergency calls (typically all phones) are added and registered with Unified CM. See the documentation and online help included with Unified CM if you need assistance.

The following sections provide an example setup for your network before adding Emergency Responder.

Create Phone Partition

If you have not already created a partition for the phones, do so now.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description.

Step 4

Click Insert to add the new partition.

Create Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one.

Procedure

Step 1

Select Route Plan > Calling Search Space in Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.

Step 4

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.

Step 5

Click Insert to add the new calling search space.

Assign Partition and Calling Search Space to Phones

You can use the Bulk Administration Tool 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.

After you have created the Phones partition (Create Phone Partition) and PhonesCSS calling search space (Create Phone Calling Search Space), configure the phones to use them.

Procedure

Step 1

Select Device > Phone.
Unified CM displays the Find and List Phones page.

Step 2

Select Device name is not empty in the search fields and click Find.
Unified CM lists all of the phones in the bottom frame.

Step 3

Click the phone with the configuration that you want to change.
Unified CM displays the Phone Configuration page.

Step 4

Change the calling search space to PhoneCSS and click Update.

Step 5

Click the line number that you want to configure in the left-hand column.
Unified CM displays the Directory Number Configuration page.

Step 6

Change the partition to Phones, and the calling search space to PhoneCSS.

Step 7

Click Insert to save your changes.

Set Up Cisco Unified Communications Manager for Emergency Responder

To handle emergency calls, you must configure the emergency call numbers (such as 911) so that Cisco Emergency Responder (Emergency Responder) intercepts them. Emergency Responder 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.

The following topics describe how to define the Cisco Unified Communications Manager (Unified CM) elements required for Emergency Responder.

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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.

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

Create Required CTI Ports

Emergency Responder 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 that you configure is the number of simultaneous calls Emergency Responder can make to these personnel. It does not relate to the number of emergency calls Emergency Responder can handle or forward to the PSAP. There is no configurable limitation to the number of simultaneous emergency calls that Emergency Responder can handle.

Before You Begin
Emergency Responder 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.

Procedure

Step 1

Select Device > Phone.
Unified CM opens the Find and List Phones page.

Step 2

Click Add a New Phone.
Unified CM opens the Add a New Phone page.

Step 3

Select CTI Port for Phone Type and click Next.
Unified CM opens the Phone Configuration page.

Step 4

Configure the CTI Port, entering this information:

- Device Name- Enter something meaningful to you, for example, CTI3001.

- Device Pool- Select an appropriate device pool. This device pool must use the G.711 region.

- Calling Search Space- Select PhoneCSS.

Step 5

Click Insert.
Unified CM creates the CTI port and asks if you want to configure line 1. Click OK. Unified CM opens the Directory Number Configuration page.

Step 6

Configure line 1 for the CTI port, entering this information:

- Partition- Select Phones.

- Calling Search Space- Select 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.
Unified CM 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.

Create a Cisco Unified Communications Manager Group for Cisco Emergency Responder

A Cisco Unified Communications Manager (Unified CM) Group is a list of up to three Unified CMs that are assigned to a device pool to assist with call processing. The first Unified CM in the list acts as the primary Unified CM for the Group and the other members act as secondary and tertiary or backup Unified CMs. By creating a Unified CM Group, you can balance the call process load across multiple Unified CMs and ensure a level of redundancy for your network.

Because each device pool has one Unified CM Group assigned to it, a Unified CM Group improves your load distribution across a device pool. When a device registers, it attempts to connect to the primary Unified CM in the Unified CM Group. If the primary Unified CM is not available, the device tries to connect with the secondary Unified CM. If the secondary Unified CM is not available, the device tries to connect to the tertiary Unified CM.

You must create a Unified CM Group for Emergency Responder.

Note

The primary Cisco Unified CM in the Group assigned to the device pool for Cisco ER must also be the primary CTI Manager for Cisco Emergency Responder. The Group must also contain the secondary CTI manager for Cisco ER.

Procedure

Step 1

Select System > Unified CM Group.
The Find and List Unified CM Groups page opens.

Step 2

Click Add New.
The Unified CM Group Configuration page opens.

Step 3

Enter the following information in the appropriate field:

- Name – Enter a CM Group name that is meaningful to you; for example, Cisco Emergency Responder CM Group.

- Auto-registration Cisco Unified Communications Manager Group - Do not check this box for the Unified CM Group for Emergency Responder.

- Cisco Unified Communications Managers – Add the primary and secondary CTI Manager for Emergency Responder to the list of Selected Cisco Unified Communications Managers by selecting each from the Available Cisco Unified Communications Managers and clicking the Down Arrow.

Step 4

Click Save.

Error and System Messages

Unified CM generates several alarms to assist you in troubleshooting Emergency Responder problems. You should set up notification of Emergency Responder events so that an email notification alerts you to such important events.

The following table shows the relevant alarms.

Relevant Unified CM Alarms

Relevant Alarms

Alarm Level

Explanation

Recommended Action

CtiProviderOpened

Informational

Application opened the provider successfully.

This alarm is for informational purposes only; no action is required.

CtiProviderClosed

Informational

Application closed the provider.

Verify that Cisco Emergency Responder is up and running, verify network connectivity between application server and Unified CM, and verify the CPU utilization is in the safe range for the application server and Unified CM.

ApplicationConnectionDropped

Warning

TCP or TLS connection between CTIManager and Application is disconnected.

Verify that Cisco Emergency Responder is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for the application server and Unified CM.

CtiIncompatibleProtocolVersion

Warning

The Cisco Emergency Responder version or its Unified Communications Manager setting is not compatible with this version of CTIManager.

Verify that the correct version of the Cisco Emergency Responder is being used and its Unified CM version setting is correct. See Change Cisco Unified Communications Manager Version to view and update the Unified CM version.

By default, only Error events are posted to the event log. You should modify the event level to post warnings and set up a customer alert if the Emergency Responder user closes its applications or ports.

To do this, navigate to the Serviceability Web Page by selecting Alarm >Configuration>Server>Service Group (CM Services)>Service (Cisco CTI Manager). Change the Alarm Event Level to Error to have all of the last three alarms in the above table posted to SysLog.

These alarms are systemwide alarms and not specific to Emergency Responder. So any CTI application that triggers a warning message will post to the event log and not only Emergency Responder. You should set up notification of Unified CM events relevant to Emergency Responder so that if the provider goes out of service, an email or other notification event will alert you.

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Create 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. Emergency Responder 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 Create Emergency Call Route Points.

Before You Begin
Ensure that you have a list of all the DIDs you are using for ELINs.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The 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.

- Partition - Select E911.

- Numbering Plan- Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select 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.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Create 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 eliminates the secondary dialtone timing.

Create translation patterns so that when users dial the local system external access code of 9 plus 911, the calls are directed to the single 911 pattern previously created in the Create Emergency Call Route Points.

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.

The following table provides translation patterns for external access code of 9.

Translation Patterns for External Access Code of 9

Translation Pattern

911

9.911

Partition

Phones

Phones

Calling Search Space

E911CSS

E911CSS

Route Option

Route this pattern

Route this pattern

Provide outside dial tone

Check this box

Check this box

Called Party Transformations, Discard Digits (Outgoing Calls)

None

PreDot

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - 911.

- Partition - Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Make sure that this box is checked.

- Called Party Transformations, Discard Digits - Select <none>.

Step 4

Click Insert.
Unified CM saves the translation pattern.

Step 5

Repeat Step 2 to Step 4 with the following changes:

- Translation Pattern—9.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 1 provides emergency call route points for 9.911.

Note:
These route points are similar to the route points that you created in the Create Emergency Call Route Points. In this case, you enter E911 for the partition instead of Phones.

Emergency Call Route Points for 9.911

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder 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

911

912

913XXXXXXXXXX

Partition

E911

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Note:
Configuring call-forwarding numbers for the standby server ensures that calls are either routed to the PSAP servicing the default ERL or to 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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Create Route Points for 9.911

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. Table 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 1.

Step 4

Click Insert to add the new CTI route point.

- Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

- Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line that you are creating using the information in Table 1.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in Table 1 are configured.

For additional assistance, see the documentation and online help included with Unified CM.

Create 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.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The number you want to support as an emergency number. In this example, 9.911.

- Partition - Select Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Select this.

- Called Party Transformations, Discard Digits (Outgoing Calls) - Select PreDot.

Step 4

Click Insert.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Set Up Calling Search Space for Gateway and PSAP Connection

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 about setting up the gateway, and the Unified CM 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.

Procedure

Step 1

Select Device > Gateway.
Unified CM opens the Find and List Gateways page.

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.
Unified CM lists the gateways that match your criteria.

Step 3

Click the gateway you want to configure.
Unified CM opens the Gateway Configuration page.

Step 4

Select E911CSS for Calling Search Space.

Step 5

Click Update.
Unified CM saves your changes.

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Emergency Responder group in an Emergency Responder cluster, you must configure route patterns to enable each Emergency Responder group to route emergency calls to another Emergency Responder group if a caller's phone homes to a Unified CM cluster outside the current location of the phone. See Cisco Emergency Responder Clusters for a detailed explanation of how Emergency Responder groups communicate within a Emergency Responder cluster.

This procedure explains how to create the route pattern for one Emergency Responder group. The Inter-Cisco ER Group Route Pattern defined on a Emergency Responder Group is a route pattern for incoming Emergency Calls. Consider the network setup in the following figure.

For inter-group communications to work:

- You must define inter-cluster trunks in each Unified CM cluster to enable communications between the Unified CM clusters. See the Unified CM documentation for information about creating these types of gateways.

- Define the route pattern on the Unified CM

- Define route pattern 2000.911 and 3000.911 in CUCM cluster A.

- Define Route Pattern 1000.911 and 3000.911 in CUCM cluster B.

- Define Route Pattern 1000.911 and 2000.911 in CUCM cluster C.

- Define Inter-Emergency Responder Group Route Pattern

- In Emergency Responder Group A, define 1000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group B, define 2000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group C, define 3000.911 as the Inter Emergency Responder Group Route Pattern.

These definitions allow a call in an ERL managed by Emergency Responder Group B to be routed to Emergency Responder Group B even though the phone homes to Unified CM cluster A, which is serviced by Emergency Responder Group A.

Understanding Inter-Cisco Emergency Responder Group Route Patterns

Create Route Patterns on Unified CM

Before You Begin
The dial plans must be unique between all Unified CM clusters supported by a Emergency Responder cluster. For example, in the network shown in Create Route Patterns for Inter-Cisco Emergency Responder Group Communications, the extension 3003 can only be defined in Unified CM cluster CUCM-A.

Procedure

Step 1

Go to Cisco Unified CM Administration. Select Call Routing > Route/Hunt > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add New.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern— A pattern that you can transform to the emergency call number, typically a number, a decimal point, and the emergency call number. For example, 1000.911 or 2000.911. The pattern can only consist of numbers and decimal points.

- Partition — Select E911.

- Numbering Plan — Select the numbering plan for your area.

- Gateway/Route List — Select the inter-cluster trunk gateway to use for connecting to the Unified CM cluster supported by the Emergency Responder group whose inter-Emergency Responder group route pattern you are defining.

- Route Option — Select Route this pattern.

- Called Party Transformations: Discard Digits — Select 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. Unified CM saves the route pattern. To add additional route patterns, return to Step 2.

Note

Ensure that you define the route pattern in all other Unified CM clusters serviced by Emergency Responder groups other than the Emergency Responder group whose Inter-Emergency Responder group route pattern you are defining.

Note

For emergency calls to work across Emergency Responder Server Groups in a Emergency Responder cluster with Unified CM 8.5 or later, the Calling Party Selection option should be set to Originator in the Device> Trunk Configuration page in Unified CM Administration website.

Create an Inter-Emergency Responder Group Route Pattern

Note

Ensure you define the Inter-Emergency Responder Route pattern in all other Cisco Emergency Responder groups.

Procedure

Step 1

Go to Cisco Emergency Responder Administration. Select System > Telephony Settings.

Step 2

Add the Inter-Emergency Responder Route pattern.

Step 3

Update Settings.

Create Emergency Responder Cisco Unified Communications Manager User

You must add Emergency Responder as a Unified CM user. The settings you enter here are used when you configure the Unified CM settings for Emergency Responder.

Procedure

Step 1

In Unified CM, select User Management > Application User. Click the Add New button.
Unified CM displays the Application User Configuration page.

Step 2

Complete the following required fields:

- UserID—Use a descriptive name such as "Emergency_Responder_User."

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

In the Device Information section, select the desired route points and CTI ports and then click the down arrow to add the selected devices to the user control list. The list of devices appears in the Controlled Devices area.

Step 4

Select the following devices:
Note:
You may need to use Find Phones or Find Route Points to select the desired devices.

- All CTI ports created for Cisco Emergency Responder use. For more information, see "Creating the Required CTI Ports" section.

- The primary emergency call number, for example, 911.

- The backup emergency call number, for example, 912.

- The route point used for ELINs, for example, 913XXXXXXXXXX.

Step 5

Click Save.

Step 6

In the Unified CM menu at the top, click User Management > User Group.
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.

Step 8

Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page.

Step 9

Click Add Application Users to Group.
The Find and List Application Users popup window appears.

Step 10

Enter the User ID and click Find.
The list of Applications users appears.

Step 11

Check the check box next to the user ID and click Add Selected.
Unified CM adds the selected user to the Standard CTI Allow Calling Number Modification user group.

Step 12

Choose 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.

Step 14

Click the Standard CTI Enabled group.
Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.

Chapter 4. Configure Cisco Emergency Responder

Cisco Emergency Responder Configuration Overview

After you install Cisco Emergency Responder (Emergency Responder) and configure Cisco Unified Communications Manager (Unified CM), you can configure Emergency Responder so that it begins managing emergency calls.

Configuration Overview

Emergency Responder provides several features, including expanded administrative website interfaces, role-based user management, and upload and download utilities.

Note

Emergency Responder is compatible with Cisco EnergyWise, including provisions to detect user activity on powered-down phones.

Website Interfaces

Emergency Responder provides several web sites from which you can access and use different parts of the system. From the main Emergency Responder web page, you can access the following areas:

- Emergency Responder Serviceability

- Emergency Responder Administration (default home)

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

Each of these web sites allows a user access to different parts of the system and requires a separate login and password. Access to these web sites is controlled through the role-based user management mechanism (for more information, see Role-Based User Management).

When the Emergency Responder system is first installed, a default Emergency Responder Administrator user is created. The default Administrator has full access to all web sites except the Cisco Unified OS Administration and Disaster Recovery System websites, and can create users, roles, and user groups. The default Administrator cannot be deleted from the system.

Role-Based User Management

Emergency Responder uses a role-based user management mechanism. The information in the following topics describe this mechanism.

User Management

On installation, the system creates one default user, Emergency Responder Administrator. The Emergency Responder Administrator has access to all system administration screens except the Platform Administration and Disaster Recovery System screens. By default, the Emergency Responder Administrator user is assigned to the Emergency Responder System Administrator, Emergency Responder Serviceability, Emergency Responder Admin Utility, and Emergency Responder User user groups and has access to the resources defined for the Emergency Responder System Admin, Emergency Responder Serviceability, Emergency Responder Admin Utility, and Emergency Responder User roles.

Note

The default Emergency Responder Administrator user cannot be deleted.

You can add additional users. After 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.

Role Management

On installation, the system creates six default roles. The following table lists and describes the default roles.

Note

Default roles cannot be deleted.

Default Roles

Role

Description

Emergency Responder System Admin

Has access to all system administration screens.

Emergency Responder Serviceability

Has access to all serviceability screens.

Emergency Responder Admin Utility

Has access to all Admin Utility screens.

Emergency Responder Network Admin

Has access to Cisco Unified Communications Manager, LAN switch, and SNMP settings screens.

Emergency Responder ERL Admin

Has access to all ERL-related screens.

Emergency Responder User

Has access to the user screens.

When creating a new role or modifying an existing role, you specify which system resources are assigned to the role. A resource is the same thing as a web page or a menu item within the Emergency Responder administration website. For example, the Find and List Roles web page is a resource, as is the User Management > Role menu item.

The following table 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 Emergency Responder Serviceability website is one resource but it contains many submenus.

Resources Assigned to Default Roles

Resource

Emergency Responder System Admin

Emergency Responder Network Admin

Emergency Responder ERL Admin

Emergency Responder Serviceability

Emergency Responder Admin Utility

Emergency Responder User

Add Subscriber

x

Admin Utility

x

ALI Formatting Tool

x

All Logs

x

Application User

x

Call History

x

Unified CM Details

x

x

Emergency Responder Groups in Cluster

x

Change Unified CM Version

x

Cluster DBHost Setting

x

Control Center

x

CPU and Memory Usage

x

Device SNMP Settings

x

x

Disk Usage

x

ERL

x

x

ERL Audit Trail

x

ERL Debug Tool

x

ERL Migration

x

x

Event Viewer

x

File Management Utility

x

Functional role

x

Intrado ERL

x

x

Intrado VUI Settings

x

IP subnet

x

x

License Management

x

Mail Alert Configurations

x

Manually Configured Phones

x

x

MIB2 System Group Configuration

x

Off-Premises ERL

x

x

Onsite Contact

x

x

Pager Alert Configurations

x

x

Phone Search

x

Point to New Publisher

x

Processes

x

PS ALI Convert

x

PS ALI Export

x

Purge

x

Run Tracking

x

x

Tracking Schedule

x

x

Server

x

Server Group

x

LAN Switches

x

x

SNMP V1/V3c Configuration

x

SNMP V3 Configuration

x

Switch Port

x

x

Synthetic Phone

x

x

Telephony

x

Unlocated Phones

x

x

User Call History

x

User Group

x

Web Alert

x

User Group Management

On installation, the system creates six default user groups. The following table lists and describes the default user groups.

Note

Default user groups cannot be deleted.

Default User Groups

User Group

Description

Emergency Responder System Administrator

Assigned System Administration roles

Emergency Responder Network Administrator

Assigned Network Administration role

Emergency Responder ERL Administrator

Assigned ERL Administration role

Emergency Responder Serviceability

Assigned Serviceability role

Emergency Responder Admin Utility

Assigned Admin Utility role

Emergency Responder User

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 have access to all the resources defined by the roles assigned to the group.

Upload and Download Utilities

Emergency Responder includes download and upload utilities that allow you to transfer bulk data in the form of csv files from a Emergency Responder server to a local system (download) and from a local system to a Emergency Responder 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 Emergency Responder server, and import the data in the csv file into the Emergency Responder database.

The following table lists the Emergency Responder 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.

Administrative Web Pages Containing the Upload and Download Utilities

Page Name

Navigation Path

Find Conventional ERL Data

ERL > Conventional ERL

Find Off-Premises ERL Data

ERL >Off-premises ERL>Off-premises ERL(Search and List)

Find Intrado ERLs Data

ERL > Intrado ERL>Intrado ERL (Search and List)

LAN Switch Details

Phone Tracking > LAN Switch Details

Switch Port Details

ERL Membership > Switch Ports

Find and List IP subnets

ERL Membership > IP subnets

Find and List Manually Configured Phones

ERL Membership > Manually Configured Phones

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

Set Up Users and Groups

The following procedure provides information about the tasks that must be completed to set up Emergency Responder users and groups. This task can be completed by a System Administrator.

- Create the users your organization requires for Emergency Responder administration.

- Create the Emergency Responder group.

- Set up the Emergency Responder group telephony settings.

- Update Emergency Responder servers to the Emergency Responder group.

- Upload the product license key.

- Identify and configure the Unified CM clusters whose emergency calls this Emergency Responder group handles.

Note

The network administrator can also perform this step.

- Understand recurring system administration tasks.

- If you use Intrado V9-1-1 for Enterprise Service, configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

- If you support off-premise users, configure AXL authentication information with Unified CM.

Set Up Switch Connection

The following procedure provides information about the tasks that must be completed to set up Emergency Responder switch connection. This task can be completed by a Network Administrator.

- Enter the SNMP read community strings.

- Define the schedule Emergency Responder should use for updating information from the switches.

- Identify the switches that can have phones connected to them.

- Run the switch-port and phone update process so that Emergency Responder can identify the ports on the switches and whether phones are attached to them.

- Understand recurring network administration tasks.

Manage Onsite Alerts, ERLs, and ALI Data

The following procedure provides information about the tasks that must be completed to Manage onsite alerts, ERLs, and ALI data. This task can be completed by an ERL Administrator.

- Identify the onsite alert (security) personnel that should receive alerts from Emergency Responder.

- 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.

- Add phones that Emergency Responder does not directly support.

Note

Emergency Responder does not automatically track the movement of these phones.

- Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Emergency Responder 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.

Set Up Emergency Responder with Intrado V9-1-1 for Enterprise Service

The following tasks apply when you use Emergency Responder with Intrado V9-1-1 for Enterprise Service:

- Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

- Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

- If you support off-premise users, create off-premise ERLs and assign to IP subnets and unlocated phones.

Note

You cannot assign off-premise ERLs to switch ports.

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Add Users

You can add 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.

In Emergency Responder, you can add a user either as a local user or a remote user. Remote users must use their Unified CM credentials or Active Directory credentials for authentication.

You can add users to either the primary and standby servers within a single Emergency Responder group. Because 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 can log into the backup server.

Before You Begin
Develop a list of users for each security level. You must know the user names of all onsite alert personnel, and you should determine who should have access to each of the administration security levels.

Note

You can use this procedure to add or remove users. However, you cannot remove the administrative user created at the time of Emergency Responder installation.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Click the Add New User button. The User Configuration page appears.

Step 3

Enter the required information in the User Name, Authentication Mode, Password, Confirm Password and Unified CM Cluster fields.

Step 4

Click Insert.

Step 5

Repeat these steps to add additional users.

Step 6

To assign security levels to the new users, you must add them to one or more user groups.

Step 7

Repeat this procedure on the other Emergency Responder server in the Emergency Responder server group.
Note:
To remove a user from a group, you must remove the user from groups on both the primary and standby servers.

Modify Users

After you have created a user, you can change user authentication mode, change the password for a local user, or change a Unified CM cluster for a remote user.

Change User Authentication Mode

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to modify and click Find, or click Find without any search criteria to display all configured users. The search results are displayed.

Step 3

Click on the user name. The User Configuration—Modify User page appears.

Step 4

Select the authentication mode that you want to assign to the user from the drop-down box:

- If you select Remote as the authentication mode, select a Unified CM Cluster from the drop-down box.

- If you select Local as the authentication mode, enter a password and reconfirm the password.

Step 5

Click Update.

Change Password for a Local User

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to modify and click Find, or click Find without any search criteria to display all configured users. The search results are displayed.

Step 3

Click on the user name. The Modify User page, used for user configuration, appears.

Step 4

Select the authentication mode that you want to assign to the user from the drop-down box.
If you select Local as the authentication mode, enter a new password and reconfirm the new password.

Step 5

Click Update.

Change a Unified CM Cluster for a Remote User

In Emergency Responder, you can also change the Unified CM cluster of an existing remote user to another Unified CM Cluster.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to modify and click Find, or click Find without any search criteria to display all configured users. The search results are displayed.

Step 3

If you select Remote as the authentication mode, select a Unified CM Cluster from the drop-down box. The User Configuration—Modify User page appears.

Step 4

Select the new Unified CM Cluster for all the remote users.

Step 5

Click Update

Delete Users

Emergency Responder enables you to perform batch operations in which you can either delete a single user or delete multiple users in bulk.

Note

You cannot delete the default administrative user created at the time of installing Emergency Responder.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to delete and click Find, or click Find without any search criteria to display all configured users. The search results appear.

Step 3

Find the user that you want to delete and click the Delete icon for that user.
The system displays a warning prompting you to confirm the deletion.

You also can select multiple users from the list, both local and remote, by checking the check box and then clicking the Delete Users button to delete users in bulk.

The system displays a warning prompting you to confirm the deletion.

Step 4

Click OK. The user is removed from the system and all User Group associations to the user are deleted.

Changing Users to Remote in Bulk

Emergency Responder allows you to change the user to either local or remote. A remote user is authenticated using the Unified CM Cluster.

Before You Begin

Note

You must have system administrator or ERL administrator authority to access this page.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to delete and click Find, or click Find without any search criteria to display all configured users. The search results appear.

Step 3

Click Username. The Modify User page, used for user configuration, appears.

Step 4

Select the authentication mode that you want to assign to the user. You can change a local user to remote user.

Step 5

Select an Unified CM Cluster from the drop-down box if you have changed the user to remote user.

Step 6

Click Update.
Note:
To change users in bulk, select the users that you want to change by checking the check box and then clicking the Change to Remote Users button. Select the Unified CM cluster from the drop-down box, as described in Step 6.

Emergency Responder Role Management

When you install Emergency Responder, the system defines six default roles (see Role Management for more information about the default roles). You can also define additional roles or modify existing roles.

The following topics describe how to add new roles and how to modify and delete existing roles.

Add 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
Decide what additional roles you want to create and determine if any existing default role meets your needs.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > Roles.
The Find and List Roles page appears.

Step 2

Click Add a New Role.
The Role Configuration page appears.

Step 3

Enter the Role Name (required) and Description (optional) in the text boxes.

Step 4

From the list of resources, check the check box next to the resources to which the new role should have access.

Step 5

Click Insert to add the new role to the system.

Step 6

Verify that you successfully added the new role by returning to the User Management > Roles page and performing 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.

Modify Roles

Note

You cannot modify default roles.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > Roles.
The Find and List Roles page appears.

Step 2

Enter search criteria to find the specific role that you want to modify and click Find, or click Find without any search criteria to display all configured roles. The search results appears.

Step 3

Click the role name.
The Role Configuration—Modify Role page appears.

Step 4

If desired, modify the Role Name and Description (if one is listed) in the text boxes.

Step 5

From the list of resources, checking or unchecking the check boxes next to the resources to which the modified role should have access.

Step 6

Click Update to add the updated role information to the system.

Step 7

Verify that you successfully modified the new role by returning to the User Management > Roles page and perform a role search. Enter search criteria to find the specific role that 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 Configuration—Modify Role page.

Delete Roles

Note

You cannot delete a default role.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > Roles.
The Find and List Roles page appears.

Step 2

Enter search criteria to find the specific role that you want to delete and click Find, or click Find without any search criteria to display all configured roles. The search results appear.

Step 3

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.

Step 4

Click OK to delete the role.
The Find and List Roles page refresh and the roles are no longer listed in the Role Names list.

Emergency Responder User Group Management

When you install Emergency Responder, the system defines six default user groups (see User Group Management for more information about the default user groups). You can also define additional user groups or modify existing user groups.

You can create a user group to receive web alert from a specific ERL. You must associate this User Group with the Onsite Alert ID assigned for an ERL. For additional information, see Add Onsite Security Personnel.

Note

The group members can still view all web alerts in the system, if applicable.

The following topics describe how to add new user groups and how to modify existing user groups.

Add 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 that you want to create and determine if any existing default user groups meets your needs.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User Group.
The Find and List User Groups page appears.

Step 2

Click Add a User Group.
The User Group Configuration—Add User Group page appears.

Step 3

Enter the User Group Name (required) and Description (optional) in the text boxes.

Step 4

Click Add Users.
The User Names page appears.

Step 5

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.

Step 6

Check the check box to the left of the user names to be added and click Add.
The User Name page closes and the added names appears in the Add User to Group text box on User Group Configuration—Add User Group page.

Note:
To delete users from this list, select the user name and click Remove Users.

Step 7

Click Add Roles.
The Role Names page appears.

Step 8

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.

Step 9

Check the check box to the left of the roles to be added and click Add.
The Role Names page closes and the added roles appear in the Add Roles to Group text box on User Group Configuration page.

Note:
To delete roles from this list, select the user name and click Delete Roles.

Step 10

Click Insert to add the new role to the system.

Modify User Groups

Note

You cannot modify default user groups.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User Group.
The Find and List User Groups page appears.

Step 2

Enter search criteria to find the specific user group that you want to modify and click Find, or click Find without any search criteria to display all configured user groups. The search results appear.

Step 3

Click the user group name.
The User Group Configuration—Modify User Group page appears.

Step 4

(Optional) Modify the description of the User Group (if one is listed) in the Description text box.

Step 5

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 Add User Groups.
To remove users, highlight the name of the users and click Remove Users.

Step 6

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 Add Roles.
To remove roles, highlight the name of the roles and click Remove Roles.

Step 7

When you are finished, click Update to save the updated user group information to the system.

Step 8

Verify that you successfully modified the user group by returning to the User Management > User Group page and performing a search. Enter search criteria to find the specific user group that 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 Configuration—Modify User Group page.

Delete User Groups

Note

You cannot delete the default user groups. You can only delete user groups that you have created.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User Group.
The Find and List User Groups page appears.

Step 2

Enter search criteria to find the specific user group that you want to delete and click Find, or click Find without any search criteria to display all configured user groups. The search results appear.

Step 3

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 refresh and the deleted user group is no longer be listed in the User Groups list.

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Restrict Maximum Number of Concurrent Sessions

Emergency Responder allows the administrator to restrict the maximum number of concurrent sessions that can be active at a time for any user. If this restriction is enabled, the administrator can specify a maximum limit (between 1 and15) for the number of concurrent sessions allowed.

This limit is applicable to all users configured in Emergency Responder.

Emergency Responder restricts users from creating more than the specified number of concurrent sessions. Users who attempt to create additional sessions that exceed the concurrent session limit are prevented from logging in to Emergency Responder and will see the following error message: Session limit exceeded. Please log out of any existing sessions and try again.

Note

This limit is applicable to all users that exceed the limit.

Note

This limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Warning

If a user logs in to an Emergency Responder website and closes the browser without logging out, the session remains active until it times out after a period of 30 minutes. During this period, if the user attempts to establish additional sessions beyond the prescribed limit, he will be unable to do so.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Check the Limit Concurrent Sessions check box. This option is used to enable limiting the number of concurrent sessions and enables the Max. number of concurrent sessions drop-down box.

Step 3

Select the maximum number of concurrent sessions that you want to impose on the Emergency Responder user, from the Max. number of concurrent sessions drop-down box.

Step 4

Click the Update Settings button to apply the new change.
Note:
You can disable the maximum number of concurrent settings by selecting System > Emergency Responder Group Settings and uncheck the Limit Concurrent Sessions check box.

Server and Server Group Configuration

The information in the following topics describe how to configure Emergency Responder servers and server groups, and the telephony connection between the Emergency Responder groups and Unified CM.

Set Up a Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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, 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada) or Spanish(Spain), select it in the drop-down box. The default language is English(US).

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

Modify 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 Emergency Responder user in Unified CM.

Caution

Modify the emergency number during off-peak hours.

Procedure

Step 1

Associate the new route point with the Emergency Responder user in Unified CM. See Create Emergency Responder Cisco Unified Communications Manager User.

Step 2

Modify the route point for the new number: enter the number in the Route Point for Primary Cisco ER Server. field.

Step 3

Click Update Settings.
Note:
Emergency Responder can still support only one emergency number. After you change it, Emergency Responder starts routing calls received at the new emergency number route point.

Configure Servers

After you create an Emergency Responder group, you can use the Server Settings page to update Emergency Responder 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 Emergency Responder server.

Procedure

Step 1

Select System > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

Select the server name in the left-hand Servers list to change the server settings (Server Name or Debug Package List, or Trace Package List settings). Emergency Responder loads the server settings into the edit boxes. Make your changes and click Update.

Step 3

Select the server and click Delete to remove a server from the group. 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.

Step 4

When you are satisfied with your settings, click Update.
Emergency Responder saves your changes and displays them in the list of servers at the top of the page.

Upload License File

Cisco Prime License Manager maintains the licensing for Cisco Emergency Responder 10.0 and later.

Use the Prime License Manager tool to obtain licenses from Cisco, to install the licenses, and to manage and view your inventory of licenses. This tool also tracks license compliance or noncompliance.

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Set Up Emergency Responder Cluster and Cluster DB Host

Procedure

Step 1

Identify the following:

- All the Emergency Responder groups participating in the Emergency Responder cluster

- One of the Emergency Responder publishers as "Cluster DB Host"

- A password that is the same across the Cluster as "Cluster password"

Step 2

Using the Emergency Responder Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1.

Step 3

Repeat steps 1 and 2 for each Emergency Responder server group in the cluster.

Step 4

Restart Emergency Responder services.
Note:
Emergency Responder server groups can communicate with Emergency Responder 1.3, 2.x, 7.1 and 8.0 and later versions of Emergency Responder server groups in an Emergency Responder cluster.

Cisco Unified Communications Manager Cluster Changes

If you change or upgrade the Unified CM cluster identified in Emergency Responder to a later version, you must use the Admin Utility to identify Emergency Responder with the later Unified CM version.

To change the Unified CM cluster that is identified in Emergency Responder to a different version, see Change Cisco Unified Communications Manager Version.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Add Onsite Security 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 Emergency Responder end-user interface specific to emergency calls originating from the assigned ERL. They also can view all alerts in the system.

- An email message. If you use an email-based paging address, the message results in a page.

- A telephone call indicating that an emergency call was made.

Before You Begin
You must log into Emergency Responder 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).

Procedure

Step 1

Select ERL > Onsite Alert Settings.
Emergency Responder opens the Onsite Alert Settings page.

Step 2

Enter the unique ID, name, telephone number, email address, and pager address, and User Group of a security or onsite alert person.
Unique ID might be a badge number, email name, or other site-specific unique name. You 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.
Emergency Responder adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.

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 person's record.

- To modify onsite alert settings, click on the person's Onsite Alert ID, Onsite Alert Name, Onsite Alert Number, Onsite Alert Email Address or Onsite Alert Pager 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 person's Onsite Alert ID: to change the Onsite Alert ID, delete the person's entry and create a new one.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Set Up Default ERL

Emergency Responder 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 ERLs that are 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 Emergency Responder only if no other ERL is configured for that phone.

Emergency Responder also uses the default ERL for all emergency calls when the Emergency Responder server is first started (or restarted when there is no standby Emergency Responder server) until the initial switch port update is finished. (This process is started immediately.)

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

You must first configure the required ELINs in Unified CM.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find Conventional ERL Data page.

Step 2

Click Configure Default ERL.
Emergency Responder opens the ERL Information for Default window.

Step 3

Fill in the ERL Information for Default window.

Step 4

Click ALI Details.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Update ALI Info. Emergency Responder saves your ALI. Click Close to close the window.

Step 6

Make the ERL Information for Default window the active window if it is not, and click Update.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
Tip:
You cannot delete the default ERL. In addition, you cannot configure other ERLs unless the default ERL is configured.

Set Up ERLs for Non-PSAP Deployment

You may want to deploy Emergency Responder 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 Only—In 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. Emergency Responder then initiates a call to the configured security phone and plays prompts to alert security personnel to the emergency call.

- Configure Security IDs and Route/Translation Patterns—In this scenario, you configure security IDs for the zones for any ERL and you also configure a route/translation pattern without an ELIN number. Emergency Responder 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. Emergency Responder 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.

Procedure

Step 1

Identify the security personnel to be notified in case of an emergency call (see Add Onsite Security Personnel).
For example, configure security A with directory number 1000.

Step 2

Add an ERL with no route pattern or ELIN, but only with security IDs for that ERL (see ERL Creation).
For example, add ERL X with security A.

Step 3

Go to the switch port screen and assign discovered switch ports to the already configured ERLs (see Switch Port Configuration).
For example, associate switch ports of switch IP Y to ERL X.

All emergency calls from any phone connected to switch IP Y use ERL X and ring on the security A directory number 1000.

Note:
If you use Layer 3 (IP) roaming for wireless IP phones or wireless phones register using their Wireless Access Point's IP address, then Emergency Responder cannot automatically track movement of these phones. This is because Emergency Responder uses the IP address of the phone to determine the phone's location. Do not use Layer 3 roaming if you need Emergency Responder to automatically track movement of wireless phones in your network.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

Import Several ERLs

Rather than defining ERLs one at a time, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Prepare an import file. Emergency Responder 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 to import it.

You can import conventional, off-premise, or Intrado ERLs. Click the Import link in the upper-right corner of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Use the following procedure to view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL data page, Find Off-Premises ERLs data page, or the Find Intrado ERLs data page), click Import.
Emergency Responder opens the Import ERL data page.

Step 2

Select the format of your import file (csv or xml) from the pull-down menu.

Step 3

Click Upload to upload the file from your local machine.

Step 4

Select your import file.

Step 5

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 6

Click Close to close the Import ERL Data window.

Convert ALI Data

Use the PS-ALI Converter tool to generate an ERL csv (Comma Separated Value) text file that can be accepted by the Emergency Responder ERL. You must first upload an existing ALI file in NENA 2.0 format to Emergency Responder before converting it.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

To convert ALI data, follow these steps:

Procedure

Step 1

Select Tools > PS-ALI Converter.
Emergency Responder displays the PS-ALI Converter page.

Step 2

Click the Upload PSALI file button to upload an ERL file in NENA 2.0 format. The Upload File page appears.

Step 3

Follow the instructions in the Upload File to upload the ERL file.

Step 4

Select the uploaded file from pulldown menu.

Step 5

In the Output file (in csv format) Name field, enter the name of the converted csv file you want to create.

Step 6

Click Convert to create the csv file.
The generated csv file is in the following folder:

%cerroot%/import
You can import the file or download the file using the File Manager utility.

Step 7

Modify the converted csv file as needed. For example, add the ERL name, route pattern, and security details to update the ERL.

Step 8

Click Close to close the window.

Set Up IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Emergency Responder supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco Emergency Responder then routes the emergency calls based on the configured IP subnet and ERL associations.

This feature is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.

Use IP subnet-based ERLs to locate and track wireless endpoints, such as Cisco Unified Wireless IP Phone 7920 series devices and Cisco clients using wireless IP connection. Cisco Emergency Responder cannot locate or track wireless endpoints to a Cisco Access Point.

Note

Subnet-based tracking is limited by the IP subnet addressing plan. It cannot distinguish location within a same IP Subnet.

Before You Begin
You must have system administrator or ERL administrator authority to access this page.

Procedure

Step 1

Select ERL Membership > IP subnets and click the Add new IP subnet link on the Find and List IP Subnets page.
Emergency Responder opens the Configure IP Subnets page.

Step 2

At the Subnet ID field, enter the IP address of the subnet that you want to define, for example,10.76.35.0.

Step 3

At the Subnet Mask field, enter the mask of the subnet that you want to define, for example, 255.255.255.224.

Step 4

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.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the subnet and click Select ERL. The Find ERL page closes.

Step 7

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

To change the fields on this page back to the last saved settings, click Cancel Changes.

Step 9

To return to the Find and List IP Subnets page, click Back to IP Subnet Search.

Set Up Test ERLs

You can use Cisco Unified Operations Manager to monitor the health and functionality of Emergency Responder.

To use Cisco Unified Operations Manager with Emergency Responder, you configure a test ERL for conventional ERLs, then add a synthetic phone and associate the synthetic phone to the test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can configure test ERLs only to synthetic phones.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

All synthetic phones used for Emergency Responder 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 are not logged in Call History logs.

- Web alerts are not generated for emergency calls from synthetic phones.

- Email alerts are not generated for emergency calls from synthetic phones.

- PS-ALI records for test ERLs are not 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.

Procedure

Step 1

Select ERL > Conventional ERL and click Add New ERL on the ERL Configuration page.

Step 2

At the ERL field, enter a name for the test ERL.

Step 3

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.

Step 4

Click Insert to save the test ERL and click Close to close the window.

Step 5

Select ERL Membership > Synthetic Phones and click Add New Synthetic phone on the Find and List Synthetic Phones page.

Step 6

In 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

Step 7

In 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.

Step 8

Click Insert to add the phone to the list of defined synthetic phones.

Step 9

To change the fields on this page back to the last saved settings, click Cancel Changes.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

View Audit Trail for 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.

Procedure

Step 1

Select Reports > ERL Audit Trail.
Emergency Responder opens the ERL Audit Trail page.

Step 2

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:

1. Select the field that 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.

2. 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).

3. Click Find when you have entered all of the search criteria.
Emergency Responder lists the matching audit records. If there are a lot of matches, Emergency Responder uses several pages to display them. Use the links at the bottom of the list to change pages.

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.

Emergency Responder Switch Configuration

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. The following topics describe the switch requirements and how to identify switches to Emergency Responder.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Set Up SNMP Connection

Emergency Responder uses SNMP to obtain information about the ports on a switch. Emergency Responder must obtain this port information so that you can assign the ports to ERLs, and so that Emergency Responder can identify phones that are attached to the ports and update their ERL assignments.

Emergency Responder only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.

When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Unified CM servers. Emergency Responder must be able to make SNMP queries of all Unified CM servers in the cluster that it supports.

If your Cisco Emergency Responder servers, Unified CM servers, and Cisco IP Phones are in a different subnet than your switches, you must either configure both the subnets for the servers and phones as well as the subnet for the switches or use *.*.*.*.

Set Up SNMPv2

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 define in Emergency Responder. If you use different strings for different sets of switches, determine whether 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.*.*.

If two or more patterns match an IP address, Emergency Responder 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, Emergency Responder uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

Procedure

Step 1

Select Phone Tracking > SNMPv2 Settings.
Emergency Responder opens the SNMP Settings page.

Step 2

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 Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see LAN Switch Identification for more information), it does not matter if the IP address patterns cover devices other than switches.

- If all of your switches use the same read community string, enter *.*.*.*. You 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 Emergency Responder 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, Emergency Responder 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.

Step 4

Enter the read community string, for example, public.

Step 5

Click Insert.
Emergency Responder adds the SNMP setting to the list of settings.

Step 6

If you must create more than one setting, return to Step 2.
If you change the SNMP read community string on a switch, you must update the associated setting in Emergency Responder:

- To change an SNMP setting, select it in the list. Emergency Responder 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 setting's entry.

Set Up SNMPv3

Procedure

Step 1

Select Phone Tracking > SNMPv3 Settings.
Emergency Responder opens the SNMPv3 Settings page.

Step 2

Enter the User information for which you want to provide access.
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.

Step 3

To require authentication, check the Authentication Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 4

If you checked the Authentication Required check box, you can specify privacy information. To require privacy, check the Privacy Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 5

Enter the timeout and retries values.
These values work together to determine how often and how long Emergency Responder 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, Emergency Responder 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.

The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.

Step 6

Click Insert.

Step 7

If you must create more than one setting, return to Step 2.
Whenever you change the SNMPv3 settings on a switch or Unified CM server, you must update the associated setting in Emergency Responder:

- To change an SNMPv3 setting, select it in the list. Emergency Responder 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 SNMPv3 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 setting's entry.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Identify LAN Switches One at a Time

You can enter switches into the Emergency Responder 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 Import a Group of Switches for more information.

Before You Begin
You must have system administrator or network administrator authority to add, remove, or change switch definitions.

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, Emergency Responder must use the CAM information about the switch to identify phones. See Network Hardware and Software Requirements for information about which phones require CAM access.

Ensure that you configure the SNMP read community strings before adding switches. See Set Up SNMPv2 for more information.

Note

Emergency Responder performs a full discovery scan for all the switches when you either reboot the Emergency Responder server or while upgrading to a higher version. This process can be time consuming, depending on network size and number of switches.

Note

Always delete the LAN Switches from Emergency Responder Administration > Phone Tracking > LAN Switch Details, if this has been removed from the network.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Enter information about the switch:

- 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.

- If you want to display the switch port descriptions that are configured on the switch in the locations field in Emergency Responder, select Use port description as port location.

Step 3

Click Insert to add the switch to the Emergency Responder configuration.
Emergency Responder asks if you want to run the switch port and phone update process. You must run this process so that Emergency Responder 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, Emergency Responder 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.

Note:
Emergency Responder expects only one IP address or hostname per chassis and needs access to the following MIBs:

- mib-2

- IF-MIB

- CISCO-CDP-MIB

- ENTITY-MIB

- CISCO-VLAN-MEMBERSHIP-MIB

- RIDGE-MIB*

- CISCO-STACK-MIB

- Mib-2

- interface

- CISCO-2900-MIB

Click a switch in the LAN Switches list to view the switch's Emergency Responder 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 switch's 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, Emergency Responder identifies any phones connected to the switch as unlocated phones.

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Track Change of Switch IP Address Dynamically

Emergency Responder allows you to dynamically track the change in a LAN switch IP address managed by Emergency Responder. This feature is intended for LAN switches that have been added using the switch hostname.

Before You Begin
You must have system administrator authority to enable dynamic tracking of a LAN switch IP address.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select the Dynamic Tracking of Switch IP Address check box to dynamically track a switch's IP address.

Step 3

Click the Update Settings button to apply the change.
You must wait for the next Incremental Discovery cycle to start. During this cycle Emergency Responder detects the new IP address of the LAN switch and updates its database. You will be notified of this change detection from an entry in the Emergency Responder Event Viewer and with an administrative email alert.

Note:
It is recommended that you enable Dynamic Tracking of Switch IP Address only during a scheduled maintenance window when the switch is subject to an actual change of IP address. It is recommended that you disable this option during normal periods as this operation is CPU intensive.

Note:
For a LAN switch that has been added using the IP address, Emergency Responder cannot track any change in its IP address. In this case, you must delete the switch and add it again with the new IP address.

Phone Management

The following 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 Emergency Responder.

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

Set Up Individual Switch Ports

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 Set Up Large Number of Ports 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 Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports.
Emergency Responder opens the Switch Port Details page.

Step 2

Enter search criteria to list the ports that you want to configure.

- Find displays a maximum of 1,000 records. Refine your search accordingly. To limit the number of ports that are displayed, check the check box next to Collapse search results. The search displays the IP address or name of the switches found. To display all ports associated with a switch and display the expanded view, click the + button next to the switch. To display just the switch and collapse the list, click the - button next to the switch.

- 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. Emergency Responder lists all ports discovered on the switch.

- If you want to narrow your search by using multiple criteria, click the + button 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 Emergency Responder group that 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 Emergency Responder group. You can only search one Emergency Responder group at a time.
Note:
Emergency Responder remembers the previous search criteria for the login session.

Step 3

Assign ports to ERLs:

1. Check the check box next to the switch port that you want to assign an ERL.
If you want to assign all listed ports for a switch, select the check box for that switch. 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.

2. Select the ERL you want to assign to the ports.

3. 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 Emergency Responder server in the Emergency Responder group.

4. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

5. Enter the ERL Search Parameters and click Find. The search results appear.

6. Click the radio button next to the ERL that you want to assign to the switch ports and click Select ERL. The Find ERL page closes.

7. Click Assign ERL.
Emergency Responder 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.

Emergency Responder commits your ERL assignments. From here, you can continue to the other page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.

Click Edit View to change the fields and arrangement of fields in the port list. If you want to revert to the standard view, then click Restore Defaults.

The phone location information is saved on the primary Emergency Responder server. Back up this data regularly.

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Switch-Port Change Reporting for Wired Cisco Unified IP Phones

Emergency Responder 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. Emergency Responder notifies the system administrator of these changes by email.

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 Emergency Responder. Cisco Unified IP Phones that appear on the Unlocated Phones page in Emergency Responder 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 Emergency Responder.

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 extensions.

Procedure

Step 1

Select System > Mail Alert Configurations.
The Email Alert Settings page appears.

Step 2

In the Misc parameters section, check the check box to the right of Switch Port location change reporting parameter to enable or disable email alerts. Check the Include event viewer contents in mail check box if you want to include the details from the event viewer in the email message.

Step 3

Click Update Settings.

What to Do Next

Note

Configure the email client settings to allow line breaks in the email to improve readability.

Supported Cisco Unified IP Phones—This 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 Unified CM. The only exception for this rule is Cisco Unified IP Phones previously registered in Unified CM. These Cisco Unified IP Phones are reported as missing.

Cluster Scenario—The active server in each server group within a cluster sends separate notifications for the Cisco Unified IP Phones it discovers and tracks.

Server Group Scenario—Within a server group, Emergency Responder performs change detection and notification on the active Emergency Responder server only.

Feature Activation—The change detection and notification feature requires manual activation.

Change Notification conditions - Emergency Responder 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 Emergency Responder Administrator web interface.

- Because of a Unified CM 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.

- Because of a LAN switch addition to Emergency Responder the system administrator starts the discovery process.

- Because 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 Unified CM 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 Emergency Responder Server 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.

EnergyWise

Cisco EnergyWise allows administrators to measure and reduce the energy consumption of devices connected to a Cisco network, such as IP telephones. Because each telephone reports its power consumption to a switch or router, you can monitor energy consumption across a network. You can then manage the power state of a phone by determining what phones are powered up, when they receive power, and how much power they receive.

Cisco EnergyWise Phone User Experience

When a phone enters Power Save Plus mode, it becomes unregistered from Unified CM and powers down after negotiating with the EnergyWise switch. Administrators configure the sleep and wakeup times, which are communicated to the switch by the phone.

Users can wake up the Cisco Unified IP Phone 6900, 8900, and 9900 series phones from Power Save Plus mode but cannot wake up the Cisco Unified IP Phone 7900 series.

Phone Discovery Scenarios Common to EnergyWise Users

The following three phone discovery scenarios are common to EnergyWise users. These scenarios can help you to understand this feature.

Scenario 1 — When the phone is connected to a switch that is configured on Emergency Responder for discovery:

- A phone is configured with EnergyWise on the Unified CM.

- The phone is connected to the switch and is discovered by Emergency Responder. The phone is displayed on the Switch Port page, connected to a switch port.

- Before the next Major Discovery, the phone enters Power Save Plus mode and it becomes unregistered with Unified CM.

- During the next Major discovery, Emergency Responder retains the phone location information. It is listed on the Switch Port page as being connected to the same switch port.

- When the phone is powered up again, the correct location is available if the user can make a 911 call without waiting for the next Incremental or Major discovery.

Note

When a phone in Power Save Plus mode is unplugged, the EnergyWise configurations on the switch are lost. And if a Major Discovery takes place, the phone location information is lost also. Even if the phone is plugged back into the same port, powers up and registers with the switch, Emergency Responder treats this phone as a newly registered phone in the next discovery cycle.

Note

If an EnergyWise phone is connected to a supported switch that is configured on Emergency Responder for discovery, the phone must be discovered at least once before entering Power Save Plus mode. This ensures that Emergency Responder retains the phone location and configuration information into the next Major Discovery. If the phone enters Power Save Plus mode without being discovered, it is not listed on the Switch page. But instead the phone is listed on the IP Subnet page (if configured) or the Unlocated Phone page in the next discovery. When it wakes up, registers with the switch and is discovered, the phone is listed on the Switch Port page.

Scenario 2 — IP subnet-based phone discovery in Emergency Responder:

- The phone is configured with EnergyWise on the Unified CM.

- The phone is discovered by Emergency Responder, based on the IP subnet. It is listed on the IP Subnet page.

- Before the next Major Discovery, the phone enters Power Save Plus mode and becomes unregistered with Unified CM.

- During the next Major Discovery, Emergency Responder retains the phone location information and the phone is listed on the IP Subnet page.

- When the phone is powered up again, the correct location is available if the user makes a 911 call without waiting for the next Incremental or Major discovery.

Scenario 3 — Unlocated phones in Emergency Responder:

- The phone is configured with EnergyWise on Unified CM.

- The phone is listed on the Unlocated Phones page in Emergency Responder after discovery.

- Before the next Major discovery, the phone enters Power Save Plus mode and it becomes unregistered with Unified CM.

- During the next Major discovery, Emergency Responder retains the phone location information. It is listed on the Unlocated Phones page.

- When the phone is powered up again, users can make a 911 call without waiting for the next Incremental or Major discovery. But the phone is in the default ERL or the ERL assigned to the Unlocated Phone switch.

Power Save Plus Mode Limitations

Consider the following limitations for users making 911 calls from phones in Power Save Plus mode:

- Users cannot wake up Cisco Unified IP Phones 7900 series that are in Power Save Plus mode because the sleep and wake-up times are configured on the Unified CM. The phone location information is not deleted from Emergency Responder, but users cannot make a 911 call until the phone reaches the configured wake-up time.

- Users can wake up Cisco Unified IP Phones 6900, 8900, 9900 in Power Save Plus mode. But the phone takes a few minutes to wake up and register with Unified CM and you should consider this delay during emergencies.

- You can track phones connected to a switch on the Emergency Responder page. But if the phones go into Power Save Plus mode before they are discovered, they are considered unlocated and are listed on the Unlocated Phones page.

- If a network has a standalone Emergency Responder with no backup subscriber, you should consider the impact of a system or Emergency Responder restart. Because there is no backup server, the existing discovery data is lost when the system is restarted. And when discovery occurs, it is considered a fresh discovery and Emergency Responder does not identify the switch location information for any phones that entered Power Save Plus mode before the restart.

In Emergency Responder, these phones are listed on the Unlocated Phones page or IP Subnet page (if configured). When the phones are powered up and are discovered, they are listed on the Switch Port page. Consider these sleeping phones and their wake-up time when you assign the ERL.

To avoid losing phones in the Power Save Plus mode when Emergency Responder is stopped, we recommend that you configure a backup Emergency Responder subscriber. If the publisher Emergency Responder service is stopped or the server goes down, the subscriber accesses the backup version of the discovery data, including the phones in Power Save Plus Mode. And when a restart occurs, the discovery data is retrieved from the subscriber and the phones in Power Save Plus mode are not lost.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Assign Large Number of Manually Configured Phones to ERLs

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 a 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 Emergency Responder (see Export Manually Configured Phone Information), 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 following procedure explains how to get to this page. Links on the page also display the detailed information about the required file format for the import file if you need it.

Emergency Responder 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 Emergency Responder.

You can only configure manually configured phones defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
The Find and List Manually Configured Phones page appears.

Step 2

Click Import.
The Import Manually Configured Phones page appears.

Step 3

Select the Import Format (csv) using the pull-down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select the import file using the Select File to Import pull-down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Manually Configured Phone page.

Export Manually Configured Phone Information

You can export your Emergency Responder manually configured phone configuration. By exporting this information, you can back up your data or create a file that you can use to update a large number of manually configured phone mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens the Find and List Manually Configured Phones page.

Step 2

Click Export.
Emergency Responder opens the Export Manual Phones page.

Step 3

Select the export format (csv) from the Select Export Format pulldown menu.

Step 4

Enter the desired file name in the Enter Export File Name field and click Export.
Emergency Responder exports the file to the export location.

Step 5

To download the exported file to your local system, select the file name from the Select file to download pulldown menu and click Download.

Step 6

Click Close to close the Export Manual Phones page.

Synthetic Phones

With Emergency Responder, you can use Cisco Unified Operations Manager to monitor the health and functionality of Cisco Emergency Responder. To use Cisco Unified Operations Manager with Cisco Emergency Responder, you configure a synthetic phone in Emergency Responder and associate the synthetic phone to an ERL that is used as a test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can only configure test ERLs for conventional ERLs. You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

For more information, see Set Up Test ERLs.

View Emergency Call History

You can view the history of emergency calls made in your network that are handled by Emergency Responder. Emergency Responder sends emergency call notifications to the onsite alert personnel that you identify in your ERLs, and these people respond to the notifications. From the administrator interface, you can view the same call history that your onsite alert personnel can view, and see 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 about the 10,000 most recent calls. You can find records of older calls in Emergency Responder raw call log files. See Call History Logs for more information.

Procedure

Step 1

Select Reports > Call History.
Emergency Responder opens the Call History page.

Step 2

Click Find.
All call summary information appears.

Step 3

Enter the search criteria that 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. 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).

Step 4

From the list of calls that Emergency Responder shows you in response to your search criteria, you can:

- View the call characteristics.

- Click 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. Emergency Responder opens a separate window where you make your editorial changes.

Tip:
If a large number of calls match your search criteria, Emergency Responder uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.

Chapter 5. Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Emergency Responder and Intrado V9-1-1Enterprise Services Overview

Cisco Emergency Responder (Emergency Responder) supports Intrado V9-1-1 for Enterprise Service in the Cisco Unified Communications environment as an alternative to direct connection with the Local Exchange Carrier (LEC). The Intrado V9-1-1 for Enterprise Service provides local routing and emergency service response for Intrado customers. Emergency Responder works in conjunction with Intrado to provide emergency services to phones that are on the corporate network (on-premise) and phones that are located away from the corporate network (off-premise).

For more information about configuring Emergency Responder, managing Emergency Responder users, working with ERLs, and other related topics, see the "Add Scheduled Intrado Updates" section.

These topics provide an overview of how Emergency Responder operates with Intrado V9-1-1 for Enterprise Service and how to configure and use Emergency Responder to support Intrado V-9-1-1 Enterprise users.

Intrado V9-1-1 for Enterprise Service

If you are a subscriber to IntradoV9-1-1 for Enterprise Service, you can use Emergency Responder to simplify emergency call management. Emergency Responder provides an interface that allows you to enter and synchronize location information directly to the Intrado database. Emergency Responder provides location information for emergency calls for both on-premise phones and off-premise phones and works with Intrado and Unified CM to complete emergency calls.

Emergency Responder tracks IP phones by the IP subnet or when someone manually configures and assigns the MAC address. Emergency Responder maintains the status of the phones (on-premise, off-premise, unlocated), and passes on any ALI or ELIN information to Intrado. Users with on-premise phones rely on Cisco Unified Communications to route their emergency calls to Intrado and the designated emergency provider.

Users with off-premise phones cannot make emergency calls until the users enter in their location and associate this information with their directory number. After the location information has been verified, emergency calls placed from off-premise phones can be completed.

Note

Users can only configure one off-premise location for each DID (DN + External Mask). This configuration also applies to shared lines. If two off-premise phones share a DID, the user can only associate one location to the DID.

The following figure shows the interactions between users, Emergency Responder, and Intrado.

Understanding the Interactions Between Users, Emergency Responder, and Intrado

Emergency Call Flow

When a user makes an emergency call:

1. Unified CM routes the call to Emergency Responder.

2. Emergency Responder routes the call to Intrado.

3. Intrado receives the 10-digit ELIN for the calling party and obtains the ALI data for the caller from this calling party number.

4. Intrado completes the call.

Set Up Support for Intrado V9-1-1 for Enterprise Service

After you have confirmed your emergency service support with Intrado, you must configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

You must complete the tasks described in the following procedure before creating Intrado ERLs.

Note

You must configure the IP address of the DNS server to resolve the URLs provided by Intrado before completing these tasks. See Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder.

Procedure

Step 1

Configure the following items in the Validation and Update Interface (VUI):

1. Upload the certificate provided by Intrado.

2. Validate the certificate.

3. Configure Intrado Account Information.

Step 2

Configure Route Patterns for routing calls to Intrado on the Emergency Responder server.

Step 3

Configure Route Patterns and gateway for routing calls to Intrado on Unified CM server.
See Understanding Route Plans chapter in Cisco Unified Communications Manager System Guide, and the "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Step 4

Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

Step 5

Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Set Up Intrado Route Patterns on Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

Procedure

Step 1

From Emergency Responder, Choose System >Telephony Settings.
The Telephony Settings page is displayed.

Step 2

Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. The "ALI Information section", Cisco Emergency Responder Administration Web Interface Appendix A, contains detailed explanations of each field. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Intrado ERL Imports

If you have multiple ERLs, and you want to add them all at once, you can create a file that contains more than one ERL definition, and import all the ERLs at the same time into your Emergency Responder configuration. For more information about importing ERLs, see Import Several ERLs.

Intrado ERL Information Export

Use the Export ERL page to create ERL export files for our own use, for example, to back up or move an ERL configuration. For more information about importing ERLs, see Export ERL Information.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

ERL Data Migration

Emergency Responder supports migrating existing conventional ERLs to Intrado ERLs and vice versa.

Migrate Conventional ERL Data to Intrado ERL Data

Procedure

Step 1

In Emergency Responder Administration, choose ERL>ERL Migration Tool.
The ERL Migration Tool page appears.

Step 2

Choose Conventional ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 3

Select the ERLs that you want to migrate by checking the check box next to the ERL name.
The Enter Route Patterns for ERL Migration window appears.

Step 4

Choose an updated route pattern from the drop-down menu.

Step 5

Click Migrate to Intrado ERL.

Migrate Intrado ERL Data to Conventional ERL Data

Procedure

Step 1

Step 2

In Emergency Responder Administration, choose ERL> ERL Migration Tool. The ERL Migration Tool page appears.

Step 3

Choose Intrado ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 4

Select the ERLs that you wish to migrate by checking the check box next to the ERL name. The Enter Route Patterns for ERL Migration window appears.

Step 5

Enter an updated route/pattern translation pattern in the adjacent text box.

Step 6

Click Migrate to Conventional ERL.

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Set Up Emergency Responder Location Management in Cisco Unified Communications Manager

You must configure the Emergency Responder Location Management server on the Unified CM server before your users can use it to enter their off-premise locations.

To enable Cisco Emergency Location Manager in Unified CM, follow these steps:

Procedure

Step 1

From Unified CM Administration, choose System > Application Server.

Step 2

Click Add New. The Application Server Configuration page is displayed.

Step 3

From the Application Server Type drop-down box, choose CER Location Management.

Step 4

Click Next.

Step 5

Enter a name that identifies Emergency Responder Off-Premise application. The name is displayed in the navigation drop-down box on the User Option page and is selected by the user to navigate to the Emergency Responder Off-Premise page.

Step 6

Enter the URL for the Emergency Responder Off-Premise page. The URL takes the form of http://cer_host/ofpuser , where cer_host is the name or IP address of the Emergency Responder publisher or Emergency Responder subscriber.
Note:
You must enter both the Emergency Responder publisher and Emergency Responder subscriber as separate application servers on Unified CM Administration.

Step 7

Click Save.

Set Up AXL Application User

You must configure the AXL application user for Emergency Responder on Unified CM, so that an off-premises user can log in to the Emergency Responder off-premises user website.

Procedure

Step 1

In Cisco Unified Communications Manager, choose User Management > Application User. Click Add New. Cisco Unified Communications Manager displays the Application User Configuration page.

Step 2

Complete the following required fields:

- User ID—Use a descriptive name such as AXL Application User.

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

Click Save.

Step 4

Choose User Management > User Group in the Cisco Unified Communications Manager menu. The user group search page appears.

Step 5

At search criterion, enter standard and click Find.
The list of user groups starting with the name standard appears.

Step 6

Click Standard CCM Admin Users to display the User Group configuration page.

Step 7

Click Add App Users to Group. The Find and List Application Users pop-up window appears.

Step 8

Enter the User ID created in Step 2 as the search criterion and click Find. The list of Applications users appears.

Step 9

Click the check box next to the user ID. Click Add Selected.
Unified CM adds the selected user to the Standard CCM Admin Users user group.

Step 10

Choose User Management > User Group. The user group search page appears.

Step 11

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 12

Click the Standard TabSync User group.

Step 13

Repeat steps 7 through 9 to add the user to the Standard TabSync User group.

Step 14

Choose User Management > User Group. The user group search page appears.

Step 15

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 16

Click the Standard RealtimeAndTraceCollection group.

Step 17

Repeat steps 7 through 9 to add the user to the Standard RealtimeAndTraceCollection group.

Set Up AXL Authentication

Procedure

Step 1

From Emergency Responder, choose Phone Tracking > Unified CM.

Step 2

Under AXL Setting, enter the following information:

- AXL Username

- AXL Password

- AXL Port Number

Step 3

Click Insert.

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Off-Premise ERL Imports

If you have multiple ERLs, and you want to add them all at once, you can create a file that contains more than one ERL definition, and import all the ERLs at the same time into your Emergency Responder configuration. For more information about importing ERLs, see Import Several ERLs.

Off-Premise ERL Information Exports

Use the Export ERL page to create ERL export files for our own use, for example, to back up or move an ERL configuration. For more information about importing ERLs, see Export ERL Information.

Add Scheduled Intrado Updates

You can create ALI and Secondary Status update schedules between Emergency Responder and Intrado. A scheduled ALI update sends newly created TN records to Intrado. A scheduled Secondary Status update sends queries to Intrado requesting information about records with errors that have been corrected.

Procedure

Step 1

Choose ERL>Intrado ERL>Intrado Schedule from Emergency Responder, . The Intrado Schedule page appears.

Step 2

Choose the days of the week and the time of day that you want to schedule an update.

Step 3

Check the Enable Schedule box if you want to activate this schedule.

Step 4

Choose either ALI Update Schedule or Secondary Status Update Schedule.

Step 5

Click Add to add the schedule to the list of schedules

Update Scheduled Intrado Update

Procedure

Step 1

From Emergency Responder, choose ERL > Intrado ERL > Intrado Schedule. The Intrado Schedule page appears.

Step 2

Click the Edit link adjacent to the schedule that you want to update.

Step 3

Choose the days of the week and the time of day.

Step 4

Check the Enable Schedule box to activate this schedule.

Step 5

Click Update to change the schedule on the list of schedules.

Chapter 6. Configure Cisco Emergency Responder Serviceability

Cisco Emergency Responder Serviceability Configuration Overview

Note

The following information addresses SNMP Management. For information about SNMP setting for phone tracking , refer to Set Up SNMP Connection.

Emergency Responder supports SNMP V1/V2C and V3. You can use the Serviceability web interface to configure SNMP V1/V2C (Community String and Notification Destination) and SNMP V3 (User and Notification Destination).

Each SNMP version has security models and security levels. Users are assigned to groups that are defined by a security model and specified security levels. Each group also has a defined security access level to a set of MIB objects for reading and writing, which are known as views. The switch has a default view (all MIB objects) and defaults groups defined for SNMP V1 and V2C security models. SNMP V3 provides additional security features that cover message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree.

The following sections describe how to configure SNMP V1/V2C and V3.

Serviceability Tools

The following sections describe the Emergency Responder Serviceability tools.

Use Control Center

The Control Center allows you to perform actions on the services running on the selected Emergency Responder system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Control Center. The Control Center page appears.

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 Emergency Responder Serviceability website. These services can only be started, stopped, or restarted using the CLI.

Step 3

Click Refresh to refresh the page.

Use Event Viewer

The Event Viewer allows you to view events for the prior six months.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Event Viewer. The Event Viewer page appears.

Step 2

Click Find without entering any search criteria to find all events that occurred over the prior six months
To find events that match specific criteria, enter search criteria:

- 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 pull-down menu to the right.

If you select Module, you can then select the module on which to search from the pull-down menu to the right.

Note:
For a list of available Types and Modules, see Event Viewer.

When you have entered your search criteria, click Find.

Step 3

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.

SNMP Configuration

Note

The following SNMP configuration information is for SNMP management. For information on SNMP setting for phone tracking, see Set Up SNMP Connection.

Emergency Responder supports SNMP V1/V2C and V3. You can use the Serviceability web interface to configure SNMP V1/V2C (Community String and Notification Destination) and SNMP V3 (User and Notification Destination).

Each SNMP version has security models and security levels. Users are assigned to groups that are defined by a security model and specified security levels. Each group also has a defined security access level to a set of MIB objects for reading and writing, which are known as views. The switch has a default view (all MIB objects) and defaults groups defined for SNMP V1 and V2C security models. SNMP V3 provides additional security features that cover message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree.

The following sections describe how to configure SNMP V1/V2C and V3.

Set Up SNMP Community String

By configuring SNMP, you can control SNMP access to the Emergency Responder 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

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V1/V2C Configuration > Community String. The SNMP Community String Configuration page appears.

Step 2

Enter the name of the community string in the Community String Name text box.

Step 3

Click Accept SNMP Packets only from these hosts to specify specific hosts whose SNMP packets will be accepted, 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.

Step 4

Select the host IP address and click Remove to remove an existing host, .

Step 5

Select the access privilege for the host from the Access Privileges pull-down menu then click Insert.

Set Up SNMP Users

SNMP V3 provides additional security features that include message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V3 Configuration > User.
The SNMP User Configuration page appears.

Step 2

Click Add New to add a new SNMP User,

Step 3

Enter the name of the new user in the User Name text box.

Step 4

Check the Authentication Required check box to require authentication. Enter a password in the Password text box, reenter the password in the Reenter Password textbox, and click either MD5 or SHA to select a Protol. Click Insert to add the user.

Step 5

Check the Privacy Required check box to require information privacy. Enter a password in the Password textbox, reenter the password in the Reenter Password textbox, and click the DES check box.
Note:
A message is displayed stating 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

Repeats Step 2 through to Step 4 to add additional users.

Set Up MIB2

The SNMP MIB2 tool allows you to specify a contact person for a MIB2 managed node and the physical location of the managed node.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > System Group Configuration > MIB2 System Group Configuration. The SNMP MIB2 Configuration page appears.

Step 2

In the System Contact text box, enter the name of the contact.

Step 3

In the Location text box, enter the location of the managed node.

Step 4

Click Update in the upper left corner of the page.

Step 5

Click Clear in the upper left corner of the page to modify the information, enter the new information in the System Contact and Location text boxes, and click Update.

System Monitor Tools

The following sections describe how to use the System Monitor tools.

Use 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.

Procedure

Step 1

From the Emergency Responder 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 about the information that is displayed, see Table 1.

Step 2

Enter a value (in seconds) in the Set the screen refresh value text box to change the rate at which the page refreshes, and click Set. The minimum value you can enter is 5 seconds.

Step 3

Check the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Click the Start Log button in the Processors section of the page to create a log file of the CPU usage.
Click Start Log in the Memory section of the page to create a log file of the Memory usage.

You can create up to 25 log files.

The default interval for logging is 10 seconds. To change the logging interval, follow these steps:

1. 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.

2. 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

Click Download CPU Log File or Download Memory Log File to download the log files.
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 names that you want to download. To download all log files, check 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 creates and downloads a zipped folder called CPULogs (for Processor log files) and MemoryLogs (for Memory log files).

Step 7

To view the log files online without downloading them, click the file name. The system displays the contents of the log file.

Use 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 can change how often the information refreshes, or you can disable the auto-refresh feature.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Processes.
The Processes page appears. For details about the information that is displayed, see Table 2.

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.

Step 2

Enter a value in the Set the screen refresh value text box in the upper right corner and click Set to change the rate at which the page refreshes. The minimum value you can enter is 5 seconds.

Step 3

Select the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Select the check box to the left of the process name and click View Selected Processes to view the details of a process. 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 stop a log, 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

Click Download Process Logs from the Process Log Files page to download the log files. To download log files click Download Log File from the Processes page.

Step 6

Select the check box to the left of the log file names to download individual files. 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 creates and downloads a zipped folder called ProcessLogs.

Step 7

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.

Use Disk Usage Tool

The Disk Usage tool displays the percentage of available disk space used by the different partitions in the system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Disk Usage.
The Disk Usage page appears. For details about the Disk Usage page, see Table 1.

Step 2

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.

Use Emergency Responder Logs

Emergency Responder 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 Emergency Responder logs.

Emergency Responder logs are organized into three types. The three types, and the logs within these types, are as follows:

- Emergency Responder 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

- DB Logs

- Cerdbmon

- Install DB

- CLI Output Files

- Platform

- DB

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Logs > Log Type > Log Name.
The selected Log Files page appears. See Use Emergency Responder Logs for details about 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

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 creates and downloads a zipped folder called CPULogs. The names of the zipped folders are based on the type of logs they contain, as follows:

- CER Admin

- CERr Server

- CER Phone Tracking

- Syslog

- JTAPI

- Tomcat

- Install

- DRS

- CLILogs

- CMILogs

- ServmLogs

- RemoteSupportLogs

- InstallDBLogs

- CertificateManagement&IPSecLogs

- CerdbmonLogs

- CLIOutputPlatform

- CLIOutputDB

Step 3

Click the file name to view the log files online without downloading them. The system displays the contents of the log file in a separate window.

Step 4

Click Reload Log File to refresh the log file you are viewing.

Step 5

Click Download Log to download the log file you are viewing.

Chapter 7. Configure Cisco Unified Operating System

Access Cisco Unified Communications Operating System Administration

Note

Do not use the browser controls (for example, the Back button) while you are using Cisco Unified Communications Operating System Administration.

Procedure

Step 1

Log in to Emergency Responder.

Step 2

From the Navigation menu in the upper right corner of the Emergency Responder Administration page, choose Cisco Unified OS Administration and click Go.
The Cisco Unified Communications Operating System Administration Logon window appears.

Note:
You can also access Cisco Unified Communications Operating System Administration directly at http://"server-name"/cmplatform.

Step 3

Enter your Administrator username and password.
Note:
The Administrator username and password are established during installation or created by using the CLI.

Step 4

Click Submit.
The Cisco Unified Communications Operating System Administration window appears.

Recover Administrator and Security Passwords

If you lose the administrator password or security password, use the following procedure to reset these passwords.

To perform the password recovery process, you must be connected to the system through the system console, that is, you must have a keyboard and monitor connected to the server. You cannot recover a password when connected to the system through a secure shell session.

Caution

The security password on all servers in the server group must match. Change the security password on all machines, or the servers will not communicate with one another.

Caution

You must reset each server in a server group after you change its security password. Failure to reboot the servers causes system service problems and problems with the Emergency Responder Administration page on the subscriber server.

Note

During this procedure, you must remove and then insert a valid CD or DVD in the disk drive to prove that you have physical access to the system.

Procedure

Step 1

Log in to the system with the following username and password:

- Username: pwrecovery

- Password: pwreset

The Welcome to platform password reset window displays.

Step 2

Press any key to continue.

Step 3

If you have a CD or DVD in the disk drive, remove it now.

Step 4

Press any key to continue.
The system tests to ensure that you have removed the CD or DVD from the disk drive.

Step 5

Insert a valid CD or DVD into the disk drive.
Note:
For this test, you must use a data CD, not a music CD.

The system tests to ensure that you have inserted the disk.

Step 6

After the system verifies that you have inserted the disk, you get prompted to enter one of the following options to continue:

- Enter a to reset the administrator password.

- Enter s to reset the security password.

- Enter q to quit.

Step 7

Enter a new password of the type that you chose.

Step 8

Reenter the new password.
The password must contain at least 6 characters. The system checks the new password for strength. If the password does not pass the strength check, you get prompted to enter a new password.

Step 9

After the system verifies the strength of the new password, the password gets reset, and you get prompted to press any key to exit the password reset utility.

View 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 sections describe how to display this information.

View ServerGroup Information

Procedure

Step 1

From the main Cisco Unified Operating System Administration web page, select Show > ServerGroup. The ServerGroup page appears.

Step 2

For descriptions of the fields on the ServerGroup page, see Table 1.

View Hardware Status

Procedure

Step 1

From the main Cisco Unified Operating System 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 1.

View 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.

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > Network. The Network Settings page appears.

Step 2

See Table 1 for descriptions of the fields on the Network Settings page.

View Installed Software

Procedure

Step 1

From the Cisco Unified Operating System 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 1.

View System Status

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > System. The System Status page appears.

Step 2

See Table 1 for descriptions of the fields on the System Status page.

View IP Preferences

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > IP Preference. The IP Preferences page appears.

Step 2

To find all records in the database, ensure the dialog box is empty; go to Step 3.
To filter or search records:

- From the first drop-down list box, select a search parameter.

- From the second drop-down list box, select a search pattern.

- Specify the appropriate search text, if applicable.

Note:
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click Clear Filter to remove all added search criteria.

Step 3

Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.

Display and Modify Cisco Unified OS Settings

Use the Settings options to display and modify IP settings, host settings, and Network Time Protocol (NTP) settings. The following sections describe how to display and modify Cisco Unified OS settings.

Set Up 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 port 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.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > IP > Ethernet. The Ethernet Configuration page appears.

Step 2

Modify the Ethernet settings by entering the new values in the appropriate fields. For a description of the fields on the Ethernet Configuration page, see Table 1.
Note:
If you enable DHCP, then the Port Information and Gateway Information settings are disabled and cannot be changed.

Step 3

Click Save to preserve your changes.

Set Up 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 about the NTP Server List page, see NTP Server List.

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.

Set Up SMTP Settings

The SMTP Settings window allows you to view or set the SMTP hostname and indicates whether the SMTP host is active.

Tip

If you want the system to send you e-mail, you must configure an SMTP host.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > SMTP.
The SMTP Settings page appears. For details about the SMTP Settings page, see SMTP Settings.

Step 2

Enter the hostname or IP address of the SMTP host.

Step 3

Click Save.

Set Up Time Settings

Before You Begin

Note

Before you can manually configure the server time, you must delete any NTP servers that you have configured. See Set Up NTP Servers for information about deleting NTP servers.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > Time. The Time Settings page appears. For details about the Time Settings page, see Time Settings.

Step 2

Enter the date and time for the system.

Step 3

Click Save.

Manage Software Versions

You can use this option both when you are upgrading to a newer software version or when you must fall back to an earlier software version.

Caution

This procedure causes the system to restart and become temporarily out of service.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > Version. The Version Settings page appears. For details about the Version Settings page, see Version Settings.

Step 2

Click Restart to restart the version running on the active partition.
The system restarts on the current partition without switching versions.

Step 3

Click Shutdown to shut down the system.
The system halts all processes and shuts down.

Note:
The hardware does not power down automatically.

Caution:
If you press the power button on the server, the system immediately shuts down.

Step 4

Click Switch Versions 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.
The system restarts and the partition that is currently inactive becomes active.

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 must fall back to an earlier software version.

Change IP Addresses for Emergency Responder Servers

You can change the IP address of either the Emergency Responder Publisher, Emergency Responder Subscriber, or both the Emergency Responder Publisher and Subscriber.

The following sections provide information on changing IP addresses on the Emergency Responder servers.

Change IP Address of Emergency Responder Publisher or Standalone Server

Before You Begin

Note

Update the IP address information about your DNS server before you begin changing the IP address on the server.

Procedure

Step 1

Change the IP address on the Emergency Responder Publisher by using one of the following options:

- In Cisco Unified Operating System Administration, enter the new IP address in Settings > IP > Ethernet.

- On the CLI, configure the new IP address with the set network ip command.

Step 2

Reboot the Emergency Responder Publisher or Standalone server and wait until it is fully operational. For a Standalone server, go to Step 7 once the server is operational.

Step 3

When the Emergency Responder Publisher is fully operational, login to Cisco Unified Operating System Administration on the Emergency Responder Subscriber.

Step 4

Choose Settings > IP > Publisher. Cisco Unified Operating System Administration displays the old IP address of the Publisher. Enter the new IP address of the Publisher in the Edit box and click Save.

Step 5

Reboot the Emergency Responder Subscriber immediately, so that the Emergency Responder Publisher maintains communication with the Emergency Responder Subscriber.

Step 6

Verify the replication using the utils dbreplication status CLI command. The value on each server should equal two.

Step 7

Verify that the CTI ports are registered on the Emergency Responder Publisher server. If the CTI ports are not registered, you must recreate the CTI ports by deleting the ports and adding them back in again.

Change IP Address of Emergency Responder Subscriber

Before You Begin
Update the IP address information about your DNS server before you begin changing the IP address on the server.

Procedure

Step 1

Change the IP address on the Emergency Responder Subscriber by using one of the following options:

- In Cisco Unified Operating System Administration, enter the new IP address in Settings > IP > Ethernet.

- On the CLI, configure the new IP address with the set network ip command.

Step 2

Reboot the Emergency Responder Subscriber.

Step 3

After the Emergency Responder Subscriber is fully operational, reboot the Emergency Responder Publisher.

Step 4

Verify that the replication using the utils dbreplication status CLI command. The value on each server should equal two.

Change IP Address of Emergency Responder Publisher and Subscriber

If you are planning to change the IP address of both the Publisher and Subscriber, you must change the IP addresses on the servers sequentially, starting with the subscriber first.

Caution

Do not begin to change the IP address of the publisher server until you have completed the task of changing the IP address on the subscriber.

For information about changing the IP address of the Emergency Responder Subscriber server, see Change IP Address of Emergency Responder Subscriber.

For information about changing the IP address of the Emergency Responder Publisher server, see Change IP Address of Emergency Responder Publisher or Standalone Server.

Security Management

The information in the following sections describes how to perform security and IPsec management tasks.

Set Internet Explorer Security Options

You need to ensure that your Internet Explorer security settings are configured correctly so that you can download certificates from the server.

Procedure

Step 1

Start Internet Explorer.

Step 2

Navigate to Tools > Internet Options.

Step 3

Click Advanced.

Step 4

Scroll down to the Security section on the Advanced tab.

Step 5

If necessary, clear the Do not save encrypted pages to disk check box.

Step 6

Click OK.

Certificate Management

The following sections describe the functions you can perform using the Certificate Management menu options.

Display Certificates

Procedure

Step 1

Select Security > Certificate Management from the Cisco Unified OS Administration web page. The Certificate List page appears. For details about the Certificate List page, see Certificate List.

Step 2

Use the Find controls to filter the certificate list.

Step 3

Click the file name to view details of a certificate or trust store.
The Certificate Configuration page displays information about the certificate.

Step 4

Select Back To Find/List in the Related Links list to return to the Certificate List page then click Go.

Download Certificate or CTL to Your Local System

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Click the filename of the certificate or CTL.

Step 2

Use the Find controls to filter the certificate list.

Step 3

Click the filename of the certificate or CTL. The Certificate Configuration page appears.

Step 4

Click Download.

Step 5

In the File Download dialog box, click Save.

Certificate Deletion or Regeneration

The following sections describe deleting and regenerating a certificate.

Delete Certificate

Caution

Deleting a certificate can affect your system operations. Any existing CSR for the certificate that you choose from the Certificate list gets deleted from the system, and you must generate a new CSR. For more information, see Generate Certificate Signing Request.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.

Step 2

Use the Find controls to filter the certificate list.

Step 3

Click the file name of the certificate or CTL.
The Certificate Configuration page appears.

Step 4

Click Delete.

Regenerate Certificate

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.

Step 2

Click Generate New. The Generate Certificate dialog box opens.

Step 3

Choose a certificate name from the Certificate Name list. For a description of the certificate names that display, see the following table.

Certificate Names and Descriptions

Name

Description

tomcat

This self-signed root certificate gets generated during installation for the HTTPS server.

ipsec

This self-signed root certificate gets generated during installation for IPsec connections with MGCP and H.323 gateways.

Step 4

Click Generate New.

Certificate or Certificate Trust List Uploads

Caution

Uploading a new certificate or Certificate Trust List (CTL) file can affect your system operations. After you upload a new tomcat certificate or certificate trust list, you must restart the Cisco Tomcat service by entering the CLI command utils service restart Cisco Tomcat.

Note

The system does not distribute trust certificates to other cluster servers automatically. If you must have the same certificate on more than one server, you must upload the certificate to each server individually.

The following sections describe how upload a CA root certificate, application certificate, or CTL file to the server.

Upload Certificate or CTL File

Procedure

Step 1

Select Security > Certificate Management from the Cisco Unified OS Administration web page. The Certificate List page appears.

Step 2

Click Upload Certificate. The Upload Certificate dialog box opens.

Step 3

Select the certificate name from the Certificate Name list.

Step 4

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.

Step 5

Select the file to upload by doing one of the following steps:

- Enter the path to the file in the Upload File text box.

- Click the Browse button and navigate to the file, then click Open.

Step 6

Click Upload File to upload the file to the server.

Upload Trusted Certificate

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.

Step 2

Click Upload CTL. The Upload Certificate Trust List dialog box opens.

Step 3

Select the certificate name from the Certificate Name list.

Step 4

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.

Step 5

Select the file to upload by doing one of the following steps:

- In the Upload File text box, enter the path to the file.

- Click Browse and navigate to the file, then click Open.

Step 6

Click Upload File to upload the file to the server.

Use 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 procedure outlines this process, with references to additional documentation.

Procedure

Step 1

Generate a CSR on the server.

Step 2

Download the CSR to your PC.

Step 3

Use the CSR to obtain an application certificate from a CA. Get information about obtaining application certificates from your CA.

Step 4

Obtain the CA root certificate. Get information about obtaining a root certificate from your CA.

Step 5

Upload the CA root certificate to the server.

Step 6

Upload the application certificate to the server.

Step 7

Restart the services that are affected by the new certificate. For all certificate types, restart the corresponding service (for example, restart the Tomcat service if you updated the Tomcat certificate). In addition, if you updated the certificate for CAPF or Unified CM, restart the TFTP service.

Generate Certificate Signing Request

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.

Step 2

Click Generate CSR. The Generate Certificate Signing Request dialog box opens.

Step 3

Select the certificate name from the Certificate Name list.

Step 4

Click Generate CSR.

Download Certificate Signing Request

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.

Step 2

Click Download CSR. The Download Certificate Signing Request dialog box opens.

Step 3

Select the certificate name from the Certificate Name list.

Step 4

Click Download CSR.

Step 5

Click Save in the File Download dialog box.

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. You can get information about obtaining these certificates from your CA. The process varies among CAs.

CAPF and Emergency Responder CSRs include extensions that you must include in your request for an application certificate from the CA. If your CA does not support the Extension Request method, 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 the CSRs in PEM encoding format. It accepts certificates in DER and DER encoding formats.

Set Up Certificate Expiration Monitor

The system can automatically send you an e-mail when a certificate is close to its expiration date.

Before You Begin
To update information about the Certificate Expiration Monitor page, the Cisco Certificate Expiry Monitor service must be running.

Procedure

Step 1

Select Security > Certificate Monitor from the Cisco Unified OS Administration web page. The Certificate Monitor page appears.

Step 2

Enter the required configuration information. See Table 1 for a description of the Certificate Monitor Expiration fields.

Step 3

Click Save to save your changes,.

IPsec Management

The following topics describe how to manage IPsec.

Note

IPsec does not get automatically set up between servers in the server group during installation.

Display or Change Existing IPsec Policy

Note

Because any changes that you make to an IPsec policy during a system upgrade are lost, do not modify or create IPsec policies during an upgrade.

Caution

IPsec, especially with encryption, affects the performance of you system.

Procedure

Step 1

Select Security > IPsec Configuration from the Cisco Unified OS Administration web page.
Caution:
Any changes that you make to the existing IPsec policies can impact your normal system operations.

The IPsec Policy Configuration page appears.

Step 2

Click the Display Detail link. The Association Details page appears. For an explanation of the fields in this page, see Table 2.

Set Up IPsec Policy

Note

Because any changes you make to an IPsec policy during a system upgrade are lost, do not modify or create IPsec policies during an upgrade.

Caution

IPsec, especially with encryption, affects the performance of you system.

Procedure

Step 1

Select Security > IPsec Configuration from the Cisco Unified OS Administration web page. The IPsec Policy List page appears.

Step 2

Click Add New. The IPsec Policy Configuration page appears.

Step 3

Click Next. The Setup IPsec Policy and Association page appears.

Step 4

Enter the appropriate information about the IPsec Policy Configuration page. For a description of the fields on this page, see Table 2.

Step 5

Click Save to set up the new IPsec policy.

Manage Existing IPsec Policies

To display, enable or disable, or delete an existing IPsec policy, follow this procedure:

Note

Because any changes that you make to an IPsec policy during a system upgrade are lost, do not modify or create IPsec policies during an upgrade.

Caution

IPsec, especially with encryption, affects the performance of your system.

Caution

Any changes that you make to the existing IPsec policies can impact your normal system operations.

Procedure

Step 1

Navigate to Security > IPsec Configuration.
Note:
To access the Security menu items, you must log in to Cisco Unified Communications Operating System Administration again by using your Administrator password.

The IPsec Policy List window displays.

Step 2

Follow these steps to display, enable, or disable a policy :

1. Click the policy name. The IPsec Policy Configuration window displays.

2. To enable or disable the policy, check or uncheck the Enable Policy check box.

3. Click Save.

Step 3

Follow these steps to delete one or more policies:

1. Select the check box next to the policies that you want to delete.
Select Select All to select all policies or Clear All to clear all the check boxes.

2. Click Delete Selected.

Software Upgrades

The information in the following sections describes how to perform software upgrades.

Software Upgrade Overview

The Software Upgrade pages enable you to upgrade Emergency Responder software from a DVD (local source) or from a network location (remote source) that the Emergency Responder server can access. The Emergency Responder Publisher must be upgraded first, followed by the Subscriber.

With Emergency Responder 8.6 and later, you cannot install upgrade software on your server while the system continues to operate. A Refresh Upgrade is required for all upgrades from Emergency Responder 8.6 or earlier to the most recent version of Emergency Responder. A Refresh Upgrade is a fresh install on the inactive partition, with embedded data migration. A Refresh Upgrade requires server downtime. This is less critical in a redundant system with both Emergency Responder Publisher and Subscriber.

Before you begin the upgrade, back up your system.

When you install the upgrade software, there will be a temporary server outage while the Emergency Responder software is installed. After you begin the upgrade, using either the command line or graphical user interface, the data will be migrated, and the system will automatically reboot, at which point the server outage begins. The duration of this outage depends on your configuration and amount of data. A notification email is sent at the start and end of Refresh Upgrade.

If an administrator makes changes during the upgrade process such as exporting data, then that data could be lost after upgrade.

The previous software remains in the inactive partition until the next upgrade.

A manual switch back can revert to the old version. If the upgrade fails, the system automatically reverts to the previous version. 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 using the switch-version option.

However, any configuration changes that you made since you upgraded the software will be lost, because the database on the inactive partition does not get updated. If you make changes to the database after an upgrade, you must repeat those changes after switching back to the inactive partition.

Supported Upgrades

For supported upgrades, see the Cisco Emergency Responder Release Notes.

Upgrade Cisco Unified Operating System

Note

You must complete the items in the Upgrade Tasks section before you perform any configuration tasks. You also must not make any configuration changes to Cisco Emergency Responder during an upgrade. Configuration changes include any changes that you make in Emergency Responder Administration or Serviceability pages. Any configuration changes that you make during an upgrade could be lost after the upgrade completes, and some configuration changes can cause the upgrade to fail.

Note

Do not perform configuration tasks until the upgrade completes on both Emergency Responder Publisher and Subscriber, until you have switched the servers over to the upgraded partition and until you have verified that database replication is functioning.

Procedure

Step 1

Stop all configuration tasks, including all configuration tasks in the various Cisco Emergency Responder-related GUIs or the CLI.

Step 2

Apply the required cop file.

Step 3

Upgrade the Emergency Responder Publisher.
Note:
The upgraded system will not automatically reboot to the upgraded partition. Instead you are presented with two options: Reboot to new partition and Do not reboot to new partition. The latter is the default option and is considered the best practice. If choose to reboot to new partition, then Steps 5 and 6 are not required.

Step 4

Upgrade the Emergency Responder Subscriber.

Step 5

Switch over the Emergency Responder Publisher to the upgraded partition.

Step 6

Switch over the Emergency Responder Subscribe to the upgraded partition.

Step 7

Ensure that database replication is functioning between the Emergency Responder Publisher and the Emergency Responder Subscriber.

Step 8

When all other upgrade tasks are complete, you can perform any needed configuration tasks as required.

Upgrade File

Before you begin the upgrade process, you must obtain the appropriate upgrade file by placing an order for Cisco Emergency Responder software. You must also download the appropriate cop file as needed from Cisco.com.

Note

Do not rename the patch file before you install it because the system will not recognize it as a valid file.

Note

Do not unzip or untar the upgrade file. If you do, the system cannot read the upgrade files.

You can access the upgrade file during the installation process from either a local DVD or from a remote FTP or SFTP server. Be aware that directory names and filenames that you enter to access the upgrade file are case-sensitive.

Install or Upgrade Software From DVD

You can install software from a DVD that is in the local disk 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 Configure Cisco Emergency Responder Disaster Recovery System chapter.

Procedure

Step 1

Order the appropriate upgrade file. You may choose to receive a physical DVD or download an disk image file through electronic software delivery.
Note:
If you download a disk image file, create the DVD by using the .iso file to burn a DVD. The .iso file contains the complete image of the original DVD disk. You must not copy the .iso file to the DVD. You must use your burner software to extract the files that are in the image and burn them on the DVD. This creates an exact replica of the DVD disk.

Step 2

Insert the DVD into the disk drive on the local server that is to be upgraded.

Step 3

From the Cisco Unified OS Administration web page, select Software Upgrades > Install/Upgrade. The Software Installation/Upgrade page appears.

Step 4

Choose DVD/CD from the Source list.

Step 5

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 (/).

Step 6

Click Next to continue the upgrade process.

Step 7

Choose the upgrade version that you want to install and click Next.

Step 8

On the next page, monitor the progress of the download, which includes the filename and the number of megabytes that are being transferred.

Step 9

Choose Switch to new version after upgrade to install the upgrade and automatically reboot to the upgraded partition. The system restarts on the upgraded software.

Install Software From Network Drive or Remote Server

Note

Do not use your browser controls, such as Refresh/Reload, while accessing Cisco Unified Operating System Administration. Instead, you should use use the navigation controls on the interface.

Before You Begin
Be sure to back up your system data before starting the software upgrade process. For more information, see Configure Cisco Emergency Responder 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.

Step 2

Choose Remote Filesystem from the Source list.

Step 3

Enter the path to the patch file on the remote system in the Directory field.
If the upgrade file is 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 on a Windows server, remember that you are connecting to an FTP or SFTP server so use the appropriate syntax, including:

- Begin the path with a forward slash (/) and use forward slashes throughout the path.

- The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path, which starts with a drive letter (for example, C:).

Step 4

Enter the server name in the Server field.

Step 5

Enter your user name in the User Name field.

Step 6

Enter your password in the User Password field.

Step 7

Select the transfer protocol from the Transfer Protocol field.

Step 8

Click Next to continue the upgrade process.

Step 9

Choose the upgrade version that you want to install and click Next.

Step 10

On the next page, monitor the progress of the download, which includes the filename and the number of megabytes that are getting transferred.

Step 11

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.

Note:
If you lose your connection with the server or close your browser during the upgrade process, you may see following message when you try to access the Software Upgrades menu again:

Warning: Another session is installing software, click Assume
Control to take over the installation.

Click Assume Control if you are sure you want to take over the session.

If Assume Control is not displayed, you can also monitor the upgrade with the Real Time Monitoring Tool.

Step 12

Choose Reboot to upgraded partition to install the upgrade and automatically reboot to the upgraded partition. The system restarts and runs the upgraded software.

Step 13

To install the upgrade and then manually reboot to the upgraded partition at a later time, do the following steps:

1. Choose Do not reboot after upgrade.

2. Click Next. The Upgrade Status window displays the Upgrade log.

3. Click Finish when the installation completes, .

4. Choose Settings > Version to restart the system and activate the upgrade, then click Switch Version. The system restarts running the upgraded software.

Troubleshoot Stalled Upgrades

During a software upgrade, the software installation may stall. Check the upgrade log for new messages. If the upgrade log does not have any new log messages, then the installation may have stalled.

You must cancel the upgrade, disable I/O throttling, and restart the upgrade procedure. When you successfully complete the upgrade, you do not need to enable I/O throttling again.

- To disable I/O throttling, enter the CLI command utils iothrottle disable.

- To display the status of I/O throttling, enter the CLI command utils iothrottle status.

- To enable I/O throttling, enter the CLI command utils iothrottle enable. By default, I/O throttle remains enabled.

If the system does not respond to the cancellation, you must reboot the server, disable I/O throttling, and restart the upgrade process procedure.

If the software upgrade shows stalled at /partb rpm deletion in the logs, then stop the rpm -e process using the root to proceed further.

[root@<Hostname>]# ps -eaf | grep rpm

root      4925  4913  0 18:21 ?        00:00:00 rpm -e --nodeps master

root      7264     1  0 14:02 ?        00:00:00 /usr/local/os-services/sbin/arpmond

root     24359 24188  0 18:37 pts/3    00:00:00 grep

[root@<Hostname>]# kill -9 4925

[root@<Hostname>]# ps -eaf | grep rpm

root      7264     1  0 14:02 ?        00:00:00 /usr/local/os-services/sbin/arpmond

root     24652 24188  0 18:37 pts/3    00:00:00 grep rpm

What to Do Next

If the software upgrade continues to stall, then contact Cisco TAC for assistance.

Revert to Previous Version

After upgrading, you can revert to the software version that was running before the upgrade, by restarting your system and switching to the software version on the inactive partition.

Procedure

Step 1

Revert the publisher node. For more information, see Revert Publisher Server to Previous Version.

Step 2

Revert all backup subscriber nodes. For more information, see Revert Subscriber Server to Previous Version.

Revert Publisher Server to Previous Version

Procedure

Step 1

Open Cisco Unified Communications Operating System Administration directly by entering the following URL:
https://"server-name"/cmplatform

Server-name is the host name or IP address of the Emergency Responder server.

Step 2

Enter your Administrator username and password.

Step 3

Choose Settings>Version. The Version Settings window displays.

Step 4

Click Switch Versions.
After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.

Step 5

Verify that the version switch was successful:

1. Log into Open Cisco Unified Communications Operating System Administration again.

2. Choose Settings>Version. The Version Settings window displays.

3. Verify that the correct product version is now running on the active partition.

4. Verify that all activated services are running.

5. Log into Emergency Responder by entering the following URL and entering your user name and password:
https://"server-name"/ccmadmin

6. Verify that you can log in and that your configuration data exists.

Revert Subscriber Server to Previous Version

Procedure

Step 1

Open Cisco Unified Communications Operating System Administration directly by entering the following URL:
https://"server-name"/cmplatform

"server-name" is the host name or IP address of the Emergency Responder server.

Step 2

Enter your Administrator user name and password.

Step 3

Choose Settings>Version. The Version Settings window displays.

Step 4

Click Switch Versions.
After you verify that you want to restart the system, the system restarts, which might take up to 15 minutes.

Step 5

Verify that the version switch was successful:

1. Log into Open Cisco Unified Communications Operating System Administration again.

2. Choose Settings>Version. The Version Settings window displays.

3. Verify that the correct product version is now running on the active partition.

4. Verify that all activated services are running.

Upload Customized Logon Message

You can upload a text file that contains a customized logon message that appears in Cisco Unified Communications Operating System Administration, Unified CM Administration, and the CLI.

Procedure

Step 1

From the Cisco Unified Communications Operating System Administration window, navigate to Software Upgrades > Customized Logon Message.

The Customized Logon Message window displays.

Step 2

Click Browse to choose the text file that you want to upload.

Step 3

Click Upload File.
Note:
You cannot upload a file that is larger than 10 KB.

The system displays the customized logon message.

Step 4

Click Delete to revert to the default logon message.
Your customized logon message is deleted, and the system displays the default logon message.

Cisco Unified OS Services

The following sections describe how to use Cisco Unified OS services.

Ping Another System

The Ping Configuration page enables you to send ping requests to test if other systems are reachable over the network.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Services > Ping.
The Ping Configuration page appears. For details about the Ping Configuration page, see Ping Configuration.

Step 2

Enter the IP address or network name for the system that you want to ping.

Step 3

Enter the ping interval in seconds.

Step 4

Enter the packet size.

Step 5

Enter the ping count, which is 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. The ping command displays the date and time once the ping count is completed.

Step 6

Choose if you want to validate IPsec or not.

Step 7

Click Ping.
The Ping Results text box displays the ping statistics.

Set Up Remote Support

From the Remote Support page, you can set up a remote account that Cisco support personnel can use to access the Emergency Responder system for a specified period of time.

1. The customer sets up a remote support account. This account includes a configurable time limit on how long Cisco personnel can access it.

2. When the remote support account is set up, a pass phrase gets generated.

3. The customer calls Cisco support and provides the remote support account name and pass phrase.

4. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase.

5. Cisco support logs into the remote support account on the customer system by using the decoded password.

6. 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

If no remote support account is configured, click Add.

Step 3

Enter an account name for the remote account and the account life in days.
Note:
Ensure the account name at least six-characters long and all lowercase, alphabetic characters.

Step 4

Click Save. The Remote Access Configuration page redisplays. For descriptions of fields on the Remote Access Configuration page, see Table 2.

Step 5

To access the system by using the generated pass phrase, contact your Cisco TAC.

Chapter 8. Configure Cisco Emergency Responder Disaster Recovery System

Disaster Recovery System Overview

The Disaster Recovery System (DRS), which can be invoked from the main Cisco Emergency Responder  web interface, provides full data backup and restore capabilities for all servers in an Emergency Responder server group. The Disaster Recovery System allows you to perform a regularly scheduled automatic or user-invoked data backup. DRS supports multiple backup schedules.

The Cisco Disaster Recovery System performs a server group-level backup, which means that it collects backups for all servers in an Emergency Responder server group to a central location and archives the backup data to physical storage device.

Cisco Emergency Responder provides DRS Email Alerts to System Administrators with status and description of any successes or failures.

DRS restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. DRS backs up and restores drfDevice.xml and drfSchedule.xml files. When the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.

When performing a system data restoration, you can choose which servers in the server group that 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 servers in the server group.

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 about data migration from a Windows-based platform to a Linux-based platform, see the Data Migration Assistant User Guide before performing the following the steps.

Caution

Schedule backups during off-peak hours to avoid call-processing interruptions and impact to service.

Backup and Restore Procedures

The following sections provide a quick reference for the backup and restore procedures.

Perform Backup Procedure

The following procedure 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.

Procedure

Step 1

Create backup devices on which to back up data. For more information, see Add Backup Devices.

Step 2

Create and edit backup schedules to back up data on a schedule.
Note:
Either a manual or a scheduled backup backs up the server group.

For more information, see Create and Edit Backup Schedules.

Step 3

Enable and disable backup schedules to back up data. For more information, see Manage Backup Schedules.

Step 4

(Optional)Run a manual backup. For more information, see Start Manual Backup.

Step 5

Check the status of the backup. While a backup is running, you can check the status of the current backup job. For more information, see Check Backup Status.

Perform Restore Procedure

The following procedure 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.

Procedure

Step 1

Choose storage location. You must first choose the storage location from which you want to restore a backup file.

Step 2

Choose the backup file. From a list of available files, choose the backup file that you want to restore.

Step 3

Choose features. From the list of available features, choose the features that you want to restore.

Step 4

Choose server. If the feature was backed up from multiple servers, you must choose the servers that you want to restore.

Step 5

Check the status of the restore. While the restore process is running, you can check the status of the current restore job.

Supported Features and Components

For your Emergency Responder release, you can back up and restore Emergency Responder.

When you choose a feature for backup, the system backs up all of its subcomponents automatically.

System Requirements

Make sure that the current version of Emergency Responder is running on all servers in the server group.

To back up data to a remote device on the network, you must have an SFTP server configured. Cisco tests and recommends the following SFTP servers, but you may use any SFTP server:

- Open SSH (for Unix systems)

- Cygwin

- freeFTPD

- Titan

Note

Cisco does not support third-party software. Contact the SFTP vendor for support issues.

Note

While a backup or restore is running you cannot perform any OS Administration tasks because Disaster Recovery System blocks all OS Administration requests by locking the platform API. However, a backup or restore does not block most CLI commands because only the CLI-based upgrade commands use the Platform API locking package.

Access Disaster Recovery System

To access the Disaster Recovery System, select Disaster Recover System from the pull-down Navigation menu on the main Emergency Responder 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.

Note

You set the Administrator username and password during Emergency Responder installation, and you can change the Administrator password or set up a new Administrator account by using the CLI.

Master Agent Duties and Activation

The system automatically activates the Master Agent on all servers in the server group, 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 Emergency Responder 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 server group, 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 an Emergency Responder server group, 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 server in the server group.

The Local Agent runs backup and restore scripts on each server in the server group.

Add 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.

Procedure

Step 1

Select Backup > Backup Device from the main Disaster Recovery System web page. The Backup Device List page appears.

Step 2

Click Add New to configure a new backup device. To edit a backup device, select it in the Backup Device list and click Edit Selected. The Backup Device window appears.

Step 3

In the Backup device name field, enter the backup device name.
Note:
The backup device name may contain only alphanumeric characters, spaces ( ), dashes (-), and underscores (_). No other characters are allowed.

Step 4

Choose one of the following backup devices and enter the appropriate field values in the Select Destination area:

- Tape Device—Stores 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 Directory—Stores 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 before the backup. The account that is used to access the SFTP server must have write permission for the selected path.

Step 5

Click Save to update these settings, .
Note:
For network directory backups, after you click the Save button, the DRS Master Agent validates the selected SFTP server. If the user name, password, server name, or directory path is invalid, the save fails.

Step 6

To delete a backup device, select it in the Backup Device list and Delete Selected.
Note:
You cannot delete a backup device that is configured as the backup device in a backup schedule.

Create and Edit 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.

Procedure

Step 1

Select Backup > Scheduler from the main Disaster Recovery System web page.
The Schedule List window appears.

Step 2

Do one of the following steps to add a new schedule or edit an existing schedule:

- Click Add New to create a new schedule.

- Click a name in the Schedule List column to configure an existing schedule.

The scheduler window appears.

Step 3

Enter a schedule name in the Schedule Name field.
Note:
You cannot change the name of the default schedule.

Step 4

Select the backup device in the Select Backup Device area.

Step 5

Select the features to back up in the Select Features area. You must choose at least one feature.

Step 6

Choose the date and time when you want the backup to begin in the Start Backup at area.

Step 7

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 occurs.
Tip:
To set the backup frequency to Weekly, occurring Tuesday through Saturday, click Set Default.

Step 8

Click Save to update these settings.

Step 9

Click Enable Schedule to enable the schedule.
The next backup occurs automatically at the time that you set.

Note:
Ensure that all servers in the server group are running the same version of Emergency Responder and are reachable through the network. Servers that are not running at the time of the scheduled backup are not backed up.

Step 10

Click Disable Schedule to disable the schedule.

Manage Backup Schedules

Procedure

Step 1

Select Backup > Scheduler from the main Disaster Recovery System web page. The Schedule List window appears.

Step 2

Select the check boxes next to the schedules that you want to modify:

- Click Select All to select all schedules.

- Click Clear All To uncheck all check boxes.

Step 3

Click Enable Selected Schedules to enable the selected schedules.

Step 4

Click Disable Selected Schedules to disable the selected schedules.

Step 5

Click Delete Selected to delete the selected schedules.

Start Manual Backup

Procedure

Step 1

Select Backup > Manual Backup from the main Disaster Recovery System web page. The Manual Backup page appears.

Step 2

Select a backup device in the Select Backup Device area.

Step 3

Select the features to back up in the Select Features area.

Step 4

Click Start Backup to start the manual backup.

Check Backup Status

You can check the status of the current backup job and cancel the current backup job. To view the backup history, see Backup and Restore History.

Procedure

Step 1

Select Backup > Current Status from the main Disaster Recovery System web page. The Backup Status page appears.

Step 2

Click the log filename link to view the backup log file.

Step 3

Click Cancel Backup to cancel the current backup. The backup is cancelled after the current component has completed its backup operation.

Restore Backup File

Disaster Recovery System adheres to strict version checking and allows restore only for matching versions of Emergency Responder.

The Restore Wizard leads you through the steps that are required to restore a backup.

Tip

To restore all servers in a server group, see Restore Entire Server Group.

Caution

Before you restore Emergency Responder, ensure that the Emergency Responder version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Emergency Responder for restore.

The product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Emergency Responder database restore.

Procedure

Step 1

Select Restore > Restore Wizard from the main Disaster Recovery System web page. The first page of the Restore Wizard (Step1 Restore—Choose Backup Device) appears.

Step 2

Choose the backup device to restore in the Select Backup Device area.

Step 3

Click Next. The Step 2 Restore—Choose the Backup Tar File page appears.

Step 4

Choose the backup file that you want to restore.
Note:
The backup filename indicates the date and time that the system created the backup file.

Step 5

Click Next. The Step 3 Restore—Select the Type of Restore page appears.

Step 6

Choose the features that you want to restore.
Note:
Only the features that were backed up to the chosen file are displayed.

Step 7

Click Next. The Step 4 Restore—Final Warning for Restore page appears.

Step 8

Click Restore to start restoring the data, . You are prompted to choose the server to restore.

Step 9

Choose the appropriate server.
Caution:
After you choose the server that you want restored, any existing data on that server will be overwritten.

Your data is restored on the server that you chose. To view the status of the restore, see View Restore Status.

Step 10

Restart the server.
Note:
The system can require one hour or more to restore depending on the size of your database and the chosen components.

Restore Entire Server Group

If a major failure or a hardware upgrade occurs, you may need to restore all the servers in the server group.

Note

Before you restore a server group, make sure that the subscriber server in the server group is up and communicating with the publisher server. You must carry out a fresh install for the subscriber server that is down or not communicating with publisher server at the time of the restore.

Procedure

Step 1

Restore both Emergency Responder Publisher and Subscriber at the same time by selecting both the servers using Restore wizard.

Step 2

Restart Publisher.

Step 3

Restart the Subscriber after the publisher is back online.
Note:
You must restore both the servers in the server group at the same time.

The following sections provide the procedures for restoring servers in a server group.

Restore Publisher Server

Caution

Before you restore Emergency Responder, ensure that the Emergency Responder version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Emergency Responder for restore.

Procedure

Step 1

Perform a fresh installation of Cisco Emergency Responder on the Publisher server. See the Install Emergency Responder Publisher procedure for more information.

Step 2

From the main Disaster Recovery System web page, select Restore > Restore Wizard. The first page of the Restore Wizard (Step 1 Restore—Choose Backup Device) appears.

Step 3

Choose the backup device from which to restore in the Select Backup Device area.

Step 4

Click Next. The Step 2 Restore—Choose the Backup Tar File page appears.

Step 5

Choose the backup file that you want to restore.
Note:
The backup filename indicates the date and time that the backup file was created.

Step 6

Click Next. The Step 3 Restore—Select the Type of Restore page appears.

Step 7

Choose the features that you want to restore.
Note:
Only the features that were backed up to the chosen file are displayed.

Step 8

Click Next. The Step 4 Restore—Final Warning for Restore page appears.

Step 9

Click Restore to start restoring the data.

Step 10

Choose only the Publisher when you are prompted to choose the server to restore.

Step 11

Your data is restored on the publisher server. To view the status of the restore, see View Restore Status.
Note:
During the restore process, do not perform any tasks with Emergency Responder Administration or User Pages.

Step 12

Restart the server.
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.

Step 13

After the publisher server restarts, continue with the Restore Subscriber Server.

Restore Subscriber Server

Caution

When restoring a server group, you must restore the publisher server before you restore the subscriber server.

Before You Begin
Before you restore Emergency Responder, ensure that the Emergency Responder version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Emergency Responder for restore.

Procedure

Step 1

Perform a fresh installation of Cisco Emergency Responder on the Subscriber server.

Step 2

Select Restore > Restore Wizard from the main Disaster Recovery System web page. The first page of the Restore Wizard (Step 1 Restore—Choose Backup Device) appears.

Step 3

Choose the backup device in the Select Backup Device area.

Step 4

Click Next. The Step 2 Restore—Choose the Backup Tar File page appears.

Step 5

Choose the backup file that you want to restore.
Caution:
To restore the subscriber server in the server group, you must choose the same backup file that you used to restore the Publisher.

Step 6

Click Next. The Step 3 Restore—Select the Type of Restore page appears.

Step 7

Choose the features that you want to restore.
Note:
Only the features that were backed up to the chosen file are displayed.

Step 8

Click Next. The Step 4 Restore—Final Warning for Restore page appears.

Step 9

Click Restore to start restoring the data.

Step 10

Choose only the Subscriber when you are prompted to choose the servers to restore.

Step 11

Your data is restored on the subscriber server.

Step 12

Restart the server.
Note:
The system can require one hour or more to restore depending on the size of your database and the components that you choose to restore.

Step 13

When the subscriber has rebooted and is running the restored version of Emergency Responder, reboot the publisher.

Step 14

Check the Replication Status value on all nodes by using the utils dbreplication status CLI command. The value on each node should equal two.
Tip:
If replication does not set up properly, use the utils dbreplication reset CLI command.

View Restore Status

Procedure

Step 1

From the main Disaster Recovery System web page, select Restore > Status. The Restore Status page appears. The Status column in the Restore Status window shows the status of the restoration in progress, including the percentage of completion of the restore procedure.

Step 2

Click the log filename link to view the restore log file.

Backup and Restore History

The following sections describe how you can see the last 20 backup and restore jobs.

View Backup History

Procedure

Step 1

Select Backup > History from the main Disaster Recovery System web page. The Backup History page appears.

Step 2

From the Backup History page, you can view the backups that you have performed, including filename, backup device, completion date, result, and features that are backed up.
Note:
The Backup History page displays only the last 20 backup jobs.

View Restore History

Procedure

Step 1

Select Restore > History from the main Disaster Recovery System web page. The Restore History page appears.

Step 2

From the Restore History page, you can view the restores that you have performed, including filename, backup device, 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*

You can view trace files by using the CLI.

Use the CLI for Backup and Restore

The Disaster Recovery System also provides command-line access to a subset of backup and restore functions.

Disaster Recovery System CLI

Command

Description

utils disaster_recovery backup

Starts a manual backup by using the features that are configured in the Disaster Recovery System interface.

utils disaster_recovery restore

Starts a restore and requires parameters for backup location, filename, features, and servers to restore.

utils disaster_recovery status

Displays the status of ongoing backup or restore job.

utils disaster_recovery show_backupfiles

Displays existing backup files.

utils disaster_recovery cancel_backup

Cancels an ongoing backup job.

utils disaster_recovery show_registration

Displays the currently configured registration.

utils disaster_recovery show_tapeid

Displays the tape identification information.

Part IV. Administration

Chapter 9. Cisco Emergency Responder Admin Utility

Cisco Emergency Responder Admin Utility Overview

In Cisco Emergency Responder (Emergency Responder), the Admin Utility is integrated into the Emergency Responder itself. The Admin Utility has its own web interface that you can access from the main Emergency Responder web page. As with the other Emergency Responder administration web interfaces, the Admin Utility web interface is password protected.

Change Cisco Unified Communications Manager Version

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

From the main Emergency Responder Admin Utility page, select Update > CCM Version. The Upgrade CCM Version page appears.

Step 3

Select the new version of Unified CM from the Choose the CCM Version to Upgrade pull-down menu and click Go.
Note:
You must change the Unified CM version separately for the Publisher and Subscriber nodes.

During a Layer 2 upgrade, if a lower version of Emergency Responder has Unified CM version configured as 6.0 or lower then Emergency Responder sets the Unified CM to the 6.1 version after the upgrade.

Similarly, during a Layer 2 upgrade if  lower version of Emergency Responder has Unified CM version configured as 7.0, then Emergency Responder sets it to the 7.1 version after the upgrade.

The Status area of the Upgrade CCM Version page displays the new version number after the system makes the change.

Update Emergency Responder Cluster Database Host Details

By default, each server in a cluster considers its own database to be the cluster database host. Because each cluster should have only one database host, you must update the cluster configuration accordingly.

For example, if you have two server groups (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. Update the cluster database host password for Servergroup A using Servergroup A's own host name.

2. Update the cluster database host password for Servergroup B by entering the IP address and cluster database password for Servergroup A.

3. Repeat Step 2 for other server groups 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 fails and cluster functionality is 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.

Note

This procedure only updates the Emergency Responder Cluster DB host details for this server group. Other servers in this Emergency Responder cluster do not updated automatically.

Before You Begin
You must reboot the server to update Emergency Responder Cluster DB host details. Only restarting Emergency Responder services does not work because the IP address is cached by other services.

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Select Update > Cluster DBHost from the main Emergency Responder Admin Utility page. The Update Cluster DB Host page appears.

Step 3

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.

Step 4

Enter the password for the new Cluster DBHost in the Password text box.

Step 5

Reenter the password for the new Cluster DBHost in the Confirm Password text box.

Step 6

Click Go.

Chapter 10. Cisco Emergency Responder User Preparation

Cisco Emergency Responder User Preparation Overview

This chapter describes the various roles for Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder fits into your organization's emergency response needs.

Emergency Responder Onsite Alert Personnel Preparations

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder:

- How to use the Emergency Responder web interface. See the Emergency Responder user web interface online help for information about these topics. The online help includes a user's guide in PDF format that you can print out and distribute to your users. The information in the user's 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 and how to view specific (if set by the administrator) or all alerts in the system.

- 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.

- Explain how they receive notification of an emergency call.

- A web alert appears for everyone logged into the Emergency Responder 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 Emergency Responder 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 have for identifying the location of the emergency caller.

- Explain the organization's policy for responding to emergency calls. Work with the emergency response teams to develop an acceptable policy if you do not already have one.

Emergency Responder ERL Administrator Role

The following table lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder ERL Administration Recurring Tasks

Recurring Task

Description

More Information

Assign ERLs to new or changed switch ports

If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.

Switch Port Configuration

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 Emergency Responder.

- ERL Creation

- Switch Port Configuration

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.

- Export ERL Information

- Export ALI Information for Submission to Your Service Provider

- ERL Creation

- ALI Submission and Service Provider Requirements

Audit the manually defined phones

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.

- Manually Define Phones

Audit the unlocated phones list

Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco Emergency Responder cannot locate the phones and to resolve the problems.

- Identify Unlocated Phones

- Unlocated Phones

Add new onsite personnel or remove old ones; update phone numbers

As onsite alert personnel are added, define them in Cisco Emergency Responder and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco Emergency Responder. Update phone numbers, email address, and other contact information as they change.

- Add Onsite Security Personnel

- ERL Creation

Add IP subnet for the IP subnets to be tracked

If there is a new IP subnet that needs to be discovered by Emergency Responder, then perform the following tasks:

- Configure an ERL spanning the new IP subnet's geographical location.

- Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL.

- Set Up IP Subnet-based ERLs

Emergency Responder Network Administrator Role

The following table lists the recurring tasks for which a network administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder Network Administration Recurring Tasks

Recurring Task

Description

More Information

Add new switches

Add any switches that you add to the network to the Cisco Emergency Responder configuration. A switch is considered new if it has an IP address not defined in Cisco Emergency Responder.

- LAN Switch Identification

- Manually Run the Switch-Port and Phone Update Process

Remove old switches

Remove switches from the Cisco Emergency Responder configuration if you remove them from the network. Nonexistent switches in the Cisco Emergency Responder configuration do not create problems, but they do increase the time required to do phone tracking, because Cisco Emergency Responder attempts to connect to the switch must time out before moving on to the next switch.

- LAN Switch Identification

Update the SNMP read community if it changes

If you change the read community string on any defined switch, you must update the SNMP settings in Cisco Emergency Responder. Until the setting is updated, Cisco Emergency Responder cannot track phones attached to the switch.

- Set Up SNMPv2

Update or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder system administrator.

- Identify Cisco Unified Communications Manager Clusters

Check ERL assignments

Use the ERL Debug Tool to check that the correct and expected ERL is used for a selected phone.

- Emergency Responder Admin Utility

Emergency Responder System Administrator Role

The following table 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 Emergency Responder ERL Administrator Role and the Emergency Responder Network Administrator Role.

Cisco Emergency Responder System Administration Recurring Tasks

Recurring Task

Description

More Information

Add additional Cisco Emergency Responder groups

As telephones are added to the network, you might need additional Cisco Emergency Responder groups. Install and define them and their telephony settings.

Work with the telephony administrator to complete the required Unified CM configuration.

- Installation on a New System

- Set Up Server Group

- Set Up Group Telephony Settings for Server

- Configure Servers

- Identify Cisco Unified Communications Manager Clusters

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.

Create new Cisco Emergency Responder users; remove old users

As onsite alert personnel change, or as Cisco Emergency Responder system, network, and ERL administrators change, add or remove them as required.

- Emergency Responder User Management

Add or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder network administrator.

- Identify Cisco Unified Communications Manager Clusters

Monitor the email alerts that Cisco Emergency Responder generates

If your email ID is configured in the server group settings, Cisco Emergency Responder sends email alerts about critical errors to you. You are expected to understand the error and take action to correct the problem.

See Troubleshoot Email Alerts for information to help you understand the email alerts and resolve problems.

- Set Up Server Group

Chapter 11. ALI Formatting Tool

ALI Formatting Tool Overview

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 (Emergency Responder) and with Cisco Unified Communications Manager (Unified CM) before deploying AFT.

Features

Emergency Responder helps you manage emergency calls in your telephony network. Emergency Responder tracks a system's 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 Emergency Responder 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 Emergency Responder 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.

File Generation

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

ALI Formatting Tool Interface Capabilities

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 Emergency Responder. 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.

The following table shows how to use the AFT interface to perform the main AFT tasks.

Using the AFT Interface to Perform Main Tasks

Task

Procedure

Notes

Open AFT for your service provider

Go to Tools > ALI Formatting Tool. Click the name of your service provider in the pull-down menu.

You must log in to the Emergency Responder Administration website with the proper privileges.

Give a NENA files as input to AFT

Select an Input File for the AFT from the list of files provided in the pull-down menu.

If no NENA files are listed, go to Tools > Export PS-ALI Record and export a NENA 2.0 file.

Go to a specific ELIN number

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.

View ALI details for an ELIN/Select an ELIN to edit its ALI fields

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 screen.

You can then edit the ALI records by entering new values in the ALI editable fields.

Perform a bulk update to the ALI files

Select the ELINs on which you want to perform a bulk update. Click the Bulk Update button above the list of ELINs.

Review Changes

After you make some changes, click the Review Changes/Generate File button.

A list of all the ELINs that have been changed appears.

Click the ELIN link on the Review Changes/Generate File page to view the changed information.

View/Edit Header Record

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.

Header record is common to the ALI file and not per ELIN.

View/Edit Trailer 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.

Trailer record is common to the ALI file and not per ELIN.

Add More ELINs

On the Review Changes/Generate File page, click the Add More ELIN(s) button.

A list of unchanged ELINs appears. Select the ELINs that you want to keep in the final generated file.

Remove ELINs

On the Review Changes/Generate File page, select the ELIN to be removed and click the Remove ELIN(s) button.

The changes made on this record are lost and this ELIN is added to the pool of unchanged ELINs.

Generate Formatted File

On the Review Changes/Generate File page, follow these steps:

1. Select the ELINs that you want to include in the formatted file.

2. Enter a Name for the Formatted File to be generated.

3. 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. Go to Tools > File Management Utility

2. In the search parameters, select ALI Formatting Tool and then select the service provider. Formatted files are displayed.

3. Select the formatted file and click Download.

Generate Formatted ALI File

Procedure

Step 1

Provide a NENA 2.0 file generated by Emergency Responder as input to AFT by following these steps:

1. From the Emergency Responder Administration web page, go to Tools > ALI Formatting Tool.

2. Click your service provider name in the menu.

3. Select an Input File for the ALI Formatting Tool from the list of files provided in the pull-down menu.
AFT displays all the ELINs from the NENA file.

Step 2

Click on an ELIN link to view details of the ALI files. The ALI Record Details for ELIN are populated in the right pane of the screen.

Step 3

Edit the ALI fields by entering new values in the editable fields.

Step 4

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.

Step 5

Update the service provider fields in AFT.
For details about the service provider-specific information required, see Using AFT for Specific Service Providers

Step 6

At this point, if you want to edit some fields in many ELINs simultaneously, you can use the AFT Bulk Update feature. To do so, follow these steps:

1. Select the ELINs to edit using Bulk Update.

2. Click on the Bulk Update button. The Bulk Update form appears.

3. For details about the service provider-specific information required, see Using AFT for Specific Service Providers

Step 7

Generate a formatted file by following these steps:

1. Click on the Review Changes/Generate File button.
The list of edited ELINs are displayed. You can add unchanged ELINs and remove edited ELINs from the list.

2. Select the ELINs that will be part of the final formatted file and enter the name for the formatted file.

3. 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:
Before generating the formatted file, verify the details entered.

Step 8

Using the service provider's preferred method of transmitting files, send the ALI file to your service provider so that 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 is helpful if the service provider reports errors; you can make any required changes to the file without having to re-do all of 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:

1. 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. See 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 Emergency Responder to correct the fields. Then use AFT to regenerate the file.

2. Send the corrected file to your service provider. Be sure to keep a copy of your corrected file for your records.

3. Repeat this process until your service provider can read the formatted files and can use them to update their ELIN records.

Part V. Troubleshooting

Chapter 12. Troubleshoot Cisco Emergency Responder

Troubleshoot Phone-Related Problems

The following sections help you troubleshoot problems related to assigning phones to ERLs and managing the phones.

Check Unified CM SNMP Settings

If Cisco Emergency Responder (Emergency Responder) is not discovering the phones homing to Cisco Unified Communications Manager (Unified CM), check that all Unified CMs are SNMP-reachable and that the SNMP settings are correct. Emergency Responder logs an event if Unified CM is SNMP-unreachable.

Procedure

Step 1

Log in to the Emergency Responder Administration CLI and use the following command to ping the Unified CM server: utils network ping <ipaddress of CUCM>

Step 2

If you successfully ping the Unified CM, verify that the SNMP settings are correct on Unified CM, as follows:

- If you are using a Linux-based version of Unified CM (version 6.0 or higher), log in to the Unified CM 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 Unified CM, open the services on Unified CM and choose Start > Settings > Control Panel > Administrative Tools > Services Properties > SNMP > Properties > Security Tab.

Step 3

Check to see if Unified CM is SNMP reachable by running the following CLI command on the Emergency Responder server:
utils snmp get <ccm ip-address/host name> <snmp-read-community-string> 1.3.6.1.2.1.1.2.0

If the Unified CM is SNMP reachable, then the output of the preceding command should be similar to the following:

Variable = 1.3.6.1.2.1.1.2.0

value = OBJECT IDENTIFIER <sys-oid-of-ccm>

Unlocated Phones

Emergency Responder obtains a list of registered phones from Unified CM and tries to locate all phones. If Emergency Responder 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 is 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 Emergency Responder can resolve some of the problems automatically. See Manually Run the Switch-Port and Phone Update Process for more information.

These are some of the situations that can prevent Emergency Responder from locating a phone:

- If more than one switch port reports the phone as a Cisco Discovery Protocol (CDP) neighbor, then the phone is placed in unlocated phones. This condition is corrected in the next phone tracking when only one switch port reports this phone as its CDP neighbor.

- The phone is attached to a switch that is not defined in Emergency Responder. See LAN Switch Identification for information about 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 Network Hardware and Software Requirements for a list of supported switches. See Manually Define Phones for information about 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. Emergency Responder 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 Emergency Responder. Correct the Emergency Responder configuration. See Set Up SNMPv2.

- The phone requires CAM table access, but CAM tracking is not enabled for the switch in Emergency Responder. See LAN Switch Identification.

- There is a network outage preventing communication between the Emergency Responder server and the switch. Locate and resolve the network outage problem.

Unreachable switches are not retried until Emergency Responder runs the next full switch port and phone update process, unless you run it against the individual switch.

- The phone has moved to a switch served by a different Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list. If the phone is not in the next incremental phone tracking process after it is moved, the phone remains unlocated in any Emergency Responder 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 LAN Switch Identification for information about enabling CAM-based tracking, and Network Hardware and Software Requirements for a list of phones that require CAM-based tracking.

After fixing the problems that are preventing Emergency Responder 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 switch—Select 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 switches—Select Phone Tracking > Run Switch-Port & Phone Update.

Phones Not Located with SMNPv3

Check if the SNMP V3 settings on the SNMPv3 page match the Cisco Unified Communications Manager settings on the Serviceability page. Select Phone Tracking > SNMP V3 Settings. For more information, see Set Up SNMPv3.

Check if the Use SNMP V3 for Discovery checkbox is enabled on the LAN Switch Details page. Select Phone Tracking > Cisco Unified Communications Manager and Phone Tracking > LAN Switch Details.

Check if the Unified Communications Manager and switch added in Emergency Responder are SNMP reachable by executing a SNMP Walk command. Use the CLI and follow one of these examples:

- snmpwalk –v3 <CUCM IP Address> -u <USERNAME> -l AuthPriv -a <AUTH PROTOCOL> -A <AUTH PASSWORD> -x <PRIVACY PROTOCOL> -X <PRIVACY PWD> 1.3.6.1.4.1.9.9.156.1.1.2.1.7

- snmpwalk –v3 <CUCM IP Address> -u <USERNAME> -l AuthNoPriv -a <AUTH PROTOCOL> -A <AUTH PASSWORD> 1.3.6.1.4.1.9.9.156.1.1.2.1.7

- snmpwalk -v3 <CUCM IP Address> -u <USERNAME> -lNoAuthNoPriv 1.3.6.1.4.1.9.9.156.1.1.2.1.7

- snmpwalk -v3 <SWITCH IP Address> -u <USERNAME> -lAuthPriv-a <AUTH PROTOCOL> -A <AUTH PASSWORD> -x <PRIVACY PROTOCOL> -X <PRIVACY PWD> 1.3.6.1.4.1.9.9.23.1.2.1.1.3

- snmpwalk -v3 <SWITCH IP Address> -u <USERNAME> -lAuthNoPriv-a <AUTH PROTOCOL> -A <AUTH PASSWORD> 1.3.6.1.4.1.9.9.23.1.2.1.1.3

- snmpwalk -v3 <SWITCH IP Address> -u <USERNAME> -lNoAuthNoPriv1.3.6.1.4.1.9.9.23.1.2.1.1.3

If you notice a SNMPReqTimeOut or SNMP Unreachable issue in the event logs or the phone tracking logs, then increase the Timeout and Maximum Retry Attempts value under Phone Tracking > SNMP V3 Settings page and run a Major Discovery.

If the issue continues, then try the following:

- Log in to Cisco Emergency Responder from CLI and enter the command utils network capture eth0 file <"filename"> count 10000 size ALL port 161.

- Navigate to Phone Tracking > Run Switch-Port & Phone Update and run a Major Discovery.

- When the Major Discovery is completed, stop the CLI command by pressing CTRL-C.

- Download the packet capture file. Open it and examine the file for the error codes; take the appropriate actions, if needed.

Common Error Messages

SL No

Error message

Occurrence

1

usmStatsUnsupportedSecurityLevel (.1.3.6.1.6.3.15.1.1.1.0)

This is set when the security level (AuthPrivAuthNoPriv/NoAuthNoPriv) specified is not supported by the agent.

This error is reported by the agent with its first varbind containing the OID .1.3.6.1.6.3.15.1.1.1.0".

2

usmStatsNotInTimeWindows (.1.3.6.1.6.3.15.1.1.2.0)

This is set when the engineTime specified is not within the timeWindow of agent. The engineTime is considered not within the timeWindow if any of the following is true:

- If the agent's snmpEngineBoots value is equal to 2147483647.

- If the request's snmpEngineBoots value differs from that of the agent.

- If the difference between the SNMP request's snmpEngineTime and that of the agent is greater than 150.

3

usmStatsUnknownUserNames (.1.3.6.1.6.3.15.1.1.3.0)

This is set when the user name specified is not present in the agent.

This error is reported by the agent with its first varbind containing the OID .1.3.6.1.6.3.15.1.1.3.0.

4

usmStatsWrongDigests (.1.3.6.1.6.3.15.1.1.5.0)

This is set when the password specified is not correct. So check if both Auth and Priv passwords are correct if configured.

This error is reported by the agent with its first varbind containing the OID .1.3.6.1.6.3.15.1.1.5.0.

5

usmStatsDecryptionErrors (.1.3.6.1.6.3.15.1.1.6.0)

This is set when the packet is unable to decrypt on the agent side. This error occurs while querying an AuthPriv user. So check if the Auth and Priv Protocol specified are correct.

This error is reported by the agent with it's first varbind containing the OID .1.3.6.1.6.3.15.1.1.6.0".

IP Subnet Marked as Non-trackable

The IP Subnet Phones page appears when you choose ERL Membership> IP Subnets. The Tracked column shows if the phones under the IP subnet are tracked or not. For IP subnets configured as non-trackable, the View Phones icon will show all phones that are not tracked.

- If a phone falls under both a tracked and non-tracked IP subnets, precedence is given to the more specific IP subnet.

- The phones under the IP subnet marked as non-trackable are not displayed on Switch Ports or Unlocated Phones page.

- If a phone moves between a trackable and non-trackable IP subnet, you must perform a Major Discovery to reflect the changes.

- Cisco Emergency Responder does not restrict a 911 call flow for the phones that are under a non-trackable IP subnet. If a call is made, the default ERL treatment is provided.

Phone Disappears in Emergency Responder

If Emergency Responder is in the middle of a phone tracking process, and a phone is in the middle of homing to a different Unified CM cluster, no Unified CM cluster has a record of the phone. Thus, Emergency Responder does not know the phone exists, and you cannot look up the phone in the Emergency Responder interface. However, assuming the phone successfully connects to a Unified CM cluster, Emergency Responder tracks the phone during the next incremental phone tracking process, and the phone should then appear in the Emergency Responder interface.

This problem can also occur if phones are reconnecting to a primary Unified CM server from a backup server during the Emergency Responder phone tracking process.

Wrong ERL Used for Shared Line

When two or more phones with a shared line appearance move from switches that are monitored by one Emergency Responder group to switches that are monitored by a different Emergency Responder group, then Emergency Responder may assign an incorrect ERL to these phones during an emergency call. This situation can occur when the phones move to a different campus that has a different Unified CM cluster (although the moved phones are still registered with the original Unified CM cluster), and it can also occur when the phones move within a single large campus that is served by multiple Unified CM clusters.

Because the moved phones are still registered to their original Unified CM cluster, emergency calls from these phones are routed to the original Emergency Responder group. In this case, the Emergency Responder group detects that the calling phone is connected to a switch that is monitored by a different Emergency Responder group, and the call is forwarded to the appropriate Emergency Responder 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 Emergency Responder 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 Emergency Responder group, this is not a problem. However, when multiple phones with a shared line appearance connect to switches monitored by the receiving Emergency Responder group, then Emergency Responder 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.

Wireless Endpoints Using Unexpected ERL

Wireless endpoints (such as Cisco Wireless IP 7920 Phones and Cisco IP SoftPhones) may be using switch port-based ERL instead of the configured subnet-based ERL.

Cisco Emergency Responder (Emergency Responder) give a higher priority to switch port association for call routing. If Emergency Responder finds a switch port mapping for any endpoint (including wireless 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, Emergency Responder routes emergency calls using subnet-ERL configuration.

See the switch port screen or the ERL debug tool (see Check Emergency Responder Configuration Using ERL Debug Tool) to check if the wireless endpoint is associated with a switch port.

It is recommended that you track wireless endpoints using subnet-based ERLs.

Troubleshoot Emergency Call Problems

The following sections describe how to troubleshoot emergency calls routing and how to use the information supplied with the calls.

Emergency Calls Not Intercepted by Emergency Responder

If Emergency Responder is not intercepting emergency calls, there is probably a mistake in your Unified CM configuration or its representation in the Emergency Responder configuration.

- The emergency call number (911) is in the Phones partition and uses the E911CSS calling search space. Ensure that this number was identified during Emergency Responder installation (see Installation on a New System) to ensure that users can dial the emergency number. See Create Emergency Call Route Points for information about setting up the Unified CM configuration for this number.

- The standby Emergency Responder server route point (912) is in the E911 partition and uses the E911CSS calling search space. See Create Emergency Call Route Points for information about setting up the Unified CM configuration for this number. Ensure this number is defined as the standby server route point in the Emergency Responder configuration (see Set Up Group Telephony Settings for Server).

- The PSAP callback route point pattern (913XXXXXXXXXX) is in the E911 partition and uses the E911CSS calling search space. See Create Emergency Call Route Points for information about setting up the Unified CM configuration for this number. Ensure this number is defined as the PSAP callback route point pattern in the Emergency Responder configuration, and that the strip prefix (913) is also identified (see Set Up Group Telephony Settings for Server).

- All ELIN route patterns are in the E911 partition. See Create Route Patterns for ERLs for information about setting up the Unified CM 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 Emergency Responder partitions and calling search spaces in the same manner as these partitions in the examples described in the Create Route Patterns for ERLs.

- All gateways to the service provider's network use the E911CSS calling search space. See Set Up Calling Search Space for Gateway and PSAP Connection for more information.

- The Unified CM Version (JTAPI jar) being configured is proper. To check the Unified CM version, follow these steps:

1. Log in to the Emergency Responder Admin Utility website.

2. Select Update > CCM Version

3. In the Status section, check the Current Version of CCM.

ELIN Not Transmitted to 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 (the ELIN) rather than a static number, such as the main site number. See CAMA and PRI Trunks.

ELIN Default ERL Used for Calls From Other ERLs

If an emergency call is assigned an ELIN defined for the default ERL instead of an ELIN assigned to the ERL from where the call was made:

- Check the Unified CM configuration for the route pattern for the ELIN you expected to be used. See Create Route Patterns for ERLs.

- Check the ERL definition in Emergency Responder to ensure that the ELIN is correctly configured for the ERL. See Set Up Individual ERL and Automatic Location Information (ALI).

If the route pattern for an ERL fails, Emergency Responder uses the route pattern defined for the default ERL.

Emergency Calls Not Routed to 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 Create Route Patterns for ERLs). Ensure that the partitions and calling search spaces for the gateways are correct (see Set Up Calling Search Space for Gateway and PSAP Connection).

Note

When a 911 call is made, the call does not route to an alternate PSAP when the primary PSAP call fails. The caller may hear a busy tone, but the Emergency Responder administrator will not receive an email alert that the emergency call could not be routed.

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 Emergency Responder 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 is not routed correctly. See ERL Creation.

- No Calling Party Transformation masks are set at the Gateway or Trunk, which may transform the ELIN set by Emergency Responder.

- If the ELIN is correct, is the ELIN 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 provider's network that cannot connect to the desired PSAP. Consult with your service provider to determine gateway requirements.

See these topics:

- ELIN Numbers Emergency Calls and PSAP Callbacks

- Deployment in Main Site with Two or More PSAPs

- Does the service provider's ALI database contain the correct information for the ELIN? Emergency call routing outside your network is based on the information in the service provider's database, not on the information in your local network. See Export ERL Information.

- Does the emergency caller's phone register with a Unified CM cluster supported by a different Emergency Responder group than the Emergency Responder group that supports the originating switch port? Then you might have a mis-configured Emergency Responder cluster. See these topics:

- Installation on a new system

- Create route patterns for Inter-Cisco Emergency Responder Group communications

- Set up group telephony settings for server

Note

If the call reaches the PSAP, but the PSAP cannot talk to the caller, ensure that the Unified CM for the remote Emergency Responder group has the Unified CM for the local Emergency Responder group defined as a gateway.

Emergency Calls Get Busy Signal and 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 Emergency Responder server:

- If you have only configured a primary Emergency Responder server, install and configure a standby Emergency Responder server. If CPU utilization on the primary server reaches 100 percent, Emergency Responder cannot handle emergency calls. In this case, the standby server handles the calls.

- Check the route point configuration for the standby server. Ensure the emergency call route point's call forward settings are configured to forward calls to this number. See Create Emergency Call Route Points for information about the Unified CM configuration, and the Set Up Group Telephony Settings for Server for the Emergency Responder configuration.

PSAP Call Back Errors

You might encounter a PSAP call back error if a PSAP operator tries to call back an emergency caller using the ELIN provided by caller ID. The following sections describe two such errors: if a PSAP cannot reach the original emergency call extension and if onsite security personnel get a call back from a PSAP.

PSAP Cannot Reach Original Emergency Call Extension

Problem    PSAP could not reach the original emergency call extension.

Solution    Emergency Responder caches a mapping between the caller's 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, Emergency Responder must reuse these numbers and thus overwrites the original caller's extension. You can view the call history to determine the extension of the original caller. See Emergency Call Process.

If this is not the problem, check the configuration of the PSAP callback route point in Unified CM and Emergency Responder (see Create Emergency Call Route Points and Set Up Group Telephony Settings for Server), and ELIN translation patterns in Unified CM (see Create Translation Patterns for ELINs).

Onsite Alert Security Personnel Get Callbacks From PSAP

Problem    Onsite alert (security) personnel get callbacks from the PSAP.

Solution    Emergency Responder 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.

Onsite Alert Personnel 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 Emergency Responder partitions and calling search spaces.

Also, ensure that the Emergency Responder configuration for the Unified CM clusters is correct. The Emergency Responder configuration should show the correct beginning address for the telephony ports that you defined as CTI ports in Unified CM. The number of telephony ports should be the correct number, and the number must be greater than 0 for any calls to occur. Emergency Responder uses this CTI port to place the telephone calls to onsite alert personnel.

If the Event Viewer in the Emergency Responder 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 Emergency Responder Serviceability web interface and select Tools > Event Viewer.

Onsite Alert Phone Does Not Ring When Emergency Call Placed

You might encounter this problem if the onsite alert phone does not ring when an emergency call is placed.

Problem    The onsite alert phone does not ring when an emergency call is placed.

Possible Cause    The onsite alert phone does not ring if the Do Not Disturb (DND) feature is enabled on the phone and if Emergency Responder is configured with Unified CM 6.x.

Solution    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.

Problem    Prompts do not get played at the onsite alert phone when the call is initiated from the CTI ports.

Possible Cause    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.

Solution    To avoid this problem, configure only one line per CTI port in the Unified CM that is configured for Emergency Responder.

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, check the Emergency Responder configurations SMTP settings. Ensure that the SMTP server address and source mail ID are correct, 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 ERL Creation.

- Is the phone location data for the switch port correct? See Switch Port Configuration.

- 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 previously correct configuration is no longer correct. Wires cannot be moved from port to port without potentially invalidating the ERL assignment. See Data Integrity and Reliability.

- The wiring closet is secure, but the ERL assignment is incorrect. See Switch Port Configuration.

- 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 Manually Define Phones.

- The phone is not supported and it is not defined as a manual phone. See Manually Define Phones.

- The phone is supported but Emergency Responder could not locate it. You might have to manually assign the phone to an ERL if you cannot resolve the problem. See Unlocated Phones.

- 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 Manually Define Phones.

Emergency Call History Problems

There are two issues you might encounter when viewing the emergency call history information:

- Emergency call information does not appear in call history.

- Call history does not show call ELIN and route pattern.

For additional information, see View Emergency Call History.

Emergency Call Information Does Not Appear in Call History

Problem    Emergency call information does not show up in call history right away.

Solution    Emergency Responder writes call history information to the database every 15 seconds. You can view history information after 15 seconds.

Call History Does Not Show Call ELIN and Route Pattern

Problem    The call history does not show the ELIN and route pattern used for a call.

Solution    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 Emergency Calls Not Routed to Correct PSAP.

Troubleshoot Licensing

Emergency Responder licensing is managed by Prime License Manager. Prime License Manager manages licensing fulfilment, and supports the allocation and the reconciliation of licenses across supported products. Prime License Manager also provides enterprise-level reporting of usage and entitlement, including status messages.

License Manager Status Messages

The following table shows a list of all status messages as they appear on the License Manager page.

Status Messages on the License Manager Page

Device

State

Status/Warning Message

Description

Emergency Responder

Demonstration mode

Emergency Responder functioning under Evaluation period of 60 days. If the required licenses to cover the shortage are not configured in your Prime License Manager, the Cisco Phone Tracking Engine will be stopped.

This message displays on Emergency Responder during the Evaluation Period.

Emergency Responder

Demonstration period expired

The system has passed the Evaluation Period without being added to any Prime License Manager. The Cisco Phone Tracking Engine has been stopped. Add the instance to a Prime License Manager.

This message displays on Emergency Responder when the Evaluation Period expires and licenses are not installed on Prime License Manager.

Emergency Responder

License overage

Warning : Total phones tracked by the group of Emergency Responder instances added to the Prime License Manager exceed the number of user licenses available. Upload the additional user licenses.

This warning displays on Emergency Responder when the number of Emergency Responder licenses uploaded on Prime License Manager are less than the number of phones tracked by Emergency Responder.

Emergency Responder

Cisco Emergency Responder removed from Prime License Manager.

Cisco Emergency Responder has been deleted from Prime License Manager. Add it to a Prime License Manager to manage Emergency Responder-specific licenses.

Cisco Emergency Responder has been removed from the Prime License Manager. You must add the Emergency Responder instance back to the same or some other Prime License Manager to manage licenses. If you have added Cisco Emergency Responder back to Prime License Manager but you are still getting the same warning, you should synchronize from the Prime License Manager page.

Emergency Responder

Prime License Manager not connected

The system has not synchronized successfully with Prime License Manager since the last successful attempt.

This message displays on Emergency Responder when the system can not synchronize with Prime License Manager after a successful synchronization. Emergency Responder attempts to synchronize with Prime License Manager on a daily basis.

Cisco Prime License Manager Messages

The following table lists the status messages as they appear on the Cisco Prime License Manager page.

Status Messages on the Cisco Prime License Manager Page

Device

State

Alarm Message

Description

Cisco Prime License Manager

Demonstration mode

Cisco Prime License Manager is operating in demo mode. Install licenses to cover the license requirements of your product instances in order to avoid losing functionality in those products.

New installation - no product licenses installed.

Cisco Prime License Manager

License Overage

Insufficient Licenses.

Message displayed in Cisco Prime License Manager within Dashboard and License Usage displays.

Cisco Prime License Manager

Prime License Manager not connected

- Instance Unreachable

- Login Failed

- Certificate Mismatch

- Registration Conflict

- Invalid Server Type

- Product Type Mismatch

- Duplicate Product Instance

Synchronization has not occurred with device. This message with the synchronization status and last date of synchronization displays on Dashboard and Inventory windows.

Troubleshoot Email Alerts

The following sections describe how you troubleshoot problems related to the email alerts generated by Emergency Responder.

JTAPI Incompatibility Warning

As an administrator, you will be alerted if the Unified CM version configured on Emergency Responder differs from the version to which Emergency Responder route points are registered, so that you can take corrective action and assure that emergency calls are processed correctly. An email alert will be sent to the configured email address using SMTP mail server.

Ensure that email alerts for Emergency Call Routing Parameters are enabled under Email Alert Settings on the Emergency Responder administration pages.

The error is also displayed on the Event Viewer page. See the Related Links below.

Alert would be as follows:

Unified CM at <IP address> is version CUCM x which differs from CUCM version setting CUCM y on Cisco Emergency Responder.

This warning could occur in the following cases:

- Unified CM version is no longer supported; for example, Unified CM 2.0 integrated with Cisco Emergency Responder 8.7 or 9.0

- Unified CM version is not yet supported; for example, Unified CM 9.5 integrated with Cisco Emergency Responder 8.7 or 9.0

- Unified CM version is supported, but Unified CM version setting on Emergency Responder is incorrect; for example, Unified CM 9.0 integrated with Cisco Emergency Responder 8.7 or 9.0, but Emergency Responder Unified CM version setting is Unified CM 7.1

Multiple Unified CM versions in the same Emergency Responder will always cause one of the above situations.

JTAPI Route Point Registration Failure Alarm

As an administrator, you will be alerted if Emergency Responder cannot register its JTAPI route points so that you can take corrective action and assure that emergency calls are processed correctly.

The following events can cause the route point to register or unregister:

- Cisco Emergency Responder or SNMP service restart.

- Cisco Emergency Responder failover or fallback.

- JTAPI version upgrade or downgrade.

- Incompatible JTAPI version.

- Emergency Responder or Unified CM upgrade.

- Application user’s credential is incorrectly mentioned in Emergency Responder.

- Application user password expired.

- CTI telephony port begin number is wrongly mentioned in Emergency Responder (impacts only CTI ports).

- CTI telephony port count is wrongly mentioned in Emergency Responder (impacts only CTI ports).

- SNMP configuration is incorrect in either Emergency Responder or Unified CM.

- Route point DN numbers mismatch in Cisco Emergency Responder or Unified CM.

If Unified CM is SNMP unreachable or application user credentials to Unified CM are incorrect, then Emergency Responder will send an email alert to the configured email ID. Ensure that the email alert settings under the discovery parameters are enabled under Email Alert Settings on the Emergency Responder administration pages.

The email alert would be as follows:

<CERserver hostname> Cisco ER Phone Tracking could not get information [using SNMP] from 1 Cisco CallManager(s) Check EventViewer on CERServer for details.

This is a serious condition and may indicate that Emergency Responder will not receive and process emergency calls.

Emergency Call Alert

Whenever a user makes a 911(Emergency) call, Emergency Responder generates an email alert. Emergency Responder 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.

Security personnel are expected to respond to that user. For detailed call information, see the following URL:

http://<<CERServer HostName>>/ceruserreports

When a 911 call is made and the backup Emergency Responder 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 Emergency Responder)
Caller Extension:332101
Display Name     :Caller's Name
Zone/ERL         :Z1
Location         :ddd
Call Time        :June 2, 2003 3:47:30 PM IST

Transition Alert

When the standby Emergency Responder server takes control and becomes the active server, a Transition Alert is sent to the Emergency Responder administrator. This situation occurs under any of the following circumstances:

- If the primary Emergency Responder server is stopped.

- If the Emergency Responder service is stopped on that server.

- If the connectivity between primary and standby Emergency Responder servers is broken.

The administrator should diagnose the cause and fix the problem as soon as possible.

When the Emergency Responder backup server takes control, an alert similar to the following is sent:

Subject: Transition Alert: Cisco ER Backup is activeMessage:
Backup Cisco ER <<CER HostName>> has taken control as Active Cisco ER.
Transition Time  :June 2, 2003 3:57:12 PM IST

When the master Emergency Responder server takes control, an alert similar to the following is sent:

Subject: Transition Alert: Cisco ER Master is activeMessage:
Master Cisco ER <<Emergency Responder Server HostName>> has taken control
as Active Cisco ER. Transition Time  :June 2, 2003 3:57:12 PM IST

Tracking Failure

At the end of a switch port and phone tracking process, if there are any devices that could not be tracked, Emergency Responder sends a Tracking Failure email to the Emergency Responder administrator.

The administrator should look at the event log on the Emergency Responder server to find the list of devices that were not tracked. The administrator should check the following and make any required corrections:

1. Make sure that the correct SNMP Community String is configured in Emergency Responder.

2. Check that the device is connected.

3. Check that the host name for the Emergency Responder server is resolvable, that is, it can be found.

4. Check that the SNMP service is enabled on that particular device (Switch / Unified CM).

Here is an example of a tracking failure alert:

Subject: CER Phone Tracking failed to track some devicesMessage:
CER Phone Tracking could not get information [using SNMP] from 2
Cisco Unified CM(s) and 1 Switch(es)Check Event Viewer
on CER Server for details.

Failed to Get Provider Alert

Emergency Responder sends a Failed to Get Provider alert to the Emergency Responder administrator if Emergency Responder is not able to register to one of the configured Unified CM clusters. Emergency Responder continues trying the registration until it succeeds. Emergency Responder sends the Failed to Get Provider email after a few retries.

The message provides information about how to clear the problem, as shown in the following example:

Subject: Failed to get JTAPI Provider for Cisco Unified CM <<CCM IP/Host Name>>
(Generated by Backup Cisco ER)Message:
Please check the following:
1) Check if the Cisco Unified CM 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 Emergency Responder Phone Tracking Engine

Emergency Responder sends this email alert to the Emergency Responder administrator if the Emergency Responder server fails to establish communication with the Phone Tracking Engine for a period of time. This failure to communicate can occur if the Emergency Responder Phone Tracking Engine service is down. The administrator should perform the following steps:

1. If the Emergency Responder Phone Tracking Engine service is down, start the service.

2. Make sure that the Host Name of the Emergency Responder 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.

Lost Communication with Emergency Responder Phone Tracking Engine

Emergency Responder sends this email alert to the Emergency Responder administrator if the Emergency Responder server loses communication with the Emergency Responder Phone Tracking Engine. This situation is likely to occur if the Emergency Responder Phone Tracking Engine service goes down when the Emergency Responder server is running.

The administrator should restart the Emergency Responder Phone Tracking Engine service.

The following shows an example of a tracking failure alert:

Subject: CER Server lost communication with CER Phone Tracking EngineMessage:
CER Server could not communicate with CER Phone Tracking Engine.

Failed to Send Unlocated Phone Details to Remote Emergency Responder Server Group

If Emergency Responder 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 occurs very rarely. It can occur when a Emergency Responder server is found in more than one Emergency Responder 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:
CER Server 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, Emergency Responder 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 Cisco Unified CM is not enabled, please enable it.

Solution

- If you are running Unified CM 4.2 or 4.3, make sure that the Calling Party Number check box on the Emergency Responder User page is checked.

- If you are running Unified CM 5.x or Unified CM 6.x, make sure that the routes are available.

- Add the Emergency Responder Application User to the "Standard CTI Allow Calling Number Modification" user group.

Calling Party Modification Failed

If the calling party modification was not successful, Emergency Responder sends the following email to the system administrator:

Subject: Emergency Calling Party Modification Failed (Emergency ResponderServer: <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 routed to default ERL because the
calling party modification failed. Please make sure that the check box "Enable Calling
Party Number Modification: is checked on the Cisco Unified CM user page for the
CER user. PSAP callbacks MAY NOT work correctly. The CER service will need to
be restarted once the flag is checked on the Cisco Unified CM User page.

Solution

Check the box for the "Enable Calling Party Number Modification" in the Emergency Responder user page in Unified CM 4.2 or 4.3 Administration. After you enable this flag, restart the Emergency Responder service for the changes to take effect.

Troubleshoot Web Alerts

You might encounter Web Alert Refreshes Every 30 Seconds when receiving web alerts.

Web Alert Refreshes Every 30 Seconds

Problem    Web alert continues to refresh every 30 seconds. You can see this problem by checking the status in the browser. The status displays the seconds remaining before refresh if it is in this mode.

Solution    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.

Troubleshoot Emergency Responder System and Administration Problems

The following sections describe how you can troubleshoot problems related to the Emergency Responder system and its administration, such as server and web server problems.

Cannot Validate Publisher

If the installation cannot validate the Publisher (Step 5 of the Install Emergency Responder Subscriber), check the following:

1. Verify that the Publisher hostname is correct and that the Publisher is reachable by hostname.

2. Verify that the Publisher and Subscriber servers are running the same version of Emergency Responder.

3. Verify that the database password that you entered is correct. This password was specified on the Database Access Security Configuration page during installation.

4. Make sure that the Subscriber has been configured correctly on the Publisher.

Troubleshoot Login Problems

The following section shows some issues you might encounter while logging into Emergency Responder.

Cannot Access Emergency Responder Administration Website

Problem    You cannot log in to the Emergency Responder Administration website.

Solution    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.

HTTP Error 500

If the Emergency Responder Administration website displays a HTTP Error 500 after the installation or upgrade, try the following:

- Restart Cisco Emergency Responder and Cisco Tomcat service.

- Run a select query to cerremote table and check if the RMI objects have been created for both Publisher and Subscriber Nodes.

- If you have replication issues between Publisher and Subscriber:

- Check the .rhosts file of the Publisher and confirm that it was entered with the correct values. If the correct values have not been entered, restart the Cisco Emergency Responder service.

- Run the utils dbreplication repair and utils dbreplication reset commands to reset the Database replication.

- If these steps do not fix this issue, set the server to permissive mode using the utils os secure permissive command and reboot it.

Cisco Unified Operations Manager

Use Cisco Unified Operations Manager to continuously monitor the health of the Emergency Responder system.

For information about setting up Emergency Responder to use Cisco Unified Operations Manager, see Set Up Test ERLs.

For information about installing and using Cisco Unified Operations Manager, go to this location:

Click Here .

Troubleshoot Emergency Responder Switch and Port Configuration Problems

The following sections describe several common issues that you might encounter while configuring switches or switch ports in Emergency Responder.

Phones Do Not Get Discovered

Problem    Emergency Responder is configured with Unified CM information, but no phones get discovered.

Solution    Ensure that the Unified CM servers are reachable on the network. Then ensure that the SNMP read community strings are configured correctly for the switches and Unified CM servers (see Set Up SNMPv2.) Manually run the switch port and phone update process (see Manually Run the Switch-Port and Phone Update Process.) Use the CLI-based utils snmp command to determine if the Unified CM is SNMP reachable.

Emergency Responder Does Not Show Ports on Switch

Problem    Emergency Responder does not show the ports on a switch configured in Emergency Responder.

Solution    If you add a supported switch to Emergency Responder and run phone tracking on the switch after adding it, you can view the list of Ethernet ports on the switch. If Emergency Responder does not list the ports, check the SNMP settings in Emergency Responder for the switch (see Set Up SNMPv2.) 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 LAN Switch Details.)

If the problem persists, ensure that the switch is supported (see Network Hardware and Software Requirements.) Also, check the Event Viewer for error messages.

Some Phones Do Not Appear in Switch Port List

Problem    Some phones do not appear in the switch port list.

Solution    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 are placed as unlocated phones. See Unlocated Phones for a list of reasons that a phone could not be located.

Cannot Delete Switch From Emergency Responder Configuration

Problem    Cannot delete a switch from the Emergency Responder configuration.

Solution    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 Emergency Responder server might not be running. Check the control center and restart the server (see Manage Emergency Responder Server.)

Import or Export of Switch Port Details Fails

Problem    Import or export of the switch port details fails.

Solution    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 Emergency Responder server is not running (use the control center to restart it, see Manage Emergency Responder Server); the Emergency Responder server is not completely initialized (wait for it to initialize).

Import of Some Switch Port Configurations Fail

Problem    The import of some switch port configurations fail.

Solution    To import switch port configurations, Emergency Responder must already be configured with the switch and Emergency Responder 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 Emergency Responder, the importation of those settings fails. See Manually Run the Switch-Port and Phone Update Process for information about the process. Run it on the switches whose port configurations you could not import, then retry the import.

Phones Moved To and From Various Emergency Responder Groups Incorrectly Display in Switch Port Details

Problem    Phones moved from other Emergency Responder groups to this Emergency Responder group, and then moved back, are still showing up in the switch port details for the Emergency Responder group.

Solution    These 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 Manually Run the Switch-Port and Phone Update Process.

Check Emergency Responder Configuration Using ERL Debug Tool

The ERL Debug Tool takes a phone extension as the search criteria and displays the ERLs currently being used for routing emergency calls for the phones.

Use this diagnostic tool to verify the Emergency Responder 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 mis-configured 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.

Procedure

Step 1

Select Tools > ERL Debug Tool.
Emergency Responder displays the ERL Debug Tool page.

Step 2

In the Find Phones field, to list specific phones, select the search criteria and click Find.
Emergency Responder displays the ERL currently being used for routing emergency calls for the phone.

Step 3

If the configurations are not correct, make the required changes.
Note:
Emergency Responder displays a maximum of 1,000 records.

Publisher and Subscriber Server Replacement

The following sections describe how to replace a faulty Publisher server and how to replace a faulty Subscriber server.

Replace Faulty Subscriber

To replace a faulty Subscriber, go to Emergency Responder administration and delete the faulty Subscriber. Install a new Emergency Responder Subscriber for the Publisher (see Installation on a New System).

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 Emergency Responder administration screen on the Publisher server.

Replace 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 Emergency Responder.

Procedure

Step 1

Install the same version of the Emergency Responder Publisher on a server with the same host name as the one you used previously.

Step 2

Choose the same configuration options (such as the Unified CM version, and so on) during the installation.

Step 3

Restore the old configuration data using the Disaster Recovery System.

Emergency Responder Admin Utility

You can use the Emergency Responder Admin Utility tool to perform the following tasks:

- To update Emergency Responder cluster database host details

- To upgrade the CCM version

Use Emergency Responder Admin Utility Tool

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Using the menu bar, choose a task to perform:

1. To change the Publisher that the Subscriber server points to, select Update > Publisher.

2. To update the Unified CM version, select Update > CCM Version.

3. To update the cluster settings on both the Publisher and Subscriber servers, select Cluster > DBHost.
Note:
This action updates the Emergency Responder cluster DB details for this server group only. Other servers in this Emergency Responder cluster will NOT be updated automatically.

Step 3

To save the changes that you have made, restart both the Publisher and the Subscriber servers.

Set Up Subscriber Database

To configure the Publisher-Subscriber setup again if you have an issue with the Subscriber (apart from DB replication), follow these steps:

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface on the Subscriber server.

Step 2

Select Update > Publisher.

Step 3

Specify the same Publisher Host Name, IP address (already being pointed to) and database access security password.

Step 4

Click Go.
This step might a take a while to set up.

Database and Enterprise Replication Troubleshooting Commands

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

- utils service list—Checks whether the IDS service is running or not.

- show tech dbstateinfo—Provides the DB state information, which is helpful in debugging database issues.

- show tech dbinuse—Displays the currently used database.

- show tech dbintegrity—Shows database integrity information.

- show tech database—Creates a .csv file with contents of all the tables in the database.

Use the following CLI commands for troubleshooting Enterprise Replication:

- utils dbreplication status—Displays the status of the database replication.

- utils dbreplication reset—Resets and restarts the database replication between the Publisher and Subscriber.

- utils dbreplication repair—Compares the data on replication servers (Publisher and Subscriber) and creates 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.

For troubleshooting database problems using logs, download logs from the Emergency Responder Serviceability website or through the CLI.

The following logs provide information for debugging database-related issues:

- Install and 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/

Replication Fails to Start After Subscriber and DNS Installation

Problem    Replication fails to start after the Subscriber is installed with DNS and the CLI command utils dbreplication status indicates that replication is not working.

Possible Cause    The .rhosts have the host name for the Subscriber instead of FQDN (Fully Qualified Domain Name) of the Subscriber.

Solution    Use the CLI command utils dbreplication repair to repair the replication issue. This command tries to repair replication by rebuilding the corrupted .rhosts file.

Troubleshoot Emergency Responder System Problems

The following sections discuss some issues you might encounter with general operation of the Emergency Responder system and the configuration screens that involve the Emergency Responder server, group, and cluster.

Emergency Responder Intra-Cluster Call Routing Fails or Phones Not Discovered Correctly

Problem    Emergency Responder intra-cluster call routing fails or Emergency Responder does not discover phones correctly.

Solution    Ensure that all the Emergency Responder servers in an Emergency Responder cluster can be found by their host name, and ensure that all are reachable on the network by all the other Emergency Responder servers. Solution    Ensure that all the Emergency Responder servers can reach the Emergency Responder cluster DB host and that the cluster DB password is the same across all servers in the cluster.

Emergency Responder Exits After Starting

Problem    Emergency Responder exits after starting.

Possible Cause

You have configured Emergency Responder to use a TCP port that is already in use.

Solution    Check the Windows Event Viewer for the message "CER could not open socket at port peer-tcp-port, Exiting." If you see this message, change the Emergency Responder group configuration to use a different TCP port.

Emergency Responder Groups in Cluster Screen Does Not Load and Displays a Cannot Connect to Cluster DB Host Error

Problem    The Emergency Responder Groups in Cluster screen does not load, and exhibits the error "Cannot connect to cluster DB host."

Solution    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 Emergency Responder server groups in the cluster.

For more information, see Set Up Emergency Responder Cluster and Cluster DB Host.

Troubleshoot Cisco Unified Communications Manager Configuration Problems

These are some issues that you might encounter when the Emergency Responder communicates with Unified CM. Additional problems with symptoms that involve emergency call failures are discussed in the Troubleshoot Emergency Call Problems.

Emergency Responder Does Not Register with Route Points and CTI Ports

Problem    Emergency Responder does not register with the route points and CTI ports configured for its use.

Solution    Ensure that the route points and CTI ports are associated with the Unified CM Cisco Emergency Responder user (see Create Emergency Responder Cisco Unified Communications Manager User.) Ensure that the CTI Manager on the Unified CM server (or the DC Directory on a Windows-based Unified CM server) is running properly.

Cannot Delete Unified CM From Emergency Responder Configuration

Problem    When trying to delete a Unified CM from the Cisco Emergency Responder configuration, Emergency Responder displays the message "Phone tracking in progress."

Solution    You cannot delete a Unified CM server from the Emergency Responder 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 Unified CM user for Emergency Responder use and CTI ports and route points that must be assigned to the user before Emergency Responder tries to create a provider with the Emergency Responder cluster. Emergency Responder only registers the CTI ports and route points that are associated with the user when the provider is created. Any devices that you add to the user after starting Emergency Responder is not registered by Emergency Responder.

If you add devices to the Emergency Responder user in Unified CM, you can force Emergency Responder to recreate the provider using any of these techniques:

- Restart the Emergency Responder server.

- Delete the Unified CM server from the Emergency Responder configuration and reenter it.

- Change the backup CTI Manager setting for the Unified CM server in the Emergency Responder configuration and click Update to force Emergency Responder to log off the provider and to recreate it.

- Change the name of the user in Unified CM, or create a new user, and associate all devices with it. Then update the Emergency Responder configuration to use the new user.

Phone Moves Between Clusters

For additional information, see Track Phone Movement Across a Cluster.

Identify Emergency Responder Groups and Servers in Cluster

If you are connected to the administrator interface on a Emergency Responder server, you can view the details of the server and the Emergency Responder group's standby server by selecting System > Cisco ER Group Settings.

You can also identify the Emergency Responder groups and their Emergency Responder servers that are in the same Emergency Responder cluster. To view the other Emergency Responder groups in the cluster, select System > Cisco ER Groups in Cluster. From the Emergency Responder Groups in Cluster page, select the group that you want to view; and Emergency Responder displays the Emergency Responder servers that are in the group. To view the details for these servers, you must log into the Emergency Responder Administration interface running on one of the servers, select System > Cisco ER Groups in Cluster, then select the group that you want to view from the list of groups.

If you must uninstall a Emergency Responder group, first delete the group from the Emergency Responder cluster using this page. You must log in as a system administrator to delete the group. Deleting the group from the cluster only removes the entries for the group from the Emergency Responder Cluster DB; it does not remove Emergency Responder from the group's servers.

Manage Emergency Responder Server

When you install Emergency Responder, the Emergency Responder server is set up to automatically start whenever the computer is powered up or rebooted. However, you can stop and then restart an Emergency Responder server through the Emergency Responder Serviceability web interface without powering down or rebooting the computer.

Procedure

Step 1

Log in to the Emergency Responder Serviceability web interface and select Tools > Control Center. The Control Center Services page displays, showing all Emergency Responder 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.
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.

The following table explains the meaning of the icons that you see on the Control Center Services page.

Cisco Emergency Responder Control Center Icons

Icon

Meaning

The Emergency Responder server or the Emergency Responder Phone Tracking Engine is started and functioning normally.

The Emergency Responder server Emergency Responder Phone Tracking Engine was stopped by the administrator.

Troubleshoot 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.

Emergency Responder 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 can provide you with a list of errors, or you can see these when using your service provider's data upload software. You must fix any mistaken records and resubmit the ALI data export file. To fix the records, you need to manually edit the records in error.

The following sections describe the general procedure for fixing ALI data records, and explain how to edit the various types of NENA formatted files.

Fix ALI Data Records

To correct data errors that you might receive when uploading ALI records to your service provider, follow these steps.

Before You Begin
Obtain NENA Doc 02-010, refer the appropriate Exhibit for NENA version for the Recommended Formats and Protocols for Data Exchange, from NENA or your service provider. Service Provider may have additional requirements.

Procedure

Step 1

Check the error reports to determine the problems you encountered.

Step 2

In the Emergency Responder web interface, change the fields that were in error for the ERL or 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.

Step 3

Export the ALI data again (see the online help).

Step 4

If any of the records in error were new, you must change the database function for the records. Because Emergency Responder has already exported these records, Emergency Responder labels them as updates instead of new insertions. However, because these records failed on upload, the service provider's database views 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:

- NENA 2.0 and 2.1 File Formats

- NENA 3.0 File Formats

Step 5

Submit the edited file to your service provider.

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 (Exhibit 5.5 for Version 2.0 and Exhibit 5.9 for Version 2.1), 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.

The following table describes the fields you are most likely to edit. You should use the Emergency Responder web interface to change the other fields.

NENA 2.0 and 2.1 Common Fields

Field

Description

Function Code

Location: Byte 1.

Length: 1 character.

Description: The database function for the record. One of:

- I—Insert new ALI record

- C—Change 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.

- D—Delete the record. Emergency Responder only generates a deletion record once, in the export file created after you deleted the ALI from the Emergency Responder configuration. If you must regenerate the record, cut and paste it from the previous export file (and adjust the record count), or recreate the ALI in Emergency Responder, save it, export the data, then delete the ALI and export the data again.

Cycle Counter (sequence number)

Location: Byte 62 to 67.

Length: 6 characters.

Description: The sequence number of the file you are submitting to the service provider (for example, 1 or 2.) 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 or 2.) The number is right-aligned with leading spaces.

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 included 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 predefined character.

Use NENA Doc 02-010 (Exhibit 5.13 for Version 3.1), 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.

The file contains one header and one trailer record. The ALI data records are contained between these records.

The following table describes the fields that you are most likely to edit. You should use the Emergency Responder web interface to change the other fields.

NENA 3.0 Common Fields

Field

Description

Function Code

Tag: FOC.

Description: The database function for the record. One of:

- I—Insert new ALI record (FOCI)

- C—Change 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.

- D—Delete the record (FOCD). Emergency Responder only generates a deletion record once, in the export file created after you deleted the ALI from the Emergency Responder configuration. If you must regenerate the record, cut the version number and paste it from the previous export file (and adjust the record count); or recreate the ALI in Emergency Responder, save it, export the data, then delete the ALI and export the data again.

Cycle Counter (sequence number)

Tag: CYC.

Description: The sequence number of the file you are submitting to the service provider (for example, CYC1 or CYC2.) 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 that you are submitting to the service provider (for example REC1 or REC2.)

Call History Logs

Emergency Responder 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.

Emergency Responder maintains in its database a history of the emergency calls that have been placed. When the primary Emergency Responder server (Publisher) is not active, emergency calls are handled by the backup Emergency Responder 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 Emergency Responder servers.

To download these records, click the Download button at the top of the table displaying the call history. These records are downloadable in Excel (.xls) format.

Trace and Debug Information

When you contact Cisco Technical Support for help with a problem that you are having with Emergency Responder, Cisco might request that you collect trace and debug information.

Because collecting trace and debug information affects Emergency Responder performance, you should only turn on tracing and debugging at Cisco's request. The generated information is for Cisco's use in resolving product problems.

Enable Emergency Responder Trace and Debug Information

Procedure

Step 1

From the Emergency Responder web interface, select Cisco ER Group > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

From the left column, select the server from which you must collect debug or trace information.
Emergency Responder displays the settings for the server.

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_DATABASE—The database subsystem, covers the log information generated by the database access code.

- CER_REMOTEUPDATE—The remote update subsystem, which manages updates between servers.

- CER_PHONETRACKINGENGINE—The phone tracking subsystem, which runs the phone tracking and switch port and phone update processes.

- ER_ONSITEALERT—The onsite alert subsystem for notifying onsite alert personnel.

- CER_CALLENGINE—The call engine subsystem, which routes and processes calls.

- CER_SYSADMIN—The system administration web interface subsystem.

- CER_TELEPHONY—The telephony subsystem, used for interactions with Unified CM.

- CER_AGGREGATOR—The aggregator module covers all Emergency Responder server communication and data handling with the phone tracking engine. The module includes the search and lookup of tracked data for the subsystems such as cluster, Administration, Cisco IP SoftPhone, and call routing.

- CER_GROUP—The Emergency Responder server group subsystem used for communicating between servers within a group.

- CER_CLUSTER—The server cluster subsystem used for communicating between Emergency Responder groups in a cluster.

Step 4

Click Update to save and activate your changes.
Emergency Responder begins generating the requested trace and debug information.

Note:
The traces for Emergency Responder can be collected from either Emergency Responder Serviceability web interface or by using the CLI.

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. Click Update to complete the change.

Syslog Enablement

To collect trace and debug information, you must enable syslog for Emergency Responder.

To enable syslog for Emergency Responder, see Collect Information From Syslog.

Event Messages

You can view Emergency Responder event messages to help diagnose problems with the software by using the Emergency Responder Serviceability web interface.

For information about viewing Emergency Responder events, see Use Event Viewer.

For details about the Find and List Events page, see Event Viewer.

Performance Management

See the latest version of the Release Notes for Cisco Emergency Responder for supported platforms and their Emergency Responder scalability.

Emergency Responder performance can be affected if Emergency Responder is managing switches across a WAN link. Emergency Responder 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 Set Up SNMPv2 for more information.

Network Management Systems Integration

You can manage the status of the Emergency Responder server remotely using any SNMP-based network management system.

The following sections provide information to assist you in integrating Emergency Responder with network management systems.

Cisco Discovery Protocol Support

Cisco Emergency Responder 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 Emergency Responder server by listening to these periodic messages.

Using information provided through CDP, the SNMP-based network management server can detect the Cisco Emergency Responder server and build topology maps displaying the Cisco Emergency Responder server.

In addition to sending out CDP messages, the Cisco Emergency Responder server uses CDP to locate phones that support CDP. You must ensure CDP is enabled on your switches so that Cisco Emergency Responder can obtain this information through SNMP queries to the switches.

Emergency Responder Components

Cisco Emergency Responder supports the SYSAPPL-MIB that allows you to use any SNMP-based browser to remotely access information about the following Emergency Responder components:

- Cisco Emergency Responder Server

- CERServer.exe

- Cisco PhoneTrackingEngine

- CERPhoneTracking.exe

- MSQL Server-related Services

The SYSAPPL-MIB uses SNMP. Emergency Responder supports the following SYSAPPL-MIB tables:

- SysApplInstallPkgTable—Provides 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).

- SysApplRunTable—Describes the application starting time and run-time status.

- SysApplInstallElmtTable—Describes the individual application elements, or associated executables, which comprise the applications defined in the SysApplInstallPkgTable.

- SysApplElmtRunTable—Describes the processes, or executables, that are currently running on the host system.

Collect Information From Syslog

You can configure Emergency Responder to use Syslog output from Emergency Responder for use with other network management systems.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select enable in Enable Syslog.

Step 3

Enter the fully qualified DNS name of the server in the Syslog Server field, for example, server.domain.com.

Step 4

Click Update Settings to save your changes.
Emergency Responder immediately begins writing messages to syslog.

Data Backup and Recovery

Emergency Responder uses the Disaster Recovery System to backup and restore system data.

For information about using the Disaster Recovery System, see Configure Cisco Emergency Responder Disaster Recovery System

During a backup and restore procedure, you might encounter one of the following errors:

- Unable to send network request to master agent. This may be due to Master or Local Agent being down.

- Local Agent is not responding. This may be due to Master or Local Agent being down.

Check your Publisher and Subscriber services and confirm that your DRS Local and Master services are active and running.

Check your IPSEC certificates via the Cisco Emergency Responder OS Administration UI. Make sure these IPSEC-Trust certificates are not expired or corrupted. If they are expired or corrupted, regenerate these IPSEC certificates on all nodes and restart the Master and local agents.

Troubleshoot 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 Emergency Responder database are verified against the Emergency Responder database schema.

DMA Backup and Validation Failed

Problem    DMA backup and validation failed.

Solution    Go through the following check list:

- Check if MSDE is running. If the database is not running, the backup fails.

- 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.

DMA Backup Is Successful but Validation Failed

Problem    DMA backup is successful but the validation failed.

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 in the database before a migration to Emergency Responder can succeed.

The DMA Logs are in the following locations:

- exportdb.log and migratecCERCSV.log are 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

Solution    The validation log files are as follows:

- Solution    exportdb.log

- Solution    installdbw1.log

- Solution    installdbw1.log.err

- Solution    dbl_INSTALLEDBxxxxxx.txt

Troubleshoot Linux Upgrades

You might encounter certain problems when upgrading to future versions of Emergency Responder from your current version of Emergency Responder. This section explains what could cause these problems and the provides recommended actions.

No Valid Upgrade Options Found Error Appears on the First Page of Install/Upgrade Menu

Problem    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.

Solution    Verify that you are not trying to upgrade the Subscriber before upgrading the Publisher. When upgrading an Emergency Responder server group, you must always upgrade the Publisher first. Solution    Verify that the local or remote path that you have specified actually contains a valid, signed ISO image, having the extension .sgn.iso.

Incorrect User Name/Password Error Appears on the First Page of the Install/Upgrade Menu

Problem    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.

Solution    Verify that the username and password entered for the remote SFTP or FTP location are correct.

Checksum Values Do Not Match After Downloading ISO Image on Emergency Responder Server

Problem    After downloading the ISO image onto the Emergency Responder server, the checksum values do not match.

Solution    Download a fresh ISO image from Cisco.com and try the upgrade again.

Upgrade Cancelled and Warning Message Appears Prompting You to Reboot System

Problem    The upgrade was cancelled, but a warning message appears prompting you to reboot the system.

Solution    During the upgrade, certain services on the Emergency Responder server could have been stopped, depending on when the upgrade was cancelled. In this case, it is highly recommended that you reboot the server.

Appendix A. Cisco Emergency Responder Administration Web Interface

Server Groups in Cluster

The Emergency Responder Server Groups in Cluster page appears when you choose System > Cisco Emergency Responder Groups in Cluster.

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the Emergency Responder Server Groups in Cluster page to view the Emergency Responder groups that form an Emergency Responder cluster. You can view which Emergency Responder servers belong to each Emergency Responder group within the cluster. You can click on the link for the remote server groups in an Emergency Responder cluster (select either the primary server or the backup server) to go directly to the Emergency Responder interface for these servers.

The following table describes the Emergency Responder Server Groups in Cluster page.

Cisco Emergency Responder Server Groups in Cluster Page

Field

Description

Notes

Emergency Responder Groups

Emergency Responder Groups list

A list of the Emergency Responder server groups that are pointing to the same cluster database host.

Click a group name to view the servers in the group.

The Emergency Responder cluster consists of this set of Emergency Responder groups. You create the cluster when installing Emergency Responder servers. See Installation on a New System.

Servergroup Details

Emergency Responder Group Name

The name of the server group.

Click the server group name to display the servers in that group in the Servergroup Details section of page.

Primary Host Name

The DNS host name or IP address of the primary server in the group.

Click this host name (except for the local server group) to open the Emergency Responder administration page for that server in a new window.

Standby Host Name

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 Emergency Responder administration page for that server in a new window.

Delete button

Click Delete to remove the Emergency Responder group you are viewing from the Emergency Responder cluster.

Only system administrators can delete a Emergency Responder group from the cluster.

Delete a group from the cluster before you uninstall a Emergency Responder group.

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page— English (US), French (Canada) or Spanish (Spain).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Telephony Settings

The Telephony Settings page appears when you choose System > Telephony Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Telephony Settings page to define the telephone numbers and telephony ports used by the Emergency Responder group.

The following table describes the Telephony Settings page.

Telephony Settings Page

Field

Description

Notes

Specify telephony attributes

Route Point for Primary Emergency Responder Server

The CTI route point that the primary server should use, such as 911.

See Create Emergency Call Route Points for more information.

Route Point for Standby Emergency Responder Server

The CTI route point that the standby server should use, such as 912. Configure this number as the call forward number for the primary emergency number.

See Create Emergency Call Route Points for more information.

PSAP Callback Route Point Pattern

CTI route point that 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.

For more information, see Create Emergency Call Route Points.

ELIN Digit Strip Pattern

Digits to strip from the beginning of the PSAP Callback Route Point Pattern, for example, 913. The number that results from stripping the pattern should be the ELIN numbers that the PSAP can use to call into your network.

This string must be part of the PSAP Callback Route Point Pattern.

UDP Port Begin

Port numbers that are used by CTI ports during their registration.

The range is 1024 to 65535.

Inter-Emergency Responder Group Route Pattern

Route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

The pattern can only consist of numbers and dots.

For a more detailed explanation of this number, see Create route patterns for Inter-Cisco Emergency Responder Group Communications.

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 Emergency Responder.

The ToS value entered here only applies to the RTP packets sent by Emergency Responder for the onsite audio alert feature.

Onsite Alert Prompt Repeat Count

Number of times the prompt is played on the onsite alert phone.

Use IP Address from call signaling

If this parameter is enabled, Emergency Responder obtains the IP address of the phone from JTAPI. This parameter is used to route the call. If an IP subnet is configured for the phone, this parameter setting takes precedence over any other manual configuration.

If this parameter is disabled, Emergency Responder uses the manual configuration of the phone to route the call.

This field is applicable only if Emergency Responder is configured with Cisco Unified Communications Manager 6.x and above.

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado Route Pattern Settings

Intrado Route/Translation Pattern

Enter the route patterns or translation pattern for an Intrado emergency response location (ERL). An Intrado ERL is an ERL that is serviced by Intrado. Intrado ERL only lists the route patterns that have been configured on this page. You can add new route patterns or translation patterns, or you can update or remove existing route patterns or translation patterns.

To add a new route or translation pattern, click on the text box, enter the route pattern, including numbers and wildcard (do not use spaces), and click Add.

To update an existing route pattern, click on the appropriate route pattern, modify the pattern, and click Update.

To remove an existing route pattern, click on the appropriate route pattern and click Remove.

To cancel your existing changes and go back to the last saved settings, click Cancel Changes.

Server Settings for Emergency ResponderServerGroup

The Server Settings for Emergency ResponderServerGroup page appears when you choose System > Server Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Emergency Responder servers are inserted in the Emergency Responder group when the Emergency Responder services are started. (See Installation on a New System.)

Use the Server Settings for Emergency ResponderServerGroup page to update server settings, for example, to change the server name or to change the trace and debug settings, or to delete servers.

Note

You cannot modify the host name of the server.

The following table describes the Server Settings Emergency ResponderServerGroup page.

Server Settings for the Emergency ResponderServerGroup Page

Field

Description

Notes

Status

Displays the status of the Server Settings Emergency ResponderServerGroup page.

Select Server

Server

List of servers you have already created. Click on a server name to see the settings for that server.

You can configure a maximum of two servers per server group.

Modify Server Settings

Server Name

The name of the server.

Change this server name field to any desired value.

Host Name

The DNS name of the Emergency Responder server.

This field cannot be modified.

Debug Package List

A selection of subsystems for which you must collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Debug Package List.

Clear All button

Clears all selected subsystems in the Debug Package List.

Trace Package List

A selection of subsystems for which you must collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's 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.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Trace Package List.

Clear All button

Clears all selected subsystems in the Trace Package List.

Update Settings button

Click Update when viewing an existing server's settings to save changes you make to the settings.

Only available when viewing the settings of an existing server.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

License Manager

The License Manager page appears when you choose System > License Manager.

Authorization Requirements

You must have system administrator authority to access this page.

Description

The License Manager Page provides the summary and detailed information on system license usage, as reported to the Prime License Manager.

License Manager Page

Field

Description

Status

Displays alarms or licensing alerts.

See License Manager Status Messages for further information on status messages. See License Compliance for further information on license compliance and noncompliance

Details of Emergency Responder Licenses

Displays the current license requirement for the server group:

- Number of phones discovered

- Number of phones manually configured

- Total number of users being tracked currently

Prime License Manager

Shows if the Prime License Manager manages the Emergency Responder Server Group.

If the Server Group has been added to an Prime License Manager product inventory, a link is provided to the Prime Collaboration License Manager server login page.

Emergency Responder must connect with the Prime License Manager at least once every 24 hours. This connection and communications of license requirements from the Emergency Responder and Prime License Manager is called synchronization.

The Enterprise License Manager status shows the time and date stamp of the last successful synchronization between the Emergency Responder and Prime License Manager.

Email Alert Settings

The Email Alert Settings page appears when you choose System > Mail Alert Configurations.

Authorization Requirements

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 Emergency Responder sends email alerts. Use the check box to the right of each parameter to enable (check) or disable (uncheck) email alerts for that parameter. Check the Include event viewer contents in mail check box if you want to include the details from the event viewer in the email message.

The following table describes the Email Alert Settings page.

Email Alert Settings Page

Field

An email alert is sent when:

Discovery Parameters

Discovery Engine Registration Failed

The Discovery Engine fails to register

Discovery Engine goes out of connection

The Discovery Engine loses connection

For unreachable devices during recovery

Devices such as switches and Cisco Unified Communications Managers become unreachable

Emergency Call Routing Parameters

Call information

A 911 call is placed

Call routing session ended due to problems

Call routing is stopped due to any of these reasons:

- Invalid CMC

- Invalid FAC

- FAC and CMC needed

- CMC needed

- FAC needed

- RESOURCE_BUSY

Rerouting of call

An emergency call is rerouted

Routing failure

Call routing fails

Route Point out of Service

The route point goes out of service

Cluster Parameters

Cluster DB Failure

The server cannot communicate with the cluster database host

Intra Cluster Failure

The intra-cluster communication to a server group in the cluster fails

Misc Parameters

Subscriber becomes active

The Subscriber becomes active

Publisher comes back online

The Publisher comes back online

Not able to get the JTAPI Provider

When Emergency Responder cannot get the JTAPI provider

Available user licenses get exhausted during phone tracking

When the number of user licenses are exhausted during phone tracking

Switch Port location change reporting

When you enable switch port change reporting for phones

Suppress IP Communicator location change reporting

When you filter Cisco Unified IP Communicator from the location change reporting email alerts

Update Settings button

Updates the email alert settings

Cancel Changes button

Cancels changes made to the email alert settings

Add Subscriber

The Add Subscriber page appears when you choose System > Add Subscriber.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add Subscriber page to add a subscriber server to a Emergency Responder server group. After adding the subscriber information, you must enter the correct publisher server information when prompted during installation.

Before You Begin

You must first configure a Publisher server before configuring a Subscriber server.

The following table describes the Add Subscriber page.

Add Subscriber Page

Field

Description

Add Subscriber

HostName

Host name of the subscriber server.

Insert button

Click Insert to add the new subscriber server.

Cancel Changes button

Removes input form the Add Subscriber page.

Configured Servers

A list of all currently configured servers, showing the host name and IP address of each server.

Intrado VUI Settings

The Intrado VUI Settings page appears when you choose System > Intrado VUI Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado VUI Settings page to enter the account information that is required for Emergency Responder to interoperate with Intrado Validation and Update Interface. After entering the required information, you can test the connectivity to Intrado from this page.

The following table describes the Intrado VUI Settings page.

Intrado VUI Settings

Field

Description

Status

Displays status messages.

Intrado VUI Settings

Upload Certificate

Uploads the certificate from your local drive to the Emergency Responder server.

To upload a certificate, follow these steps:

1. Click Upload Certificate.

An Upload Certificate window appears.

2. Click the Browse button to locate the certificate file on your local machine.

3. Click the Upload button to upload the certificate file.

Validate Certificate

Intrado Certificate Password

The password that was generated with this certificate.

VUI URL

VUI URL is provided by Intrado.

Test and Validate Certificate

Use this button to test the validity of your certificate.

Configure Account Details

VUI Schema URL

The VUI Schema URL provided by Intrado.

Intrado Account ID

Your Intrado Account ID provided by Intrado.

Max VUI Connections

The maximum number of simultaneous VUI connections that Emergency Responder allows across the Server group.

Test Connectivity

Use this link to verify whether Emergency Responder can successfully connect to Intrado VUI.

Delete Account

Deletes an existing Intrado account from the Emergency Responder database.

Update

Click Update to save the changes you made on this page.

Cancel

Click Cancel to change the fields on this page back to the last saved settings.

Onsite Alert Settings

The Onsite Alert Settings page appears when you choose ERL > Onsite Alert Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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. Emergency Responder alerts the assigned personnel when an emergency call is made within the zone.

The following table describes the Onsite Alert Settings page.

Onsite Alert Settings Page

Field

Description

Notes

Add New Onsite Alert Contact

Onsite Alert ID

The identifier for the onsite alert contact. The identifiers you use should be based on your site identification strategy (for example, security ID or badge number). This field is used throughout Emergency Responder to identify the contact; for example, you select from Onsite Alert IDs when assigning contacts to zones. The Onsite Alert ID cannot be modified after you have saved it.

Use a naming strategy meaningful to your organization, but which is also useful when configuring zones in Emergency Responder.

Onsite Alert Name

The name of the onsite alert contact.

Onsite Alert Number

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.

When Emergency Responder gets an emergency call from an ERL, it calls the onsite alert number of the contact for the ERL and plays a prerecorded message that includes the phone number from which the emergency call was placed.

Onsite Alert Email Address

The email address for the onsite alert contact, for example, email@domain.com.

When Emergency Responder 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 Pager Address

The pager email address for the onsite alert contact, for example, <pager_number>@domain.com.

You can limit the size of the message that is sent to the pager by configuring the fields on the Pager Alert Setting Page. See Pager Alert Settings.

Available User Group

The User Group which will receive the specific web alert from the associated ERL. By default Emergency Responder User Group is selected, which has all users.

The users can view all alerts in the system by selecting ALL on the Web Alert page.

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.

Cancel Changes button

Click Cancel Changes to cancel any changes made to this page.

Available Onsite Alerts

Section of the page that displays onsite alert contacts that have already been configured. For configured onsite alert contacts, the following information is displayed:

- Onsite Alert ID

- Onsite Alert Name

- Onsite Alert Number

- Onsite Alert Email Address

- Onsite User Group

To change an entry, click the entry or click the Edit icon; the person's 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.

If no contacts have previously been configured, this section is blank.

You cannot modify a contact's Onsite Alert ID.

Before you can delete the entry, you must update the ERLs to which the person is assigned to remove the person from the ERL.

Add New button

Click Add New to add another contact.

Update button

Click Update when viewing an existing contact's information to save changes you make to the information.

Only available when viewing the information for an existing contact.

Pager Alert Settings

The Pager Alert Settings page appears when you choose ERL > Pager Alert Configurations.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Pager Alert Configurations page to limit the size of system wide pager messages by selecting the fields that are sent to the pager and by editing the labels for those fields.

The following table describes the Pager Alert Settings page.

Pager Alert Settings

Field

Descriptions

You can limit the size of the pager message that is sent by selecting the following fields and editing the labels are associated with those fields:

- Extension

- ERL

- Location

- Time

- Server

To select the fields that you would like to display on the pager, check the box adjacent to the field.

To edit the label that you want to send to the pager, click on the text box for that field.

Update Settings Button

Click Update Settings to save changes that you made.

Restore Defaults Button

Click Restore Defaults to restore the default pager and label settings.

Send Sample Message to a pager

To send a test message to your pager, enter a pager address in the text box and click the Send Test Message button.

Conventional ERL

The Conventional ERL page appears when you choose ERL >Conventional ERL.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create are 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.

The following table describes the Find and List ERLs page.

Find and List ERLs Page

Field

Description

Notes

ERL Search Parameters

Find Conventional ERL where...

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:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL 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 is 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 remains there until it is modified.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Configure Default ERL

Click Configure Default ERL to configure a default ERL

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Add New ERL

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. If the ERL name is First Floor, the page that appears is titled ERL Information for First Floor.

The Add New ERL and ERL Information for ERL Name pages are essentially the same, as follows:

- The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL). 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 choose ERL > Conventional ERL).

Note

You cannot use a default ERLs as a Test ERL. The Test ERL check box is not available on the ERL Information for Default page.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this 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.

Emergency Responder allows you to select the ERL as a Test ERL.

Use the Find ERL Data page to view or update an existing ERL.

See ELIN Numbers Emergency Calls and PSAP Callbacks for information about configuring the ELIN numbers in Cisco Unified Communications Manager.

If you want to route emergency calls to onsite security instead of the PSAP, see Set Up ERLs for Non-PSAP Deployment for the Route/Translation Pattern and ELIN settings.

The following table describes the Add New ERL and ERL Information pages.

Add New ERL and ERL Information Pages

Field

Description

Notes

ERL Settings

ERL Name

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 sees 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 an ERL naming strategy.

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 are trimmed.

Description

Enter a description of the new ERL (optional).

Test ERL (Used for Synthetic Testing)

Check this check box if this ERL is used for testing.

See Set Up Test ERLs.

This setting is not available on the ERL Information for Default; default ERLs may not be used as test ERLs.

ELIN Settings

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 that 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 cannot 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.

Note:
Emergency Responder restricts the association of an ELIN with an ERL if the ELIN has been configured as a DID Number for an Off-Premises Emergency Responder user. Emergency Responder does not impose this restriction if the DID Number belongs to a user who has never associated an off-premises location in Emergency Responder.

Route/Translation Pattern

The phone number, defined as a route pattern in Cisco Unified Communications Manager, that is configured to use the gateway that 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.

ELIN Number

The unique phone number which the PSAP can use to locate a caller 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, for the North American Numbering Plan, such as 4085551212, or an E.164 Number including country code such as +14085551212. The number can only contain numbers, a plus sign (+), single hyphens, dots, or parentheses.

An ELIN when being sent as ANI to PSAP through outgoing Gateway must be a DID (direct inward dial) number provided by your service provider.

Add button

To add a route point and ELIN combination, enter the information and click Add.

Update button

To change an existing combination, select it in the list, change the information in the edit boxes, and click Update.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact's ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

ERL Address

ALI Details button

Click ALI Details to view or change the automatic location information (ALI) of an ERL. The ALI provides detailed information about the location of the ERL, such as street address and phone number.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

Export ERL Data

The Export ERL Data page appears when you click the Export link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder server.

To create a file to send to your service provider to update their ALI data, see Export PS-ALI Records.

The following table describes the Export ERL Data page.

Export ERL Data Page

Field

Description

Select Export Format

The file format to be used in the export file. For ERL data, either csv (comma-separated value) or XML.

Enter Export File Name

The name of the file you want to create. Do not include a file extension.

Export button

Click Export to create the export file.

Close button

Click Close to close the window.

Import ERL Data

The Import ERL Data page appears when you click the Import link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import ERL Data page.

Import ERL Data Page

Field

Description

Select Import Format

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

Select the file from which you want to import ERL data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add ERL data from the import file to the Emergency Responder database.

Note:
The imported ERL data overwrites conflicting data in the Emergency Responder database.

Close button

Click Close to close the window.

Off-Premises ERL

The Find Off-Premises ERL Data page appears when you choose ERL > Off-Premise ERL > Search And List.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Off-Premise ERL Data page to define the emergency response locations (ERLs) for individuals with phones that are located outside of the corporate network.

The following table describes the Find and List Off-Premise ERLs page.

Find Intrado ERL Data (Off-Premise)

Field

Description

Notes

ERL Search Parameters

Find Off-Premises ERL where...

Select search criteria and click Find to list existing Off-Premise ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

Add New ERL

Click Add New ERL to create a new ERL.

Add New ERL

The Add New ERL (Off-Premise phones) page appears when you choose Add New ERL on the Find Intrado ERL Data page (opened when you choose ERL > Off-Premise ERL> Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New ERL page to create a new emergency response location (ERL) for Off-Premise phones. Alternatively, you can create or update many ERLs at once by importing predefined ERL information from a separate file.

Use the Find ERL Data page to view or update an existing ERL.

The following table describes the Add New ERL (Off-Premise Phones) page.

Add New ERL (Off-Premise Phones)

Field

Description

Note

ERL Settings

ERL Name

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 sees 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.

Work with your security team to develop an ERL naming strategy.

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 is trimmed.

Description

Enter a description of the new ERL (optional).

Route/Translation Pattern 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.

Add button

To add a route point, choose a route point from the drop-down list and click Add.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

Off-Premise ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Off-Premise ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about off-premise telephone number record update transactions that were flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for off-premise telephone number records with errors.

The following table describes the Secondary Status for Off-Premise phones.

Secondary Status (Off-Premise Phones)

Field

Description

Find DIDs where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

View ALI Discrepancies for a Specific ELIN

Choose ERL > Intrado ERL > View ALI Discrepancies and search for discrepancies. The View ALI Discrepancies for a specific ELIN page appears when you select a specific ELIN from the results.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies for a Specific ELIN page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies for a specific ELIN page.

ALI Discrepancies for Specific ELIN

Field

Description

View Intrado ALI Discrepancies

ALI Fields

List of ALI field information from the local Emergency Responder database and from Intrado database:

- House Number

- House Suffix

- Street Name

- Prefix Directional

- Street Suffix

- Post Directional

- Community Name

- State

- Main NPA

- Class of Service

- Type of Service

- Exchange

- Customer Name

- Order Number

- Extract Date

- County ID

- Company ID

- Zip Code

- Zip Code Extension

- Customer Code

- Comments

- Longitude

- Latitude

- Elevation

- TAR Code

- Location

- Reserved

Save button

Click Save to save your changes in the local Emergency Responder database.

Save Intrado ALI Info button

Click Save Intrado ALI Info to update the Intrado VUI database.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Close button

Click Close to close the window.

ERL Migration Tool

The ERL Migration Tool page appears when you choose ERL > ERL Migration Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the ERL Migration Tool page to migrate ERLs from conventional ERL data to Intrado ERL data and vice versa.

The following table describes the ERL Migration Tool page.

ERL Migration Tool

Field

Description

Status

Displays status messages

ERL Search Parameter

Find

Select search criteria and click Find to list either existing Conventional ERLs or Intrado ERLs.

From the search results list, you can select the ERLs that you want to migrate

Migrate to Intrado ERL Button

When you search for Conventional ERLs, you can select the ERLs that you want to migrate to Intrado.

When you click the Migrate to Intrado ERL button, you can select an Intrado route point for all the selected ERL.

Migrate to Regular ERL

When you search for Intrado ERLs, you can select the ERLs that you want to migrate to a conventional ERL data.

When you click the Migrate to Regular ERL button, you can enter a route point, and specify whether the ERL is a test ERL and test the ERL.

SNMP Settings

The SNMP Settings page appears when you choose Phone Tracking > SNMPv2 Settings or Phone Tracking > SNMPv3 Settings.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the SNMPv2 Settings page or the SNMPv3 Settings page to define the SNMP read community string used by your switches.

SNMP v2 Settings Page

Use the information in the following table to configure the SNMPv2 Settings.

SNMP v2 Settings Page

Field

Description

Notes

Add SNMPv2 Community Setting

IP Address/Host Name

The IP address or host name of a switch whose SNMP read community string you are defining.

If you use the same read community string for all switches, you only need to define one entry: *.*.*.*.

If you use different read community strings for sets of switches, you can define each set, using variables and ranges. For example, if you have 10 switches from 10.1.115.0 to 10.1.125.0, you can use 10.1.115-125.0 as the IP address. You can also mix ranges and variables, such as *.*.115-125.*.

You are not defining your switches on this page, you are only associating IP address patterns to read community strings.

Emergency Responder only tries to use the string with the specific switches you identify on the LAN Switch Details page. See LAN Switch Details for more information.

If two or more patterns match an IP address, Emergency Responder uses the SNMP string associated with the most closely matching pattern.

Timeout

The time, in seconds, in which Emergency Responder should consider an attempted SNMP connection to a switch to have failed. See the explanation of Retries for more information.

Default is 10 seconds. The optimal value is 10 to 15 seconds.

Maximum Retry Attempts

The number of times Emergency Responder should attempt to contact a switch.

With each retry, the previous timeout is multiplied by 2, to ensure that the switch has enough time to respond. For example, if you specify 10 for timeout, the first attempt times out in 10 seconds, the second attempt times out in 20 seconds, the third attempt times out in 40 seconds, and so forth.

Default is 2 retries. This number does not include the initial attempt; that is, if retries is 2, Emergency Responder attempts to contact a switch up to 3 times (the initial attempt plus 2 retries).

The optimal value is 2 to 3 retries.

Read Community

The SNMPv2 read community string for the switch.

Default is public for any IP address not covered in the SNMPv2 settings list.

Insert button

Click Insert to add the entry to the list of SNMP settings.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

SNMPv2 Settings

A list of SNMPv2 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.

Add New button

Click Add New to add another SNMPv2 setting.

Update button

Click Update to save changes you make to an existing SNMPv2 setting.

Only available when viewing an existing setting.

SNMP v3 Settings Page

Use the information in the following table to configure the SNMP v3 Settings.

SNMP v3 Settings Page

Field

Description

Notes

Add SNMPv3 User Details

User Information

IP Address/Host Name

Enter the IP address or host name of the Cisco Unified Communications Manager or LAN switch.

You can use an asterisk (*) as a wildcard character.

You can also use a range of number for octets, such as 15 to 30.

User Name

Enter the user name configured on Cisco Unified Communications Manager or LAN switch.

The name can contain up to 32 characters and can contain any combination of alphanumeric characters, hyphens (-), and underscore characters (_).

Authentication Information

Password

To enable authentication, check the Authentication Required check box; in the Password and the Reenter Password fields, enter the password for the user configured on the Cisco Unified Communications Manager or LAN switch.

Protocol

Choose the appropriate protocol as configured for the user on Cisco Unified Communications Manager or LAN switch.

Privacy Information

Password

If you selected the Authentication Required check box, you can specify the privacy information.

To require privacy, select the check box, enter the password in both the Password and the Reenter Password fields for the user configured on the Cisco Unified Communications Manager or LAN switch.

Protocol

Choose the appropriate protocol as configured for the user on Cisco Unified Communications Manager or LAN switch.

Other Information

Timeout (in seconds)

The length of time that an attempted SNMP connection remains idle before it is considered to have failed.

For more information, see the explanation for Maximum Retry Attempts.

The default value is 10 seconds. The optimal value is 10 to 15 seconds.

Maximum Retry Attempts

The number of times Emergency Responder attempts to contact a Cisco Unified Communications Manager or a switch.

With each retry, the previous timeout is multiplied by two to ensure the switch has time to respond. For example, if you specify a Timeout value of 10 seconds, the first attempt times out in 10 seconds, the second attempt times out in 20 seconds, and the third attempt times out in 40 seconds.

The default value is two. But the optimal value is two to three retries.

The Maximum Retry Attempts does not include the initial attempt. For example, if Maximum Retry Attempts is set to two, Emergency Responder attempts to contact a switch three times - the initial attempt plus two retries.

Phone Tracking Schedule

The Phone Tracking Schedule page appears when you choose Phone Tracking > Schedule.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Phone Tracking Schedule page to define the Cisco Emergency Responder (Emergency Responder) schedule for updating phone and switch information from the network. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Cisco Unified Communications Manager to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone ERL.

- Switch Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Ensure that your ERL administrator updates the ERL assignment for new ports.

The following table describes the Phone Tracking Schedule page.

Phone Tracking Schedule Page

Field

Description

Notes

Incremental Phone Tracking

Incremental Phone Tracking Interval

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.

The default is 30 minutes.

The range of the interval that can be defined is 5 to 300 minutes.

Add New Schedule

Enter the schedule that you want to add:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

We recommend that you run the switch port and phone update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Insert button

Click Insert to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes that you make to the schedule.

Only available when viewing an existing schedule.

Switch-Port and Phone Update Schedule

The list of schedules you have defined.

To change a schedule, click the Hour link, the Minute 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.

If any schedules overlap, only one schedule is run.

Add New button

Click Add New to add another schedule.

Cisco Unified Communications Manager Clusters

The Cisco Unified Communications Manager Clusters page appears when you choose Phone Tracking > Cisco Unified Communications Manager.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Cisco Unified Communications Manager Clusters page to identify the Cisco Unified Communications Manager clusters whose emergency calls this Emergency Responder group handles. Only assign a Cisco Unified Communications Manager cluster to a single Emergency Responder group. Emergency Responder gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones.

The following table describes the Cisco Unified Communications Manager Clusters page.

Cisco Unified Communications Manager Clusters Page

Field

Description

Notes

Add New Cisco Unified Communications Manager Cluster

Cisco Unified Communications Manager

The IP address or DNS name of a Cisco Unified Communications Manager server that is running Cisco Unified Communications Manager and SNMP services.

Only add one server per Cisco Unified Communications Manager cluster— Emergency Responder can identify the other servers in the cluster. The Cisco Unified Communications Manager server you specify represents the cluster in which it is a member.

When viewing a previously defined Cisco Unified Communications Manager server, Emergency Responder 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.

After the IP address or DNS name has been configured, it cannot be modified.

CTI Manager

The IP address or DNS name of the CTI Manager used by the specified Cisco Unified Communications Manager server.

CTI Manager User Name

The name of the user created in the Cisco Unified Communications Manager server for Emergency Responder use.

This user must have specific characteristics and device assignments. See Create Emergency Responder Cisco Unified Communications Manager User 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, Emergency Responder calls the onsite alert personnel for the originating ERL using the telephony ports you configure here.

You must first create this port in Cisco Unified Communications Manager. See Create Required CTI Ports for more information.

Number of Telephony Ports

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 Emergency Responder can make to onsite alert personnel.

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, Emergency Responder uses 3000, 3001, 3002, and 3003.

Enable Secure Connection

Enable Secure Connection check box

Check this check box to enable a secure connection. You can enter data in the other fields of this section only if you have enabled Secure Connection.

TFTP Server IP Address

The IP address of the TFTP server.

TFTP Server Port

The port of the TFTP server.

Backup TFTP Server IP Address

The IP address of the backup TFTP server, for the Unified CM node being added.

CAPF Server IP Address

The IP address of the CAPF server.

CAPF Server Port

The port of the CAPF server.

Instance ID for Publisher

The instance ID for the Publisher node.

Secure Authentication String for Publisher

The secure authentication string for the Publisher node.

Instance ID for Subscriber

The instance ID for the Subscriber node.

Secure Authentication String for Subscriber

The secure authentication string for the Subscriber node.

AXL Settings

AXL Username

The username for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Password

The password for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Port Number

The port number that is used by the application on Cisco Unified Communications Manger. The default value is 8443.

SNMP Settings

Use SNMPv3 for discovery

Check this check box if the Cisco Unified Communications Manager has SNMPv3 enabled and you want Emergency Responder to use SNMPv3 for discovery.

Insert button

Click Insert to add the new Cisco Unified Communications Manager server to the list of servers.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

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.

Cisco Unified Communications Manager Clusters

Add New button

Click Add New to add another Cisco Unified Communications Manager server.

Cisco Unified Communications Manager list

A list of Cisco Unified Communications Manager servers defined for this Emergency Responder group. Click a server link or the Edit icon to view and modify the Emergency Responder configuration for the server. Click the Delete icon to delete the server.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Export LAN Switch

The Export LAN Switch page appears when you click Export in the LAN Switch Details page (opened when you choose Phone Tracking > LAN Switch Details).

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Export LAN Switch page to create a file containing the Emergency Responder switch configuration.

If you must update several switch entries in Emergency Responder, 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 Download File for more information.

The following table describes the Export LAN Switch page.

Export LAN Switch Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma- separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a LAN switches configuration file and click Download to download the file to your local system.

Import LAN Switch

The Import LAN Switch page appears when you click Import in the LAN Switch Details page (opened when you choose Phone Tracking > LAN Switch Details).

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Import LAN Switch page to add several switches at once to the Emergency Responder 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 Upload File for more information.

The following table describes the Import LAN Switch page.

Import LAN Switch Page

Field

Description

Select Import Format

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

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.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the information in the import file to your Emergency Responder configuration.

Emergency Responder 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 choose OK. If you choose Cancel, Emergency Responder 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 Manually Run the Switch-Port and Phone Update Process.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Run Switch-Port and Phone Update

When you choose 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 Emergency Responder."

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Run Switch-Port and Phone Update page to run manually the switch port and phone update process.

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Export Switch Ports

The Export Switch Ports page appears when you click Export in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports ).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Switch Ports page to create a file containing the Emergency Responder switch port configuration.

If you must 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 Download File for more information.

The following table describes the Export Switch Ports page.

Export Switch Ports Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma-separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Import Switch Ports

The Import Switch Ports page appears when you click Import in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Import Switch Ports page to add or update several switch port configurations at once to the Emergency Responder configuration. Switch port configurations are mappings of ports to ERLs.

To create the switch port import file, follow these steps:

1. Export the switch port details.

2. Modify the ERK field of these records and save the file.

3. 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 Upload File for more information.

The following table describes the Import Switch Ports page.

Import Switch Ports Page

Field

Description

Select Import Format

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 Emergency Responder, modify the export file using a spreadsheet program, and then import the modified file.

Note:
See Export Switch Port Information for information about exporting switch port information.

Select File to Import

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the information in the import file to your Emergency Responder configuration. ERL assignments in the import file override assignments that already exist in the Emergency Responder configuration.

Note:
Port ERL configurations are only updated if Emergency Responder has discovered the port before you import the port configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Find and List IP Subnets

The Find and List IP Subnets page appears when you choose ERL Membership > IP Subnets.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List IP Subnets page.

Find and List IP Subnets Page

Field

Description

IP Subnet Search Parameters

Find IP Subnets where...

To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.

IP Subnets

IP Subnets list

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 preceding records or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field 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 of the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See IP Subnet Phones.

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

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.

Add New IP Subnet

Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See Configure IP Subnet for more information

Export

Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See Export IP Subnets for more information,

Import

Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See Import IP Subnets for more information,

Configure IP Subnet

To reach the Configure IP Subnet page, choose ERL Membership > IP Subnets and click on the Add New IP Subnet link. The Configure IP Subnet page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Configure IP Subnet page to manually define an IP subnet and its ERL. You must manually define an IP Subnet if Emergency Responder cannot automatically track the type of phone. One example is if the phone is wireless. See Network Hardware and Software Requirements for information about phone support.

You can choose not to track the phones in an IP Subnet by checking the check box Do not track phones under this IP subnet. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

The following table describes the Configure IP Subnet page.

Configure IP Subnet Page

Field

Description

Add New IP Subnet

Subnet ID

The IP address of the subnet you want to define.

Subnet Mask

The mask of the subnet you want to define.

Do not track phones under this IP subnet

Check this check box if you do not want this IP subnet and the underlying phones tracked by Cisco Emergency Responder. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

Location (optional)

The location of the new IP subnet.

ERL Name

The ERL to assign to the subnet. Type in a valid ERL name or click Search ERL to find and select the ERL.

Insert button

Click Insert to add the subnet.

When you click Insert, Emergency Responder asks if you want to run the switch port and phone update process on the switch immediately. Click OK to run the process now, or click Cancel to add the IP subnet to the configuration without running the process immediately.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

IP Subnet Phones

The IP Subnet Phones page appears when you choose ERL Membership/ IP Subnets and click the View Phones icon in any records returned by the IP Subnet Search.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the IP subnet Phones page to view all the IP subnet phones discovered by Emergency Responder.

The IP subnet phones page displays the subnet ID, the subnet mask for each IP subnet and lists all the phones tracked in that IP subnet, and when the last phone was tracked.

Export IP Subnets

To reach the Export IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Export link. The Export IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export IP Subnets page to create a file containing the Emergency Responder Export IP Subnet configurations.

If you must 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 Download File for more information.

The following table describes the Export IP Subnets page.

Export IP Subnets Page

Field

Description

Select Export Format

Select the format used in the file that 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

Click Export to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Import IP Subnets

To reach the Import IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Import link. The Import IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import IP Subnets page.

Import IP Subnets Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Unlocated Phones

The Unlocated Phones page appears when you choose ERL Membership > Unlocated Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Unlocated Phones page to identify phones that are registered with Cisco Unified Communications Manager, but which Emergency Responder cannot locate. A phone can become unlocated for several reasons:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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.

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you might have to manually assign a phone to an ERL on this page. See Unlocated Phones for troubleshooting information.

The following table describes the Unlocated Phones page.

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 pull-down 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.

Assign ERL

To assign the ERL, select the phones by checking the check box next to the phones, click Search ERL to find and select the ERL, and click Assign ERL.

Unassign ERL

To unassign a ERL, select the phones and click on Unassign ERL button.

List of unlocated phones

A list of the phones Emergency Responder could not assign to a specific ERL. The following information is displayed:

- Emergency Responder Group

- Phone IP Address

- Phone Mac Address

- Phone Extension

- Assigned ERL

- Effective ERL

- ERL Rule

If the phone has moved to a switch served by a different Emergency Responder group, the Emergency Responder group name is shown for the phone in the list.

Note:
If there are a lot of unlocated phones, Emergency Responder 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.

Export Unlocated Phones

To view the Export Unlocated Phones page, choose ERL Membership > Unlocated Phones and click Export.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Unlocated Phones page to do one of two actions:

- Create a file containing the Emergency Responder Export Unlocated Phones.

- Use the Download utility to download a file containing the Emergency Responder Export Unlocated Phones.

The following table describes the fields found on the Export Unlocated Phones page.

Export Unlocated Phones Page

Field

Description

Select Export Format

Select the file format that matches the file being imported.

After you select the format, click View Sample File to see an example of the expected format and sequence of values. Use this example when creating your imported file.

Enter Export File Name

The name of the file that you want to create. Do not include the file extension.

Export button

Click Export to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pulldown menu to select a file. Click Download to download the file.

Find and List Manually Configured Phone

The Find and List Manually Configured Phones page appears when you choose ERL Membership > Manually Configured Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Manually Configured Phones page.

Note

When you are performing this search as part of an E.164 dial plan, the "+" is a valid character.

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 that you want to find.

To find all manually configured phones, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed per page from the pull-down 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 Add New Manual Phone 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 Export Manual Phones for more information.

Import

To import Manually Configured Phone information to a file, click Import on the Find and List Manually Configured Phones page. See Import Manual Phones for more information.

Add New Manual Phone

To reach the Add New Manual Phone page, choose 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.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Manual Phone page to manually define a phone ERL. You must manually define a phone if any of these conditions apply:

- Emergency Responder cannot automatically track the type of phone, for example, if the phone is analog. See Network Hardware and Software Requirements for information about 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, Emergency Responder cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure that they are correct.

The following table describes the Add New Manual Phone page.

Add New Manual Phone Page

Field

Description

Add New Manual Phone

Line Number

The extension of the phone you want to define.

MAC Address

The MAC address of the phone, if it is an IP phone.

IP Address

The IP address of the phone, if it is an IP phone.

Phone Type

The type of phone, such as analog. This field is for your information only.

Version

The version of the phone software, if any. This field is for your information only.

Location

The location of the phone.

ERL Name

The ERL that you want to assign to the phone. To find and select the ERL, click Search ERL.

Insert button

Click Insert to add the phone to the list of phones.

Note:
The Insert button only appears when you are adding a phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Export Manual Phones

To reach the Export Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Export link. The Export Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Manual Phones page to create a file containing the Emergency Responder manual phone configurations.

If you must 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 Download File for more information.

The following table describes the Export Manual Phones page.

Export Manual Phones Page

Field

Description

Export Manual Phones

Select Export Format

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 that you want to create. Do not include the file extension.

Export button

Click Export to export the file to a file.

Close button

Click Close to close the window.

Download

Select a file to download

Use the pull-down menu to select a file and then click Download to download the file to your local system.

Import Manual Phones

To reach the Import Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 must 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 Upload File for more details.

The following table describes the Import Manual Phones page.

Import Manual Phones Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload

Click Upload to upload a file from a local system. The Upload File page appears. See Upload File for more details.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Displays status messages.

Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you choose ERL Membership > Synthetic Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Synthetic Phones page.

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 pull-down 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 are displayed from the pull-down 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 Add New Synthetic Phone 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, choose 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.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Synthetic Phone page to manually define a synthetic phone ERL. You must configure synthetic phones in the subnet for testing ERL configurations.

For synthetic phones, Emergency Responder cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure that they are correct.

The following table describes the Add New Synthetic Phone page.

Add New Synthetic Phone Page

Field

Description

Notes

MAC Address

The MAC address of the synthetic phone, or a range of MAC addresses.

The synthetic MAC address must be within the 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.

Insert button

Click Insert to add the synthetic phone to the list of phones.

The Insert button only appears when you are adding a phone.

New button

Click New to add another phone.

The New button only appears when you are viewing an existing phone.

Update button

Click Update when viewing an existing phone to save changes you make to the phone.

The Update button only appears when you are viewing an existing phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Find and List Users

The Find and List Users page appears when you choose User Management > User.

Authorization Requirements

You must have system administrator authority to access this page.

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.

The following table describes the Find and List Users page.

Find and List Users Page

Field

Description

User Search Parameters

Find User where User Name

Enter search criteria to select the users that you want to find.

To find all users, click Find without entering any criteria.

To narrow your search:

- Select All to indicate that only users that match the selected criteria be displayed (an AND search).

- Select Any to indicate that users that match any search criteria be selected (an OR search).

- From the pull down menu, select the field that you want to search, select its corresponding relationship and select how many results per page are displayed. The search fields and the corresponding relationships are:

- Authentication Mode—Both, Remote or Local

- User Name— Ends with, Starts with, contains or Exactly.

- Unified CM Cluster—Ends with, Starts with, contains or Exactly.

- 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.

User

Users list

This section of the page displays the search results. If there are no usernames are displayed after completion of the search, then no users have been configured yet.

Username

Displays the users name based on the selection criteria.

Authentication Mode

Displays the authentication mode of the user. The authentication mode can be either Remote or Local.

Unified CM Cluster

This value is displayed only when the user is authenticated remotely, with the Unified CM server.

Edit icon

Click the user name or the Edit icon to display the Modify User page, which allows you to change the user authentication mode, password and Unified CM cluster. The Modify User page also displays which groups and roles have been assigned to the user.

Delete icon

Click the Delete icon to delete the user from the system.

Note:
You cannot delete the Administrator.

Add New User button

Click the Add New User button to open the Add User page. See Table 1 for a description of the Add User page.

Delete Users button

Click the Delete Users button to delete users in bulk. Select multiple users, both remote and local, by checking the check box and then clicking the Delete Users button.

Change to Remote Users button

Click the Change to Remote Users button to change local users to remotely authenticated users in bulk.

Add User

The Add User page appears when you choose 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 Modify User for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add User page to add a new user to the system.

The following table describes the Add User page.

Add User Page

Field

Description

User Name

Enter the username for the new user.

Authentication Mode

Select the authentication mode of the new user. The user can either be a Remote user or a Local user.

Password

Enter the password for the new user.

Confirm Password

Reenter the password for the new user.

Unified CM Cluster

This field is enabled only when the user is a Remote user. Select a Unified CM cluster, from the drop-down list, to authenticate the remote user.

Insert button

Inserts the new user.

Cancel Changes button

Cancels changes made to the Add User page.

Modify User

The Modify User page appears when you choose User Management > User, search for a user, and then click a user name or on the Edit icon associated with the user on the Find and List Users page.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Modify User page to change a current user's password.

The following table describes the Modify User page.

Modify User Page

Field

Description

User Name

Displays the name of the user whose information is being modified.

Note:
You cannot change the username on the Modify User page.

Authentication Mode

Change the authentication mode for a user. You can change a local user to a remote user and a remote user to local user.

Password

Enter the new password for the user.

Confirm Password

Reenter the new password for the user.

Unified CM Cluster

Select a Unified CM cluster. This is required when you change a local user to remote user. You can also change the Unified CM cluster of an existing remote user to another Unified CM Cluster.

Note:
The Unified CM Cluster drop down box are enabled only when the authentication mode is selected as remote.

Update button

Applies changes made from the Modify User page.

Cancel Changes button

Cancels changes made to the Modify User page.

Add new User

Click this button to add a new user. The Add User page appears. See Table 1 for more information.

User Groups for this user

Displays the groups to which the user is assigned.

User Roles for this user

Displays the roles to which the user is assigned.

Change to Remote User

The Change to Remote Users page appears when you choose User Management > User and click Change to Remote Users on the Find and List Users page.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Change to Remote Users page to change the authentication mode of the local user to remote user.

The following table describes the Remote User page.

Change to Remote Users Page

Field

Description

Unified CM Cluster

Select the Unified CM Cluster from the drop-down box to remotely authenticate the selected users.

Selected Users

Displays the local users that change to remote users.

Update button

Applies changes made from the Change to Remote Users page.

Close button

Closes the window.

Find and List Roles

The Find and List Roles page appears when you choose User Management > Role.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List Role page to find, list, modify, and delete current roles, and to add new roles.

The following table describes the Find and List Roles page.

Find and List Roles Page

Field

Description

Role Search Parameters

Find Role where Role Name is

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 pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Roles

Section of the page in which the search results are displayed. These default roles are created during installation:

- Emergency Responder System Admin

- Emergency Responder ERL Admin

- Emergency Responder Network Admin

- Emergency Responder 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:

- Role Name

- Description

- List of resources assigned to that role

Note:
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 are 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 1 for more information about the Modify Role page.

Edit icon

Click the Edit icon to display the Modify Role page. See Table 1 for information about the Modify Role page.

Delete icon

Click the Delete icon to delete the role from the system.

Note:
You cannot delete any of the default roles.

Add New Role button

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 1 for information about the Add Role page.

Add Role

The Add Role page appears when you choose 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 Modify Role for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add Role page to add a new role to the system.

The following table describes the Add Role page.

Add Role Page

Field

Description

Add Role

Role Name

The name of the new role you are adding.

Description

A description of the new role.

Resource Permissions

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.

Select All button

Click Select All to select all the listed resources.

Clear All button

Click Clear All to deselect all currently selected resources.

Insert button

Click Insert to add the new role.

Cancel Changes button

Click Cancel Changes to cancel the Add Role operation.

Modify Role

The Modify Role page appears when you choose 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.

Authorization Requirements

You must have system administrator authority to access this 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.

The following table describes the Modify Role page.

Modify Role Page

Field

Description

Modify Role

Role Name

The name of the new role you are modifying.

Note:
The Role Name cannot be changed.

Description

A description of the role you are modifying. Modify the description by adding new text in the text box.

Resource Permissions

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.

Select All button

Click Select All to select all the listed resources.

Clear All button

Click Clear All to deselect all currently selected resources.

Update button

Click Update to save the changes made to the Modify Role page.

Cancel Changes button

Click Cancel Changes to cancel the changes made to the Modify Role page.

Add new Role button

Allows you to add a new role. See the Add Role for information about adding new roles.

Find and List User Groups

The Find and List User Groups page appears when you choose User Management > User Group.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List User Groups page to find, list, modify, and delete current user groups, and to add new user groups.

The following table describes the Find and List User Groups page.

Find and List User Groups Page

Field

Description

User Group Search Parameters

Find User Group where User Group Name

Enter search criteria to select the user group you want to find.

To find all user groups, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

User Groups

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 Modify User Group for information.

Edit icon

Click the Edit icon to display the Modify User Group page. See Modify User Group for information.

Delete icon

Click the Delete icon to delete the user group from the system.

Note:
You cannot delete default user groups that were created during installation.

Add New User Group button

Click the Add New User Group button to display the Add User Group page. See Table 1 for information about the Add User Group page.

Add User Group

The Add User Group page appears when you choose 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 Modify User Group for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add User Group page to add a new user group to the system.

The following table describes the Add User Group page.

Add User Group Page

Field

Description

Add User Group

User Group Name

The name of the new user group you are adding.

Description

A description of the new user group.

Add Users to the Group

This section of the page has a text box that displays the names of the users you add to the user group.

Add Users button

Allows you to add users to the new group. When you click Add Users, the Add Users page appears. See Add User for more information.

Remove Users button

Allows you to remove users from the group. To do so, highlight the username in the text box and click Remove Users.

Assign Roles to Group

This section of the page has a text box that displays the roles you assign to the new user group.

Add Roles button

Allows you to assign roles to the new group. When you click Add Roles, the Add Roles page appears. See Add Role for more information.

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.

Insert button

Click Insert to add the new role.

Modify User Group

The Modify User Group page appears when you choose User Management > User Group, search for a user group, and then click a user group name, description, or the Edit icon associated with the user group on the Find and List User Groups page.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Modify Role page to modify information for an existing user group.

The following table describes the Modify User Group page.

Modify User Group Page

Field

Description

Modify User Group

User Group Name

The name of the user group you are modifying.

Note:
The User Group Name cannot be changed.

Description

A description of the User Group you are modifying. Modify the description by adding or changing text in the text box.

Add Users to the Group

This section of the page has a text box that displays the names of the users currently in the user group.

Add Users button

Allows you to add more users to the group. When you click Add User, the Add User page appears. See Add User for more information.

Remove Users button

Allows you to remove users from the group. To do so, highlight the username in the text box and click Remove Users.

Assign Roles to Group

This section of the page has a text box that displays the roles currently assigned to the user group.

Add Roles button

Allows you to assign more roles to the group. When you click Add Roles, the Add Role page appears. See Add Role 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 that 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

Click Update to save the changes made to the Modify User Group page.

Add New User Group button

Allows you to add a new user group. See Add User Group for information.

Call History

The Call History page appears when you choose Reports > Call History.

Authorization Requirements

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. Emergency Responder maintains the most recent 10,000 call history records. There is no restriction on when these calls were placed.

The following table describes the Call History page.

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 pull down menu, select the field that you want to search on (ERL Name, Caller 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.

Call History Matching Records

A list of emergency calls that match your search criteria is displayed with the following information:

- ERL Name—Click the name to view details about the ERL and its ALI information. See Conventional ERL for descriptions of the configuration fields.

- Caller Extension—The extension used to place the emergency call.

- Time—The time the call was made.

- Date—The date the call was made.

- Route Pattern-ELIN No.—The route pattern and ELIN combination used for the call. See Conventional ERL for more detailed information about these fields.

- Location—The location of the phone based on whether the phone was configured manually, or whether it was configured based on the switch port or IP subnet.

- Call Acknowledged—The acknowledged status of a call on the Web Alert page.

- Acknowledged By—The ID of the user who acknowledged the call.

- Time Acknowledged—The time that the call was acknowledged.

- Date Acknowledged—The date that the call was acknowledged.

- Comments—Any 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

Click Download to save the call history data to a spreadsheet that you can view or download to your local system.

Update

Click Update to include your comments in the call history for the call.

Note:
Only viewable from the Call Details page.

Cancel Changes

Click Cancel Changes to remove unsaved comments. You can then reenter comments.

Note:
Only viewable from the Call Details page.

Close

Click Close to close the Call Details page.

Note:
Only viewable from the Call Details page.

ERL Audit Trail

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

- Choose Reports > ERL Audit Trail.

- Click view in the Audit Trail column for an ERL displayed on the ERL Configuration page (opened by choosing ERL > Conventional ERL.)

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the ERL Audit Trail page to view the change history for ERLs.

The following table describes the ERL Audit Trail page.

ERL Audit Trail Page

Field

Description

ERL Audit Trail

Search criteria

Enter search criteria to select the audit details that 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 pull-down menu, select the field that 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 pull-down 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:

- ERL Name—The name of the ERL that was changed.

- Modified By—The login ID of the user who changed the ERL.

- Modified Time—The date and time the ERL was changed.

- Modification Details—A 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.

Note:
If there are a large number of records match your search, Emergency Responder 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.

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

PS-ALI Converter

The PS-ALI Converter page appears when you choose Tools > PS-ALI Converter.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the PS-ALI Converter tool to generate an ERL file that can be accepted by the Emergency Responder 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 Emergency Responder.

Note

If you change the customer code in your ALI record, Emergency Responder 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 and 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.

PS-ALI Converter Page

Field

Description

Export PS-ALI Records

Select PS-ALI file (NENA 2.0 format)

The name of the PS-ALI file to be converted. The file must be in the default format, NENA format 2.0.

Output File (in csv format) Name

The name of the csv file that you want to create.

Convert button

Click Convert to create the csv file.

Cancel button

Click Cancel to stop the converting process. and close the window.

PS-ALI Records Download

Download File appears when you choose Export PS-ALI records->Download

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

The Exported PS-ALI Records can be downloaded from here using the download button.

Download PS-ALI Records

Field

Description

Select a file to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Close button

Click Close to close the window.

ERL Debug Tool

The ERL Debug Tool page appears when you choose Tools > ERL Debug Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

The ERL Debug Tool takes the phone extension as input and displays the ERLs currently being used for routing emergency calls for the phones.

Use this diagnostic tool to verify the Emergency Responder configuration during the ERL creation and the ERL assignment phase and to troubleshoot calls directed to incorrect ERLs.

The following table describes the ERL Debug Tool page.

ERL Debug Tool Page

Field

Description

ERL Debug Tool

Find Phones where extension

Enter search criteria to select the extensions that you want to find.

To find all extensions, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Matching records

Section of the page that displays the ERLs currently being used for routing emergency calls for the phones. 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.

Export button

Click Export to create the export file.

ERL Debug Tool Export

The Export ERL Debug Tool page appears when you click Export in the ERL Debug Tool page.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export ERL Debug Tool page to create a file which shows phone extension with ERLs currently being used for routing emergency calls for the phones.

Export ERL Debug Tool

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma-separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

ALI Formatting Tool

The ALI Formatting Tool page appears when you choose Tools > ALI Formatting Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder 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

The following table describes the ALI Formatting Tool page.

ALI Formatting Tool Page

Field

Description

Select a Service Provider

Use the pull-down menu to select a service provider

Select an Input File for the ALI Formatting Tool from the List Below

Use the pull-down menu to select an input file

Submit button

Click the Submit button to display the Search for ELINs page, which is described in Table 2.

The following table describes the Search for ELINs page.

Search for ELINs Page

Field

Description

Use Search to Filter-out ELINs on Area, City and Local Code(last 4-digits).

Allows you to search ELINs by Local Code, Area Code, or City Code.

Add (+) button

Adds more search parameters

Remove (-) button

Removes search parameters

The following table describes the Bulk Update page.

Bulk Update Page

Field

Description

Remove Changes/Generate File button

Shows all the ELINs that have been changed.

Search for ELIN

Displays the ELIN search page.

The following table describes the Review Changes/Generate File page.

Review Changes/Generate File Page

Field

Description

Add More ELIN

Displays the remaining ELINs that have not been changed.

Remove ELIN

Removes the selected ELINs from the list

Search for ELIN

Displays the ELIN search screen

Generate File button

Generates the formatted file.

The following table describes the Download Formatted File page.

Download Formatted File Page

Field

Description

Download Formatted File button

Displays a Download File dialog box so that the formatted file can be downloaded to the local system.

File Management Utility

The File Management Utility page appears when you choose Tools > File Management Utility.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the File Management Utility page to search for, download, or delete exported files.

The following table describes the File Management Utility page.

File Management Utility Page

Field

Description

Search Parameters

Please Select:

From the pull-down menu, select the type of file that you want to search for.

Search button

Click Search to perform the search.

Exported Files

Area of the page that displays the search results. Displays the File Name, Last Modified data, and File Size for each file found.

Download button

Downloads the selected file.

Note:
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.

Delete button

Deletes the selected file.

Note:
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.

Purge Call History

The Purge Utility for Call History page appears when you choose Tools > Purge Utility.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Purge Call History Utility to delete call history records that are older than an age that you specify. You can use this utility to purge records immediately or schedule daily purging of call history records. Emergency Responder logs the results of the purge in the Emergency Responder Administration logs.

The following table describes the purge utility page.

Purge Utility for Call History

Field

Description

Status

Displays status messages

Purge Now

Purge Data older than

Specify the age of record that you want to delete.

Schedule Purge

Daily Purge at

Specify a time (GMT) during the day at which old records are deleted.

Purge Data older than

Specify the age of record that you want to delete.

Update

Click Update to save and activate your changes.

Cancel

Click Cancel Changes to change the fields on this page back to the last saved settings.

Appendix B. Change IP Address and Hostname

IP Address and Hostname Overview

You can change the network-level IP address and hostname name of nodes in your deployment for a variety of reasons, including moving the node from one network domain to another or resolving a duplicate IP address problem. The IP address is the network-level Internet Protocol (IP) associated with the node, and the Hostname is the network-level hostname of the node.

This document provides detailed procedures for the following tasks for Cisco Emergency Responder nodes:

- Change the IP address of a node

- Change the hostname of a node

Task lists are provided for each of these procedures that summarize the steps to perform.

Use the Cisco Emergency Responder 10.5(1) Command Line Interface Guide to assist you when changing an IP Address or Hostname. This guide replaces the chapter previously found in the Cisco Emergency Responder Administration Guide.

The Emergency Responder Command Line Interface Guide can be found on the Cisco Emergency Responder Command Reference page.

Note

You must complete all pre-change tasks and system health checks before you make these changes, and you must complete the post-change tasks after you make any of these changes.

Pre-Change Tasks and System Health Checks

The following sections discuss pre-change tasks and system health checks. You must perform these tasks before you change a Hostname or IP address.

Pre-Change Task List for Cisco Emergency Responder Nodes

The following table lists the tasks to perform before you proceed to change the IP address and hostname for Cisco Unified Communications Manager nodes. You must perform these procedures during a scheduled maintenance window. Perform all system health checks before you perform the pre-change setup tasks.

For details about any of the tasks that are listed, see topics related to performing system health checks on nodes and pre-change setup.

Caution

If you do not receive the results that you expect when you perform these tasks, do not continue until you have resolved the issue.

Item

Task

System health checks

1.

If you have DNS configured anywhere on the Cisco Emergency Responder servers, ensure that forward and reverse records (for example, a record and PTR record) are configured and that the DNS is reachable and working.

2.

Ensure that all servers in the cluster are up and available, and check for any active ServerDown alerts.

3.

Check the database replication status of all Cisco Emergency Responder nodes in the cluster to ensure that all servers are replicating database changes successfully.

4.

Check network connectivity and DNS server configuration.

Pre-change setup tasks

5.

Use Cisco Emergency Responder Administration to compile a list of all nodes in the cluster. Retain this information for use later.

6.

Run a manual Disaster Recovery System backup and ensure that all nodes and active services are backed up successfully. For more information, see the Disaster Recovery System Administration Guide for your release.

Check System Health

Perform the applicable system health checks on the nodes in your deployment as part of the pre-change setup and as part of the post-change tasks that you must perform after you have changed any network identifiers.

Caution

If you do not receive the results that you expect when you perform these tasks, do not continue until you have resolved the issue.

Some of the checks in this procedure are required only for post-change verification. See the post-change task list for a complete list of the system health checks to perform.

Note

If you are performing system health checks as part of the pre-change setup, you can skip the following steps which are only required when you are performing the post-change tasks:

- Verification that the new hostname or IP address appears on the Cisco Emergency Responder server list.

- Verification that changes to the IP address, hostname, or both are fully implemented in the network.

- Verification that changes to the hostname is fully implemented in the network.

Procedure

Step 1

If you have DNS configured anywhere on the Cisco Emergency Responder servers, ensure that a forward and reverse lookup zone has been configured and that the DNS is reachable and working.

Step 2

Check for any active ServerDown alerts to ensure that all servers in the cluster are up and available. Use either the Cisco Unified Real-Time Monitoring Tool (RTMT) or the command line interface (CLI) on the first node.

1. To check using Unified RTMT, access Alert Central and check for ServerDown alerts.

2. To check using the CLI on the first node, enter the following CLI command and inspect the application event log: file search activelog syslog/CiscoSyslog ServerDown

Step 3

Check the database replication status on all nodes in the cluster to ensure that all servers are replicating database changes successfully.
Use CLI to get status of DB replication.

To check using the CLI, enter utils dbreplication status

For example output, see topics related to example database replication output. For detailed procedures and troubleshooting, see topics related to verifying database replication and troubleshooting database replication.

Step 4

Enter the CLI command utils diagnose as shown in the following example to check network connectivity and DNS server configuration.

admin:utils diagnose module validate_network

Log file: platform/log/diag1.log

Starting diagnostic test(s)
===========================
test - validate_network    : Passed

Diagnostics Completed

The final output will be in Log file: platform/log/diag1.log

Please use file view activelog platform/log/diag1.log command to see the output

Step 5

If you are performing the pre-change system health checks, you are done; otherwise, continue to perform the post-change verification steps.

Step 6

Verify that the new hostname or IP address appears on the Cisco Unified Communications Manager server list. In Cisco Unified Communications Manager Administration, select System > Server Settings.
Note:   Perform this step only as part of the post-change tasks.

Step 7

Verify that changes to the IP address, hostname, or both are fully implemented in the network. Enter the CLI command show network cluster on each node in the cluster. Perform this step only as part of the post-change tasks.
Note:   The output should contain the new IP address or hostname of the node.

Example

admin:show network cluster
10.77.29.191 cer-191-p123.cisco.com cer-191-p123 Publisher callmanager DBPub authenticated
10.77.29.192 cer186-sub.cisco.com cer186-sub Subscriber ciscoer DBSub authenticated using TCP since Fri Oct 10 18:42:40 2014

Successful

Step 8

Verify that changes to the hostname are fully implemented in the network. Enter the CLI command utils network host <new_hostname> on each node in the cluster.
Perform this step only as part of the post-change tasks.

Note:   The output should confirm that the new hostname resolves locally and externally to the IP address.

Example

admin:utils network host cer-191-p123
Local Resolution:
cer-191-p123.cisco.com resolves locally to 10.77.29.191 (CER-191-P123.cisco.com)

External Resolution:
cer-191-p123.cisco.com has address 10.77.29.191

Pre-Change Setup

Perform all pre-change setup tasks to ensure that your system is prepared for a successful IP address, hostname, domain, or node name change. You must perform these tasks during a scheduled maintenance window.

You should perform the system health checks on your deployment before performing the pre-change setup.

Perform Pre-Change Setup Tasks for Cisco Emergency Responder Nodes

Perform the following pre-change setup tasks before you change the IP address or hostname. You must perform these tasks during a scheduled maintenance window. See the pre-change task list for more information.

Caution

If you do not receive the results that you expect when you perform these tasks, do not continue until you have resolved the issue.

Before You Begin
Perform the system health checks on your deployment.

Procedure

Step 1

From Cisco Unified Communications Manager Administration on the first node, select System > Server and click Find. A list of all servers in the cluster displays. Retain this list of servers for future reference.
Ensure that you save an inventory of both the hostname and IP address of each node in your cluster.

Step 2

Run a manual Disaster Recovery System backup and ensure that all nodes and active services are backed up successfully. For more information, see the Disaster Recovery System Administration Guide for your release.

IP Address and Hostname Changes

The following sections provide important information on IP Address and Hostname Changes. You must read these sections before you change an IP address or Hostname.

Change IP Address and Hostname Task List

The following table lists the tasks to perform to change the IP address and hostname for Cisco Emergency Responder nodes.

Change IP Address and Hostname Task List

Item

Task

1.

Perform the pre-change tasks and system health checks.

2.

Change the IP address or hostname for the node using either the Command Line Interface (CLI) or the Unified Operating System GUI.

3.

Perform the post-change tasks.

Change IP Address or Hostname Using Unified Operating System GUI

You can use Cisco Unified Operating System Administration to change the IP address or hostname for publisher and subscriber nodes that are defined by a hostname in your deployment. Unless otherwise stated, each step in this procedure applies to both publisher and subscriber nodes on Cisco Emergency Responder Server Group.

Changing the hostname triggers automatic self-signed certificate regeneration. This causes all devices in the cluster to reset so that they can download an updated ITL file. If your cluster is using CA-signed certificates, you will need to have them re-signed.

Before You Begin
Perform the pre-change tasks and system health checks on your deployment.

Procedure

Step 1

From Cisco Unified Operating System Administration, select Settings > IP > Ethernet.

Step 2

Change the hostname, IP address, and if necessary, the default gateway.

Step 3

Click Save.

What to Do Next

Perform all applicable post-change tasks to ensure that your changes are properly implemented in your deployment.

Note

Do not proceed if the new hostname does not resolve to the correct IP address. If your cluster is using CA-signed certificates, you will need to have them re-signed. Run the CTL client and update the CTL file if the Cisco Unified Communications Manager cluster security is operating in mixed mode.

Change IP Address or Hostname Using CLI

You can use the Command Line Interface (CLI) to change the IP address or hostname for publisher and subscriber nodes that are defined by a hostname in your deployment. Unless otherwise stated, each step in this procedure applies to both publisher and subscriber nodes on Cisco Emergency Responder Server Group.

Changing the hostname triggers automatic self-signed certificate regeneration. This causes all devices in the cluster to reset so that they can download an updated ITL file. If your cluster is using CA-signed certificates, you will need to have them re-signed.

Before You Begin
Perform the pre-change tasks and system health checks on your deployment.

Procedure

Step 1

Log into the CLI of the node that you want to change.

Step 2

Enter set network hostname.

Step 3

Follow the prompts to change the hostname, IP address, or default gateway.

1. Enter the new hostname and press Enter.

2. Enter Yes if you also want to change the IP address; otherwise, go to Step 4.

3. Enter the new IP address.

4. Enter the subnet mask.

5. Enter the address of the gateway.

Step 4

Verify that all your input is correct and enter yes to start the process.

Step 5

Wait for all services to come up on the node where the change is applied.

Step 6

If the change is applied on Publisher and only Hostname is changed, restart Cisco Emergency Responder service on Publisher.

Step 7

If the change is applied on Publisher and IP address is also changed along with the Hostname; restart Cisco Emergency Responder service on both Publisher and Subscriber node.

Step 8

If the node that you have changed is a subscriber node, reboot the node.

What to Do Next

Perform all applicable post-change tasks to ensure that your changes are properly implemented in your deployment.

Note

Do not proceed if the new hostname does not resolve to the correct IP address.

If your cluster is using CA-signed certificates, you will need to have them re-signed. Run the CTL client and update the CTL file if the Cisco Emergency Responder cluster security is operating in mixed mode.

Example CLI Output for Set Network Hostname: Changing Hostname Only of Publisher

The following code shows an example of the CLI Output for Set Network Hostname.

admin:set network hostname

WARNING: Changing this setting will invalidate software license
on this server. The license will have to be re-hosted.
Continue(y/n):
Continue (y/n)?y

ctrl-c: To quit the input.

***   W A R N I N G   ***
Do not close this window without first canceling the command.

This command will automatically restart system services.
The command should not be issued during normal operating
hours.

=======================================================
Note: Please verify that the new hostname is a unique
name across the cluster and, if DNS services are
utilized, any DNS configuration is completed
before proceeding.
=======================================================

Security Warning : This operation will regenerate
all CUCM Certificates including any third party
signed Certificates that have been uploaded.

Enter the hostname:: newHostName
Would you like to change the network ip address at this time [yes]:: no

Warning: Do not close this window until command finishes.

Hostname: newHostName

Do you want to continue [yes/no]? yes

calling 1 of 10 component notification script: acluster_healthcheck.sh
calling 2 of 10 component notification script: adns_verify.sh
No Primary DNS server defined
No Secondary DNS server defined
calling 3 of 10 component notification script: aetc_hosts_verify.sh
calling 4 of 10 component notification script: ahostname_callback.sh
Info(0): Processnode query returned using cer195pub123:
hostaddress
============
cer195pub123
updating cerserver table from:'cer195pub123', to: 'newHostName'
Rows: 1
updating cersystemparameters table from:'cer195pub123', to: 'newHostName'
Rows: 3
updating database, please wait 90 seconds
updating database, please wait 60 seconds
updating database, please wait 30 seconds
calling 5 of 10 component notification script: clm_notify_hostname.sh
Verifying update across cluster nodes...
Updating platformConfig.xml: cer195pub123 to newHostName
Updating platformConfig.xml: cer195pub123 to newHostName
Updating platformConfig.xml: cer195pub123 to newHostName
Updating processnode.xml: cer195pub123 to newHostName
\  Restarting Cluster Manager service... Please Wait

cluster update successfull
calling 6 of 10 component notification script: drf_notify_hostname_change.py
calling 7 of 10 component notification script: elm_client_reset_registration
calling 8 of 10 component notification script: idsLocalPrefsUpdateFile.sh
Going to trigger /usr/bin/python /usr/local/er/lib/dblupdatefiles-plugin.py -f=newHostName,cer195pub123
calling 9 of 10 component notification script: regenerate_all_certs.sh
calling 10 of 10 component notification script: update_idsenv.sh

System services will restart in 1 minute
admin:

Example CLI Output for Set Network Hostname: Changing IP Address and Publisher Hostname

The following code shows an example of the CLI Output for Set Network Hostname.

admin:set network hostname

WARNING: Changing this setting will invalidate software license
on this server. The license will have to be re-hosted.
Continue(y/n):
Continue (y/n)?y

ctrl-c: To quit the input.

***   W A R N I N G   ***
Do not close this window without first canceling the command.

This command will automatically restart system services.
The command should not be issued during normal operating
hours.

=======================================================
Note: Please verify that the new hostname is a unique
name across the cluster and, if DNS services are
utilized, any DNS configuration is completed
before proceeding.
=======================================================

Security Warning : This operation will regenerate
all CUCM Certificates including any third party
signed Certificates that have been uploaded.

Enter the hostname:: newHostNameAndnewIPAddress
Would you like to change the network ip address at this time [yes]::

Warning: Do not close this window until command finishes.

ctrl-c: To quit the input.

***   W A R N I N G   ***
=======================================================
Note: Please verify that the new ip address is unique
across the cluster.
=======================================================

Enter the ip address:: 10.77.29.186
Enter the ip subnet mask:: 255.255.255.0
Enter the ip address of the gateway:: 10.77.29.1
Hostname:       newHostNameAndnewIPAddress
IP Address:     10.77.29.186
IP Subnet Mask: 255.255.255.0
Gateway:        10.77.29.1

Do you want to continue [yes/no]? yes

calling 1 of 6 component notification script: ahostname_callback.sh
Info(0): Processnode query returned using newHostName:
hostaddress
===========
newHostName
updating cerserver table from:'newHostName', to: 'newHostNameAndnewIPAddress'
Rows: 1
updating cersystemparameters table from:'newHostName', to: 'newHostNameAndnewIPAddress'
Rows: 3
updating database, please wait 90 seconds
updating database, please wait 60 seconds
updating database, please wait 30 seconds
calling 2 of 6 component notification script: clm_notify_hostname.sh
Verifying update across cluster nodes...
Updating platformConfig.xml: newHostName to newHostNameAndnewIPAddress
Updating platformConfig.xml: newHostName to newHostNameAndnewIPAddress
Updating platformConfig.xml: newHostName to newHostNameAndnewIPAddress
Updating processnode.xml: newHostName to newHostNameAndnewIPAddress
\  Restarting Cluster Manager service... Please Wait

cluster update successfull
calling 3 of 6 component notification script: drf_notify_hostname_change.py
calling 4 of 6 component notification script: idsLocalPrefsUpdateFile.sh
Going to trigger /usr/bin/python /usr/local/er/lib/dblupdatefiles-plugin.py -f=newHostNameAndnewIPAddress,newHostName
calling 5 of 6 component notification script: regenerate_all_certs.sh
calling 6 of 6 component notification script: update_idsenv.sh
calling 1 of 3 component notification script: aaupdateip.sh
calling 2 of 3 component notification script: ahostname_callback.sh
Info(0): Processnode query returned =
name
==================================================
10.77.29.195-AdminUpdateManager
10.77.29.195-SystemUpdateManager
updating server table from:'10.77.29.195', to: '10.77.29.186'
Rows: 1
Rows: 1
updating database, please wait 90 seconds
updating database, please wait 60 seconds
updating database, please wait 30 seconds
calling 3 of 3 component notification script: clm_notify_hostname.sh
Verifying update across cluster nodes...
Shutting down interface eth0:

Change IP Address Only

Do not use set network hostname CLI command to change IP Address only.

Command Syntax

set network ip eth0 ip-address ip-mask gate-way

Syntax Description

Parameters

Description

eth0

Specifies Ethernet interface 0.

ip-address

The IP address that you want assign.

ip-mask

The IP mask that you want to assign.

gate-way

The IP of default gate way to be assigned.

Example

Note

For further information please refer the admin guide IP address change section.

admin:set network ip eth0 10.77.34.243 255.255.255.0 10.77.34.1

WARNING: Changing this setting will invalidate software license
on this server. The license will have to be re-hosted.
Continue(y/n):
Continue (y/n)?y
***   W A R N I N G   ***
This command will restart system services
=======================================================
Note: Please verify that the new ip address is unique
across the cluster and, if DNS services are
utilized, any DNS configuration is completed
before proceeding.
=======================================================

Continue (y/n)?y
calling 1 of 7 component notification script: aaupdateip.sh
calling 2 of 7 component notification script: acluster_healthcheck.sh
calling 3 of 7 component notification script: adns_verify.sh
Verifying 10.77.34.243 against primary DNS server 10.77.34.227 ...
Successfully verified against primary DNS server 10.77.34.227
IPADDR_RETURNED matches 10.77.34.243
calling 4 of 7 component notification script: aetc_hosts_verify.sh
calling 5 of 7 component notification script: ahostname_callback.sh
Info(0): Processnode query returned =
name
==================================================
10.77.34.207-AdminUpdateManager
10.77.34.207-SystemUpdateManager
updating server table from:'10.77.34.207', to: '10.77.34.243'
Rows: 1
Rows: 1
updating database, please wait 90 seconds
updating database, please wait 60 seconds
updating database, please wait 30 seconds
calling 6 of 7 component notification script: clm_notify_hostname.sh
Verifying update across cluster nodes...
Shutting down interface eth0:

Post-Change Tasks and Verification

The following sections provide information on post-change tasks and verification. You must read these sections and perform these tasks to complete the IP Address and Hostname changes.

Post-Change Task List for Cisco Emergency Responder Nodes

The following table lists the tasks to perform after you have changed the IP address or hostname of the Cisco Emergency Responder nodes in your cluster.

Perform the tasks that apply to your deployment in the order in which they are presented in the task list. For details about system health checks or generating ITL certificates, see the related topics.

Post-Change Task List for Cisco Emergency Responder Nodes

Item

Task

System health checks

1.

Ensure that all servers in the cluster are up and available, and check for any active ServerDown alerts.

Note:
ServerDown alerts in the Syslog are normal during the change process, but should not appear in the log after the change is done.

2.

Check the database replication status of all Cisco Emergency Responder nodes in the cluster to ensure that all servers are replicating database changes successfully.

3.

Check network connectivity and DNS server configuration on the node that was changed using the CLI command utils diagnose module validate_network.

Security enabled cluster tasks

4.

For security-enabled clusters (Cluster Security Mode 1 - Mixed), update the CTL file and then restart all nodes in the cluster before you perform the system health checks and other post-change tasks.

For detailed instructions on updating and managing the CTL file, including adding a new TFTP server to an existing CTL file, see the Cisco Unified Communications Manager Security Guide .

5.

If you enabled cluster security using Certificate Trust List (CTL) files and USB eTokens, you must regenerate the Initial Trust List (ITL) file and the certificates in the ITL.

Skip this step if you have not enabled cluster security using Certificate Trust List (CTL) files and USB eTokens.

Post-change tasks

6.

Run a manual DRS backup and ensure that all nodes and active services back up successfully. For more information, see the Disaster Recovery System Administration Guide for your release.

Note:
You must run a manual DRS backup after you change the IP address of a node, because you cannot restore a node with a DRS file that contains a different IP address or hostname.

The post-change DRS file will include the new IP address or hostname.

7.

If you are using the integrated DHCP server that runs on Cisco Unified Communications Manager, update the DHCP server.

Perform Post-Change Tasks for Cisco Emergency Responder Nodes

Perform all post-change tasks to ensure that your changes are properly implemented in your deployment. Perform the tasks in the order in which they are presented in the task list.

Before You Begin
Before you perform your post-changes tasks, you must:

- Perform all applicable system health checks to verify the changes that were made to your deployment.

- Perform the security enabled cluster tasks if cluster security is enabled for your deployment.

Procedure

Step 1

Run a manual DRS backup and ensure that all nodes and active services back up successfully. For more information, see the Disaster Recovery System Administration Guide for your release.
Note:
You must run a manual DRS backup after you change the IP address of a node, because you cannot restore a node with a DRS file that contains a different IP address or hostname. The post-change DRS file will include the new IP address or hostname.

Step 2

If you are using the integrated DHCP server that runs on Cisco Unified Communications Manager, update the DHCP server.

Troubleshooting

The following sections provide information on troubleshooting an IP Address and Hostname change. Use this information to diagnose and resolve any issues.

Troubleshoot Cluster Authentication

You can troubleshoot cluster authentication issues on subscriber nodes using the Command Line Interface (CLI).

Procedure

Step 1

Enter show network eth0 [detail] to verify network configuration.

Step 2

Enter show network cluster to verify the network cluster information.

- If the output displays incorrect publisher information, enter the set network cluster publisher [hostname/IP address] CLI command on the subscriber node to correct the information.

- If you are on a publisher node, and the show network cluster CLI command displays incorrect subscriber information, login to Cisco Emergency Responder Administration and choose System > Server Settings to check the output.

- If you are on a subscriber node and the show network cluster output displays incorrect publisher information, use the set network cluster publisher [hostname | IP_address] CLI command to change the publisher hostname or IP address.

Troubleshoot Database Replication

You can use the Command Line Interface (CLI) to troubleshoot database replication on the nodes in your cluster.

- Verify that database replication is in a correct state in the cluster.

- Repair and reestablish database replication for the nodes.

- Reset database replication.

For more information about these commands or using the CLI, see the Command Line Interface Guide for Cisco Emergency Responder Administration Guide.

Verify Database Replication

Use the Command Line Interface (CLI) to check the database replication status for all nodes in the cluster. Verify that the Replication STATE is shown as "Active" for both publisher and subscriber replication server. Anything other than "Active" state (for example, "Dropped", "Connecting") means that there is a problem with database replication and that you need to reset replication for the node. See topics related to database replication examples for example output.

Procedure

Enter utils dbreplication status on the publisher and subscriber to check database replication on both the nodes in a Server Group.
Note:
If replication is not set up for the nodes in your cluster, you can reset database replication for the nodes using the CLI. For more information, see topics related to resetting database replication using the CLI

Example:

On Publisher

admin:utils dbreplication status

-------------------- utils dbreplication status --------------------
Output is in file /var/log/active/er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_24_02.out

Please use "file view activelog er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_24_02.out " command to see the output
admin:file view activelog er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_24_02.out

Mon Oct 13 18:24:02 2014 main()  DEBUG:  -->
Mon Oct 13 18:24:02 2014 main()  DEBUG:  Replication cluster summary:
SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_2_cer10_5_0_98000_9000    2 Active   Local           0
g_3_cer10_5_0_98000_9000    3 Active   Connected       0 Oct 13 17:31:15
Mon Oct 13 18:24:03 2014 main()  DEBUG:  <--

end of the file reached
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 7 of 7) :
admin:
On Subscriber:

admin:utils dbreplication status

-------------------- utils dbreplication status --------------------
Output is in file /var/log/active/er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_33_14.out

Please use "file view activelog er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_33_14.out " command to see the output
admin:file view activelog er/trace/dbl/sdi/ReplicationStatus.2014_10_13_18_33_14.out

Mon Oct 13 18:33:14 2014 main()  DEBUG:  -->
Mon Oct 13 18:33:14 2014 main()  DEBUG:  Replication cluster summary:
SERVER                 ID STATE    STATUS     QUEUE  CONNECTION CHANGED
-----------------------------------------------------------------------
g_2_cer10_5_0_98000_9000    2 Active   Connected       0 Oct 13 17:31:15
g_3_cer10_5_0_98000_9000    3 Active   Local           0
Mon Oct 13 18:33:15 2014 main()  DEBUG:  <--

end of the file reached
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 7 of 7) :
admin:

Repair Database Replication

Use the Command Line Interface (CLI) to repair database replication.

Procedure

Step 1

Enter utils dbreplication repair all on the Publisher to attempt to repair database replication.
Depending on the size of the database, it may take several minutes to repair database replication. Proceed to the next step to monitor the progress of database replication repair.

Example:

admin:utils dbreplication repair all
-------------------- utils dbreplication repair --------------------
Logs for the repair of ~informix/.rhosts file is present in er/logs/repair-rhosts-1818.log file
/usr/local/er/db/informix/bin/cdr list server >> /var/log/active/er/trace/dbl/sdi/ReplicationRepair.2014_10_13_18_38_07.out 2>&1
Output is in file er/trace/dbl/sdi/ReplicationRepair.2014_10_13_18_38_07.out

Please use "file view activelog er/trace/dbl/sdi/ReplicationRepair.2014_10_13_18_38_07.out " command to see the output
admin:

Step 2

View the ReplicationRepair file as mentioned in step 1 to check whether all tables are scanned and replicated properly. Any error will be reflected in this file.
If errors or mismatches are found, there may be a transient mismatch between nodes. Run the procedure to repair database replication again.

Note:
If, after several attempts to repair replication, mismatches or errors are being reported, try resetting the replication to resolve this issue.

Reset Database Replication

Reset database replication if replication is not set up for the nodes in your cluster. You can reset database replication using the command line interface (CLI).

Procedure

Step 1

Reset replication on nodes in your cluster. Do the following:

1. Enter utils db replication reset all on Publisher node in a CER Server Group.

2. Before you run this CLI command on the Publisher node, first run the command utils dbreplication stop on subscriber node, and then on the publisher node.

Step 2

After the command is executed successfully on Publisher node, restart subscriber node.

Troubleshoot Network

You can troubleshoot network issues on nodes using the Command Line Interface (CLI).

Procedure

Step 1

Enter show network eth0 [detail] to verify network configuration.

Step 2

If any of the fields are missing, then reset the network interface.

1. Enter set network status eth0 down.

2. Enter set network status eth0 up.

Step 3

Verify the IP address, mask, and gateway. Ensure that these values are unique across the network.

Troubleshoot Network Time Protocol

The following sections discuss troubleshooting NTP issues on the Publisher and Subscriber nodes. Use this information to resolve any potential issues.

Troubleshoot NTP on Subscriber Nodes

You can troubleshoot Network Time Protocol (NTP) issues on subscriber nodes using the Command Line Interface (CLI).

Procedure

Step 1

Enter show network eth0 [detail] to verify network configuration.

Step 2

Enter utils ntp status to verify NTP status.

Step 3

Enter utils ntp restart to Restart NTP.

Step 4

Enter show network cluster to verify the network cluster.
If the output displays incorrect publisher information, use the set network cluster publisher [hostname/IP_address] CLI command to reset the publisher.

Troubleshoot NTP on Publisher Nodes

You can troubleshoot Network Time Protocol (NTP) issues on publisher nodes using the Command Line Interface (CLI).

Procedure

Step 1

Enter show network eth0 [detail] to verify network configuration.

Step 2

Enter utils ntp status to verify NTP status.

Step 3

Enter utils ntp restart to Restart NTP.

Step 4

Enter utils ntp server list to verify NTP servers.
To add or delete an NTP server, use the utils ntp server [add/delete] CLI command.

Appendix C. Cisco Emergency Responder Serviceability Web Interface

Control Center

The Control Center page appears when you choose Tools > Control Center.

Authorization Requirements

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.

The following table describes the Control Center page.

Control Center Page

Field

Description

Start button

Starts the selected services.

Stop button

Stops the selected services.

Restart button

Restarts the selected services.

Refresh button

Refreshes the list of currently running services on the selected server.

Service Name

Names of the currently running services on the selected server. To select a service, click the radio button next to the service name.

Status

Current status of the selected service.

Event Viewer

The Event Viewer page appears when you choose Tools > Event Viewer.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Event Viewer page to view Emergency Responder events for the previous six months.

The following table describes the Event Viewer page.

Event Viewer Page

Field

Description

Type pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down 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 pull-down menu to the right of the Type pull-down menu.

Module pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down menu to the right changes to display the available Type or Module options.

Allows you to select the Emergency Responder module for which you want to view events. When you select Module from the pull-down 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

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.

Type column

Displays the type of event. The Type column displays one of the following:

- INFO

- WARN

- ERROR

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.

Module column

Displays the Emergency Responder 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.

SNMP Community String Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP Community String Configuration page to view, add, update, and delete community strings. Community strings control access to the Emergency Responder by clients using SNMP V1 and V2c.

The following table describes the SNMP Community String Configuration page.

SNMP Community String Configuration Page

Field

Description

Community String Name column

Lists all community strings defined for the selected server. Click 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 this button, Emergency Responder opens a second SNMP Community String Configuration page.

Note:
Clicking the Add New button brings up the same screen displayed when you click the Add New icon.

Delete Selected button or icon

Deletes the selected community strings. To delete a community string, you must first select it from the list of community strings. Click the box to the left of the community string name to select it. To delete all community strings from the selected server, click 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 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.

The following table describes the second SNMP Community String Configuration page.

SNMP Community String Configuration Page—2

Field

Description

Community String Name

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.

Host IP Address Information

Accept SNMP Packets from any host

Click this radio button to allow any host to access the Emergency Responder using SNMP.

Accept SNMP Packets only from these hosts

Click this radio button to specify which hosts can access the Emergency Responder 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.

Access Privileges pulldown menu

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:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert 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.

Clear button or icon

Clears the community string information displayed on the current page.

SNMP User Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the SNMP User Configuration page.

SNMP User Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to view, add, update, or delete users. After you select a server, Emergency Responder displays the currently configured information in the following format:

- User Name

- Authentication Required

- Authentication Protocol

- Privacy Required

- Privacy Protocol

- Access Privileges

Click user name to display the Add and Update SNMP User Configuration page, from which you can update the information for that user.

Add New User button or icon

Add a new user for the selected server. When you click this icon, Emergency Responder opens the 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 the box to the left of the User Name column heading.

Use the second SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the Add/Update SNMP User Configuration page.

SNMP User Configuration Page—2

Field

Description

User Name field

Enter the name of the new SNMP V3 user.

Note:
If you reached this page by clicking an existing user name on the SNMP User Configuration page, the fields on this page display the currently configured information.

Authentication Information

Use this section to configure the following information:

- If authentication is required for this user, check the check box that is 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 the radio button for either MD5 or SHA.

Privacy Information

Use this section to configure the following information:

- If privacy is required for this user, check the check box that is labelled 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 labelled DES.

Host IP Addresses Information

Use the radio buttons in this section of the page to do the following:

- Specify which hosts can access the Emergency Responder using SNMP. You can insert IP addresses for new hosts that you want to have SNMP access to the Emergency Responder, or you can remove IP addresses of hosts that you no longer want to have SNMP access to Emergency Responder.

- Allow any host to access Emergency Responder using SNMP.

Access Privileges pulldown menu

When adding a new user, this pull-down menu allows you to specify the access privilege for the new user. When updating a user's information, this field displays the current access privilege level. The available access privilege levels are as follows:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert button or icon

Insert the new user information for the selected server.

Clear button or icon

Clears the user information displayed on the current page.

MIB2 System Group Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the MIB2 System Group Configuration page to specify the name and physical location of the contact person for MIB2 managed mode.

The following table describes the MIB2 System Group Configuration page.

MIB2 System Group Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to update the MIB2 contact information. After you select a server, Emergency Responder displays fields in which you enter the name and physical location of the contact.

System Contact

The name of the MIB2 contact.

System Location

The physical location of the managed node.

Update button or icon

Saves the updated MIB2 contact information.

Clear button or icon

Clears the MIB2 contact information displayed on the current page.

CPU and Memory Usage

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the CPU and Memory Usage page to view the CPU and memory usage for the Emergency Responder system.

The following table describes the CPU and Memory Usage page.

CPU and Memory Usage Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Set the screen reset value

Specify in seconds how often this page should be refreshed.

Set CPU Logging Interval

Specify in seconds how often CPU usage is logged. The interval must be between 5 and 600 seconds.

Processors

This section displays the percentage of CPU time being used by various system components.

Download CPU Log File

Click this link to download the currently displayed CPU and memory usage information to a file. 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 2.

Processor

Name of the processor.

%User

Percentage of processor time being used by the User mode.

%System

Percentage of processor time being used by the System mode.

%Nice

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

Percentage of time in which the processor is idle.

%Irq

Percentage of processor time being used by interrupt requests (IRQ).

%Softirq

Percentage of processor time being used by soft IRQs.

Note:
A soft IRQ is an interrupt request that can be deferred.

%I/O Wait

Percentage of time that the processor is executing read or write operations.

%CPU

The processor's share of the elapsed CPU time (excluding idle time) since last update, expressed as a percentage of CPU time.

Start Log button

Starts a log file of the current CPU usage.

Note:
You can create a maximum of 25 CPU log files.

Memory

This section displays the percentage of memory allocated for different uses.

Download Memory Log File

Click this link to download to a file the currently displayed CPU and memory usage information. When you click this link, a new page opens that lists all the saved CPU log files. For more information about this screen, see Table 3.

Total (KB)

The amount of memory available, in kilobytes.

Used (KB)

Amount of memory currently being used, in kilobytes.

Free (KB)

Amount of memory that is available for use, in kilobytes.

Shared (KB)

Amount of memory used by shared processes, in kilobytes.

Buffers (KB)

Amount of memory used by buffers, in kilobytes.

Cached (KB)

Amount of memory used for caching, in kilobytes.

Total Swap (KB)

Amount of total swap space, in kilobytes

Used Swap (KB)

Amount of swap space currently being used, in kilobytes.

Free Swap (KB)

Amount of available swap space, in kilobytes

%VM Used

Amount of virtual memory being used.

Start Log button

Starts a log file of the current memory usage.

Use the CPU Log Files page to view and download the CPU log files.

The following table describes the CPU Log Files page.

CPU Log Files Page

Field

Description

Download button

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.

CPU Log Files

This section displays the details of the saved CPU log files.

File Name

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.

Last Modified

Date and time of the last modification to the CPU log file.

File Size (KB)

Size of the CPU log file, in kilobytes.

Use the Memory Log Files page to view and download the memory log files.

The following table describes the Memory Log Files page.

Memory Log Files Page

Field

Description

Download button

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.

Memory Log Files

This section displays the details of the saved Memory log files.

File Name

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.

Last Modified

Date and time of the last modification to the Memory log file.

File Size (KB)

Size of the Memory log file, in kilobytes.

Processes

The Processes page appears when you choose System Monitor > Processes.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Processes page to view and download information about 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.

The following table describes the Processes page.

Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

Download Log File

Click this link to download log files you have created. You cannot download log files until you have first created them.

Select

Check boxes that allow you to select files to be viewed or downloaded.

Process

Name of the process.

PID

ID number of the process.

%CPU

Percentage of processor time being used by the process.

Status

Task's process status: Running (R), Sleeping (S), Uninterruptible disk sleep (D), Zombie (Z), 4 Traced (T), Paging (P)

Nice (Level)

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.

Vm RSS (KB)

Resident set currently in physical memory in kilobytes, including Code, Data and Stack.

Vm Size (KB)

Size of virtual memory, in kilobytes.

Vm Data (KB)

Amount of data currently stored in virtual memory, in kilobytes.

Thread Count

Number of program threads currently running.

Data Stack (KB)

Size of the data stack, in kilobytes.

Page Fault Count

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.

The following table describes the View Selected Processes page.

View Selected Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

View All Processes button

Returns you to the previous Processes screen, which displays all running processes.

Start Log button

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 1.

Disk Usage

The Disk Usage page appears when you choose System Monitor > Disk Usage.

Authorization Requirements

You must have serviceability authority to access this page.

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.

The following table describes the Disk Usage page.

Disk Usage Page

Field

Description

Disk Usage Details

Partition

Name of the partition.

Size

Size of the partition.

Percentage Used

How much disk space is the partition using, as a percentage of total allocated disk space.

Available Space

How much disk space is currently available on the partition.

Used Space

How much disk space is the partition using.

System Logs Menu

The System Logs menu contains the following submenus, under which all system logs are grouped:

- System Logs > Emergency Responder Logs

- System Logs > Platform Logs

- System Logs > DB Logs

- System Logs >CLI Output Files

Authorization Requirements

You must have serviceability authority to access the System Logs pages.

Note

Use the Up and Down arrows next to each column heading to sort the information by each category.

The following table describes the System Logs pages.

General Description of System Logs Pages

Field

Description

Download button

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 creates a Zip file that contains the log files to be downloaded.

File Name

Name of the log file. If you click 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.

Reload Log File button

Reloads the log file currently being viewed, so that any updates can be seen.

Note:
This button is only available when you have clicked a file name and are viewing the contents of particular log file.

Last Modified

Date the log file was last modified.

File Size (KB)

Size of the log file, in kilobytes.

Descriptions of Individual System Log File Pages

Menu/Log File Page

Description

CER Logs > CER Admin

View or download Emergency Responder Admin logs.

CER Logs > CER Server

View or download Emergency Responder Server logs.

CER Logs > CER Phone Tracking

View or download Emergency Responder Phone Tracking logs.

CER Logs > JTAPI

View or download JTAPI logs.

CER Logs > Tomcat

View or download Tomcat logs.

CER Logs > Event Viewer

View or download Emergency Responder Event logs.

CER Logs > Audio Driver

View or download Emergency Responder Audio Driver logs.

Platform Logs > CLI

View or download CLI operations logs.

Platform Logs > CLM

View or download CLM (Cluster Manager) logs.

Platform Logs > Certificate Management/IPSec

View or download Certificate Management and IPSec logs.

Platform Logs > DRS

View or download DRS (Disaster Recovery System) logs.

Platform Logs > Install/Upgrade

View or download Installation and Upgrade logs.

Platform Logs > Remote Support

View or download Remote Account creation and operations logs.

Platform Logs > Syslog

View or download Syslog logs.

Platform Logs > Servm

View or download Servm (Services Manager) logs.

DB Logs > Cerdbmon

View or download Cerdbmon logs.

DB Logs > Install DB

View or download InstallDB Utility logs.

CLI OutputFiles >Platform

View or download Platform log files.

CLI OutputFiles >DB

View or download DB log files.

Appendix D. Cisco Unified Operating System Administration Web Interface

ServerGroup

The ServerGroup page appears when you choose Show > ServerGroup.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the ServerGroup page to view information about the Emergency Responder servers in the server group.

The following table describes the ServerGroup page.

ServerGroup Page

Field

Description

ServerGroup

Hostname

Displays the name of the host.

IP Address

Displays the IP address of the host.

Alias

Displays the alias of the host

Type of Node

Displays the node type of the host.

Hardware Status

The Hardware Status page appears when you choose Show > Hardware.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Hardware Status page to view information about the Emergency Responder hardware.

The following table describes the Hardware Status page.

Hardware Status Page

Field

Description

Hardware Resources

Platform Type

Model identity of the platform server

Processor Speed

Speed of the processor

CPU Type

Type of processor in the platform server

Memory

Total amount of memory in Mbytes

Object ID

Object ID of the platform server

OS Version

Operating system version running on the platform server

RAID Details

Detailed summary of the platform hardware

Network Configuration

The Network Configuration page appears when you choose Show > Network.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Network Configuration page.

Network Configuration Page

Field

Description

Ethernet Details

DHCP Status

Indicates whether DHCP is enabled for Ethernet port 0.

Status

Indicates whether the port is Up or Down for Ethernet ports 0 and 1.

IP Address

Shows the IP address of Ethernet port 0 (and Ethernet port 1 if Network Fault Tolerance (NFT) is enabled).

IP Mask

Shows the IP mask of Ethernet port 0 (and Ethernet port 1 if NFT is enabled).

Link Detected

Indicates whether there is an active link.

Queue Length

Displays the length of the queue.

MTU

Displays the maximum transmission unit.

MAC Address

Displays the hardware address of the port.

RX Stats

Displays information about received bytes and packets.

TX Stats

Displays information about transmitted bytes and packets.

DNS Details

Primary DNS

Displays the IP address of the primary domain name server.

Secondary DNS

Displays the IP address of the secondary domain name server.

Options

Displays the number of attempts and timeouts.

Domain

Displays the domain of the server.

Gateway

Displays the IP address of the network gateway on Ethernet port 0.

Software Packages

The Software Packages page appears when you choose Show > Software.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Software Packages page to view the software versions and installed software options.

The following table describes the Software Packages page.

Software Packages Page

Field

Description

Partition Versions

Displays the software version that is running on the active and inactive partitions.

Active Version Installed Software Options

Displays the versions of installed software options that are installed on the active version.

Inactive Version Installed Software Options

Displays the versions of installed software options that are installed on the inactive version.

System Status

The System Status page appears when you choose Show > System.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the System Status page to view the status of the Emergency Responder system.

The following table describes the System Status page.

System Status Page

Field

Description

Host Name

Name of the Cisco UCS host where the Emergency Responder system is installed.

Date

Date and time based on the continent and region that were specified during operating system installation.

Time Zone

Time zone that was chosen during installation.

Locale

Locale of the system.

Product Version

Operating system version.

Platform Version

Platform version.

Uptime

Displays system uptime information.

CPU

Displays the percentage of CPU capacity that is idle, the percentage that is running system processes, and the percentage that is running user processes.

Memory

Displays information about memory usage, including the amount of total memory, free memory, and used memory in kilobytes.

Disk/active

Displays the amount of total, free, and used disk space on the active disk.

Disk/inactive

Displays the amount of total, free, and used disk space on the inactive disk.

Disk/logging

Displays the amount of total, free, and disk space that is used for disk logging.

IP Preferences

The IP Preferences page appears when you choose Show > IP Preferences.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the IP Preferences page to view a list of registered ports that can be used by the system. The following table describes the IP Preferences page.

IP Preferences Page

Field

Description

Application

Name of the application using (listening on) the port.

Protocol

Protocol used on this port (TCP, UDP, and so on).

Port Number

Numeric port number.

Type

Type of traffic allowed on this port:

- Public—All traffic allowed.

- Translated—All traffic allowed but forwarded to a different port.

- Private—Traffic only allowed from a defined set of remote servers, for example, other servers in the server group.

Translated Port

Traffic destined for this port get forwarded to the port listed in the Port Number column. This field applies to Translated type ports only.

Status

Status of port usage:

- Enabled—In use by the application and opened by the firewall.

- Disabled—Blocked by the firewall and not in use.

Description

Brief description of how the port is used.

Ethernet Configuration

The Ethernet Configuration page appears when you choose Settings > IP > Ethernet.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Ethernet Configuration page.

Ethernet Configuration Page

Field

Description

DHCP Information

DHCP

Indicates whether DHCP is enabled or disabled and allows you to change the DHCP setting using the pull-down menu.

Host Information

Hostname

Displays the server name (Display only—Cannot configure).

Port Information

IP Address

Displays the IP address of the system. You can change the IP address by entering a new IP address in the text box.

Subnet Mask

Displays the IP subnet mask address. You can change the mask by entering a new subnet mask in the text box.

Gateway Information

Default Gateway

Displays 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.

Save button or icon

Saves any changes made to the Ethernet Configuration page.

Caution:
If you click Save, the machine reboots. Do not click Save unless you want to shut down and reboot your system.

Note:
To recognize any new IP addresses, both servers in the server group must be manually rebooted.

Publisher Settings

The Publisher Settings page appears when you choose Settings > IP > Publisher.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Publisher Settings page to view or change the Publisher hostname or IP address.

Note

You can only view and change the publisher hostname IP address only on the Emergency Responder Subscriber, not on the Emergency Responder publisher itself. Changing these fields must be followed by an immediate reboot of the Subscriber.

Publisher Settings Page

Field

Description

Hostname

Displays the hostnames of the Emergency Responder Publisher for this Subscriber. To change the hostname, enter the new hostname in the text box, and click Save.

IP Address

Displays the IP address of the Emergency Responder Publisher for this Subscriber. To change the IP address, enter the IP address in the text box, and click Save.

Save button or icon

Saves the information in the Publisher Configuration Settings page.

NTP Server List

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

Authorization Requirements

You must have platform administrator authority to access this page.

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 to 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.

The following table describes the NTP Server List page.

NTP Server List Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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.

Clear All button or icon

Deselects all NTP servers listed. When you click this button or icon, all check marks disappear.

Note:
The Clear All button or icon is only visible if you have previously configured one or more NTP servers.

Delete Selected button or icon

Deletes the selected NTP server. To delete an NTP server, you must first select it from the list of NTP servers. Click 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.

The following table describes the NTP Server Configuration page.

NTP Server Configuration Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server Settings

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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.

SMTP Settings

The SMTP Settings page appears when you choose Settings > SMTP.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the SMTP Settings page to manually configure the SMTP host.

The following table describes the SMTP Settings page.

SMTP Settings Page

Field

Description

Status

Displays the status of the SMTP Settings page.

SMTP Host

Hostname or IP Address

Enter the hostname or IP address of the SMTP server in the text box.

Host Status

Displays the status of the SMTP host server.

Save button or icon

Saves changes made to the SMTP Settings page.

Time Settings

The Time Settings page appears when you choose Settings > Time.

Authorization Requirements

You must have platform administrator authority to access this page.

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 NTP Server List for more information.

Caution

If you change the server time, you must reboot both the Publisher and the Subscriber.

The following table describes the Time Settings page.

Time Settings Page

Field

Description

Date

Allows you to set the month, day, year, hours, minutes, and seconds using the pull-down menus.

Save button or icon

Saves changes made to the Time Settings page.

Version Settings

The Version Settings page appears when you choose Settings > Version.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Version Settings page to restart or shutdown the system and to switch software versions.

Note

You must have a different software version installed on the inactive partition to switch versions.

Caution

Initiating this action causes the system to restart and become temporarily unavailable.

The following table describes the Version Settings page.

Version Settings Page

Field

Description

Status

Displays the current status.

Installed Versions

Active Version

Displays the version running on the active partition.

Inactive Version

Display the version on the inactive partition.

Restart button or icon

Restarts the system.

Shutdown button or icon

Shuts down the system.

Switch Versions button or icon

Actives the software version on the inactive partition.

Note:
The Switch Versions button or icon is only visible if there is a software version installed on the inactive partition.

Certificate List

The Certificate List page appears when you choose Security > Certificate Management.

Authorization Requirements

You must have platform administrator authority to access this page.

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

The following table describes the Certificate List page.

Certificate List Page

Field

Description

Status

Displays the current status.

Certificate List

Find certificate list where

Enter search criteria for the certificate lists you want to find.

To find all certificate lists by file name, select File Name from the pull-down menu and click Find without entering any criteria.

To find all certificate lists by certificate name, select Certificate Name from the pull-down menu and click Find without entering any criteria.

To narrow your search:

- Select the search relationship (begins with, contains, and so on) from the pull-down 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 pull-down 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 7 for information about the Certificate Configuration Page.

Generate New button or icon

Allows you to generate a new certificate. When you click Generate New, the Generate Certificate page appears. See Table 2 for a description of the Generate Certificate page.

Upload Certificate 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 3 for a description of the Upload Certificate page.

Upload CTL button or icon

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 4 for a description of the Upload Certificate Trust List page.

Generate CSR button or icon

Allows you to generate a new Certificate Signing Request (CSR). When you click Generate CSR, the Generate Certificate Signing Request page appears. See Table 5 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 6 for a description of the Download Certificate Signing Request page.

The following table describes the Generate Certificate page.

Generate Certificate Page

Field

Description

Status

Displays the current status of the Generate Certificate page.

Generate Certificate

Certificate Name

Allows you to choose a certificate name from the pull-down menu.

Generate New button or icon

Generates a new certificate. You must first select a Certificate Name from the pull-down menu.

Close button or icon

Closes the Generate Certificate page.

The following table describes the Upload Certificate page.

Upload Certificate Page

Field

Description

Status

Displays the current status of the Upload Certificate page.

Upload Certificate

Certificate Name

Use the pull-down menu to select the name of the certificate to upload.

Root Certificate

Enter the name of the root certificate.

Upload File

Use the Browse button to select the file to be uploaded.

Upload File button or icon

Uploads the certificate file specified in the Upload Certificate section.

Close button or icon

Closes the Update Certificate page.

The following table describes the Upload CTL page.

Upload CTL Page

Field

Description

Status

Displays the current status of the Upload CTL page.

Upload Certificate

Certificate Name

Use the pull-down menu to select the name of the CTL file to upload.

Root Certificate

Enter the name of the root certificate.

Upload File

Use the Browse button to select the file to be uploaded.

Upload File button or icon

Uploads the certificate file specified in the Upload Certificate Trust List section.

Close button or icon

Closes the Update CTL page.

The following table describes the Generate CSR page.

Generate CSR Page

Field

Description

Status

Displays the current status of the Generate CSR page.

Generate Certificate Signing Request

Certificate Name

Use the pull-down menu to select the name of the CTL file to generate.

Generate CSR button or icon

Generates a new CSR.

Close button or icon

Close the Generate CSR page.

The following table describes the Download CSR page.

Download CSR Page

Field

Description

Status

Displays the current status of the Download CSR page.

Download Certificate Signing Request

Certificate Name

Use the pull-down menu to select the name of the CTL file to download.

Download CSR button or icon

Downloads the CSR specified in the Download Certificate Signing Request section.

Close button or icon

Closes the Download CSR page.

The following table describes the Certificate Configuration page.

Certificate Configuration Page

Field

Description

Status

Displays the current status of the Certificate Configuration page.

Certificate Settings

Displays the following information about the certificate:

- File Name

- Certificate Name

- Certificate Type

- Certificate Group

- Description

Certificate File Data

Displays the contents of the certificate file.

Delete button or icon

Deletes the current certificate.

Download button or icon

Downloads the certificate to your local system.

Certificate Monitor

The Certificate Monitor page appears when you choose Security > Certificate Monitor.

Authorization Requirements

You must have platform administrator authority to access this page.

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

The following table describes the Certificate Monitor page.

Certificate Monitor Page

Field

Description

Status

Displays the current status of the Certificate Monitor page.

Certificate Monitor Configuration

Notification Start Time

Enter the number of days before the certificate expires that you want to be notified.

Notification Frequency

Enter the notification frequency and click one of the radio buttons to indicate days or hours.

Enable Email Notification

Check the box to the enable email notification.

Note:
For the system to send notifications, you must configure an SMTP host.

Email ID

Enter the email addresses of those to be notified in the text box. Enter multiple e-mail addresses by separating each address with a semicolon (;). There should be no spaces between the email addresses.

Save button or icon

Saves the information entered on the Certificate Monitor page.

IPSec Policy List

The IPSec Policy List page appears when you choose Security > IPSec Configuration.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the IPsec Policy List page to display existing IPsec policies, add an additional IPsec policy, or modify an existing IPsec policy.

The following table describes the IPsec Policy List page.

IPSec Policy List Page

Field

Description

Status

Displays the current status of the IPsec Policy List page.

IPSec Policy List

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 2 for information about the IPsec Policy Configuration page.

The following table describes the IPSec Policy Configuration page.

IPSec Policy Configuration Page

Field

Description

Status

Displays the current status of the IPsec Policy Configuration page.

IPSec Policy Details

Policy Group Name

Policy Name

Specifies the name of the IPsec policy.

Authentication Method

Specifies the authentication method.

Preshared Key

Specifies the preshared key if you selected Pre-shared Key in the Authentication Name field.

Peer Type

Specifies whether the peer is the same type or different.

Certificate Name

The name of the certificate.

Destination Address

Specifies the IP address or FQDN of the destination.

Destination Port

Specifies the port number at the destination.

Source Address

Specifies the IP address or FQDN of the source.

Source Port

Specifies the port number at the source.

Mode

Specifies Tunnel or Transport mode.

Remote Port

Specifies the port number to use at the destination.

Protocol

Specifies the specific protocol, or Any:

- TCP

- UDP

- Any

Encryption Algorithm

From the drop-down list, choose the encryption algorithm. Choices include:

- DES

- 3DES

Hash Algorithm

Specifies the hash algorithm:

- SHA1—Hash algorithm that is used in phase 1 IKE negotiation.

- MD5—Hash algorithm that is used in phase 1 IKE negotiation.

ESP Algorithm

From the drop-down list, choose the ESP algorithm. Choices include:

- NULL_ENC

- DES

- 3DES

- BLOWFISH

- RIJNDAEL

Phase 1 DH Group

Phase One Life Time

Specifies the lifetime for phase One, IKE negotiation, in seconds.

Phase One DH

From the drop-down list, choose the phase One DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18.

Phase 1 DH Group

Phase Two Life Time

Specifies the lifetime for phase Two, IKE negotiation, in seconds.

Phase Two DH

From the drop-down list, choose the phase Two DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18.

IPSec Policy Configuration

Enable Policy

Check the check box to enable the policy.

Save button or icon

Saves the changes made to the IPsec Policy List page.

Software Installation/Upgrade

The Software Installation/Upgrade page appears when you choose Software Upgrades > Install/Upgrade.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Software Installation/Upgrade page to install or upgrade software from a DVD/CD or from a file system on a remote server.

The following table describes the Software Installation/Upgrade page.

Software Installation/Upgrade Page

Field

Description

Status

Displays the current status of the Software Installation/Upgrade page.

Software Location

Source

Pull-down menu used to specify the source for the installation/upgrade. Options are DVD/CD or Remote Filesystem.

Directory

The name of the directory containing the files.

Note:
If the upgrade file is on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path that you want to specify. For example, if the upgrade file is in the patches directory, you must enter /patches. If the upgrade file is on a Windows server, check with your system administrator for the correct directory path.

Server

The hostname or IP address of the remote server from which the software is downloaded.

User Name

The name of a user who is configured on the remote server.

User Password

Password that is configured for this user on the remote server.

Transfer Protocol

Pull-down 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 pull-down menu. If you selected DVD/CD, this pull-down menu is grayed out.

Cancel Install button or icon

Cancels the installation or upgrade procedure.

Next button or icon

Continues with the installation or upgrade procedure.

Ping Configuration

The Ping Configuration page appears when you choose Services > Ping.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Ping Configuration page to send ping requests to test if other systems are reachable over the network.

The following table describes the Ping Configuration page.

Ping Configuration Page

Field

Description

Status

Displays the current status of the Ping Configuration page.

Ping Settings

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

Text box in which you enter the amount of time between ping requests, in seconds.

Packet Size

Text box into which you enter the packet size of the ping request.

Ping iterations

Pull-down 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

Select the check box to have the system validate IPsec.

Ping Results

Text box in which the ping results are displayed.

Ping button or icon

Sends the ping request.

Remote Access Configuration

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

Authorization Requirements

You must have platform administrator authority to access this page.

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. If the account duration limit expires, Cisco support can not 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:

1. Call Cisco support and provide them with the remote support account name and pass phrase.

2. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase.

3. 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 can create a new account.

The following table describes the Remote Access Configuration page.

Remote Access Configuration Page

Field

Description

Status

Displays the current status of the Remote Access Configuration page.

Remote Access Account Information

Account Name

Name for the new remote account. Account names must be at least six-characters long and consist of all lowercase, alphabetic characters

Account Duration

The amount of time that the remote account exists, in days.

Save button or icon

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 2 for a description of the fields on the Remote Access Configuration page.

Delete button or icon

Deletes the currently configured remote account.

Note:
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.

The following table describes the Remote Access Configuration page.

Remote Access Configuration Page

Field

Description

Remote Access Account Information

Account Name

Displays the name of the remote support account.

Expiration

Displays the date and time when access to the remote account expires.

Passphrase

Displays the generated pass phrase.

Decode Version

Indicates the version of the decoder in use.

Delete button or icon

Deletes the remote access account information.

Appendix E. Disaster Recovery System Web Interface

Backup Device List

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Device List page to list, add, and delete backup devices.

The following table describes the Backup Device List page.

Backup Device List Page

Field

Description

Backup Device List

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.

Add New button

Adds a new backup device. When you click the Add icon, the Backup Device page appears. See Table 2 for information about the Backup Device page.

Select All button and icon

Selects all the listed backup devices.

Clear All button and icon

Deselects all selected backup devices.

Delete Selected button and icon

Deletes the selected backup devices.

The following table describes the Backup Device page, which you use to add new backup devices.

Backup Device Page

Field

Description

Backup device name

Enter the device name in the text box (required).

Select Destination

To select the backup destination, click the Tape Device or Network Directory radio button (required).

Tape Device

Select the name of the tape device from the pull-down menu.

Network Directory

In the fields provided, enter the Server name, Path name, User name, and Password for the Network Directory.

Number of backups to store on the Network Directory

Select the number of backups using the pull-down menu.

Save button and icon

Saves the information about the new backup device.

Back button and icon

Returns to the Backup Device List page.

Schedule List

The Schedule List page appears when you choose Backup > Scheduler.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Schedule List page.

Schedule List Page

Field

Description

Schedule List

Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click 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 2 for information about 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.

Clear All button or icon

Deselects all selected schedules.

Note:
The Clear All button only appears if no schedules have been configured.

Delete Selected button or icon

Deletes the selected schedules.

Note:
The Delete Selected button only appears if no schedules have been configured.

Enable Selected Schedules button or icon

Enables the selected schedules.

Note:
The Enable Selected Schedules icon only appears if no schedules have been configured.

Disable Selected Schedules button or icon

Disables the selected schedules.

Note:
The Disable Selected Schedules button only appears if no schedules have been configured.

The following table describes the Scheduler page.

Scheduler Page

Field

Description

Status

Displays the status of the Scheduler page.

Schedule Name

Enter the name of the schedule in the text box.

Select Backup Device

Select the name of the backup device from the pull-down menu.

Select Features

Select Emergency Responder as the feature to be backed up.

Start Backup at

Date

From the pull-down menus, enter the year, month, and day on which the backup starts.

Time

From the pull-down menus, enter the hour and minute at which the backup starts.

Frequency

Once

Click this radio button to schedule a single backup.

Daily

Click this radio button to schedule a daily backup.

Weekly

Click this radio button to schedule a weekly backup. Check the check boxes to specify the days on which the weekly backup is scheduled.

Monthly

Click this radio button to schedule a monthly backup.

Save button or icon

Saves the backup schedule information.

Set Default button or icon

Saves the information entered as the default for scheduled backups.

Disable Schedule button or icon

Disables the Schedule. If the Schedule is currently disabled, this button is grayed out.

Enable Schedule button or icon

Enables the Schedule. If the Schedule is currently enabled, this button is grayed out.

Back button or icon

Returns to the Scheduler List page.

Manual Backup

The Manual Backup page appears when you choose Backup > Manual Backup.

Authorization Requirements

You must have platform administrator authority to access this page.

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 are not backed up.

The following table describes the Manual Backup page.

Manual Backup Page

Field

Description

Select Backup Device

Select the name of the backup device from the pulldown menu.

Select Features

Check Emergency Responder as the feature to be backed up.

Start Backup button or icon

Starts a manual backup.

Select All button or icon

Selects all the listed features.

Clear All button or icon

Deselects all selected features.

Backup History and Restore History

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup History page to view information about past backups. Use the Restore History page to view information about past restore operations.

The following table describes the Backup History page.

Backup History Page

Field

Description

Backup History information

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.

The following table describes the Restore History page.

Restore History Page

Field

Description

Restore History information

The following information about past backups is displayed:

- Tar Filename

- Backup Device

- Completed On

- Result

- Features Restored

Refresh button or icon

Refreshes the information in the Restore History page.

Backup Status

The Backup Status page appears when you choose Backup > Current Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Status page to view status information about the current backup.

The following table describes the Backup Status page.

Backup Status Page

Field

Description

Status

Provides information about the status of the current backup.

Backup Details

The following information about the current backup is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current backup.

Cancel Backup button or icon

Cancels the current backup.

Restore Wizard

The Restore Wizard page appears when you choose Restore > Restore Wizard.

Authorization Requirements

You must have platform administrator authority to access this page.

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 Restore—Choose Backup Device page to select the backup device to be used for the backup.

The following table describes the Step1 Restore—Choose Backup Device page.

Step 1 Restore—Choose Backup Device Page

Field

Description

Status

Indicates the current status of the recovery operation.

Select Backup Device

Select the backup device using the pull-down menu.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step2 Restore—Choose the Backup Tar File page to select the backup tar file to be restored.

The following table describes the Step2 Restore—Choose the Backup Tar File page.

Step 2 Restore—Choose the Backup Tar File Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Backup File

Use the pull-down menu to select the tar file for backup

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step3 Restore—Select the Type of Restore page to select the features to be restored.

The following table describes the Step3 Restore—Select the Type of Restore page.

Step 3 Restore—Select the Type of Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Features

Click the box to the left of the Emergency Responder feature name to select the Emergency Responder feature for backup.

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step4 Restore—Final Warning for Restore page to select the servers to be restored.

The following table describes the Step4 Restore—Final Warning for Restore page.

Step 4 Restore—Final Warning for Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Warning

Displays a warning message stating that the restore operation overwrites all existing data on the selected servers.

Select the Servers to be restored for each Feature

Under the Emergency Responder feature name, select the servers to be restored. To do so, click the check box to the left of the server name.

Back button or icon

Returns to the previous page in the Restore Wizard.

Restore button or icon

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.

Caution:
The restore operation overwrites any existing data on the selected servers.

Cancel button or icon

Cancels the restore operation.

Restore Status

The Restore Status page appears when you choose Restore > Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Restore Status page to view the status of restore operations.

The following table describes the Restore Status page.

Restore Status Page

Field

Description

Status

Provides information about the status of the current restore operation.

Restore Details

The following information about the current restore operation is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current restore operation.

Appendix F. Admin Utility Web Interface for Cisco Emergency Responder

Update Cisco Unified Communications Manager Version

The Upgrade CUCM Version page appears when you choose Update > CUCM Version.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Upgrade CUCM Version page to select a different version of Cisco Unified Communications Manager.

The following table describes the Upgrade CUCM Version page.

Upgrade CUCM Version Page

Field

Description

Status

Displays the current Cisco Unified Communications Manager version.

CUCM Version Details

Choose the Cisco Unified Communications Manager version to upgrade

Use the pull down menu to select a version of Cisco Unified Communications Manager.

Go button

Click Go to begin the update process.

Note:
Change the CUCM version separately on the Publisher and Subscriber nodes.

Cancel button

Cancels the Cisco Unified Communications Manager update.

Update Cluster DB Host

The Update Cluster DB Host page appears when you choose Update > Cluster DB Host.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Update Cluster DB Host page to designate a new server as the Emergency Responder cluster database host server.

The following table describes the Update Cluster DB Host page.

Update Cluster DB Host Page

Field

Description

Status

Displays the name of the current cluster database host

Cluster DB Host Details

ClusterDB Hostname/IP Address

Enter the hostname (if DNS is configured) or the IP address of the new cluster database host.

Note:
If the cluster is spread across domains, then enter a fully qualified hostname.

Password

Enter the password for the new cluster database host

Confirm Password

Reenter the password for the new cluster database host.

Go button

Click the Go button to designate the new server as the new cluster database host.

Note:
The Emergency Responder Cluster DB host details are updated. Emergency Responder services must be restarted for this change to take effect. You must restart Emergency Responder Services by rebooting the Emergency Responder publisher and subscriber servers. Only restarting Emergency Responder services does not work because the IP address is cached by other services and this updates the Emergency Responder Cluster DB host details for this server group only. Other servers in this Emergency Responder cluster are NOT updated automatically. For further details, see Update Emergency Responder Cluster Database Host Details.

Cancel button

Cancels the Update Cluster DB Host operation.

Appendix G. Using AFT for Specific Service Providers

ALI Formatting Tool for Bell Canada

The following topics describe how to use AFT for Bell Canada.

Transaction Code Modifications

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 rejects the record and returns it in an Error Return file with an error message.

The following table shows the values displayed in the Function Field in NENA records and the corresponding values for the Transaction Code in Bell Canada records.

NENA and Bell Canada Function/Transaction Fields

NENA Function Code Field

Bell Canada Transaction Code Field

I for Insert a new record.

A for Add a new record.

C for Change a record.

A for Change a record.

Note:
The NENA Function Code C is mapped to Bell Canada's Transaction Code A.

D for Delete a record.

D for Delete a record.

Bell Canada Data

The following table describes the remaining Bell Canada-specific fields. Some fields require data to generate ALI files in the format specified in Bell Canada's ALI data support documentation; other fields can remain blank.

If there is an error in these fields, Bell Canada rejects the record and sends back an 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.

Modifying Bell Canada-Specific Fields

Field

Description

Format

Notes

Service Class

Type of telephone service of the customer's Terminal Number.

3 alphanumeric characters

Required field.

Postal Code

Postal code of the customer's service address.

6 alphanumeric characters

Required field. The first character must be alphabetic.

Municipality Code

Unique code assigned to each municipality.

3 alphanumeric characters

Required field.

Class of Service

Code that identifies the grade, class, and type of service.

5 alphanumeric characters

Required field.

System Source

Identifies the source database of the Transaction Record.

1 alphabetic character

Required field.

Location Type

Type of location within a building (for example, apartment).

15 alphanumeric characters

Optional field.

Location Number

Number of the location identified in the Location Type field (for example, apartment 2, floor 2).

6 alphanumeric characters

Optional field.

Service Municipality

City, town, village, borough, or locality.

35 alphanumeric characters

Required field.

LSP ID

Unique code provided to the PS ALI customer by Bell Canada that denotes the provider of local telephone service.

5 alphanumeric characters

Required field.

Must be the valid LSP Identifier provided to the PS ALI customer by Bell Canada.

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.

Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder to correct errors reported by Ameritech, you may need to use AFT to change the Function Code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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.

ALI Formatting Tool for SBC-PacBell

The following sections describe how to use the AFT for SBC-PacBell.

Call Back for ELIN Enablement

Emergency Responder displays the ELIN at the PSAP. If the emergency call is cut off for any reason, or if the PSAP 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.

We recommend 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.)

Function Code Modifications

Emergency Responder 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 Emergency Responder to correct errors reported by your service provider, you may need to use AFT to change the function code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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.

ALI Formatting Tool for SBC-Southwestern Bell

The following sections describe how to use the AFT for SBC-Southwestern Bell.

PS Code for SBC-Southwestern Bell

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, see the Southwestern Bell documentation.

Function Code Modifications

Emergency Responder 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 Emergency Responder to correct errors reported by your service provider, you may need to use AFT to change the function code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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.

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 (Emergency Responder) 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 Emergency Responder to correct errors reported by Qwest, you may need to use AFT to change the function code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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

ALI Formatting Tool for Verizon

The following sections describe how to use the AFT for Verizon.

Function Code Modifications

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.

Emergency Responder sets the function code to one of the following:

- I—Inserting a new ALI record (the default)

- C—Updating an ALI record, such as changing a street name

- D—Deleting an ALI record

- U—Unlocking an ALI Record (included to support Local Number Portability)

- M—Migrating an ALI Record (included to support Local Number Portability)

If you make changes to an ALI record in Emergency Responder to correct errors reported by Verizon, you may need to use AFT to change the function code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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.

Verizon New England State Disability Indicator Modifications

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.

The following table shows the Disability Indicator designations that you can use to populate the location field of an ALI record.

Disability Indicator Descriptions

Disability Indicator

Description

LSS

Life Support System

MI

Mobility Impaired

B

Blind

DHH

Deaf and Hard of Hearing

TTY

Teletypewriter

SI

Speech Impaired

DD

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).

Customer Name for Verizon West State Modifications

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 which uses a comma followed by a space between the last name and the first name. For example, 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 field—one in the Emergency Responder 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 Emergency Responder GUI.

New Jersey Location Modifications

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 field—one in the Emergency Responder 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 Emergency Responder GUI.

Appendix H. Event Log Messages

CER_DATABASE

CER_DATABASE Event Log Messages

Type

Message

INFO

Failed to get the fully qualified host name. DNS might not be enabled. Putting Ipaddress in Cluster database.

ERROR

CER Server Memory Usage is HIGH - above threshold value of 80%

ERROR

Database replication BROKEN.

ERROR

Number of <NUM> limit exceeded. Fetching only a maximum of *** <NUM> *** entries

CER_SYSADMIN

CER_SYSADMIN Event Log Messages

Type

Message

ERROR

Failed to add this CER group to CER cluster.

WARNING

Cisco ER cluster functionality will not work till this problem is fixed.

1. Check if "CERCluster password" is same as in Cisco ER ClusterDB.

2. Check if Cisco Tomcat and Database services are running on Cisco ER ClusterDB.

3. Check if Cisco ER ClusterDB Hostname is correct and accessible.

For more details see EventViewer on ER Server.<Error reason>.

ERROR

Failed to initialize LDAP. <Error Message>

CER_TELEPHONY

CER_TELEPHONY Event Log Messages

Type

Message

WARNING

Emergency call from<CALLING ADDRESS>has been routed to default ERL because calling party modification failed.

Please make sure that the checkbox "Enable Calling Party Number Modification" is checked on the Call Manager user page for the CER user. PSAP callbacks MAY NOT work correctly. The CER service will need to be restarted once the flag is checked on the Call Manager User page.

WARNING

Emergency call from<calling address>could not be routed using the following Routepatterns.

<LIST OF RP's>

Call Routed to <RP/NUMBER>

Please check the availablility 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 CER, please disable them.

2. If the "Calling Party Number Modification" flag on the CER user page in the call manager is not enabled, please enable it.

ERROR

Failed to load class <CLASS NAME>.

ERROR

CCMString is empty can't load telephony classes.

WARNING

Got OutOfService event from provider: <PROVIDER_NAME>.

INFO

Got InService event from provider: <PROVIDER_NAME>.

WARNING

Logged out of the duplicate provider - <CTI_Manager> from CER. Specify the CTI Ports (if any) of this provider, in a different CCM node.

ERROR

Cannot register media terminal for port: <PORT_NUMBER>.

WARNING

CTI Port: <PORT_NUMBER> is in OUTOFSERVICE, trying after 10 seconds.

ERROR

Mediachannel creation failed: <ERROR>.

WARNING

Failed to create media channel for: <PORT_NUMBER>.

ERROR

Failed to initiate call to security: <NUMBER> <ERROR>.

<ERROR> corresponds to:

- PrivilegeViolationException

- InvalidPartyException

- MethodNotSupportedException

- InvalidArgumentException

- InvalidStateException

- E911CallRouterException

- <Other Exceptions (if any)>

ERROR

Failed to register route point: <ROUTE_PATTERN> with Provider: <PROVIDER_NAME>.

ERROR

RouteAddress: <ADDRESS> is in OUTOFSERVICE.

WARNING

<ADDRESS> Route Point received IN_SERVICE event from Provider <NAME>.

WARNING

<ADDRESS> Route Point received OUT_OF_SERVICE event from Provider <NAME>.

ERROR

<msg>Address = <CALLING ADDRESS> ; Terminal = <CALLING TERMINAL> because, routeEndEvent returned :<CAUSE>

<msg> corresonds to

Call failed to reach PSAP for : /PSAP Callback failed for :

<CAUSE> corresponds to

CAUSE_INVALID_DESTINATION/CAUSE_ROUTING_TIMER_EXPIRED/CAUSE_PARAMETER_NOT_SUPPORTED/CAUSE_STATE_INCOMPATIBLE/CAUSE_UNSPECIFIED_ERROR

ERROR

<msg>Address = <CALLING ADDRESS> ; Terminal = <CALLING TERMINAL> because, routeEndEvent returned : CAUSE_CTIERR_FAC_CMC_REASON_CMC_NEEDED. Please Uncheck the Requirement of FAC/CMC codes on the Route points used by the Cisco Emergency Responder.

<msg> corresonds to

Call failed to reach PSAP for : /PSAP Callback failed for :

<msg>Address = <CALLING ADDRESS> ; Terminal = <CALLING TERMINAL> because, routeEndEvent returned :<CAUSE>Please Uncheck the Requirement of FAC/CMC codes on the Route points used by the Cisco Emergency Responder.

<msg> corresonds to Call failed to reach PSAP for : /PSAP Callback failed for :

<CAUSE> corresponds to

CAUSE_CTIERR_FAC_CMC_REASON_FAC_INVALID/CAUSE_CTIERR_FAC_CMC_REASON_CMC_INVALID/ CAUSE_CTIERR_FAC_CMC_REASON_FAC_CMC_NEEDED./ CAUSE_CTIERR_FAC_CMC_REASON_CMC_NEEDED.

WARNING

Call from <CALLER ID> could not be routed to the Offpremies ERL : <ERL NAME>.

Possible reasons: The phone-location association has not yet happened or has met with errors.

Device Name: <DEVICE NAME>

Caller ID: <CALLER ID>

WARNING

Call from <CALLER ID> could not be routed to the Offpremies ERL. Possible reasons:

The phone-location association has not yet happened or has met with errors.

WARNING

Failed to get the JTAPI Provider for: <NAME_STRING> trying infinitely.

WARNING

Not registering the provider: <PROVIDER_NAME> as is already registered/in the same CCM Cluster as that of:<element>.

WARNING

JTAPI logs are not enabled as the logs path is empty in E911Bootstrap properties.

ERROR

Failed to get the JTAPI Provider for: <IP Address/Host Name> after <NUMBER> attempts.

WARNING

Currently, no CTI Ports are available to place the call for <CallingAddress>. Phone notification will be retried in the next 60 seconds.

CER_AGGREGATOR

CER_AGGREGATOR Event Log Messages

Type

Message

WARNING

Device <ipaddress> is SNMP unreachable. Please check SNMP settings in CER and also on this CCM. Please confirm proper access privilege ( READ_ONLY ) set on this box for SNMP service. Also, verify n/w connectivity.

WARNING

During discovery some devices are unreachable.

List of Unreachable Switches <List>.

WARNING

WARNING During discovery some devices are unreachable.

List of Unreachable CCMs <List>.

WARNING

CERServer could not communicate with CERPhoneTrackingEngine.

WARNING

CERServer could not communicate with CERPhoneTrackingEngine.

INFO

Device <IP Address> is SNMP unreachable. Please check SNMP settings in CER and also on this CCM. Please confirm proper access privilege ( READ_ONLY ) set on this box for SNMP service. Also, verify n/w connectivity.

INFO

Error in resolving HostName -> IPAddress through DNS, ignoring the seed from DE <IP Address>.

INFO

IP Address mismatch detected,OLD_IP <IP Address> NEW_IP <IP Address> SEED <IP Address> for any changed configuration, deletion and re addition of seed device is recommended.

INFO

Device <IP Address> is not a valid switch.

INFO

Device <IP Address> is SNMP Un-reachable.

INFO

Device <IP Address> is not supported.

INFO

This Device <IP Address> is identified for a different device family than earlier discovered, ignored for this discovery cycle.

INFO

Failed to retrieve SysOid of a device <IP Address> Please check if device is SNMP reachable.

INFO

This device is not supported <seed>.

INFO

This Device <IPADDRESS> is earlier discovered with different device family for changed device config (ipAddress, deviceFamily, dnsName ). Delete and re-add the device is must; also you need to re-enter SNMP community string if changed from earlier one.

INFO

The device <IP Address> is not a valid switch...please confirm.

INFO

This device not a valid CCM to discover <IP Address>.

INFO

Error in resolving HostName -> IPAddress, ignoring the seed for discovery <IP Address>.

INFO

IP Address mismatch detected,OLD_IP <IP Address> NEW_IP <IP Address> SEED <IP Address> for any changed configuration, deletion and re addition of seed device is recommended.

During discovery some devices are unreachable List of Unreachable Switches<SWITCH LIST> Cisco CallManager(s)<CCM LIST>.

Device <IPADDRESS> is SNMP unreachable. Please check SNMP settings in CER and also on device. IF this is a CCM box then please confirm proper access privilege ( READ_ONLY ) set on this box for SNMP service. Also, verify n/w connectivity.

INFO

Device <IP Address> is not a valid CCM.

CER_GROUP

CER_GROUP Event Log Messages

Type

Message

INFO

Active Cisco Emergency Responder set to : <Server Details>.

INFO

Connection established with Cisco Emergency Responder: <PEER>

WARNING

Disconnected from Cisco ER: <PEER>.

ERROR

Cisco ER Couldn't open socket at port <NUMBER>, Exiting.

WARNING

Failed to open connection with Cisco Emergency Responder: <_remoteAddress>/<_remotePort>

CER_CALLENGINE

CER_CALLENGINE Event Log Messages

Type

Message

INFO

Cisco ER Exiting: Graceful shutdown.

ERROR

Problem in initializing SERVER (Server Group). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing Database (E911ServerGroupParameters). Retried... <COUNT> times.

ERROR

Problem in initializing SERVER (Server). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing Database (Server). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing Database (CERServers). Retried... <COUNT> times.

ERROR

Problem in initializing SERVER (License). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (Zone). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (DiscoveryEngine). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (CERIPSubnetManager). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (CERVHMPhoneManager). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (CCM Cluster - No Call Manager seeds configured). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (Seed Switch). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (Discrepant entry). Cannot continue... <EXCEPTION>.

ERROR

Problem in initializing SERVER (Security Contact). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Server Group). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Zone). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Server). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Seed Switch). Cannot continue...<EXCEPTION>.

ERROR

Problem in refreshing LDAP (CCM Cluster). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Discrepant entry). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Security Contact). Cannot continue... <EXCEPTION>.

ERROR

Problem in refreshing LDAP (Security Contact). Cannot continue...<EXCEPTION>.

ERROR

Problem in refreshing zone port tree (Switchport to zone map). Cannot continue... <EXCEPTION>.

ERROR

LicenseManager: End Of 60 Day Evaluation Period. CER Will not work. Please upload a valid License file.

WARNING

Warning!!! You have insufficient number of user licenses.Total phones tracked by the group of CER instances added to the Prime License Manager exceed the user licenses available.

CER_CLUSTER

CER_CLUSTER Event Log Messages

Type

Message

WARNING

IntraCluster Communication failed to ServerGroup with servers Master:<SERVER DETAILS> StandBy: <SERVER DETAILS>.

CER_ONSITEALERT

CER_ONSITEALERT Event Log Messages

Type

Message

WARNING

Backup Cisco ER <hostname> has taken control as Active Cisco ER.

Transition time: <timestamp>.

WARNING

Master Cisco ER <hostname> has taken control as Active Cisco ER.

Transition Time: <timestamp>.

WARNING

Emergency call DetailsCaller Extension:<Extn>Call Time :<TimeStamp>

WARNING

Emergency call DetailsCaller Extension:<Extn>Zone/ERL :<zone>LOCATION :<Location>Call Time :<Timestamp>

Appendix I. Cisco Emergency Responder Port Usage

Cisco Emergency Responder (Emergency Responder) uses the following ports:

Port Usage in Emergency Responder

Protocol

TCP /UDP

Port Range

For this protocol, app or box is: <Client, Server, or Peer>

What is other end?

Relevance to Product

What it does

SNMP

UDP

161

Provides services for SNMP-based management app.

SNMP

UDP

6161

Native SNMP agent listens for requests forwarded by SNMP master agents.

TCP

TCP

7161

Used for communication between SNMP master agent and subagents.

TCP

TCP

1500

IDS DB

TCP

TCP

1501

IDS DB

XML

TCP

1515

IDS DB

Proprietary

TCP

8500

IPsec Cluster Manager

N/A

TCP

22

Secure File Transfer Protocol

TCP

TCP

22

SSH port for remote access

N/A

UDP

123

NTP port used on Unified CM server

HTTPS

TCP

443

HTTPS

N/A

UDP

500

Internet Security Association and Key Management Protocol

N/A

UDP

514

System Logging Service

Proprietary

TCP

2444

Used by CTL Client to communicate with CTL Provider to set the cluster security mode and manage the CTL file

TCP

TCP

3804

Certificate Authority Proxy Function (CAPF) Port for listening to incoming requests from endpoints

XML

TCP

5555

License Manager listens for license requests on this port

TCP

TCP

7070

Certificate Manager Daemon

TCP

TCP

7999

Cellular Digital Packet Data Protocol

HTTPS

TCP

50000-50004

HTTPS to HP SIM

N/A

UDP

67 and 68

DHCP port used on Unified CM server

N/A

UDP

ephemeral

Package Management Tool

N/A

UDP

ephemeral

DNS

N/A

IP

GRE: IP 47, ESP: IP 50, AH: IP 51, IPSec: UDP 500.

IPsec configuration

SMTP

TCP

25

client

SMTP Mail Server(*)

core

Send e-pages, e-mail notifications

CDP

client

core

Discovery of CDP-enabled phones

CLM

UDP

8500

server

clm

core

cluster manager

SYSLOGD

UDP

514

server

syslog server

optional

syslog port

SYSLOG

UDP

8888

client

syslog client

optional

syslog port

HTTPS

TCP

8443

server

Browser

core

secure web access (Tomcat)

HTTP

TCP

8080

server

Browser

core

web access (Tomcat)

NTPD

UDP

123

client

NTP server

optional

network time sync

Peer TCP

TCP

17001*

peer

Emergency Responder Server

core

Emergency Responder Master Backup Failover

Peer RMI

TCP

7777

server

Emergency Responder Server

core

Emergency Responder Server RMI ports

Peer RMI

TCP

7778

server

Emergency Responder Admin

core

Emergency Responder Admin RMI ports

Applet

TCP

55000

server

Applets

core

Web alert

SNMP

UDP

162

server

SNMP Agents

optional

Network Management

DBLRPC

TCP

1515

server

dblrpc

core

Db replication

RACOON

ESP

client

Emergency Responder Server

optional

IPsec traffic

RACOON

UDP

500

client

Emergency Responder Server

optional

IPsec setup port

IDS

TCP

1500

server

IDS

Informix database server

TCP

TCP

1099

AMC

AMC RMI Registry port

TCP

TCP

1090

AMC

AMC RMI Object port

TCP

TCP

4040

CiscoDRFMaster

DRS Master Agent port

Preface

Overview

This document provides you with the required information to install, configure, manage, and use Cisco Emergency Responder (Emergency Responder).

Audience

Network engineers, system administrators, and telecom engineers should review this guide to learn the steps required to properly set up Emergency Responder in the network. Because of the close interaction of Emergency Responder with Cisco Unified Communications Manager, you should be familiar with Cisco Unified Communications Manager before deploying Emergency Responder.

Security personnel should also read this document.

Organization

The following table details how this guide is organized:

Topic

Description

Plan for Cisco Emergency Responder

Provides information to help you understand emergency call ordinances, how Emergency Responder helps you meet the ordinances, and what you must do to deploy Emergency Responder successfully.

Cisco Emergency Responder Installation

Provides detailed information about installing or upgrading to Emergency Responder.

Configure Cisco Unified Communications Manager

Describes the configuration procedures for Unified CM 4.1, 4.2, and 4.3 for Emergency Responder.

Configure Cisco Emergency Responder

Describes the configuration procedure for Emergency Responder.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Describes how to configure Emergency Responder to interoperate with Intrado V-9-1-1 Enterprise.

Configure Cisco Emergency Responder Serviceability

Describes how to configure and use Emergency Responder Serviceability features.

Configure Cisco Unified Operating System

Describes how to configure and use the Cisco Unified Communications Operating System, which is bundled with Emergency Responder.

Configure Cisco Emergency Responder Disaster Recovery System

Describes how to configure the Cisco Emergency Responder Disaster Recovery System.

Cisco Emergency Responder Admin Utility

Describes how to use the Cisco Emergency Responder Admin Utility.

Cisco Emergency Responder User Preparation

Describes the various roles for Emergency Responder users.

Troubleshoot Cisco Emergency Responder

Addresses problems you might encounter with Emergency Responder and provides ways to resolve them; also includes other tasks associated with problem identification and resolution.

ALI Formatting Tool

Describes the ALI Formatting Tool (AFT) and provides information about how to use and troubleshoot the AFT.

Cisco Emergency Responder Administration Web Interface

Describes the fields on the pages of the Emergency Responder administrator web interface.

Cisco Emergency Responder Serviceability Web Interface

Describes the Emergency Responder serviceability web interface.

Cisco Unified Operating System Administration Web Interface

Describes the Cisco Unified Operating System (OS) Administration web interface.

Disaster Recovery System Web Interface

Describes the Cisco Emergency Responder Disaster Recovery System Administration web interface.

Admin Utility Web Interface for Cisco Emergency Responder

Describes the Cisco Emergency Responder Admin Utility web interface.

Using AFT for Specific Service Providers

Provides service-provider specific information for use in conjunction with the AFT.

Event Log Messages

Provides Emergency Responder based Event Log messages and administrative alerts.

Cisco Emergency Responder Port Usage

Provides information about the ports used by Emergency Responder.

Related Documentation

For additional information about Cisco Emergency Responder (Emergency Responder) and Cisco Unified Communications Manager, see the following publications.

- All Cisco Emergency Responder documents are available at:

Click Here

- Cisco Unified Communications Manager installation documents are available at:

Click Here

- Cisco Unified Communications Manager operating system installation documents and backup and restore documents are available at:

Click Here

- Information about Cisco Unified Operations Manager is available at:

Click Here

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: Click Here .

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

Cisco Product Security Overview

This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.

Further information regarding U.S. export regulations may be found at the U.S. Bureau of Industry and Security's Export Administration Regulation Downloadable Files web page.

Acknowledgments

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, 2011 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. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. 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.

3. 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)."

4. 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

5. Products derived from this software may not be called "WebMacro" nor may "WebMacro" appear in their names without prior written permission of Justin Wells.

6. 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)."

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.

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 following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on, users are encouraged to try to correct the interference by using one or more of the following measures:

- Reorient or relocate the receiving antenna.

- Increase the separation between the equipment and receiver.

- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

- Consult the dealer or an experienced radio/TV technician for help.

Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s 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.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned 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. (1110R)

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 talks to the caller and arranges the appropriate emergency response, such as sending police, fire, or ambulance teams.

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 is routed to a PSAP, but not necessarily the local one.

- The caller location information must be displayed at the emergency operator 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 or if the PSAP 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 multiline 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 that 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 7000 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 References

E911 and Cisco Emergency Responder Terminology

Related Information

Understanding Cisco Emergency Responder

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Understanding Cisco Emergency Responder

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

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Related Information

Overview of Enhanced 911 Requirements

Understanding Cisco Emergency Responder

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 talks to the caller and arranges the appropriate emergency response, such as sending police, fire, or ambulance teams.

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 is routed to a PSAP, but not necessarily the local one.

- The caller location information must be displayed at the emergency operator 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 or if the PSAP 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 multiline 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 that 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 7000 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.

Understanding Cisco Emergency Responder

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

Upload License Files

You can upload license files to the Emergency Responder servers using the Emergency Responder Administration web interface. All license files must only be uploaded from the Publisher server when it is up and running.

Note

Emergency Responder license files can only be uploaded from the primary Emergency Responder server.

To upload license files, follow these steps:

Procedure

Step 1

Log in to the Emergency Responder Administration website.

Step 2

Select System > License Manager. The License Manager page appears.

Step 3

Click Upload license. The Upload File page appears.

Step 4

Use the Browse... button to select the license file to upload from your local system.

Step 5

Click Upload. The selected license file is uploaded to the Emergency Responder server.

Related References

License Manager

License Manager

The License Manager page appears when you choose System > License Manager.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the License Manager page to view the details of the licenses for the server group and to upload a license file for the server group.

Table 1 describes the License Manager page.

License Manager Page

Field

Description

Status

Displays status messages

Upload license button

Allows you to upload a license file to the server selected in the drop-down menu.

Note:
You must purchase separate license files for the publisher and subscriber servers, but you can upload both the publisher and subscriber license files with the Cisco Emergency Administration web page on the publisher server only.

Details of Emergency Responder Licenses

Installation Date (MM/YY/DD)

Displays the date on which the server license was installed.

Note:
This appears only for the evaluation license.

Emergency Responder Server License

Emergency Responder server license type

Displays the type of server license installed. There are two possible values for this field:

- Evaluation—No server license is installed and Emergency Responder is operating in 60-day mode

- Permanent—The server license is installed

Server license count

Displays the number of licensed servers in the server group

Emergency Responder User License

Displays the following information about the installed Emergency Responder user licenses:

- Cumulative user license count

- Publisher user license count

- Subscriber user license count

- Number of phones discovered

- Number of phones manually configured

- Total number of users being tracked currently

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Responder Deployment

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Emergency Responder Deployment

The information in the following sections describe deployment models for various types of networks. You can use these examples as modules, combining them to form a larger, more complex network.

CTI Application Call Forwarding

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 is the location of the application server, not the location of the original caller. This situation occurs even if the application retains the original calling line number. For this reason, you should dial 911 directly.

Related Tasks

Set Up Calling Search Space for Gateway and PSAP Connection

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Data Integrity and Reliability

ERLs

ELIN Numbers Emergency Calls and PSAP Callbacks

Network Preparations

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Data Integrity and Reliability

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 provider's network. In the service provider's network, the routing is based on the ELIN, which is also used to look up the ALI for the caller. Your ERL configuration must be reliable so that the correct ELIN is assigned to the emergency call.

The following information will help you 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. 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 is used for the port, and the wrong ALI is sent to the PSAP.

This type of change does not normally result in an incorrectly routed call, because it is unlikely that a single LAN switch connects 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.

- With phones that Emergency Responder cannot automatically track, you ensure that any moves, adds, or changes to these phones also result in an update to the Emergency Responder configuration. See Manually Define Phones for information about defining these types of phones.

Note

If the switch port mapping changes, an email alert is sent.

- Before Emergency Responder 1.2, if registered phones were not located behind a switch port, Emergency Responder would list the phone in the Unlocated Phones page.

Emergency Responder 1.2 and later locates these phones as follows:

- If a registered phone is not located behind a switch port, it may be located 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, Emergency Responder lists the phone in the Unlocated Phones page.

To determine the ERL that Emergency Responder will use for call routing, use the ERL Debug Tool to search for the phone. The search yields the current ERL used in routing the emergency call from this phone and why Emergency Responder chose that ERL. For more information, see Emergency Responder Admin Utility.

- When you install Emergency Responder, 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  Emergency Responder 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. 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 Emergency Responder 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 Emergency Responder and clicking Locate Switch Ports. See LAN Switch Identification for more information.

Phones connected to undefined switches are listed as unlocated phones in Emergency Responder. If you changed a defined switch, new or changed ports become ports without an ERL association. You should assign ERLs for the new or changed switch ports. See Emergency Responder Network Administrator Role and Emergency Responder ERL Administrator Role for information about 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 Export ERL Information and Export ALI Information for Submission to Your Service Provider for more information.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

Set Up Calling Search Space for Gateway and PSAP Connection

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 about setting up the gateway, and the Unified CM 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.

Procedure

Step 1

Select Device > Gateway.
Unified CM opens the Find and List Gateways page.

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.
Unified CM lists the gateways that match your criteria.

Step 3

Click the gateway you want to configure.
Unified CM opens the Gateway Configuration page.

Step 4

Select E911CSS for Calling Search Space.

Step 5

Click Update.
Unified CM saves your changes.

Network Preparations

The information in the following topics describe the steps you should take to prepare your network before deploying Cisco Emergency Responder.

Phone Clusters

The following scenario illustrates how Emergency Responder treats phones moving between clusters:

- Server Group A (SGA) has a phone (Phone_1) that is moving out of SGA.

- Emergency Responder discovers Phone_1 in Server Group B (SGB).

- The Unlocated Phones page in SGA displays the phone in SGB.

- If both the Emergency Responder servers (Publisher and Subscriber) in SGB go down, SGA still displays Phone_1 in SGB.

- Calls made from Phone_1 during this time are redirected to SGB and Emergency Responder takes the same steps to route this emergency call when Emergency Responder servers are not there in SGB.

- Phone_1 is also treated like any other phone in SGB when both the SGB Emergency Responder servers are down.

- If Phone_1 moves to Server Group C (SGC):

- It is discovered after the next incremental phone tracking on SGA and then in SGC.

- The Unlocated Phones page changes the association of Phone_1 to SGC.

- If Phone_1 moves back to SGA, it is discovered in the next incremental phone tracking and displayed under the corresponding switch port.

Be aware of the following when planning your Emergency Responder system:

- A single Emergency Responder group cannot support clusters with a mix of Cisco Unified Communications Manager versions. For example, Emergency Responder can support all Cisco Unified Call Manager 4.2 clusters or all Cisco Unified Call Manager 5.1 clusters.

However, a Emergency Responder cluster can contain Emergency Responder groups that support different versions of Cisco Unified Communications Manager. In this way, Emergency Responder can support a mix of Cisco Unified Communications Manager versions in your telephony network.

- A Emergency Responder server group can form an Emergency Responder cluster with other Emergency Responder server groups of version 1.3 or higher.

Note

If you make an emergency call from a Cisco Unified IP Phone using a shared line, the call may terminate on an incorrect ERL across the cluster.

Note

Moving of phones discovered and associated with an ERL to a different Unified CM cluster, tracked by a different Emergency Responder Server Group belonging to the same Emergency Responder cluster, requires the deletion of the ERLs association from the current Emergency Responder Server Group. See Step 7 of Identify Unlocated Phones to unassign an ERL from the current Emergency Responder Server Group.

Related Information

Emergency Responder and Your Network

Emergency Call Process

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
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 Tasks

Export ALI Information for Submission to Your Service Provider

Related References

ALI Formatting Tool

Related Information

Emergency Responder Deployment

ALI Submission and Service Provider Requirements

ALI Formatting Tool

Emergency Responder Deployment

The information in the following sections describe deployment models for various types of networks. You can use these examples as modules, combining them to form a larger, more complex network.

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

ALI Formatting Tool

ALI Formatting Tool

The ALI Formatting Tool page appears when you choose Tools > ALI Formatting Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder 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

The following table describes the ALI Formatting Tool page.

ALI Formatting Tool Page

Field

Description

Select a Service Provider

Use the pull-down menu to select a service provider

Select an Input File for the ALI Formatting Tool from the List Below

Use the pull-down menu to select an input file

Submit button

Click the Submit button to display the Search for ELINs page, which is described in Table 2.

The following table describes the Search for ELINs page.

Search for ELINs Page

Field

Description

Use Search to Filter-out ELINs on Area, City and Local Code(last 4-digits).

Allows you to search ELINs by Local Code, Area Code, or City Code.

Add (+) button

Adds more search parameters

Remove (-) button

Removes search parameters

The following table describes the Bulk Update page.

Bulk Update Page

Field

Description

Remove Changes/Generate File button

Shows all the ELINs that have been changed.

Search for ELIN

Displays the ELIN search page.

The following table describes the Review Changes/Generate File page.

Review Changes/Generate File Page

Field

Description

Add More ELIN

Displays the remaining ELINs that have not been changed.

Remove ELIN

Removes the selected ELINs from the list

Search for ELIN

Displays the ELIN search screen

Generate File button

Generates the formatted file.

The following table describes the Download Formatted File page.

Download Formatted File Page

Field

Description

Download Formatted File button

Displays a Download File dialog box so that the formatted file can be downloaded to the local system.

Data Integrity and Reliability

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 provider's network. In the service provider's network, the routing is based on the ELIN, which is also used to look up the ALI for the caller. Your ERL configuration must be reliable so that the correct ELIN is assigned to the emergency call.

The following information will help you 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. 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 is used for the port, and the wrong ALI is sent to the PSAP.

This type of change does not normally result in an incorrectly routed call, because it is unlikely that a single LAN switch connects 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.

- With phones that Emergency Responder cannot automatically track, you ensure that any moves, adds, or changes to these phones also result in an update to the Emergency Responder configuration. See Manually Define Phones for information about defining these types of phones.

Note

If the switch port mapping changes, an email alert is sent.

- Before Emergency Responder 1.2, if registered phones were not located behind a switch port, Emergency Responder would list the phone in the Unlocated Phones page.

Emergency Responder 1.2 and later locates these phones as follows:

- If a registered phone is not located behind a switch port, it may be located 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, Emergency Responder lists the phone in the Unlocated Phones page.

To determine the ERL that Emergency Responder will use for call routing, use the ERL Debug Tool to search for the phone. The search yields the current ERL used in routing the emergency call from this phone and why Emergency Responder chose that ERL. For more information, see Emergency Responder Admin Utility.

- When you install Emergency Responder, 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  Emergency Responder 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. 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 Emergency Responder 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 Emergency Responder and clicking Locate Switch Ports. See LAN Switch Identification for more information.

Phones connected to undefined switches are listed as unlocated phones in Emergency Responder. If you changed a defined switch, new or changed ports become ports without an ERL association. You should assign ERLs for the new or changed switch ports. See Emergency Responder Network Administrator Role and Emergency Responder ERL Administrator Role for information about 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 Export ERL Information and Export ALI Information for Submission to Your Service Provider for more information.

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Cisco Emergency Responder User Preparation

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Cisco Emergency Responder User Preparation

CAMA and PRI Trunks

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. You should consult with your service provider and decide on the type of connection that works best for you.

Consider these issues:

- PRI—If 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 that 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 that 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-party number rather than a generic number (such as the main number of the site). Otherwise, the PSAP does not receive the expected ELIN, and the emergency call might not be routed to the right PSAP.

- CAMA—CAMA trunks are dedicated to emergency calls, and are available in most areas. You do not need to do 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, with 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 Tasks

Set Up Calling Search Space for Gateway and PSAP Connection

Set Up Calling Search Space for Gateway and PSAP Connection

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 about setting up the gateway, and the Unified CM 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.

Procedure

Step 1

Select Device > Gateway.
Unified CM opens the Find and List Gateways page.

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.
Unified CM lists the gateways that match your criteria.

Step 3

Click the gateway you want to configure.
Unified CM opens the Gateway Configuration page.

Step 4

Select E911CSS for Calling Search Space.

Step 5

Click Update.
Unified CM saves your changes.

DID Service Provider Numbers

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 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. For example, if four people make emergency calls within an hour, and if the PSAP calls the ELIN, the PSAP connects to the last caller. This situation 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, Emergency Responder uses those ELINs in sequence until all are used, then reuses the ELINs in order. Emergency Responder maintains the link between the ELIN and the extension of the actual emergency caller for up to three hours.

Because you must 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 Emergency Responder can handle. Because Emergency Responder reuses the ELINs that 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.

Related Information

ELIN Numbers Emergency Calls and PSAP Callbacks

ERL Creation

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Related Tasks

Export ERL Information

Related Information

ERLs

ERL Management

ERL Creation

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Switch and Phone Upgrades

The most powerful capability of Emergency Responder 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. By automatically tracking phones, you can reduce the cost of maintaining your telephone network, and simplify moves, adds, or changes.

However, Emergency Responder only can 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 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.

Related Information

Emergency Responder Switch Configuration

Phone Management

Emergency Responder Switch Configuration

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. The following topics describe the switch requirements and how to identify switches to Emergency Responder.

Phone Management

The following 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 Emergency Responder.

Preparing Your Staff for Emergency Responder

Emergency Responder does not replace your existing emergency procedures. Instead, Emergency Responder is a tool you can use to augment those procedures. Before deploying Emergency Responder, consider how it fits into your procedures and how you want to use the Emergency Responder system's capabilities.

These are the main things to consider when deciding how to use Emergency Responder:

- When someone makes an emergency call, Emergency Responder 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 helps them respond quickly to emergencies. Incorporating building names, floor numbers, and other readily understood location information in the name are the types of factors to consider.

- Emergency Responder lets you define three types of administrative user, so you can divide responsibilities for overall Emergency Responder 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 Emergency Responder 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 Data Integrity and Reliability for more information about maintaining data integrity.

Related References

Emergency Responder ERL Administrator Role

Emergency Responder Network Administrator Role

Emergency Responder System Administrator Role

Related Information

Emergency Responder Onsite Alert Personnel Preparations

Emergency Responder Onsite Alert Personnel Preparations

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder:

- How to use the Emergency Responder web interface. See the Emergency Responder user web interface online help for information about these topics. The online help includes a user's guide in PDF format that you can print out and distribute to your users. The information in the user's 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.

- Explain how they receive notification of an emergency call.

- A web alert appears for everyone logged into the Emergency Responder 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 Emergency Responder 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 have for identifying the location of the emergency caller.

- Explain the organization's policy for responding to emergency calls. Work with the emergency response teams to develop an acceptable policy if you do not already have one.

Emergency Responder ERL Administrator Role

The following table lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder ERL Administration Recurring Tasks

Recurring Task

Description

More Information

Assign ERLs to new or changed switch ports

If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.

Switch Port Configuration

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 Emergency Responder.

- ERL Creation

- Switch Port Configuration

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.

- Export ERL Information

- Export ALI Information for Submission to Your Service Provider

- ERL Creation

- ALI Submission and Service Provider Requirements

Audit the manually defined phones

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.

- Manually Define Phones

Audit the unlocated phones list

Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco Emergency Responder cannot locate the phones and to resolve the problems.

- Identify Unlocated Phones

- Unlocated Phones

Add new onsite personnel or remove old ones; update phone numbers

As onsite alert personnel are added, define them in Cisco Emergency Responder and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco Emergency Responder. Update phone numbers, email address, and other contact information as they change.

- Add Onsite Security Personnel

- ERL Creation

Add IP subnet for the IP subnets to be tracked

If there is a new IP subnet that needs to be discovered by Emergency Responder, then perform the following tasks:

- Configure an ERL spanning the new IP subnet's geographical location.

- Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL.

- Set Up IP Subnet-based ERLs

Emergency Responder Network Administrator Role

The following table lists the recurring tasks for which a network administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder Network Administration Recurring Tasks

Recurring Task

Description

More Information

Add new switches

Add any switches that you add to the network to the Cisco Emergency Responder configuration. A switch is considered new if it has an IP address not defined in Cisco Emergency Responder.

- LAN Switch Identification

- Manually Run the Switch-Port and Phone Update Process

Remove old switches

Remove switches from the Cisco Emergency Responder configuration if you remove them from the network. Nonexistent switches in the Cisco Emergency Responder configuration do not create problems, but they do increase the time required to do phone tracking, because Cisco Emergency Responder attempts to connect to the switch must time out before moving on to the next switch.

- LAN Switch Identification

Update the SNMP read community if it changes

If you change the read community string on any defined switch, you must update the SNMP settings in Cisco Emergency Responder. Until the setting is updated, Cisco Emergency Responder cannot track phones attached to the switch.

- Set Up SNMPv2

Update or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder system administrator.

- Identify Cisco Unified Communications Manager Clusters

Check ERL assignments

Use the ERL Debug Tool to check that the correct and expected ERL is used for a selected phone.

- Emergency Responder Admin Utility

Emergency Responder System Administrator Role

The following table 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 Emergency Responder ERL Administrator Role and the Emergency Responder Network Administrator Role.

Cisco Emergency Responder System Administration Recurring Tasks

Recurring Task

Description

More Information

Add additional Cisco Emergency Responder groups

As telephones are added to the network, you might need additional Cisco Emergency Responder groups. Install and define them and their telephony settings.

Work with the telephony administrator to complete the required Unified CM configuration.

- Installation on a New System

- Set Up Server Group

- Set Up Group Telephony Settings for Server

- Configure Servers

- Identify Cisco Unified Communications Manager Clusters

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.

Create new Cisco Emergency Responder users; remove old users

As onsite alert personnel change, or as Cisco Emergency Responder system, network, and ERL administrators change, add or remove them as required.

- Emergency Responder User Management

Add or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder network administrator.

- Identify Cisco Unified Communications Manager Clusters

Monitor the email alerts that Cisco Emergency Responder generates

If your email ID is configured in the server group settings, Cisco Emergency Responder sends email alerts about critical errors to you. You are expected to understand the error and take action to correct the problem.

See Troubleshoot Email Alerts for information to help you understand the email alerts and resolve problems.

- Set Up Server Group

Deployment in Main Site and PSAP

To support a simple telephony network consisting of a single Cisco Unified Communications Manager cluster, install two Emergency Responder 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 provider's network, although capacity planning for your telephony network might require more than one gateway. Configure all route patterns to use this gateway.

The following figure shows how Emergency Responder fits into a simple telephony network with a single Cisco Unified Communications Manager cluster.

Deploying Cisco Emergency Responder in One Main Site with One PSAP

See these examples to extend this example to more complex networks:

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

Deployment in Main Site with Two or More PSAPs

The following figure illustrates the Emergency Responder configuration with 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 Two Main Site Deployments.

Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs

To support this type of network, install two Emergency Responder servers and configure one server as the Publisher and the other server as a Subscriber pointing to the Publisher.

Because there are two PSAPs serving the location, you probably need more than one gateway connecting to different parts of the service provider's network. However, this depends on the layout of the service provider's 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 that you need two gateways; 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 provider's 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, Emergency Responder 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:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

Deployment in Main Site with Satellite Offices

The following figure illustrates the Emergency Responder configuration with 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 Two Main Site Deployments.

Deploying Cisco Emergency Responder in One Main Site with Satellite Offices

Caution

In this configuration, if the WAN link between the offices goes down, the people in the satellite office cannot make emergency calls with Emergency Responder support. SRST in the satellite office can provide basic support for emergency calls in case of WAN failure.

To support this type of network, install two Emergency Responder 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. You probably need more than one gateway connecting to different parts of the service provider's network (you might have different service providers). However, this depends on the layout of the service provider's 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 that you need two gateways; 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 provider's network, configure all route patterns used in Columbus's ERLs to use gateway COL, and all route patterns used in Chillicothe's ERLs to use gateway CHIL. As phones move between sites, Emergency Responder 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. Emergency Responder must do SNMP queries of the remote site 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 Set Up SNMPv2 for more information.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site Serving Multiple Sites

- Two Main Site Deployments

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 Emergency Responder in the main office.

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

One Site Serving Multiple Sites with EMCC

Using Extension Mobility Cross Cluster (EMCC) between two Unified CM clusters enables Emergency Responder to provide enhanced support for 911 calls.

Figure 1 illustrates how the Emergency Responder is deployed at one site and serves two or more sites with the Unified CM in each site.

In this scenario, the Emergency Responder server is shared by the EMCC user's home cluster and the visiting Unified CM cluster. For Emergency Responder to process a 911 call made by an EMCC logged-in user, the home Unified CM cluster must not use an Adjunct Calling Search Space (CSS) to direct the 911 call to the user's visiting cluster.

The shared Emergency Responder servers supporting both the clusters process the 911 call in the user's home cluster.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Two Main Site Deployments

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

Cluster Deployment in Two Main Sites with EMCC

Emergency Responder can provide enhanced support for 911 calls when using Extension Mobility Cross Cluster (EMCC) between two Unified CM clusters.

Figure 1 illustrates the Emergency Responder configuration with two (or more) main sites, each served by a separate PSAP.

In this scenario, the two clusters must be configured for EMCC. When a 911 call is made by an EMCC logged-in user, the call is offered to Emergency Responder group in the users home cluster.

Emergency Responder groups in the user's home cluster and visiting cluster form an Emergency Responder cluster. Emergency Responder group in home cluster redirects the call to visiting Emergency Responder group by using Inter-Cluster Trunk (ICT) between the two Unified CM clusters and the visiting Emergency Responder routes the call to appropriate PSAP.

Note

In this scenario, the Unified CM does not have adjunct CSS configured.

See these examples to extend this example to other networks:

- Deployment in Main Site and PSAP

- Deployment in Main Site with Two or More PSAPs

- Deployment in Main Site with Satellite Offices

- Deployment in Main Site Serving Multiple Sites

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

Configure a Local Route Group in a Wide Area Network

With an Emergency Responder and Cisco Unified Communications Manager deployment that spans multiple locations over a wide area network (WAN), you may want to configure a Local Route Group (LRG) to ensure that users can make emergency calls if the connection between Emergency Responder and Cisco Unified Communications manager goes down.

While there is a communication failure between Emergency Responder and Cisco Unified Communications Manager, the following Emergency Responder features are not supported:

- Onsite alerts

- Web alerts

- Email alerts

- PSAP callback

- Device mobility

To support device mobility, you must configure device mobility in Cisco Unified Communications Manager to route the 911 call to the new LRG location when the phones are moved from one location to another.

To configure LRG, follow these steps:

Procedure

Step 1

On Cisco Unified Communications Manager Administration, configure the LRG route pattern and route point for 911 emergency call routing.

Step 2

On Cisco Unified Communications Manager Administration, configure any destination route point that is being forwarded in the emergency call route point with the LRG route pattern.

Step 3

On Emergency Responder Administration, configure the LRG route pattern as the default ERL.

Related Tasks

Determine Required Cisco Emergency Responder Groups

Related Information

Emergency Call Process

Emergency Responder and Your Network

Installation on a New System

Configure Cisco Unified Communications Manager

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Determine Required Cisco Emergency Responder Groups

To ensure efficient Emergency Responder performance, determine the limits that each Emergency Responder group can support when planning your Emergency Responder deployment. A single Cisco Unified Communications Manager cluster can only be supported by one Emergency Responder group, although a single Emergency Responder group can support more than one Cisco Unified Communications Manager cluster.

See the latest version of the Release Notes for Cisco Emergency Responder for the capacities of a single Emergency Responder 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 Emergency Responder 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 provider's ALI database providers. If your network extends into more than one ALI database provider's territory, you should use the ALI Formatting Tool (AFT) to export ALI records in multiple ALI database formats.

To have a single Emergency Responder group support multiple LECs, follow these steps:

Procedure

Step 1

Obtain an ALI record file output from Emergency Responder in standard NENA format. This file contains the records destined for multiple LECs.

Step 2

Make a copy of the original file for each required ALI format (one copy per LEC).

Step 3

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 about using the AFT, see ALI Formatting Tool) The information to delete can usually be identified by NPA (or area code).

Step 4

Save the resulting file in the required ALI format for LEC-A, and name the file accordingly.

Step 5

Repeat steps 3 and 4 for each LEC.
If AFTs are not available for each LEC, you can achieve a similar result by editing the NENA-formatted files with a text editor.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Configure Cisco Unified Communications Manager

Create Phone Partition

If you have not already created a partition for the phones, do so now.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description.

Step 4

Click Insert to add the new partition.

Related Tasks

Create Phone Calling Search Space

Assign Partition and Calling Search Space to Phones

Related Information

Configure Cisco Unified Communications Manager

Configure Cisco Unified Communications Manager

Create Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one.

Procedure

Step 1

Select Route Plan > Calling Search Space in Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.

Step 4

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.

Step 5

Click Insert to add the new calling search space.

Assign Partition and Calling Search Space to Phones

You can use the Bulk Administration Tool 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.

After you have created the Phones partition (Create Phone Partition) and PhonesCSS calling search space (Create Phone Calling Search Space), configure the phones to use them.

Procedure

Step 1

Select Device > Phone.
Unified CM displays the Find and List Phones page.

Step 2

Select Device name is not empty in the search fields and click Find.
Unified CM lists all of the phones in the bottom frame.

Step 3

Click the phone with the configuration that you want to change.
Unified CM displays the Phone Configuration page.

Step 4

Change the calling search space to PhoneCSS and click Update.

Step 5

Click the line number that you want to configure in the left-hand column.
Unified CM displays the Directory Number Configuration page.

Step 6

Change the partition to Phones, and the calling search space to PhoneCSS.

Step 7

Click Insert to save your changes.

Create Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one.

Procedure

Step 1

Select Route Plan > Calling Search Space in Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.

Step 4

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.

Step 5

Click Insert to add the new calling search space.

Related Tasks

Create Phone Partition

Assign Partition and Calling Search Space to Phones

Related Information

Configure Cisco Unified Communications Manager

Create Phone Partition

If you have not already created a partition for the phones, do so now.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description.

Step 4

Click Insert to add the new partition.

Configure Cisco Unified Communications Manager

Assign Partition and Calling Search Space to Phones

You can use the Bulk Administration Tool 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.

After you have created the Phones partition (Create Phone Partition) and PhonesCSS calling search space (Create Phone Calling Search Space), configure the phones to use them.

Procedure

Step 1

Select Device > Phone.
Unified CM displays the Find and List Phones page.

Step 2

Select Device name is not empty in the search fields and click Find.
Unified CM lists all of the phones in the bottom frame.

Step 3

Click the phone with the configuration that you want to change.
Unified CM displays the Phone Configuration page.

Step 4

Change the calling search space to PhoneCSS and click Update.

Step 5

Click the line number that you want to configure in the left-hand column.
Unified CM displays the Directory Number Configuration page.

Step 6

Change the partition to Phones, and the calling search space to PhoneCSS.

Step 7

Click Insert to save your changes.

Assign Partition and Calling Search Space to Phones

You can use the Bulk Administration Tool 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.

After you have created the Phones partition (Create Phone Partition) and PhonesCSS calling search space (Create Phone Calling Search Space), configure the phones to use them.

Procedure

Step 1

Select Device > Phone.
Unified CM displays the Find and List Phones page.

Step 2

Select Device name is not empty in the search fields and click Find.
Unified CM lists all of the phones in the bottom frame.

Step 3

Click the phone with the configuration that you want to change.
Unified CM displays the Phone Configuration page.

Step 4

Change the calling search space to PhoneCSS and click Update.

Step 5

Click the line number that you want to configure in the left-hand column.
Unified CM displays the Directory Number Configuration page.

Step 6

Change the partition to Phones, and the calling search space to PhoneCSS.

Step 7

Click Insert to save your changes.

Related Tasks

Create Phone Partition

Create Phone Calling Search Space

Related Information

Configure Cisco Unified Communications Manager

Create Phone Partition

If you have not already created a partition for the phones, do so now.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description.

Step 4

Click Insert to add the new partition.

Configure Cisco Unified Communications Manager

Create Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one.

Procedure

Step 1

Select Route Plan > Calling Search Space in Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.

Step 4

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.

Step 5

Click Insert to add the new calling search space.

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Related Tasks

Create Emergency Responder Calling Search Space

Create Emergency Call Route Points

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

Related Information

Configure Cisco Unified Communications Manager

Set Up Phone Route Plans

ELIN Numbers Emergency Calls and PSAP Callbacks

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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.

Configure Cisco Unified Communications Manager

Set Up Phone Route Plans

Before configuring Emergency Responder, you must ensure that the phones that might be used to make emergency calls (typically all phones) are added and registered with Unified CM. See the documentation and online help included with Unified CM if you need assistance.

The following sections provide an example setup for your network before adding Emergency Responder.

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Emergency Responder group in an Emergency Responder cluster, you must configure route patterns to enable each Emergency Responder group to route emergency calls to another Emergency Responder group if a caller's phone homes to a Unified CM cluster outside the current location of the phone. See Cisco Emergency Responder Clusters for a detailed explanation of how Emergency Responder groups communicate within a Emergency Responder cluster.

This procedure explains how to create the route pattern for one Emergency Responder group. The Inter-Cisco ER Group Route Pattern defined on a Emergency Responder Group is a route pattern for incoming Emergency Calls. Consider the network setup in the following figure.

For inter-group communications to work:

- You must define inter-cluster trunks in each Unified CM cluster to enable communications between the Unified CM clusters. See the Unified CM documentation for information about creating these types of gateways.

- Define the route pattern on the Unified CM

- Define route pattern 2000.911 and 3000.911 in CUCM cluster A.

- Define Route Pattern 1000.911 and 3000.911 in CUCM cluster B.

- Define Route Pattern 1000.911 and 2000.911 in CUCM cluster C.

- Define Inter-Emergency Responder Group Route Pattern

- In Emergency Responder Group A, define 1000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group B, define 2000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group C, define 3000.911 as the Inter Emergency Responder Group Route Pattern.

These definitions allow a call in an ERL managed by Emergency Responder Group B to be routed to Emergency Responder Group B even though the phone homes to Unified CM cluster A, which is serviced by Emergency Responder Group A.

Understanding Inter-Cisco Emergency Responder Group Route Patterns

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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 Tasks

Create Emergency Responder Partition

Create Emergency Call Route Points

Create Alternate Emergency Call Numbers

Set Up Calling Search Space for Gateway and PSAP Connection

Related Information

Configure Cisco Unified Communications Manager

Set Up Phone Route Plans

ELIN Numbers Emergency Calls and PSAP Callbacks

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Configure Cisco Unified Communications Manager

Set Up Phone Route Plans

Before configuring Emergency Responder, you must ensure that the phones that might be used to make emergency calls (typically all phones) are added and registered with Unified CM. See the documentation and online help included with Unified CM if you need assistance.

The following sections provide an example setup for your network before adding Emergency Responder.

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

Create 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.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The number you want to support as an emergency number. In this example, 9.911.

- Partition - Select Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Select this.

- Called Party Transformations, Discard Digits (Outgoing Calls) - Select PreDot.

Step 4

Click Insert.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Set Up Calling Search Space for Gateway and PSAP Connection

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 about setting up the gateway, and the Unified CM 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.

Procedure

Step 1

Select Device > Gateway.
Unified CM opens the Find and List Gateways page.

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.
Unified CM lists the gateways that match your criteria.

Step 3

Click the gateway you want to configure.
Unified CM opens the Gateway Configuration page.

Step 4

Select E911CSS for Calling Search Space.

Step 5

Click Update.
Unified CM saves your changes.

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

Related Tasks

Create Emergency Responder Partition

Create Emergency Responder Calling Search Space

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

Create Alternate Emergency Call Numbers

Create Emergency Responder Cisco Unified Communications Manager User

Set Up Group Telephony Settings for Server

Related Information

ELIN Numbers Emergency Calls and PSAP Callbacks

Installation on a New System

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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.

ELIN Numbers Emergency Calls and 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.

Emergency Responder converts a caller extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Emergency Responder 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. When there is no active association of an ELIN to an internal phone extension, Emergency Responder routes calls to that ELIN to on-site security.

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.

Emergency Responder reuses 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 period, the first emergency caller's ELIN mapping is replaced by the third caller's extension. If the PSAP tries to call the first caller, the PSAP reaches the third caller. This information will help as you determine the number of DIDs you need for each ERL.

See ERL Creation for information about how to configure the ERLs with these numbers.

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Emergency Responder group in an Emergency Responder cluster, you must configure route patterns to enable each Emergency Responder group to route emergency calls to another Emergency Responder group if a caller's phone homes to a Unified CM cluster outside the current location of the phone. See Cisco Emergency Responder Clusters for a detailed explanation of how Emergency Responder groups communicate within a Emergency Responder cluster.

This procedure explains how to create the route pattern for one Emergency Responder group. The Inter-Cisco ER Group Route Pattern defined on a Emergency Responder Group is a route pattern for incoming Emergency Calls. Consider the network setup in the following figure.

For inter-group communications to work:

- You must define inter-cluster trunks in each Unified CM cluster to enable communications between the Unified CM clusters. See the Unified CM documentation for information about creating these types of gateways.

- Define the route pattern on the Unified CM

- Define route pattern 2000.911 and 3000.911 in CUCM cluster A.

- Define Route Pattern 1000.911 and 3000.911 in CUCM cluster B.

- Define Route Pattern 1000.911 and 2000.911 in CUCM cluster C.

- Define Inter-Emergency Responder Group Route Pattern

- In Emergency Responder Group A, define 1000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group B, define 2000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group C, define 3000.911 as the Inter Emergency Responder Group Route Pattern.

These definitions allow a call in an ERL managed by Emergency Responder Group B to be routed to Emergency Responder Group B even though the phone homes to Unified CM cluster A, which is serviced by Emergency Responder Group A.

Understanding Inter-Cisco Emergency Responder Group Route Patterns

Create 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.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The number you want to support as an emergency number. In this example, 9.911.

- Partition - Select Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Select this.

- Called Party Transformations, Discard Digits (Outgoing Calls) - Select PreDot.

Step 4

Click Insert.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Create Emergency Responder Cisco Unified Communications Manager User

You must add Emergency Responder as a Unified CM user. The settings you enter here are used when you configure the Unified CM settings for Emergency Responder.

Procedure

Step 1

In Unified CM, select User Management > Application User. Click the Add New button.
Unified CM displays the Application User Configuration page.

Step 2

Complete the following required fields:

- UserID—Use a descriptive name such as "Emergency_Responder_User."

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

In the Device Information section, select the desired route points and CTI ports and then click the down arrow to add the selected devices to the user control list. The list of devices appears in the Controlled Devices area.

Step 4

Select the following devices:
Note:
You may need to use Find Phones or Find Route Points to select the desired devices.

- All CTI ports created for Cisco Emergency Responder use. For more information, see "Creating the Required CTI Ports" section.

- The primary emergency call number, for example, 911.

- The backup emergency call number, for example, 912.

- The route point used for ELINs, for example, 913XXXXXXXXXX.

Step 5

Click Save.

Step 6

In the Unified CM menu at the top, click User Management > User Group.
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.

Step 8

Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page.

Step 9

Click Add Application Users to Group.
The Find and List Application Users popup window appears.

Step 10

Enter the User ID and click Find.
The list of Applications users appears.

Step 11

Check the check box next to the user ID and click Add Selected.
Unified CM adds the selected user to the Standard CTI Allow Calling Number Modification user group.

Step 12

Choose 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.

Step 14

Click the Standard CTI Enabled group.
Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Create Required CTI Ports

Emergency Responder 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 that you configure is the number of simultaneous calls Emergency Responder can make to these personnel. It does not relate to the number of emergency calls Emergency Responder can handle or forward to the PSAP. There is no configurable limitation to the number of simultaneous emergency calls that Emergency Responder can handle.

Before You Begin
Emergency Responder 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.

Procedure

Step 1

Select Device > Phone.
Unified CM opens the Find and List Phones page.

Step 2

Click Add a New Phone.
Unified CM opens the Add a New Phone page.

Step 3

Select CTI Port for Phone Type and click Next.
Unified CM opens the Phone Configuration page.

Step 4

Configure the CTI Port, entering this information:

- Device Name- Enter something meaningful to you, for example, CTI3001.

- Device Pool- Select an appropriate device pool. This device pool must use the G.711 region.

- Calling Search Space- Select PhoneCSS.

Step 5

Click Insert.
Unified CM creates the CTI port and asks if you want to configure line 1. Click OK. Unified CM opens the Directory Number Configuration page.

Step 6

Configure line 1 for the CTI port, entering this information:

- Partition- Select Phones.

- Calling Search Space- Select 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.
Unified CM 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 Tasks

Create Emergency Responder Partition

Create Emergency Responder Calling Search Space

Create Emergency Responder Cisco Unified Communications Manager User

Identify Cisco Unified Communications Manager Clusters

Related Information

ERL Creation

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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.

Create Emergency Responder Cisco Unified Communications Manager User

You must add Emergency Responder as a Unified CM user. The settings you enter here are used when you configure the Unified CM settings for Emergency Responder.

Procedure

Step 1

In Unified CM, select User Management > Application User. Click the Add New button.
Unified CM displays the Application User Configuration page.

Step 2

Complete the following required fields:

- UserID—Use a descriptive name such as "Emergency_Responder_User."

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

In the Device Information section, select the desired route points and CTI ports and then click the down arrow to add the selected devices to the user control list. The list of devices appears in the Controlled Devices area.

Step 4

Select the following devices:
Note:
You may need to use Find Phones or Find Route Points to select the desired devices.

- All CTI ports created for Cisco Emergency Responder use. For more information, see "Creating the Required CTI Ports" section.

- The primary emergency call number, for example, 911.

- The backup emergency call number, for example, 912.

- The route point used for ELINs, for example, 913XXXXXXXXXX.

Step 5

Click Save.

Step 6

In the Unified CM menu at the top, click User Management > User Group.
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.

Step 8

Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page.

Step 9

Click Add Application Users to Group.
The Find and List Application Users popup window appears.

Step 10

Enter the User ID and click Find.
The list of Applications users appears.

Step 11

Check the check box next to the user ID and click Add Selected.
Unified CM adds the selected user to the Standard CTI Allow Calling Number Modification user group.

Step 12

Choose 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.

Step 14

Click the Standard CTI Enabled group.
Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Related Tasks

Create Translation Patterns for ELINs

Create Emergency Responder Partition

Related Information

Configure Cisco Unified Communications Manager

ERLs

ERL Creation

Create 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. Emergency Responder 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 Create Emergency Call Route Points.

Before You Begin
Ensure that you have a list of all the DIDs you are using for ELINs.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The 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.

- Partition - Select E911.

- Numbering Plan- Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select 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.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Configure Cisco Unified Communications Manager

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Create 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. Emergency Responder 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 Create Emergency Call Route Points.

Before You Begin
Ensure that you have a list of all the DIDs you are using for ELINs.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The 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.

- Partition - Select E911.

- Numbering Plan- Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select 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.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Related Tasks

Create Route Patterns for ERLs

Related Information

Configure Cisco Unified Communications Manager

ERLs

ERL Creation

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Configure Cisco Unified Communications Manager

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Create 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 eliminates the secondary dialtone timing.

Create translation patterns so that when users dial the local system external access code of 9 plus 911, the calls are directed to the single 911 pattern previously created in the Create Emergency Call Route Points.

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.

The following table provides translation patterns for external access code of 9.

Translation Patterns for External Access Code of 9

Translation Pattern

911

9.911

Partition

Phones

Phones

Calling Search Space

E911CSS

E911CSS

Route Option

Route this pattern

Route this pattern

Provide outside dial tone

Check this box

Check this box

Called Party Transformations, Discard Digits (Outgoing Calls)

None

PreDot

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - 911.

- Partition - Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Make sure that this box is checked.

- Called Party Transformations, Discard Digits - Select <none>.

Step 4

Click Insert.
Unified CM saves the translation pattern.

Step 5

Repeat Step 2 to Step 4 with the following changes:

- Translation Pattern—9.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 1 provides emergency call route points for 9.911.

Note:
These route points are similar to the route points that you created in the Create Emergency Call Route Points. In this case, you enter E911 for the partition instead of Phones.

Emergency Call Route Points for 9.911

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder 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

911

912

913XXXXXXXXXX

Partition

E911

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.
or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Note:
Configuring call-forwarding numbers for the standby server ensures that calls are either routed to the PSAP servicing the default ERL or to 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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Related Tasks

Create Route Patterns for ERLs

Related Information

Configure Cisco Unified Communications Manager

ERLs

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Configure Cisco Unified Communications Manager

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

Create Route Points for 9.911

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. Table 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 1.

Step 4

Click Insert to add the new CTI route point.

- Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

- Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line that you are creating using the information in Table 1.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in Table 1 are configured.

For additional assistance, see the documentation and online help included with Unified CM.

Related Tasks

Create Route Patterns for ERLs

Related Information

Configure Cisco Unified Communications Manager

ERLs

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Configure Cisco Unified Communications Manager

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

Create 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.

Procedure

Step 1

Select Route Plan > Translation Pattern.
Unified CM opens the Find and List Translation Patterns page.

Step 2

Click Add a New Translation Pattern.
Unified CM opens the Translation Pattern Configuration page.

Step 3

Create the translation pattern:

- Translation Pattern - The number you want to support as an emergency number. In this example, 9.911.

- Partition - Select Phones.

- Numbering Plan - Select the numbering plan for your area.

- Calling Search Space - Select E911CSS.

- Route Option - Select Route this pattern.

- Provide Outside Dial Tone - Select this.

- Called Party Transformations, Discard Digits (Outgoing Calls) - Select PreDot.

Step 4

Click Insert.
Unified CM saves the translation pattern. To add additional translation patterns, return to Step 2.

Related Tasks

Create Phone Partition

Create Phone Calling Search Space

Related Information

Configure Cisco Unified Communications Manager

Configure Cisco Unified Communications Manager

Create Phone Partition

If you have not already created a partition for the phones, do so now.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as Phones, in the Partition Name and Description field. You can optionally include a description.

Step 4

Click Insert to add the new partition.

Create Phone Calling Search Space

If you do not already have a calling search space defined for the phones, follow this procedure to create one.

Procedure

Step 1

Select Route Plan > Calling Search Space in Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as PhoneCSS, in the Calling Search Space Name field.

Step 4

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.

Step 5

Click Insert to add the new calling search space.

Set Up Calling Search Space for Gateway and PSAP Connection

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 about setting up the gateway, and the Unified CM 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.

Procedure

Step 1

Select Device > Gateway.
Unified CM opens the Find and List Gateways page.

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.
Unified CM lists the gateways that match your criteria.

Step 3

Click the gateway you want to configure.
Unified CM opens the Gateway Configuration page.

Step 4

Select E911CSS for Calling Search Space.

Step 5

Click Update.
Unified CM saves your changes.

Related Tasks

Create Emergency Responder Calling Search Space

Related Information

CAMA and PRI Trunks

Emergency Responder Deployment

Emergency Responder and Your Network

Create Emergency Responder Calling Search Space

To create the Emergency Responder calling search space, follow these steps:

Procedure

Step 1

Select Route Plan > Calling Search Space from Unified CM.
The Find and List Calling Search Spaces page appears.

Step 2

Click Add a New Calling Search Space.
The Calling Search Space Configuration page appears.

Step 3

Enter a descriptive name, such as E911CSS, in the Calling Search Space Name field.

Step 4

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 Create Translation Patterns for 9.911), the 911 Route Point is 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 Emergency Responder 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.

CAMA and PRI Trunks

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. You should consult with your service provider and decide on the type of connection that works best for you.

Consider these issues:

- PRI—If 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 that 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 that 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-party number rather than a generic number (such as the main number of the site). Otherwise, the PSAP does not receive the expected ELIN, and the emergency call might not be routed to the right PSAP.

- CAMA—CAMA trunks are dedicated to emergency calls, and are available in most areas. You do not need to do 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, with 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.

Emergency Responder Deployment

The information in the following sections describe deployment models for various types of networks. You can use these examples as modules, combining them to form a larger, more complex network.

Emergency Responder and Your Network

The following figure shows how Cisco Emergency Responder (Emergency Responder) fits into your network.

How Cisco Emergency Responder Fits Into Your Network

Emergency Responder depends on Cisco Unified Communications Manager (Cisco Unified CM) for the corporate dial plan, which you must modify to send emergency calls to the Emergency Responder group.

To track phones, Emergency Responder queries Cisco Unified CM for a list of phones registered with the cluster. Emergency Responder then queries the switches on the network to determine the port used by the phones. Emergency Responder performs this operation at regular intervals throughout the day to identify phones that have changed location. See the Emergency Responder Switch Configuration for more information about setting up switches for Emergency Responder. See Phone Management for information about configuring switch ports so that Emergency Responder can send emergency calls to the correct PSAP based on port and phone location.

Note

If you locate your Cisco IP Phones using a Cisco Layer 2 protocol with connected switch port discovery, then you must map and control your wiring plan. If you do not document changes in your wiring, Emergency Responder may not be able to locate a phone in your network. Update your wiring plan and your Emergency Responder configuration every time you change your wiring.

You can also have an SMTP email server in your network or with a service provider. You can then configure Emergency Responder to send an email to your onsite security personnel when an emergency call occurs. If the server is set up as an email-based paging service, the personnel are paged.

You also need a gateway with a PRI or CAMA link to the service provider's network so that Emergency Responder can route emergency calls to the local public safety answering point (PSAP).

Figure 1 shows one Emergency Responder group supporting a single Cisco Unified Communications Manager cluster. You can support more than one Cisco Unified Communications Manager cluster with a single Emergency Responder group as long as the Unified CMs are running the same software version. With a larger network, you can install multiple Emergency Responder groups and create a Emergency Responder cluster.

See Emergency Call Process for an explanation of the path an emergency call takes when managed by Emergency Responder.

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Emergency Responder group in an Emergency Responder cluster, you must configure route patterns to enable each Emergency Responder group to route emergency calls to another Emergency Responder group if a caller's phone homes to a Unified CM cluster outside the current location of the phone. See Cisco Emergency Responder Clusters for a detailed explanation of how Emergency Responder groups communicate within a Emergency Responder cluster.

This procedure explains how to create the route pattern for one Emergency Responder group. The Inter-Cisco ER Group Route Pattern defined on a Emergency Responder Group is a route pattern for incoming Emergency Calls. Consider the network setup in the following figure.

For inter-group communications to work:

- You must define inter-cluster trunks in each Unified CM cluster to enable communications between the Unified CM clusters. See the Unified CM documentation for information about creating these types of gateways.

- Define the route pattern on the Unified CM

- Define route pattern 2000.911 and 3000.911 in CUCM cluster A.

- Define Route Pattern 1000.911 and 3000.911 in CUCM cluster B.

- Define Route Pattern 1000.911 and 2000.911 in CUCM cluster C.

- Define Inter-Emergency Responder Group Route Pattern

- In Emergency Responder Group A, define 1000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group B, define 2000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group C, define 3000.911 as the Inter Emergency Responder Group Route Pattern.

These definitions allow a call in an ERL managed by Emergency Responder Group B to be routed to Emergency Responder Group B even though the phone homes to Unified CM cluster A, which is serviced by Emergency Responder Group A.

Understanding Inter-Cisco Emergency Responder Group Route Patterns

Related Tasks

Create Emergency Responder Partition

Set Up Group Telephony Settings for Server

Related Information

Installation on a New System

Create Emergency Responder Partition

You must create the Emergency Responder partition E911. This partition contains the numbers used by the PSAP to call into the network and to certain other CTI route points.

Procedure

Step 1

Select Route Plan > Partition in Unified CM.
The Find and List Partitions page appears.

Step 2

Click Add a New Partition.
The Partition Configuration page appears.

Step 3

Enter a descriptive name, such as E911, in the Partition Name field.

Step 4

Click Insert to add the new partition.

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Create Emergency Responder Cisco Unified Communications Manager User

You must add Emergency Responder as a Unified CM user. The settings you enter here are used when you configure the Unified CM settings for Emergency Responder.

Procedure

Step 1

In Unified CM, select User Management > Application User. Click the Add New button.
Unified CM displays the Application User Configuration page.

Step 2

Complete the following required fields:

- UserID—Use a descriptive name such as "Emergency_Responder_User."

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

In the Device Information section, select the desired route points and CTI ports and then click the down arrow to add the selected devices to the user control list. The list of devices appears in the Controlled Devices area.

Step 4

Select the following devices:
Note:
You may need to use Find Phones or Find Route Points to select the desired devices.

- All CTI ports created for Cisco Emergency Responder use. For more information, see "Creating the Required CTI Ports" section.

- The primary emergency call number, for example, 911.

- The backup emergency call number, for example, 912.

- The route point used for ELINs, for example, 913XXXXXXXXXX.

Step 5

Click Save.

Step 6

In the Unified CM menu at the top, click User Management > User Group.
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.

Step 8

Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page.

Step 9

Click Add Application Users to Group.
The Find and List Application Users popup window appears.

Step 10

Enter the User ID and click Find.
The list of Applications users appears.

Step 11

Check the check box next to the user ID and click Add Selected.
Unified CM adds the selected user to the Standard CTI Allow Calling Number Modification user group.

Step 12

Choose 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.

Step 14

Click the Standard CTI Enabled group.
Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.

Related Tasks

Create Emergency Call Route Points

Create Required CTI Ports

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

Create Required CTI Ports

Emergency Responder 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 that you configure is the number of simultaneous calls Emergency Responder can make to these personnel. It does not relate to the number of emergency calls Emergency Responder can handle or forward to the PSAP. There is no configurable limitation to the number of simultaneous emergency calls that Emergency Responder can handle.

Before You Begin
Emergency Responder 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.

Procedure

Step 1

Select Device > Phone.
Unified CM opens the Find and List Phones page.

Step 2

Click Add a New Phone.
Unified CM opens the Add a New Phone page.

Step 3

Select CTI Port for Phone Type and click Next.
Unified CM opens the Phone Configuration page.

Step 4

Configure the CTI Port, entering this information:

- Device Name- Enter something meaningful to you, for example, CTI3001.

- Device Pool- Select an appropriate device pool. This device pool must use the G.711 region.

- Calling Search Space- Select PhoneCSS.

Step 5

Click Insert.
Unified CM creates the CTI port and asks if you want to configure line 1. Click OK. Unified CM opens the Directory Number Configuration page.

Step 6

Configure line 1 for the CTI port, entering this information:

- Partition- Select Phones.

- Calling Search Space- Select 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.
Unified CM 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.

Website Interfaces

Emergency Responder provides several web sites from which you can access and use different parts of the system. From the main Emergency Responder web page, you can access the following areas:

- Emergency Responder Serviceability

- Emergency Responder Administration (default home)

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

Each of these web sites allows a user access to different parts of the system and requires a separate login and password. Access to these web sites is controlled through the role-based user management mechanism (for more information, see Role-Based User Management).

When the Emergency Responder system is first installed, a default Emergency Responder Administrator user is created. The default Administrator has full access to all web sites except the Cisco Unified OS Administration and Disaster Recovery System websites, and can create users, roles, and user groups. The default Administrator cannot be deleted from the system.

Related Information

Cisco Emergency Responder Administration Web Interface

Cisco Emergency Responder Serviceability Web Interface

Cisco Unified Operating System Administration Web Interface

Disaster Recovery System Web Interface

Cisco Emergency Responder Administration Web Interface

Cisco Emergency Responder Serviceability Web Interface

Cisco Unified Operating System Administration Web Interface

Disaster Recovery System Web Interface

User Management

On installation, the system creates one default user, Emergency Responder Administrator. The Emergency Responder Administrator has access to all system administration screens except the Platform Administration and Disaster Recovery System screens. By default, the Emergency Responder Administrator user is assigned to the Emergency Responder System Administrator, Emergency Responder Serviceability, Emergency Responder Admin Utility, and Emergency Responder User user groups and has access to the resources defined for the Emergency Responder System Admin, Emergency Responder Serviceability, Emergency Responder Admin Utility, and Emergency Responder User roles.

Note

The default Emergency Responder Administrator user cannot be deleted.

You can add additional users. After 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 References

Find and List Users

Related Information

Emergency Responder User Management

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Find and List Users

The Find and List Users page appears when you choose User Management > User.

Authorization Requirements

You must have system administrator authority to access this page.

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.

The following table describes the Find and List Users page.

Find and List Users Page

Field

Description

User Search Parameters

Find User where User Name

Enter search criteria to select the users that you want to find.

To find all users, click Find without entering any criteria.

To narrow your search:

- Select All to indicate that only users that match the selected criteria be displayed (an AND search).

- Select Any to indicate that users that match any search criteria be selected (an OR search).

- From the pull down menu, select the field that you want to search, select its corresponding relationship and select how many results per page are displayed. The search fields and the corresponding relationships are:

- Authentication Mode—Both, Remote or Local

- User Name— Ends with, Starts with, contains or Exactly.

- Unified CM Cluster—Ends with, Starts with, contains or Exactly.

- 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.

User

Users list

This section of the page displays the search results. If there are no usernames are displayed after completion of the search, then no users have been configured yet.

Username

Displays the users name based on the selection criteria.

Authentication Mode

Displays the authentication mode of the user. The authentication mode can be either Remote or Local.

Unified CM Cluster

This value is displayed only when the user is authenticated remotely, with the Unified CM server.

Edit icon

Click the user name or the Edit icon to display the Modify User page, which allows you to change the user authentication mode, password and Unified CM cluster. The Modify User page also displays which groups and roles have been assigned to the user.

Delete icon

Click the Delete icon to delete the user from the system.

Note:
You cannot delete the Administrator.

Add New User button

Click the Add New User button to open the Add User page. See Table 1 for a description of the Add User page.

Delete Users button

Click the Delete Users button to delete users in bulk. Select multiple users, both remote and local, by checking the check box and then clicking the Delete Users button.

Change to Remote Users button

Click the Change to Remote Users button to change local users to remotely authenticated users in bulk.

Role Management

On installation, the system creates six default roles. The following table lists and describes the default roles.

Note

Default roles cannot be deleted.

Default Roles

Role

Description

Emergency Responder System Admin

Has access to all system administration screens.

Emergency Responder Serviceability

Has access to all serviceability screens.

Emergency Responder Admin Utility

Has access to all Admin Utility screens.

Emergency Responder Network Admin

Has access to Cisco Unified Communications Manager, LAN switch, and SNMP settings screens.

Emergency Responder ERL Admin

Has access to all ERL-related screens.

Emergency Responder User

Has access to the user screens.

When creating a new role or modifying an existing role, you specify which system resources are assigned to the role. A resource is the same thing as a web page or a menu item within the Emergency Responder administration website. For example, the Find and List Roles web page is a resource, as is the User Management > Role menu item.

The following table 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 Emergency Responder Serviceability website is one resource but it contains many submenus.

Resources Assigned to Default Roles

Resource

Emergency Responder System Admin

Emergency Responder Network Admin

Emergency Responder ERL Admin

Emergency Responder Serviceability

Emergency Responder Admin Utility

Emergency Responder User

Add Subscriber

x

Admin Utility

x

ALI Formatting Tool

x

All Logs

x

Application User

x

Call History

x

Unified CM Details

x

x

Emergency Responder Groups in Cluster

x

Change Unified CM Version

x

Cluster DBHost Setting

x

Control Center

x

CPU and Memory Usage

x

Device SNMP Settings

x

x

Disk Usage

x

ERL

x

x

ERL Audit Trail

x

ERL Debug Tool

x

ERL Migration

x

x

Event Viewer

x

File Management Utility

x

Functional role

x

Intrado ERL

x

x

Intrado VUI Settings

x

IP subnet

x

x

License Management

x

Mail Alert Configurations

x

Manually Configured Phones

x

x

MIB2 System Group Configuration

x

Off-Premises ERL

x

x

Onsite Contact

x

x

Pager Alert Configurations

x

x

Phone Search

x

Point to New Publisher

x

Processes

x

PS ALI Convert

x

PS ALI Export

x

Purge

x

Run Tracking

x

x

Tracking Schedule

x

x

Server

x

Server Group

x

LAN Switches

x

x

SNMP V1/V3c Configuration

x

SNMP V3 Configuration

x

Switch Port

x

x

Synthetic Phone

x

x

Telephony

x

Unlocated Phones

x

x

User Call History

x

User Group

x

Web Alert

x

Related References

Find and List Roles

Related Information

Emergency Responder Role Management

Emergency Responder Role Management

When you install Emergency Responder, the system defines six default roles (see Role Management for more information about the default roles). You can also define additional roles or modify existing roles.

The following topics describe how to add new roles and how to modify and delete existing roles.

Find and List Roles

The Find and List Roles page appears when you choose User Management > Role.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List Role page to find, list, modify, and delete current roles, and to add new roles.

The following table describes the Find and List Roles page.

Find and List Roles Page

Field

Description

Role Search Parameters

Find Role where Role Name is

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 pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Roles

Section of the page in which the search results are displayed. These default roles are created during installation:

- Emergency Responder System Admin

- Emergency Responder ERL Admin

- Emergency Responder Network Admin

- Emergency Responder 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:

- Role Name

- Description

- List of resources assigned to that role

Note:
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 are 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 1 for more information about the Modify Role page.

Edit icon

Click the Edit icon to display the Modify Role page. See Table 1 for information about the Modify Role page.

Delete icon

Click the Delete icon to delete the role from the system.

Note:
You cannot delete any of the default roles.

Add New Role button

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 1 for information about the Add Role page.

User Group Management

On installation, the system creates six default user groups. The following table lists and describes the default user groups.

Note

Default user groups cannot be deleted.

Default User Groups

User Group

Description

Emergency Responder System Administrator

Assigned System Administration roles

Emergency Responder Network Administrator

Assigned Network Administration role

Emergency Responder ERL Administrator

Assigned ERL Administration role

Emergency Responder Serviceability

Assigned Serviceability role

Emergency Responder Admin Utility

Assigned Admin Utility role

Emergency Responder User

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 have access to all the resources defined by the roles assigned to the group.

Related References

Find and List User Groups

Related Information

Emergency Responder User Group Management

Emergency Responder User Group Management

When you install Emergency Responder, the system defines six default user groups (see User Group Management for more information about the default user groups). You can also define additional user groups or modify existing user groups.

The following topics describe how to add new user groups and how to modify existing user groups.

Find and List User Groups

The Find and List User Groups page appears when you choose User Management > User Group.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List User Groups page to find, list, modify, and delete current user groups, and to add new user groups.

The following table describes the Find and List User Groups page.

Find and List User Groups Page

Field

Description

User Group Search Parameters

Find User Group where User Group Name

Enter search criteria to select the user group you want to find.

To find all user groups, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

User Groups

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 Modify User Group for information.

Edit icon

Click the Edit icon to display the Modify User Group page. See Modify User Group for information.

Delete icon

Click the Delete icon to delete the user group from the system.

Note:
You cannot delete default user groups that were created during installation.

Add New User Group button

Click the Add New User Group button to display the Add User Group page. See Table 1 for information about the Add User Group page.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

Related References

Conventional ERL

LAN Switch Details

Switch Port Details

Find and List IP Subnets

Find and List Manually Configured Phone

File Management Utility

Conventional ERL

The Conventional ERL page appears when you choose ERL >Conventional ERL.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create are 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.

The following table describes the Find and List ERLs page.

Find and List ERLs Page

Field

Description

Notes

ERL Search Parameters

Find Conventional ERL where...

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:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL 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 is 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 remains there until it is modified.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Configure Default ERL

Click Configure Default ERL to configure a default ERL

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Find and List IP Subnets

The Find and List IP Subnets page appears when you choose ERL Membership > IP Subnets.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List IP Subnets page.

Find and List IP Subnets Page

Field

Description

IP Subnet Search Parameters

Find IP Subnets where...

To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.

IP Subnets

IP Subnets list

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 preceding records or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field 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 of the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See IP Subnet Phones.

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

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.

Add New IP Subnet

Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See Configure IP Subnet for more information

Export

Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See Export IP Subnets for more information,

Import

Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See Import IP Subnets for more information,

Find and List Manually Configured Phone

The Find and List Manually Configured Phones page appears when you choose ERL Membership > Manually Configured Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Manually Configured Phones page.

Note

When you are performing this search as part of an E.164 dial plan, the "+" is a valid character.

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 that you want to find.

To find all manually configured phones, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed per page from the pull-down 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 Add New Manual Phone 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 Export Manual Phones for more information.

Import

To import Manually Configured Phone information to a file, click Import on the Find and List Manually Configured Phones page. See Import Manual Phones for more information.

File Management Utility

The File Management Utility page appears when you choose Tools > File Management Utility.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the File Management Utility page to search for, download, or delete exported files.

The following table describes the File Management Utility page.

File Management Utility Page

Field

Description

Search Parameters

Please Select:

From the pull-down menu, select the type of file that you want to search for.

Search button

Click Search to perform the search.

Exported Files

Area of the page that displays the search results. Displays the File Name, Last Modified data, and File Size for each file found.

Download button

Downloads the selected file.

Note:
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.

Delete button

Deletes the selected file.

Note:
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.

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

Related Tasks

Set Up Users and Groups

Set Up Switch Connection

Manage Onsite Alerts, ERLs, and ALI Data

Set Up Emergency Responder with Intrado V9-1-1 for Enterprise Service

Set Up Users and Groups

The following procedure provides information about the tasks that must be completed to set up Emergency Responder users and groups. This task can be completed by a System Administrator.

- Create the users your organization requires for Emergency Responder administration.

- Create the Emergency Responder group.

- Set up the Emergency Responder group telephony settings.

- Update Emergency Responder servers to the Emergency Responder group.

- Upload the product license key.

- Identify and configure the Unified CM clusters whose emergency calls this Emergency Responder group handles.

Note

The network administrator can also perform this step.

- Understand recurring system administration tasks.

- If you use Intrado V9-1-1 for Enterprise Service, configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

- If you support off-premise users, configure AXL authentication information with Unified CM.

Set Up Switch Connection

The following procedure provides information about the tasks that must be completed to set up Emergency Responder switch connection. This task can be completed by a Network Administrator.

- Enter the SNMP read community strings.

- Define the schedule Emergency Responder should use for updating information from the switches.

- Identify the switches that can have phones connected to them.

- Run the switch-port and phone update process so that Emergency Responder can identify the ports on the switches and whether phones are attached to them.

- Understand recurring network administration tasks.

Manage Onsite Alerts, ERLs, and ALI Data

The following procedure provides information about the tasks that must be completed to Manage onsite alerts, ERLs, and ALI data. This task can be completed by an ERL Administrator.

- Identify the onsite alert (security) personnel that should receive alerts from Emergency Responder.

- 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.

- Add phones that Emergency Responder does not directly support.

Note

Emergency Responder does not automatically track the movement of these phones.

- Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Emergency Responder 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.

Set Up Emergency Responder with Intrado V9-1-1 for Enterprise Service

The following tasks apply when you use Emergency Responder with Intrado V9-1-1 for Enterprise Service:

- Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

- Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

- If you support off-premise users, create off-premise ERLs and assign to IP subnets and unlocated phones.

Note

You cannot assign off-premise ERLs to switch ports.

Set Up Users and Groups

The following procedure provides information about the tasks that must be completed to set up Emergency Responder users and groups. This task can be completed by a System Administrator.

- Create the users your organization requires for Emergency Responder administration.

- Create the Emergency Responder group.

- Set up the Emergency Responder group telephony settings.

- Update Emergency Responder servers to the Emergency Responder group.

- Upload the product license key.

- Identify and configure the Unified CM clusters whose emergency calls this Emergency Responder group handles.

Note

The network administrator can also perform this step.

- Understand recurring system administration tasks.

- If you use Intrado V9-1-1 for Enterprise Service, configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

- If you support off-premise users, configure AXL authentication information with Unified CM.

Related Tasks

Emergency Responder Configuration

Log In to Emergency Responder

Set Up Server Group

Set Up Group Telephony Settings for Server

Configure Servers

Upload License File

Identify Cisco Unified Communications Manager Clusters

Set Up Intrado VUI Settings

Set Up AXL Authentication

Related References

Emergency Responder System Administrator Role

Related Information

Emergency Responder User Management

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Set Up Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings, as described in the Group Settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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 Add Onsite Security Personnel), 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada), select it in the drop-down box. The default language is English.
Note:
The drop-down box provides a selection for Spanish (Spain) Voice Alerts only. When selected, the web interface remains in default English.

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

Configure Servers

After you create an Emergency Responder group, you can use the Server Settings page to update Emergency Responder 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 Emergency Responder server.

Procedure

Step 1

Select System > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

Select the server name in the left-hand Servers list to change the server settings (Server Name or Debug Package List, or Trace Package List settings). Emergency Responder loads the server settings into the edit boxes. Make your changes and click Update.

Step 3

Select the server and click Delete to remove a server from the group. 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.

Step 4

When you are satisfied with your settings, click Update.
Emergency Responder saves your changes and displays them in the list of servers at the top of the page.

Upload License File

Cisco Prime License Manager maintains the licensing for Cisco Emergency Responder 10.0 and later.

Use the Prime License Manager tool to obtain licenses from Cisco, to install the licenses, and to manage and view your inventory of licenses. This tool also tracks license compliance or noncompliance.

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Emergency Responder System Administrator Role

The following table 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 Emergency Responder ERL Administrator Role and the Emergency Responder Network Administrator Role.

Cisco Emergency Responder System Administration Recurring Tasks

Recurring Task

Description

More Information

Add additional Cisco Emergency Responder groups

As telephones are added to the network, you might need additional Cisco Emergency Responder groups. Install and define them and their telephony settings.

Work with the telephony administrator to complete the required Unified CM configuration.

- Installation on a New System

- Set Up Server Group

- Set Up Group Telephony Settings for Server

- Configure Servers

- Identify Cisco Unified Communications Manager Clusters

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.

Create new Cisco Emergency Responder users; remove old users

As onsite alert personnel change, or as Cisco Emergency Responder system, network, and ERL administrators change, add or remove them as required.

- Emergency Responder User Management

Add or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder network administrator.

- Identify Cisco Unified Communications Manager Clusters

Monitor the email alerts that Cisco Emergency Responder generates

If your email ID is configured in the server group settings, Cisco Emergency Responder sends email alerts about critical errors to you. You are expected to understand the error and take action to correct the problem.

See Troubleshoot Email Alerts for information to help you understand the email alerts and resolve problems.

- Set Up Server Group

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Set Up AXL Authentication

Procedure

Step 1

From Emergency Responder, choose Phone Tracking > Unified CM.

Step 2

Under AXL Setting, enter the following information:

- AXL Username

- AXL Password

- AXL Port Number

Step 3

Click Insert.

Set Up Switch Connection

The following procedure provides information about the tasks that must be completed to set up Emergency Responder switch connection. This task can be completed by a Network Administrator.

- Enter the SNMP read community strings.

- Define the schedule Emergency Responder should use for updating information from the switches.

- Identify the switches that can have phones connected to them.

- Run the switch-port and phone update process so that Emergency Responder can identify the ports on the switches and whether phones are attached to them.

- Understand recurring network administration tasks.

Related Tasks

Emergency Responder Configuration

Set Up SNMPv2

Define Phone Tracking and Switch Update Schedules

Manually Run the Switch-Port and Phone Update Process

Related References

Emergency Responder Network Administrator Role

Related Information

LAN Switch Identification

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

Set Up SNMPv2

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 define in Emergency Responder. If you use different strings for different sets of switches, determine whether 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.*.*.

If two or more patterns match an IP address, Emergency Responder 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, Emergency Responder uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

Procedure

Step 1

Select Phone Tracking > SNMPv2 Settings.
Emergency Responder opens the SNMP Settings page.

Step 2

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 Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see LAN Switch Identification for more information), it does not matter if the IP address patterns cover devices other than switches.

- If all of your switches use the same read community string, enter *.*.*.*. You 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 Emergency Responder 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, Emergency Responder 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.

Step 4

Enter the read community string, for example, public.

Step 5

Click Insert.
Emergency Responder adds the SNMP setting to the list of settings.

Step 6

If you must create more than one setting, return to Step 2.
If you change the SNMP read community string on a switch, you must update the associated setting in Emergency Responder:

- To change an SNMP setting, select it in the list. Emergency Responder 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 setting's entry.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Emergency Responder Network Administrator Role

The following table lists the recurring tasks for which a network administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder Network Administration Recurring Tasks

Recurring Task

Description

More Information

Add new switches

Add any switches that you add to the network to the Cisco Emergency Responder configuration. A switch is considered new if it has an IP address not defined in Cisco Emergency Responder.

- LAN Switch Identification

- Manually Run the Switch-Port and Phone Update Process

Remove old switches

Remove switches from the Cisco Emergency Responder configuration if you remove them from the network. Nonexistent switches in the Cisco Emergency Responder configuration do not create problems, but they do increase the time required to do phone tracking, because Cisco Emergency Responder attempts to connect to the switch must time out before moving on to the next switch.

- LAN Switch Identification

Update the SNMP read community if it changes

If you change the read community string on any defined switch, you must update the SNMP settings in Cisco Emergency Responder. Until the setting is updated, Cisco Emergency Responder cannot track phones attached to the switch.

- Set Up SNMPv2

Update or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder system administrator.

- Identify Cisco Unified Communications Manager Clusters

Check ERL assignments

Use the ERL Debug Tool to check that the correct and expected ERL is used for a selected phone.

- Emergency Responder Admin Utility

Manage Onsite Alerts, ERLs, and ALI Data

The following procedure provides information about the tasks that must be completed to Manage onsite alerts, ERLs, and ALI data. This task can be completed by an ERL Administrator.

- Identify the onsite alert (security) personnel that should receive alerts from Emergency Responder.

- 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.

- Add phones that Emergency Responder does not directly support.

Note

Emergency Responder does not automatically track the movement of these phones.

- Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Emergency Responder 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.

Related Tasks

Emergency Responder Configuration

Add Onsite Security Personnel

Manually Define Phones

Identify Unlocated Phones

Export ERL Information

Export ALI Information for Submission to Your Service Provider

Related References

Emergency Responder ERL Administrator Role

Related Information

ERLs

ERL Management

ERL Creation

Switch Port Configuration

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Add Onsite Security 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 Emergency Responder end-user interface.

- An email message. If you use an email-based paging address, the message results in a page.

- A telephone call indicating that an emergency call was made.

Before You Begin
You must log into Emergency Responder 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).

Procedure

Step 1

Select ERL > Onsite Alert Settings.
Emergency Responder opens the Onsite Alert Settings page.

Step 2

Enter the unique ID, name, telephone number, email address, and pager address of a security or onsite alert person.
Unique ID might be a badge number, email name, or other site-specific unique name. You 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.
Emergency Responder adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.

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 person's record.

- To modify onsite alert settings, click on the person's Onsite Alert ID, Onsite Alert Name, Onsite Alert Number, Onsite Alert Email Address or Onsite Alert Pager 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 person's Onsite Alert ID: to change the Onsite Alert ID, delete the person's entry and create a new one.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

Emergency Responder ERL Administrator Role

The following table lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder ERL Administration Recurring Tasks

Recurring Task

Description

More Information

Assign ERLs to new or changed switch ports

If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.

Switch Port Configuration

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 Emergency Responder.

- ERL Creation

- Switch Port Configuration

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.

- Export ERL Information

- Export ALI Information for Submission to Your Service Provider

- ERL Creation

- ALI Submission and Service Provider Requirements

Audit the manually defined phones

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.

- Manually Define Phones

Audit the unlocated phones list

Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco Emergency Responder cannot locate the phones and to resolve the problems.

- Identify Unlocated Phones

- Unlocated Phones

Add new onsite personnel or remove old ones; update phone numbers

As onsite alert personnel are added, define them in Cisco Emergency Responder and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco Emergency Responder. Update phone numbers, email address, and other contact information as they change.

- Add Onsite Security Personnel

- ERL Creation

Add IP subnet for the IP subnets to be tracked

If there is a new IP subnet that needs to be discovered by Emergency Responder, then perform the following tasks:

- Configure an ERL spanning the new IP subnet's geographical location.

- Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL.

- Set Up IP Subnet-based ERLs

Set Up Emergency Responder with Intrado V9-1-1 for Enterprise Service

The following tasks apply when you use Emergency Responder with Intrado V9-1-1 for Enterprise Service:

- Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

- Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

- If you support off-premise users, create off-premise ERLs and assign to IP subnets and unlocated phones.

Note

You cannot assign off-premise ERLs to switch ports.

Related Tasks

Emergency Responder Configuration

Set Up Intrado ERLs

Reconcile ALI Discrepancies

Set Up Off-Premise ERL

Identify Unlocated Phones

Related Information

Switch Port Configuration

Emergency Responder Configuration

The following procedure provides information about the tasks that must be completed to configure Emergency Responder and indicates which user types can complete the tasks, with pointers to more detailed information.

Note

Some of the following tasks listed can be done in parallel.

- Create and set up Emergency Responder users and groups. This step can be completed by the System Administrator.

- Identify the switches and configure the connection to them. This step can be completed by the Network Administrator.

- Identify the onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. This step can be completed by the ERL Administrator.

- Set up Emergency Responder with Intrado V9-1-1 for Enterprise Service.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Delete Users

Emergency Responder enables you to perform batch operations in which you can either delete a single user or delete multiple users in bulk.

Note

You cannot delete the default administrative user created at the time of installing Emergency Responder.

Procedure

Step 1

From the Emergency Responder Administration web interface, select User Management > User.
The Find and List Users page appears.

Step 2

Enter search criteria to find the specific user that you want to delete and click Find, or click Find without any search criteria to display all configured users. The search results appear.

Step 3

Find the user that you want to delete and click the Delete icon for that user.
The system displays a warning prompting you to confirm the deletion.

You also can select multiple users from the list, both local and remote, by checking the check box and then clicking the Delete Users button to delete users in bulk.

The system displays a warning prompting you to confirm the deletion.

Step 4

Click OK. The user is removed from the system and all User Group associations to the user are deleted.

Related Tasks

Log In to Emergency Responder

Related Information

Cisco Emergency Responder User Preparation

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Cisco Emergency Responder User Preparation

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Related Information

Emergency Responder User Management

Emergency Responder Role Management

Emergency Responder User Group Management

Cisco Emergency Responder User Preparation

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Emergency Responder Role Management

When you install Emergency Responder, the system defines six default roles (see Role Management for more information about the default roles). You can also define additional roles or modify existing roles.

The following topics describe how to add new roles and how to modify and delete existing roles.

Emergency Responder User Group Management

When you install Emergency Responder, the system defines six default user groups (see User Group Management for more information about the default user groups). You can also define additional user groups or modify existing user groups.

The following topics describe how to add new user groups and how to modify existing user groups.

Cisco Emergency Responder User Preparation

Restrict Maximum Number of Concurrent Sessions

Emergency Responder allows the administrator to restrict the maximum number of concurrent sessions that can be active at a time for any user. If this restriction is enabled, the administrator can specify a maximum limit (between 1 and15) for the number of concurrent sessions allowed.

This limit is applicable to all users configured in Emergency Responder.

Emergency Responder restricts users from creating more than the specified number of concurrent sessions. Users who attempt to create additional sessions that exceed the concurrent session limit are prevented from logging in to Emergency Responder and will see the following error message: Session limit exceeded. Please log out of any existing sessions and try again.

Note

This limit is applicable to all users that exceed the limit.

Note

This limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Warning

If a user logs in to an Emergency Responder website and closes the browser without logging out, the session remains active until it times out after a period of 30 minutes. During this period, if the user attempts to establish additional sessions beyond the prescribed limit, he will be unable to do so.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Check the Limit Concurrent Sessions check box. This option is used to enable limiting the number of concurrent sessions and enables the Max. number of concurrent sessions drop-down box.

Step 3

Select the maximum number of concurrent sessions that you want to impose on the Emergency Responder user, from the Max. number of concurrent sessions drop-down box.

Step 4

Click the Update Settings button to apply the new change.
Note:
You can disable the maximum number of concurrent settings by selecting System > Emergency Responder Group Settings and uncheck the Limit Concurrent Sessions check box.

Related References

Group Settings

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page—English or French (Canadian).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Set Up a Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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, 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada) or Spanish(Spain), select it in the drop-down box. The default language is English(US).

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Related Tasks

Configure Servers

Collect Information From Syslog

Related References

Group Settings

Configure Servers

After you create an Emergency Responder group, you can use the Server Settings page to update Emergency Responder 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 Emergency Responder server.

Procedure

Step 1

Select System > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

Select the server name in the left-hand Servers list to change the server settings (Server Name or Debug Package List, or Trace Package List settings). Emergency Responder loads the server settings into the edit boxes. Make your changes and click Update.

Step 3

Select the server and click Delete to remove a server from the group. 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.

Step 4

When you are satisfied with your settings, click Update.
Emergency Responder saves your changes and displays them in the list of servers at the top of the page.

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page—English or French (Canadian).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Collect Information From Syslog

You can configure Emergency Responder to use Syslog output from Emergency Responder for use with other network management systems.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select enable in Enable Syslog.

Step 3

Enter the fully qualified DNS name of the server in the Syslog Server field, for example, server.domain.com.

Step 4

Click Update Settings to save your changes.
Emergency Responder immediately begins writing messages to syslog.

Modify 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 Emergency Responder user in Unified CM.

Caution

Modify the emergency number during off-peak hours.

Procedure

Step 1

Associate the new route point with the Emergency Responder user in Unified CM. See Create Emergency Responder Cisco Unified Communications Manager User.

Step 2

Modify the route point for the new number: enter the number in the Route Point for Primary Cisco ER Server. field.

Step 3

Click Update Settings.
Note:
Emergency Responder can still support only one emergency number. After you change it, Emergency Responder starts routing calls received at the new emergency number route point.

Related Tasks

Create Emergency Call Route Points

Create Route Patterns for ERLs

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

Identify Cisco Unified Communications Manager Clusters

Related References

Telephony Settings

Telephony Settings

The Telephony Settings page appears when you choose System > Telephony Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Telephony Settings page to define the telephone numbers and telephony ports used by the Emergency Responder group.

The following table describes the Telephony Settings page.

Telephony Settings Page

Field

Description

Notes

Specify telephony attributes

Route Point for Primary Emergency Responder Server

The CTI route point that the primary server should use, such as 911.

See Create Emergency Call Route Points for more information.

Route Point for Standby Emergency Responder Server

The CTI route point that the standby server should use, such as 912. Configure this number as the call forward number for the primary emergency number.

See Create Emergency Call Route Points for more information.

PSAP Callback Route Point Pattern

CTI route point that 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.

For more information, see Create Emergency Call Route Points.

ELIN Digit Strip Pattern

Digits to strip from the beginning of the PSAP Callback Route Point Pattern, for example, 913. The number that results from stripping the pattern should be the ELIN numbers that the PSAP can use to call into your network.

This string must be part of the PSAP Callback Route Point Pattern.

UDP Port Begin

Port numbers that are used by CTI ports during their registration.

The range is 1024 to 65535.

Inter-Emergency Responder Group Route Pattern

Route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

The pattern can only consist of numbers and dots.

For a more detailed explanation of this number, see Create route patterns for Inter-Cisco Emergency Responder Group Communications.

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 Emergency Responder.

The ToS value entered here only applies to the RTP packets sent by Emergency Responder for the onsite audio alert feature.

Onsite Alert Prompt Repeat Count

Number of times the prompt is played on the onsite alert phone.

Use IP Address from call signaling

If this parameter is enabled, Emergency Responder obtains the IP address of the phone from JTAPI. This parameter is used to route the call. If an IP subnet is configured for the phone, this parameter setting takes precedence over any other manual configuration.

If this parameter is disabled, Emergency Responder uses the manual configuration of the phone to route the call.

This field is applicable only if Emergency Responder is configured with Cisco Unified Communications Manager 6.x and above.

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado Route Pattern Settings

Intrado Route/Translation Pattern

Enter the route patterns or translation pattern for an Intrado emergency response location (ERL). An Intrado ERL is an ERL that is serviced by Intrado. Intrado ERL only lists the route patterns that have been configured on this page. You can add new route patterns or translation patterns, or you can update or remove existing route patterns or translation patterns.

To add a new route or translation pattern, click on the text box, enter the route pattern, including numbers and wildcard (do not use spaces), and click Add.

To update an existing route pattern, click on the appropriate route pattern, modify the pattern, and click Update.

To remove an existing route pattern, click on the appropriate route pattern and click Remove.

To cancel your existing changes and go back to the last saved settings, click Cancel Changes.

Create Emergency Call Route Points

You must configure CTI route points in Unified CM for these numbers:

- The emergency call number for your locale, such as 911.

Note

If you use 9 as the access code, see Create Translation Patterns for 9.911 to configure Emergency Responder.

- The number that your standby Emergency Responder server should listen to, such as 912.

- The number that incoming calls from the public safety answering point (PSAP) use.

- Emergency Responder 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 ELIN Numbers Emergency Calls and PSAP Callbacks 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 Emergency Responder, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

The following table describes the emergency call route points.

Emergency Call Route Points

Route Point Setting

Route Points

Primary Number (911)

Backup Number (912)

ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Emergency Responder handles all calls to this number.

Route point for the Emergency Responder standby server. If the primary server is unable to handle a call, the standby server receives the call through this route point.

The destination of all incoming calls from the PSAP. Emergency Responder transfers these calls to the emergency caller. The Route pattern is a prefix (913) plus a Fully Qualified Number.

Fully Qualified Number could be North American Numbering Plan or E.164 with Country Code. In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Note:   In case the ELIN is received as E.164 number with a leading plus sign ( +), use a Translation Pattern to remove the leading plus sign.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination:

- Route pattern for default ERL.

or

- Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Voice Mail Mask

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Do not configure a Voice Mail Mask for this route point.

Note

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. Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Emergency Responder cannot handle the call.

Procedure

Step 1

In Unified CM, 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.

Step 3

Fill in the CTI route point properties:

- Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. The Emergency call route points table above 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 the Emergency call route points table above.

Step 4

Click Insert to add the new CTI route point.
Unified CM adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Unified CM opens the Directory Number configuration page.

Step 5

Enter the configuration for the line you are creating using the information in the Emergency call route points table above.

Step 6

Click Insert.
Unified CM adds the line to the device. Repeat this procedure until all devices described in the Emergency call route points table above are configured.

For additional assistance, see documentation and online help included with Unified CM.

Create Route Patterns for ERLs

Emergency Responder 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 connects to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you assign the route pattern.

You must create one route pattern for every ERL 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 ERL Creation for information about ERLs.

Procedure

Step 1

Select Route Plan > Route Pattern.
Unified CM opens the Find and List Route Patterns page.

Step 2

Click Add a New Route Pattern.
Unified CM opens the Route Pattern Configuration page.

Step 3

Enter the information for the route pattern:

- Route Pattern - A 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.

- Partition - Select E911.

- Numbering Plan - Select the numbering plan for your area.

- Gateway/Route List - Select the gateway to use for connecting to the local PSAP.

- Route Option - Select Route this pattern.

- Use Calling Party's External Phone Number Mask - Select this option.

- Discard Digits - Select 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.
Unified CM 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 Emergency Responder cluster identifier; y is a Emergency Responder group identifier; zz is the PSAP identifier; aaa is the ERL identifier; and b is the ELIN identifier (within the ERL).

Create Route Patterns for Inter-Cisco Emergency Responder Group Communications

If you have more than one Emergency Responder group in an Emergency Responder cluster, you must configure route patterns to enable each Emergency Responder group to route emergency calls to another Emergency Responder group if a caller's phone homes to a Unified CM cluster outside the current location of the phone. See Cisco Emergency Responder Clusters for a detailed explanation of how Emergency Responder groups communicate within a Emergency Responder cluster.

This procedure explains how to create the route pattern for one Emergency Responder group. The Inter-Cisco ER Group Route Pattern defined on a Emergency Responder Group is a route pattern for incoming Emergency Calls. Consider the network setup in the following figure.

For inter-group communications to work:

- You must define inter-cluster trunks in each Unified CM cluster to enable communications between the Unified CM clusters. See the Unified CM documentation for information about creating these types of gateways.

- Define the route pattern on the Unified CM

- Define route pattern 2000.911 and 3000.911 in CUCM cluster A.

- Define Route Pattern 1000.911 and 3000.911 in CUCM cluster B.

- Define Route Pattern 1000.911 and 2000.911 in CUCM cluster C.

- Define Inter-Emergency Responder Group Route Pattern

- In Emergency Responder Group A, define 1000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group B, define 2000.911 as the Inter-Emergency Responder Group Route Pattern.

- In Emergency Responder Group C, define 3000.911 as the Inter Emergency Responder Group Route Pattern.

These definitions allow a call in an ERL managed by Emergency Responder Group B to be routed to Emergency Responder Group B even though the phone homes to Unified CM cluster A, which is serviced by Emergency Responder Group A.

Understanding Inter-Cisco Emergency Responder Group Route Patterns

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Configure Servers

After you create an Emergency Responder group, you can use the Server Settings page to update Emergency Responder 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 Emergency Responder server.

Procedure

Step 1

Select System > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

Select the server name in the left-hand Servers list to change the server settings (Server Name or Debug Package List, or Trace Package List settings). Emergency Responder loads the server settings into the edit boxes. Make your changes and click Update.

Step 3

Select the server and click Delete to remove a server from the group. 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.

Step 4

When you are satisfied with your settings, click Update.
Emergency Responder saves your changes and displays them in the list of servers at the top of the page.

Related Tasks

Set Up Server Group

Set Up Group Telephony Settings for Server

Identify Cisco Unified Communications Manager Clusters

Related References

Server Settings for Emergency ResponderServerGroup

Related Information

Installation on a New System

Installation on a New System

This procedure describes how to install Emergency Responder as a new installation.

You enter Emergency Responder group configuration through the Emergency Responder Administration web interface based on Publisher (primary) and Subscriber (secondary) server pairs as described in the following sections.

Set Up Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings, as described in the Group Settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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 Add Onsite Security Personnel), 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada), select it in the drop-down box. The default language is English.
Note:
The drop-down box provides a selection for Spanish (Spain) Voice Alerts only. When selected, the web interface remains in default English.

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Server Settings for Emergency ResponderServerGroup

The Server Settings for Emergency ResponderServerGroup page appears when you choose System > Server Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Emergency Responder servers are inserted in the Emergency Responder group when the Emergency Responder services are started. (See Installation on a New System.)

Use the Server Settings for Emergency ResponderServerGroup page to update server settings, for example, to change the server name or to change the trace and debug settings, or to delete servers.

Note

You cannot modify the host name of the server.

The following table describes the Server Settings Emergency ResponderServerGroup page.

Server Settings for the Emergency ResponderServerGroup Page

Field

Description

Notes

Status

Displays the status of the Server Settings Emergency ResponderServerGroup page.

Select Server

Server

List of servers you have already created. Click on a server name to see the settings for that server.

You can configure a maximum of two servers per server group.

Modify Server Settings

Server Name

The name of the server.

Change this server name field to any desired value.

Host Name

The DNS name of the Emergency Responder server.

This field cannot be modified.

Debug Package List

A selection of subsystems for which you must collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Debug Package List.

Clear All button

Clears all selected subsystems in the Debug Package List.

Trace Package List

A selection of subsystems for which you must collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's 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.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Trace Package List.

Clear All button

Clears all selected subsystems in the Trace Package List.

Update Settings button

Click Update when viewing an existing server's settings to save changes you make to the settings.

Only available when viewing the settings of an existing server.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Upload License File

Cisco Prime License Manager maintains the licensing for Cisco Emergency Responder 10.0 and later.

Use the Prime License Manager tool to obtain licenses from Cisco, to install the licenses, and to manage and view your inventory of licenses. This tool also tracks license compliance or noncompliance.

Related References

License Manager

Related Information

Emergency Responder Licensing

Emergency Responder Licensing

Cisco Prime License Manager centralizes all of the licensing for Emergency Responder Release 10.0 and later releases.

Emergency Responder communicates the licensing requirements to Cisco Prime License Manager. Emergency Responder attempts to discover all phones on Unified Communications Manager, excluding subnets not tracked by Emergency Responder. Along with the manually configured phones, Emergency Responder builds and sends the corresponding license requirements to the Cisco Prime License Manager. The Cisco Prime License Manager then compares the Emergency Responder license requirements with the licenses installed and reports back license compliance or noncompliance.

For more information, refer to the Enterprise License Manager User Guide.

License Manager

The License Manager page appears when you choose System > License Manager.

Authorization Requirements

You must have system administrator authority to access this page.

Description

The License Manager Page provides the summary and detailed information on system license usage, as reported to the Prime License Manager.

License Manager Page

Field

Description

Status

Displays alarms or licensing alerts.

See License Manager Status Messages for further information on status messages. See License Compliance for further information on license compliance and noncompliance

Details of Emergency Responder Licenses

Displays the current license requirement for the server group:

- Number of phones discovered

- Number of phones manually configured

- Total number of users being tracked currently

Prime License Manager

Shows if the Prime License Manager manages the Emergency Responder Server Group.

If the Server Group has been added to an Prime License Manager product inventory, a link is provided to the Prime Collaboration License Manager server login page.

Emergency Responder must connect with the Prime License Manager at least once every 24 hours. This connection and communications of license requirements from the Emergency Responder and Prime License Manager is called synchronization.

The Enterprise License Manager status shows the time and date stamp of the last successful synchronization between the Emergency Responder and Prime License Manager.

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Related References

Cisco Unified Communications Manager Clusters

Cisco Unified Communications Manager Clusters

The Cisco Unified Communications Manager Clusters page appears when you choose Phone Tracking > Cisco Unified Communications Manager.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Cisco Unified Communications Manager Clusters page to identify the Cisco Unified Communications Manager clusters whose emergency calls this Emergency Responder group handles. Only assign a Cisco Unified Communications Manager cluster to a single Emergency Responder group. Emergency Responder gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones.

The following table describes the Cisco Unified Communications Manager Clusters page.

Cisco Unified Communications Manager Clusters Page

Field

Description

Notes

Add New Cisco Unified Communications Manager Cluster

Cisco Unified Communications Manager

The IP address or DNS name of a Cisco Unified Communications Manager server that is running Cisco Unified Communications Manager and SNMP services.

Only add one server per Cisco Unified Communications Manager cluster— Emergency Responder can identify the other servers in the cluster. The Cisco Unified Communications Manager server you specify represents the cluster in which it is a member.

When viewing a previously defined Cisco Unified Communications Manager server, Emergency Responder 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.

After the IP address or DNS name has been configured, it cannot be modified.

CTI Manager

The IP address or DNS name of the CTI Manager used by the specified Cisco Unified Communications Manager server.

CTI Manager User Name

The name of the user created in the Cisco Unified Communications Manager server for Emergency Responder use.

This user must have specific characteristics and device assignments. See Create Emergency Responder Cisco Unified Communications Manager User 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, Emergency Responder calls the onsite alert personnel for the originating ERL using the telephony ports you configure here.

You must first create this port in Cisco Unified Communications Manager. See Create Required CTI Ports for more information.

Number of Telephony Ports

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 Emergency Responder can make to onsite alert personnel.

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, Emergency Responder uses 3000, 3001, 3002, and 3003.

Enable Secure Connection

Enable Secure Connection check box

Check this check box to enable a secure connection. You can enter data in the other fields of this section only if you have enabled Secure Connection.

TFTP Server IP Address

The IP address of the TFTP server.

TFTP Server Port

The port of the TFTP server.

Backup TFTP Server IP Address

The IP address of the backup TFTP server, for the Unified CM node being added.

CAPF Server IP Address

The IP address of the CAPF server.

CAPF Server Port

The port of the CAPF server.

Instance ID for Publisher

The instance ID for the Publisher node.

Secure Authentication String for Publisher

The secure authentication string for the Publisher node.

Instance ID for Subscriber

The instance ID for the Subscriber node.

Secure Authentication String for Subscriber

The secure authentication string for the Subscriber node.

AXL Settings

AXL Username

The username for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Password

The password for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Port Number

The port number that is used by the application on Cisco Unified Communications Manger. The default value is 8443.

SNMP Settings

Use SNMPv3 for discovery

Check this check box if the Cisco Unified Communications Manager has SNMPv3 enabled and you want Emergency Responder to use SNMPv3 for discovery.

Insert button

Click Insert to add the new Cisco Unified Communications Manager server to the list of servers.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

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.

Cisco Unified Communications Manager Clusters

Add New button

Click Add New to add another Cisco Unified Communications Manager server.

Cisco Unified Communications Manager list

A list of Cisco Unified Communications Manager servers defined for this Emergency Responder group. Click a server link or the Edit icon to view and modify the Emergency Responder configuration for the server. Click the Delete icon to delete the server.

Set Up Emergency Responder Cluster and Cluster DB Host

Procedure

Step 1

Identify the following:

- All the Emergency Responder groups participating in the Emergency Responder cluster

- One of the Emergency Responder publishers as "Cluster DB Host"

- A password that is the same across the Cluster as "Cluster password"

Step 2

Using the Emergency Responder Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1.

Step 3

Repeat steps 1 and 2 for each Emergency Responder server group in the cluster.

Step 4

Restart Emergency Responder services.
Note:
Emergency Responder server groups can communicate with Emergency Responder 1.3, 2.x, 7.1 and 8.0 and later versions of Emergency Responder server groups in an Emergency Responder cluster.

Related Tasks

Update Emergency Responder Cluster Database Host Details

Related References

Update Cluster DB Host

Update Cluster DB Host

The Update Cluster DB Host page appears when you choose Update > Cluster DB Host.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Update Cluster DB Host page to designate a new server as the Emergency Responder cluster database host server.

The following table describes the Update Cluster DB Host page.

Update Cluster DB Host Page

Field

Description

Status

Displays the name of the current cluster database host

Cluster DB Host Details

ClusterDB Hostname/IP Address

Enter the hostname (if DNS is configured) or the IP address of the new cluster database host.

Note:
If the cluster is spread across domains, then enter a fully qualified hostname.

Password

Enter the password for the new cluster database host

Confirm Password

Reenter the password for the new cluster database host.

Go button

Click the Go button to designate the new server as the new cluster database host.

Note:
The Emergency Responder Cluster DB host details are updated. Emergency Responder services must be restarted for this change to take effect. You must restart Emergency Responder Services by rebooting the Emergency Responder publisher and subscriber servers. Only restarting Emergency Responder services does not work because the IP address is cached by other services and this updates the Emergency Responder Cluster DB host details for this server group only. Other servers in this Emergency Responder cluster are NOT updated automatically. For further details, see Update Emergency Responder Cluster Database Host Details.

Cancel button

Cancels the Update Cluster DB Host operation.

Update Emergency Responder Cluster Database Host Details

By default, each server in a cluster considers its own database to be the cluster database host. Because each cluster should have only one database host, you must update the cluster configuration accordingly.

For example, if you have two server groups (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. Update the cluster database host password for Servergroup A using Servergroup A's own host name.

2. Update the cluster database host password for Servergroup B by entering the IP address and cluster database password for Servergroup A.

3. Repeat Step 2 for other server groups 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 fails and cluster functionality is 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.

Note

This procedure only updates the Emergency Responder Cluster DB host details for this server group. Other servers in this Emergency Responder cluster do not updated automatically.

Before You Begin
You must reboot the server to update Emergency Responder Cluster DB host details. Only restarting Emergency Responder services does not work because the IP address is cached by other services.

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Select Update > Cluster DBHost from the main Emergency Responder Admin Utility page. The Update Cluster DB Host page appears.

Step 3

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.

Step 4

Enter the password for the new Cluster DBHost in the Password text box.

Step 5

Reenter the password for the new Cluster DBHost in the Confirm Password text box.

Step 6

Click Go.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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 Tasks

Export ERL Information

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

ERL Management

ERL Creation

Emergency Call Process

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Emergency Call Process

This topic describes the process that Cisco Emergency Responder (Emergency Responder) uses to handle emergency calls. Understanding this process can help you set up Emergency Responder correctly and troubleshoot problems that you might encounter.

The following figure illustrates how Emergency Responder routes an emergency call.

How Cisco Emergency Responder Routes Emergency Calls

When someone uses extension 3003 to make an emergency call:

1. Cisco Unified Communications Manager routes the call to Emergency Responder.

2. Emergency Responder gets the route pattern configured for the emergency response location (ERL) of the caller. See Call Routing Order for information about the order of call routing.

3. Emergency Responder converts the calling party number to the route pattern configured for the caller's 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 that the PSAP can use to call back the emergency caller.

4. Emergency Responder saves a mapping between the caller's 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.

5. Emergency Responder 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.

6. Concurrently, Emergency Responder sends web alerts to the Emergency Responder user. In addition, Emergency Responder calls the onsite alert (security) personnel assigned to the ERL. If you configure an email address for the personnel, Emergency Responder also sends an email. If the address is for an email-based paging service, the personnel get pages instead of emails.

7. 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 Emergency Responder, and Emergency Responder converts the ELIN to the last cached extension associated with the ELIN. The call is then routed to the extension.

To ensure proper performance and eliminate major points of failure, verify the following:

- For the emergency call to be routed correctly, the caller's 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 not routing the call correctly relates to the ELIN definition. If you assign the ELINs route pattern to the wrong gateway, the emergency call can be routed to the wrong network and the PSAP can receive the wrong emergency call.

Work with your service provider to determine how many gateways you need and where to connect them. These requirements are based on the service provider's network topology more than on your network's topology. In the United States, connecting to the PSTN does not ensure the correct routing of emergency calls.

- The call might be routed incorrectly in the service provider's 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. Emergency Responder 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 reaches the third caller, not the first caller. The likelihood of this problem arising depends on how many ELINs that you define for an ERL and the typical rate of emergency calls in the ERL.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Related References

Emergency Responder ERL Administrator Role

Related Information

ERLs

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

Emergency Responder ERL Administrator Role

The following table lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder ERL Administration Recurring Tasks

Recurring Task

Description

More Information

Assign ERLs to new or changed switch ports

If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.

Switch Port Configuration

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 Emergency Responder.

- ERL Creation

- Switch Port Configuration

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.

- Export ERL Information

- Export ALI Information for Submission to Your Service Provider

- ERL Creation

- ALI Submission and Service Provider Requirements

Audit the manually defined phones

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.

- Manually Define Phones

Audit the unlocated phones list

Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco Emergency Responder cannot locate the phones and to resolve the problems.

- Identify Unlocated Phones

- Unlocated Phones

Add new onsite personnel or remove old ones; update phone numbers

As onsite alert personnel are added, define them in Cisco Emergency Responder and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco Emergency Responder. Update phone numbers, email address, and other contact information as they change.

- Add Onsite Security Personnel

- ERL Creation

Add IP subnet for the IP subnets to be tracked

If there is a new IP subnet that needs to be discovered by Emergency Responder, then perform the following tasks:

- Configure an ERL spanning the new IP subnet's geographical location.

- Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL.

- Set Up IP Subnet-based ERLs

Set Up Default ERL

Emergency Responder 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 ERLs that are 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 Emergency Responder only if no other ERL is configured for that phone.

Emergency Responder also uses the default ERL for all emergency calls when the Emergency Responder server is first started (or restarted when there is no standby Emergency Responder server) until the initial switch port update is finished. (This process is started immediately.)

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

You must first configure the required ELINs in Unified CM.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find Conventional ERL Data page.

Step 2

Click Configure Default ERL.
Emergency Responder opens the ERL Information for Default window.

Step 3

Fill in the ERL Information for Default window.

Step 4

Click ALI Details.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Update ALI Info. Emergency Responder saves your ALI. Click Close to close the window.

Step 6

Make the ERL Information for Default window the active window if it is not, and click Update.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
Tip:
You cannot delete the default ERL. In addition, you cannot configure other ERLs unless the default ERL is configured.

Related Tasks

Set Up Individual ERL and Automatic Location Information (ALI)

Related References

Conventional ERL

Add New ERL

ALI Information

Related Information

ERLs

ERL Management

Conventional ERL

The Conventional ERL page appears when you choose ERL >Conventional ERL.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create are 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.

The following table describes the Find and List ERLs page.

Find and List ERLs Page

Field

Description

Notes

ERL Search Parameters

Find Conventional ERL where...

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:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL 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 is 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 remains there until it is modified.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Configure Default ERL

Click Configure Default ERL to configure a default ERL

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Add New ERL

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. If the ERL name is First Floor, the page that appears is titled ERL Information for First Floor.

The Add New ERL and ERL Information for ERL Name pages are essentially the same, as follows:

- The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL). 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 choose ERL > Conventional ERL).

Note

You cannot use a default ERLs as a Test ERL. The Test ERL check box is not available on the ERL Information for Default page.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this 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.

Emergency Responder allows you to select the ERL as a Test ERL.

Use the Find ERL Data page to view or update an existing ERL.

See ELIN Numbers Emergency Calls and PSAP Callbacks for information about configuring the ELIN numbers in Cisco Unified Communications Manager.

If you want to route emergency calls to onsite security instead of the PSAP, see Set Up ERLs for Non-PSAP Deployment for the Route/Translation Pattern and ELIN settings.

The following table describes the Add New ERL and ERL Information pages.

Add New ERL and ERL Information Pages

Field

Description

Notes

ERL Settings

ERL Name

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 sees 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 an ERL naming strategy.

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 are trimmed.

Description

Enter a description of the new ERL (optional).

Test ERL (Used for Synthetic Testing)

Check this check box if this ERL is used for testing.

See Set Up Test ERLs.

This setting is not available on the ERL Information for Default; default ERLs may not be used as test ERLs.

ELIN Settings

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 that 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 cannot 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.

Note:
Emergency Responder restricts the association of an ELIN with an ERL if the ELIN has been configured as a DID Number for an Off-Premises Emergency Responder user. Emergency Responder does not impose this restriction if the DID Number belongs to a user who has never associated an off-premises location in Emergency Responder.

Route/Translation Pattern

The phone number, defined as a route pattern in Cisco Unified Communications Manager, that is configured to use the gateway that 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.

ELIN Number

The unique phone number which the PSAP can use to locate a caller 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, for the North American Numbering Plan, such as 4085551212, or an E.164 Number including country code such as +14085551212. The number can only contain numbers, a plus sign (+), single hyphens, dots, or parentheses.

An ELIN when being sent as ANI to PSAP through outgoing Gateway must be a DID (direct inward dial) number provided by your service provider.

Add button

To add a route point and ELIN combination, enter the information and click Add.

Update button

To change an existing combination, select it in the list, change the information in the edit boxes, and click Update.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact's ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

ERL Address

ALI Details button

Click ALI Details to view or change the automatic location information (ALI) of an ERL. The ALI provides detailed information about the location of the ERL, such as street address and phone number.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 1 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 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 building (for example, the "170" in 170 West Tasman Dr.)

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

Street Name

The street name from the postal address for the building.

You are limited to 60 characters.

Prefix Directional

A leading directional indicator if the street name contains one, for example, N for North.

Can be one of these directions: N, S, E, W, NE, NW, SE, SW.

Street Suffix

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 can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions: N, S, E, W, NE, NW, SE, SW.

Community Name

The community name for the address, for example, a city, town, or district name.

You are limited to 32 characters.

State

The 2-digit state abbreviation.

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

You are limited to 7 characters.

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

You are limited to 4 characters. Ask your service provider for this identifier.

Customer Name

The subscriber name associated with the ERL, typically, your company name.

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

This is a read-only field.

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

You are limited to 4 characters.

Company ID

Your NENA-registered company identification code.

You are limited to 5 characters.

Zip Code

The postal zip code for the address.

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record.

U.S. Format: NNNNN or NNNNN-NNNN

Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These comments might be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

You are limited to 9 digits.

Latitude

The latitude of the ERL.

You are limited to 9 digits.

Elevation

The elevation of the ERL.

You are limited to 5 digits.

TAR Code

The taxing area rate code.

You are limited to 6 characters.

Location

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.

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

Ask your service provider if you must enter 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 Emergency Responder 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.

Update ALI Info button.

Click Update ALI Info to save your changes.

This button is only available when viewing a previously configured ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Close button

Click Close to close the window.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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 Tasks

Import Several ERLs

Related References

Conventional ERL

Add New ERL

ALI Information

Related Information

ERLs

ERL Management

Conventional ERL

The Conventional ERL page appears when you choose ERL >Conventional ERL.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create are 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.

The following table describes the Find and List ERLs page.

Find and List ERLs Page

Field

Description

Notes

ERL Search Parameters

Find Conventional ERL where...

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:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL 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 is 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 remains there until it is modified.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Configure Default ERL

Click Configure Default ERL to configure a default ERL

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Add New ERL

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. If the ERL name is First Floor, the page that appears is titled ERL Information for First Floor.

The Add New ERL and ERL Information for ERL Name pages are essentially the same, as follows:

- The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL). 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 choose ERL > Conventional ERL).

Note

You cannot use a default ERLs as a Test ERL. The Test ERL check box is not available on the ERL Information for Default page.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this 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.

Emergency Responder allows you to select the ERL as a Test ERL.

Use the Find ERL Data page to view or update an existing ERL.

See ELIN Numbers Emergency Calls and PSAP Callbacks for information about configuring the ELIN numbers in Cisco Unified Communications Manager.

If you want to route emergency calls to onsite security instead of the PSAP, see Set Up ERLs for Non-PSAP Deployment for the Route/Translation Pattern and ELIN settings.

The following table describes the Add New ERL and ERL Information pages.

Add New ERL and ERL Information Pages

Field

Description

Notes

ERL Settings

ERL Name

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 sees 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 an ERL naming strategy.

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 are trimmed.

Description

Enter a description of the new ERL (optional).

Test ERL (Used for Synthetic Testing)

Check this check box if this ERL is used for testing.

See Set Up Test ERLs.

This setting is not available on the ERL Information for Default; default ERLs may not be used as test ERLs.

ELIN Settings

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 that 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 cannot 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.

Note:
Emergency Responder restricts the association of an ELIN with an ERL if the ELIN has been configured as a DID Number for an Off-Premises Emergency Responder user. Emergency Responder does not impose this restriction if the DID Number belongs to a user who has never associated an off-premises location in Emergency Responder.

Route/Translation Pattern

The phone number, defined as a route pattern in Cisco Unified Communications Manager, that is configured to use the gateway that 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.

ELIN Number

The unique phone number which the PSAP can use to locate a caller 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, for the North American Numbering Plan, such as 4085551212, or an E.164 Number including country code such as +14085551212. The number can only contain numbers, a plus sign (+), single hyphens, dots, or parentheses.

An ELIN when being sent as ANI to PSAP through outgoing Gateway must be a DID (direct inward dial) number provided by your service provider.

Add button

To add a route point and ELIN combination, enter the information and click Add.

Update button

To change an existing combination, select it in the list, change the information in the edit boxes, and click Update.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact's ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

ERL Address

ALI Details button

Click ALI Details to view or change the automatic location information (ALI) of an ERL. The ALI provides detailed information about the location of the ERL, such as street address and phone number.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

Import Several ERLs

Rather than defining ERLs one at a time, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Prepare an import file. Emergency Responder 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 to import it.

You can import conventional, off-premise, or Intrado ERLs. Click the Import link in the upper-right corner of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Use the following procedure to view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL data page, Find Off-Premises ERLs data page, or the Find Intrado ERLs data page), click Import.
Emergency Responder opens the Import ERL data page.

Step 2

Select the format of your import file (csv or xml) from the pull-down menu.

Step 3

Click Upload to upload the file from your local machine.

Step 4

Select your import file.

Step 5

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 6

Click Close to close the Import ERL Data window.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Import Several ERLs

Rather than defining ERLs one at a time, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Prepare an import file. Emergency Responder 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 to import it.

You can import conventional, off-premise, or Intrado ERLs. Click the Import link in the upper-right corner of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Use the following procedure to view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL data page, Find Off-Premises ERLs data page, or the Find Intrado ERLs data page), click Import.
Emergency Responder opens the Import ERL data page.

Step 2

Select the format of your import file (csv or xml) from the pull-down menu.

Step 3

Click Upload to upload the file from your local machine.

Step 4

Select your import file.

Step 5

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 6

Click Close to close the Import ERL Data window.

Related Tasks

Set Up Individual ERL and Automatic Location Information (ALI)

Related References

Import ERL Data

Related Information

ERLs

ERL Management

Upload File

ERL Creation

Set Up Off-Premise ERL

Set Up Intrado ERLs

Import ERL Data

The Import ERL Data page appears when you click the Import link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import ERL Data page.

Import ERL Data Page

Field

Description

Select Import Format

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

Select the file from which you want to import ERL data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add ERL data from the import file to the Emergency Responder database.

Note:
The imported ERL data overwrites conflicting data in the Emergency Responder database.

Close button

Click Close to close the window.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. The "ALI Information section", Cisco Emergency Responder Administration Web Interface Appendix A, contains detailed explanations of each field. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Convert ALI Data

Use the PS-ALI Converter tool to generate an ERL csv (Comma Separated Value) text file that can be accepted by the Emergency Responder ERL. You must first upload an existing ALI file in NENA 2.0 format to Emergency Responder before converting it.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

To convert ALI data, follow these steps:

Procedure

Step 1

Select Tools > PS-ALI Converter.
Emergency Responder displays the PS-ALI Converter page.

Step 2

Click the Upload PSALI file button to upload an ERL file in NENA 2.0 format. The Upload File page appears.

Step 3

Follow the instructions in the Upload File to upload the ERL file.

Step 4

Select the uploaded file from pulldown menu.

Step 5

In the Output file (in csv format) Name field, enter the name of the converted csv file you want to create.

Step 6

Click Convert to create the csv file.
The generated csv file is in the following folder:

%cerroot%/import
You can import the file or download the file using the File Manager utility.

Step 7

Modify the converted csv file as needed. For example, add the ERL name, route pattern, and security details to update the ERL.

Step 8

Click Close to close the window.

Related Tasks

Set Up Individual ERL and Automatic Location Information (ALI)

Related References

Import ERL Data

Related Information

ERLs

ERL Management

Import ERL Data

The Import ERL Data page appears when you click the Import link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import ERL Data page.

Import ERL Data Page

Field

Description

Select Import Format

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

Select the file from which you want to import ERL data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add ERL data from the import file to the Emergency Responder database.

Note:
The imported ERL data overwrites conflicting data in the Emergency Responder database.

Close button

Click Close to close the window.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Set Up IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Emergency Responder supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco Emergency Responder then routes the emergency calls based on the configured IP subnet and ERL associations.

This feature is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.

Use IP subnet-based ERLs to locate and track wireless endpoints, such as Cisco Unified Wireless IP Phone 7920 series devices and Cisco clients using wireless IP connection. Cisco Emergency Responder cannot locate or track wireless endpoints to a Cisco Access Point.

Note

Subnet-based tracking is limited by the IP subnet addressing plan. It cannot distinguish location within a same IP Subnet.

Before You Begin
You must have system administrator or ERL administrator authority to access this page.

Procedure

Step 1

Select ERL Membership > IP subnets and click the Add new IP subnet link on the Find and List IP Subnets page.
Emergency Responder opens the Configure IP Subnets page.

Step 2

At the Subnet ID field, enter the IP address of the subnet that you want to define, for example,10.76.35.0.

Step 3

At the Subnet Mask field, enter the mask of the subnet that you want to define, for example, 255.255.255.224.

Step 4

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.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the subnet and click Select ERL. The Find ERL page closes.

Step 7

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

To change the fields on this page back to the last saved settings, click Cancel Changes.

Step 9

To return to the Find and List IP Subnets page, click Back to IP Subnet Search.

Related References

Find and List Synthetic Phones

Add New Synthetic Phone

Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you choose ERL Membership > Synthetic Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Synthetic Phones page.

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 pull-down 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 are displayed from the pull-down 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 Add New Synthetic Phone 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, choose 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.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Synthetic Phone page to manually define a synthetic phone ERL. You must configure synthetic phones in the subnet for testing ERL configurations.

For synthetic phones, Emergency Responder cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure that they are correct.

The following table describes the Add New Synthetic Phone page.

Add New Synthetic Phone Page

Field

Description

Notes

MAC Address

The MAC address of the synthetic phone, or a range of MAC addresses.

The synthetic MAC address must be within the 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.

Insert button

Click Insert to add the synthetic phone to the list of phones.

The Insert button only appears when you are adding a phone.

New button

Click New to add another phone.

The New button only appears when you are viewing an existing phone.

Update button

Click Update when viewing an existing phone to save changes you make to the phone.

The Update button only appears when you are viewing an existing phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Set Up Test ERLs

You can use Cisco Unified Operations Manager to monitor the health and functionality of Emergency Responder.

To use Cisco Unified Operations Manager with Emergency Responder, you configure a test ERL for conventional ERLs, then add a synthetic phone and associate the synthetic phone to the test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can configure test ERLs only to synthetic phones.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

All synthetic phones used for Emergency Responder 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 are not logged in Call History logs.

- Web alerts are not generated for emergency calls from synthetic phones.

- Email alerts are not generated for emergency calls from synthetic phones.

- PS-ALI records for test ERLs are not 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.

Procedure

Step 1

Select ERL > Conventional ERL and click Add New ERL on the ERL Configuration page.

Step 2

At the ERL field, enter a name for the test ERL.

Step 3

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.

Step 4

Click Insert to save the test ERL and click Close to close the window.

Step 5

Select ERL Membership > Synthetic Phones and click Add New Synthetic phone on the Find and List Synthetic Phones page.

Step 6

In 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

Step 7

In 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.

Step 8

Click Insert to add the phone to the list of defined synthetic phones.

Step 9

To change the fields on this page back to the last saved settings, click Cancel Changes.

Related References

Find and List Synthetic Phones

Add New Synthetic Phone

Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you choose ERL Membership > Synthetic Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Synthetic Phones page.

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 pull-down 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 are displayed from the pull-down 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 Add New Synthetic Phone 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, choose 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.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Synthetic Phone page to manually define a synthetic phone ERL. You must configure synthetic phones in the subnet for testing ERL configurations.

For synthetic phones, Emergency Responder cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure that they are correct.

The following table describes the Add New Synthetic Phone page.

Add New Synthetic Phone Page

Field

Description

Notes

MAC Address

The MAC address of the synthetic phone, or a range of MAC addresses.

The synthetic MAC address must be within the 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.

Insert button

Click Insert to add the synthetic phone to the list of phones.

The Insert button only appears when you are adding a phone.

New button

Click New to add another phone.

The New button only appears when you are viewing an existing phone.

Update button

Click Update when viewing an existing phone to save changes you make to the phone.

The Update button only appears when you are viewing an existing phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Related References

Export ERL Data

Related Information

ERLs

ERL Management

ERL Creation

Set Up Off-Premise ERL

Set Up Intrado ERLs

Export ERL Data

The Export ERL Data page appears when you click the Export link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder server.

To create a file to send to your service provider to update their ALI data, see Export PS-ALI Records.

The following table describes the Export ERL Data page.

Export ERL Data Page

Field

Description

Select Export Format

The file format to be used in the export file. For ERL data, either csv (comma-separated value) or XML.

Enter Export File Name

The name of the file you want to create. Do not include a file extension.

Export button

Click Export to create the export file.

Close button

Click Close to close the window.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. The "ALI Information section", Cisco Emergency Responder Administration Web Interface Appendix A, contains detailed explanations of each field. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Switch-Port Change Reporting for Wired Cisco Unified IP Phones

Emergency Responder 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. Emergency Responder notifies the system administrator of these changes by email.

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 Emergency Responder. Cisco Unified IP Phones that appear on the Unlocated Phones page in Emergency Responder 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 Emergency Responder.

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 extensions.

Procedure

Step 1

Select System > Mail Alert Configurations.
The Email Alert Settings page appears.

Step 2

In the Misc parameters section, check the check box to the right of Switch Port location change reporting parameter to enable or disable email alerts. Check the Include event viewer contents in mail check box if you want to include the details from the event viewer in the email message.

Step 3

Click Update Settings.

What to Do Next

Note

Configure the email client settings to allow line breaks in the email to improve readability.

Supported Cisco Unified IP Phones—This 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 Unified CM. The only exception for this rule is Cisco Unified IP Phones previously registered in Unified CM. These Cisco Unified IP Phones are reported as missing.

Cluster Scenario—The active server in each server group within a cluster sends separate notifications for the Cisco Unified IP Phones it discovers and tracks.

Server Group Scenario—Within a server group, Emergency Responder performs change detection and notification on the active Emergency Responder server only.

Feature Activation—The change detection and notification feature requires manual activation.

Change Notification conditions - Emergency Responder 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 Emergency Responder Administrator web interface.

- Because of a Unified CM 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.

- Because of a LAN switch addition to Emergency Responder the system administrator starts the discovery process.

- Because 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 Unified CM 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 Emergency Responder Server 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.

Related References

Set Up a Server Group

Set Up a Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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, 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada) or Spanish(Spain), select it in the drop-down box. The default language is English(US).

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

Related References

ALI Information

Export ERL Data

Export PS-ALI Records

Related Information

ERLs

ERL Management

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

Export ERL Data

The Export ERL Data page appears when you click the Export link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder server.

To create a file to send to your service provider to update their ALI data, see Export PS-ALI Records.

The following table describes the Export ERL Data page.

Export ERL Data Page

Field

Description

Select Export Format

The file format to be used in the export file. For ERL data, either csv (comma-separated value) or XML.

Enter Export File Name

The name of the file you want to create. Do not include a file extension.

Export button

Click Export to create the export file.

Close button

Click Close to close the window.

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

View Audit Trail for 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.

Procedure

Step 1

Select Reports > ERL Audit Trail.
Emergency Responder opens the ERL Audit Trail page.

Step 2

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:

1. Select the field that 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.

2. 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).

3. Click Find when you have entered all of the search criteria.
Emergency Responder lists the matching audit records. If there are a lot of matches, Emergency Responder uses several pages to display them. Use the links at the bottom of the list to change pages.

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 References

ERL Audit Trail

Related Information

Work with Emergency Responder Locations

ERL Audit Trail

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

- Choose Reports > ERL Audit Trail.

- Click view in the Audit Trail column for an ERL displayed on the ERL Configuration page (opened by choosing ERL > Conventional ERL.)

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the ERL Audit Trail page to view the change history for ERLs.

The following table describes the ERL Audit Trail page.

ERL Audit Trail Page

Field

Description

ERL Audit Trail

Search criteria

Enter search criteria to select the audit details that 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 pull-down menu, select the field that 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 pull-down 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:

- ERL Name—The name of the ERL that was changed.

- Modified By—The login ID of the user who changed the ERL.

- Modified Time—The date and time the ERL was changed.

- Modification Details—A 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.

Note:
If there are a large number of records match your search, Emergency Responder 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.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Related Tasks

Set Up SNMPv2

Define Phone Tracking and Switch Update Schedules

Manually Run the Switch-Port and Phone Update Process

Related Information

LAN Switch Identification

Set Up SNMPv2

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 define in Emergency Responder. If you use different strings for different sets of switches, determine whether 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.*.*.

If two or more patterns match an IP address, Emergency Responder 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, Emergency Responder uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

Procedure

Step 1

Select Phone Tracking > SNMPv2 Settings.
Emergency Responder opens the SNMP Settings page.

Step 2

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 Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see LAN Switch Identification for more information), it does not matter if the IP address patterns cover devices other than switches.

- If all of your switches use the same read community string, enter *.*.*.*. You 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 Emergency Responder 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, Emergency Responder 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.

Step 4

Enter the read community string, for example, public.

Step 5

Click Insert.
Emergency Responder adds the SNMP setting to the list of settings.

Step 6

If you must create more than one setting, return to Step 2.
If you change the SNMP read community string on a switch, you must update the associated setting in Emergency Responder:

- To change an SNMP setting, select it in the list. Emergency Responder 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 setting's entry.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Set Up SNMP Connection

Emergency Responder uses SNMP to obtain information about the ports on a switch. Emergency Responder must obtain this port information so that you can assign the ports to ERLs, and so that Emergency Responder can identify phones that are attached to the ports and update their ERL assignments.

Emergency Responder only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.

When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Unified CM servers. Emergency Responder must be able to make SNMP queries of all Unified CM servers in the cluster that it supports.

If your Cisco Emergency Responder servers, Unified CM servers, and Cisco IP Phones are in a different subnet than your switches, you must either configure both the subnets for the servers and phones as well as the subnet for the switches or use *.*.*.*.

Related References

SNMP Settings

Related Information

LAN Switch Identification

SNMP Settings

The SNMP Settings page appears when you choose Phone Tracking > SNMPv2 Settings or Phone Tracking > SNMPv3 Settings.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the SNMPv2 Settings page or the SNMPv3 Settings page to define the SNMP read community string used by your switches.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Set Up SNMPv3

Procedure

Step 1

Select Phone Tracking > SNMPv3 Settings.
Emergency Responder opens the SNMPv3 Settings page.

Step 2

Enter the User information for which you want to provide access.
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.

Step 3

To require authentication, check the Authentication Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 4

If you checked the Authentication Required check box, you can specify privacy information. To require privacy, check the Privacy Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 5

Enter the timeout and retries values.
These values work together to determine how often and how long Emergency Responder 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, Emergency Responder 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.

The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.

Step 6

Click Insert.

Step 7

If you must create more than one setting, return to Step 2.
Whenever you change the SNMPv3 settings on a switch or Unified CM server, you must update the associated setting in Emergency Responder:

- To change an SNMPv3 setting, select it in the list. Emergency Responder 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 SNMPv3 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 setting's entry.

Related References

SNMP Settings

Related Information

LAN Switch Identification

SNMP Settings

The SNMP Settings page appears when you choose Phone Tracking > SNMPv2 Settings or Phone Tracking > SNMPv3 Settings.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the SNMPv2 Settings page or the SNMPv3 Settings page to define the SNMP read community string used by your switches.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

Related Tasks

Manually Run the Switch-Port and Phone Update Process

Related References

Phone Tracking Schedule

Phone Tracking Schedule

The Phone Tracking Schedule page appears when you choose Phone Tracking > Schedule.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Phone Tracking Schedule page to define the Cisco Emergency Responder (Emergency Responder) schedule for updating phone and switch information from the network. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Cisco Unified Communications Manager to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone ERL.

- Switch Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Ensure that your ERL administrator updates the ERL assignment for new ports.

The following table describes the Phone Tracking Schedule page.

Phone Tracking Schedule Page

Field

Description

Notes

Incremental Phone Tracking

Incremental Phone Tracking Interval

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.

The default is 30 minutes.

The range of the interval that can be defined is 5 to 300 minutes.

Add New Schedule

Enter the schedule that you want to add:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

We recommend that you run the switch port and phone update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Insert button

Click Insert to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes that you make to the schedule.

Only available when viewing an existing schedule.

Switch-Port and Phone Update Schedule

The list of schedules you have defined.

To change a schedule, click the Hour link, the Minute 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.

If any schedules overlap, only one schedule is run.

Add New button

Click Add New to add another schedule.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Identify LAN Switches One at a Time

You can enter switches into the Emergency Responder 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 Import a Group of Switches for more information.

Before You Begin
You must have system administrator or network administrator authority to add, remove, or change switch definitions.

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, Emergency Responder must use the CAM information about the switch to identify phones. See Network Hardware and Software Requirements for information about which phones require CAM access.

Ensure that you configure the SNMP read community strings before adding switches. See Set Up SNMPv2 for more information.

Note

Emergency Responder performs a full discovery scan for all the switches when you either reboot the Emergency Responder server or while upgrading to a higher version. This process can be time consuming, depending on network size and number of switches.

Note

Always delete the LAN Switches from Emergency Responder Administration > Phone Tracking > LAN Switch Details, if this has been removed from the network.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Enter information about the switch:

- 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.

- If you want to display the switch port descriptions that are configured on the switch in the locations field in Emergency Responder, select Use port description as port location.

Step 3

Click Insert to add the switch to the Emergency Responder configuration.
Emergency Responder asks if you want to run the switch port and phone update process. You must run this process so that Emergency Responder 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, Emergency Responder 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.

Note:
Emergency Responder expects only one IP address or hostname per chassis and needs access to the following MIBs:

- mib-2

- IF-MIB

- CISCO-CDP-MIB

- ENTITY-MIB

- CISCO-VLAN-MEMBERSHIP-MIB

- RIDGE-MIB*

- CISCO-STACK-MIB

- Mib-2

- interface

- CISCO-2900-MIB

Click a switch in the LAN Switches list to view the switch's Emergency Responder 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 switch's 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, Emergency Responder identifies any phones connected to the switch as unlocated phones.

Related Tasks

Import a Group of Switches

Export Switch Information

Related References

LAN Switch Details

Related Information

Switch Requirements for Emergency Responder

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

Related Tasks

Identify LAN Switches One at a Time

Export Switch Information

Related References

LAN Switch Details

Related Information

Switch Requirements for Emergency Responder

Identify LAN Switches One at a Time

You can enter switches into the Emergency Responder 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 Import a Group of Switches for more information.

Before You Begin
You must have system administrator or network administrator authority to add, remove, or change switch definitions.

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, Emergency Responder must use the CAM information about the switch to identify phones. See Network Hardware and Software Requirements for information about which phones require CAM access.

Ensure that you configure the SNMP read community strings before adding switches. See Set Up SNMPv2 for more information.

Note

Emergency Responder performs a full discovery scan for all the switches when you either reboot the Emergency Responder server or while upgrading to a higher version. This process can be time consuming, depending on network size and number of switches.

Note

Always delete the LAN Switches from Emergency Responder Administration > Phone Tracking > LAN Switch Details, if this has been removed from the network.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Enter information about the switch:

- 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.

- If you want to display the switch port descriptions that are configured on the switch in the locations field in Emergency Responder, select Use port description as port location.

Step 3

Click Insert to add the switch to the Emergency Responder configuration.
Emergency Responder asks if you want to run the switch port and phone update process. You must run this process so that Emergency Responder 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, Emergency Responder 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.

Note:
Emergency Responder expects only one IP address or hostname per chassis and needs access to the following MIBs:

- mib-2

- IF-MIB

- CISCO-CDP-MIB

- ENTITY-MIB

- CISCO-VLAN-MEMBERSHIP-MIB

- RIDGE-MIB*

- CISCO-STACK-MIB

- Mib-2

- interface

- CISCO-2900-MIB

Click a switch in the LAN Switches list to view the switch's Emergency Responder 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 switch's 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, Emergency Responder identifies any phones connected to the switch as unlocated phones.

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

Related Tasks

Identify LAN Switches One at a Time

Import a Group of Switches

Related References

LAN Switch Details

Related Information

Switch Requirements for Emergency Responder

Identify LAN Switches One at a Time

You can enter switches into the Emergency Responder 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 Import a Group of Switches for more information.

Before You Begin
You must have system administrator or network administrator authority to add, remove, or change switch definitions.

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, Emergency Responder must use the CAM information about the switch to identify phones. See Network Hardware and Software Requirements for information about which phones require CAM access.

Ensure that you configure the SNMP read community strings before adding switches. See Set Up SNMPv2 for more information.

Note

Emergency Responder performs a full discovery scan for all the switches when you either reboot the Emergency Responder server or while upgrading to a higher version. This process can be time consuming, depending on network size and number of switches.

Note

Always delete the LAN Switches from Emergency Responder Administration > Phone Tracking > LAN Switch Details, if this has been removed from the network.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Enter information about the switch:

- 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.

- If you want to display the switch port descriptions that are configured on the switch in the locations field in Emergency Responder, select Use port description as port location.

Step 3

Click Insert to add the switch to the Emergency Responder configuration.
Emergency Responder asks if you want to run the switch port and phone update process. You must run this process so that Emergency Responder 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, Emergency Responder 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.

Note:
Emergency Responder expects only one IP address or hostname per chassis and needs access to the following MIBs:

- mib-2

- IF-MIB

- CISCO-CDP-MIB

- ENTITY-MIB

- CISCO-VLAN-MEMBERSHIP-MIB

- RIDGE-MIB*

- CISCO-STACK-MIB

- Mib-2

- interface

- CISCO-2900-MIB

Click a switch in the LAN Switches list to view the switch's Emergency Responder 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 switch's 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, Emergency Responder identifies any phones connected to the switch as unlocated phones.

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Related Tasks

Define Phone Tracking and Switch Update Schedules

Identify Unlocated Phones

Related Information

Switch Requirements for Emergency Responder

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Track Change of Switch IP Address Dynamically

Emergency Responder allows you to dynamically track the change in a LAN switch IP address managed by Emergency Responder. This feature is intended for LAN switches that have been added using the switch hostname.

Before You Begin
You must have system administrator authority to enable dynamic tracking of a LAN switch IP address.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select the Dynamic Tracking of Switch IP Address check box to dynamically track a switch's IP address.

Step 3

Click the Update Settings button to apply the change.
You must wait for the next Incremental Discovery cycle to start. During this cycle Emergency Responder detects the new IP address of the LAN switch and updates its database. You will be notified of this change detection from an entry in the Emergency Responder Event Viewer and with an administrative email alert.

Note:
It is recommended that you enable Dynamic Tracking of Switch IP Address only during a scheduled maintenance window when the switch is subject to an actual change of IP address. It is recommended that you disable this option during normal periods as this operation is CPU intensive.

Note:
For a LAN switch that has been added using the IP address, Emergency Responder cannot track any change in its IP address. In this case, you must delete the switch and add it again with the new IP address.

Related Tasks

Define Phone Tracking and Switch Update Schedules

Related References

Group Settings

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page—English or French (Canadian).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

Set Up Individual Switch Ports

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 Set Up Large Number of Ports 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 Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports.
Emergency Responder opens the Switch Port Details page.

Step 2

Enter search criteria to list the ports that you want to configure.

- Find displays a maximum of 1,000 records. Refine your search accordingly. To limit the number of ports that are displayed, check the check box next to Collapse search results. The search displays the IP address or name of the switches found. To display all ports associated with a switch and display the expanded view, click the + button next to the switch. To display just the switch and collapse the list, click the - button next to the switch.

- 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. Emergency Responder lists all ports discovered on the switch.

- If you want to narrow your search by using multiple criteria, click the + button 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 Emergency Responder group that 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 Emergency Responder group. You can only search one Emergency Responder group at a time.
Note:
Emergency Responder remembers the previous search criteria for the login session.

Step 3

Assign ports to ERLs:

1. Check the check box next to the switch port that you want to assign an ERL.
If you want to assign all listed ports for a switch, select the check box for that switch. 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.

2. Select the ERL you want to assign to the ports.

3. 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 Emergency Responder server in the Emergency Responder group.

4. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

5. Enter the ERL Search Parameters and click Find. The search results appear.

6. Click the radio button next to the ERL that you want to assign to the switch ports and click Select ERL. The Find ERL page closes.

7. Click Assign ERL.
Emergency Responder 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.

Emergency Responder commits your ERL assignments. From here, you can continue to the other page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.

Click Edit View to change the fields and arrangement of fields in the port list. If you want to revert to the standard view, then click Restore Defaults.

The phone location information is saved on the primary Emergency Responder server. Back up this data regularly.

Related Tasks

Set Up Large Number of Ports

Export Switch Port Information

Related References

Switch Port Details

Import Switch Ports

Related Information

Work with Emergency Responder Locations

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Import Switch Ports

The Import Switch Ports page appears when you click Import in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Import Switch Ports page to add or update several switch port configurations at once to the Emergency Responder configuration. Switch port configurations are mappings of ports to ERLs.

To create the switch port import file, follow these steps:

1. Export the switch port details.

2. Modify the ERK field of these records and save the file.

3. 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 Upload File for more information.

The following table describes the Import Switch Ports page.

Import Switch Ports Page

Field

Description

Select Import Format

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 Emergency Responder, modify the export file using a spreadsheet program, and then import the modified file.

Note:
See Export Switch Port Information for information about exporting switch port information.

Select File to Import

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the information in the import file to your Emergency Responder configuration. ERL assignments in the import file override assignments that already exist in the Emergency Responder configuration.

Note:
Port ERL configurations are only updated if Emergency Responder has discovered the port before you import the port configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Related Tasks

Set Up Individual Switch Ports

Export Switch Port Information

Related References

Switch Port Details

Export Switch Ports

Related Information

Switch Requirements for Emergency Responder

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Export Switch Ports

The Export Switch Ports page appears when you click Export in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports ).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Switch Ports page to create a file containing the Emergency Responder switch port configuration.

If you must 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 Download File for more information.

The following table describes the Export Switch Ports page.

Export Switch Ports Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma-separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Set Up Individual Switch Ports

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 Set Up Large Number of Ports 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 Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports.
Emergency Responder opens the Switch Port Details page.

Step 2

Enter search criteria to list the ports that you want to configure.

- Find displays a maximum of 1,000 records. Refine your search accordingly. To limit the number of ports that are displayed, check the check box next to Collapse search results. The search displays the IP address or name of the switches found. To display all ports associated with a switch and display the expanded view, click the + button next to the switch. To display just the switch and collapse the list, click the - button next to the switch.

- 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. Emergency Responder lists all ports discovered on the switch.

- If you want to narrow your search by using multiple criteria, click the + button 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 Emergency Responder group that 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 Emergency Responder group. You can only search one Emergency Responder group at a time.
Note:
Emergency Responder remembers the previous search criteria for the login session.

Step 3

Assign ports to ERLs:

1. Check the check box next to the switch port that you want to assign an ERL.
If you want to assign all listed ports for a switch, select the check box for that switch. 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.

2. Select the ERL you want to assign to the ports.

3. 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 Emergency Responder server in the Emergency Responder group.

4. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

5. Enter the ERL Search Parameters and click Find. The search results appear.

6. Click the radio button next to the ERL that you want to assign to the switch ports and click Select ERL. The Find ERL page closes.

7. Click Assign ERL.
Emergency Responder 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.

Emergency Responder commits your ERL assignments. From here, you can continue to the other page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.

Click Edit View to change the fields and arrangement of fields in the port list. If you want to revert to the standard view, then click Restore Defaults.

The phone location information is saved on the primary Emergency Responder server. Back up this data regularly.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Switch Requirements for Emergency Responder

Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder 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, Emergency Responder tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The Network Hardware and Software Requirements lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Related Tasks

Set Up Individual Switch Ports

Set Up Large Number of Ports

Related References

Switch Port Details

Related Information

Work with Emergency Responder Locations

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Set Up Individual Switch Ports

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 Set Up Large Number of Ports 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 Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports.
Emergency Responder opens the Switch Port Details page.

Step 2

Enter search criteria to list the ports that you want to configure.

- Find displays a maximum of 1,000 records. Refine your search accordingly. To limit the number of ports that are displayed, check the check box next to Collapse search results. The search displays the IP address or name of the switches found. To display all ports associated with a switch and display the expanded view, click the + button next to the switch. To display just the switch and collapse the list, click the - button next to the switch.

- 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. Emergency Responder lists all ports discovered on the switch.

- If you want to narrow your search by using multiple criteria, click the + button 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 Emergency Responder group that 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 Emergency Responder group. You can only search one Emergency Responder group at a time.
Note:
Emergency Responder remembers the previous search criteria for the login session.

Step 3

Assign ports to ERLs:

1. Check the check box next to the switch port that you want to assign an ERL.
If you want to assign all listed ports for a switch, select the check box for that switch. 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.

2. Select the ERL you want to assign to the ports.

3. 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 Emergency Responder server in the Emergency Responder group.

4. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

5. Enter the ERL Search Parameters and click Find. The search results appear.

6. Click the radio button next to the ERL that you want to assign to the switch ports and click Select ERL. The Find ERL page closes.

7. Click Assign ERL.
Emergency Responder 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.

Emergency Responder commits your ERL assignments. From here, you can continue to the other page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.

Click Edit View to change the fields and arrangement of fields in the port list. If you want to revert to the standard view, then click Restore Defaults.

The phone location information is saved on the primary Emergency Responder server. Back up this data regularly.

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Related Tasks

Manually Define Phones

Related Information

IP Subnet Phones

Switch Port Configuration

IP Subnet Phones

The IP Subnet Phones page appears when you choose ERL Membership/ IP Subnets and click the View Phones icon in any records returned by the IP Subnet Search.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the IP subnet Phones page to view all the IP subnet phones discovered by Emergency Responder.

The IP subnet phones page displays the subnet ID, the subnet mask for each IP subnet and lists all the phones tracked in that IP subnet, and when the last phone was tracked.

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Related Tasks

Identify Unlocated Phones

Assign Large Number of Manually Configured Phones to ERLs

Export Manually Configured Phone Information

Related References

Add New Manual Phone

Related Information

Network Hardware and Software Requirements

Add New Manual Phone

To reach the Add New Manual Phone page, choose 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.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Manual Phone page to manually define a phone ERL. You must manually define a phone if any of these conditions apply:

- Emergency Responder cannot automatically track the type of phone, for example, if the phone is analog. See Network Hardware and Software Requirements for information about 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, Emergency Responder cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure that they are correct.

The following table describes the Add New Manual Phone page.

Add New Manual Phone Page

Field

Description

Add New Manual Phone

Line Number

The extension of the phone you want to define.

MAC Address

The MAC address of the phone, if it is an IP phone.

IP Address

The IP address of the phone, if it is an IP phone.

Phone Type

The type of phone, such as analog. This field is for your information only.

Version

The version of the phone software, if any. This field is for your information only.

Location

The location of the phone.

ERL Name

The ERL that you want to assign to the phone. To find and select the ERL, click Search ERL.

Insert button

Click Insert to add the phone to the list of phones.

Note:
The Insert button only appears when you are adding a phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Network Hardware and Software Requirements

Emergency Responder 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  located at Click Here .

Assign Large Number of Manually Configured Phones to ERLs

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 a 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 Emergency Responder (see Export Manually Configured Phone Information), 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 following procedure explains how to get to this page. Links on the page also display the detailed information about the required file format for the import file if you need it.

Emergency Responder 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 Emergency Responder.

You can only configure manually configured phones defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
The Find and List Manually Configured Phones page appears.

Step 2

Click Import.
The Import Manually Configured Phones page appears.

Step 3

Select the Import Format (csv) using the pull-down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select the import file using the Select File to Import pull-down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Manually Configured Phone page.

Export Manually Configured Phone Information

You can export your Emergency Responder manually configured phone configuration. By exporting this information, you can back up your data or create a file that you can use to update a large number of manually configured phone mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens the Find and List Manually Configured Phones page.

Step 2

Click Export.
Emergency Responder opens the Export Manual Phones page.

Step 3

Select the export format (csv) from the Select Export Format pulldown menu.

Step 4

Enter the desired file name in the Enter Export File Name field and click Export.
Emergency Responder exports the file to the export location.

Step 5

To download the exported file to your local system, select the file name from the Select file to download pulldown menu and click Download.

Step 6

Click Close to close the Export Manual Phones page.

Assign Large Number of Manually Configured Phones to ERLs

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 a 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 Emergency Responder (see Export Manually Configured Phone Information), 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 following procedure explains how to get to this page. Links on the page also display the detailed information about the required file format for the import file if you need it.

Emergency Responder 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 Emergency Responder.

You can only configure manually configured phones defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
The Find and List Manually Configured Phones page appears.

Step 2

Click Import.
The Import Manually Configured Phones page appears.

Step 3

Select the Import Format (csv) using the pull-down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select the import file using the Select File to Import pull-down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Manually Configured Phone page.

Related Tasks

Set Up Individual Switch Ports

Export Switch Port Information

Related References

Switch Port Details

Export Switch Ports

Related Information

Work with Emergency Responder Locations

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Export Switch Ports

The Export Switch Ports page appears when you click Export in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports ).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Switch Ports page to create a file containing the Emergency Responder switch port configuration.

If you must 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 Download File for more information.

The following table describes the Export Switch Ports page.

Export Switch Ports Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma-separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Set Up Individual Switch Ports

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 Set Up Large Number of Ports 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 Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports.
Emergency Responder opens the Switch Port Details page.

Step 2

Enter search criteria to list the ports that you want to configure.

- Find displays a maximum of 1,000 records. Refine your search accordingly. To limit the number of ports that are displayed, check the check box next to Collapse search results. The search displays the IP address or name of the switches found. To display all ports associated with a switch and display the expanded view, click the + button next to the switch. To display just the switch and collapse the list, click the - button next to the switch.

- 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. Emergency Responder lists all ports discovered on the switch.

- If you want to narrow your search by using multiple criteria, click the + button 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 Emergency Responder group that 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 Emergency Responder group. You can only search one Emergency Responder group at a time.
Note:
Emergency Responder remembers the previous search criteria for the login session.

Step 3

Assign ports to ERLs:

1. Check the check box next to the switch port that you want to assign an ERL.
If you want to assign all listed ports for a switch, select the check box for that switch. 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.

2. Select the ERL you want to assign to the ports.

3. 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 Emergency Responder server in the Emergency Responder group.

4. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

5. Enter the ERL Search Parameters and click Find. The search results appear.

6. Click the radio button next to the ERL that you want to assign to the switch ports and click Select ERL. The Find ERL page closes.

7. Click Assign ERL.
Emergency Responder 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.

Emergency Responder commits your ERL assignments. From here, you can continue to the other page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.

Click Edit View to change the fields and arrangement of fields in the port list. If you want to revert to the standard view, then click Restore Defaults.

The phone location information is saved on the primary Emergency Responder server. Back up this data regularly.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Export Manually Configured Phone Information

You can export your Emergency Responder manually configured phone configuration. By exporting this information, you can back up your data or create a file that you can use to update a large number of manually configured phone mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens the Find and List Manually Configured Phones page.

Step 2

Click Export.
Emergency Responder opens the Export Manual Phones page.

Step 3

Select the export format (csv) from the Select Export Format pulldown menu.

Step 4

Enter the desired file name in the Enter Export File Name field and click Export.
Emergency Responder exports the file to the export location.

Step 5

To download the exported file to your local system, select the file name from the Select file to download pulldown menu and click Download.

Step 6

Click Close to close the Export Manual Phones page.

Related Tasks

Manually Define Phones

Assign Large Number of Manually Configured Phones to ERLs

Related Information

Work with Emergency Responder Locations

Synthetic Phones

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Assign Large Number of Manually Configured Phones to ERLs

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 a 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 Emergency Responder (see Export Manually Configured Phone Information), 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 following procedure explains how to get to this page. Links on the page also display the detailed information about the required file format for the import file if you need it.

Emergency Responder 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 Emergency Responder.

You can only configure manually configured phones defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
The Find and List Manually Configured Phones page appears.

Step 2

Click Import.
The Import Manually Configured Phones page appears.

Step 3

Select the Import Format (csv) using the pull-down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select the import file using the Select File to Import pull-down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Manually Configured Phone page.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Synthetic Phones

With Emergency Responder, you can use Cisco Unified Operations Manager to monitor the health and functionality of Cisco Emergency Responder. To use Cisco Unified Operations Manager with Cisco Emergency Responder, you configure a synthetic phone in Emergency Responder and associate the synthetic phone to an ERL that is used as a test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can only configure test ERLs for conventional ERLs. You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

For more information, see Set Up Test ERLs.

View Emergency Call History

You can view the history of emergency calls made in your network that are handled by Emergency Responder. Emergency Responder sends emergency call notifications to the onsite alert personnel that you identify in your ERLs, and these people respond to the notifications. From the administrator interface, you can view the same call history that your onsite alert personnel can view, and see 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 about the 10,000 most recent calls. You can find records of older calls in Emergency Responder raw call log files. See Call History Logs for more information.

Procedure

Step 1

Select Reports > Call History.
Emergency Responder opens the Call History page.

Step 2

Click Find.
All call summary information appears.

Step 3

Enter the search criteria that 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. 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).

Step 4

From the list of calls that Emergency Responder shows you in response to your search criteria, you can:

- View the call characteristics.

- Click 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. Emergency Responder opens a separate window where you make your editorial changes.

Tip:
If a large number of calls match your search criteria, Emergency Responder uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.

Related Information

Call History Logs

Call History Logs

Emergency Responder 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.

Emergency Responder maintains in its database a history of the emergency calls that have been placed. When the primary Emergency Responder server (Publisher) is not active, emergency calls are handled by the backup Emergency Responder 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 Emergency Responder servers.

To download these records, click the Download button at the top of the table displaying the call history. These records are downloadable in Excel (.xls) format.

Set Up Support for Intrado V9-1-1 for Enterprise Service

After you have confirmed your emergency service support with Intrado, you must configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

You must complete the tasks described in the following procedure before creating Intrado ERLs.

Note

You must configure the IP address of the DNS server to resolve the URLs provided by Intrado before completing these tasks. See Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder.

Procedure

Step 1

Configure the following items in the Validation and Update Interface (VUI):

1. Upload the certificate provided by Intrado.

2. Validate the certificate.

3. Configure Intrado Account Information.

Step 2

Configure Route Patterns for routing calls to Intrado on the Emergency Responder server.

Step 3

Configure Route Patterns and gateway for routing calls to Intrado on Unified CM server.
See Understanding Route Plans chapter in Cisco Unified Communications Manager System Guide, and the "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Step 4

Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

Step 5

Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

Related Tasks

Set Up Emergency Responder to Support Off-Premise Users

Set Up Intrado VUI Settings

Set Up Intrado Route Patterns on Emergency Responder

Set Up Intrado ERLs

Reconcile ALI Discrepancies

Identify Unlocated Phones

Related Information

Switch Port Configuration

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Set Up Intrado Route Patterns on Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

Procedure

Step 1

From Emergency Responder, Choose System >Telephony Settings.
The Telephony Settings page is displayed.

Step 2

Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Related Tasks

Set Up Intrado Route Patterns on Emergency Responder

Set Up Intrado ERLs

Reconcile ALI Discrepancies

Set Up Intrado Route Patterns on Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

Procedure

Step 1

From Emergency Responder, Choose System >Telephony Settings.
The Telephony Settings page is displayed.

Step 2

Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

Intrado ERL Information Export

Use the Export ERL page to create ERL export files for our own use, for example, to back up or move an ERL configuration. For more information about importing ERLs, see Export ERL Information.

Related Tasks

Set Up Intrado VUI Settings

Set Up Intrado Route Patterns on Emergency Responder

Reconcile ALI Discrepancies

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Set Up Intrado Route Patterns on Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

Procedure

Step 1

From Emergency Responder, Choose System >Telephony Settings.
The Telephony Settings page is displayed.

Step 2

Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

Reconcile ALI Discrepancies

You can use Emergency Responder to compare the records from Intrado VUI with the records in the database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

Procedure

Step 1

In Emergency Responder Administration, choose ERL>Intrado ERL>View ALI Discrepancies.
The View Intrado ALI Discrepancies page appears.

Step 2

Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3

Click on the radio button next to the ELIN that you want to view or click View ALI Discrepancies to launch the View Intrado ALI discrepancies for a particular ELIN.
The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4

Choose the correct data from either the local Emergency Responder database or from Intrado.

Step 5

Click Save to save changes to the local Emergency Responder database. Click Save Intrado ALI Info to save changes to the Intrado VUI.

Step 6

Click Close to close this window.

Related Tasks

Set Up Intrado VUI Settings

Set Up Intrado Route Patterns on Emergency Responder

Set Up Intrado ERLs

Set Up Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.

Note

To continue emergency service support when there is a failover to the Emergency Responder subscriber, you must upload the certificate file to the Emergency Responder subscriber separately.

Procedure

Step 1

From Emergency Responder, choose System > Intrado VUI Settings.
The Intrado VUI Settings page displays.

Step 2

Click Upload Certificate. An Upload Certificate window opens.

Step 3

Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 4

Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 5

Enter the Account Information.

- VUI Schema URL

- Intrado Account ID

- Max VUI Connections

Step 6

Click Update.
For more information about the Intrado VUI settings, see Intrado VUI Settings.

Set Up Intrado Route Patterns on Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

Procedure

Step 1

From Emergency Responder, Choose System >Telephony Settings.
The Telephony Settings page is displayed.

Step 2

Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.

Set Up Intrado ERLs

Before You Begin
You must first configure Intrado route patterns before you can add any Intrado ERLs.

Note

Intrado ERLs differ from conventional ERLs in the following ways:

- You can only select route patterns from a preconfigured list in the Telephony Settings web page.

- You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

- You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.

Procedure

Step 1

From Emergency Responder, choose ERL>Intrado ERL>Intrado ERL(Search and List).
The Find Intrado ERL Data page displays.

Step 2

Click the Add New ERL button.
Emergency Responder opens the Add New ERL window. See Find Intrado ERL for a detail explanation of each field.

Step 3

Fill in the ERL Information.

Step 4

Click ALI Details
Emergency Responder opens the ALI Information window.

Step 5

Enter the ALI Information. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6

After entering the ALI Information, click Pre-validate from Intrado.

Step 7

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Migrate Conventional ERL Data to Intrado ERL Data

Procedure

Step 1

In Emergency Responder Administration, choose ERL>ERL Migration Tool.
The ERL Migration Tool page appears.

Step 2

Choose Conventional ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 3

Select the ERLs that you want to migrate by checking the check box next to the ERL name.
The Enter Route Patterns for ERL Migration window appears.

Step 4

Choose an updated route pattern from the drop-down menu.

Step 5

Click Migrate to Intrado ERL.

Related Tasks

Set Up Support for Intrado V9-1-1 for Enterprise Service

Migrate Intrado ERL Data to Conventional ERL Data

Set Up Support for Intrado V9-1-1 for Enterprise Service

After you have confirmed your emergency service support with Intrado, you must configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

You must complete the tasks described in the following procedure before creating Intrado ERLs.

Note

You must configure the IP address of the DNS server to resolve the URLs provided by Intrado before completing these tasks. See Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder.

Procedure

Step 1

Configure the following items in the Validation and Update Interface (VUI):

1. Upload the certificate provided by Intrado.

2. Validate the certificate.

3. Configure Intrado Account Information.

Step 2

Configure Route Patterns for routing calls to Intrado on the Emergency Responder server.

Step 3

Configure Route Patterns and gateway for routing calls to Intrado on Unified CM server.
See Understanding Route Plans chapter in Cisco Unified Communications Manager System Guide, and the "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Step 4

Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

Step 5

Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

Migrate Intrado ERL Data to Conventional ERL Data

Procedure

Step 1

Step 2

In Emergency Responder Administration, choose ERL> ERL Migration Tool. The ERL Migration Tool page appears.

Step 3

Choose Intrado ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 4

Select the ERLs that you wish to migrate by checking the check box next to the ERL name. The Enter Route Patterns for ERL Migration window appears.

Step 5

Enter an updated route/pattern translation pattern in the adjacent text box.

Step 6

Click Migrate to Conventional ERL.

Migrate Intrado ERL Data to Conventional ERL Data

Procedure

Step 1

Step 2

In Emergency Responder Administration, choose ERL> ERL Migration Tool. The ERL Migration Tool page appears.

Step 3

Choose Intrado ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 4

Select the ERLs that you wish to migrate by checking the check box next to the ERL name. The Enter Route Patterns for ERL Migration window appears.

Step 5

Enter an updated route/pattern translation pattern in the adjacent text box.

Step 6

Click Migrate to Conventional ERL.

Related Tasks

Migrate Conventional ERL Data to Intrado ERL Data

Related Information

ERLs

Migrate Conventional ERL Data to Intrado ERL Data

Procedure

Step 1

In Emergency Responder Administration, choose ERL>ERL Migration Tool.
The ERL Migration Tool page appears.

Step 2

Choose Conventional ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 3

Select the ERLs that you want to migrate by checking the check box next to the ERL name.
The Enter Route Patterns for ERL Migration window appears.

Step 4

Choose an updated route pattern from the drop-down menu.

Step 5

Click Migrate to Intrado ERL.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Related Tasks

Set Up Support for Intrado V9-1-1 for Enterprise Service

Set Up Emergency Responder Location Management in Cisco Unified Communications Manager

Set Up AXL Application User

Set Up AXL Authentication

Set Up Off-Premise ERL

Identify Unlocated Phones

Set Up Support for Intrado V9-1-1 for Enterprise Service

After you have confirmed your emergency service support with Intrado, you must configure Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

You must complete the tasks described in the following procedure before creating Intrado ERLs.

Note

You must configure the IP address of the DNS server to resolve the URLs provided by Intrado before completing these tasks. See Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder.

Procedure

Step 1

Configure the following items in the Validation and Update Interface (VUI):

1. Upload the certificate provided by Intrado.

2. Validate the certificate.

3. Configure Intrado Account Information.

Step 2

Configure Route Patterns for routing calls to Intrado on the Emergency Responder server.

Step 3

Configure Route Patterns and gateway for routing calls to Intrado on Unified CM server.
See Understanding Route Plans chapter in Cisco Unified Communications Manager System Guide, and the "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Step 4

Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

Step 5

Assign Intrado ERLs to switch ports, IP subnets, and unlocated phones.

Set Up Emergency Responder Location Management in Cisco Unified Communications Manager

You must configure the Emergency Responder Location Management server on the Unified CM server before your users can use it to enter their off-premise locations.

To enable Cisco Emergency Location Manager in Unified CM, follow these steps:

Procedure

Step 1

From Unified CM Administration, choose System > Application Server.

Step 2

Click Add New. The Application Server Configuration page is displayed.

Step 3

From the Application Server Type drop-down box, choose CER Location Management.

Step 4

Click Next.

Step 5

Enter a name that identifies Emergency Responder Off-Premise application. The name is displayed in the navigation drop-down box on the User Option page and is selected by the user to navigate to the Emergency Responder Off-Premise page.

Step 6

Enter the URL for the Emergency Responder Off-Premise page. The URL takes the form of http://cer_host/ofpuser , where cer_host is the name or IP address of the Emergency Responder publisher or Emergency Responder subscriber.
Note:
You must enter both the Emergency Responder publisher and Emergency Responder subscriber as separate application servers on Unified CM Administration.

Step 7

Click Save.

Set Up AXL Application User

You must configure the AXL application user for Emergency Responder on Unified CM, so that an off-premises user can log in to the Emergency Responder off-premises user website.

Procedure

Step 1

In Cisco Unified Communications Manager, choose User Management > Application User. Click Add New. Cisco Unified Communications Manager displays the Application User Configuration page.

Step 2

Complete the following required fields:

- User ID—Use a descriptive name such as AXL Application User.

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

Click Save.

Step 4

Choose User Management > User Group in the Cisco Unified Communications Manager menu. The user group search page appears.

Step 5

At search criterion, enter standard and click Find.
The list of user groups starting with the name standard appears.

Step 6

Click Standard CCM Admin Users to display the User Group configuration page.

Step 7

Click Add App Users to Group. The Find and List Application Users pop-up window appears.

Step 8

Enter the User ID created in Step 2 as the search criterion and click Find. The list of Applications users appears.

Step 9

Click the check box next to the user ID. Click Add Selected.
Unified CM adds the selected user to the Standard CCM Admin Users user group.

Step 10

Choose User Management > User Group. The user group search page appears.

Step 11

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 12

Click the Standard TabSync User group.

Step 13

Repeat steps 7 through 9 to add the user to the Standard TabSync User group.

Step 14

Choose User Management > User Group. The user group search page appears.

Step 15

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 16

Click the Standard RealtimeAndTraceCollection group.

Step 17

Repeat steps 7 through 9 to add the user to the Standard RealtimeAndTraceCollection group.

Set Up AXL Authentication

Procedure

Step 1

From Emergency Responder, choose Phone Tracking > Unified CM.

Step 2

Under AXL Setting, enter the following information:

- AXL Username

- AXL Password

- AXL Port Number

Step 3

Click Insert.

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Set Up Emergency Responder Location Management in Cisco Unified Communications Manager

You must configure the Emergency Responder Location Management server on the Unified CM server before your users can use it to enter their off-premise locations.

To enable Cisco Emergency Location Manager in Unified CM, follow these steps:

Procedure

Step 1

From Unified CM Administration, choose System > Application Server.

Step 2

Click Add New. The Application Server Configuration page is displayed.

Step 3

From the Application Server Type drop-down box, choose CER Location Management.

Step 4

Click Next.

Step 5

Enter a name that identifies Emergency Responder Off-Premise application. The name is displayed in the navigation drop-down box on the User Option page and is selected by the user to navigate to the Emergency Responder Off-Premise page.

Step 6

Enter the URL for the Emergency Responder Off-Premise page. The URL takes the form of http://cer_host/ofpuser , where cer_host is the name or IP address of the Emergency Responder publisher or Emergency Responder subscriber.
Note:
You must enter both the Emergency Responder publisher and Emergency Responder subscriber as separate application servers on Unified CM Administration.

Step 7

Click Save.

Related Tasks

Set Up AXL Application User

Set Up AXL Authentication

Set Up Off-Premise ERL

Set Up AXL Application User

You must configure the AXL application user for Emergency Responder on Unified CM, so that an off-premises user can log in to the Emergency Responder off-premises user website.

Procedure

Step 1

In Cisco Unified Communications Manager, choose User Management > Application User. Click Add New. Cisco Unified Communications Manager displays the Application User Configuration page.

Step 2

Complete the following required fields:

- User ID—Use a descriptive name such as AXL Application User.

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

Click Save.

Step 4

Choose User Management > User Group in the Cisco Unified Communications Manager menu. The user group search page appears.

Step 5

At search criterion, enter standard and click Find.
The list of user groups starting with the name standard appears.

Step 6

Click Standard CCM Admin Users to display the User Group configuration page.

Step 7

Click Add App Users to Group. The Find and List Application Users pop-up window appears.

Step 8

Enter the User ID created in Step 2 as the search criterion and click Find. The list of Applications users appears.

Step 9

Click the check box next to the user ID. Click Add Selected.
Unified CM adds the selected user to the Standard CCM Admin Users user group.

Step 10

Choose User Management > User Group. The user group search page appears.

Step 11

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 12

Click the Standard TabSync User group.

Step 13

Repeat steps 7 through 9 to add the user to the Standard TabSync User group.

Step 14

Choose User Management > User Group. The user group search page appears.

Step 15

Enter standard as the search criterion and click Find. The list of user groups starting with the name Standard appears.

Step 16

Click the Standard RealtimeAndTraceCollection group.

Step 17

Repeat steps 7 through 9 to add the user to the Standard RealtimeAndTraceCollection group.

Set Up AXL Authentication

Procedure

Step 1

From Emergency Responder, choose Phone Tracking > Unified CM.

Step 2

Under AXL Setting, enter the following information:

- AXL Username

- AXL Password

- AXL Port Number

Step 3

Click Insert.

Set Up Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by the IP subnet and the phone MAC address assignment.

Note

You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You cannot assign off-premise ERLs to switch ports.

Procedure

Step 1

Choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List) from Emergency Responder.

Step 2

Click Add New ERL.

Step 3

Fill in the following information in the Add New ERL window and click Insert:

- ERL Name

- Description

- Intrado route pattern/translation Pattern

- Onsite Alerts

Fill in the information in the Add New ERL window. See Off-Premises ERL for detailed explanations of each field.

Note:
You must add Intrado route patterns before you can add off-premise ERLs.

Add Scheduled Intrado Updates

You can create ALI and Secondary Status update schedules between Emergency Responder and Intrado. A scheduled ALI update sends newly created TN records to Intrado. A scheduled Secondary Status update sends queries to Intrado requesting information about records with errors that have been corrected.

Procedure

Step 1

Choose ERL>Intrado ERL>Intrado Schedule from Emergency Responder, . The Intrado Schedule page appears.

Step 2

Choose the days of the week and the time of day that you want to schedule an update.

Step 3

Check the Enable Schedule box if you want to activate this schedule.

Step 4

Choose either ALI Update Schedule or Secondary Status Update Schedule.

Step 5

Click Add to add the schedule to the list of schedules

Related Tasks

Log In to Emergency Responder

Set Up Emergency Responder Cluster and Cluster DB Host

Related References

Intrado ERL - Secondary Status

Intrado Schedule

Related Information

Emergency Responder User Management

Emergency Responder Role Management

Emergency Responder User Group Management

Server and Server Group Configuration

Cisco Unified Communications Manager Cluster Changes

Work with Emergency Responder Locations

Emergency Responder Switch Configuration

Phone Management

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Emergency Responder Role Management

When you install Emergency Responder, the system defines six default roles (see Role Management for more information about the default roles). You can also define additional roles or modify existing roles.

The following topics describe how to add new roles and how to modify and delete existing roles.

Emergency Responder User Group Management

When you install Emergency Responder, the system defines six default user groups (see User Group Management for more information about the default user groups). You can also define additional user groups or modify existing user groups.

The following topics describe how to add new user groups and how to modify existing user groups.

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Server and Server Group Configuration

The information in the following topics describe how to configure Emergency Responder servers and server groups, and the telephony connection between the Emergency Responder groups and Unified CM.

Set Up Emergency Responder Cluster and Cluster DB Host

Procedure

Step 1

Identify the following:

- All the Emergency Responder groups participating in the Emergency Responder cluster

- One of the Emergency Responder publishers as "Cluster DB Host"

- A password that is the same across the Cluster as "Cluster password"

Step 2

Using the Emergency Responder Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1.

Step 3

Repeat steps 1 and 2 for each Emergency Responder server group in the cluster.

Step 4

Restart Emergency Responder services.
Note:
Emergency Responder server groups can communicate with Emergency Responder 1.3, 2.x, 7.1 and 8.0 and later versions of Emergency Responder server groups in an Emergency Responder cluster.

Cisco Unified Communications Manager Cluster Changes

If you change or upgrade the Unified CM cluster identified in Emergency Responder to a later version, you must use the Admin Utility to identify Emergency Responder with the later Unified CM version.

To change the Unified CM cluster that is identified in Emergency Responder to a different version, see Change Cisco Unified Communications Manager Version.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Emergency Responder Switch Configuration

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. The following topics describe the switch requirements and how to identify switches to Emergency Responder.

Phone Management

The following 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 Emergency Responder.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

Update Scheduled Intrado Update

Procedure

Step 1

From Emergency Responder, choose ERL > Intrado ERL > Intrado Schedule. The Intrado Schedule page appears.

Step 2

Click the Edit link adjacent to the schedule that you want to update.

Step 3

Choose the days of the week and the time of day.

Step 4

Check the Enable Schedule box to activate this schedule.

Step 5

Click Update to change the schedule on the list of schedules.

Related Tasks

Log In to Emergency Responder

Set Up Emergency Responder Cluster and Cluster DB Host

Related References

Intrado ERL - Secondary Status

Intrado Schedule

Related Information

Emergency Responder User Management

Emergency Responder Role Management

Emergency Responder User Group Management

Server and Server Group Configuration

Cisco Unified Communications Manager Cluster Changes

Work with Emergency Responder Locations

Emergency Responder Switch Configuration

Phone Management

Emergency Responder User Management

When you install Emergency Responder, the system defines one default Emergency Responder Administrator user (see User Management for more information). You can also define additional users or modify existing users.

The information in the following sections describe how to add new users and how to modify and delete existing users.

Emergency Responder Role Management

When you install Emergency Responder, the system defines six default roles (see Role Management for more information about the default roles). You can also define additional roles or modify existing roles.

The following topics describe how to add new roles and how to modify and delete existing roles.

Emergency Responder User Group Management

When you install Emergency Responder, the system defines six default user groups (see User Group Management for more information about the default user groups). You can also define additional user groups or modify existing user groups.

The following topics describe how to add new user groups and how to modify existing user groups.

Log In to Emergency Responder

You must log into the Emergency Responder web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See Role-Based User Management for more information.

Before You Begin
You must have a valid user ID and password before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.

Procedure

Step 1

From an supported browser, open this URL, where servername is the DNS name or IP address of the Emergency Responder server: http://servername/ceradmin.
The browser opens the Emergency Responder Server Administration page.

Step 2

Use the Navigation pull-down menu to select the website that you want to log into. The Emergency Responder websites are as follows:

- Emergency Responder Serviceability

- Emergency Responder Administration

- Cisco Unified OS Administration

- Disaster Recovery System

- Emergency Responder User

- Emergency Responder Admin Utility

To open the Log-in page, click one of websites in the list.

Step 3

Click Go.
The login screen for the selected website appears.

Step 4

Enter your user name and password, and click Login.
Emergency Responder 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 that you cannot view because of your authorization level.

When you are finished, click Logout above the menu bar to log out.

Note:
In Emergency Responder 8.5 and above, the validation for Username is not case sensitive.

Server and Server Group Configuration

The information in the following topics describe how to configure Emergency Responder servers and server groups, and the telephony connection between the Emergency Responder groups and Unified CM.

Set Up Emergency Responder Cluster and Cluster DB Host

Procedure

Step 1

Identify the following:

- All the Emergency Responder groups participating in the Emergency Responder cluster

- One of the Emergency Responder publishers as "Cluster DB Host"

- A password that is the same across the Cluster as "Cluster password"

Step 2

Using the Emergency Responder Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1.

Step 3

Repeat steps 1 and 2 for each Emergency Responder server group in the cluster.

Step 4

Restart Emergency Responder services.
Note:
Emergency Responder server groups can communicate with Emergency Responder 1.3, 2.x, 7.1 and 8.0 and later versions of Emergency Responder server groups in an Emergency Responder cluster.

Cisco Unified Communications Manager Cluster Changes

If you change or upgrade the Unified CM cluster identified in Emergency Responder to a later version, you must use the Admin Utility to identify Emergency Responder with the later Unified CM version.

To change the Unified CM cluster that is identified in Emergency Responder to a different version, see Change Cisco Unified Communications Manager Version.

Work with Emergency Responder 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

Unified CM supports alerts to onsite security personnel from Cisco Emergency Responder and PSAP Callback on phones that have the Do-Not-Disturb feature enabled.

Emergency Responder system administrators or ERL administrators can create and modify ERLs. The following sections explain ERLs in greater detail and explain how to work with them in Emergency Responder.

Emergency Responder Switch Configuration

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. The following topics describe the switch requirements and how to identify switches to Emergency Responder.

Phone Management

The following 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 Emergency Responder.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

Use Control Center

The Control Center allows you to perform actions on the services running on the selected Emergency Responder system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Control Center. The Control Center page appears.

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 Emergency Responder Serviceability website. These services can only be started, stopped, or restarted using the CLI.

Step 3

Click Refresh to refresh the page.

Related References

Control Center

Control Center

The Control Center page appears when you choose Tools > Control Center.

Authorization Requirements

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.

The following table describes the Control Center page.

Control Center Page

Field

Description

Start button

Starts the selected services.

Stop button

Stops the selected services.

Restart button

Restarts the selected services.

Refresh button

Refreshes the list of currently running services on the selected server.

Service Name

Names of the currently running services on the selected server. To select a service, click the radio button next to the service name.

Status

Current status of the selected service.

Use Event Viewer

The Event Viewer allows you to view events for the prior six months.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Event Viewer. The Event Viewer page appears.

Step 2

Click Find without entering any search criteria to find all events that occurred over the prior six months
To find events that match specific criteria, enter search criteria:

- 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 pull-down menu to the right.

If you select Module, you can then select the module on which to search from the pull-down menu to the right.

Note:
For a list of available Types and Modules, see Event Viewer.

When you have entered your search criteria, click Find.

Step 3

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 References

Event Viewer

Event Viewer

The Event Viewer page appears when you choose Tools > Event Viewer.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Event Viewer page to view Emergency Responder events for the previous six months.

The following table describes the Event Viewer page.

Event Viewer Page

Field

Description

Type pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down 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 pull-down menu to the right of the Type pull-down menu.

Module pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down menu to the right changes to display the available Type or Module options.

Allows you to select the Emergency Responder module for which you want to view events. When you select Module from the pull-down 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

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.

Type column

Displays the type of event. The Type column displays one of the following:

- INFO

- WARN

- ERROR

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.

Module column

Displays the Emergency Responder 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.

Set Up SNMP Community String

By configuring SNMP, you can control SNMP access to the Emergency Responder 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

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V1/V2C Configuration > Community String. The SNMP Community String Configuration page appears.

Step 2

Enter the name of the community string in the Community String Name text box.

Step 3

Click Accept SNMP Packets only from these hosts to specify specific hosts whose SNMP packets will be accepted, 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.

Step 4

Select the host IP address and click Remove to remove an existing host, .

Step 5

Select the access privilege for the host from the Access Privileges pull-down menu then click Insert.

Related References

SNMP Community String Configuration

SNMP Community String Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP Community String Configuration page to view, add, update, and delete community strings. Community strings control access to the Emergency Responder by clients using SNMP V1 and V2c.

The following table describes the SNMP Community String Configuration page.

SNMP Community String Configuration Page

Field

Description

Community String Name column

Lists all community strings defined for the selected server. Click 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 this button, Emergency Responder opens a second SNMP Community String Configuration page.

Note:
Clicking the Add New button brings up the same screen displayed when you click the Add New icon.

Delete Selected button or icon

Deletes the selected community strings. To delete a community string, you must first select it from the list of community strings. Click the box to the left of the community string name to select it. To delete all community strings from the selected server, click 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 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.

The following table describes the second SNMP Community String Configuration page.

SNMP Community String Configuration Page—2

Field

Description

Community String Name

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.

Host IP Address Information

Accept SNMP Packets from any host

Click this radio button to allow any host to access the Emergency Responder using SNMP.

Accept SNMP Packets only from these hosts

Click this radio button to specify which hosts can access the Emergency Responder 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.

Access Privileges pulldown menu

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:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert 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.

Clear button or icon

Clears the community string information displayed on the current page.

Set Up SNMP Users

SNMP V3 provides additional security features that include message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V3 Configuration > User.
The SNMP User Configuration page appears.

Step 2

Click Add New to add a new SNMP User,

Step 3

Enter the name of the new user in the User Name text box.

Step 4

Check the Authentication Required check box to require authentication. Enter a password in the Password text box, reenter the password in the Reenter Password textbox, and click either MD5 or SHA to select a Protol. Click Insert to add the user.

Step 5

Check the Privacy Required check box to require information privacy. Enter a password in the Password textbox, reenter the password in the Reenter Password textbox, and click the DES check box.
Note:
A message is displayed stating 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

Repeats Step 2 through to Step 4 to add additional users.

Related References

SNMP User Configuration

SNMP User Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the SNMP User Configuration page.

SNMP User Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to view, add, update, or delete users. After you select a server, Emergency Responder displays the currently configured information in the following format:

- User Name

- Authentication Required

- Authentication Protocol

- Privacy Required

- Privacy Protocol

- Access Privileges

Click user name to display the Add and Update SNMP User Configuration page, from which you can update the information for that user.

Add New User button or icon

Add a new user for the selected server. When you click this icon, Emergency Responder opens the 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 the box to the left of the User Name column heading.

Use the second SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the Add/Update SNMP User Configuration page.

SNMP User Configuration Page—2

Field

Description

User Name field

Enter the name of the new SNMP V3 user.

Note:
If you reached this page by clicking an existing user name on the SNMP User Configuration page, the fields on this page display the currently configured information.

Authentication Information

Use this section to configure the following information:

- If authentication is required for this user, check the check box that is 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 the radio button for either MD5 or SHA.

Privacy Information

Use this section to configure the following information:

- If privacy is required for this user, check the check box that is labelled 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 labelled DES.

Host IP Addresses Information

Use the radio buttons in this section of the page to do the following:

- Specify which hosts can access the Emergency Responder using SNMP. You can insert IP addresses for new hosts that you want to have SNMP access to the Emergency Responder, or you can remove IP addresses of hosts that you no longer want to have SNMP access to Emergency Responder.

- Allow any host to access Emergency Responder using SNMP.

Access Privileges pulldown menu

When adding a new user, this pull-down menu allows you to specify the access privilege for the new user. When updating a user's information, this field displays the current access privilege level. The available access privilege levels are as follows:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert button or icon

Insert the new user information for the selected server.

Clear button or icon

Clears the user information displayed on the current page.

Set Up SNMP v3 Notification Destination String

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.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V3 Configuration > Notification Destination.
The SNMP Notification Destination Configuration page appears.

Step 2

Click Add New to add a new SNMP Notification Destination, .

Step 3

Select Add New from the Host IP Addresses pull-down menu. Additional fields appear.

Step 4

Enter the Host IP Address and Port Number in the text boxes.

Step 5

Select Inform or Trap from the Notification Type pull-down menu. If you select Inform, you are prompted to enter a remote engine ID. If you select Trap, the Security Level pull-down menu appears. Proceed to Step 7.

Step 6

Enter the remote engine ID.

Step 7

Select the desired security level from the Security Level pull-down menu.

Step 8

Click the radio button to the left of the User Name to select a user to be associated with the notification destination.

Step 9

Repeat Step 2 through to Step 8 to add additional notification destinations, .

Related References

SNMP v3 Notification Destination Configuration

SNMP v3 Notification Destination Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP V3 Notification Destination Configuration page to identify the destination to which the Emergency Responder SNMP agent sends trap messages. The SNMP V3 Notification Destination information provides enhanced security because each notification string is associated with a specific user.

The following table describes the SNMP V3 Notification Destination Configuration page.

SNMP v3 Notification Destination Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to view, add, update, or delete SNMP notification destination information. After you select a server, Emergency Responder displays the currently configured information in the following format:

- Destination IP Address

- Port Number

- Security Model

- Security Name

- Security Level

- Notification Type

Click a Destination IP Address to update the information for the device at that address. When you click an IP address in this list, Emergency Responder 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, Emergency Responder opens the Add/Update Notification Destination page.

Add New button or icon

Add a new notification destination for the selected server. When you click this icon, Emergency Responder 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 the box to the left of the Destination IP Address column heading.

Use the second SNMP V3 Notification Destination page to add new notification destinations and to update existing notification destinations.

The following table describes the second SNMP V3 Notification Destination Configuration page.

SNMP v3 Notification Destination Configuration Page—2

Field

Description

Host IP Addresses pulldown menu

Select Add New from this pull-down menu to add a new notification destination.

Note:
If you reached this page by clicking 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

IP address of the new notification-destination host.

Port Number field

Port number on the new notification-destination host that receives the notifications from the Emergency Responder SNMP agent.

Notification Type pulldown menu

Select the SNMP message type for the new notification-destination host. The option is:

- 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 pull-down menu.

Note:
If you reached this page by clicking an existing Destination IP Address on the SNMP V3 Notification Destination Configuration page, the Remote SNMP Engine ID field displays the currently configured information.

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 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

Inserts the new notification destination for the selected server.

Clear button or icon

Clears the notification destination information displayed on the current page.

Set Up MIB2

The SNMP MIB2 tool allows you to specify a contact person for a MIB2 managed node and the physical location of the managed node.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > System Group Configuration > MIB2 System Group Configuration. The SNMP MIB2 Configuration page appears.

Step 2

In the System Contact text box, enter the name of the contact.

Step 3

In the Location text box, enter the location of the managed node.

Step 4

Click Update in the upper left corner of the page.

Step 5

Click Clear in the upper left corner of the page to modify the information, enter the new information in the System Contact and Location text boxes, and click Update.

Related References

MIB2 System Group Configuration

MIB2 System Group Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the MIB2 System Group Configuration page to specify the name and physical location of the contact person for MIB2 managed mode.

The following table describes the MIB2 System Group Configuration page.

MIB2 System Group Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to update the MIB2 contact information. After you select a server, Emergency Responder displays fields in which you enter the name and physical location of the contact.

System Contact

The name of the MIB2 contact.

System Location

The physical location of the managed node.

Update button or icon

Saves the updated MIB2 contact information.

Clear button or icon

Clears the MIB2 contact information displayed on the current page.

Use 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.

Procedure

Step 1

From the Emergency Responder 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 about the information that is displayed, see Table 1.

Step 2

Enter a value (in seconds) in the Set the screen refresh value text box to change the rate at which the page refreshes, and click Set. The minimum value you can enter is 5 seconds.

Step 3

Check the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Click the Start Log button in the Processors section of the page to create a log file of the CPU usage.
Click Start Log in the Memory section of the page to create a log file of the Memory usage.

You can create up to 25 log files.

The default interval for logging is 10 seconds. To change the logging interval, follow these steps:

1. 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.

2. 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

Click Download CPU Log File or Download Memory Log File to download the log files.
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 names that you want to download. To download all log files, check 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 creates and downloads a zipped folder called CPULogs (for Processor log files) and MemoryLogs (for Memory log files).

Step 7

To view the log files online without downloading them, click the file name. The system displays the contents of the log file.

Related References

CPU and Memory Usage

CPU and Memory Usage

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the CPU and Memory Usage page to view the CPU and memory usage for the Emergency Responder system.

The following table describes the CPU and Memory Usage page.

CPU and Memory Usage Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Set the screen reset value

Specify in seconds how often this page should be refreshed.

Set CPU Logging Interval

Specify in seconds how often CPU usage is logged. The interval must be between 5 and 600 seconds.

Processors

This section displays the percentage of CPU time being used by various system components.

Download CPU Log File

Click this link to download the currently displayed CPU and memory usage information to a file. 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 2.

Processor

Name of the processor.

%User

Percentage of processor time being used by the User mode.

%System

Percentage of processor time being used by the System mode.

%Nice

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

Percentage of time in which the processor is idle.

%Irq

Percentage of processor time being used by interrupt requests (IRQ).

%Softirq

Percentage of processor time being used by soft IRQs.

Note:
A soft IRQ is an interrupt request that can be deferred.

%I/O Wait

Percentage of time that the processor is executing read or write operations.

%CPU

The processor's share of the elapsed CPU time (excluding idle time) since last update, expressed as a percentage of CPU time.

Start Log button

Starts a log file of the current CPU usage.

Note:
You can create a maximum of 25 CPU log files.

Memory

This section displays the percentage of memory allocated for different uses.

Download Memory Log File

Click this link to download to a file the currently displayed CPU and memory usage information. When you click this link, a new page opens that lists all the saved CPU log files. For more information about this screen, see Table 3.

Total (KB)

The amount of memory available, in kilobytes.

Used (KB)

Amount of memory currently being used, in kilobytes.

Free (KB)

Amount of memory that is available for use, in kilobytes.

Shared (KB)

Amount of memory used by shared processes, in kilobytes.

Buffers (KB)

Amount of memory used by buffers, in kilobytes.

Cached (KB)

Amount of memory used for caching, in kilobytes.

Total Swap (KB)

Amount of total swap space, in kilobytes

Used Swap (KB)

Amount of swap space currently being used, in kilobytes.

Free Swap (KB)

Amount of available swap space, in kilobytes

%VM Used

Amount of virtual memory being used.

Start Log button

Starts a log file of the current memory usage.

Use the CPU Log Files page to view and download the CPU log files.

The following table describes the CPU Log Files page.

CPU Log Files Page

Field

Description

Download button

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.

CPU Log Files

This section displays the details of the saved CPU log files.

File Name

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.

Last Modified

Date and time of the last modification to the CPU log file.

File Size (KB)

Size of the CPU log file, in kilobytes.

Use the Memory Log Files page to view and download the memory log files.

The following table describes the Memory Log Files page.

Memory Log Files Page

Field

Description

Download button

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.

Memory Log Files

This section displays the details of the saved Memory log files.

File Name

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.

Last Modified

Date and time of the last modification to the Memory log file.

File Size (KB)

Size of the Memory log file, in kilobytes.

Use 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 can change how often the information refreshes, or you can disable the auto-refresh feature.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Processes.
The Processes page appears. For details about the information that is displayed, see Table 2.

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.

Step 2

Enter a value in the Set the screen refresh value text box in the upper right corner and click Set to change the rate at which the page refreshes. The minimum value you can enter is 5 seconds.

Step 3

Select the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Select the check box to the left of the process name and click View Selected Processes to view the details of a process. 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 stop a log, 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

Click Download Process Logs from the Process Log Files page to download the log files. To download log files click Download Log File from the Processes page.

Step 6

Select the check box to the left of the log file names to download individual files. 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 creates and downloads a zipped folder called ProcessLogs.

Step 7

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.

Related References

Processes

Processes

The Processes page appears when you choose System Monitor > Processes.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Processes page to view and download information about 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.

The following table describes the Processes page.

Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

Download Log File

Click this link to download log files you have created. You cannot download log files until you have first created them.

Select

Check boxes that allow you to select files to be viewed or downloaded.

Process

Name of the process.

PID

ID number of the process.

%CPU

Percentage of processor time being used by the process.

Status

Task's process status: Running (R), Sleeping (S), Uninterruptible disk sleep (D), Zombie (Z), 4 Traced (T), Paging (P)

Nice (Level)

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.

Vm RSS (KB)

Resident set currently in physical memory in kilobytes, including Code, Data and Stack.

Vm Size (KB)

Size of virtual memory, in kilobytes.

Vm Data (KB)

Amount of data currently stored in virtual memory, in kilobytes.

Thread Count

Number of program threads currently running.

Data Stack (KB)

Size of the data stack, in kilobytes.

Page Fault Count

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.

The following table describes the View Selected Processes page.

View Selected Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

View All Processes button

Returns you to the previous Processes screen, which displays all running processes.

Start Log button

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 1.

Use Disk Usage Tool

The Disk Usage tool displays the percentage of available disk space used by the different partitions in the system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Disk Usage.
The Disk Usage page appears. For details about the Disk Usage page, see Table 1.

Step 2

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.

Related References

Disk Usage

Disk Usage

The Disk Usage page appears when you choose System Monitor > Disk Usage.

Authorization Requirements

You must have serviceability authority to access this page.

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.

The following table describes the Disk Usage page.

Disk Usage Page

Field

Description

Disk Usage Details

Partition

Name of the partition.

Size

Size of the partition.

Percentage Used

How much disk space is the partition using, as a percentage of total allocated disk space.

Available Space

How much disk space is currently available on the partition.

Used Space

How much disk space is the partition using.

Use Emergency Responder Logs

Emergency Responder 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 Emergency Responder logs.

Emergency Responder logs are organized into three types. The three types, and the logs within these types, are as follows:

- Emergency Responder 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

- DB Logs

- Cerdbmon

- Install DB

- CLI Output Files

- Platform

- DB

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Logs > Log Type > Log Name.
The selected Log Files page appears. See Use Emergency Responder Logs for details about 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

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 creates and downloads a zipped folder called CPULogs. The names of the zipped folders are based on the type of logs they contain, as follows:

- CER Admin

- CERr Server

- CER Phone Tracking

- Syslog

- JTAPI

- Tomcat

- Install

- DRS

- CLILogs

- CMILogs

- ServmLogs

- RemoteSupportLogs

- InstallDBLogs

- CertificateManagement&IPSecLogs

- CerdbmonLogs

- CLIOutputPlatform

- CLIOutputDB

Step 3

Click the file name to view the log files online without downloading them. The system displays the contents of the log file in a separate window.

Step 4

Click Reload Log File to refresh the log file you are viewing.

Step 5

Click Download Log to download the log file you are viewing.

Related References

System Logs Menu

System Logs Menu

The System Logs menu contains the following submenus, under which all system logs are grouped:

- System Logs > Emergency Responder Logs

- System Logs > Platform Logs

- System Logs > DB Logs

- System Logs >CLI Output Files

Authorization Requirements

You must have serviceability authority to access the System Logs pages.

Note

Use the Up and Down arrows next to each column heading to sort the information by each category.

The following table describes the System Logs pages.

General Description of System Logs Pages

Field

Description

Download button

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 creates a Zip file that contains the log files to be downloaded.

File Name

Name of the log file. If you click 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.

Reload Log File button

Reloads the log file currently being viewed, so that any updates can be seen.

Note:
This button is only available when you have clicked a file name and are viewing the contents of particular log file.

Last Modified

Date the log file was last modified.

File Size (KB)

Size of the log file, in kilobytes.

Descriptions of Individual System Log File Pages

Menu/Log File Page

Description

CER Logs > CER Admin

View or download Emergency Responder Admin logs.

CER Logs > CER Server

View or download Emergency Responder Server logs.

CER Logs > CER Phone Tracking

View or download Emergency Responder Phone Tracking logs.

CER Logs > JTAPI

View or download JTAPI logs.

CER Logs > Tomcat

View or download Tomcat logs.

CER Logs > Event Viewer

View or download Emergency Responder Event logs.

CER Logs > Audio Driver

View or download Emergency Responder Audio Driver logs.

Platform Logs > CLI

View or download CLI operations logs.

Platform Logs > CLM

View or download CLM (Cluster Manager) logs.

Platform Logs > Certificate Management/IPSec

View or download Certificate Management and IPSec logs.

Platform Logs > DRS

View or download DRS (Disaster Recovery System) logs.

Platform Logs > Install/Upgrade

View or download Installation and Upgrade logs.

Platform Logs > Remote Support

View or download Remote Account creation and operations logs.

Platform Logs > Syslog

View or download Syslog logs.

Platform Logs > Servm

View or download Servm (Services Manager) logs.

DB Logs > Cerdbmon

View or download Cerdbmon logs.

DB Logs > Install DB

View or download InstallDB Utility logs.

CLI OutputFiles >Platform

View or download Platform log files.

CLI OutputFiles >DB

View or download DB log files.

Use 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 procedure outlines this process, with references to additional documentation.

Procedure

Step 1

Generate a CSR on the server.

Step 2

Download the CSR to your PC.

Step 3

Use the CSR to obtain an application certificate from a CA. Get information about obtaining application certificates from your CA.

Step 4

Obtain the CA root certificate. Get information about obtaining a root certificate from your CA.

Step 5

Upload the CA root certificate to the server.

Step 6

Upload the application certificate to the server.

Step 7

Restart the services that are affected by the new certificate. For all certificate types, restart the corresponding service (for example, restart the Tomcat service if you updated the Tomcat certificate). In addition, if you updated the certificate for CAPF or Unified CM, restart the TFTP service.

Related Tasks

Generate Certificate Signing Request

Download Certificate or CTL to Your Local System

Use Control Center

Related Information

Third-Party CA Certificates

Certificate or Certificate Trust List Uploads

Generate Certificate Signing Request

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears.

Step 2

Click Generate CSR. The Generate Certificate Signing Request dialog box opens.

Step 3

Select the certificate name from the Certificate Name list.

Step 4

Click Generate CSR.

Download Certificate or CTL to Your Local System

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Security > Certificate Management. The Certificate List page appears. Click the filename of the certificate or CTL.

Step 2

Use the Find controls to filter the certificate list.

Step 3

Click the filename of the certificate or CTL. The Certificate Configuration page appears.

Step 4

Click Download.

Step 5

In the File Download dialog box, click Save.

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. You can get information about obtaining these certificates from your CA. The process varies among CAs.

CAPF and Emergency Responder CSRs include extensions that you must include in your request for an application certificate from the CA. If your CA does not support the Extension Request method, 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 the CSRs in PEM encoding format. It accepts certificates in DER and DER encoding formats.

Certificate or Certificate Trust List Uploads

Caution

Uploading a new certificate or Certificate Trust List (CTL) file can affect your system operations. After you upload a new tomcat certificate or certificate trust list, you must restart the Cisco Tomcat service by entering the CLI command utils service restart Cisco Tomcat.

Note

The system does not distribute trust certificates to other cluster servers automatically. If you must have the same certificate on more than one server, you must upload the certificate to each server individually.

The following sections describe how upload a CA root certificate, application certificate, or CTL file to the server.

Use Control Center

The Control Center allows you to perform actions on the services running on the selected Emergency Responder system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Control Center. The Control Center page appears.

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 Emergency Responder Serviceability website. These services can only be started, stopped, or restarted using the CLI.

Step 3

Click Refresh to refresh the page.

Change IP Address of Emergency Responder Publisher or Standalone Server

Before You Begin

Note

Update the IP address information about your DNS server before you begin changing the IP address on the server.

Procedure

Step 1

Change the IP address on the Emergency Responder Publisher by using one of the following options:

- In Cisco Unified Operating System Administration, enter the new IP address in Settings > IP > Ethernet.

- On the CLI, configure the new IP address with the set network ip command.

Step 2

Reboot the Emergency Responder Publisher or Standalone server and wait until it is fully operational. For a Standalone server, go to Step 7 once the server is operational.

Step 3

When the Emergency Responder Publisher is fully operational, login to Cisco Unified Operating System Administration on the Emergency Responder Subscriber.

Step 4

Choose Settings > IP > Publisher. Cisco Unified Operating System Administration displays the old IP address of the Publisher. Enter the new IP address of the Publisher in the Edit box and click Save.

Step 5

Reboot the Emergency Responder Subscriber immediately, so that the Emergency Responder Publisher maintains communication with the Emergency Responder Subscriber.

Step 6

Verify the replication using the utils dbreplication status CLI command. The value on each server should equal two.

Step 7

Verify that the CTI ports are registered on the Emergency Responder Publisher server. If the CTI ports are not registered, you must recreate the CTI ports by deleting the ports and adding them back in again.

Related Tasks

Ethernet Configuration

Create Required CTI Ports

Ethernet Configuration

The Ethernet Configuration page appears when you choose Settings > IP > Ethernet.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Ethernet Configuration page.

Ethernet Configuration Page

Field

Description

DHCP Information

DHCP

Indicates whether DHCP is enabled or disabled and allows you to change the DHCP setting using the pull-down menu.

Host Information

Hostname

Displays the server name (Display only—Cannot configure).

Port Information

IP Address

Displays the IP address of the system. You can change the IP address by entering a new IP address in the text box.

Subnet Mask

Displays the IP subnet mask address. You can change the mask by entering a new subnet mask in the text box.

Gateway Information

Default Gateway

Displays 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.

Save button or icon

Saves any changes made to the Ethernet Configuration page.

Caution:
If you click Save, the machine reboots. Do not click Save unless you want to shut down and reboot your system.

Note:
To recognize any new IP addresses, both servers in the server group must be manually rebooted.

Create Required CTI Ports

Emergency Responder 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 that you configure is the number of simultaneous calls Emergency Responder can make to these personnel. It does not relate to the number of emergency calls Emergency Responder can handle or forward to the PSAP. There is no configurable limitation to the number of simultaneous emergency calls that Emergency Responder can handle.

Before You Begin
Emergency Responder 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.

Procedure

Step 1

Select Device > Phone.
Unified CM opens the Find and List Phones page.

Step 2

Click Add a New Phone.
Unified CM opens the Add a New Phone page.

Step 3

Select CTI Port for Phone Type and click Next.
Unified CM opens the Phone Configuration page.

Step 4

Configure the CTI Port, entering this information:

- Device Name- Enter something meaningful to you, for example, CTI3001.

- Device Pool- Select an appropriate device pool. This device pool must use the G.711 region.

- Calling Search Space- Select PhoneCSS.

Step 5

Click Insert.
Unified CM creates the CTI port and asks if you want to configure line 1. Click OK. Unified CM opens the Directory Number Configuration page.

Step 6

Configure line 1 for the CTI port, entering this information:

- Partition- Select Phones.

- Calling Search Space- Select 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.
Unified CM 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.

Change IP Address of Emergency Responder Subscriber

Before You Begin
Update the IP address information about your DNS server before you begin changing the IP address on the server.

Procedure

Step 1

Change the IP address on the Emergency Responder Subscriber by using one of the following options:

- In Cisco Unified Operating System Administration, enter the new IP address in Settings > IP > Ethernet.

- On the CLI, configure the new IP address with the set network ip command.

Step 2

Reboot the Emergency Responder Subscriber.

Step 3

After the Emergency Responder Subscriber is fully operational, reboot the Emergency Responder Publisher.

Step 4

Verify that the replication using the utils dbreplication status CLI command. The value on each server should equal two.

Related Tasks

Ethernet Configuration

Ethernet Configuration

The Ethernet Configuration page appears when you choose Settings > IP > Ethernet.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Ethernet Configuration page.

Ethernet Configuration Page

Field

Description

DHCP Information

DHCP

Indicates whether DHCP is enabled or disabled and allows you to change the DHCP setting using the pull-down menu.

Host Information

Hostname

Displays the server name (Display only—Cannot configure).

Port Information

IP Address

Displays the IP address of the system. You can change the IP address by entering a new IP address in the text box.

Subnet Mask

Displays the IP subnet mask address. You can change the mask by entering a new subnet mask in the text box.

Gateway Information

Default Gateway

Displays 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.

Save button or icon

Saves any changes made to the Ethernet Configuration page.

Caution:
If you click Save, the machine reboots. Do not click Save unless you want to shut down and reboot your system.

Note:
To recognize any new IP addresses, both servers in the server group must be manually rebooted.

Perform Restore Procedure

The following procedure 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.

Procedure

Step 1

Choose storage location. You must first choose the storage location from which you want to restore a backup file.

Step 2

Choose the backup file. From a list of available files, choose the backup file that you want to restore.

Step 3

Choose features. From the list of available features, choose the features that you want to restore.

Step 4

Choose server. If the feature was backed up from multiple servers, you must choose the servers that you want to restore.

Step 5

Check the status of the restore. While the restore process is running, you can check the status of the current restore job.

Related Tasks

Restore Backup File

View Restore Status

Restore Backup File

Disaster Recovery System adheres to strict version checking and allows restore only for matching versions of Emergency Responder.

The Restore Wizard leads you through the steps that are required to restore a backup.

Tip

To restore all servers in a server group, see Restore Entire Server Group.

Caution

Before you restore Emergency Responder, ensure that the Emergency Responder version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Emergency Responder for restore.

The product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Emergency Responder database restore.

Procedure

Step 1

Select Restore > Restore Wizard from the main Disaster Recovery System web page. The first page of the Restore Wizard (Step1 Restore—Choose Backup Device) appears.

Step 2

Choose the backup device to restore in the Select Backup Device area.

Step 3

Click Next. The Step 2 Restore—Choose the Backup Tar File page appears.

Step 4

Choose the backup file that you want to restore.
Note:
The backup filename indicates the date and time that the system created the backup file.

Step 5

Click Next. The Step 3 Restore—Select the Type of Restore page appears.

Step 6

Choose the features that you want to restore.
Note:
Only the features that were backed up to the chosen file are displayed.

Step 7

Click Next. The Step 4 Restore—Final Warning for Restore page appears.

Step 8

Click Restore to start restoring the data, . You are prompted to choose the server to restore.

Step 9

Choose the appropriate server.
Caution:
After you choose the server that you want restored, any existing data on that server will be overwritten.

Your data is restored on the server that you chose. To view the status of the restore, see View Restore Status.

Step 10

Restart the server.
Note:
The system can require one hour or more to restore depending on the size of your database and the chosen components.

View Restore Status

Procedure

Step 1

From the main Disaster Recovery System web page, select Restore > Status. The Restore Status page appears. The Status column in the Restore Status window shows the status of the restoration in progress, including the percentage of completion of the restore procedure.

Step 2

Click the log filename link to view the restore log file.

Update Emergency Responder Cluster Database Host Details

By default, each server in a cluster considers its own database to be the cluster database host. Because each cluster should have only one database host, you must update the cluster configuration accordingly.

For example, if you have two server groups (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. Update the cluster database host password for Servergroup A using Servergroup A's own host name.

2. Update the cluster database host password for Servergroup B by entering the IP address and cluster database password for Servergroup A.

3. Repeat Step 2 for other server groups 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 fails and cluster functionality is 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.

Note

This procedure only updates the Emergency Responder Cluster DB host details for this server group. Other servers in this Emergency Responder cluster do not updated automatically.

Before You Begin
You must reboot the server to update Emergency Responder Cluster DB host details. Only restarting Emergency Responder services does not work because the IP address is cached by other services.

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Select Update > Cluster DBHost from the main Emergency Responder Admin Utility page. The Update Cluster DB Host page appears.

Step 3

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.

Step 4

Enter the password for the new Cluster DBHost in the Password text box.

Step 5

Reenter the password for the new Cluster DBHost in the Confirm Password text box.

Step 6

Click Go.

Related References

Update Cluster DB Host

Update Cluster DB Host

The Update Cluster DB Host page appears when you choose Update > Cluster DB Host.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Update Cluster DB Host page to designate a new server as the Emergency Responder cluster database host server.

The following table describes the Update Cluster DB Host page.

Update Cluster DB Host Page

Field

Description

Status

Displays the name of the current cluster database host

Cluster DB Host Details

ClusterDB Hostname/IP Address

Enter the hostname (if DNS is configured) or the IP address of the new cluster database host.

Note:
If the cluster is spread across domains, then enter a fully qualified hostname.

Password

Enter the password for the new cluster database host

Confirm Password

Reenter the password for the new cluster database host.

Go button

Click the Go button to designate the new server as the new cluster database host.

Note:
The Emergency Responder Cluster DB host details are updated. Emergency Responder services must be restarted for this change to take effect. You must restart Emergency Responder Services by rebooting the Emergency Responder publisher and subscriber servers. Only restarting Emergency Responder services does not work because the IP address is cached by other services and this updates the Emergency Responder Cluster DB host details for this server group only. Other servers in this Emergency Responder cluster are NOT updated automatically. For further details, see Update Emergency Responder Cluster Database Host Details.

Cancel button

Cancels the Update Cluster DB Host operation.

Emergency Responder Onsite Alert Personnel Preparations

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder:

- How to use the Emergency Responder web interface. See the Emergency Responder user web interface online help for information about these topics. The online help includes a user's guide in PDF format that you can print out and distribute to your users. The information in the user's 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 and how to view specific (if set by the administrator) or all alerts in the system.

- 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.

- Explain how they receive notification of an emergency call.

- A web alert appears for everyone logged into the Emergency Responder 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 Emergency Responder 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 have for identifying the location of the emergency caller.

- Explain the organization's 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 Information

Preparing Your Staff for Emergency Responder

Preparing Your Staff for Emergency Responder

Emergency Responder does not replace your existing emergency procedures. Instead, Emergency Responder is a tool you can use to augment those procedures. Before deploying Emergency Responder, consider how it fits into your procedures and how you want to use the Emergency Responder system's capabilities.

These are the main things to consider when deciding how to use Emergency Responder:

- When someone makes an emergency call, Emergency Responder 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 helps them respond quickly to emergencies. Incorporating building names, floor numbers, and other readily understood location information in the name are the types of factors to consider.

- Emergency Responder lets you define three types of administrative user, so you can divide responsibilities for overall Emergency Responder 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 Emergency Responder 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 Data Integrity and Reliability for more information about maintaining data integrity.

Emergency Responder ERL Administrator Role

The following table lists the recurring tasks for which an ERL administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder ERL Administration Recurring Tasks

Recurring Task

Description

More Information

Assign ERLs to new or changed switch ports

If switches are added to the network, or if modules with additional ports are added to existing switches, assign the new ports ERLs.

Switch Port Configuration

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 Emergency Responder.

- ERL Creation

- Switch Port Configuration

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.

- Export ERL Information

- Export ALI Information for Submission to Your Service Provider

- ERL Creation

- ALI Submission and Service Provider Requirements

Audit the manually defined phones

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.

- Manually Define Phones

Audit the unlocated phones list

Regularly audit the unlocated phones list, and work with the network administrator to determine why Cisco Emergency Responder cannot locate the phones and to resolve the problems.

- Identify Unlocated Phones

- Unlocated Phones

Add new onsite personnel or remove old ones; update phone numbers

As onsite alert personnel are added, define them in Cisco Emergency Responder and assign them to the appropriate ERLs. Likewise, as personnel are removed, remove them from their ERLs and then from Cisco Emergency Responder. Update phone numbers, email address, and other contact information as they change.

- Add Onsite Security Personnel

- ERL Creation

Add IP subnet for the IP subnets to be tracked

If there is a new IP subnet that needs to be discovered by Emergency Responder, then perform the following tasks:

- Configure an ERL spanning the new IP subnet's geographical location.

- Configure this new IP subnet and the appropriate mask and assign this IP subnet to the created ERL.

- Set Up IP Subnet-based ERLs

Related Information

Phone Management

Phone Management

The following 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 Emergency Responder.

Emergency Responder Network Administrator Role

The following table lists the recurring tasks for which a network administrator is responsible. A system administrator can also perform these tasks.

Cisco Emergency Responder Network Administration Recurring Tasks

Recurring Task

Description

More Information

Add new switches

Add any switches that you add to the network to the Cisco Emergency Responder configuration. A switch is considered new if it has an IP address not defined in Cisco Emergency Responder.

- LAN Switch Identification

- Manually Run the Switch-Port and Phone Update Process

Remove old switches

Remove switches from the Cisco Emergency Responder configuration if you remove them from the network. Nonexistent switches in the Cisco Emergency Responder configuration do not create problems, but they do increase the time required to do phone tracking, because Cisco Emergency Responder attempts to connect to the switch must time out before moving on to the next switch.

- LAN Switch Identification

Update the SNMP read community if it changes

If you change the read community string on any defined switch, you must update the SNMP settings in Cisco Emergency Responder. Until the setting is updated, Cisco Emergency Responder cannot track phones attached to the switch.

- Set Up SNMPv2

Update or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder system administrator.

- Identify Cisco Unified Communications Manager Clusters

Check ERL assignments

Use the ERL Debug Tool to check that the correct and expected ERL is used for a selected phone.

- Emergency Responder Admin Utility

Related Information

Emergency Responder Switch Configuration

Emergency Responder Switch Configuration

Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. The following topics describe the switch requirements and how to identify switches to Emergency Responder.

Emergency Responder System Administrator Role

The following table 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 Emergency Responder ERL Administrator Role and the Emergency Responder Network Administrator Role.

Cisco Emergency Responder System Administration Recurring Tasks

Recurring Task

Description

More Information

Add additional Cisco Emergency Responder groups

As telephones are added to the network, you might need additional Cisco Emergency Responder groups. Install and define them and their telephony settings.

Work with the telephony administrator to complete the required Unified CM configuration.

- Installation on a New System

- Set Up Server Group

- Set Up Group Telephony Settings for Server

- Configure Servers

- Identify Cisco Unified Communications Manager Clusters

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.

Create new Cisco Emergency Responder users; remove old users

As onsite alert personnel change, or as Cisco Emergency Responder system, network, and ERL administrators change, add or remove them as required.

- Emergency Responder User Management

Add or remove Unified CM servers

If a Unified CM cluster is added to the network, or one is removed, update the configuration for the Cisco Emergency Responder group that supports the cluster. Although you have the authority to make these updates, your organization might assign the primary responsibility to the Cisco Emergency Responder network administrator.

- Identify Cisco Unified Communications Manager Clusters

Monitor the email alerts that Cisco Emergency Responder generates

If your email ID is configured in the server group settings, Cisco Emergency Responder sends email alerts about critical errors to you. You are expected to understand the error and take action to correct the problem.

See Troubleshoot Email Alerts for information to help you understand the email alerts and resolve problems.

- Set Up Server Group

Related Information

Server and Server Group Configuration

Troubleshoot Email Alerts

Server and Server Group Configuration

The information in the following topics describe how to configure Emergency Responder servers and server groups, and the telephony connection between the Emergency Responder groups and Unified CM.

Troubleshoot Email Alerts

The following sections describe how you troubleshoot problems related to the email alerts generated by Emergency Responder.

Unlocated Phones

Emergency Responder obtains a list of registered phones from Unified CM and tries to locate all phones. If Emergency Responder 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 is 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 Emergency Responder can resolve some of the problems automatically. See Manually Run the Switch-Port and Phone Update Process for more information.

These are some of the situations that can prevent Emergency Responder from locating a phone:

- If more than one switch port reports the phone as a Cisco Discovery Protocol (CDP) neighbor, then the phone is placed in unlocated phones. This condition is corrected in the next phone tracking when only one switch port reports this phone as its CDP neighbor.

- The phone is attached to a switch that is not defined in Emergency Responder. See LAN Switch Identification for information about 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 Network Hardware and Software Requirements for a list of supported switches. See Manually Define Phones for information about 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. Emergency Responder 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 Emergency Responder. Correct the Emergency Responder configuration. See Set Up SNMPv2.

- The phone requires CAM table access, but CAM tracking is not enabled for the switch in Emergency Responder. See LAN Switch Identification.

- There is a network outage preventing communication between the Emergency Responder server and the switch. Locate and resolve the network outage problem.

Unreachable switches are not retried until Emergency Responder runs the next full switch port and phone update process, unless you run it against the individual switch.

- The phone has moved to a switch served by a different Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list. If the phone is not in the next incremental phone tracking process after it is moved, the phone remains unlocated in any Emergency Responder 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 LAN Switch Identification for information about enabling CAM-based tracking, and Network Hardware and Software Requirements for a list of phones that require CAM-based tracking.

After fixing the problems that are preventing Emergency Responder 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 switch—Select 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 switches—Select Phone Tracking > Run Switch-Port & Phone Update.

Related Tasks

Identify Unlocated Phones

Related Information

IP Subnet Phones

Cisco Unified OS CLI Commands

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

IP Subnet Phones

The IP Subnet Phones page appears when you choose ERL Membership/ IP Subnets and click the View Phones icon in any records returned by the IP Subnet Search.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the IP subnet Phones page to view all the IP subnet phones discovered by Emergency Responder.

The IP subnet phones page displays the subnet ID, the subnet mask for each IP subnet and lists all the phones tracked in that IP subnet, and when the last phone was tracked.

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 Emergency Responder 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.

Wrong ERL Used for Shared Line

When two or more phones with a shared line appearance move from switches that are monitored by one Emergency Responder group to switches that are monitored by a different Emergency Responder group, then Emergency Responder may assign an incorrect ERL to these phones during an emergency call. This situation can occur when the phones move to a different campus that has a different Unified CM cluster (although the moved phones are still registered with the original Unified CM cluster), and it can also occur when the phones move within a single large campus that is served by multiple Unified CM clusters.

Because the moved phones are still registered to their original Unified CM cluster, emergency calls from these phones are routed to the original Emergency Responder group. In this case, the Emergency Responder group detects that the calling phone is connected to a switch that is monitored by a different Emergency Responder group, and the call is forwarded to the appropriate Emergency Responder 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 Emergency Responder 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 Emergency Responder group, this is not a problem. However, when multiple phones with a shared line appearance connect to switches monitored by the receiving Emergency Responder group, then Emergency Responder 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 Information

Two Main Site Deployments

Two Main Site Deployments

The following figure illustrates the Emergency Responder configuration with two (or more) main sites, each served by a separate PSAP.

Deploying Cisco Emergency Responder in Two Main Sites

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 Deployment in Main Site with Satellite Offices for information about deploying Emergency Responder in those offices.

If a main site is served by more than one PSAP, see Deployment in Main Site with Two or More PSAPs for information about deploying Emergency Responder in that site. To support this type of network:

- Install two Emergency Responder 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 Emergency Responder Publisher server in the Chicago Emergency Responder group for use as the cluster database. See Set Up Emergency Responder Cluster and Cluster DB Host.

- Install two Emergency Responder 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 Emergency Responder Publisher server in the Chicago Emergency Responder group for use as the cluster database. See Set Up Emergency Responder Cluster and Cluster DB Host.

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 provider's network (you might have different service providers). Consult with your service provider to determine the requirements for your buildings. 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 provider's network, configure all route patterns used in Chicago's ERLs to use gateway CHI, and all route patterns used in New York's ERLs to use gateway NYC.

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-Emergency Responder group route pattern so that Emergency Responder can transfer calls between Cisco Unified Communications Manager clusters served by separate Emergency Responder groups.

As phones move between sites, Emergency Responder dynamically updates their ERLs so that emergency calls get routed out of the desired gateway. However, if the WAN link becomes unavailable, Emergency Responder cannot track phone movement between the sites.

Wireless Endpoints Using Unexpected ERL

Wireless endpoints (such as Cisco Wireless IP 7920 Phones and Cisco IP SoftPhones) may be using switch port-based ERL instead of the configured subnet-based ERL.

Cisco Emergency Responder (Emergency Responder) give a higher priority to switch port association for call routing. If Emergency Responder finds a switch port mapping for any endpoint (including wireless 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, Emergency Responder routes emergency calls using subnet-ERL configuration.

See the switch port screen or the ERL debug tool (see Check Emergency Responder Configuration Using ERL Debug Tool) to check if the wireless endpoint is associated with a switch port.

It is recommended that you track wireless endpoints using subnet-based ERLs.

Related Tasks

Set Up IP Subnet-based ERLs

Set Up IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Emergency Responder supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco Emergency Responder then routes the emergency calls based on the configured IP subnet and ERL associations.

This feature is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.

Use IP subnet-based ERLs to locate and track wireless endpoints, such as Cisco Unified Wireless IP Phone 7920 series devices and Cisco clients using wireless IP connection. Cisco Emergency Responder cannot locate or track wireless endpoints to a Cisco Access Point.

Note

Subnet-based tracking is limited by the IP subnet addressing plan. It cannot distinguish location within a same IP Subnet.

Before You Begin
You must have system administrator or ERL administrator authority to access this page.

Procedure

Step 1

Select ERL Membership > IP subnets and click the Add new IP subnet link on the Find and List IP Subnets page.
Emergency Responder opens the Configure IP Subnets page.

Step 2

At the Subnet ID field, enter the IP address of the subnet that you want to define, for example,10.76.35.0.

Step 3

At the Subnet Mask field, enter the mask of the subnet that you want to define, for example, 255.255.255.224.

Step 4

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.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the subnet and click Select ERL. The Find ERL page closes.

Step 7

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

To change the fields on this page back to the last saved settings, click Cancel Changes.

Step 9

To return to the Find and List IP Subnets page, click Back to IP Subnet Search.

Troubleshoot Licensing

Emergency Responder licensing is managed by Prime License Manager. Prime License Manager manages licensing fulfilment, and supports the allocation and the reconciliation of licenses across supported products. Prime License Manager also provides enterprise-level reporting of usage and entitlement, including status messages.

Related References

E911 and Cisco Emergency Responder Terminology

Emergency Responder Licensing

Upload License File

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Emergency Responder Licensing

Cisco Prime License Manager centralizes all of the licensing for Emergency Responder Release 10.0 and later releases.

Emergency Responder communicates the licensing requirements to Cisco Prime License Manager. Emergency Responder attempts to discover all phones on Unified Communications Manager, excluding subnets not tracked by Emergency Responder. Along with the manually configured phones, Emergency Responder builds and sends the corresponding license requirements to the Cisco Prime License Manager. The Cisco Prime License Manager then compares the Emergency Responder license requirements with the licenses installed and reports back license compliance or noncompliance.

For more information, refer to the Enterprise License Manager User Guide.

Upload License File

Cisco Prime License Manager maintains the licensing for Cisco Emergency Responder 10.0 and later.

Use the Prime License Manager tool to obtain licenses from Cisco, to install the licenses, and to manage and view your inventory of licenses. This tool also tracks license compliance or noncompliance.

Emergency Responder Groups in Cluster Screen Does Not Load and Displays a Cannot Connect to Cluster DB Host Error

Problem    The Emergency Responder Groups in Cluster screen does not load, and exhibits the error "Cannot connect to cluster DB host."

Solution    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 Emergency Responder server groups in the cluster.

For more information, see Set Up Emergency Responder Cluster and Cluster DB Host.

Related Tasks

Identify Emergency Responder Groups and Servers in Cluster

Manage Emergency Responder Server

Related Information

Event Messages

Performance Management

Data Backup and Recovery

Identify Emergency Responder Groups and Servers in Cluster

If you are connected to the administrator interface on a Emergency Responder server, you can view the details of the server and the Emergency Responder group's standby server by selecting System > Cisco ER Group Settings.

You can also identify the Emergency Responder groups and their Emergency Responder servers that are in the same Emergency Responder cluster. To view the other Emergency Responder groups in the cluster, select System > Cisco ER Groups in Cluster. From the Emergency Responder Groups in Cluster page, select the group that you want to view; and Emergency Responder displays the Emergency Responder servers that are in the group. To view the details for these servers, you must log into the Emergency Responder Administration interface running on one of the servers, select System > Cisco ER Groups in Cluster, then select the group that you want to view from the list of groups.

If you must uninstall a Emergency Responder group, first delete the group from the Emergency Responder cluster using this page. You must log in as a system administrator to delete the group. Deleting the group from the cluster only removes the entries for the group from the Emergency Responder Cluster DB; it does not remove Emergency Responder from the group's servers.

Manage Emergency Responder Server

When you install Emergency Responder, the Emergency Responder server is set up to automatically start whenever the computer is powered up or rebooted. However, you can stop and then restart an Emergency Responder server through the Emergency Responder Serviceability web interface without powering down or rebooting the computer.

Procedure

Step 1

Log in to the Emergency Responder Serviceability web interface and select Tools > Control Center. The Control Center Services page displays, showing all Emergency Responder 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.
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.

The following table explains the meaning of the icons that you see on the Control Center Services page.

Cisco Emergency Responder Control Center Icons

Icon

Meaning

The Emergency Responder server or the Emergency Responder Phone Tracking Engine is started and functioning normally.

The Emergency Responder server Emergency Responder Phone Tracking Engine was stopped by the administrator.

Event Messages

You can view Emergency Responder event messages to help diagnose problems with the software by using the Emergency Responder Serviceability web interface.

For information about viewing Emergency Responder events, see Use Event Viewer.

For details about the Find and List Events page, see Event Viewer.

Performance Management

See the latest version of the Release Notes for Cisco Emergency Responder for supported platforms and their Emergency Responder scalability.

Emergency Responder performance can be affected if Emergency Responder is managing switches across a WAN link. Emergency Responder 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 Set Up SNMPv2 for more information.

Data Backup and Recovery

Emergency Responder uses the Disaster Recovery System to backup and restore system data.

For information about using the Disaster Recovery System, see Configure Cisco Emergency Responder Disaster Recovery System

Identify Emergency Responder Groups and Servers in Cluster

If you are connected to the administrator interface on a Emergency Responder server, you can view the details of the server and the Emergency Responder group's standby server by selecting System > Cisco ER Group Settings.

You can also identify the Emergency Responder groups and their Emergency Responder servers that are in the same Emergency Responder cluster. To view the other Emergency Responder groups in the cluster, select System > Cisco ER Groups in Cluster. From the Emergency Responder Groups in Cluster page, select the group that you want to view; and Emergency Responder displays the Emergency Responder servers that are in the group. To view the details for these servers, you must log into the Emergency Responder Administration interface running on one of the servers, select System > Cisco ER Groups in Cluster, then select the group that you want to view from the list of groups.

If you must uninstall a Emergency Responder group, first delete the group from the Emergency Responder cluster using this page. You must log in as a system administrator to delete the group. Deleting the group from the cluster only removes the entries for the group from the Emergency Responder Cluster DB; it does not remove Emergency Responder from the group's servers.

Related References

Server Groups in Cluster

Server Groups in Cluster

The Emergency Responder Server Groups in Cluster page appears when you choose System > Cisco Emergency Responder Groups in Cluster.

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the Emergency Responder Server Groups in Cluster page to view the Emergency Responder groups that form an Emergency Responder cluster. You can view which Emergency Responder servers belong to each Emergency Responder group within the cluster. You can click on the link for the remote server groups in an Emergency Responder cluster (select either the primary server or the backup server) to go directly to the Emergency Responder interface for these servers.

The following table describes the Emergency Responder Server Groups in Cluster page.

Cisco Emergency Responder Server Groups in Cluster Page

Field

Description

Notes

Emergency Responder Groups

Emergency Responder Groups list

A list of the Emergency Responder server groups that are pointing to the same cluster database host.

Click a group name to view the servers in the group.

The Emergency Responder cluster consists of this set of Emergency Responder groups. You create the cluster when installing Emergency Responder servers. See Installation on a New System.

Servergroup Details

Emergency Responder Group Name

The name of the server group.

Click the server group name to display the servers in that group in the Servergroup Details section of page.

Primary Host Name

The DNS host name or IP address of the primary server in the group.

Click this host name (except for the local server group) to open the Emergency Responder administration page for that server in a new window.

Standby Host Name

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 Emergency Responder administration page for that server in a new window.

Delete button

Click Delete to remove the Emergency Responder group you are viewing from the Emergency Responder cluster.

Only system administrators can delete a Emergency Responder group from the cluster.

Delete a group from the cluster before you uninstall a Emergency Responder group.

Manage Emergency Responder Server

When you install Emergency Responder, the Emergency Responder server is set up to automatically start whenever the computer is powered up or rebooted. However, you can stop and then restart an Emergency Responder server through the Emergency Responder Serviceability web interface without powering down or rebooting the computer.

Procedure

Step 1

Log in to the Emergency Responder Serviceability web interface and select Tools > Control Center. The Control Center Services page displays, showing all Emergency Responder 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.
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.

The following table explains the meaning of the icons that you see on the Control Center Services page.

Cisco Emergency Responder Control Center Icons

Icon

Meaning

The Emergency Responder server or the Emergency Responder Phone Tracking Engine is started and functioning normally.

The Emergency Responder server Emergency Responder Phone Tracking Engine was stopped by the administrator.

Related References

Control Center

Control Center

The Control Center page appears when you choose Tools > Control Center.

Authorization Requirements

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.

The following table describes the Control Center page.

Control Center Page

Field

Description

Start button

Starts the selected services.

Stop button

Stops the selected services.

Restart button

Restarts the selected services.

Refresh button

Refreshes the list of currently running services on the selected server.

Service Name

Names of the currently running services on the selected server. To select a service, click the radio button next to the service name.

Status

Current status of the selected service.

Enable Emergency Responder Trace and Debug Information

Procedure

Step 1

From the Emergency Responder web interface, select Cisco ER Group > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

From the left column, select the server from which you must collect debug or trace information.
Emergency Responder displays the settings for the server.

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_DATABASE—The database subsystem, covers the log information generated by the database access code.

- CER_REMOTEUPDATE—The remote update subsystem, which manages updates between servers.

- CER_PHONETRACKINGENGINE—The phone tracking subsystem, which runs the phone tracking and switch port and phone update processes.

- ER_ONSITEALERT—The onsite alert subsystem for notifying onsite alert personnel.

- CER_CALLENGINE—The call engine subsystem, which routes and processes calls.

- CER_SYSADMIN—The system administration web interface subsystem.

- CER_TELEPHONY—The telephony subsystem, used for interactions with Unified CM.

- CER_AGGREGATOR—The aggregator module covers all Emergency Responder server communication and data handling with the phone tracking engine. The module includes the search and lookup of tracked data for the subsystems such as cluster, Administration, Cisco IP SoftPhone, and call routing.

- CER_GROUP—The Emergency Responder server group subsystem used for communicating between servers within a group.

- CER_CLUSTER—The server cluster subsystem used for communicating between Emergency Responder groups in a cluster.

Step 4

Click Update to save and activate your changes.
Emergency Responder begins generating the requested trace and debug information.

Note:
The traces for Emergency Responder can be collected from either Emergency Responder Serviceability web interface or by using the CLI.

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. Click Update to complete the change.

Related References

Server Settings for Emergency ResponderServerGroup

Related Information

Cisco Emergency Responder Serviceability Web Interface

Server Settings for Emergency ResponderServerGroup

The Server Settings for Emergency ResponderServerGroup page appears when you choose System > Server Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Emergency Responder servers are inserted in the Emergency Responder group when the Emergency Responder services are started. (See Installation on a New System.)

Use the Server Settings for Emergency ResponderServerGroup page to update server settings, for example, to change the server name or to change the trace and debug settings, or to delete servers.

Note

You cannot modify the host name of the server.

The following table describes the Server Settings Emergency ResponderServerGroup page.

Server Settings for the Emergency ResponderServerGroup Page

Field

Description

Notes

Status

Displays the status of the Server Settings Emergency ResponderServerGroup page.

Select Server

Server

List of servers you have already created. Click on a server name to see the settings for that server.

You can configure a maximum of two servers per server group.

Modify Server Settings

Server Name

The name of the server.

Change this server name field to any desired value.

Host Name

The DNS name of the Emergency Responder server.

This field cannot be modified.

Debug Package List

A selection of subsystems for which you must collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Debug Package List.

Clear All button

Clears all selected subsystems in the Debug Package List.

Trace Package List

A selection of subsystems for which you must collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's 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.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Trace Package List.

Clear All button

Clears all selected subsystems in the Trace Package List.

Update Settings button

Click Update when viewing an existing server's settings to save changes you make to the settings.

Only available when viewing the settings of an existing server.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Cisco Emergency Responder Serviceability Web Interface

Collect Information From Syslog

You can configure Emergency Responder to use Syslog output from Emergency Responder for use with other network management systems.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select enable in Enable Syslog.

Step 3

Enter the fully qualified DNS name of the server in the Syslog Server field, for example, server.domain.com.

Step 4

Click Update Settings to save your changes.
Emergency Responder immediately begins writing messages to syslog.

Related References

Group Settings

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page—English or French (Canadian).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Data Backup and Recovery

Emergency Responder uses the Disaster Recovery System to backup and restore system data.

For information about using the Disaster Recovery System, see Configure Cisco Emergency Responder Disaster Recovery System

Related Information

Call History Logs

Call History Logs

Emergency Responder 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.

Emergency Responder maintains in its database a history of the emergency calls that have been placed. When the primary Emergency Responder server (Publisher) is not active, emergency calls are handled by the backup Emergency Responder 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 Emergency Responder servers.

To download these records, click the Download button at the top of the table displaying the call history. These records are downloadable in Excel (.xls) format.

JTAPI Incompatibility Warning

As an administrator, you will be alerted if the Unified CM version configured on Emergency Responder differs from the version to which Emergency Responder route points are registered, so that you can take corrective action and assure that emergency calls are processed correctly. An email alert will be sent to the configured email address using SMTP mail server.

Ensure that email alerts for Emergency Call Routing Parameters are enabled under Email Alert Settings on the Emergency Responder administration pages.

The error is also displayed on the Event Viewer page. See the Related Links below.

Alert would be as follows:

Unified CM at <IP address> is version CUCM x which differs from CUCM version setting CUCM y on Cisco Emergency Responder.

This warning could occur in the following cases:

- Unified CM version is no longer supported; for example, Unified CM 2.0 integrated with Cisco Emergency Responder 8.7 or 9.0

- Unified CM version is not yet supported; for example, Unified CM 9.5 integrated with Cisco Emergency Responder 8.7 or 9.0

- Unified CM version is supported, but Unified CM version setting on Emergency Responder is incorrect; for example, Unified CM 9.0 integrated with Cisco Emergency Responder 8.7 or 9.0, but Emergency Responder Unified CM version setting is Unified CM 7.1

Multiple Unified CM versions in the same Emergency Responder will always cause one of the above situations.

Related Information

Event Viewer

Event Viewer

The Event Viewer page appears when you choose Tools > Event Viewer.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Event Viewer page to view Emergency Responder events for the previous six months.

The following table describes the Event Viewer page.

Event Viewer Page

Field

Description

Type pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down 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 pull-down menu to the right of the Type pull-down menu.

Module pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down menu to the right changes to display the available Type or Module options.

Allows you to select the Emergency Responder module for which you want to view events. When you select Module from the pull-down 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

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.

Type column

Displays the type of event. The Type column displays one of the following:

- INFO

- WARN

- ERROR

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.

Module column

Displays the Emergency Responder 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.

Generate Formatted ALI File

Procedure

Step 1

Provide a NENA 2.0 file generated by Emergency Responder as input to AFT by following these steps:

1. From the Emergency Responder Administration web page, go to Tools > ALI Formatting Tool.

2. Click your service provider name in the menu.

3. Select an Input File for the ALI Formatting Tool from the list of files provided in the pull-down menu.
AFT displays all the ELINs from the NENA file.

Step 2

Click on an ELIN link to view details of the ALI files. The ALI Record Details for ELIN are populated in the right pane of the screen.

Step 3

Edit the ALI fields by entering new values in the editable fields.

Step 4

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.

Step 5

Update the service provider fields in AFT.
For details about the service provider-specific information required, see Using AFT for Specific Service Providers

Step 6

At this point, if you want to edit some fields in many ELINs simultaneously, you can use the AFT Bulk Update feature. To do so, follow these steps:

1. Select the ELINs to edit using Bulk Update.

2. Click on the Bulk Update button. The Bulk Update form appears.

3. For details about the service provider-specific information required, see Using AFT for Specific Service Providers

Step 7

Generate a formatted file by following these steps:

1. Click on the Review Changes/Generate File button.
The list of edited ELINs are displayed. You can add unchanged ELINs and remove edited ELINs from the list.

2. Select the ELINs that will be part of the final formatted file and enter the name for the formatted file.

3. 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:
Before generating the formatted file, verify the details entered.

Step 8

Using the service provider's preferred method of transmitting files, send the ALI file to your service provider so that 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 is helpful if the service provider reports errors; you can make any required changes to the file without having to re-do all of 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:

1. 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. See 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 Emergency Responder to correct the fields. Then use AFT to regenerate the file.

2. Send the corrected file to your service provider. Be sure to keep a copy of your corrected file for your records.

3. Repeat this process until your service provider can read the formatted files and can use them to update their ELIN records.

Related Tasks

Convert ALI Data

Related References

ALI Formatting Tool

Convert ALI Data

Use the PS-ALI Converter tool to generate an ERL csv (Comma Separated Value) text file that can be accepted by the Emergency Responder ERL. You must first upload an existing ALI file in NENA 2.0 format to Emergency Responder before converting it.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

To convert ALI data, follow these steps:

Procedure

Step 1

Select Tools > PS-ALI Converter.
Emergency Responder displays the PS-ALI Converter page.

Step 2

Click the Upload PSALI file button to upload an ERL file in NENA 2.0 format. The Upload File page appears.

Step 3

Follow the instructions in the Upload File to upload the ERL file.

Step 4

Select the uploaded file from pulldown menu.

Step 5

In the Output file (in csv format) Name field, enter the name of the converted csv file you want to create.

Step 6

Click Convert to create the csv file.
The generated csv file is in the following folder:

%cerroot%/import
You can import the file or download the file using the File Manager utility.

Step 7

Modify the converted csv file as needed. For example, add the ERL name, route pattern, and security details to update the ERL.

Step 8

Click Close to close the window.

ALI Formatting Tool

The ALI Formatting Tool page appears when you choose Tools > ALI Formatting Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder 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

The following table describes the ALI Formatting Tool page.

ALI Formatting Tool Page

Field

Description

Select a Service Provider

Use the pull-down menu to select a service provider

Select an Input File for the ALI Formatting Tool from the List Below

Use the pull-down menu to select an input file

Submit button

Click the Submit button to display the Search for ELINs page, which is described in Table 2.

The following table describes the Search for ELINs page.

Search for ELINs Page

Field

Description

Use Search to Filter-out ELINs on Area, City and Local Code(last 4-digits).

Allows you to search ELINs by Local Code, Area Code, or City Code.

Add (+) button

Adds more search parameters

Remove (-) button

Removes search parameters

The following table describes the Bulk Update page.

Bulk Update Page

Field

Description

Remove Changes/Generate File button

Shows all the ELINs that have been changed.

Search for ELIN

Displays the ELIN search page.

The following table describes the Review Changes/Generate File page.

Review Changes/Generate File Page

Field

Description

Add More ELIN

Displays the remaining ELINs that have not been changed.

Remove ELIN

Removes the selected ELINs from the list

Search for ELIN

Displays the ELIN search screen

Generate File button

Generates the formatted file.

The following table describes the Download Formatted File page.

Download Formatted File Page

Field

Description

Download Formatted File button

Displays a Download File dialog box so that the formatted file can be downloaded to the local system.

Server Groups in Cluster

The Emergency Responder Server Groups in Cluster page appears when you choose System > Cisco Emergency Responder Groups in Cluster.

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the Emergency Responder Server Groups in Cluster page to view the Emergency Responder groups that form an Emergency Responder cluster. You can view which Emergency Responder servers belong to each Emergency Responder group within the cluster. You can click on the link for the remote server groups in an Emergency Responder cluster (select either the primary server or the backup server) to go directly to the Emergency Responder interface for these servers.

The following table describes the Emergency Responder Server Groups in Cluster page.

Cisco Emergency Responder Server Groups in Cluster Page

Field

Description

Notes

Emergency Responder Groups

Emergency Responder Groups list

A list of the Emergency Responder server groups that are pointing to the same cluster database host.

Click a group name to view the servers in the group.

The Emergency Responder cluster consists of this set of Emergency Responder groups. You create the cluster when installing Emergency Responder servers. See Installation on a New System.

Servergroup Details

Emergency Responder Group Name

The name of the server group.

Click the server group name to display the servers in that group in the Servergroup Details section of page.

Primary Host Name

The DNS host name or IP address of the primary server in the group.

Click this host name (except for the local server group) to open the Emergency Responder administration page for that server in a new window.

Standby Host Name

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 Emergency Responder administration page for that server in a new window.

Delete button

Click Delete to remove the Emergency Responder group you are viewing from the Emergency Responder cluster.

Only system administrators can delete a Emergency Responder group from the cluster.

Delete a group from the cluster before you uninstall a Emergency Responder group.

Related Tasks

Identify Emergency Responder Groups and Servers in Cluster

Related References

E911 and Cisco Emergency Responder Terminology

Identify Emergency Responder Groups and Servers in Cluster

If you are connected to the administrator interface on a Emergency Responder server, you can view the details of the server and the Emergency Responder group's standby server by selecting System > Cisco ER Group Settings.

You can also identify the Emergency Responder groups and their Emergency Responder servers that are in the same Emergency Responder cluster. To view the other Emergency Responder groups in the cluster, select System > Cisco ER Groups in Cluster. From the Emergency Responder Groups in Cluster page, select the group that you want to view; and Emergency Responder displays the Emergency Responder servers that are in the group. To view the details for these servers, you must log into the Emergency Responder Administration interface running on one of the servers, select System > Cisco ER Groups in Cluster, then select the group that you want to view from the list of groups.

If you must uninstall a Emergency Responder group, first delete the group from the Emergency Responder cluster using this page. You must log in as a system administrator to delete the group. Deleting the group from the cluster only removes the entries for the group from the Emergency Responder Cluster DB; it does not remove Emergency Responder from the group's servers.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Group Settings

The Emergency Responder Group Settings page appears when you choose System > Cisco ER Group Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Emergency Responder Group Settings page to define the operational characteristics of a Emergency Responder server group.

The following table describes the Emergency Responder Server Group Settings page.

Cisco Emergency Responder Group Settings Page

Field

Description

Notes

Emergency Responder Group Name

The name of the server group. This name is used for your information only, so create a name you find useful.

Peer TCP Port

The TCP port used for communications between Emergency Responder servers within the server group. If you do not want to use the default port, ensure you select an unused port.

The range is 1024 to 65535.

Heartbeat Count

The number of counts an Emergency Responder server should wait before declaring an unresponsive Emergency Responder server unavailable.

The default number of counts is 3. The range is 3 to 10.

The time between counts is defined in Heartbeat Interval.

Heartbeat Interval

The number of seconds between sending heartbeat messages to the other Emergency Responder server in the server group.

The default is 30 seconds. The range is 30 to 300 seconds.

Active Call Timeout

How long to maintain a call route mapping so the PSAP can call back the emergency caller.

The default is 180 minutes (3 hours). The range is 30 to 1440 minutes.

SMTP Mail Server

The IP address or fully qualified name of the mail server (for example, email.domain.com).

Configure an email server if you want Emergency Responder to send email or email-based pages to security officers when an emergency call is made.

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.

Emails or pages sent to security come from this email account.

System Administrator Mail ID

Mail account where Emergency Responder sends critical information about the system.

Emails or pages sent to the system administrator by Emergency Responder come to this email account.

Enable Calling Party Modification

Dynamic modification of the calling party number. Allows you to reduce the number of route patterns by configuring multiple ELIN numbers for a single route pattern. ELIN numbers still must be unique.

You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Unified CM user.

Syslog

Pull-down menu that enables and disables the writing of log messages.

Syslog Server

The name of the server that has the log messages.

Enter the fully qualified DNS name of the server, for example, cw2k.domain.com.

You can only enter a server name if you choose Enable Syslog.

Notes

Any notes you want to enter to help you understand the use of the server group.

Dynamic Tracking of Switch IP Address

Dynamically updates a LAN switch's IP address if it is configured with hostname in Emergency Responder.

This action is not applicable to LAN switches that are added to Emergency Responder using an IP address.

Security end user web interface language

Pulldown menu allows you to select the language that is displayed on the users web page— English (US), French (Canada) or Spanish (Spain).

After you change the language, you must complete the following before the language is displayed on the users web page:

- Restart Emergency Responder Service in Emergency Responder Serviceability by choosing Tools>Control Center.

- Restart Cisco Tomcat service using the CLI command utils service restart Cisco Tomcat.

- Refresh the current Emergency Responder User webpage.

Limit Concurrent Sessions

Limits the number of concurrent sessions per user.

Selecting or deselecting this check box enables or disables the Max. number of concurrent sessions drop-down list.

Max. number of concurrent sessions

If Limit Concurrent Sessions is enabled, this limit is applicable for all the users.

The limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related Tasks

Set Up Server Group

Collect Information From Syslog

Restrict Maximum Number of Concurrent Sessions

Track Change of Switch IP Address Dynamically

Related References

E911 and Cisco Emergency Responder Terminology

Set Up Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings, as described in the Group Settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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 Add Onsite Security Personnel), 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada), select it in the drop-down box. The default language is English.
Note:
The drop-down box provides a selection for Spanish (Spain) Voice Alerts only. When selected, the web interface remains in default English.

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Collect Information From Syslog

You can configure Emergency Responder to use Syslog output from Emergency Responder for use with other network management systems.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select enable in Enable Syslog.

Step 3

Enter the fully qualified DNS name of the server in the Syslog Server field, for example, server.domain.com.

Step 4

Click Update Settings to save your changes.
Emergency Responder immediately begins writing messages to syslog.

Restrict Maximum Number of Concurrent Sessions

Emergency Responder allows the administrator to restrict the maximum number of concurrent sessions that can be active at a time for any user. If this restriction is enabled, the administrator can specify a maximum limit (between 1 and15) for the number of concurrent sessions allowed.

This limit is applicable to all users configured in Emergency Responder.

Emergency Responder restricts users from creating more than the specified number of concurrent sessions. Users who attempt to create additional sessions that exceed the concurrent session limit are prevented from logging in to Emergency Responder and will see the following error message: Session limit exceeded. Please log out of any existing sessions and try again.

Note

This limit is applicable to all users that exceed the limit.

Note

This limit is imposed separately for each Emergency Responder website:

- Emergency Responder Administration

- Emergency Responder Serviceability

- Emergency Responder User

- Emergency Responder Admin Utility

Warning

If a user logs in to an Emergency Responder website and closes the browser without logging out, the session remains active until it times out after a period of 30 minutes. During this period, if the user attempts to establish additional sessions beyond the prescribed limit, he will be unable to do so.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Check the Limit Concurrent Sessions check box. This option is used to enable limiting the number of concurrent sessions and enables the Max. number of concurrent sessions drop-down box.

Step 3

Select the maximum number of concurrent sessions that you want to impose on the Emergency Responder user, from the Max. number of concurrent sessions drop-down box.

Step 4

Click the Update Settings button to apply the new change.
Note:
You can disable the maximum number of concurrent settings by selecting System > Emergency Responder Group Settings and uncheck the Limit Concurrent Sessions check box.

Track Change of Switch IP Address Dynamically

Emergency Responder allows you to dynamically track the change in a LAN switch IP address managed by Emergency Responder. This feature is intended for LAN switches that have been added using the switch hostname.

Before You Begin
You must have system administrator authority to enable dynamic tracking of a LAN switch IP address.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Select the Dynamic Tracking of Switch IP Address check box to dynamically track a switch's IP address.

Step 3

Click the Update Settings button to apply the change.
You must wait for the next Incremental Discovery cycle to start. During this cycle Emergency Responder detects the new IP address of the LAN switch and updates its database. You will be notified of this change detection from an entry in the Emergency Responder Event Viewer and with an administrative email alert.

Note:
It is recommended that you enable Dynamic Tracking of Switch IP Address only during a scheduled maintenance window when the switch is subject to an actual change of IP address. It is recommended that you disable this option during normal periods as this operation is CPU intensive.

Note:
For a LAN switch that has been added using the IP address, Emergency Responder cannot track any change in its IP address. In this case, you must delete the switch and add it again with the new IP address.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Telephony Settings

The Telephony Settings page appears when you choose System > Telephony Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Telephony Settings page to define the telephone numbers and telephony ports used by the Emergency Responder group.

The following table describes the Telephony Settings page.

Telephony Settings Page

Field

Description

Notes

Specify telephony attributes

Route Point for Primary Emergency Responder Server

The CTI route point that the primary server should use, such as 911.

See Create Emergency Call Route Points for more information.

Route Point for Standby Emergency Responder Server

The CTI route point that the standby server should use, such as 912. Configure this number as the call forward number for the primary emergency number.

See Create Emergency Call Route Points for more information.

PSAP Callback Route Point Pattern

CTI route point that 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.

For more information, see Create Emergency Call Route Points.

ELIN Digit Strip Pattern

Digits to strip from the beginning of the PSAP Callback Route Point Pattern, for example, 913. The number that results from stripping the pattern should be the ELIN numbers that the PSAP can use to call into your network.

This string must be part of the PSAP Callback Route Point Pattern.

UDP Port Begin

Port numbers that are used by CTI ports during their registration.

The range is 1024 to 65535.

Inter-Emergency Responder Group Route Pattern

Route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

The pattern can only consist of numbers and dots.

For a more detailed explanation of this number, see Create route patterns for Inter-Cisco Emergency Responder Group Communications.

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 Emergency Responder.

The ToS value entered here only applies to the RTP packets sent by Emergency Responder for the onsite audio alert feature.

Onsite Alert Prompt Repeat Count

Number of times the prompt is played on the onsite alert phone.

Use IP Address from call signaling

If this parameter is enabled, Emergency Responder obtains the IP address of the phone from JTAPI. This parameter is used to route the call. If an IP subnet is configured for the phone, this parameter setting takes precedence over any other manual configuration.

If this parameter is disabled, Emergency Responder uses the manual configuration of the phone to route the call.

This field is applicable only if Emergency Responder is configured with Cisco Unified Communications Manager 6.x and above.

Update Settings button

Click Update Settings to save and activate your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado Route Pattern Settings

Intrado Route/Translation Pattern

Enter the route patterns or translation pattern for an Intrado emergency response location (ERL). An Intrado ERL is an ERL that is serviced by Intrado. Intrado ERL only lists the route patterns that have been configured on this page. You can add new route patterns or translation patterns, or you can update or remove existing route patterns or translation patterns.

To add a new route or translation pattern, click on the text box, enter the route pattern, including numbers and wildcard (do not use spaces), and click Add.

To update an existing route pattern, click on the appropriate route pattern, modify the pattern, and click Update.

To remove an existing route pattern, click on the appropriate route pattern and click Remove.

To cancel your existing changes and go back to the last saved settings, click Cancel Changes.

Related Tasks

Set Up Group Telephony Settings for Server

Related References

E911 and Cisco Emergency Responder Terminology

Set Up Group Telephony Settings for Server

You must configure the telephony settings to tell Emergency Responder which 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 Unified CM. See these topics for more information:

- Create Emergency Call Route Points

- Create Route Patterns for Inter-Cisco Emergency Responder Group Communication

Procedure

Step 1

Select System > Telephony Settings.
Emergency Responder opens the Telephony Settings page.

Step 2

Enter the telephony settings, as described in the Telephony Settings:

- UDP Port Begin—The first UDP port Emergency Responder can use for telephone calls. For example, 32000.

- Inter Cisco ER Group Route Pattern—The route pattern that other Emergency Responder groups use to route emergency calls to this group, for example, 1000.911.

- PSAP Callback Route Point Pattern—The CTI route point you created to receive calls from the PSAP. For example, 913XXXXXXXXXX (913 plus 10 Xs).

- ELIN Digit Strip Pattern—The digits to strip from the PSAP callback route point to reveal the ELIN. For example, 913.

- Route Point for Primary Cisco ER Server—The route point you created for the Emergency Responder primary server to use. For example, 711. You may change this number. See Modify the Emergency Number.

- Route Point for Standby Cisco ER Server—The route point you created for the Emergency Responder 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. We recommend that this default value be used for Emergency Responder.

- Onsite Alert Prompt Repeat Count—The number of times a prompt is given on the onsite security phone.

- Intrado Route Pattern—The route pattern for an Intrado emergency response location (ERL).

Step 3

Click Update Settings to save your changes.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Server Settings for Emergency ResponderServerGroup

The Server Settings for Emergency ResponderServerGroup page appears when you choose System > Server Settings.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Emergency Responder servers are inserted in the Emergency Responder group when the Emergency Responder services are started. (See Installation on a New System.)

Use the Server Settings for Emergency ResponderServerGroup page to update server settings, for example, to change the server name or to change the trace and debug settings, or to delete servers.

Note

You cannot modify the host name of the server.

The following table describes the Server Settings Emergency ResponderServerGroup page.

Server Settings for the Emergency ResponderServerGroup Page

Field

Description

Notes

Status

Displays the status of the Server Settings Emergency ResponderServerGroup page.

Select Server

Server

List of servers you have already created. Click on a server name to see the settings for that server.

You can configure a maximum of two servers per server group.

Modify Server Settings

Server Name

The name of the server.

Change this server name field to any desired value.

Host Name

The DNS name of the Emergency Responder server.

This field cannot be modified.

Debug Package List

A selection of subsystems for which you must collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Debug Package List.

Clear All button

Clears all selected subsystems in the Debug Package List.

Trace Package List

A selection of subsystems for which you must collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's 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.

See Trace and Debug Information for an explanation of each field.

Select All button

Selects all subsystems in the Trace Package List.

Clear All button

Clears all selected subsystems in the Trace Package List.

Update Settings button

Click Update when viewing an existing server's settings to save changes you make to the settings.

Only available when viewing the settings of an existing server.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related Tasks

Configure Servers

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Trace and Debug Information

Configure Servers

After you create an Emergency Responder group, you can use the Server Settings page to update Emergency Responder 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 Emergency Responder server.

Procedure

Step 1

Select System > Server Settings.
Emergency Responder opens the Server Settings page.

Step 2

Select the server name in the left-hand Servers list to change the server settings (Server Name or Debug Package List, or Trace Package List settings). Emergency Responder loads the server settings into the edit boxes. Make your changes and click Update.

Step 3

Select the server and click Delete to remove a server from the group. 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.

Step 4

When you are satisfied with your settings, click Update.
Emergency Responder saves your changes and displays them in the list of servers at the top of the page.

Trace and Debug Information

When you contact Cisco Technical Support for help with a problem that you are having with Emergency Responder, Cisco might request that you collect trace and debug information.

Because collecting trace and debug information affects Emergency Responder performance, you should only turn on tracing and debugging at Cisco's request. The generated information is for Cisco's use in resolving product problems.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

License Manager

The License Manager page appears when you choose System > License Manager.

Authorization Requirements

You must have system administrator authority to access this page.

Description

The License Manager Page provides the summary and detailed information on system license usage, as reported to the Prime License Manager.

License Manager Page

Field

Description

Status

Displays alarms or licensing alerts.

See License Manager Status Messages for further information on status messages. See License Compliance for further information on license compliance and noncompliance

Details of Emergency Responder Licenses

Displays the current license requirement for the server group:

- Number of phones discovered

- Number of phones manually configured

- Total number of users being tracked currently

Prime License Manager

Shows if the Prime License Manager manages the Emergency Responder Server Group.

If the Server Group has been added to an Prime License Manager product inventory, a link is provided to the Prime Collaboration License Manager server login page.

Emergency Responder must connect with the Prime License Manager at least once every 24 hours. This connection and communications of license requirements from the Emergency Responder and Prime License Manager is called synchronization.

The Enterprise License Manager status shows the time and date stamp of the last successful synchronization between the Emergency Responder and Prime License Manager.

Related Tasks

Upload License File

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Emergency Responder Licensing

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Emergency Responder Licensing

Cisco Prime License Manager centralizes all of the licensing for Emergency Responder Release 10.0 and later releases.

Emergency Responder communicates the licensing requirements to Cisco Prime License Manager. Emergency Responder attempts to discover all phones on Unified Communications Manager, excluding subnets not tracked by Emergency Responder. Along with the manually configured phones, Emergency Responder builds and sends the corresponding license requirements to the Cisco Prime License Manager. The Cisco Prime License Manager then compares the Emergency Responder license requirements with the licenses installed and reports back license compliance or noncompliance.

For more information, refer to the Enterprise License Manager User Guide.

Upload License File

Cisco Prime License Manager maintains the licensing for Cisco Emergency Responder 10.0 and later.

Use the Prime License Manager tool to obtain licenses from Cisco, to install the licenses, and to manage and view your inventory of licenses. This tool also tracks license compliance or noncompliance.

Email Alert Settings

The Email Alert Settings page appears when you choose System > Mail Alert Configurations.

Authorization Requirements

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 Emergency Responder sends email alerts. Use the check box to the right of each parameter to enable (check) or disable (uncheck) email alerts for that parameter. Check the Include event viewer contents in mail check box if you want to include the details from the event viewer in the email message.

The following table describes the Email Alert Settings page.

Email Alert Settings Page

Field

An email alert is sent when:

Discovery Parameters

Discovery Engine Registration Failed

The Discovery Engine fails to register

Discovery Engine goes out of connection

The Discovery Engine loses connection

For unreachable devices during recovery

Devices such as switches and Cisco Unified Communications Managers become unreachable

Emergency Call Routing Parameters

Call information

A 911 call is placed

Call routing session ended due to problems

Call routing is stopped due to any of these reasons:

- Invalid CMC

- Invalid FAC

- FAC and CMC needed

- CMC needed

- FAC needed

- RESOURCE_BUSY

Rerouting of call

An emergency call is rerouted

Routing failure

Call routing fails

Route Point out of Service

The route point goes out of service

Cluster Parameters

Cluster DB Failure

The server cannot communicate with the cluster database host

Intra Cluster Failure

The intra-cluster communication to a server group in the cluster fails

Misc Parameters

Subscriber becomes active

The Subscriber becomes active

Publisher comes back online

The Publisher comes back online

Not able to get the JTAPI Provider

When Emergency Responder cannot get the JTAPI provider

Available user licenses get exhausted during phone tracking

When the number of user licenses are exhausted during phone tracking

Switch Port location change reporting

When you enable switch port change reporting for phones

Suppress IP Communicator location change reporting

When you filter Cisco Unified IP Communicator from the location change reporting email alerts

Update Settings button

Updates the email alert settings

Cancel Changes button

Cancels changes made to the email alert settings

Related Tasks

Set Up Server Group

Related References

Onsite Alert Settings

Onsite Alert Settings

The Onsite Alert Settings page appears when you choose ERL > Onsite Alert Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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. Emergency Responder alerts the assigned personnel when an emergency call is made within the zone.

The following table describes the Onsite Alert Settings page.

Onsite Alert Settings Page

Field

Description

Notes

Add New Onsite Alert Contact

Onsite Alert ID

The identifier for the onsite alert contact. The identifiers you use should be based on your site identification strategy (for example, security ID or badge number). This field is used throughout Emergency Responder to identify the contact; for example, you select from Onsite Alert IDs when assigning contacts to zones. The Onsite Alert ID cannot be modified after you have saved it.

Use a naming strategy meaningful to your organization, but which is also useful when configuring zones in Emergency Responder.

Onsite Alert Name

The name of the onsite alert contact.

Onsite Alert Number

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.

When Emergency Responder gets an emergency call from an ERL, it calls the onsite alert number of the contact for the ERL and plays a prerecorded message that includes the phone number from which the emergency call was placed.

Onsite Alert Email Address

The email address for the onsite alert contact, for example, email@domain.com.

When Emergency Responder 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 Pager Address

The pager email address for the onsite alert contact, for example, <pager_number>@domain.com.

You can limit the size of the message that is sent to the pager by configuring the fields on the Pager Alert Setting Page. See Pager Alert Settings.

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.

Cancel Changes button

Click Cancel Changes to cancel any changes made to this page.

Available Onsite Alerts

Section of the page that displays onsite alert contacts that have already been configured. For configured onsite alert contacts, the following information is displayed:

- Onsite Alert ID

- Onsite Alert Name

- Onsite Alert Number

- Onsite Alert Email Address

To change an entry, click the entry or click the Edit icon; the person's 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.

If no contacts have previously been configured, this section is blank.

You cannot modify a contact's Onsite Alert ID.

Before you can delete the entry, you must update the ERLs to which the person is assigned to remove the person from the ERL.

Add New button

Click Add New to add another contact.

Update button

Click Update when viewing an existing contact's information to save changes you make to the information.

Only available when viewing the information for an existing contact.

Set Up Server Group

To configure a Emergency Responder server group, you must connect to the administration interface on one of the servers that is part of the group. An Emergency Responder server group consists of up to two Emergency Responder servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled.

Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See Data Integrity and Reliability for more information.

Before You Begin
You must have system administrator authority to configure an Emergency Responder server group.

Procedure

Step 1

Select System > Cisco ER Group Settings.
Emergency Responder opens the Emergency Responder Group Settings page.

Step 2

Fill in the group settings, as described in the Group Settings. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

- Cisco ER Group Name—Enter a name for the group. This name is mainly for your use, so choose a name that you find meaningful.

- SMTP Mail Server and Source Mail ID—If you want Emergency Responder to send email alerts to your Emergency Responder system administrator and 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 Add Onsite Security Personnel), 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 ID—If you want Emergency Responder to send email alerts in the case of critical errors, enter the email account information for the system contact.

- Calling Party Modification flag—You must set this flag if you enabled Calling Party Modification when you created Emergency Responder as a Cisco Call Manager user.

- Enable Syslog and Syslog Server—You can configure Emergency Responder to send log messages to the Syslog Server. To do this, select Enable Syslog and enter the fully qualified DNS name of the Syslog server.

- Security end user web interface language—To display the Emergency Responder User web pages in French (Canada), select it in the drop-down box. The default language is English.
Note:
The drop-down box provides a selection for Spanish (Spain) Voice Alerts only. When selected, the web interface remains in default English.

Step 3

When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the Emergency Responder group.

Add Subscriber

The Add Subscriber page appears when you choose System > Add Subscriber.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add Subscriber page to add a subscriber server to a Emergency Responder server group. After adding the subscriber information, you must enter the correct publisher server information when prompted during installation.

Before You Begin

You must first configure a Publisher server before configuring a Subscriber server.

The following table describes the Add Subscriber page.

Add Subscriber Page

Field

Description

Add Subscriber

HostName

Host name of the subscriber server.

Insert button

Click Insert to add the new subscriber server.

Cancel Changes button

Removes input form the Add Subscriber page.

Configured Servers

A list of all currently configured servers, showing the host name and IP address of each server.

Related Tasks

Install Emergency Responder Publisher

Install Emergency Responder Subscriber

Install Emergency Responder Publisher

To install Emergency Responder, you install the Publisher (primary) first, then you install the Subscriber (backup) on a separate server. You must install Emergency Responder 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 Emergency Responder Installation DVD.
If the system finds the DVD, you are asked if you want to perform a media check before installation to determine if there are problems with the DVD. The system displays the checksum of the DVD and instructs you to verify this checksum on the Emergency Responder 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 Emergency Responder system installer starts. The Product Deployment Selection screen displays a message saying the Cisco Emergency Responder product suite is installing. Click OK to continue.

Step 3

The Proceed with Install page displays the current software version on the hard drive 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 4

On the Platform Configuration Wizard page, click Proceed to continue with the platform installation.
If you click Skip, the system installs both the platform and Emergency Responder software without prompting you to provide information during the installation. After the installation is completed and the system reboots, you are prompted to enter the required configuration details.

Step 5

Click Continue to proceed. The Timezone Configuration page appears.

Step 6

Choose the correct time zone 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 time zone from the list

- After selecting the correct time zone, click OK. The Auto Negotiation Configuration page appears.

Step 7

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.

Step 8

On the NIC Speed and Duplex Configuration page, do the following:

1. Select the NIC Speed. The available options are 10 Megabit, 100 Megabit, or 1000 Megabit.

2. Select the NIC Duplex setting. The available options are Full or Half.

3. Click OK. The DHCP Configuration page appears.

Step 9

On the MTU Configuration page, you can set the maximum transmission unit (MTU) that can be sent in a network as follows:

1. Click Yes if you want to configure a a MTU value of less than 1500 bytes.

2. Click No to use the default MTU value of 1500 bytes.

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.

Step 11

If you chose not to use DHCP, enter the following information about the Static Network Configuration page:

- Host Name

- IP Address

- IP Mask

- Gateway (GW) Address

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 about 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.
When you have finished, click OK. The Certificate Information page appears.

Step 15

Enter the following information about 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 Install Emergency Responder Subscriber for information about installing the Subscriber.

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.

Caution:
For Emergency Responder install on UCS servers, it is mandatory to configure NTP server.

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 finish 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.
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 Emergency Responder server groups when performing installation/upgrade, DRS backup or restore, and "Point to a new Publisher" operations.

Click Help to display guidelines. When you finish, 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.

Step 20

On the Platform Configuration Confirmation page, do one of the following:

- Select OK to save the platform configuration information and continue with the installation. The Cisco Emergency Responder Configuration page appears.
Note:
After you select OK, you cannot 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.

Step 21

On the Cisco Emergency Responder Configuration page, do the following:

- 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 and then select OK.

Step 22

On the Security End User Language Selection page, choose a language for the Cisco Emergency Responder web pages. The system defaults to the English language.
The Application User Password Configuration page appears.

Step 23

On the Application User Configuration page, enter the username and password. This username and password is associated with the default administrative account and is used to log in to the Emergency Responder Administration web page. Click Help for guidelines.
When you are finished, click OK. The Cisco Emergency Responder Configuration Confirmation page appears.

Step 24

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:
After you select OK, you can not 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 Emergency Responder Application User Configuration page.

- Select Cancel to cancel the installation.

Step 25

After the system reboots, it checks the status of various system components. If the system finds any problems, you are prompted to correct the problem.
If the system does not find any problems, the installation process continues. The system ejects the installation DVD, reboot, and then finish the installation. When the installation is complete, a CLI prompt appears.

Note:
During this process, the system displays the MAC address of the Publisher. Write down the MAC address when it displays; you use the MAC address later to acquire Emergency Responder licenses. If you are not able to capture the MAC address during installation, you can look it up later. See Server Licenses for information about looking up the server MAC address.

Step 26

To bring up the Emergency Responder websites, go to any Windows system on the network, start a supported web browser, and enter the following URL:
http://your Emergency Responder hostname/

or

http://your Emergency Responder IP address/

Note:
Make sure that the Emergency Responder is configured with DNS so that hostname is resolved to the IP address.

Install Emergency Responder Subscriber

You must install Subscriber only after you have installed the Publisher. You must install the Subscriber on a separate server from the Emergency Responder Publisher.

Caution

You must complete the installation of the Publisher, which includes a system reboot, before you start to install the Subscriber.

Procedure

Step 1

On the Publisher server, add the details about the Subscriber server by doing the following:

1. Log in the Publisher Emergency Responder Administration website.

2. Select System > Add Subscriber. The Add Server page appears.

3. Enter the hostname of the new Subscriber and click Insert. The Add Subscriber page appears again.

4. In the Configured Servers list, check that the hostname and IP address of the new Subscriber is listed.

Step 2

Follow Steps 1 through 15 in the Installation on a New System section. After you complete Step 15, the Publisher Configuration page appears.

Step 3

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 Publisher 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.

Step 4

The Network Connectivity Test Configuration page appears. The system attempts to verify system connectivity. Click No to continue the installation.

Step 5

The Publisher Access Configuration page appears. Enter the following:

- Publisher hostname

- Publisher IP address

- Publisher Database/Security password

Step 6

Verify that the Publisher information is correct and click OK.

Step 7

The SMTP Host Configuration page appears. Choose Yes if you want to configure the SMTP Host.

Step 8

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 Emergency Responder Subscriber begins and takes an additional 20 to 30 minutes to complete.

Step 9

When the installation completes, go to the Emergency Responder 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" appears. This message indicates that the Subscriber was installed successfully.
Note:
If the Subscriber installation cannot validate the Publisher, See Cannot Validate Publisher in the Troubleshooting chapter.

Intrado VUI Settings

The Intrado VUI Settings page appears when you choose System > Intrado VUI Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado VUI Settings page to enter the account information that is required for Emergency Responder to interoperate with Intrado Validation and Update Interface. After entering the required information, you can test the connectivity to Intrado from this page.

The following table describes the Intrado VUI Settings page.

Intrado VUI Settings

Field

Description

Status

Displays status messages.

Intrado VUI Settings

Upload Certificate

Uploads the certificate from your local drive to the Emergency Responder server.

To upload a certificate, follow these steps:

1. Click Upload Certificate.

An Upload Certificate window appears.

2. Click the Browse button to locate the certificate file on your local machine.

3. Click the Upload button to upload the certificate file.

Validate Certificate

Intrado Certificate Password

The password that was generated with this certificate.

VUI URL

VUI URL is provided by Intrado.

Test and Validate Certificate

Use this button to test the validity of your certificate.

Configure Account Details

VUI Schema URL

The VUI Schema URL provided by Intrado.

Intrado Account ID

Your Intrado Account ID provided by Intrado.

Max VUI Connections

The maximum number of simultaneous VUI connections that Emergency Responder allows across the Server group.

Test Connectivity

Use this link to verify whether Emergency Responder can successfully connect to Intrado VUI.

Delete Account

Deletes an existing Intrado account from the Emergency Responder database.

Update

Click Update to save the changes you made on this page.

Cancel

Click Cancel to change the fields on this page back to the last saved settings.

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Onsite Alert Settings

The Onsite Alert Settings page appears when you choose ERL > Onsite Alert Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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. Emergency Responder alerts the assigned personnel when an emergency call is made within the zone.

The following table describes the Onsite Alert Settings page.

Onsite Alert Settings Page

Field

Description

Notes

Add New Onsite Alert Contact

Onsite Alert ID

The identifier for the onsite alert contact. The identifiers you use should be based on your site identification strategy (for example, security ID or badge number). This field is used throughout Emergency Responder to identify the contact; for example, you select from Onsite Alert IDs when assigning contacts to zones. The Onsite Alert ID cannot be modified after you have saved it.

Use a naming strategy meaningful to your organization, but which is also useful when configuring zones in Emergency Responder.

Onsite Alert Name

The name of the onsite alert contact.

Onsite Alert Number

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.

When Emergency Responder gets an emergency call from an ERL, it calls the onsite alert number of the contact for the ERL and plays a prerecorded message that includes the phone number from which the emergency call was placed.

Onsite Alert Email Address

The email address for the onsite alert contact, for example, email@domain.com.

When Emergency Responder 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 Pager Address

The pager email address for the onsite alert contact, for example, <pager_number>@domain.com.

You can limit the size of the message that is sent to the pager by configuring the fields on the Pager Alert Setting Page. See Pager Alert Settings.

Available User Group

The User Group which will receive the specific web alert from the associated ERL. By default Emergency Responder User Group is selected, which has all users.

The users can view all alerts in the system by selecting ALL on the Web Alert page.

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.

Cancel Changes button

Click Cancel Changes to cancel any changes made to this page.

Available Onsite Alerts

Section of the page that displays onsite alert contacts that have already been configured. For configured onsite alert contacts, the following information is displayed:

- Onsite Alert ID

- Onsite Alert Name

- Onsite Alert Number

- Onsite Alert Email Address

- Onsite User Group

To change an entry, click the entry or click the Edit icon; the person's 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.

If no contacts have previously been configured, this section is blank.

You cannot modify a contact's Onsite Alert ID.

Before you can delete the entry, you must update the ERLs to which the person is assigned to remove the person from the ERL.

Add New button

Click Add New to add another contact.

Update button

Click Update when viewing an existing contact's information to save changes you make to the information.

Only available when viewing the information for an existing contact.

Related Tasks

Add Onsite Security Personnel

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

ERL Creation

Emergency Responder Onsite Alert Personnel Preparations

Add Onsite Security 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 Emergency Responder end-user interface specific to emergency calls originating from the assigned ERL. They also can view all alerts in the system.

- An email message. If you use an email-based paging address, the message results in a page.

- A telephone call indicating that an emergency call was made.

Before You Begin
You must log into Emergency Responder 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).

Procedure

Step 1

Select ERL > Onsite Alert Settings.
Emergency Responder opens the Onsite Alert Settings page.

Step 2

Enter the unique ID, name, telephone number, email address, and pager address, and User Group of a security or onsite alert person.
Unique ID might be a badge number, email name, or other site-specific unique name. You 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.
Emergency Responder adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.

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 person's record.

- To modify onsite alert settings, click on the person's Onsite Alert ID, Onsite Alert Name, Onsite Alert Number, Onsite Alert Email Address or Onsite Alert Pager 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 person's Onsite Alert ID: to change the Onsite Alert ID, delete the person's entry and create a new one.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

Emergency Responder Onsite Alert Personnel Preparations

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder:

- How to use the Emergency Responder web interface. See the Emergency Responder user web interface online help for information about these topics. The online help includes a user's guide in PDF format that you can print out and distribute to your users. The information in the user's 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.

- Explain how they receive notification of an emergency call.

- A web alert appears for everyone logged into the Emergency Responder 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 Emergency Responder 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 have for identifying the location of the emergency caller.

- Explain the organization's policy for responding to emergency calls. Work with the emergency response teams to develop an acceptable policy if you do not already have one.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Pager Alert Settings

The Pager Alert Settings page appears when you choose ERL > Pager Alert Configurations.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Pager Alert Configurations page to limit the size of system wide pager messages by selecting the fields that are sent to the pager and by editing the labels for those fields.

The following table describes the Pager Alert Settings page.

Pager Alert Settings

Field

Descriptions

You can limit the size of the pager message that is sent by selecting the following fields and editing the labels are associated with those fields:

- Extension

- ERL

- Location

- Time

- Server

To select the fields that you would like to display on the pager, check the box adjacent to the field.

To edit the label that you want to send to the pager, click on the text box for that field.

Update Settings Button

Click Update Settings to save changes that you made.

Restore Defaults Button

Click Restore Defaults to restore the default pager and label settings.

Send Sample Message to a pager

To send a test message to your pager, enter a pager address in the text box and click the Send Test Message button.

Related References

Onsite Alert Settings

Related Information

Emergency Responder Onsite Alert Personnel Preparations

Onsite Alert Settings

The Onsite Alert Settings page appears when you choose ERL > Onsite Alert Settings.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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. Emergency Responder alerts the assigned personnel when an emergency call is made within the zone.

The following table describes the Onsite Alert Settings page.

Onsite Alert Settings Page

Field

Description

Notes

Add New Onsite Alert Contact

Onsite Alert ID

The identifier for the onsite alert contact. The identifiers you use should be based on your site identification strategy (for example, security ID or badge number). This field is used throughout Emergency Responder to identify the contact; for example, you select from Onsite Alert IDs when assigning contacts to zones. The Onsite Alert ID cannot be modified after you have saved it.

Use a naming strategy meaningful to your organization, but which is also useful when configuring zones in Emergency Responder.

Onsite Alert Name

The name of the onsite alert contact.

Onsite Alert Number

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.

When Emergency Responder gets an emergency call from an ERL, it calls the onsite alert number of the contact for the ERL and plays a prerecorded message that includes the phone number from which the emergency call was placed.

Onsite Alert Email Address

The email address for the onsite alert contact, for example, email@domain.com.

When Emergency Responder 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 Pager Address

The pager email address for the onsite alert contact, for example, <pager_number>@domain.com.

You can limit the size of the message that is sent to the pager by configuring the fields on the Pager Alert Setting Page. See Pager Alert Settings.

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.

Cancel Changes button

Click Cancel Changes to cancel any changes made to this page.

Available Onsite Alerts

Section of the page that displays onsite alert contacts that have already been configured. For configured onsite alert contacts, the following information is displayed:

- Onsite Alert ID

- Onsite Alert Name

- Onsite Alert Number

- Onsite Alert Email Address

To change an entry, click the entry or click the Edit icon; the person's 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.

If no contacts have previously been configured, this section is blank.

You cannot modify a contact's Onsite Alert ID.

Before you can delete the entry, you must update the ERLs to which the person is assigned to remove the person from the ERL.

Add New button

Click Add New to add another contact.

Update button

Click Update when viewing an existing contact's information to save changes you make to the information.

Only available when viewing the information for an existing contact.

Emergency Responder Onsite Alert Personnel Preparations

You probably already have emergency response policies and procedures in place. Consider how Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder:

- How to use the Emergency Responder web interface. See the Emergency Responder user web interface online help for information about these topics. The online help includes a user's guide in PDF format that you can print out and distribute to your users. The information in the user's 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.

- Explain how they receive notification of an emergency call.

- A web alert appears for everyone logged into the Emergency Responder 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 Emergency Responder 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 have for identifying the location of the emergency caller.

- Explain the organization's policy for responding to emergency calls. Work with the emergency response teams to develop an acceptable policy if you do not already have one.

Conventional ERL

The Conventional ERL page appears when you choose ERL >Conventional ERL.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Conventional ERL Data page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create are 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.

The following table describes the Find and List ERLs page.

Find and List ERLs Page

Field

Description

Notes

ERL Search Parameters

Find Conventional ERL where...

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:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL 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 is 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 remains there until it is modified.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Configure Default ERL

Click Configure Default ERL to configure a default ERL

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Related References

Export PS-ALI Records

E911 and Cisco Emergency Responder Terminology

Related Information

ERL Creation

ERLs

ERL Management

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

ERL Creation

The following sections describe how to create emergency response locations (ERLs).

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Add New ERL

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. If the ERL name is First Floor, the page that appears is titled ERL Information for First Floor.

The Add New ERL and ERL Information for ERL Name pages are essentially the same, as follows:

- The Add New ERL page appears when you select Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL). 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 choose ERL > Conventional ERL).

Note

You cannot use a default ERLs as a Test ERL. The Test ERL check box is not available on the ERL Information for Default page.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this 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.

Emergency Responder allows you to select the ERL as a Test ERL.

Use the Find ERL Data page to view or update an existing ERL.

See ELIN Numbers Emergency Calls and PSAP Callbacks for information about configuring the ELIN numbers in Cisco Unified Communications Manager.

If you want to route emergency calls to onsite security instead of the PSAP, see Set Up ERLs for Non-PSAP Deployment for the Route/Translation Pattern and ELIN settings.

The following table describes the Add New ERL and ERL Information pages.

Add New ERL and ERL Information Pages

Field

Description

Notes

ERL Settings

ERL Name

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 sees 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 an ERL naming strategy.

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 are trimmed.

Description

Enter a description of the new ERL (optional).

Test ERL (Used for Synthetic Testing)

Check this check box if this ERL is used for testing.

See Set Up Test ERLs.

This setting is not available on the ERL Information for Default; default ERLs may not be used as test ERLs.

ELIN Settings

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 that 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 cannot 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.

Note:
Emergency Responder restricts the association of an ELIN with an ERL if the ELIN has been configured as a DID Number for an Off-Premises Emergency Responder user. Emergency Responder does not impose this restriction if the DID Number belongs to a user who has never associated an off-premises location in Emergency Responder.

Route/Translation Pattern

The phone number, defined as a route pattern in Cisco Unified Communications Manager, that is configured to use the gateway that 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.

ELIN Number

The unique phone number which the PSAP can use to locate a caller 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, for the North American Numbering Plan, such as 4085551212, or an E.164 Number including country code such as +14085551212. The number can only contain numbers, a plus sign (+), single hyphens, dots, or parentheses.

An ELIN when being sent as ANI to PSAP through outgoing Gateway must be a DID (direct inward dial) number provided by your service provider.

Add button

To add a route point and ELIN combination, enter the information and click Add.

Update button

To change an existing combination, select it in the list, change the information in the edit boxes, and click Update.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact's ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

ERL Address

ALI Details button

Click ALI Details to view or change the automatic location information (ALI) of an ERL. The ALI provides detailed information about the location of the ERL, such as street address and phone number.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

Related Tasks

Set Up Default ERL

Set Up Individual ERL and Automatic Location Information (ALI)

Set Up Test ERLs

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

ERLs

ERL Management

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

Set Up Default ERL

Emergency Responder 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 ERLs that are 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 Emergency Responder only if no other ERL is configured for that phone.

Emergency Responder also uses the default ERL for all emergency calls when the Emergency Responder server is first started (or restarted when there is no standby Emergency Responder server) until the initial switch port update is finished. (This process is started immediately.)

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

You must first configure the required ELINs in Unified CM.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find Conventional ERL Data page.

Step 2

Click Configure Default ERL.
Emergency Responder opens the ERL Information for Default window.

Step 3

Fill in the ERL Information for Default window.

Step 4

Click ALI Details.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Update ALI Info. Emergency Responder saves your ALI. Click Close to close the window.

Step 6

Make the ERL Information for Default window the active window if it is not, and click Update.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
Tip:
You cannot delete the default ERL. In addition, you cannot configure other ERLs unless the default ERL is configured.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

Set Up Test ERLs

You can use Cisco Unified Operations Manager to monitor the health and functionality of Emergency Responder.

To use Cisco Unified Operations Manager with Emergency Responder, you configure a test ERL for conventional ERLs, then add a synthetic phone and associate the synthetic phone to the test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can configure test ERLs only to synthetic phones.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

All synthetic phones used for Emergency Responder 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 are not logged in Call History logs.

- Web alerts are not generated for emergency calls from synthetic phones.

- Email alerts are not generated for emergency calls from synthetic phones.

- PS-ALI records for test ERLs are not 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.

Procedure

Step 1

Select ERL > Conventional ERL and click Add New ERL on the ERL Configuration page.

Step 2

At the ERL field, enter a name for the test ERL.

Step 3

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.

Step 4

Click Insert to save the test ERL and click Close to close the window.

Step 5

Select ERL Membership > Synthetic Phones and click Add New Synthetic phone on the Find and List Synthetic Phones page.

Step 6

In 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

Step 7

In 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.

Step 8

Click Insert to add the phone to the list of defined synthetic phones.

Step 9

To change the fields on this page back to the last saved settings, click Cancel Changes.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

Related Tasks

Set Up Default ERL

Set Up Individual ERL and Automatic Location Information (ALI)

Import Several ERLs

Related References

Export PS-ALI Records

E911 and Cisco Emergency Responder Terminology

Related Information

ERLs

ERL Management

Set Up Default ERL

Emergency Responder 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 ERLs that are 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 Emergency Responder only if no other ERL is configured for that phone.

Emergency Responder also uses the default ERL for all emergency calls when the Emergency Responder server is first started (or restarted when there is no standby Emergency Responder server) until the initial switch port update is finished. (This process is started immediately.)

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

You must first configure the required ELINs in Unified CM.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find Conventional ERL Data page.

Step 2

Click Configure Default ERL.
Emergency Responder opens the ERL Information for Default window.

Step 3

Fill in the ERL Information for Default window.

Step 4

Click ALI Details.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Update ALI Info. Emergency Responder saves your ALI. Click Close to close the window.

Step 6

Make the ERL Information for Default window the active window if it is not, and click Update.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
Tip:
You cannot delete the default ERL. In addition, you cannot configure other ERLs unless the default ERL is configured.

Set Up Individual ERL and Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see "Import Several ERLs" section for strategies for simplifying the definition of similar ERLs.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

Select ERL > Conventional ERL.
Emergency Responder opens the Find conventional ERLs page.

Step 2

Click Add New ERL.
Emergency Responder opens the Add New ERL window.

Step 3

Fill in the Add New ERL window.

Step 4

Click the Add ALI button.
Emergency Responder opens the ALI Information window.

Step 5

Fill in the ALI Information window.
When finished filling in the ALI, click Save and Close.

Step 6

Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.

Step 7

Click Close to close the window.
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. Emergency Responder 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.

Import Several ERLs

Rather than defining ERLs one at a time, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Prepare an import file. Emergency Responder 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 to import it.

You can import conventional, off-premise, or Intrado ERLs. Click the Import link in the upper-right corner of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Use the following procedure to view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL data page, Find Off-Premises ERLs data page, or the Find Intrado ERLs data page), click Import.
Emergency Responder opens the Import ERL data page.

Step 2

Select the format of your import file (csv or xml) from the pull-down menu.

Step 3

Click Upload to upload the file from your local machine.

Step 4

Select your import file.

Step 5

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 6

Click Close to close the Import ERL Data window.

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export ERL Data

The Export ERL Data page appears when you click the Export link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder server.

To create a file to send to your service provider to update their ALI data, see Export PS-ALI Records.

The following table describes the Export ERL Data page.

Export ERL Data Page

Field

Description

Select Export Format

The file format to be used in the export file. For ERL data, either csv (comma-separated value) or XML.

Enter Export File Name

The name of the file you want to create. Do not include a file extension.

Export button

Click Export to create the export file.

Close button

Click Close to close the window.

Related Tasks

Export ERL Information

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

ALI Submission and Service Provider Requirements

ERLs

ERL Management

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Import ERL Data

The Import ERL Data page appears when you click the Import link on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import ERL Data page.

Import ERL Data Page

Field

Description

Select Import Format

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

Select the file from which you want to import ERL data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add ERL data from the import file to the Emergency Responder database.

Note:
The imported ERL data overwrites conflicting data in the Emergency Responder database.

Close button

Click Close to close the window.

Related Tasks

Import Several ERLs

Export ERL Information

Upload File

Related References

E911 and Cisco Emergency Responder Terminology

Export PS-ALI Records

Related Information

ERLs

ERL Management

Import Several ERLs

Rather than defining ERLs one at a time, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Prepare an import file. Emergency Responder 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 to import it.

You can import conventional, off-premise, or Intrado ERLs. Click the Import link in the upper-right corner of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Use the following procedure to view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL data page, Find Off-Premises ERLs data page, or the Find Intrado ERLs data page), click Import.
Emergency Responder opens the Import ERL data page.

Step 2

Select the format of your import file (csv or xml) from the pull-down menu.

Step 3

Click Upload to upload the file from your local machine.

Step 4

Select your import file.

Step 5

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 6

Click Close to close the Import ERL Data window.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

Off-Premises ERL

The Find Off-Premises ERL Data page appears when you choose ERL > Off-Premise ERL > Search And List.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Off-Premise ERL Data page to define the emergency response locations (ERLs) for individuals with phones that are located outside of the corporate network.

The following table describes the Find and List Off-Premise ERLs page.

Find Intrado ERL Data (Off-Premise)

Field

Description

Notes

ERL Search Parameters

Find Off-Premises ERL where...

Select search criteria and click Find to list existing Off-Premise ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

Add New ERL

Click Add New ERL to create a new ERL.

Related Tasks

Set Up Emergency Responder to Support Off-Premise Users

Related References

Add New ERL

Off-Premise ERL - Secondary Status

Add New ERL

The Add New ERL (Off-Premise phones) page appears when you choose Add New ERL on the Find Intrado ERL Data page (opened when you choose ERL > Off-Premise ERL> Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New ERL page to create a new emergency response location (ERL) for Off-Premise phones. Alternatively, you can create or update many ERLs at once by importing predefined ERL information from a separate file.

Use the Find ERL Data page to view or update an existing ERL.

The following table describes the Add New ERL (Off-Premise Phones) page.

Add New ERL (Off-Premise Phones)

Field

Description

Note

ERL Settings

ERL Name

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 sees 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.

Work with your security team to develop an ERL naming strategy.

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 is trimmed.

Description

Enter a description of the new ERL (optional).

Route/Translation Pattern 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.

Add button

To add a route point, choose a route point from the drop-down list and click Add.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

Off-Premise ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Off-Premise ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about off-premise telephone number record update transactions that were flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for off-premise telephone number records with errors.

The following table describes the Secondary Status for Off-Premise phones.

Secondary Status (Off-Premise Phones)

Field

Description

Find DIDs where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Add New ERL

The Add New ERL (Off-Premise phones) page appears when you choose Add New ERL on the Find Intrado ERL Data page (opened when you choose ERL > Off-Premise ERL> Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New ERL page to create a new emergency response location (ERL) for Off-Premise phones. Alternatively, you can create or update many ERLs at once by importing predefined ERL information from a separate file.

Use the Find ERL Data page to view or update an existing ERL.

The following table describes the Add New ERL (Off-Premise Phones) page.

Add New ERL (Off-Premise Phones)

Field

Description

Note

ERL Settings

ERL Name

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 sees 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.

Work with your security team to develop an ERL naming strategy.

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 is trimmed.

Description

Enter a description of the new ERL (optional).

Route/Translation Pattern 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.

Add button

To add a route point, choose a route point from the drop-down list and click Add.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

Related Tasks

Set Up Emergency Responder to Support Off-Premise Users

Related References

Off-Premises ERL

Off-Premise ERL - Secondary Status

Off-Premises ERL

The Find Off-Premises ERL Data page appears when you choose ERL > Off-Premise ERL > Search And List.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Off-Premise ERL Data page to define the emergency response locations (ERLs) for individuals with phones that are located outside of the corporate network.

The following table describes the Find and List Off-Premise ERLs page.

Find Intrado ERL Data (Off-Premise)

Field

Description

Notes

ERL Search Parameters

Find Off-Premises ERL where...

Select search criteria and click Find to list existing Off-Premise ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

Add New ERL

Click Add New ERL to create a new ERL.

Off-Premise ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Off-Premise ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about off-premise telephone number record update transactions that were flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for off-premise telephone number records with errors.

The following table describes the Secondary Status for Off-Premise phones.

Secondary Status (Off-Premise Phones)

Field

Description

Find DIDs where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Off-Premise ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Off-Premise ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about off-premise telephone number record update transactions that were flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for off-premise telephone number records with errors.

The following table describes the Secondary Status for Off-Premise phones.

Secondary Status (Off-Premise Phones)

Field

Description

Find DIDs where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Related Tasks

Set Up Emergency Responder to Support Off-Premise Users

Related References

Off-Premises ERL

Add New ERL

Off-Premises ERL

The Find Off-Premises ERL Data page appears when you choose ERL > Off-Premise ERL > Search And List.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Off-Premise ERL Data page to define the emergency response locations (ERLs) for individuals with phones that are located outside of the corporate network.

The following table describes the Find and List Off-Premise ERLs page.

Find Intrado ERL Data (Off-Premise)

Field

Description

Notes

ERL Search Parameters

Find Off-Premises ERL where...

Select search criteria and click Find to list existing Off-Premise ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

Add New ERL

Click Add New ERL to create a new ERL.

Add New ERL

The Add New ERL (Off-Premise phones) page appears when you choose Add New ERL on the Find Intrado ERL Data page (opened when you choose ERL > Off-Premise ERL> Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New ERL page to create a new emergency response location (ERL) for Off-Premise phones. Alternatively, you can create or update many ERLs at once by importing predefined ERL information from a separate file.

Use the Find ERL Data page to view or update an existing ERL.

The following table describes the Add New ERL (Off-Premise Phones) page.

Add New ERL (Off-Premise Phones)

Field

Description

Note

ERL Settings

ERL Name

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 sees 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.

Work with your security team to develop an ERL naming strategy.

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 is trimmed.

Description

Enter a description of the new ERL (optional).

Route/Translation Pattern 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.

Add button

To add a route point, choose a route point from the drop-down list and click Add.

Remove button

To remove a combination, select it in the list and click Remove.

Onsite Alert Settings

Available Onsite Alert IDs

Text box that displays the IDs of all available onsite alert personnel.

You must first add the contact to the list of onsite alert personnel.

Add button

Select the onsite alert (security) contacts to be assigned to the ERL. These contacts are 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 contact ID then appears in the Onsite Alert IDs for the ERL text box.

Remove button

To remove a contact for the ERL, select the appropriate ID in the Onsite Alert IDs for the ERL text box and click Remove.

Insert button

Click Insert to save your changes to the new ERL.

The Insert button is only available when creating a new ERL.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update to save your changes to the ERL.

The Update button is only available when changing an existing ERL.

Close button

Click Close to close the window. You must click Update or Insert to save your changes before you click Close.

Set Up Emergency Responder to Support Off-Premise Users

Cisco Emergency Responder allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

- Cisco Emergency Responder

- Unified CM 7.1 or later version.

- Intrado V9-1-1 Enterprise Services

After you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Unified CM User Option page.

Note

Dialable 10-digit North American Numbering Plan numbers are required as DIDs for endpoints using the Emergency Responder off-premises location management feature. However, you can configure an abbreviated line number and an external phone number mask on Unified CM, creating the 10-digit DID in the calling line number in the 911 call to Intrado. Each combination of line number and external mask must be unique to one off-premises user, because it will be used to identify the caller’s location and for callback by the PSAP, if necessary.

Procedure

Step 1

Configure Emergency Responder for use with Intrado.

Step 2

Enable Emergency Responder Location Management in Unified CM for off-premise support.

Step 3

Configure the AXL application user for Emergency Responder in Unified CM.

Step 4

Configure AXL authentication with Cisco Unified Communications Manager.

Step 5

Configure Off-Premise ERLs.

Step 6

Assign off-premise ERLs to IP subnets and unlocated phones.
Note:
You cannot assign off-premise ERLs to switch ports.

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Related References

Default ALI Values

Intrado ERL - Secondary Status

Intrado Schedule

View ALI Discrepancies

Related Information

Intrado V9-1-1 for Enterprise Service

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Intrado V9-1-1 for Enterprise Service

If you are a subscriber to IntradoV9-1-1 for Enterprise Service, you can use Emergency Responder to simplify emergency call management. Emergency Responder provides an interface that allows you to enter and synchronize location information directly to the Intrado database. Emergency Responder provides location information for emergency calls for both on-premise phones and off-premise phones and works with Intrado and Unified CM to complete emergency calls.

Emergency Responder tracks IP phones by the IP subnet or when someone manually configures and assigns the MAC address. Emergency Responder maintains the status of the phones (on-premise, off-premise, unlocated), and passes on any ALI or ELIN information to Intrado. Users with on-premise phones rely on Cisco Unified Communications to route their emergency calls to Intrado and the designated emergency provider.

Users with off-premise phones cannot make emergency calls until the users enter in their location and associate this information with their directory number. After the location information has been verified, emergency calls placed from off-premise phones can be completed.

Note

Users can only configure one off-premise location for each DID (DN + External Mask). This configuration also applies to shared lines. If two off-premise phones share a DID, the user can only associate one location to the DID.

The following figure shows the interactions between users, Emergency Responder, and Intrado.

Understanding the Interactions Between Users, Emergency Responder, and Intrado

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related References

Find Intrado ERL

Intrado ERL - Secondary Status

Intrado Schedule

View ALI Discrepancies

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Related References

Find Intrado ERL

Default ALI Values

Intrado Schedule

View ALI Discrepancies

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

Related References

Find Intrado ERL

Default ALI Values

Intrado ERL - Secondary Status

View ALI Discrepancies

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Related References

Find Intrado ERL

Default ALI Values

Intrado ERL - Secondary Status

Intrado Schedule

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

View ALI Discrepancies for a Specific ELIN

Choose ERL > Intrado ERL > View ALI Discrepancies and search for discrepancies. The View ALI Discrepancies for a specific ELIN page appears when you select a specific ELIN from the results.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies for a Specific ELIN page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies for a specific ELIN page.

ALI Discrepancies for Specific ELIN

Field

Description

View Intrado ALI Discrepancies

ALI Fields

List of ALI field information from the local Emergency Responder database and from Intrado database:

- House Number

- House Suffix

- Street Name

- Prefix Directional

- Street Suffix

- Post Directional

- Community Name

- State

- Main NPA

- Class of Service

- Type of Service

- Exchange

- Customer Name

- Order Number

- Extract Date

- County ID

- Company ID

- Zip Code

- Zip Code Extension

- Customer Code

- Comments

- Longitude

- Latitude

- Elevation

- TAR Code

- Location

- Reserved

Save button

Click Save to save your changes in the local Emergency Responder database.

Save Intrado ALI Info button

Click Save Intrado ALI Info to update the Intrado VUI database.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Close button

Click Close to close the window.

Related References

Find Intrado ERL

Default ALI Values

Intrado ERL - Secondary Status

Intrado Schedule

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

ERL Migration Tool

The ERL Migration Tool page appears when you choose ERL > ERL Migration Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the ERL Migration Tool page to migrate ERLs from conventional ERL data to Intrado ERL data and vice versa.

The following table describes the ERL Migration Tool page.

ERL Migration Tool

Field

Description

Status

Displays status messages

ERL Search Parameter

Find

Select search criteria and click Find to list either existing Conventional ERLs or Intrado ERLs.

From the search results list, you can select the ERLs that you want to migrate

Migrate to Intrado ERL Button

When you search for Conventional ERLs, you can select the ERLs that you want to migrate to Intrado.

When you click the Migrate to Intrado ERL button, you can select an Intrado route point for all the selected ERL.

Migrate to Regular ERL

When you search for Intrado ERLs, you can select the ERLs that you want to migrate to a conventional ERL data.

When you click the Migrate to Regular ERL button, you can enter a route point, and specify whether the ERL is a test ERL and test the ERL.

Related References

Find Intrado ERL

Default ALI Values

Intrado ERL - Secondary Status

Intrado Schedule

View ALI Discrepancies

Related Information

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

ERL Data Migration

Find Intrado ERL

The Find Intrado ERL page appears when you choose ERL > Intrado ERL > Intrado ERL (Search and List).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

When you use Intrado V91-1-1 services, you can use the Intrado ERL Data page to define the emergency response locations (ERLs) for your company.

The following table describes the Find and List Intrado ERLs page.

Find Intrado ERL Data

Field

Description

Notes

ERL Search Parameters

Find Intrado ERL where...

Select search criteria and click Find to list existing Intrado ERLs. To list all ERLs, click Find without entering any criteria. From the drop-down list, you can select the number of records that display per page for each search.

From the search results list, you can:

- 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 ERL Audit Trail for more information.

When copying an ERL, information that must be unique in an ERL is not copied.

See Add New ERL for more information.

Add New ERL

Click Add New ERL to create a new ERL.

See Add New ERL for more information.

Level of service button

Click Level of service to display the level of service that Intrado designates for the specific address that is configured in the ALI details. Intrado supports the following level of service:

- No Coverage—Intrado does not have access to the selective router and cannot provide the callback number and address to the PSAP that services that address.

- Basic—The PSAP that provides service currently can not provide emergency support for wire line services or VoIP service providers.

- Enhanced—Calls can be routed to the PSAP with the existing E9-1-1 selective router network, and Intrado can provide the callback number and address to the PSAP.

Bulk TN Update button

Select multiple ERLs and click Bulk TN Update to update the ELIN for the selected ERL.

Export

Click the Export link to create a file containing your ERL configuration.

See Export ERL Data for information about exporting ERL data.

Import

Click the Import link to create or update ERLs using information stored in a separate file. By importing ERL data, you can create or update many ERLs at one time.

See Import ERL Data for information about importing ERL data.

Default ALI Values

The Default ALI Values page appears when you choose ERL > Intrado ERL > Default ALI Values.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Default ALI Values page to set the default values that automatically populate the respective ALI fields when a new Intrado ERL is created.

The following table describes the Default ALI Information page.

Default ALI Values

Field

Description

Default ALI Values for Intrado ERLs

Type of Service

Defines the type of service for the calling party number, such as FX in 911 area or Non-Pub.

Note:
Intrado recommends setting the default to Non-Pub.

Class of Service

Defines the class of service for the calling party number, such as residential, business, VoIP.

Note:
Intrado recommends setting the default to VoIP.

Company ID

Specified by Intrado.

Customer Name

Specified by Intrado.

Update button

Click Update to save your changes.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Intrado ERL - Secondary Status

The Secondary Status page appears when you choose ERL > Intrado ERL > Secondary Status.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Secondary Status page to query the Intrado Secondary Status database for information about telephone number record update transactions that were previously flagged with errors. These records may include the following:

- Corrected records that are now in the Intrado database.

- Error records that are referred back to customers for correction.

- Deleted error records from the Intrado database.

You can query the Intrado Secondary status database for telephone number records with errors that have been corrected.

The following table describes the Secondary Status for phones that are serviced by Intrado.

Secondary Status (Intrado Phones)

Field

Description

Find ELINS where...

Select search criteria and click Find to list the result of a query on the Intrado secondary status server.

Intrado Schedule

The Intrado Schedule page appears when you choose ERL >Intrado ERL > Intrado Schedule.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Intrado Schedule page to specify the day of the week and time when ALI update requests and secondary status update requests are sent to Intrado. ALI update requests sends newly created TN records to Intrado. Secondary Status update requests sends queries to Intrado requesting information about records with errors that have been corrected.

The following table describes the Intrado Schedule page.

Intrado Schedule

Field

Description

Notes

Add new schedule

Specify the day of the week and time of the day when you want to schedule an update:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

3. Check the Enable Schedule check box if you want to activate this schedule.

4. Choose either ALI Update Schedule or Secondary Status Update Schedule.

We recommend that you run the Intrado update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Add button

Click Add to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes you make to the schedule.

Only available when viewing an existing schedule.

View ALI Discrepancies

The View ALI Discrepancies page appears when you choose ERL > Intrado ERL > View ALI Discrepancies.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the View ALI Discrepancies page to view discrepancies in the records between the ALI data that is stored in the local Emergency Responder database and the ALI data for this ELIN in the Intrado database.

The following table describes the Find ALI Discrepancies page.

ALI Discrepancies

Field

Description

Find ELIN where...

Enter search criteria to select the ELIN that you want to find.

To find all ELIN, click Find without entering any criteria.

To narrow your search, select the field that you want to search on from the drop-down list, select the search relationship (is contains, begins with, and so on), and enter the search string. Click Find.

Configure Emergency Responder and Intrado V9-1-1 Enterprise Services

ERL Data Migration

Emergency Responder supports migrating existing conventional ERLs to Intrado ERLs and vice versa.

SNMP Settings

The SNMP Settings page appears when you choose Phone Tracking > SNMPv2 Settings or Phone Tracking > SNMPv3 Settings.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the SNMPv2 Settings page or the SNMPv3 Settings page to define the SNMP read community string used by your switches.

Related Tasks

Set Up SNMPv2

Set Up SNMPv3

Related References

E911 and Cisco Emergency Responder Terminology

Set Up SNMPv2

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 define in Emergency Responder. If you use different strings for different sets of switches, determine whether 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.*.*.

If two or more patterns match an IP address, Emergency Responder 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, Emergency Responder uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

Procedure

Step 1

Select Phone Tracking > SNMPv2 Settings.
Emergency Responder opens the SNMP Settings page.

Step 2

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 Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see LAN Switch Identification for more information), it does not matter if the IP address patterns cover devices other than switches.

- If all of your switches use the same read community string, enter *.*.*.*. You 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 Emergency Responder 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, Emergency Responder 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.

Step 4

Enter the read community string, for example, public.

Step 5

Click Insert.
Emergency Responder adds the SNMP setting to the list of settings.

Step 6

If you must create more than one setting, return to Step 2.
If you change the SNMP read community string on a switch, you must update the associated setting in Emergency Responder:

- To change an SNMP setting, select it in the list. Emergency Responder 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 setting's entry.

Set Up SNMPv3

Procedure

Step 1

Select Phone Tracking > SNMPv3 Settings.
Emergency Responder opens the SNMPv3 Settings page.

Step 2

Enter the User information for which you want to provide access.
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.

Step 3

To require authentication, check the Authentication Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 4

If you checked the Authentication Required check box, you can specify privacy information. To require privacy, check the Privacy Required check box, enter the password in the Password and Reenter Password fields, and choose the appropriate protocol.

Step 5

Enter the timeout and retries values.
These values work together to determine how often and how long Emergency Responder 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, Emergency Responder 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.

The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.

Step 6

Click Insert.

Step 7

If you must create more than one setting, return to Step 2.
Whenever you change the SNMPv3 settings on a switch or Unified CM server, you must update the associated setting in Emergency Responder:

- To change an SNMPv3 setting, select it in the list. Emergency Responder 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 SNMPv3 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 setting's entry.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Phone Tracking Schedule

The Phone Tracking Schedule page appears when you choose Phone Tracking > Schedule.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Phone Tracking Schedule page to define the Cisco Emergency Responder (Emergency Responder) schedule for updating phone and switch information from the network. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Cisco Unified Communications Manager to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone ERL.

- Switch Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Ensure that your ERL administrator updates the ERL assignment for new ports.

The following table describes the Phone Tracking Schedule page.

Phone Tracking Schedule Page

Field

Description

Notes

Incremental Phone Tracking

Incremental Phone Tracking Interval

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.

The default is 30 minutes.

The range of the interval that can be defined is 5 to 300 minutes.

Add New Schedule

Enter the schedule that you want to add:

1. Select the days of the week when you want to run the switch port and phone update process.

2. Select the time of day when you want the process to run. 00 hour and 00 min is midnight. Time is based on the 24-hour clock.

We recommend that you run the switch port and phone update process at least once per day. Because of the added network traffic, it is best to run the process outside normal business hours.

Insert button

Click Insert to add the schedule to the list of schedules.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

Click Update when viewing an existing schedule to save changes that you make to the schedule.

Only available when viewing an existing schedule.

Switch-Port and Phone Update Schedule

The list of schedules you have defined.

To change a schedule, click the Hour link, the Minute 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.

If any schedules overlap, only one schedule is run.

Add New button

Click Add New to add another schedule.

Related Tasks

Define Phone Tracking and Switch Update Schedules

Manually Run the Switch-Port and Phone Update Process

Related References

E911 and Cisco Emergency Responder Terminology

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Cisco Unified Communications Manager Clusters

The Cisco Unified Communications Manager Clusters page appears when you choose Phone Tracking > Cisco Unified Communications Manager.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Cisco Unified Communications Manager Clusters page to identify the Cisco Unified Communications Manager clusters whose emergency calls this Emergency Responder group handles. Only assign a Cisco Unified Communications Manager cluster to a single Emergency Responder group. Emergency Responder gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones.

The following table describes the Cisco Unified Communications Manager Clusters page.

Cisco Unified Communications Manager Clusters Page

Field

Description

Notes

Add New Cisco Unified Communications Manager Cluster

Cisco Unified Communications Manager

The IP address or DNS name of a Cisco Unified Communications Manager server that is running Cisco Unified Communications Manager and SNMP services.

Only add one server per Cisco Unified Communications Manager cluster— Emergency Responder can identify the other servers in the cluster. The Cisco Unified Communications Manager server you specify represents the cluster in which it is a member.

When viewing a previously defined Cisco Unified Communications Manager server, Emergency Responder 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.

After the IP address or DNS name has been configured, it cannot be modified.

CTI Manager

The IP address or DNS name of the CTI Manager used by the specified Cisco Unified Communications Manager server.

CTI Manager User Name

The name of the user created in the Cisco Unified Communications Manager server for Emergency Responder use.

This user must have specific characteristics and device assignments. See Create Emergency Responder Cisco Unified Communications Manager User 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, Emergency Responder calls the onsite alert personnel for the originating ERL using the telephony ports you configure here.

You must first create this port in Cisco Unified Communications Manager. See Create Required CTI Ports for more information.

Number of Telephony Ports

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 Emergency Responder can make to onsite alert personnel.

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, Emergency Responder uses 3000, 3001, 3002, and 3003.

Enable Secure Connection

Enable Secure Connection check box

Check this check box to enable a secure connection. You can enter data in the other fields of this section only if you have enabled Secure Connection.

TFTP Server IP Address

The IP address of the TFTP server.

TFTP Server Port

The port of the TFTP server.

Backup TFTP Server IP Address

The IP address of the backup TFTP server, for the Unified CM node being added.

CAPF Server IP Address

The IP address of the CAPF server.

CAPF Server Port

The port of the CAPF server.

Instance ID for Publisher

The instance ID for the Publisher node.

Secure Authentication String for Publisher

The secure authentication string for the Publisher node.

Instance ID for Subscriber

The instance ID for the Subscriber node.

Secure Authentication String for Subscriber

The secure authentication string for the Subscriber node.

AXL Settings

AXL Username

The username for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Password

The password for the application user on Cisco Unified Communications Manager with privileges to perform AXL queries.

AXL Port Number

The port number that is used by the application on Cisco Unified Communications Manger. The default value is 8443.

SNMP Settings

Use SNMPv3 for discovery

Check this check box if the Cisco Unified Communications Manager has SNMPv3 enabled and you want Emergency Responder to use SNMPv3 for discovery.

Insert button

Click Insert to add the new Cisco Unified Communications Manager server to the list of servers.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Update button

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.

Cisco Unified Communications Manager Clusters

Add New button

Click Add New to add another Cisco Unified Communications Manager server.

Cisco Unified Communications Manager list

A list of Cisco Unified Communications Manager servers defined for this Emergency Responder group. Click a server link or the Edit icon to view and modify the Emergency Responder configuration for the server. Click the Delete icon to delete the server.

Related Tasks

Identify Cisco Unified Communications Manager Clusters

Create Emergency Responder Cisco Unified Communications Manager User

Create Required CTI Ports

Related References

E911 and Cisco Emergency Responder Terminology

Identify Cisco Unified Communications Manager Clusters

You must identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group that you are configuring. Cisco Emergency Responder obtains the list of phones registered with these Unified CM servers and tracks the movements of these phones

Cisco Emergency Responder 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 Unified CM clusters.

You must activate Cisco Unified Communications Manager on the server before Emergency Responder can access the Unified CM cluster list. For more information, refer to CSCsx52550 using the Software Bug Toolkit.

Every Unified CM server in the Unified CM cluster must be running SNMP services so that Emergency Responder 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 Emergency Responder tries to create a provider with the Cisco Emergency Responder cluster. Cisco Emergency Responder 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:

- Create Emergency Responder Cisco Unified Communications Manager User

- Create Required CTI Ports

To identify one Unified CM server per Unified CM cluster that you want to manage with the Cisco Emergency Responder group you are configuring, follow these steps:

Procedure

Step 1

Select Phone Tracking > Cisco Unified Communications Manager Details.
Cisco Emergency Responder opens the Unified CM Details page.

Step 2

Enter the details for the Unified CM server:

- Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Unified CM and SNMP services. Do not define more than one Unified CM server within the same Unified CM cluster in the Emergency Responder configuration.

- CTI Manager—The IP address or DNS name of the CTI manager for the cluster to which the server belongs.

- CTI Manager User Name—The user you created for Cisco Emergency Responder. See Create Emergency Responder Cisco Unified Communications Manager User for more information.

- CTI Manager Password—The user password.

- Backup CTI 1 Manager—The IP address or DNS name of the first backup CTI manager for the cluster.

- Backup CTI 2Manager—The IP address or DNS name of the second backup CTI manager for the cluster.

- Telephony Port Begin Address—The first CTI port address in the sequence of ports you created for Emergency Responder use. See Create Required CTI Ports for more information.

- Number of Telephony Ports—The number of CTI ports in the sequence you created for Emergency Responder use.

Step 3

To establish secure JTAPI communications, do the following:

1. Check the Enable Secure Connection check box.

2. 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 Unified CM 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
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 Create Required CTI Ports for details.

Step 4

To configure the AXL Settings, do the following:

1. Enter the AXL Username configured on the Cisco Unified Communications Manager.

2. Enter the password for the AXL User.

3. Enter the Port Number. By default Port 8443 is chosen.

Step 5

Select the SNMP Settings checkbox if the Cisco Unified Communications Manager has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Step 6

Click Insert.
Emergency Responder adds the Unified CM server to the list of servers. Repeat this procedure if you are supporting other Unified CM clusters with this Emergency Responder group.

Tip:

- To view or change a Unified CM server 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 Unified CM server from the Emergency Responder configuration, click it in the list of servers, then click Delete.

Create Emergency Responder Cisco Unified Communications Manager User

You must add Emergency Responder as a Unified CM user. The settings you enter here are used when you configure the Unified CM settings for Emergency Responder.

Procedure

Step 1

In Unified CM, select User Management > Application User. Click the Add New button.
Unified CM displays the Application User Configuration page.

Step 2

Complete the following required fields:

- UserID—Use a descriptive name such as "Emergency_Responder_User."

- Password—Enter a password for this user.

- Confirm Password—Reenter the password for this user.

Step 3

In the Device Information section, select the desired route points and CTI ports and then click the down arrow to add the selected devices to the user control list. The list of devices appears in the Controlled Devices area.

Step 4

Select the following devices:
Note:
You may need to use Find Phones or Find Route Points to select the desired devices.

- All CTI ports created for Cisco Emergency Responder use. For more information, see "Creating the Required CTI Ports" section.

- The primary emergency call number, for example, 911.

- The backup emergency call number, for example, 912.

- The route point used for ELINs, for example, 913XXXXXXXXXX.

Step 5

Click Save.

Step 6

In the Unified CM menu at the top, click User Management > User Group.
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.

Step 8

Click the Standard CTI Allow Calling Number Modification user group link to display the User Group configuration page.

Step 9

Click Add Application Users to Group.
The Find and List Application Users popup window appears.

Step 10

Enter the User ID and click Find.
The list of Applications users appears.

Step 11

Check the check box next to the user ID and click Add Selected.
Unified CM adds the selected user to the Standard CTI Allow Calling Number Modification user group.

Step 12

Choose 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.

Step 14

Click the Standard CTI Enabled group.
Repeat steps 9 through 11 to add the user to the Standard CTI Enabled group.

Create Required CTI Ports

Emergency Responder 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 that you configure is the number of simultaneous calls Emergency Responder can make to these personnel. It does not relate to the number of emergency calls Emergency Responder can handle or forward to the PSAP. There is no configurable limitation to the number of simultaneous emergency calls that Emergency Responder can handle.

Before You Begin
Emergency Responder 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.

Procedure

Step 1

Select Device > Phone.
Unified CM opens the Find and List Phones page.

Step 2

Click Add a New Phone.
Unified CM opens the Add a New Phone page.

Step 3

Select CTI Port for Phone Type and click Next.
Unified CM opens the Phone Configuration page.

Step 4

Configure the CTI Port, entering this information:

- Device Name- Enter something meaningful to you, for example, CTI3001.

- Device Pool- Select an appropriate device pool. This device pool must use the G.711 region.

- Calling Search Space- Select PhoneCSS.

Step 5

Click Insert.
Unified CM creates the CTI port and asks if you want to configure line 1. Click OK. Unified CM opens the Directory Number Configuration page.

Step 6

Configure line 1 for the CTI port, entering this information:

- Partition- Select Phones.

- Calling Search Space- Select 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.
Unified CM 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.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

Related Tasks

Manually Run the Switch-Port and Phone Update Process

Identify Unlocated Phones

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

LAN Switch Identification

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export LAN Switch

The Export LAN Switch page appears when you click Export in the LAN Switch Details page (opened when you choose Phone Tracking > LAN Switch Details).

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Export LAN Switch page to create a file containing the Emergency Responder switch configuration.

If you must update several switch entries in Emergency Responder, 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 Download File for more information.

The following table describes the Export LAN Switch page.

Export LAN Switch Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma- separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a LAN switches configuration file and click Download to download the file to your local system.

Related Tasks

Export Switch Information

Download File

Import a Group of Switches

Related References

LAN Switch Details

E911 and Cisco Emergency Responder Terminology

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Import LAN Switch

The Import LAN Switch page appears when you click Import in the LAN Switch Details page (opened when you choose Phone Tracking > LAN Switch Details).

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the Import LAN Switch page to add several switches at once to the Emergency Responder 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 Upload File for more information.

The following table describes the Import LAN Switch page.

Import LAN Switch Page

Field

Description

Select Import Format

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

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.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the information in the import file to your Emergency Responder configuration.

Emergency Responder 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 choose OK. If you choose Cancel, Emergency Responder 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 Manually Run the Switch-Port and Phone Update Process.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Related Tasks

Import a Group of Switches

Export Switch Information

Upload File

Related References

LAN Switch Details

E911 and Cisco Emergency Responder Terminology

Import 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 can 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 Emergency Responder 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. Emergency Responder 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 to import it. Use the following procedure 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 Set Up SNMPv2 for more information.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.

Step 3

Select the file format, and the name of the file you want to import.

Step 4

Click Import.
Emergency Responder 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, Emergency Responder imports the switches but does not run the phone tracking process.

After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.

Step 5

Click Close to close the window.

Step 6

If you did not run phone tracking on the imported switches, select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.

Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports to run the process only on the selected switch.

Export Switch Information

You can export your Cisco Emergency Responder (Emergency Responder) configuration. By exporting this information, you can back up your data, or create a file for updating a large number of switch definitions in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or network administrator authority to export switch definitions.

Procedure

Step 1

Select Phone Tracking > LAN Switch Details.
Emergency Responder opens the LAN Switch Details page.

Step 2

Click Export in the switch list.
Emergency Responder opens the Export LAN Switch page.

Step 3

Select the file type and enter the file name for the export file. Do not include a file extension.

Step 4

Click Export.
Emergency Responder creates the export file. Click Close to close the window.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

LAN Switch Details

The LAN Switch Details page appears when you choose Phone Tracking > LAN Switch Details.

Note

Cisco Emergency Responder supports SNMP Version 1, Version 2 , Version 2C, and Version 3 of a LAN switch.

Authorization Requirements

You must have system administrator or network administrator authority to access this page.

Description

Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure that 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 Emergency Responder, and are assigned to the Default ERL.

The following table describes the LAN Switch Details page.

LAN Switch Details Page

Field

Description

LAN Switch Details

Switch Host Name/IP Address

The IP address or DNS name of the switch.

Description

Description of this switch.

Enable CAM-based Phone Tracking

Check this check box 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, Emergency Responder must use the Content Addressable Memory (CAM) information about the switch to identify phones.

Use port description as port location

Check this check box if you want to display the switch port description that is configured on the switch in the Location Field.

Use SNMPv3 for Discovery

Select this check box if the switch has SNMPv3 enabled and Emergency Responder should discover it using SNMPv3.

Insert button

Check Insert to add the switch to the list of switches.

When you click Insert, Emergency Responder 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 add the switch to the configuration without running the process right away.

Note:
See Manually Run the Switch-Port and Phone Update Process for information about running the process if you select not to run it immediately.

Update button

Click Update when viewing an existing switch to save changes that you make to the switch.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

LAN Switches

LAN Switch list

A list of the switches you have already defined. Click 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.

Add LAN Switch button

Click Add LAN Switch to add another switch.

Export

Click the Export link to export the switch definitions to another file. See Export LAN Switch for more information.

Import

Click the Import link to import a list of switches into the Emergency Responder configuration. This list might be exported from your network management software. See Import LAN Switch for more information.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Run Switch-Port and Phone Update

When you choose 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 Emergency Responder."

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Run Switch-Port and Phone Update page to run manually the switch port and phone update process.

Related Tasks

Manually Run the Switch-Port and Phone Update Process

Define Phone Tracking and Switch Update Schedules

Identify Unlocated Phones

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

Define Phone Tracking and Switch Update Schedules

To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:

- Phone Tracking—A periodic comparison of the phones registered with Unified CM to the location information obtained from the switches. If a phone moves, Emergency Responder updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see Identify Unlocated Phones).

Note

If you do not configure a switch port phone update schedule, the default schedule runs at midnight.

- Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin
You must have system administrator or network administrator authority to define the schedule.

Procedure

Step 1

Select Phone Tracking > Schedule.
Emergency Responder opens the Schedule page.

Step 2

Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder runs the phone tracking process this number of minutes after finishing the previous phone tracking process.

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. Emergency Responder adds the schedule to the list.

- Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Emergency Responder adds the schedule to the list.
If you define schedules that overlap, Emergency Responder only runs one process.

Note:
The Emergency Responder Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Unified CM must be set to a value greater than the Emergency Responder incremental phone tracking interval, for tracking phone changes efficiently.

To change a switch port and phone update schedule, click the schedule in the list. Emergency Responder loads the schedule's settings in the schedule fields. Make your changes and click Update. To delete a schedule, click the delete icon on the schedule's list entry.

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

Related Tasks

Manually Run the Switch-Port and Phone Update Process

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Switch Port Configuration

LAN Switch Identification

Switch Port Configuration

After the network administrator adds switches to the Emergency Responder 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 that you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments are only 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 Data Integrity and Reliability for more information.

LAN Switch Identification

You must tell Cisco Emergency Responder (Emergency Responder) which switches to manage. Emergency Responder 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 Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder 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.

The following sections describe how to identify switches to Emergency Responder, and how to export switch information.

Manually Run the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see Define Phone Tracking and Switch Update Schedules 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.

Because the switch port and phone update process does extensive checking, only run it if you are trying to refresh the entire Emergency Responder 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. To run on individual switches, select Phone Tracking > LAN Switch Details, select the switch in the left-hand column then click Locate Switch Ports.

These are some reasons you might run phone tracking on an individual switch:

- You add a switch to Emergency Responder. When you add a switch, Emergency Responder 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 Ports. Emergency Responder runs the process for all switches you added to the Emergency Responder 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 Emergency Responder.

- You can add and delete IP subnet-based ERLs.

Manually run the switch port and the following phone update process if:

- You want to refresh the Emergency Responder tracking results.

- You add switches to Emergency Responder by importing switch definitions, as described in the Import a Group of Switches, but you did not run phone tracking during the importation.

- If you find a large number of entries in the unlocated phones list (see Identify Unlocated Phones), run this process to see if Emergency Responder can find some of those phones. See Unlocated Phones 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.

Procedure

Select Phone Tracking > Run Switch-Port & Phone Update.
Emergency Responder runs the process without changing the page you are viewing. Any newly discovered ports are assigned to the Default ERL.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export Switch Ports

The Export Switch Ports page appears when you click Export in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports ).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Switch Ports page to create a file containing the Emergency Responder switch port configuration.

If you must 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 Download File for more information.

The following table describes the Export Switch Ports page.

Export Switch Ports Page

Field

Description

Select Export Format

The format to use for the file, such as CSV (comma-separated values).

Enter Export File Name

The name of the file you want to create. Do not include the file extension.

Export button

Click Export to create the file. The Status box shows the status of the exportation.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Related Tasks

Export Switch Port Information

Download File

Set Up Large Number of Ports

Related References

Switch Port Details

E911 and Cisco Emergency Responder Terminology

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Import Switch Ports

The Import Switch Ports page appears when you click Import in the Switch Port Details page (opened when you choose ERL Membership > Switch Ports).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Import Switch Ports page to add or update several switch port configurations at once to the Emergency Responder configuration. Switch port configurations are mappings of ports to ERLs.

To create the switch port import file, follow these steps:

1. Export the switch port details.

2. Modify the ERK field of these records and save the file.

3. 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 Upload File for more information.

The following table describes the Import Switch Ports page.

Import Switch Ports Page

Field

Description

Select Import Format

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 Emergency Responder, modify the export file using a spreadsheet program, and then import the modified file.

Note:
See Export Switch Port Information for information about exporting switch port information.

Select File to Import

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the information in the import file to your Emergency Responder configuration. ERL assignments in the import file override assignments that already exist in the Emergency Responder configuration.

Note:
Port ERL configurations are only updated if Emergency Responder has discovered the port before you import the port configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Related Tasks

Set Up Large Number of Ports

Upload File

Export Switch Port Information

Related References

Switch Port Details

E911 and Cisco Emergency Responder Terminology

Set Up Large Number of Ports

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 Emergency Responder (see Export Switch Port Information), 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 following procedure explains how to get to this page. Links on the page also displays the detailed information about the required file format for the import file if you need it.

Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.

You can only configure ports defined for the Emergency Responder group to which you are logged in.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Import.
Emergency Responder opens the Import Switch Ports page.

Step 3

Select the format of your import file (csv) from the pull–down menu.

Step 4

Click Upload to upload the file from your local machine. See Upload File for information about using the Upload utility.

Step 5

Select your import file using the Select File to Import pull–down menu.

Step 6

Click Import.
Emergency Responder 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 Emergency Responder configuration.

Step 7

Click Close to close the Import Switch Port page.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

Export Switch Port Information

You can export your Emergency Responder port configuration. By exporting this information, you can back up your data, or create a file that you can use to update a large number of switch port mappings in Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.

Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.

Procedure

Step 1

Select ERL Membership > Switch Ports .
Emergency Responder opens the Switch Port Details page.

Step 2

Click Export.
Emergency Responder opens the Export Switch Ports page.

Step 3

Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the export location.

Step 4

To download the exported file to your local system, select the file name from the Select file to download pull–down menu and click Download.

Step 5

Click Close to close the Export Switch Port page.

Switch Port Details

The Switch Port Details page appears when you choose ERL Membership > Switch Ports.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder 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 switch, which have ports that can be uniquely identified by Switch ID, Module ID and Port ID combination, Emergency Responder 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).

- 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.

The following table describes the Switch Port Details page.

Switch Port Details Page

Field

Description

Notes

Switch Port Search Parameters

Find ports where...

Enter search criteria to select the ports that you want to view or configure.

To view all ports, 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 pull-down menu, select the field that 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.

If you are configuring ports, you must first generate a list of ports using the Find button.

The list of switch ports that match your search criteria, one line per port.

To assign ERLs to selected ports, check the check box to the left of the switch details, enter the ERL name in the text box, or click Search ERL to find and select the ERL, then click Assign ERL.

To view and update the phone location for a port, click the View link in the port's Location column.

To change the fields shown in the list and to change their order, click Edit View. This action opens a separate Edit View page:

- To add a field, select it in the Available Fields list and click > (right arrow).

- To remove a field, select it in the Selected Fields list and click < (left arrow).

Note:
You cannot remove the ERL Name from the table view.

Click Apply to save your changes on the Edit Table View page. Click Close to close the window.

Emergency Responder displays a maximum number of 1,000 switch port records at a time. If the search results in more than 1,000 switch ports, an error message to refine the search is displayed.

If a large number of ports match your search criteria, Emergency Responder 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.

Export

Click Export to export the ERL to switch port configuration to another file. See Export Switch Ports for more information.

Import

Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See Import Switch Ports for more information.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Configure IP Subnet

To reach the Configure IP Subnet page, choose ERL Membership > IP Subnets and click on the Add New IP Subnet link. The Configure IP Subnet page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Configure IP Subnet page to manually define an IP subnet and its ERL. You must manually define an IP Subnet if Emergency Responder cannot automatically track the type of phone. One example is if the phone is wireless. See Network Hardware and Software Requirements for information about phone support.

You can choose not to track the phones in an IP Subnet by checking the check box Do not track phones under this IP subnet. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

The following table describes the Configure IP Subnet page.

Configure IP Subnet Page

Field

Description

Add New IP Subnet

Subnet ID

The IP address of the subnet you want to define.

Subnet Mask

The mask of the subnet you want to define.

Do not track phones under this IP subnet

Check this check box if you do not want this IP subnet and the underlying phones tracked by Cisco Emergency Responder. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

Location (optional)

The location of the new IP subnet.

ERL Name

The ERL to assign to the subnet. Type in a valid ERL name or click Search ERL to find and select the ERL.

Insert button

Click Insert to add the subnet.

When you click Insert, Emergency Responder asks if you want to run the switch port and phone update process on the switch immediately. Click OK to run the process now, or click Cancel to add the IP subnet to the configuration without running the process immediately.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related Tasks

Set Up IP Subnet-based ERLs

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Synthetic Phones

Set Up IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Emergency Responder supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco Emergency Responder then routes the emergency calls based on the configured IP subnet and ERL associations.

This feature is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.

Use IP subnet-based ERLs to locate and track wireless endpoints, such as Cisco Unified Wireless IP Phone 7920 series devices and Cisco clients using wireless IP connection. Cisco Emergency Responder cannot locate or track wireless endpoints to a Cisco Access Point.

Note

Subnet-based tracking is limited by the IP subnet addressing plan. It cannot distinguish location within a same IP Subnet.

Before You Begin
You must have system administrator or ERL administrator authority to access this page.

Procedure

Step 1

Select ERL Membership > IP subnets and click the Add new IP subnet link on the Find and List IP Subnets page.
Emergency Responder opens the Configure IP Subnets page.

Step 2

At the Subnet ID field, enter the IP address of the subnet that you want to define, for example,10.76.35.0.

Step 3

At the Subnet Mask field, enter the mask of the subnet that you want to define, for example, 255.255.255.224.

Step 4

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.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the subnet and click Select ERL. The Find ERL page closes.

Step 7

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

To change the fields on this page back to the last saved settings, click Cancel Changes.

Step 9

To return to the Find and List IP Subnets page, click Back to IP Subnet Search.

Synthetic Phones

With Emergency Responder, you can use Cisco Unified Operations Manager to monitor the health and functionality of Cisco Emergency Responder. To use Cisco Unified Operations Manager with Cisco Emergency Responder, you configure a synthetic phone in Emergency Responder and associate the synthetic phone to an ERL that is used as a test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can only configure test ERLs for conventional ERLs. You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

For more information, see Set Up Test ERLs.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

IP Subnet Phones

The IP Subnet Phones page appears when you choose ERL Membership/ IP Subnets and click the View Phones icon in any records returned by the IP Subnet Search.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the IP subnet Phones page to view all the IP subnet phones discovered by Emergency Responder.

The IP subnet phones page displays the subnet ID, 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 References

Find and List IP Subnets

Configure IP Subnet

Find and List IP Subnets

The Find and List IP Subnets page appears when you choose ERL Membership > IP Subnets.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List IP Subnets page.

Find and List IP Subnets Page

Field

Description

IP Subnet Search Parameters

Find IP Subnets where...

To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.

IP Subnets

IP Subnets list

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 preceding records or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field 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 of the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See IP Subnet Phones.

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

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.

Add New IP Subnet

Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See Configure IP Subnet for more information

Export

Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See Export IP Subnets for more information,

Import

Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See Import IP Subnets for more information,

Configure IP Subnet

To reach the Configure IP Subnet page, choose ERL Membership > IP Subnets and click on the Add New IP Subnet link. The Configure IP Subnet page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Configure IP Subnet page to manually define an IP subnet and its ERL. You must manually define an IP Subnet if Emergency Responder cannot automatically track the type of phone. One example is if the phone is wireless. See Network Hardware and Software Requirements for information about phone support.

You can choose not to track the phones in an IP Subnet by checking the check box Do not track phones under this IP subnet. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

The following table describes the Configure IP Subnet page.

Configure IP Subnet Page

Field

Description

Add New IP Subnet

Subnet ID

The IP address of the subnet you want to define.

Subnet Mask

The mask of the subnet you want to define.

Do not track phones under this IP subnet

Check this check box if you do not want this IP subnet and the underlying phones tracked by Cisco Emergency Responder. If you do not track the phones in an IP subnet, then you do not need the Emergency Responder User Licenses for these phones.

Location (optional)

The location of the new IP subnet.

ERL Name

The ERL to assign to the subnet. Type in a valid ERL name or click Search ERL to find and select the ERL.

Insert button

Click Insert to add the subnet.

When you click Insert, Emergency Responder asks if you want to run the switch port and phone update process on the switch immediately. Click OK to run the process now, or click Cancel to add the IP subnet to the configuration without running the process immediately.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Export IP Subnets

To reach the Export IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Export link. The Export IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export IP Subnets page to create a file containing the Emergency Responder Export IP Subnet configurations.

If you must 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 Download File for more information.

The following table describes the Export IP Subnets page.

Export IP Subnets Page

Field

Description

Select Export Format

Select the format used in the file that 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

Click Export to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Related Tasks

Download File

Related References

Find and List IP Subnets

Import IP Subnets

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Find and List IP Subnets

The Find and List IP Subnets page appears when you choose ERL Membership > IP Subnets.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List IP Subnets page.

Find and List IP Subnets Page

Field

Description

IP Subnet Search Parameters

Find IP Subnets where...

To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.

IP Subnets

IP Subnets list

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 preceding records or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field 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 of the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See IP Subnet Phones.

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

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.

Add New IP Subnet

Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See Configure IP Subnet for more information

Export

Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See Export IP Subnets for more information,

Import

Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See Import IP Subnets for more information,

Import IP Subnets

To reach the Import IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Import link. The Import IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import IP Subnets page.

Import IP Subnets Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Import IP Subnets

To reach the Import IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Import link. The Import IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

If you must 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 Upload File for more information.

The following table describes the Import IP Subnets page.

Import IP Subnets Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload button

Click Upload to upload a file from your local system. See Upload File for more information.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Text box that displays status information.

Related Tasks

Upload File

Related References

Find and List IP Subnets

Export IP Subnets

Find and List IP Subnets

The Find and List IP Subnets page appears when you choose ERL Membership > IP Subnets.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List IP Subnets page.

Find and List IP Subnets Page

Field

Description

IP Subnet Search Parameters

Find IP Subnets where...

To list specific IP subnets, select the search criteria and click Find. To list all IP subnets, click Find without entering any criteria.

IP Subnets

IP Subnets list

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 preceding records or click the Edit icon to modify that IP subnet. The Configure IP Subnets page appears. Change the Location field 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 of the IP subnet phones. The IP Subnet Phones page displays a list of the discovered phones in the IP subnet. See IP Subnet Phones.

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

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.

Add New IP Subnet

Click Add New IP Subnet to configure new IP subnets. The Configure IP Subnets page appears. See Configure IP Subnet for more information

Export

Click Export to create a file containing the IP subnets configuration information. The Export IP Subnet page appears. See Export IP Subnets for more information,

Import

Click Import to import IP subnet configuration information from a file. The Import IP Subnet page appears. See Import IP Subnets for more information,

Export IP Subnets

To reach the Export IP Subnets page, choose ERL Membership > IP Subnets. On the Find and List IP Subnets page, click the Export link. The Export IP Subnets page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export IP Subnets page to create a file containing the Emergency Responder Export IP Subnet configurations.

If you must 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 Download File for more information.

The following table describes the Export IP Subnets page.

Export IP Subnets Page

Field

Description

Select Export Format

Select the format used in the file that 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

Click Export to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pull-down menu to select a file and click Download to download the file to your local system.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

Unlocated Phones

The Unlocated Phones page appears when you choose ERL Membership > Unlocated Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Unlocated Phones page to identify phones that are registered with Cisco Unified Communications Manager, but which Emergency Responder cannot locate. A phone can become unlocated for several reasons:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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.

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you might have to manually assign a phone to an ERL on this page. See Unlocated Phones for troubleshooting information.

The following table describes the Unlocated Phones page.

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 pull-down 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.

Assign ERL

To assign the ERL, select the phones by checking the check box next to the phones, click Search ERL to find and select the ERL, and click Assign ERL.

Unassign ERL

To unassign a ERL, select the phones and click on Unassign ERL button.

List of unlocated phones

A list of the phones Emergency Responder could not assign to a specific ERL. The following information is displayed:

- Emergency Responder Group

- Phone IP Address

- Phone Mac Address

- Phone Extension

- Assigned ERL

- Effective ERL

- ERL Rule

If the phone has moved to a switch served by a different Emergency Responder group, the Emergency Responder group name is shown for the phone in the list.

Note:
If there are a lot of unlocated phones, Emergency Responder 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.

Related Tasks

Identify Unlocated Phones

Related References

E911 and Cisco Emergency Responder Terminology

Find and List Manually Configured Phone

Related Information

Unlocated Phones

Identify Unlocated Phones

If Emergency Responder 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 Emergency Responder from locating the phones.

These are some things that can prevent Emergency Responder from locating a phone:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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 Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list.

- No IP subnet is configured for the phone.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See Unlocated Phones for more detailed information about resolving these problems.

In addition, Emergency Responder also displays the following in the unlocated phone list:

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Before You Begin
You must have system administrator or ERL administrator authority to view or configure unlocated phones.

Procedure

Step 1

Select ERL Membership > Unlocated Phones.
Emergency Responder opens the Unlocated Phones page.

Step 2

Enter search criteria to list the unlocated phones.

Step 3

Check the check box next to the phone that you want to assign an ERL.

Step 4

Click the Search ERL button next to the ERL Name field to select the ERL you want to assign to the selected phone. The Find ERL page appears.

Step 5

Enter the ERL Search Parameters and click Find. The search results appear.

Step 6

Click the radio button next to the ERL that you want to assign to the unlocated phones and click Select ERL. The Find ERL page closes.

Step 7

Click the Assign ERL button.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.

Note:
To unassign a ERL, select the phones and click on Unassign ERL button.

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:
Emergency Responder 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 must be manually configured. See Manually Define Phones for more information.

Unlocated Phones

Emergency Responder obtains a list of registered phones from Unified CM and tries to locate all phones. If Emergency Responder 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 is 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 Emergency Responder can resolve some of the problems automatically. See Manually Run the Switch-Port and Phone Update Process for more information.

These are some of the situations that can prevent Emergency Responder from locating a phone:

- If more than one switch port reports the phone as a Cisco Discovery Protocol (CDP) neighbor, then the phone is placed in unlocated phones. This condition is corrected in the next phone tracking when only one switch port reports this phone as its CDP neighbor.

- The phone is attached to a switch that is not defined in Emergency Responder. See LAN Switch Identification for information about 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 Network Hardware and Software Requirements for a list of supported switches. See Manually Define Phones for information about 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. Emergency Responder 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 Emergency Responder. Correct the Emergency Responder configuration. See Set Up SNMPv2.

- The phone requires CAM table access, but CAM tracking is not enabled for the switch in Emergency Responder. See LAN Switch Identification.

- There is a network outage preventing communication between the Emergency Responder server and the switch. Locate and resolve the network outage problem.

Unreachable switches are not retried until Emergency Responder runs the next full switch port and phone update process, unless you run it against the individual switch.

- The phone has moved to a switch served by a different Emergency Responder group. If this is the case, the Emergency Responder group name is shown for the phone in the unlocated phones list. If the phone is not in the next incremental phone tracking process after it is moved, the phone remains unlocated in any Emergency Responder 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 LAN Switch Identification for information about enabling CAM-based tracking, and Network Hardware and Software Requirements for a list of phones that require CAM-based tracking.

After fixing the problems that are preventing Emergency Responder 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 switch—Select 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 switches—Select Phone Tracking > Run Switch-Port & Phone Update.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Find and List Manually Configured Phone

The Find and List Manually Configured Phones page appears when you choose ERL Membership > Manually Configured Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Manually Configured Phones page.

Note

When you are performing this search as part of an E.164 dial plan, the "+" is a valid character.

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 that you want to find.

To find all manually configured phones, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed per page from the pull-down 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 Add New Manual Phone 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 Export Manual Phones for more information.

Import

To import Manually Configured Phone information to a file, click Import on the Find and List Manually Configured Phones page. See Import Manual Phones for more information.

Export Unlocated Phones

To view the Export Unlocated Phones page, choose ERL Membership > Unlocated Phones and click Export.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Unlocated Phones page to do one of two actions:

- Create a file containing the Emergency Responder Export Unlocated Phones.

- Use the Download utility to download a file containing the Emergency Responder Export Unlocated Phones.

The following table describes the fields found on the Export Unlocated Phones page.

Export Unlocated Phones Page

Field

Description

Select Export Format

Select the file format that matches the file being imported.

After you select the format, click View Sample File to see an example of the expected format and sequence of values. Use this example when creating your imported file.

Enter Export File Name

The name of the file that you want to create. Do not include the file extension.

Export button

Click Export to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Download

Select a File to Download

Use the pulldown menu to select a file. Click Download to download the file.

Related Tasks

Download File

Unlocated Phones

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Unlocated Phones

The Unlocated Phones page appears when you choose ERL Membership > Unlocated Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Unlocated Phones page to identify phones that are registered with Cisco Unified Communications Manager, but which Emergency Responder cannot locate. A phone can become unlocated for several reasons:

- The phone is attached to a switch that is not defined in Emergency Responder.

- 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.

- The phone that was manually assigned.

- The phone that was previously identified as an unlocated phone and assigned an ERL.

Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Emergency Responder from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you might have to manually assign a phone to an ERL on this page. See Unlocated Phones for troubleshooting information.

The following table describes the Unlocated Phones page.

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 pull-down 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.

Assign ERL

To assign the ERL, select the phones by checking the check box next to the phones, click Search ERL to find and select the ERL, and click Assign ERL.

Unassign ERL

To unassign a ERL, select the phones and click on Unassign ERL button.

List of unlocated phones

A list of the phones Emergency Responder could not assign to a specific ERL. The following information is displayed:

- Emergency Responder Group

- Phone IP Address

- Phone Mac Address

- Phone Extension

- Assigned ERL

- Effective ERL

- ERL Rule

If the phone has moved to a switch served by a different Emergency Responder group, the Emergency Responder group name is shown for the phone in the list.

Note:
If there are a lot of unlocated phones, Emergency Responder 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.

Find and List Manually Configured Phone

The Find and List Manually Configured Phones page appears when you choose ERL Membership > Manually Configured Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Manually Configured Phones page.

Note

When you are performing this search as part of an E.164 dial plan, the "+" is a valid character.

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 that you want to find.

To find all manually configured phones, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed per page from the pull-down 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 Add New Manual Phone 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 Export Manual Phones for more information.

Import

To import Manually Configured Phone information to a file, click Import on the Find and List Manually Configured Phones page. See Import Manual Phones for more information.

Related References

E911 and Cisco Emergency Responder Terminology

Add New Manual Phone

Export Manual Phones

Import Manual Phones

Related Information

IP Subnet Phones

IP Subnet Phones

The IP Subnet Phones page appears when you choose ERL Membership/ IP Subnets and click the View Phones icon in any records returned by the IP Subnet Search.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the IP subnet Phones page to view all the IP subnet phones discovered by Emergency Responder.

The IP subnet phones page displays the subnet ID, the subnet mask for each IP subnet and lists all the phones tracked in that IP subnet, and when the last phone was tracked.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Add New Manual Phone

To reach the Add New Manual Phone page, choose 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.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Manual Phone page to manually define a phone ERL. You must manually define a phone if any of these conditions apply:

- Emergency Responder cannot automatically track the type of phone, for example, if the phone is analog. See Network Hardware and Software Requirements for information about 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, Emergency Responder cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure that they are correct.

The following table describes the Add New Manual Phone page.

Add New Manual Phone Page

Field

Description

Add New Manual Phone

Line Number

The extension of the phone you want to define.

MAC Address

The MAC address of the phone, if it is an IP phone.

IP Address

The IP address of the phone, if it is an IP phone.

Phone Type

The type of phone, such as analog. This field is for your information only.

Version

The version of the phone software, if any. This field is for your information only.

Location

The location of the phone.

ERL Name

The ERL that you want to assign to the phone. To find and select the ERL, click Search ERL.

Insert button

Click Insert to add the phone to the list of phones.

Note:
The Insert button only appears when you are adding a phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Export Manual Phones

To reach the Export Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Export link. The Export Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Manual Phones page to create a file containing the Emergency Responder manual phone configurations.

If you must 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 Download File for more information.

The following table describes the Export Manual Phones page.

Export Manual Phones Page

Field

Description

Export Manual Phones

Select Export Format

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 that you want to create. Do not include the file extension.

Export button

Click Export to export the file to a file.

Close button

Click Close to close the window.

Download

Select a file to download

Use the pull-down menu to select a file and then click Download to download the file to your local system.

Import Manual Phones

To reach the Import Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 must 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 Upload File for more details.

The following table describes the Import Manual Phones page.

Import Manual Phones Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload

Click Upload to upload a file from a local system. The Upload File page appears. See Upload File for more details.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Displays status messages.

Add New Manual Phone

To reach the Add New Manual Phone page, choose 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.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Manual Phone page to manually define a phone ERL. You must manually define a phone if any of these conditions apply:

- Emergency Responder cannot automatically track the type of phone, for example, if the phone is analog. See Network Hardware and Software Requirements for information about 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, Emergency Responder cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure that they are correct.

The following table describes the Add New Manual Phone page.

Add New Manual Phone Page

Field

Description

Add New Manual Phone

Line Number

The extension of the phone you want to define.

MAC Address

The MAC address of the phone, if it is an IP phone.

IP Address

The IP address of the phone, if it is an IP phone.

Phone Type

The type of phone, such as analog. This field is for your information only.

Version

The version of the phone software, if any. This field is for your information only.

Location

The location of the phone.

ERL Name

The ERL that you want to assign to the phone. To find and select the ERL, click Search ERL.

Insert button

Click Insert to add the phone to the list of phones.

Note:
The Insert button only appears when you are adding a phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related Tasks

Manually Define Phones

Related References

Import Manual Phones

Export Manual Phones

E911 and Cisco Emergency Responder Terminology

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Import Manual Phones

To reach the Import Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 must 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 Upload File for more details.

The following table describes the Import Manual Phones page.

Import Manual Phones Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload

Click Upload to upload a file from a local system. The Upload File page appears. See Upload File for more details.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Displays status messages.

Export Manual Phones

To reach the Export Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Export link. The Export Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Manual Phones page to create a file containing the Emergency Responder manual phone configurations.

If you must 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 Download File for more information.

The following table describes the Export Manual Phones page.

Export Manual Phones Page

Field

Description

Export Manual Phones

Select Export Format

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 that you want to create. Do not include the file extension.

Export button

Click Export to export the file to a file.

Close button

Click Close to close the window.

Download

Select a file to download

Use the pull-down menu to select a file and then click Download to download the file to your local system.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export Manual Phones

To reach the Export Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Export link. The Export Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Export Manual Phones page to create a file containing the Emergency Responder manual phone configurations.

If you must 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 Download File for more information.

The following table describes the Export Manual Phones page.

Export Manual Phones Page

Field

Description

Export Manual Phones

Select Export Format

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 that you want to create. Do not include the file extension.

Export button

Click Export to export the file to a file.

Close button

Click Close to close the window.

Download

Select a file to download

Use the pull-down menu to select a file and then click Download to download the file to your local system.

Related Tasks

Manually Define Phones

Download File

Related References

Import Manual Phones

Find and List Synthetic Phones

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Download File

Procedure

Step 1

From one of the pages listed in Table 1, click Export. The Export page appears.

Step 2

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.

Step 3

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.

Import Manual Phones

To reach the Import Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 must 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 Upload File for more details.

The following table describes the Import Manual Phones page.

Import Manual Phones Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload

Click Upload to upload a file from a local system. The Upload File page appears. See Upload File for more details.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Displays status messages.

Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you choose ERL Membership > Synthetic Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Synthetic Phones page.

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 pull-down 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 are displayed from the pull-down 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 Add New Synthetic Phone for more information.

Note:
The Add new Synthetic Phone button is also available from the Modify Synthetic Phone page.

Import Manual Phones

To reach the Import Manual Phones page, choose ERL Membership > Manually Configured Phones. On the Find and List Manually Configured Phones page, click the Import link. The Import Manual Phones page appears.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 must 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 Upload File for more details.

The following table describes the Import Manual Phones page.

Import Manual Phones Page

Field

Description

Select Import Format

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

Select the file from which you want to import data.

Upload

Click Upload to upload a file from a local system. The Upload File page appears. See Upload File for more details.

Import button

Click Import to add data from the import file to your Emergency Responder configuration.

Close button

Click Close to close the window.

Import Status

Displays status messages.

Related Tasks

Manually Define Phones

Upload File

Related References

Find and List Synthetic Phones

Manually Define Phones

To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Unified CM, even if Emergency Responder does not directly support the phone. Emergency Responder 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 Emergency Responder cannot dynamically change the ERL of a manually defined phone if that phone is moved.

You must manually define a phone if any of these conditions apply:

- Emergency Responder does not support automatic tracking of that type of phone, for example, if the phone is an analog phone connected to an analog line gateway such as analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway.

- 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.

- 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 must update the ERL assignment for the phone in Emergency Responder.

Emergency Responder does not support automatic tracking of analog phones including analog phones connected to the Analog Telephone Adapter (ATA) or the Cisco VG200 series Analog Voice Gateway. Instead, you must manually assign such phones an ERL that is based on the phone's line number.

Note

New switch ports and unlocated phones are NOT associated to Default ERLs automatically. They are treated as "ERL not configured." The Default ERL is used only internally by Emergency Responder if no other ERL is configured for that phone. Emergency Responder 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 Unified CM Extension Mobility. With Unified CM Extension Mobility, a user can log into a phone and the phone is assigned the user's 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 Unified CM Extension Mobility are connected to supported switch ports.

Before You Begin
You must have system administrator or ERL administrator authority to manually define phones.

Note

Manually configured phones can have E.164 and non-E.164 line numbers.

Procedure

Step 1

Select ERL Membership > Manually Configured Phones.
Emergency Responder opens a new page, the Find and List Manually Configured Phones page.

Step 2

Enter the extension and click Find to search for phones that you must modify. Emergency Responder 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 3

Click the Delete icon on the phone entry to remove a phone.

Step 4

To change an existing phone:

1. Click the phone entry in the list. Emergency Responder opens the Add/Modify Phones page with the phone information displayed in the edit boxes.

2. Make your changes and click Update. Emergency Responder updates the phone.

3. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5

To add a new phone:

1. Click Add New Manual Phone. Emergency Responder opens the Add New Manual Phone page.

2. Enter information about the phone you want to define. You must enter the line number 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.

3. To select the ERL you want to assign to the selected ports, click the Search ERL button next to the ERL Name field. The Find ERL page appears.

4. Enter the ERL Search Parameters and click Find. The search results appear.

5. Click the radio button next to the ERL that you want to assign to the manual phone and click Select ERL. The Find ERL page close.

6. Click Insert. Emergency Responder adds the phone to the list of manually defined phones.

7. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Upload File

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 Emergency Responder server, or one that you created.

Procedure

Step 1

From one of the pages listed in Table 1, click Import. The Import page appears.

Step 2

Click Upload. The Upload File page appears.

Step 3

Click Browse to select the file to be uploaded. A Choose File window opens and displays the files on your local system.

Step 4

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.

Step 5

Click Upload. The file is uploaded to the Emergency Responder server. You can then import the data from the file.

Find and List Synthetic Phones

The Find and List Synthetic Phones page appears when you choose ERL Membership > Synthetic Phones.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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.

The following table describes the Find and List Synthetic Phones page.

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 pull-down 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 are displayed from the pull-down 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 Add New Synthetic Phone 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, choose 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.

Note

You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Add New Synthetic Phone page to manually define a synthetic phone ERL. You must configure synthetic phones in the subnet for testing ERL configurations.

For synthetic phones, Emergency Responder cannot automatically locate and update ERL information. You should regularly review synthetic phone configurations to ensure that they are correct.

The following table describes the Add New Synthetic Phone page.

Add New Synthetic Phone Page

Field

Description

Notes

MAC Address

The MAC address of the synthetic phone, or a range of MAC addresses.

The synthetic MAC address must be within the 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.

Insert button

Click Insert to add the synthetic phone to the list of phones.

The Insert button only appears when you are adding a phone.

New button

Click New to add another phone.

The New button only appears when you are viewing an existing phone.

Update button

Click Update when viewing an existing phone to save changes you make to the phone.

The Update button only appears when you are viewing an existing phone.

Cancel Changes button

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related References

E911 and Cisco Emergency Responder Terminology

Related Information

Synthetic Phones

Synthetic Phones

With Emergency Responder, you can use Cisco Unified Operations Manager to monitor the health and functionality of Cisco Emergency Responder. To use Cisco Unified Operations Manager with Cisco Emergency Responder, you configure a synthetic phone in Emergency Responder and associate the synthetic phone to an ERL that is used as a test ERL. When a synthetic phone makes an emergency call, Emergency Responder uses the associated test ERL to route the call.

Note

You can only configure test ERLs for conventional ERLs. You cannot configure test ERLs for off-premise ERLs and Intrado ERLs.

For more information, see Set Up Test ERLs.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Add User

The Add User page appears when you choose 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 Modify User for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add User page to add a new user to the system.

The following table describes the Add User page.

Add User Page

Field

Description

User Name

Enter the username for the new user.

Authentication Mode

Select the authentication mode of the new user. The user can either be a Remote user or a Local user.

Password

Enter the password for the new user.

Confirm Password

Reenter the password for the new user.

Unified CM Cluster

This field is enabled only when the user is a Remote user. Select a Unified CM cluster, from the drop-down list, to authenticate the remote user.

Insert button

Inserts the new user.

Cancel Changes button

Cancels changes made to the Add User page.

Related References

Find and List Roles

Find and List User Groups

Related Information

Role-Based User Management

Role-Based User Management

Emergency Responder uses a role-based user management mechanism. The information in the following topics describe this mechanism.

Find and List Roles

The Find and List Roles page appears when you choose User Management > Role.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List Role page to find, list, modify, and delete current roles, and to add new roles.

The following table describes the Find and List Roles page.

Find and List Roles Page

Field

Description

Role Search Parameters

Find Role where Role Name is

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 pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Roles

Section of the page in which the search results are displayed. These default roles are created during installation:

- Emergency Responder System Admin

- Emergency Responder ERL Admin

- Emergency Responder Network Admin

- Emergency Responder 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:

- Role Name

- Description

- List of resources assigned to that role

Note:
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 are 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 1 for more information about the Modify Role page.

Edit icon

Click the Edit icon to display the Modify Role page. See Table 1 for information about the Modify Role page.

Delete icon

Click the Delete icon to delete the role from the system.

Note:
You cannot delete any of the default roles.

Add New Role button

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 1 for information about the Add Role page.

Find and List User Groups

The Find and List User Groups page appears when you choose User Management > User Group.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List User Groups page to find, list, modify, and delete current user groups, and to add new user groups.

The following table describes the Find and List User Groups page.

Find and List User Groups Page

Field

Description

User Group Search Parameters

Find User Group where User Group Name

Enter search criteria to select the user group you want to find.

To find all user groups, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

User Groups

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 Modify User Group for information.

Edit icon

Click the Edit icon to display the Modify User Group page. See Modify User Group for information.

Delete icon

Click the Delete icon to delete the user group from the system.

Note:
You cannot delete default user groups that were created during installation.

Add New User Group button

Click the Add New User Group button to display the Add User Group page. See Table 1 for information about the Add User Group page.

Add Role

The Add Role page appears when you choose 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 Modify Role for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add Role page to add a new role to the system.

The following table describes the Add Role page.

Add Role Page

Field

Description

Add Role

Role Name

The name of the new role you are adding.

Description

A description of the new role.

Resource Permissions

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.

Select All button

Click Select All to select all the listed resources.

Clear All button

Click Clear All to deselect all currently selected resources.

Insert button

Click Insert to add the new role.

Cancel Changes button

Click Cancel Changes to cancel the Add Role operation.

Related References

Find and List Users

Find and List User Groups

Related Information

Role-Based User Management

Role-Based User Management

Emergency Responder uses a role-based user management mechanism. The information in the following topics describe this mechanism.

Find and List Users

The Find and List Users page appears when you choose User Management > User.

Authorization Requirements

You must have system administrator authority to access this page.

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.

The following table describes the Find and List Users page.

Find and List Users Page

Field

Description

User Search Parameters

Find User where User Name

Enter search criteria to select the users that you want to find.

To find all users, click Find without entering any criteria.

To narrow your search:

- Select All to indicate that only users that match the selected criteria be displayed (an AND search).

- Select Any to indicate that users that match any search criteria be selected (an OR search).

- From the pull down menu, select the field that you want to search, select its corresponding relationship and select how many results per page are displayed. The search fields and the corresponding relationships are:

- Authentication Mode—Both, Remote or Local

- User Name— Ends with, Starts with, contains or Exactly.

- Unified CM Cluster—Ends with, Starts with, contains or Exactly.

- 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.

User

Users list

This section of the page displays the search results. If there are no usernames are displayed after completion of the search, then no users have been configured yet.

Username

Displays the users name based on the selection criteria.

Authentication Mode

Displays the authentication mode of the user. The authentication mode can be either Remote or Local.

Unified CM Cluster

This value is displayed only when the user is authenticated remotely, with the Unified CM server.

Edit icon

Click the user name or the Edit icon to display the Modify User page, which allows you to change the user authentication mode, password and Unified CM cluster. The Modify User page also displays which groups and roles have been assigned to the user.

Delete icon

Click the Delete icon to delete the user from the system.

Note:
You cannot delete the Administrator.

Add New User button

Click the Add New User button to open the Add User page. See Table 1 for a description of the Add User page.

Delete Users button

Click the Delete Users button to delete users in bulk. Select multiple users, both remote and local, by checking the check box and then clicking the Delete Users button.

Change to Remote Users button

Click the Change to Remote Users button to change local users to remotely authenticated users in bulk.

Find and List User Groups

The Find and List User Groups page appears when you choose User Management > User Group.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List User Groups page to find, list, modify, and delete current user groups, and to add new user groups.

The following table describes the Find and List User Groups page.

Find and List User Groups Page

Field

Description

User Group Search Parameters

Find User Group where User Group Name

Enter search criteria to select the user group you want to find.

To find all user groups, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

User Groups

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 Modify User Group for information.

Edit icon

Click the Edit icon to display the Modify User Group page. See Modify User Group for information.

Delete icon

Click the Delete icon to delete the user group from the system.

Note:
You cannot delete default user groups that were created during installation.

Add New User Group button

Click the Add New User Group button to display the Add User Group page. See Table 1 for information about the Add User Group page.

Add User Group

The Add User Group page appears when you choose 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 Modify User Group for more information.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Add User Group page to add a new user group to the system.

The following table describes the Add User Group page.

Add User Group Page

Field

Description

Add User Group

User Group Name

The name of the new user group you are adding.

Description

A description of the new user group.

Add Users to the Group

This section of the page has a text box that displays the names of the users you add to the user group.

Add Users button

Allows you to add users to the new group. When you click Add Users, the Add Users page appears. See Add User for more information.

Remove Users button

Allows you to remove users from the group. To do so, highlight the username in the text box and click Remove Users.

Assign Roles to Group

This section of the page has a text box that displays the roles you assign to the new user group.

Add Roles button

Allows you to assign roles to the new group. When you click Add Roles, the Add Roles page appears. See Add Role for more information.

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.

Insert button

Click Insert to add the new role.

Related References

Find and List Users

Find and List Roles

Related Information

Role-Based User Management

Role-Based User Management

Emergency Responder uses a role-based user management mechanism. The information in the following topics describe this mechanism.

Find and List Users

The Find and List Users page appears when you choose User Management > User.

Authorization Requirements

You must have system administrator authority to access this page.

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.

The following table describes the Find and List Users page.

Find and List Users Page

Field

Description

User Search Parameters

Find User where User Name

Enter search criteria to select the users that you want to find.

To find all users, click Find without entering any criteria.

To narrow your search:

- Select All to indicate that only users that match the selected criteria be displayed (an AND search).

- Select Any to indicate that users that match any search criteria be selected (an OR search).

- From the pull down menu, select the field that you want to search, select its corresponding relationship and select how many results per page are displayed. The search fields and the corresponding relationships are:

- Authentication Mode—Both, Remote or Local

- User Name— Ends with, Starts with, contains or Exactly.

- Unified CM Cluster—Ends with, Starts with, contains or Exactly.

- 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.

User

Users list

This section of the page displays the search results. If there are no usernames are displayed after completion of the search, then no users have been configured yet.

Username

Displays the users name based on the selection criteria.

Authentication Mode

Displays the authentication mode of the user. The authentication mode can be either Remote or Local.

Unified CM Cluster

This value is displayed only when the user is authenticated remotely, with the Unified CM server.

Edit icon

Click the user name or the Edit icon to display the Modify User page, which allows you to change the user authentication mode, password and Unified CM cluster. The Modify User page also displays which groups and roles have been assigned to the user.

Delete icon

Click the Delete icon to delete the user from the system.

Note:
You cannot delete the Administrator.

Add New User button

Click the Add New User button to open the Add User page. See Table 1 for a description of the Add User page.

Delete Users button

Click the Delete Users button to delete users in bulk. Select multiple users, both remote and local, by checking the check box and then clicking the Delete Users button.

Change to Remote Users button

Click the Change to Remote Users button to change local users to remotely authenticated users in bulk.

Find and List Roles

The Find and List Roles page appears when you choose User Management > Role.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Find and List Role page to find, list, modify, and delete current roles, and to add new roles.

The following table describes the Find and List Roles page.

Find and List Roles Page

Field

Description

Role Search Parameters

Find Role where Role Name is

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 pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Roles

Section of the page in which the search results are displayed. These default roles are created during installation:

- Emergency Responder System Admin

- Emergency Responder ERL Admin

- Emergency Responder Network Admin

- Emergency Responder 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:

- Role Name

- Description

- List of resources assigned to that role

Note:
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 are 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 1 for more information about the Modify Role page.

Edit icon

Click the Edit icon to display the Modify Role page. See Table 1 for information about the Modify Role page.

Delete icon

Click the Delete icon to delete the role from the system.

Note:
You cannot delete any of the default roles.

Add New Role button

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 1 for information about the Add Role page.

Call History

The Call History page appears when you choose Reports > Call History.

Authorization Requirements

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. Emergency Responder maintains the most recent 10,000 call history records. There is no restriction on when these calls were placed.

The following table describes the Call History page.

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 pull down menu, select the field that you want to search on (ERL Name, Caller 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.

Call History Matching Records

A list of emergency calls that match your search criteria is displayed with the following information:

- ERL Name—Click the name to view details about the ERL and its ALI information. See Conventional ERL for descriptions of the configuration fields.

- Caller Extension—The extension used to place the emergency call.

- Time—The time the call was made.

- Date—The date the call was made.

- Route Pattern-ELIN No.—The route pattern and ELIN combination used for the call. See Conventional ERL for more detailed information about these fields.

- Location—The location of the phone based on whether the phone was configured manually, or whether it was configured based on the switch port or IP subnet.

- Call Acknowledged—The acknowledged status of a call on the Web Alert page.

- Acknowledged By—The ID of the user who acknowledged the call.

- Time Acknowledged—The time that the call was acknowledged.

- Date Acknowledged—The date that the call was acknowledged.

- Comments—Any 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

Click Download to save the call history data to a spreadsheet that you can view or download to your local system.

Update

Click Update to include your comments in the call history for the call.

Note:
Only viewable from the Call Details page.

Cancel Changes

Click Cancel Changes to remove unsaved comments. You can then reenter comments.

Note:
Only viewable from the Call Details page.

Close

Click Close to close the Call Details page.

Note:
Only viewable from the Call Details page.

Related Tasks

View Emergency Call History

Related References

E911 and Cisco Emergency Responder Terminology

View Emergency Call History

You can view the history of emergency calls made in your network that are handled by Emergency Responder. Emergency Responder sends emergency call notifications to the onsite alert personnel that you identify in your ERLs, and these people respond to the notifications. From the administrator interface, you can view the same call history that your onsite alert personnel can view, and see 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 about the 10,000 most recent calls. You can find records of older calls in Emergency Responder raw call log files. See Call History Logs for more information.

Procedure

Step 1

Select Reports > Call History.
Emergency Responder opens the Call History page.

Step 2

Click Find.
All call summary information appears.

Step 3

Enter the search criteria that 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. 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).

Step 4

From the list of calls that Emergency Responder shows you in response to your search criteria, you can:

- View the call characteristics.

- Click 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. Emergency Responder opens a separate window where you make your editorial changes.

Tip:
If a large number of calls match your search criteria, Emergency Responder uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

ERL Audit Trail

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

- Choose Reports > ERL Audit Trail.

- Click view in the Audit Trail column for an ERL displayed on the ERL Configuration page (opened by choosing ERL > Conventional ERL.)

Authorization Requirements

You must have system administrator, ERL administrator, or network administrator authority to access this page.

Description

Use the ERL Audit Trail page to view the change history for ERLs.

The following table describes the ERL Audit Trail page.

ERL Audit Trail Page

Field

Description

ERL Audit Trail

Search criteria

Enter search criteria to select the audit details that 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 pull-down menu, select the field that 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 pull-down 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:

- ERL Name—The name of the ERL that was changed.

- Modified By—The login ID of the user who changed the ERL.

- Modified Time—The date and time the ERL was changed.

- Modification Details—A 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.

Note:
If there are a large number of records match your search, Emergency Responder 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 Tasks

View Audit Trail for ERL

Related References

E911 and Cisco Emergency Responder Terminology

View Audit Trail for 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.

Procedure

Step 1

Select Reports > ERL Audit Trail.
Emergency Responder opens the ERL Audit Trail page.

Step 2

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:

1. Select the field that 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.

2. 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).

3. Click Find when you have entered all of the search criteria.
Emergency Responder lists the matching audit records. If there are a lot of matches, Emergency Responder uses several pages to display them. Use the links at the bottom of the list to change pages.

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.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

Export PS-ALI Records

The Export PS-ALI Records page appears when you choose Tools > Export PS-ALI Records.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 do not submit an export file, subsequent export files might not have correct command information for the database update, and you must 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, Emergency Responder 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 and Insert sequence is only generated the first time you export ALI after changing the code. You must ensure that you submit this export file to the service provider.

You can also use export files to back up your ERL configuration.

The following table describes the Export RS-ALI Records page.

Export PS-ALI Records Page

Field

Description

Export PS-ALI Records

Select NENA Format

The file format to be used in the export file, NENA formats 3.0, 2.1, or 2.0.

File to Export

The name of the file you want to create. Do not include a file extension.

Company Name (NENA Header field)

The name of your company. You cannot have spaces in the name.

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 file; if you are redoing an export, you must manually edit the export file to change the record status fields.

Note:
The data complies with NENA requirements.

End of Line Format

Allows you to select the end-of-line format for the PS-ALI records that is exported for download. You can select from the following two formats:

- Windows style (\r\n)

- Unix/Linux style (\n)

Export button

Click Export to create the export file.

Download File

Click Download File to download an exported PS-ALI file.

Cancel button

Click Cancel to cancel the export operation.

Related Tasks

Export ERL Information

Export ALI Information for Submission to Your Service Provider

Related References

ALI Information

E911 and Cisco Emergency Responder Terminology

Related Information

ALI Submission and Service Provider Requirements

ERLs

ERL Management

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

PS-ALI Converter

The PS-ALI Converter page appears when you choose Tools > PS-ALI Converter.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the PS-ALI Converter tool to generate an ERL file that can be accepted by the Emergency Responder 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 Emergency Responder.

Note

If you change the customer code in your ALI record, Emergency Responder 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 and 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.

PS-ALI Converter Page

Field

Description

Export PS-ALI Records

Select PS-ALI file (NENA 2.0 format)

The name of the PS-ALI file to be converted. The file must be in the default format, NENA format 2.0.

Output File (in csv format) Name

The name of the csv file that you want to create.

Convert button

Click Convert to create the csv file.

Cancel button

Click Cancel to stop the converting process. and close the window.

Related Tasks

Export ERL Information

Export ALI Information for Submission to Your Service Provider

Related References

ALI Information

E911 and Cisco Emergency Responder Terminology

Related Information

ALI Submission and Service Provider Requirements

ERLs

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

ALI Submission and Service Provider Requirements

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.

Emergency Responder 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.

Emergency Responder does not include automated capability for submitting ALIs.

Tip

Before deploying Emergency Responder throughout your network, test the ALI submission process with your service provider. With your service provider's help, test that the PSAP can successfully call back into your network using the ALI data. Each service provider and ALI database provider has slightly different rules concerning ALI information. Emergency Responder allows you to create ALI data according to the general NENA standards, but your service provider or database provider has stricter rules.

Export 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. You can export conventional, off-premise, or Intrado ERLs. Click the Export link in the upper-right corner of the Find Conventional ERL Data page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

Note

Do not submit ERL export files to your service provider; they are not exported in a format that your service provider can use.

For information about exporting ALI information, see Export ALI Information for Submission to Your Service Provider.

For information about reformating ALI data to be accepted by the ERL, see Export ALI Information for Submission to Your Service Provider.

Before You Begin
You must log into Emergency Responder with system administrator or ERL administrator authority.

Procedure

Step 1

In the Find ERL page (Find Conventional ERL Data page, Find Off-Premises ERLs Data page, or the Find Intrado ERLs Data page), click Export.
Emergency Responder opens the Export ER Data window.

Step 2

Select the Export Format (csv or xml) from the pull-down menu.

Step 3

Enter the name of the file to be exported in the Enter Export File Name field.

Step 4

Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5

Select the exported file from the pull-down menu and click Download to download it to your local machine.

Step 6

Click Close to close the Export ERL Data window.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

E911 and Cisco Emergency Responder Terminology

The following list defines some of the key terminology used in this document.

ALI

Automatic location information. Information that connects an ELIN to a location, is used to route emergency calls from that ELIN to the correct local PSAP, and is provided to the PSAP to help the PSAP locate the emergency caller. In Emergency Responder, you fill in ALI data for each ERL and submit the ALI data to your service provider for inclusion in the ALI database.
ANI

Automatic number identification. ANI is another name for ELIN. This document uses ELIN instead of ANI.
CAMA

Centralized automated message accounting. An analog phone trunk that connects directly to an E911 selective router, bypassing the Public Switched Telephone Network (PSTN).
DID

Direct inward dial. A telephone number obtained from your service provider that can be used to dial into your telephone network. DID numbers are used for ELIN.
ELIN

Emergency location identification number. A phone number that routes the emergency call to the local PSAP, and which the PSAP can use to call back the emergency caller. The PSAP might need to call the number if the emergency call is cut off, or if the PSAP needs additional information after normally ending the emergency call. See ALI.
emergency call

A call made to the local emergency number, such as 911. Emergency Responder routes the call to the service provider's network where the call is routed to the local PSAP.
emergency caller

The person who places the emergency call. The caller might require help for a personal emergency, or might be reporting a more general emergency (fire, theft, accident, and so forth).
ERL

Emergency response location. The area from which an emergency call is placed. The ERL is not necessarily the location of the emergency. If an emergency caller is reporting a general emergency, the actual emergency might be in a different area. In Emergency Responder, you assign switch ports and phones to ERLs, and ERL definitions include ALI data.
ESN

Emergency service number.
ESZ

Emergency service zone. The area covered by a given PSAP. This area usually includes several police and fire departments. For example, a city and its suburbs might be serviced by one PSAP.

Each ESZ is assigned a unique ESN to identify it.

MSAG

Master street address guide. A database of ALIs that enables proper routing of emergency calls to the correct PSAP. In Emergency Responder, you export your ALI definitions and transmit them to your service provider, who ensures that the MSAG is updated. You must negotiate this service with your service provider — it is not a service provided directly through Emergency Responder.
NENA

National Emergency Number Association. The organization that recommends data and file formats for ALI definitions and other emergency call requirements in the United States. Emergency Responder uses the NENA formats for ALI data export files. Your service provider has additional restrictions on data format, so ensure that your ALI entries comply with your service provider's rules.
PSAP

Public safety answering point. The PSAP is the organization that receives emergency calls (for example, the 911 operator) and is staffed by people trained in handling emergency calls. The PSAP talks to the emergency caller and notifies the appropriate public service organizations (such as police, fire, or ambulance) of the emergency and its location.

ERL Debug Tool

The ERL Debug Tool page appears when you choose Tools > ERL Debug Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

The ERL Debug Tool takes the phone extension as input and displays the ERLs currently being used for routing emergency calls for the phones.

Use this diagnostic tool to verify the Emergency Responder configuration during the ERL creation and the ERL assignment phase and to troubleshoot calls directed to incorrect ERLs.

The following table describes the ERL Debug Tool page.

ERL Debug Tool Page

Field

Description

ERL Debug Tool

Find Phones where extension

Enter search criteria to select the extensions that you want to find.

To find all extensions, click Find without entering any criteria.

To narrow your search, use the pull-down 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 are displayed from the pull-down menu. When you have specified your search criteria, click Find.

Matching records

Section of the page that displays the ERLs currently being used for routing emergency calls for the phones. 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.

Export button

Click Export to create the export file.

Related Tasks

Use Emergency Responder Admin Utility Tool

Related Information

ERLs

ERL Management

Use Emergency Responder Admin Utility Tool

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Using the menu bar, choose a task to perform:

1. To change the Publisher that the Subscriber server points to, select Update > Publisher.

2. To update the Unified CM version, select Update > CCM Version.

3. To update the cluster settings on both the Publisher and Subscriber servers, select Cluster > DBHost.
Note:
This action updates the Emergency Responder cluster DB details for this server group only. Other servers in this Emergency Responder cluster will NOT be updated automatically.

Step 3

To save the changes that you have made, restart both the Publisher and the Subscriber servers.

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 considered as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

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 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, or 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 multistory.

- 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 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.

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).

2. Talk to your service provider to learn about their rules or recommendations.

3. 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 because the ERL name is one of the major data points they 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 including the complete street address of the building. Although security can also view the ALI from the Emergency Responder 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 Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition you assign personnel to each ERL.

5. Use Emergency Responder to define the ERLs and their ALI. See ERL Creation for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See Switch Port Configuration for more information. Someone with network administrator authority must first add the switches to the Emergency Responder configuration before you can complete this task.

7. Define any phones that are not directly supported by Emergency Responder. See Manually Define Phones, for more information.

8. 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 Export ERL Information and the Export ALI Information for Submission to Your Service Provider 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.

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.

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 reexport ALI data and submit it to your service provider.

ALI Formatting Tool

The ALI Formatting Tool page appears when you choose Tools > ALI Formatting Tool.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

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 Emergency Responder 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

The following table describes the ALI Formatting Tool page.

ALI Formatting Tool Page

Field

Description

Select a Service Provider

Use the pull-down menu to select a service provider

Select an Input File for the ALI Formatting Tool from the List Below

Use the pull-down menu to select an input file

Submit button

Click the Submit button to display the Search for ELINs page, which is described in Table 2.

The following table describes the Search for ELINs page.

Search for ELINs Page

Field

Description

Use Search to Filter-out ELINs on Area, City and Local Code(last 4-digits).

Allows you to search ELINs by Local Code, Area Code, or City Code.

Add (+) button

Adds more search parameters

Remove (-) button

Removes search parameters

The following table describes the Bulk Update page.

Bulk Update Page

Field

Description

Remove Changes/Generate File button

Shows all the ELINs that have been changed.

Search for ELIN

Displays the ELIN search page.

The following table describes the Review Changes/Generate File page.

Review Changes/Generate File Page

Field

Description

Add More ELIN

Displays the remaining ELINs that have not been changed.

Remove ELIN

Removes the selected ELINs from the list

Search for ELIN

Displays the ELIN search screen

Generate File button

Generates the formatted file.

The following table describes the Download Formatted File page.

Download Formatted File Page

Field

Description

Download Formatted File button

Displays a Download File dialog box so that the formatted file can be downloaded to the local system.

Related Tasks

Export ALI Information for Submission to Your Service Provider

Related References

ALI Information

Related Information

ALI Formatting Tool for Bell Canada

ALI Formatting Tool for SBC Ameritech

ALI Formatting Tool for SBC-PacBell

ALI Formatting Tool for SBC-Southwestern Bell

ALI Formatting Tool for Qwest

ALI Formatting Tool for Verizon

ALI Information

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. If the ERL name is First Floor, the page that appears is titled ALI Information for First Floor.

The ALI Information (for ERL Name) page appears when you do one of these:

- Click Add/Edit ALI in the ERL Address section on the Add New ERL page.

Note

The Add New ERL page appears when you choose Add New ERL on the Find ERL Data page (opened when you choose ERL > Conventional ERL).

- 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 choose ERL > Details).

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Enter ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). Send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs are routed to the local PSAP and public safety answering points (PSAPs) can locate an emergency caller.

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 are based on the National Emergency Number Association (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.

Enter ALI Information Page

Field

Description

Notes

Find all prevalidated fields from validation file by selecting a tag

Select a Tag

Select the tag whose associated ALI data you want to load into the window. You can then edit the information for this specific ALI.

You can simplify the entry of ALI data by setting up tags in a file called validate.txt. 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 is 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 select a tag and the ALI data is loaded with the data you defined for the tag.

Field

Description

Value Type

(A = Alphabets, N = Numeric, S = Special Characters [# @ & * ( ) - _ + , . : ; " ' /] )

ALI Data

House Number

The number from the postal street address for the building. Example: 170 in 170 West Tasman Dr.

AN, dash "-", and @ sign "@"

The number can be up to 10 characters, but your service provider might only support 8 character numbers.

House Number Suffix

The number extension (such as /2) for the house number, if any.

ANS

Street Name

The street name from the postal address for the building.

ANS

You are limited to 60 characters.

Prefix Directional

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.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Street Suffix

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.

A

You can also type in the suffix. You are limited to 4 characters.

Post Directional

A trailing directional indicator if the street name contains one, for example, N for North.

Can be one of these directions:

- N

- S

- E

- W

- NE

- NW

- SE

- SW

Community Name

The community name for the address, for example, a city, town, or district name.

ANS

You are limited to 32 characters.

State

The 2-digit state abbreviation.

A

You are limited to 2 characters.

Main NPA

The 3-digit area code of the main number associated with the ERL.

N

Main Telephone No.

The main phone number associated with the ERL. This might be the number of the security office for the ERL.

N

Class of Service

Select the class of service for the ERL.

If you do not know your class of service, ask your service provider.

Type of Service

Select the type of service for the ERL.

If you do not know your class of service, ask your service provider.

Exchange

The Local Exchange Carrier (LEC) exchange identifier for the serving telephone office for the phone.

ANS

You are limited to 4 characters. Ask your service provider for this identifier

Customer Name

The subscriber name associated with the ERL, and typically your company name.

ANS

You are limited to 32 characters.

Order Number

The service order number of the activity of establishing or updating this record.

ANS

You are limited to 10 characters. Work with your service provider to determine a valid order number, if one is needed.

Extract Date

The date on which the record was created.

Date [mmddyy]

County ID

The county identification code for the zone. In the USA, use the FIPS code assigned to the county by the U.S. Census Bureau.

AN

You are limited to 4 characters.

Zip Code

The postal zip code for the address.

AN, hyphen "-"

Indicates a U.S. zip code on a U.S. service order record or a Canadian postal code on a Canadian service order record. U.S. Format: NNNNN or NNNNN-NNNN; Canadian Format: ANANAN or ANA[space] NAN

Zip Code Extension

The postal zip code "plus four" number.

AN, hyphen "-"

You are limited to 4 digits.

Customer Code

Your customer code. Ask your service provider if you do not know your code.

ANS

You are limited to 3 characters.

If you change this field, Emergency Responder 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 and Insert sequence is only generated the next time you export ALI: you must ensure that you submit this export file to the service provider.

Comments

Optional comments. These commentsmight be displayed at the PSAP if an emergency call is made from this ERL.

You are limited to 30 characters.

Longitude

The longitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Latitude

The latitude of the ERL.

N, dot ".", plus "+", minus "-"

You are limited to 9 digits.

Elevation

The elevation of the ERL.

AN dot ".", plus "+",minus "-"

You are limited to 5 digits.

TAR Code

The taxing area rate code.

ANS

You are limited to 6 characters.

Location

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.

ANS

You are limited to 60 characters.

Reserved

Information your service provider might require to create a valid ALI file.

AN

Ask your service provider if you must

enter 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 Emergency Responder 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.

Export 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 conventional 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 ALI Formatting Tool chapter for information about sending ALI details to your service provider.

Before You Begin
You must log into Emergency Responder 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.

Procedure

Step 1

Select Tools > Export PS-ALI Records.
Emergency Responder opens the Export PS-ALI Records page.

Step 2

At the Select the NENA Format field, choose the format required by your service provider from the drop-down list.

Step 3

At the File to Export field, enter the name of the file to export.

Step 4

At the Company Name field, enter your company name.
Note:   Emergency Responder 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 file. If you are redoing an export, you have to manually edit the export file to change the record status fields.

Step 5

Click Export.
Emergency Responder creates the export file and tells you how many records were exported.

Step 6

Click Download to download the file to your local machine.

Step 7

Click Close to close the Export ALI Records window.

Step 8

Use your service provider's method of transmitting the file to the service provider.

ALI Formatting Tool for Bell Canada

The following topics describe how to use AFT for Bell Canada.

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.

Cisco Emergency Responder (Emergency Responder) 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 Emergency Responder to correct errors reported by Ameritech, you may need to use AFT to change the Function Code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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.

ALI Formatting Tool for SBC-PacBell

The following sections describe how to use the AFT for SBC-PacBell.

ALI Formatting Tool for SBC-Southwestern Bell

The following sections describe how to use the AFT for SBC-Southwestern Bell.

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 (Emergency Responder) 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 Emergency Responder to correct errors reported by Qwest, you may need to use AFT to change the function code for ELIN records.

For example, Emergency Responder 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 Emergency Responder.

When Emergency Responder 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

ALI Formatting Tool for Verizon

The following sections describe how to use the AFT for Verizon.

File Management Utility

The File Management Utility page appears when you choose Tools > File Management Utility.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the File Management Utility page to search for, download, or delete exported files.

The following table describes the File Management Utility page.

File Management Utility Page

Field

Description

Search Parameters

Please Select:

From the pull-down menu, select the type of file that you want to search for.

Search button

Click Search to perform the search.

Exported Files

Area of the page that displays the search results. Displays the File Name, Last Modified data, and File Size for each file found.

Download button

Downloads the selected file.

Note:
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.

Delete button

Deletes the selected file.

Note:
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.

Related References

Upload and Download Utilities

Upload and Download Utilities

Emergency Responder includes download and upload utilities that allow you to transfer bulk data in the form of csv files from a Emergency Responder server to a local system (download) and from a local system to a Emergency Responder 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 Emergency Responder server, and import the data in the csv file into the Emergency Responder database.

The following table lists the Emergency Responder 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.

Administrative Web Pages Containing the Upload and Download Utilities

Page Name

Navigation Path

Find Conventional ERL Data

ERL > Conventional ERL

Find Off-Premises ERL Data

ERL >Off-premises ERL>Off-premises ERL(Search and List)

Find Intrado ERLs Data

ERL > Intrado ERL>Intrado ERL (Search and List)

LAN Switch Details

Phone Tracking > LAN Switch Details

Switch Port Details

ERL Membership > Switch Ports

Find and List IP subnets

ERL Membership > IP subnets

Find and List Manually Configured Phones

ERL Membership > Manually Configured Phones

Purge Call History

The Purge Utility for Call History page appears when you choose Tools > Purge Utility.

Authorization Requirements

You must have system administrator or ERL administrator authority to access this page.

Description

Use the Purge Call History Utility to delete call history records that are older than an age that you specify. You can use this utility to purge records immediately or schedule daily purging of call history records. Emergency Responder logs the results of the purge in the Emergency Responder Administration logs.

The following table describes the purge utility page.

Purge Utility for Call History

Field

Description

Status

Displays status messages

Purge Now

Purge Data older than

Specify the age of record that you want to delete.

Schedule Purge

Daily Purge at

Specify a time (GMT) during the day at which old records are deleted.

Purge Data older than

Specify the age of record that you want to delete.

Update

Click Update to save and activate your changes.

Cancel

Click Cancel Changes to change the fields on this page back to the last saved settings.

Related Tasks

View Emergency Call History

Related Information

Call History Logs

View Emergency Call History

You can view the history of emergency calls made in your network that are handled by Emergency Responder. Emergency Responder sends emergency call notifications to the onsite alert personnel that you identify in your ERLs, and these people respond to the notifications. From the administrator interface, you can view the same call history that your onsite alert personnel can view, and see 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 about the 10,000 most recent calls. You can find records of older calls in Emergency Responder raw call log files. See Call History Logs for more information.

Procedure

Step 1

Select Reports > Call History.
Emergency Responder opens the Call History page.

Step 2

Click Find.
All call summary information appears.

Step 3

Enter the search criteria that 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. 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).

Step 4

From the list of calls that Emergency Responder shows you in response to your search criteria, you can:

- View the call characteristics.

- Click 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. Emergency Responder opens a separate window where you make your editorial changes.

Tip:
If a large number of calls match your search criteria, Emergency Responder uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.

Call History Logs

Emergency Responder 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.

Emergency Responder maintains in its database a history of the emergency calls that have been placed. When the primary Emergency Responder server (Publisher) is not active, emergency calls are handled by the backup Emergency Responder 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 Emergency Responder servers.

To download these records, click the Download button at the top of the table displaying the call history. These records are downloadable in Excel (.xls) format.

Control Center

The Control Center page appears when you choose Tools > Control Center.

Authorization Requirements

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.

The following table describes the Control Center page.

Control Center Page

Field

Description

Start button

Starts the selected services.

Stop button

Stops the selected services.

Restart button

Restarts the selected services.

Refresh button

Refreshes the list of currently running services on the selected server.

Service Name

Names of the currently running services on the selected server. To select a service, click the radio button next to the service name.

Status

Current status of the selected service.

Related Tasks

Manage Emergency Responder Server

Manage Emergency Responder Server

When you install Emergency Responder, the Emergency Responder server is set up to automatically start whenever the computer is powered up or rebooted. However, you can stop and then restart an Emergency Responder server through the Emergency Responder Serviceability web interface without powering down or rebooting the computer.

Procedure

Step 1

Log in to the Emergency Responder Serviceability web interface and select Tools > Control Center. The Control Center Services page displays, showing all Emergency Responder 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.
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.

The following table explains the meaning of the icons that you see on the Control Center Services page.

Cisco Emergency Responder Control Center Icons

Icon

Meaning

The Emergency Responder server or the Emergency Responder Phone Tracking Engine is started and functioning normally.

The Emergency Responder server Emergency Responder Phone Tracking Engine was stopped by the administrator.

Event Viewer

The Event Viewer page appears when you choose Tools > Event Viewer.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Event Viewer page to view Emergency Responder events for the previous six months.

The following table describes the Event Viewer page.

Event Viewer Page

Field

Description

Type pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down 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 pull-down menu to the right of the Type pull-down menu.

Module pulldown menu

Note:
This pull-down menu contains two options: Type and Module. When you choose either Type or Module, the pull-down menu to the right changes to display the available Type or Module options.

Allows you to select the Emergency Responder module for which you want to view events. When you select Module from the pull-down 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

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.

Type column

Displays the type of event. The Type column displays one of the following:

- INFO

- WARN

- ERROR

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.

Module column

Displays the Emergency Responder 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 Tasks

Use Event Viewer

Use Event Viewer

The Event Viewer allows you to view events for the prior six months.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select Tools > Event Viewer. The Event Viewer page appears.

Step 2

Click Find without entering any search criteria to find all events that occurred over the prior six months
To find events that match specific criteria, enter search criteria:

- 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 pull-down menu to the right.

If you select Module, you can then select the module on which to search from the pull-down menu to the right.

Note:
For a list of available Types and Modules, see Event Viewer.

When you have entered your search criteria, click Find.

Step 3

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.

SNMP Community String Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP Community String Configuration page to view, add, update, and delete community strings. Community strings control access to the Emergency Responder by clients using SNMP V1 and V2c.

The following table describes the SNMP Community String Configuration page.

SNMP Community String Configuration Page

Field

Description

Community String Name column

Lists all community strings defined for the selected server. Click 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 this button, Emergency Responder opens a second SNMP Community String Configuration page.

Note:
Clicking the Add New button brings up the same screen displayed when you click the Add New icon.

Delete Selected button or icon

Deletes the selected community strings. To delete a community string, you must first select it from the list of community strings. Click the box to the left of the community string name to select it. To delete all community strings from the selected server, click 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 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.

The following table describes the second SNMP Community String Configuration page.

SNMP Community String Configuration Page—2

Field

Description

Community String Name

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.

Host IP Address Information

Accept SNMP Packets from any host

Click this radio button to allow any host to access the Emergency Responder using SNMP.

Accept SNMP Packets only from these hosts

Click this radio button to specify which hosts can access the Emergency Responder 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.

Access Privileges pulldown menu

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:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert 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.

Clear button or icon

Clears the community string information displayed on the current page.

Related Tasks

Set Up SNMP Community String

Set Up SNMP Community String

By configuring SNMP, you can control SNMP access to the Emergency Responder 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

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V1/V2C Configuration > Community String. The SNMP Community String Configuration page appears.

Step 2

Enter the name of the community string in the Community String Name text box.

Step 3

Click Accept SNMP Packets only from these hosts to specify specific hosts whose SNMP packets will be accepted, 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.

Step 4

Select the host IP address and click Remove to remove an existing host, .

Step 5

Select the access privilege for the host from the Access Privileges pull-down menu then click Insert.

SNMP User Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the SNMP User Configuration page.

SNMP User Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to view, add, update, or delete users. After you select a server, Emergency Responder displays the currently configured information in the following format:

- User Name

- Authentication Required

- Authentication Protocol

- Privacy Required

- Privacy Protocol

- Access Privileges

Click user name to display the Add and Update SNMP User Configuration page, from which you can update the information for that user.

Add New User button or icon

Add a new user for the selected server. When you click this icon, Emergency Responder opens the 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 the box to the left of the User Name column heading.

Use the second SNMP User Configuration page to configure new SNMP V3 users.

The following table describes the Add/Update SNMP User Configuration page.

SNMP User Configuration Page—2

Field

Description

User Name field

Enter the name of the new SNMP V3 user.

Note:
If you reached this page by clicking an existing user name on the SNMP User Configuration page, the fields on this page display the currently configured information.

Authentication Information

Use this section to configure the following information:

- If authentication is required for this user, check the check box that is 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 the radio button for either MD5 or SHA.

Privacy Information

Use this section to configure the following information:

- If privacy is required for this user, check the check box that is labelled 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 labelled DES.

Host IP Addresses Information

Use the radio buttons in this section of the page to do the following:

- Specify which hosts can access the Emergency Responder using SNMP. You can insert IP addresses for new hosts that you want to have SNMP access to the Emergency Responder, or you can remove IP addresses of hosts that you no longer want to have SNMP access to Emergency Responder.

- Allow any host to access Emergency Responder using SNMP.

Access Privileges pulldown menu

When adding a new user, this pull-down menu allows you to specify the access privilege for the new user. When updating a user's information, this field displays the current access privilege level. The available access privilege levels are as follows:

- ReadOnly

- ReadWrite

- ReadWriteNotify

- NotifyOnly

- None

Insert button or icon

Insert the new user information for the selected server.

Clear button or icon

Clears the user information displayed on the current page.

Related Tasks

Set Up SNMP Users

Set Up SNMP Users

SNMP V3 provides additional security features that include message integrity, authentication, and encryption. In addition, SNMP V3 controls user access to specific areas of the MIB tree.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V3 Configuration > User.
The SNMP User Configuration page appears.

Step 2

Click Add New to add a new SNMP User,

Step 3

Enter the name of the new user in the User Name text box.

Step 4

Check the Authentication Required check box to require authentication. Enter a password in the Password text box, reenter the password in the Reenter Password textbox, and click either MD5 or SHA to select a Protol. Click Insert to add the user.

Step 5

Check the Privacy Required check box to require information privacy. Enter a password in the Password textbox, reenter the password in the Reenter Password textbox, and click the DES check box.
Note:
A message is displayed stating 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

Repeats Step 2 through to Step 4 to add additional users.

SNMP v3 Notification Destination Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the SNMP V3 Notification Destination Configuration page to identify the destination to which the Emergency Responder SNMP agent sends trap messages. The SNMP V3 Notification Destination information provides enhanced security because each notification string is associated with a specific user.

The following table describes the SNMP V3 Notification Destination Configuration page.

SNMP v3 Notification Destination Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to view, add, update, or delete SNMP notification destination information. After you select a server, Emergency Responder displays the currently configured information in the following format:

- Destination IP Address

- Port Number

- Security Model

- Security Name

- Security Level

- Notification Type

Click a Destination IP Address to update the information for the device at that address. When you click an IP address in this list, Emergency Responder 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, Emergency Responder opens the Add/Update Notification Destination page.

Add New button or icon

Add a new notification destination for the selected server. When you click this icon, Emergency Responder 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 the box to the left of the Destination IP Address column heading.

Use the second SNMP V3 Notification Destination page to add new notification destinations and to update existing notification destinations.

The following table describes the second SNMP V3 Notification Destination Configuration page.

SNMP v3 Notification Destination Configuration Page—2

Field

Description

Host IP Addresses pulldown menu

Select Add New from this pull-down menu to add a new notification destination.

Note:
If you reached this page by clicking 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

IP address of the new notification-destination host.

Port Number field

Port number on the new notification-destination host that receives the notifications from the Emergency Responder SNMP agent.

Notification Type pulldown menu

Select the SNMP message type for the new notification-destination host. The option is:

- 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 pull-down menu.

Note:
If you reached this page by clicking an existing Destination IP Address on the SNMP V3 Notification Destination Configuration page, the Remote SNMP Engine ID field displays the currently configured information.

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 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

Inserts the new notification destination for the selected server.

Clear button or icon

Clears the notification destination information displayed on the current page.

Related Tasks

Set Up SNMP v3 Notification Destination String

Set Up SNMP v3 Notification Destination String

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.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > V3 Configuration > Notification Destination.
The SNMP Notification Destination Configuration page appears.

Step 2

Click Add New to add a new SNMP Notification Destination, .

Step 3

Select Add New from the Host IP Addresses pull-down menu. Additional fields appear.

Step 4

Enter the Host IP Address and Port Number in the text boxes.

Step 5

Select Inform or Trap from the Notification Type pull-down menu. If you select Inform, you are prompted to enter a remote engine ID. If you select Trap, the Security Level pull-down menu appears. Proceed to Step 7.

Step 6

Enter the remote engine ID.

Step 7

Select the desired security level from the Security Level pull-down menu.

Step 8

Click the radio button to the left of the User Name to select a user to be associated with the notification destination.

Step 9

Repeat Step 2 through to Step 8 to add additional notification destinations, .

MIB2 System Group Configuration

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the MIB2 System Group Configuration page to specify the name and physical location of the contact person for MIB2 managed mode.

The following table describes the MIB2 System Group Configuration page.

MIB2 System Group Configuration Page

Field

Description

Server pulldown menu

Name of the server for which you want to update the MIB2 contact information. After you select a server, Emergency Responder displays fields in which you enter the name and physical location of the contact.

System Contact

The name of the MIB2 contact.

System Location

The physical location of the managed node.

Update button or icon

Saves the updated MIB2 contact information.

Clear button or icon

Clears the MIB2 contact information displayed on the current page.

Related Tasks

Set Up MIB2

Set Up MIB2

The SNMP MIB2 tool allows you to specify a contact person for a MIB2 managed node and the physical location of the managed node.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select SNMP > System Group Configuration > MIB2 System Group Configuration. The SNMP MIB2 Configuration page appears.

Step 2

In the System Contact text box, enter the name of the contact.

Step 3

In the Location text box, enter the location of the managed node.

Step 4

Click Update in the upper left corner of the page.

Step 5

Click Clear in the upper left corner of the page to modify the information, enter the new information in the System Contact and Location text boxes, and click Update.

CPU and Memory Usage

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

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the CPU and Memory Usage page to view the CPU and memory usage for the Emergency Responder system.

The following table describes the CPU and Memory Usage page.

CPU and Memory Usage Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Set the screen reset value

Specify in seconds how often this page should be refreshed.

Set CPU Logging Interval

Specify in seconds how often CPU usage is logged. The interval must be between 5 and 600 seconds.

Processors

This section displays the percentage of CPU time being used by various system components.

Download CPU Log File

Click this link to download the currently displayed CPU and memory usage information to a file. 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 2.

Processor

Name of the processor.

%User

Percentage of processor time being used by the User mode.

%System

Percentage of processor time being used by the System mode.

%Nice

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

Percentage of time in which the processor is idle.

%Irq

Percentage of processor time being used by interrupt requests (IRQ).

%Softirq

Percentage of processor time being used by soft IRQs.

Note:
A soft IRQ is an interrupt request that can be deferred.

%I/O Wait

Percentage of time that the processor is executing read or write operations.

%CPU

The processor's share of the elapsed CPU time (excluding idle time) since last update, expressed as a percentage of CPU time.

Start Log button

Starts a log file of the current CPU usage.

Note:
You can create a maximum of 25 CPU log files.

Memory

This section displays the percentage of memory allocated for different uses.

Download Memory Log File

Click this link to download to a file the currently displayed CPU and memory usage information. When you click this link, a new page opens that lists all the saved CPU log files. For more information about this screen, see Table 3.

Total (KB)

The amount of memory available, in kilobytes.

Used (KB)

Amount of memory currently being used, in kilobytes.

Free (KB)

Amount of memory that is available for use, in kilobytes.

Shared (KB)

Amount of memory used by shared processes, in kilobytes.

Buffers (KB)

Amount of memory used by buffers, in kilobytes.

Cached (KB)

Amount of memory used for caching, in kilobytes.

Total Swap (KB)

Amount of total swap space, in kilobytes

Used Swap (KB)

Amount of swap space currently being used, in kilobytes.

Free Swap (KB)

Amount of available swap space, in kilobytes

%VM Used

Amount of virtual memory being used.

Start Log button

Starts a log file of the current memory usage.

Use the CPU Log Files page to view and download the CPU log files.

The following table describes the CPU Log Files page.

CPU Log Files Page

Field

Description

Download button

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.

CPU Log Files

This section displays the details of the saved CPU log files.

File Name

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.

Last Modified

Date and time of the last modification to the CPU log file.

File Size (KB)

Size of the CPU log file, in kilobytes.

Use the Memory Log Files page to view and download the memory log files.

The following table describes the Memory Log Files page.

Memory Log Files Page

Field

Description

Download button

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.

Memory Log Files

This section displays the details of the saved Memory log files.

File Name

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.

Last Modified

Date and time of the last modification to the Memory log file.

File Size (KB)

Size of the Memory log file, in kilobytes.

Related Tasks

Use CPU and Memory Usage Tool

Use 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.

Procedure

Step 1

From the Emergency Responder 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 about the information that is displayed, see Table 1.

Step 2

Enter a value (in seconds) in the Set the screen refresh value text box to change the rate at which the page refreshes, and click Set. The minimum value you can enter is 5 seconds.

Step 3

Check the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Click the Start Log button in the Processors section of the page to create a log file of the CPU usage.
Click Start Log in the Memory section of the page to create a log file of the Memory usage.

You can create up to 25 log files.

The default interval for logging is 10 seconds. To change the logging interval, follow these steps:

1. 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.

2. 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

Click Download CPU Log File or Download Memory Log File to download the log files.
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 names that you want to download. To download all log files, check 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 creates and downloads a zipped folder called CPULogs (for Processor log files) and MemoryLogs (for Memory log files).

Step 7

To view the log files online without downloading them, click the file name. The system displays the contents of the log file.

Processes

The Processes page appears when you choose System Monitor > Processes.

Authorization Requirements

You must have serviceability authority to access this page.

Description

Use the Processes page to view and download information about 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.

The following table describes the Processes page.

Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

Download Log File

Click this link to download log files you have created. You cannot download log files until you have first created them.

Select

Check boxes that allow you to select files to be viewed or downloaded.

Process

Name of the process.

PID

ID number of the process.

%CPU

Percentage of processor time being used by the process.

Status

Task's process status: Running (R), Sleeping (S), Uninterruptible disk sleep (D), Zombie (Z), 4 Traced (T), Paging (P)

Nice (Level)

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.

Vm RSS (KB)

Resident set currently in physical memory in kilobytes, including Code, Data and Stack.

Vm Size (KB)

Size of virtual memory, in kilobytes.

Vm Data (KB)

Amount of data currently stored in virtual memory, in kilobytes.

Thread Count

Number of program threads currently running.

Data Stack (KB)

Size of the data stack, in kilobytes.

Page Fault Count

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.

The following table describes the View Selected Processes page.

View Selected Processes Page

Field

Description

Disable Auto-Refresh

Check this check box to disable auto-refresh of the information displayed on this page.

Refresh Rate

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.

View All Processes button

Returns you to the previous Processes screen, which displays all running processes.

Start Log button

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 1.

Related Tasks

Use Processes Tool

Use 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 can change how often the information refreshes, or you can disable the auto-refresh feature.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Processes.
The Processes page appears. For details about the information that is displayed, see Table 2.

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.

Step 2

Enter a value in the Set the screen refresh value text box in the upper right corner and click Set to change the rate at which the page refreshes. The minimum value you can enter is 5 seconds.

Step 3

Select the Disable Auto-Refresh check box in the upper left corner to disable the auto-refresh feature.

Step 4

Select the check box to the left of the process name and click View Selected Processes to view the details of a process. 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 stop a log, 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

Click Download Process Logs from the Process Log Files page to download the log files. To download log files click Download Log File from the Processes page.

Step 6

Select the check box to the left of the log file names to download individual files. 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 creates and downloads a zipped folder called ProcessLogs.

Step 7

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.

Disk Usage

The Disk Usage page appears when you choose System Monitor > Disk Usage.

Authorization Requirements

You must have serviceability authority to access this page.

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.

The following table describes the Disk Usage page.

Disk Usage Page

Field

Description

Disk Usage Details

Partition

Name of the partition.

Size

Size of the partition.

Percentage Used

How much disk space is the partition using, as a percentage of total allocated disk space.

Available Space

How much disk space is currently available on the partition.

Used Space

How much disk space is the partition using.

Related Tasks

Use Disk Usage Tool

Use Disk Usage Tool

The Disk Usage tool displays the percentage of available disk space used by the different partitions in the system.

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Monitor > Disk Usage.
The Disk Usage page appears. For details about the Disk Usage page, see Table 1.

Step 2

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.

System Logs Menu

The System Logs menu contains the following submenus, under which all system logs are grouped:

- System Logs > Emergency Responder Logs

- System Logs > Platform Logs

- System Logs > DB Logs

- System Logs >CLI Output Files

Authorization Requirements

You must have serviceability authority to access the System Logs pages.

Note

Use the Up and Down arrows next to each column heading to sort the information by each category.

The following table describes the System Logs pages.

General Description of System Logs Pages

Field

Description

Download button

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 creates a Zip file that contains the log files to be downloaded.

File Name

Name of the log file. If you click 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.

Reload Log File button

Reloads the log file currently being viewed, so that any updates can be seen.

Note:
This button is only available when you have clicked a file name and are viewing the contents of particular log file.

Last Modified

Date the log file was last modified.

File Size (KB)

Size of the log file, in kilobytes.

Descriptions of Individual System Log File Pages

Menu/Log File Page

Description

CER Logs > CER Admin

View or download Emergency Responder Admin logs.

CER Logs > CER Server

View or download Emergency Responder Server logs.

CER Logs > CER Phone Tracking

View or download Emergency Responder Phone Tracking logs.

CER Logs > JTAPI

View or download JTAPI logs.

CER Logs > Tomcat

View or download Tomcat logs.

CER Logs > Event Viewer

View or download Emergency Responder Event logs.

CER Logs > Audio Driver

View or download Emergency Responder Audio Driver logs.

Platform Logs > CLI

View or download CLI operations logs.

Platform Logs > CLM

View or download CLM (Cluster Manager) logs.

Platform Logs > Certificate Management/IPSec

View or download Certificate Management and IPSec logs.

Platform Logs > DRS

View or download DRS (Disaster Recovery System) logs.

Platform Logs > Install/Upgrade

View or download Installation and Upgrade logs.

Platform Logs > Remote Support

View or download Remote Account creation and operations logs.

Platform Logs > Syslog

View or download Syslog logs.

Platform Logs > Servm

View or download Servm (Services Manager) logs.

DB Logs > Cerdbmon

View or download Cerdbmon logs.

DB Logs > Install DB

View or download InstallDB Utility logs.

CLI OutputFiles >Platform

View or download Platform log files.

CLI OutputFiles >DB

View or download DB log files.

Related Tasks

Use Emergency Responder Logs

Use Emergency Responder Logs

Emergency Responder 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 Emergency Responder logs.

Emergency Responder logs are organized into three types. The three types, and the logs within these types, are as follows:

- Emergency Responder 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

- DB Logs

- Cerdbmon

- Install DB

- CLI Output Files

- Platform

- DB

Procedure

Step 1

From the Emergency Responder Serviceability web interface, select System Logs > Log Type > Log Name.
The selected Log Files page appears. See Use Emergency Responder Logs for details about 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

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 creates and downloads a zipped folder called CPULogs. The names of the zipped folders are based on the type of logs they contain, as follows:

- CER Admin

- CERr Server

- CER Phone Tracking

- Syslog

- JTAPI

- Tomcat

- Install

- DRS

- CLILogs

- CMILogs

- ServmLogs

- RemoteSupportLogs

- InstallDBLogs

- CertificateManagement&IPSecLogs

- CerdbmonLogs

- CLIOutputPlatform

- CLIOutputDB

Step 3

Click the file name to view the log files online without downloading them. The system displays the contents of the log file in a separate window.

Step 4

Click Reload Log File to refresh the log file you are viewing.

Step 5

Click Download Log to download the log file you are viewing.

ServerGroup

The ServerGroup page appears when you choose Show > ServerGroup.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the ServerGroup page to view information about the Emergency Responder servers in the server group.

The following table describes the ServerGroup page.

ServerGroup Page

Field

Description

ServerGroup

Hostname

Displays the name of the host.

IP Address

Displays the IP address of the host.

Alias

Displays the alias of the host

Type of Node

Displays the node type of the host.

Related Tasks

View Hardware Status

View Hardware Status

Procedure

Step 1

From the main Cisco Unified Operating System 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 1.

Hardware Status

The Hardware Status page appears when you choose Show > Hardware.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Hardware Status page to view information about the Emergency Responder hardware.

The following table describes the Hardware Status page.

Hardware Status Page

Field

Description

Hardware Resources

Platform Type

Model identity of the platform server

Processor Speed

Speed of the processor

CPU Type

Type of processor in the platform server

Memory

Total amount of memory in Mbytes

Object ID

Object ID of the platform server

OS Version

Operating system version running on the platform server

RAID Details

Detailed summary of the platform hardware

Related Tasks

View Hardware Status

View Hardware Status

Procedure

Step 1

From the main Cisco Unified Operating System 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 1.

Network Configuration

The Network Configuration page appears when you choose Show > Network.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Network Configuration page.

Network Configuration Page

Field

Description

Ethernet Details

DHCP Status

Indicates whether DHCP is enabled for Ethernet port 0.

Status

Indicates whether the port is Up or Down for Ethernet ports 0 and 1.

IP Address

Shows the IP address of Ethernet port 0 (and Ethernet port 1 if Network Fault Tolerance (NFT) is enabled).

IP Mask

Shows the IP mask of Ethernet port 0 (and Ethernet port 1 if NFT is enabled).

Link Detected

Indicates whether there is an active link.

Queue Length

Displays the length of the queue.

MTU

Displays the maximum transmission unit.

MAC Address

Displays the hardware address of the port.

RX Stats

Displays information about received bytes and packets.

TX Stats

Displays information about transmitted bytes and packets.

DNS Details

Primary DNS

Displays the IP address of the primary domain name server.

Secondary DNS

Displays the IP address of the secondary domain name server.

Options

Displays the number of attempts and timeouts.

Domain

Displays the domain of the server.

Gateway

Displays the IP address of the network gateway on Ethernet port 0.

Related Tasks

View Network Status

View 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.

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > Network. The Network Settings page appears.

Step 2

See Table 1 for descriptions of the fields on the Network Settings page.

Software Packages

The Software Packages page appears when you choose Show > Software.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Software Packages page to view the software versions and installed software options.

The following table describes the Software Packages page.

Software Packages Page

Field

Description

Partition Versions

Displays the software version that is running on the active and inactive partitions.

Active Version Installed Software Options

Displays the versions of installed software options that are installed on the active version.

Inactive Version Installed Software Options

Displays the versions of installed software options that are installed on the inactive version.

Related Tasks

View Installed Software

View Installed Software

Procedure

Step 1

From the Cisco Unified Operating System 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 1.

System Status

The System Status page appears when you choose Show > System.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the System Status page to view the status of the Emergency Responder system.

The following table describes the System Status page.

System Status Page

Field

Description

Host Name

Name of the Cisco UCS host where the Emergency Responder system is installed.

Date

Date and time based on the continent and region that were specified during operating system installation.

Time Zone

Time zone that was chosen during installation.

Locale

Locale of the system.

Product Version

Operating system version.

Platform Version

Platform version.

Uptime

Displays system uptime information.

CPU

Displays the percentage of CPU capacity that is idle, the percentage that is running system processes, and the percentage that is running user processes.

Memory

Displays information about memory usage, including the amount of total memory, free memory, and used memory in kilobytes.

Disk/active

Displays the amount of total, free, and used disk space on the active disk.

Disk/inactive

Displays the amount of total, free, and used disk space on the inactive disk.

Disk/logging

Displays the amount of total, free, and disk space that is used for disk logging.

Related Tasks

View System Status

View System Status

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > System. The System Status page appears.

Step 2

See Table 1 for descriptions of the fields on the System Status page.

IP Preferences

The IP Preferences page appears when you choose Show > IP Preferences.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the IP Preferences page to view a list of registered ports that can be used by the system. The following table describes the IP Preferences page.

IP Preferences Page

Field

Description

Application

Name of the application using (listening on) the port.

Protocol

Protocol used on this port (TCP, UDP, and so on).

Port Number

Numeric port number.

Type

Type of traffic allowed on this port:

- Public—All traffic allowed.

- Translated—All traffic allowed but forwarded to a different port.

- Private—Traffic only allowed from a defined set of remote servers, for example, other servers in the server group.

Translated Port

Traffic destined for this port get forwarded to the port listed in the Port Number column. This field applies to Translated type ports only.

Status

Status of port usage:

- Enabled—In use by the application and opened by the firewall.

- Disabled—Blocked by the firewall and not in use.

Description

Brief description of how the port is used.

Related Tasks

View IP Preferences

View IP Preferences

Procedure

Step 1

From the Cisco Unified Operating System Administration web page, select Show > IP Preference. The IP Preferences page appears.

Step 2

To find all records in the database, ensure the dialog box is empty; go to Step 3.
To filter or search records:

- From the first drop-down list box, select a search parameter.

- From the second drop-down list box, select a search pattern.

- Specify the appropriate search text, if applicable.

Note:
To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click Clear Filter to remove all added search criteria.

Step 3

Click Find.
All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.

Ethernet Configuration

The Ethernet Configuration page appears when you choose Settings > IP > Ethernet.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Ethernet Configuration page.

Ethernet Configuration Page

Field

Description

DHCP Information

DHCP

Indicates whether DHCP is enabled or disabled and allows you to change the DHCP setting using the pull-down menu.

Host Information

Hostname

Displays the server name (Display only—Cannot configure).

Port Information

IP Address

Displays the IP address of the system. You can change the IP address by entering a new IP address in the text box.

Subnet Mask

Displays the IP subnet mask address. You can change the mask by entering a new subnet mask in the text box.

Gateway Information

Default Gateway

Displays 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.

Save button or icon

Saves any changes made to the Ethernet Configuration page.

Caution:
If you click Save, the machine reboots. Do not click Save unless you want to shut down and reboot your system.

Note:
To recognize any new IP addresses, both servers in the server group must be manually rebooted.

Related Tasks

Set Up Ethernet Settings

Set Up 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 port 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.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > IP > Ethernet. The Ethernet Configuration page appears.

Step 2

Modify the Ethernet settings by entering the new values in the appropriate fields. For a description of the fields on the Ethernet Configuration page, see Table 1.
Note:
If you enable DHCP, then the Port Information and Gateway Information settings are disabled and cannot be changed.

Step 3

Click Save to preserve your changes.

Publisher Settings

The Publisher Settings page appears when you choose Settings > IP > Publisher.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Publisher Settings page to view or change the Publisher hostname or IP address.

Note

You can only view and change the publisher hostname IP address only on the Emergency Responder Subscriber, not on the Emergency Responder publisher itself. Changing these fields must be followed by an immediate reboot of the Subscriber.

Publisher Settings Page

Field

Description

Hostname

Displays the hostnames of the Emergency Responder Publisher for this Subscriber. To change the hostname, enter the new hostname in the text box, and click Save.

IP Address

Displays the IP address of the Emergency Responder Publisher for this Subscriber. To change the IP address, enter the IP address in the text box, and click Save.

Save button or icon

Saves the information in the Publisher Configuration Settings page.

Related Information

Change IP Addresses for Emergency Responder Servers

Change IP Addresses for Emergency Responder Servers

You can change the IP address of either the Emergency Responder Publisher, Emergency Responder Subscriber, or both the Emergency Responder Publisher and Subscriber.

The following sections provide information on changing IP addresses on the Emergency Responder servers.

NTP Server List

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

Authorization Requirements

You must have platform administrator authority to access this page.

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 to 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.

The following table describes the NTP Server List page.

NTP Server List Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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.

Clear All button or icon

Deselects all NTP servers listed. When you click this button or icon, all check marks disappear.

Note:
The Clear All button or icon is only visible if you have previously configured one or more NTP servers.

Delete Selected button or icon

Deletes the selected NTP server. To delete an NTP server, you must first select it from the list of NTP servers. Click 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.

The following table describes the NTP Server Configuration page.

NTP Server Configuration Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server Settings

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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 Tasks

Set Up NTP Servers

Set Up 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 about the NTP Server List page, see NTP Server List.

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.

SMTP Settings

The SMTP Settings page appears when you choose Settings > SMTP.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the SMTP Settings page to manually configure the SMTP host.

The following table describes the SMTP Settings page.

SMTP Settings Page

Field

Description

Status

Displays the status of the SMTP Settings page.

SMTP Host

Hostname or IP Address

Enter the hostname or IP address of the SMTP server in the text box.

Host Status

Displays the status of the SMTP host server.

Save button or icon

Saves changes made to the SMTP Settings page.

Related Tasks

Set Up SNMPv2

Set Up SNMPv2

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 define in Emergency Responder. If you use different strings for different sets of switches, determine whether 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.*.*.

If two or more patterns match an IP address, Emergency Responder 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, Emergency Responder uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

Procedure

Step 1

Select Phone Tracking > SNMPv2 Settings.
Emergency Responder opens the SNMP Settings page.

Step 2

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 Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see LAN Switch Identification for more information), it does not matter if the IP address patterns cover devices other than switches.

- If all of your switches use the same read community string, enter *.*.*.*. You 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 Emergency Responder 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, Emergency Responder 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.

Step 4

Enter the read community string, for example, public.

Step 5

Click Insert.
Emergency Responder adds the SNMP setting to the list of settings.

Step 6

If you must create more than one setting, return to Step 2.
If you change the SNMP read community string on a switch, you must update the associated setting in Emergency Responder:

- To change an SNMP setting, select it in the list. Emergency Responder 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 setting's entry.

Time Settings

The Time Settings page appears when you choose Settings > Time.

Authorization Requirements

You must have platform administrator authority to access this page.

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 NTP Server List for more information.

Caution

If you change the server time, you must reboot both the Publisher and the Subscriber.

The following table describes the Time Settings page.

Time Settings Page

Field

Description

Date

Allows you to set the month, day, year, hours, minutes, and seconds using the pull-down menus.

Save button or icon

Saves changes made to the Time Settings page.

Related Tasks

Set Up NTP Servers

Set Up Time Settings

Related References

NTP Server List

NTP Server List

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

Authorization Requirements

You must have platform administrator authority to access this page.

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 to 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.

The following table describes the NTP Server List page.

NTP Server List Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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.

Clear All button or icon

Deselects all NTP servers listed. When you click this button or icon, all check marks disappear.

Note:
The Clear All button or icon is only visible if you have previously configured one or more NTP servers.

Delete Selected button or icon

Deletes the selected NTP server. To delete an NTP server, you must first select it from the list of NTP servers. Click 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.

The following table describes the NTP Server Configuration page.

NTP Server Configuration Page

Field

Description

Status

Displays how many configured NTP server were found.

NTP Server Settings

Hostname or IP Address field

Displays the hostnames or IP addresses of the configured NTP servers. To change a hostname or 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.

Set Up 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 about the NTP Server List page, see NTP Server List.

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.

Set Up Time Settings

Before You Begin

Note

Before you can manually configure the server time, you must delete any NTP servers that you have configured. See Set Up NTP Servers for information about deleting NTP servers.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > Time. The Time Settings page appears. For details about the Time Settings page, see Time Settings.

Step 2

Enter the date and time for the system.

Step 3

Click Save.

Version Settings

The Version Settings page appears when you choose Settings > Version.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Version Settings page to restart or shutdown the system and to switch software versions.

Note

You must have a different software version installed on the inactive partition to switch versions.

Caution

Initiating this action causes the system to restart and become temporarily unavailable.

The following table describes the Version Settings page.

Version Settings Page

Field

Description

Status

Displays the current status.

Installed Versions

Active Version

Displays the version running on the active partition.

Inactive Version

Display the version on the inactive partition.

Restart button or icon

Restarts the system.

Shutdown button or icon

Shuts down the system.

Switch Versions button or icon

Actives the software version on the inactive partition.

Note:
The Switch Versions button or icon is only visible if there is a software version installed on the inactive partition.

Related Tasks

Manage Software Versions

Manage Software Versions

You can use this option both when you are upgrading to a newer software version or when you must fall back to an earlier software version.

Caution

This procedure causes the system to restart and become temporarily out of service.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Settings > Version. The Version Settings page appears. For details about the Version Settings page, see Version Settings.

Step 2

Click Restart to restart the version running on the active partition.
The system restarts on the current partition without switching versions.

Step 3

Click Shutdown to shut down the system.
The system halts all processes and shuts down.

Note:
The hardware does not power down automatically.

Caution:
If you press the power button on the server, the system immediately shuts down.

Step 4

Click Switch Versions 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.
The system restarts and the partition that is currently inactive becomes active.

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 must fall back to an earlier software version.

Certificate List

The Certificate List page appears when you choose Security > Certificate Management.

Authorization Requirements

You must have platform administrator authority to access this page.

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

The following table describes the Certificate List page.

Certificate List Page

Field

Description

Status

Displays the current status.

Certificate List

Find certificate list where

Enter search criteria for the certificate lists you want to find.

To find all certificate lists by file name, select File Name from the pull-down menu and click Find without entering any criteria.

To find all certificate lists by certificate name, select Certificate Name from the pull-down menu and click Find without entering any criteria.

To narrow your search:

- Select the search relationship (begins with, contains, and so on) from the pull-down 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 pull-down 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 7 for information about the Certificate Configuration Page.

Generate New button or icon

Allows you to generate a new certificate. When you click Generate New, the Generate Certificate page appears. See Table 2 for a description of the Generate Certificate page.

Upload Certificate 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 3 for a description of the Upload Certificate page.

Upload CTL button or icon

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 4 for a description of the Upload Certificate Trust List page.

Generate CSR button or icon

Allows you to generate a new Certificate Signing Request (CSR). When you click Generate CSR, the Generate Certificate Signing Request page appears. See Table 5 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 6 for a description of the Download Certificate Signing Request page.

The following table describes the Generate Certificate page.

Generate Certificate Page

Field

Description

Status

Displays the current status of the Generate Certificate page.

Generate Certificate

Certificate Name

Allows you to choose a certificate name from the pull-down menu.

Generate New button or icon

Generates a new certificate. You must first select a Certificate Name from the pull-down menu.

Close button or icon

Closes the Generate Certificate page.

The following table describes the Upload Certificate page.

Upload Certificate Page

Field

Description

Status

Displays the current status of the Upload Certificate page.

Upload Certificate

Certificate Name

Use the pull-down menu to select the name of the certificate to upload.

Root Certificate

Enter the name of the root certificate.

Upload File

Use the Browse button to select the file to be uploaded.

Upload File button or icon

Uploads the certificate file specified in the Upload Certificate section.

Close button or icon

Closes the Update Certificate page.

The following table describes the Upload CTL page.

Upload CTL Page

Field

Description

Status

Displays the current status of the Upload CTL page.

Upload Certificate

Certificate Name

Use the pull-down menu to select the name of the CTL file to upload.

Root Certificate

Enter the name of the root certificate.

Upload File

Use the Browse button to select the file to be uploaded.

Upload File button or icon

Uploads the certificate file specified in the Upload Certificate Trust List section.

Close button or icon

Closes the Update CTL page.

The following table describes the Generate CSR page.

Generate CSR Page

Field

Description

Status

Displays the current status of the Generate CSR page.

Generate Certificate Signing Request

Certificate Name

Use the pull-down menu to select the name of the CTL file to generate.

Generate CSR button or icon

Generates a new CSR.

Close button or icon

Close the Generate CSR page.

The following table describes the Download CSR page.

Download CSR Page

Field

Description

Status

Displays the current status of the Download CSR page.

Download Certificate Signing Request

Certificate Name

Use the pull-down menu to select the name of the CTL file to download.

Download CSR button or icon

Downloads the CSR specified in the Download Certificate Signing Request section.

Close button or icon

Closes the Download CSR page.

The following table describes the Certificate Configuration page.

Certificate Configuration Page

Field

Description

Status

Displays the current status of the Certificate Configuration page.

Certificate Settings

Displays the following information about the certificate:

- File Name

- Certificate Name

- Certificate Type

- Certificate Group

- Description

Certificate File Data

Displays the contents of the certificate file.

Delete button or icon

Deletes the current certificate.

Download button or icon

Downloads the certificate to your local system.

Related Information

Certificate Management

Certificate Management

The following sections describe the functions you can perform using the Certificate Management menu options.

Certificate Monitor

The Certificate Monitor page appears when you choose Security > Certificate Monitor.

Authorization Requirements

You must have platform administrator authority to access this page.

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

The following table describes the Certificate Monitor page.

Certificate Monitor Page

Field

Description

Status

Displays the current status of the Certificate Monitor page.

Certificate Monitor Configuration

Notification Start Time

Enter the number of days before the certificate expires that you want to be notified.

Notification Frequency

Enter the notification frequency and click one of the radio buttons to indicate days or hours.

Enable Email Notification

Check the box to the enable email notification.

Note:
For the system to send notifications, you must configure an SMTP host.

Email ID

Enter the email addresses of those to be notified in the text box. Enter multiple e-mail addresses by separating each address with a semicolon (;). There should be no spaces between the email addresses.

Save button or icon

Saves the information entered on the Certificate Monitor page.

Related Information

Certificate Management

Certificate Management

The following sections describe the functions you can perform using the Certificate Management menu options.

IPSec Policy List

The IPSec Policy List page appears when you choose Security > IPSec Configuration.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the IPsec Policy List page to display existing IPsec policies, add an additional IPsec policy, or modify an existing IPsec policy.

The following table describes the IPsec Policy List page.

IPSec Policy List Page

Field

Description

Status

Displays the current status of the IPsec Policy List page.

IPSec Policy List

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 2 for information about the IPsec Policy Configuration page.

The following table describes the IPSec Policy Configuration page.

IPSec Policy Configuration Page

Field

Description

Status

Displays the current status of the IPsec Policy Configuration page.

IPSec Policy Details

Policy Group Name

Policy Name

Specifies the name of the IPsec policy.

Authentication Method

Specifies the authentication method.

Preshared Key

Specifies the preshared key if you selected Pre-shared Key in the Authentication Name field.

Peer Type

Specifies whether the peer is the same type or different.

Certificate Name

The name of the certificate.

Destination Address

Specifies the IP address or FQDN of the destination.

Destination Port

Specifies the port number at the destination.

Source Address

Specifies the IP address or FQDN of the source.

Source Port

Specifies the port number at the source.

Mode

Specifies Tunnel or Transport mode.

Remote Port

Specifies the port number to use at the destination.

Protocol

Specifies the specific protocol, or Any:

- TCP

- UDP

- Any

Encryption Algorithm

From the drop-down list, choose the encryption algorithm. Choices include:

- DES

- 3DES

Hash Algorithm

Specifies the hash algorithm:

- SHA1—Hash algorithm that is used in phase 1 IKE negotiation.

- MD5—Hash algorithm that is used in phase 1 IKE negotiation.

ESP Algorithm

From the drop-down list, choose the ESP algorithm. Choices include:

- NULL_ENC

- DES

- 3DES

- BLOWFISH

- RIJNDAEL

Phase 1 DH Group

Phase One Life Time

Specifies the lifetime for phase One, IKE negotiation, in seconds.

Phase One DH

From the drop-down list, choose the phase One DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18.

Phase 1 DH Group

Phase Two Life Time

Specifies the lifetime for phase Two, IKE negotiation, in seconds.

Phase Two DH

From the drop-down list, choose the phase Two DH value. Choices include: 2, 1, 5, 14, 16, 17, and 18.

IPSec Policy Configuration

Enable Policy

Check the check box to enable the policy.

Save button or icon

Saves the changes made to the IPsec Policy List page.

Related Information

IPsec Management

IPsec Management

The following topics describe how to manage IPsec.

Note

IPsec does not get automatically set up between servers in the server group during installation.

Ping Configuration

The Ping Configuration page appears when you choose Services > Ping.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Ping Configuration page to send ping requests to test if other systems are reachable over the network.

The following table describes the Ping Configuration page.

Ping Configuration Page

Field

Description

Status

Displays the current status of the Ping Configuration page.

Ping Settings

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

Text box in which you enter the amount of time between ping requests, in seconds.

Packet Size

Text box into which you enter the packet size of the ping request.

Ping iterations

Pull-down 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

Select the check box to have the system validate IPsec.

Ping Results

Text box in which the ping results are displayed.

Ping button or icon

Sends the ping request.

Related Tasks

Ping Another System

Ping Another System

The Ping Configuration page enables you to send ping requests to test if other systems are reachable over the network.

Procedure

Step 1

From the Cisco Unified OS Administration web page, select Services > Ping.
The Ping Configuration page appears. For details about the Ping Configuration page, see Ping Configuration.

Step 2

Enter the IP address or network name for the system that you want to ping.

Step 3

Enter the ping interval in seconds.

Step 4

Enter the packet size.

Step 5

Enter the ping count, which is 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. The ping command displays the date and time once the ping count is completed.

Step 6

Choose if you want to validate IPsec or not.

Step 7

Click Ping.
The Ping Results text box displays the ping statistics.

Remote Access Configuration

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

Authorization Requirements

You must have platform administrator authority to access this page.

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. If the account duration limit expires, Cisco support can not 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:

1. Call Cisco support and provide them with the remote support account name and pass phrase.

2. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase.

3. 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 can create a new account.

The following table describes the Remote Access Configuration page.

Remote Access Configuration Page

Field

Description

Status

Displays the current status of the Remote Access Configuration page.

Remote Access Account Information

Account Name

Name for the new remote account. Account names must be at least six-characters long and consist of all lowercase, alphabetic characters

Account Duration

The amount of time that the remote account exists, in days.

Save button or icon

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 2 for a description of the fields on the Remote Access Configuration page.

Delete button or icon

Deletes the currently configured remote account.

Note:
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.

The following table describes the Remote Access Configuration page.

Remote Access Configuration Page

Field

Description

Remote Access Account Information

Account Name

Displays the name of the remote support account.

Expiration

Displays the date and time when access to the remote account expires.

Passphrase

Displays the generated pass phrase.

Decode Version

Indicates the version of the decoder in use.

Delete button or icon

Deletes the remote access account information.

Related Tasks

Set Up Remote Support

Set Up Remote Support

From the Remote Support page, you can set up a remote account that Cisco support personnel can use to access the Emergency Responder system for a specified period of time.

1. The customer sets up a remote support account. This account includes a configurable time limit on how long Cisco personnel can access it.

2. When the remote support account is set up, a pass phrase gets generated.

3. The customer calls Cisco support and provides the remote support account name and pass phrase.

4. Cisco support enters the pass phrase into a decoder program that generates a password from the pass phrase.

5. Cisco support logs into the remote support account on the customer system by using the decoded password.

6. 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

If no remote support account is configured, click Add.

Step 3

Enter an account name for the remote account and the account life in days.
Note:
Ensure the account name at least six-characters long and all lowercase, alphabetic characters.

Step 4

Click Save. The Remote Access Configuration page redisplays. For descriptions of fields on the Remote Access Configuration page, see Table 2.

Step 5

To access the system by using the generated pass phrase, contact your Cisco TAC.

Backup Device List

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Device List page to list, add, and delete backup devices.

The following table describes the Backup Device List page.

Backup Device List Page

Field

Description

Backup Device List

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.

Add New button

Adds a new backup device. When you click the Add icon, the Backup Device page appears. See Table 2 for information about the Backup Device page.

Select All button and icon

Selects all the listed backup devices.

Clear All button and icon

Deselects all selected backup devices.

Delete Selected button and icon

Deletes the selected backup devices.

The following table describes the Backup Device page, which you use to add new backup devices.

Backup Device Page

Field

Description

Backup device name

Enter the device name in the text box (required).

Select Destination

To select the backup destination, click the Tape Device or Network Directory radio button (required).

Tape Device

Select the name of the tape device from the pull-down menu.

Network Directory

In the fields provided, enter the Server name, Path name, User name, and Password for the Network Directory.

Number of backups to store on the Network Directory

Select the number of backups using the pull-down menu.

Save button and icon

Saves the information about the new backup device.

Back button and icon

Returns to the Backup Device List page.

Related Tasks

Add Backup Devices

Add 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.

Procedure

Step 1

Select Backup > Backup Device from the main Disaster Recovery System web page. The Backup Device List page appears.

Step 2

Click Add New to configure a new backup device. To edit a backup device, select it in the Backup Device list and click Edit Selected. The Backup Device window appears.

Step 3

In the Backup device name field, enter the backup device name.
Note:
The backup device name may contain only alphanumeric characters, spaces ( ), dashes (-), and underscores (_). No other characters are allowed.

Step 4

Choose one of the following backup devices and enter the appropriate field values in the Select Destination area:

- Tape Device—Stores 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 Directory—Stores 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 before the backup. The account that is used to access the SFTP server must have write permission for the selected path.

Step 5

Click Save to update these settings, .
Note:
For network directory backups, after you click the Save button, the DRS Master Agent validates the selected SFTP server. If the user name, password, server name, or directory path is invalid, the save fails.

Step 6

To delete a backup device, select it in the Backup Device list and Delete Selected.
Note:
You cannot delete a backup device that is configured as the backup device in a backup schedule.

Schedule List

The Schedule List page appears when you choose Backup > Scheduler.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Schedule List page.

Schedule List Page

Field

Description

Schedule List

Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click 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 2 for information about 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.

Clear All button or icon

Deselects all selected schedules.

Note:
The Clear All button only appears if no schedules have been configured.

Delete Selected button or icon

Deletes the selected schedules.

Note:
The Delete Selected button only appears if no schedules have been configured.

Enable Selected Schedules button or icon

Enables the selected schedules.

Note:
The Enable Selected Schedules icon only appears if no schedules have been configured.

Disable Selected Schedules button or icon

Disables the selected schedules.

Note:
The Disable Selected Schedules button only appears if no schedules have been configured.

The following table describes the Scheduler page.

Scheduler Page

Field

Description

Status

Displays the status of the Scheduler page.

Schedule Name

Enter the name of the schedule in the text box.

Select Backup Device

Select the name of the backup device from the pull-down menu.

Select Features

Select Emergency Responder as the feature to be backed up.

Start Backup at

Date

From the pull-down menus, enter the year, month, and day on which the backup starts.

Time

From the pull-down menus, enter the hour and minute at which the backup starts.

Frequency

Once

Click this radio button to schedule a single backup.

Daily

Click this radio button to schedule a daily backup.

Weekly

Click this radio button to schedule a weekly backup. Check the check boxes to specify the days on which the weekly backup is scheduled.

Monthly

Click this radio button to schedule a monthly backup.

Save button or icon

Saves the backup schedule information.

Set Default button or icon

Saves the information entered as the default for scheduled backups.

Disable Schedule button or icon

Disables the Schedule. If the Schedule is currently disabled, this button is grayed out.

Enable Schedule button or icon

Enables the Schedule. If the Schedule is currently enabled, this button is grayed out.

Back button or icon

Returns to the Scheduler List page.

Related Tasks

Create and Edit Backup Schedules

Manage Backup Schedules

Related References

Backup History and Restore History

Backup Status

Backup History and Restore History

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup History page to view information about past backups. Use the Restore History page to view information about past restore operations.

The following table describes the Backup History page.

Backup History Page

Field

Description

Backup History information

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.

The following table describes the Restore History page.

Restore History Page

Field

Description

Restore History information

The following information about past backups is displayed:

- Tar Filename

- Backup Device

- Completed On

- Result

- Features Restored

Refresh button or icon

Refreshes the information in the Restore History page.

Backup Status

The Backup Status page appears when you choose Backup > Current Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Status page to view status information about the current backup.

The following table describes the Backup Status page.

Backup Status Page

Field

Description

Status

Provides information about the status of the current backup.

Backup Details

The following information about the current backup is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current backup.

Cancel Backup button or icon

Cancels the current backup.

Create and Edit 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.

Procedure

Step 1

Select Backup > Scheduler from the main Disaster Recovery System web page.
The Schedule List window appears.

Step 2

Do one of the following steps to add a new schedule or edit an existing schedule:

- Click Add New to create a new schedule.

- Click a name in the Schedule List column to configure an existing schedule.

The scheduler window appears.

Step 3

Enter a schedule name in the Schedule Name field.
Note:
You cannot change the name of the default schedule.

Step 4

Select the backup device in the Select Backup Device area.

Step 5

Select the features to back up in the Select Features area. You must choose at least one feature.

Step 6

Choose the date and time when you want the backup to begin in the Start Backup at area.

Step 7

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 occurs.
Tip:
To set the backup frequency to Weekly, occurring Tuesday through Saturday, click Set Default.

Step 8

Click Save to update these settings.

Step 9

Click Enable Schedule to enable the schedule.
The next backup occurs automatically at the time that you set.

Note:
Ensure that all servers in the server group are running the same version of Emergency Responder and are reachable through the network. Servers that are not running at the time of the scheduled backup are not backed up.

Step 10

Click Disable Schedule to disable the schedule.

Manage Backup Schedules

Procedure

Step 1

Select Backup > Scheduler from the main Disaster Recovery System web page. The Schedule List window appears.

Step 2

Select the check boxes next to the schedules that you want to modify:

- Click Select All to select all schedules.

- Click Clear All To uncheck all check boxes.

Step 3

Click Enable Selected Schedules to enable the selected schedules.

Step 4

Click Disable Selected Schedules to disable the selected schedules.

Step 5

Click Delete Selected to delete the selected schedules.

Manual Backup

The Manual Backup page appears when you choose Backup > Manual Backup.

Authorization Requirements

You must have platform administrator authority to access this page.

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 are not backed up.

The following table describes the Manual Backup page.

Manual Backup Page

Field

Description

Select Backup Device

Select the name of the backup device from the pulldown menu.

Select Features

Check Emergency Responder as the feature to be backed up.

Start Backup button or icon

Starts a manual backup.

Select All button or icon

Selects all the listed features.

Clear All button or icon

Deselects all selected features.

Related Tasks

Start Manual Backup

Related References

Schedule List

Schedule List

The Schedule List page appears when you choose Backup > Scheduler.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Schedule List page.

Schedule List Page

Field

Description

Schedule List

Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click 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 2 for information about 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.

Clear All button or icon

Deselects all selected schedules.

Note:
The Clear All button only appears if no schedules have been configured.

Delete Selected button or icon

Deletes the selected schedules.

Note:
The Delete Selected button only appears if no schedules have been configured.

Enable Selected Schedules button or icon

Enables the selected schedules.

Note:
The Enable Selected Schedules icon only appears if no schedules have been configured.

Disable Selected Schedules button or icon

Disables the selected schedules.

Note:
The Disable Selected Schedules button only appears if no schedules have been configured.

The following table describes the Scheduler page.

Scheduler Page

Field

Description

Status

Displays the status of the Scheduler page.

Schedule Name

Enter the name of the schedule in the text box.

Select Backup Device

Select the name of the backup device from the pull-down menu.

Select Features

Select Emergency Responder as the feature to be backed up.

Start Backup at

Date

From the pull-down menus, enter the year, month, and day on which the backup starts.

Time

From the pull-down menus, enter the hour and minute at which the backup starts.

Frequency

Once

Click this radio button to schedule a single backup.

Daily

Click this radio button to schedule a daily backup.

Weekly

Click this radio button to schedule a weekly backup. Check the check boxes to specify the days on which the weekly backup is scheduled.

Monthly

Click this radio button to schedule a monthly backup.

Save button or icon

Saves the backup schedule information.

Set Default button or icon

Saves the information entered as the default for scheduled backups.

Disable Schedule button or icon

Disables the Schedule. If the Schedule is currently disabled, this button is grayed out.

Enable Schedule button or icon

Enables the Schedule. If the Schedule is currently enabled, this button is grayed out.

Back button or icon

Returns to the Scheduler List page.

Start Manual Backup

Procedure

Step 1

Select Backup > Manual Backup from the main Disaster Recovery System web page. The Manual Backup page appears.

Step 2

Select a backup device in the Select Backup Device area.

Step 3

Select the features to back up in the Select Features area.

Step 4

Click Start Backup to start the manual backup.

Backup History and Restore History

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup History page to view information about past backups. Use the Restore History page to view information about past restore operations.

The following table describes the Backup History page.

Backup History Page

Field

Description

Backup History information

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.

The following table describes the Restore History page.

Restore History Page

Field

Description

Restore History information

The following information about past backups is displayed:

- Tar Filename

- Backup Device

- Completed On

- Result

- Features Restored

Refresh button or icon

Refreshes the information in the Restore History page.

Related References

Schedule List

Manual Backup

Backup Status

Restore Wizard

Restore Status

Related Information

Backup and Restore History

Schedule List

The Schedule List page appears when you choose Backup > Scheduler.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Schedule List page.

Schedule List Page

Field

Description

Schedule List

Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click 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 2 for information about 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.

Clear All button or icon

Deselects all selected schedules.

Note:
The Clear All button only appears if no schedules have been configured.

Delete Selected button or icon

Deletes the selected schedules.

Note:
The Delete Selected button only appears if no schedules have been configured.

Enable Selected Schedules button or icon

Enables the selected schedules.

Note:
The Enable Selected Schedules icon only appears if no schedules have been configured.

Disable Selected Schedules button or icon

Disables the selected schedules.

Note:
The Disable Selected Schedules button only appears if no schedules have been configured.

The following table describes the Scheduler page.

Scheduler Page

Field

Description

Status

Displays the status of the Scheduler page.

Schedule Name

Enter the name of the schedule in the text box.

Select Backup Device

Select the name of the backup device from the pull-down menu.

Select Features

Select Emergency Responder as the feature to be backed up.

Start Backup at

Date

From the pull-down menus, enter the year, month, and day on which the backup starts.

Time

From the pull-down menus, enter the hour and minute at which the backup starts.

Frequency

Once

Click this radio button to schedule a single backup.

Daily

Click this radio button to schedule a daily backup.

Weekly

Click this radio button to schedule a weekly backup. Check the check boxes to specify the days on which the weekly backup is scheduled.

Monthly

Click this radio button to schedule a monthly backup.

Save button or icon

Saves the backup schedule information.

Set Default button or icon

Saves the information entered as the default for scheduled backups.

Disable Schedule button or icon

Disables the Schedule. If the Schedule is currently disabled, this button is grayed out.

Enable Schedule button or icon

Enables the Schedule. If the Schedule is currently enabled, this button is grayed out.

Back button or icon

Returns to the Scheduler List page.

Manual Backup

The Manual Backup page appears when you choose Backup > Manual Backup.

Authorization Requirements

You must have platform administrator authority to access this page.

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 are not backed up.

The following table describes the Manual Backup page.

Manual Backup Page

Field

Description

Select Backup Device

Select the name of the backup device from the pulldown menu.

Select Features

Check Emergency Responder as the feature to be backed up.

Start Backup button or icon

Starts a manual backup.

Select All button or icon

Selects all the listed features.

Clear All button or icon

Deselects all selected features.

Backup Status

The Backup Status page appears when you choose Backup > Current Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Status page to view status information about the current backup.

The following table describes the Backup Status page.

Backup Status Page

Field

Description

Status

Provides information about the status of the current backup.

Backup Details

The following information about the current backup is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current backup.

Cancel Backup button or icon

Cancels the current backup.

Restore Wizard

The Restore Wizard page appears when you choose Restore > Restore Wizard.

Authorization Requirements

You must have platform administrator authority to access this page.

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 Restore—Choose Backup Device page to select the backup device to be used for the backup.

The following table describes the Step1 Restore—Choose Backup Device page.

Step 1 Restore—Choose Backup Device Page

Field

Description

Status

Indicates the current status of the recovery operation.

Select Backup Device

Select the backup device using the pull-down menu.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step2 Restore—Choose the Backup Tar File page to select the backup tar file to be restored.

The following table describes the Step2 Restore—Choose the Backup Tar File page.

Step 2 Restore—Choose the Backup Tar File Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Backup File

Use the pull-down menu to select the tar file for backup

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step3 Restore—Select the Type of Restore page to select the features to be restored.

The following table describes the Step3 Restore—Select the Type of Restore page.

Step 3 Restore—Select the Type of Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Features

Click the box to the left of the Emergency Responder feature name to select the Emergency Responder feature for backup.

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step4 Restore—Final Warning for Restore page to select the servers to be restored.

The following table describes the Step4 Restore—Final Warning for Restore page.

Step 4 Restore—Final Warning for Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Warning

Displays a warning message stating that the restore operation overwrites all existing data on the selected servers.

Select the Servers to be restored for each Feature

Under the Emergency Responder feature name, select the servers to be restored. To do so, click the check box to the left of the server name.

Back button or icon

Returns to the previous page in the Restore Wizard.

Restore button or icon

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.

Caution:
The restore operation overwrites any existing data on the selected servers.

Cancel button or icon

Cancels the restore operation.

Restore Status

The Restore Status page appears when you choose Restore > Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Restore Status page to view the status of restore operations.

The following table describes the Restore Status page.

Restore Status Page

Field

Description

Status

Provides information about the status of the current restore operation.

Restore Details

The following information about the current restore operation is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current restore operation.

Backup and Restore History

The following sections describe how you can see the last 20 backup and restore jobs.

Backup Status

The Backup Status page appears when you choose Backup > Current Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup Status page to view status information about the current backup.

The following table describes the Backup Status page.

Backup Status Page

Field

Description

Status

Provides information about the status of the current backup.

Backup Details

The following information about the current backup is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current backup.

Cancel Backup button or icon

Cancels the current backup.

Related Tasks

Check Backup Status

Related References

Schedule List

Schedule List

The Schedule List page appears when you choose Backup > Scheduler.

Authorization Requirements

You must have platform administrator authority to access this page.

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.

The following table describes the Schedule List page.

Schedule List Page

Field

Description

Schedule List

Lists all scheduled backups. Displays the Schedule List name, the Device Path, and the Schedule Status. Click 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 2 for information about 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.

Clear All button or icon

Deselects all selected schedules.

Note:
The Clear All button only appears if no schedules have been configured.

Delete Selected button or icon

Deletes the selected schedules.

Note:
The Delete Selected button only appears if no schedules have been configured.

Enable Selected Schedules button or icon

Enables the selected schedules.

Note:
The Enable Selected Schedules icon only appears if no schedules have been configured.

Disable Selected Schedules button or icon

Disables the selected schedules.

Note:
The Disable Selected Schedules button only appears if no schedules have been configured.

The following table describes the Scheduler page.

Scheduler Page

Field

Description

Status

Displays the status of the Scheduler page.

Schedule Name

Enter the name of the schedule in the text box.

Select Backup Device

Select the name of the backup device from the pull-down menu.

Select Features

Select Emergency Responder as the feature to be backed up.

Start Backup at

Date

From the pull-down menus, enter the year, month, and day on which the backup starts.

Time

From the pull-down menus, enter the hour and minute at which the backup starts.

Frequency

Once

Click this radio button to schedule a single backup.

Daily

Click this radio button to schedule a daily backup.

Weekly

Click this radio button to schedule a weekly backup. Check the check boxes to specify the days on which the weekly backup is scheduled.

Monthly

Click this radio button to schedule a monthly backup.

Save button or icon

Saves the backup schedule information.

Set Default button or icon

Saves the information entered as the default for scheduled backups.

Disable Schedule button or icon

Disables the Schedule. If the Schedule is currently disabled, this button is grayed out.

Enable Schedule button or icon

Enables the Schedule. If the Schedule is currently enabled, this button is grayed out.

Back button or icon

Returns to the Scheduler List page.

Check Backup Status

You can check the status of the current backup job and cancel the current backup job. To view the backup history, see Backup and Restore History.

Procedure

Step 1

Select Backup > Current Status from the main Disaster Recovery System web page. The Backup Status page appears.

Step 2

Click the log filename link to view the backup log file.

Step 3

Click Cancel Backup to cancel the current backup. The backup is cancelled after the current component has completed its backup operation.

Restore Wizard

The Restore Wizard page appears when you choose Restore > Restore Wizard.

Authorization Requirements

You must have platform administrator authority to access this page.

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 Restore—Choose Backup Device page to select the backup device to be used for the backup.

The following table describes the Step1 Restore—Choose Backup Device page.

Step 1 Restore—Choose Backup Device Page

Field

Description

Status

Indicates the current status of the recovery operation.

Select Backup Device

Select the backup device using the pull-down menu.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step2 Restore—Choose the Backup Tar File page to select the backup tar file to be restored.

The following table describes the Step2 Restore—Choose the Backup Tar File page.

Step 2 Restore—Choose the Backup Tar File Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Backup File

Use the pull-down menu to select the tar file for backup

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step3 Restore—Select the Type of Restore page to select the features to be restored.

The following table describes the Step3 Restore—Select the Type of Restore page.

Step 3 Restore—Select the Type of Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Features

Click the box to the left of the Emergency Responder feature name to select the Emergency Responder feature for backup.

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step4 Restore—Final Warning for Restore page to select the servers to be restored.

The following table describes the Step4 Restore—Final Warning for Restore page.

Step 4 Restore—Final Warning for Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Warning

Displays a warning message stating that the restore operation overwrites all existing data on the selected servers.

Select the Servers to be restored for each Feature

Under the Emergency Responder feature name, select the servers to be restored. To do so, click the check box to the left of the server name.

Back button or icon

Returns to the previous page in the Restore Wizard.

Restore button or icon

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.

Caution:
The restore operation overwrites any existing data on the selected servers.

Cancel button or icon

Cancels the restore operation.

Related Tasks

Restore Backup File

Restore Entire Server Group

Related References

Backup History and Restore History

Restore Status

Backup History and Restore History

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup History page to view information about past backups. Use the Restore History page to view information about past restore operations.

The following table describes the Backup History page.

Backup History Page

Field

Description

Backup History information

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.

The following table describes the Restore History page.

Restore History Page

Field

Description

Restore History information

The following information about past backups is displayed:

- Tar Filename

- Backup Device

- Completed On

- Result

- Features Restored

Refresh button or icon

Refreshes the information in the Restore History page.

Restore Status

The Restore Status page appears when you choose Restore > Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Restore Status page to view the status of restore operations.

The following table describes the Restore Status page.

Restore Status Page

Field

Description

Status

Provides information about the status of the current restore operation.

Restore Details

The following information about the current restore operation is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current restore operation.

Restore Backup File

Disaster Recovery System adheres to strict version checking and allows restore only for matching versions of Emergency Responder.

The Restore Wizard leads you through the steps that are required to restore a backup.

Tip

To restore all servers in a server group, see Restore Entire Server Group.

Caution

Before you restore Emergency Responder, ensure that the Emergency Responder version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Emergency Responder for restore.

The product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Emergency Responder database restore.

Procedure

Step 1

Select Restore > Restore Wizard from the main Disaster Recovery System web page. The first page of the Restore Wizard (Step1 Restore—Choose Backup Device) appears.

Step 2

Choose the backup device to restore in the Select Backup Device area.

Step 3

Click Next. The Step 2 Restore—Choose the Backup Tar File page appears.

Step 4

Choose the backup file that you want to restore.
Note:
The backup filename indicates the date and time that the system created the backup file.

Step 5

Click Next. The Step 3 Restore—Select the Type of Restore page appears.

Step 6

Choose the features that you want to restore.
Note:
Only the features that were backed up to the chosen file are displayed.

Step 7

Click Next. The Step 4 Restore—Final Warning for Restore page appears.

Step 8

Click Restore to start restoring the data, . You are prompted to choose the server to restore.

Step 9

Choose the appropriate server.
Caution:
After you choose the server that you want restored, any existing data on that server will be overwritten.

Your data is restored on the server that you chose. To view the status of the restore, see View Restore Status.

Step 10

Restart the server.
Note:
The system can require one hour or more to restore depending on the size of your database and the chosen components.

Restore Entire Server Group

If a major failure or a hardware upgrade occurs, you may need to restore all the servers in the server group.

Note

Before you restore a server group, make sure that the subscriber server in the server group is up and communicating with the publisher server. You must carry out a fresh install for the subscriber server that is down or not communicating with publisher server at the time of the restore.

Procedure

Step 1

Restore both Emergency Responder Publisher and Subscriber at the same time by selecting both the servers using Restore wizard.

Step 2

Restart Publisher.

Step 3

Restart the Subscriber after the publisher is back online.
Note:
You must restore both the servers in the server group at the same time.

The following sections provide the procedures for restoring servers in a server group.

Restore Status

The Restore Status page appears when you choose Restore > Status.

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Restore Status page to view the status of restore operations.

The following table describes the Restore Status page.

Restore Status Page

Field

Description

Status

Provides information about the status of the current restore operation.

Restore Details

The following information about the current restore operation is displayed:

- Tar Filename

- Backup Device

- Operation

- Percentage Complete

- Feature

- Server

- Component

- Status

- Result

- Start Time

- Log File

Refresh button or icon

Refreshes the information about the current restore operation.

Related Tasks

View Restore Status

Related References

Restore Wizard

Backup History and Restore History

Related Information

Backup and Restore History

Restore Wizard

The Restore Wizard page appears when you choose Restore > Restore Wizard.

Authorization Requirements

You must have platform administrator authority to access this page.

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 Restore—Choose Backup Device page to select the backup device to be used for the backup.

The following table describes the Step1 Restore—Choose Backup Device page.

Step 1 Restore—Choose Backup Device Page

Field

Description

Status

Indicates the current status of the recovery operation.

Select Backup Device

Select the backup device using the pull-down menu.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step2 Restore—Choose the Backup Tar File page to select the backup tar file to be restored.

The following table describes the Step2 Restore—Choose the Backup Tar File page.

Step 2 Restore—Choose the Backup Tar File Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Backup File

Use the pull-down menu to select the tar file for backup

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step3 Restore—Select the Type of Restore page to select the features to be restored.

The following table describes the Step3 Restore—Select the Type of Restore page.

Step 3 Restore—Select the Type of Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Select Features

Click the box to the left of the Emergency Responder feature name to select the Emergency Responder feature for backup.

Back button or icon

Returns to the previous page in the Restore Wizard.

Next button or icon

Advances to the next page in the Restore Wizard.

Cancel button or icon

Cancels the restore operation.

Use the Step4 Restore—Final Warning for Restore page to select the servers to be restored.

The following table describes the Step4 Restore—Final Warning for Restore page.

Step 4 Restore—Final Warning for Restore Page

Field

Description

Status

Indicates the current status of the restore operation.

Warning

Displays a warning message stating that the restore operation overwrites all existing data on the selected servers.

Select the Servers to be restored for each Feature

Under the Emergency Responder feature name, select the servers to be restored. To do so, click the check box to the left of the server name.

Back button or icon

Returns to the previous page in the Restore Wizard.

Restore button or icon

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.

Caution:
The restore operation overwrites any existing data on the selected servers.

Cancel button or icon

Cancels the restore operation.

Backup History and Restore History

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

Authorization Requirements

You must have platform administrator authority to access this page.

Description

Use the Backup History page to view information about past backups. Use the Restore History page to view information about past restore operations.

The following table describes the Backup History page.

Backup History Page

Field

Description

Backup History information

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.

The following table describes the Restore History page.

Restore History Page

Field

Description

Restore History information

The following information about past backups is displayed:

- Tar Filename

- Backup Device

- Completed On

- Result

- Features Restored

Refresh button or icon

Refreshes the information in the Restore History page.

View Restore Status

Procedure

Step 1

From the main Disaster Recovery System web page, select Restore > Status. The Restore Status page appears. The Status column in the Restore Status window shows the status of the restoration in progress, including the percentage of completion of the restore procedure.

Step 2

Click the log filename link to view the restore log file.

Backup and Restore History

The following sections describe how you can see the last 20 backup and restore jobs.

Update Cisco Unified Communications Manager Version

The Upgrade CUCM Version page appears when you choose Update > CUCM Version.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Upgrade CUCM Version page to select a different version of Cisco Unified Communications Manager.

The following table describes the Upgrade CUCM Version page.

Upgrade CUCM Version Page

Field

Description

Status

Displays the current Cisco Unified Communications Manager version.

CUCM Version Details

Choose the Cisco Unified Communications Manager version to upgrade

Use the pull down menu to select a version of Cisco Unified Communications Manager.

Go button

Click Go to begin the update process.

Note:
Change the CUCM version separately on the Publisher and Subscriber nodes.

Cancel button

Cancels the Cisco Unified Communications Manager update.

Related Tasks

Change Cisco Unified Communications Manager Version

Change Cisco Unified Communications Manager Version

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

From the main Emergency Responder Admin Utility page, select Update > CCM Version. The Upgrade CCM Version page appears.

Step 3

Select the new version of Unified CM from the Choose the CCM Version to Upgrade pull-down menu and click Go.
Note:
You must change the Unified CM version separately for the Publisher and Subscriber nodes.

During a Layer 2 upgrade, if a lower version of Emergency Responder has Unified CM version configured as 6.0 or lower then Emergency Responder sets the Unified CM to the 6.1 version after the upgrade.

Similarly, during a Layer 2 upgrade if  lower version of Emergency Responder has Unified CM version configured as 7.0, then Emergency Responder sets it to the 7.1 version after the upgrade.

The Status area of the Upgrade CCM Version page displays the new version number after the system makes the change.

Update Cluster DB Host

The Update Cluster DB Host page appears when you choose Update > Cluster DB Host.

Authorization Requirements

You must have system administrator authority to access this page.

Description

Use the Update Cluster DB Host page to designate a new server as the Emergency Responder cluster database host server.

The following table describes the Update Cluster DB Host page.

Update Cluster DB Host Page

Field

Description

Status

Displays the name of the current cluster database host

Cluster DB Host Details

ClusterDB Hostname/IP Address

Enter the hostname (if DNS is configured) or the IP address of the new cluster database host.

Note:
If the cluster is spread across domains, then enter a fully qualified hostname.

Password

Enter the password for the new cluster database host

Confirm Password

Reenter the password for the new cluster database host.

Go button

Click the Go button to designate the new server as the new cluster database host.

Note:
The Emergency Responder Cluster DB host details are updated. Emergency Responder services must be restarted for this change to take effect. You must restart Emergency Responder Services by rebooting the Emergency Responder publisher and subscriber servers. Only restarting Emergency Responder services does not work because the IP address is cached by other services and this updates the Emergency Responder Cluster DB host details for this server group only. Other servers in this Emergency Responder cluster are NOT updated automatically. For further details, see Update Emergency Responder Cluster Database Host Details.

Cancel button

Cancels the Update Cluster DB Host operation.

Related Tasks

Set Up Emergency Responder Cluster and Cluster DB Host

Update Emergency Responder Cluster Database Host Details

Set Up Emergency Responder Cluster and Cluster DB Host

Procedure

Step 1

Identify the following:

- All the Emergency Responder groups participating in the Emergency Responder cluster

- One of the Emergency Responder publishers as "Cluster DB Host"

- A password that is the same across the Cluster as "Cluster password"

Step 2

Using the Emergency Responder Admin Utility web interface, navigate to Update > ClusterDB Host, and enter the values from Step 1.

Step 3

Repeat steps 1 and 2 for each Emergency Responder server group in the cluster.

Step 4

Restart Emergency Responder services.
Note:
Emergency Responder server groups can communicate with Emergency Responder 1.3, 2.x, 7.1 and 8.0 and later versions of Emergency Responder server groups in an Emergency Responder cluster.

Update Emergency Responder Cluster Database Host Details

By default, each server in a cluster considers its own database to be the cluster database host. Because each cluster should have only one database host, you must update the cluster configuration accordingly.

For example, if you have two server groups (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. Update the cluster database host password for Servergroup A using Servergroup A's own host name.

2. Update the cluster database host password for Servergroup B by entering the IP address and cluster database password for Servergroup A.

3. Repeat Step 2 for other server groups 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 fails and cluster functionality is 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.

Note

This procedure only updates the Emergency Responder Cluster DB host details for this server group. Other servers in this Emergency Responder cluster do not updated automatically.

Before You Begin
You must reboot the server to update Emergency Responder Cluster DB host details. Only restarting Emergency Responder services does not work because the IP address is cached by other services.

Procedure

Step 1

Log in to the Emergency Responder Admin Utility web interface.

Step 2

Select Update > Cluster DBHost from the main Emergency Responder Admin Utility page. The Update Cluster DB Host page appears.

Step 3

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.

Step 4

Enter the password for the new Cluster DBHost in the Password text box.

Step 5

Reenter the password for the new Cluster DBHost in the Confirm Password text box.

Step 6

Click Go.