Cisco Emergency Responder Administration Guide 8.0
Chapter 5: Configuring Cisco Emergency Responder 8.0
Downloads: This chapterpdf (PDF - 950.0KB) The complete bookPDF (PDF - 13.77MB) | Feedback

Configuring Cisco Emergency Responder 8.0

Table Of Contents

Configuring Cisco Emergency Responder 8.0

Overview of Cisco Emergency Responder Configuration

Cisco Emergency Responder Website Interfaces

Role-Based User Management

User Management

Role Management

User Group Management

Using the Upload and Download Utilities

Downloading a File

Uploading a File

Cisco Emergency Responder 8.0 Configuration Task Checklist

Managing Cisco Emergency Responder Users

Adding Users

Modifying Users

Change the User's Authentication Mode

Change Password for Local User

Change CUCM Cluster for Remote User

Deleting Users

Changing Users to Remote in Bulk

Managing Cisco Emergency Responder Roles

Adding Roles

Modifying Roles

Deleting Roles

Managing Cisco Emergency Responder User Groups

Adding User Groups

Modifying User Groups

Deleting User Groups

Logging Into and Out of Cisco Emergency Responder

Limiting the Number of Concurrent Sessions

Configuring Servers and Server Groups

Configuring a Cisco Emergency Responder Server Group

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

Modifying the Emergency Number

Configuring Cisco Emergency Responder Servers

Uploading the Cisco Emergency Responder License File

Identifying the Cisco Unified Communications Manager Clusters

Configuring the Cisco Emergency Responder Cluster and Cluster DB Host

Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder

Working with Emergency Response Locations

Understanding ERLs

Overview of ERL Management

Identifying Security Personnel (Onsite Alert Personnel)

Creating ERLs

Setting Up the Default ERL

Setting up ERLs for Non-PSAP Deployment

Setting Up an Individual ERL and Its Automatic Location Information (ALI)

Importing Several ERLs at Once

Converting ALI Data

Configuring IP Subnet-based ERLs

Configuring Test ERLs

Exporting ERL Information

Exporting ALI Information for Submission to Your Service Provider

Viewing the Audit Trail for an ERL

Configuring Switches for Cisco Emergency Responder

Understanding Switch Requirements for Cisco Emergency Responder

Configuring the SNMP Connection

Defining the Phone Tracking and Switch Update Schedules

Identifying the LAN Switches

Identifying LAN Switches One At a Time

Importing a Group of Switches

Exporting Switch Information

Manually Running the Switch-Port and Phone Update Process

Tracking Change of Switch IP Address Dynamically

Managing Phones

Configuring Switch Ports

Configuring a Few Switch Ports at a Time

Configuring a Large Number of Ports at Once

Exporting Switch Port Information

Switch-port Change Reporting for Wired Cisco Unified IP Phones

Identifying Unlocated Phones

Manually Defining a Phone

Assigning a Large Number of Manually Configured Phones to ERLs at Once

Exporting Manually Configured Phone Information

Adding Synthetic Phones

Viewing the Emergency Call History


Configuring Cisco Emergency Responder 8.0


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

These topics describe how to configure Cisco ER 8.0:

Overview of Cisco Emergency Responder Configuration

Managing Cisco Emergency Responder Users

Managing Cisco Emergency Responder Roles

Managing Cisco Emergency Responder User Groups

Logging Into and Out of Cisco Emergency Responder

Configuring Servers and Server Groups

Configuring the Cisco Emergency Responder Cluster and Cluster DB Host

Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder

Working with Emergency Response Locations

Configuring Switches for Cisco Emergency Responder

Managing Phones

Overview of Cisco Emergency Responder Configuration

Cisco ER 8.0 provides several new features, including expanded administrative website interfaces, role-based user management, and upload/download utilities.

These topics provide an overview of configuring the Cisco ER:

Cisco Emergency Responder Website Interfaces

Role-Based User Management

Using the Upload and Download Utilities

Cisco Emergency Responder 8.0 Configuration Task Checklist

Cisco Emergency Responder Website Interfaces

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

Cisco ER Serviceability

Cisco ER Administration (default home)

Cisco Unified OS Administration

Disaster Recovery System

Cisco ER User

Cisco ER Admin Utility

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

When the Cisco ER 8.0 system is first installed, a default CERAdministrator user is created. The default CERAdministrator has full access to all websites except the Cisco Unified OS Administration and Disaster Recovery System websites, and has the ability to create users, roles, and user groups. The default CERAdministrator cannot be deleted from the system.

Related Topics

Appendix A, "Administration Web Interface For Cisco Emergency Responder"

Appendix B, "Serviceability Web Interface For Cisco Emergency Responder"

Appendix C, "Cisco Unified Operating System Administration Web Interface For Cisco Emergency Responder"

Appendix D, "Disaster Recovery System Web Interface For Cisco Emergency Responder"

Role-Based User Management

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

User Management

Role Management

User Group Management

User Management

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


Note The default CERAdministrator user cannot be deleted.


You can add additional users. Once the additional users are added, you assign them to user groups. The new user then inherits the roles that were defined for that user group.

Related Topics

Managing Cisco Emergency Responder Users

Find and List Users, page A-61

Role Management

On installation, the system creates six default roles. Table 5-1 lists and describes the default roles.


Note Default roles cannot be deleted.


Table 5-1 Default Roles

Role
Description

CER System Admin

Has access to all system administration screens

CER Serviceability

Has access to all serviceability screens.

CER Admin Utility

Has access to all Admin Utility screens.

CER Network Admin

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

CER ERL Admin

Has access to all ERL-related screens.

CER User

Has access to the user screens.


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

Table 5-2 shows the resources that are available to each default role.


Note Some resources are groups of menu items. For example, the Logs menu in the Cisco ER Serviceability website is one resource but it contains many sub-menus.


Table 5-2 Resources Assigned to Default Roles 

Resource
CER System Admin
CER Network Admin
CER ERL Admin
CER Serviceability
CER Admin Utility
CER User

Add Subscriber

x

         

Admin Utility

x

         

ALI Formatting Tool

x

         

All Logs

     

x

   

Application User

x

         

Call History

x

         

CallManager Details

x

x

       

CER Groups in Cluster

x

         

Change CUCM 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 Topics

Managing Cisco Emergency Responder Roles

Find and List Roles, page A-64

User Group Management

On installation, the system creates six default user groups. Table 5-3 lists and describes the default user groups.


Note Default user groups cannot be deleted.


Table 5-3 Default User Groups 

User Group
Description

CER System Administrator

Assigned System Administration roles

CER Network Administrator

Assigned Network Administration role

CER ERL Administrator

Assigned ERL Administration role

CER Serviceability

Assigned Serviceability role

CER Admin Utility

Assigned Admin Utility role

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

Related Topics

Managing Cisco Emergency Responder User Groups

Find and List User Groups, page A-67

Using the Upload and Download Utilities

Cisco ER 8.0 includes download and upload utilities that allow you to transfer bulk data in the form of csv files from a Cisco ER server to a local system (download) and from a local system to a Cisco ER server (upload).

For example, you can export database details to a csv file and then download the csv file to a local system. On the local system, you can modify the csv file, upload it the Cisco ER server, and import the data in the csv file into the Cisco ER database.

Table 5-4 lists the Cisco ER administrative web pages from which you can use the upload and download utilities and gives the navigation path to each page.


Note You can upload only four file types: xml, csv, lic, and txt. Filenames must not contain spaces.


Table 5-4 Administrative Web Pages Containing the Upload and Download Utilities 

Page Name
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


Downloading a File

To download a file from a Cisco ER 8.0 server to a local system, follow these steps:

Procedure


Step 1 From one of the pages listed in Table 5-4, 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.


Uploading a File

To upload a file from a local system to a Cisco ER 8.0 server, follow these steps:

Before You Begin

Before beginning the procedure, make sure the file to be uploaded exists on your local system. The file can be one that was previously downloaded from a Cisco ER 8.0 server, or one that you created.

Procedure


Step 1 From one of the pages listed in Table 5-4, 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 Cisco ER server. You can then import the data from the file.


Related Topics

Conventional ERL, page A-15

LAN Switch Details, page A-42

Switch Port Details, page A-46

Find and List IP Subnets, page A-50

Find and List Manually Configured Phone, page A-56

File Management Utility, page A-78

Cisco Emergency Responder 8.0 Configuration Task Checklist

This checklist provides information on the tasks that need to be completed to configure Cisco ER and indicates which user types can complete the tasks, with pointers to more detailed information.


Note Some of the tasks listed below can be done in parallel.


Table 5-5 Configuration Task Checklist 

Task
Description and Location Information
System Administrator Tasks

Create and configure Cisco ER users and groups.

Create the users your organization requires for Cisco ER administration.

See the "Managing Cisco Emergency Responder Users" section and the "Logging Into and Out of Cisco Emergency Responder" section.

Create the Cisco ER group.

See the "Configuring a Cisco Emergency Responder Server Group" section.

Configure the Cisco ER group's telephony settings.

See the "Configuring Group Telephony Settings For the Cisco Emergency Responder Server" section.

Update Cisco ER servers to the Cisco ER group.

See the "Configuring Cisco Emergency Responder Servers" section.

Upload the product license key.

See the "Uploading the Cisco Emergency Responder License File" section.

Identify and configure the Cisco Unified CM clusters whose emergency calls this Cisco ER group will handle.

Note The network administrator can also perform this step.

See the "Identifying the Cisco Unified Communications Manager Clusters" section.

Understand recurring system administration tasks.

See the "Understanding the Cisco Emergency Responder System Administrator's Role" section on page 11-4.

If you use Intrado V9-1-1 for Enterprise Service, configure Cisco ER to support Intrado V9-1-1 for Enterprise Service.

See the "Configuring Intrado VUI Settings" section on page 6-3.

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

See the "Configuring AXL Authentication" section on page 6-10.

Network Administrator Tasks

Identify the switches and configure the connection to them.

Enter the SNMP read community strings.

See the "Configuring the SNMP Connection" section.

Define the schedule Cisco ER should use for updating information from the switches.

See the "Defining the Phone Tracking and Switch Update Schedules" section.

Identify the switches that can have phones connected to them.

See the "Identifying the LAN Switches" section.

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

See the "Manually Running the Switch-Port and Phone Update Process" section.

Understand recurring network administration tasks.

See the "Understanding the Network Administrator's Role" section on page 11-3.

ERL Administrator Tasks

Identify your onsite alert (security) personnel, create the emergency response locations (ERLs), assign them to phones, and transmit your ALI data to your service provider. See the "Understanding ERLs" section and "Overview of ERL Management" section for a more detailed overview of ERL management.

Identify the onsite alert (security) personnel that should receive alerts from Cisco ER

See the "Identifying Security Personnel (Onsite Alert Personnel)" section.

Create the ERLs.

See the "Creating ERLs" section.

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.

See the "Configuring Switch Ports" section.

Add phones that Cisco ER does not directly support.

Note Cisco ER does not automatically track the movement of these phones.

See the "Manually Defining a Phone" section.

Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Cisco ER from locating these phones. Assign ERLs to the phones that remain.

See the "Identifying Unlocated Phones" section.

Export the ALI data and transmit it to your service provider. Work with your service provider to determine transmission requirements.

See the "Exporting ERL Information" section and the "Exporting ALI Information for Submission to Your Service Provider" section.

Understand recurring ERL administration tasks.

See the "Understanding the ERL Administrator's Role" section on page 11-2.

The following tasks apply when you use Cisco ER 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.

See the "Configuring Intrado ERLs" section on page 6-4. and the "Reconciling ALI Discrepancies" section on page 6-6.

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

For information on assigning ERLs to switch ports, see"Configuring Switch Ports" section.

For information on assigning ERLs to IP subnets, see "Configuring IP Subnet-based ERLs" section.

For information on assigning ERLs to unlocated phones, see "Identifying Unlocated Phones" section.

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.

For information on creating off-premise ERLs, see the "Configuring Off-Premise ERL" section on page 6-10.

For information on assigning ERLs to IP subnets, see "Configuring IP Subnet-based ERLs" section.

For information on assigning ERLs to unlocated phones, see "Identifying Unlocated Phones" section.


Managing Cisco Emergency Responder Users

When you install Cisco ER 8.0, the system defines one default CERAdministrator user (see the "User Management" section for more information). You can also define additional users or modify existing users.

These topics describe how to add new users and how to modify and delete existing users:

Adding Users

Modifying Users

Deleting Users

Changing Users to Remote in Bulk

Adding Users

You can add additional users to the system and then assign them to user groups. The security levels for new users are determined by which user groups you assign them to.

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

You can add users to either the primary and standby servers within a single Cisco ER group. Since access is allowed based on the combination of the user groups defined on the two servers, a user that is defined only on the primary server will still be able to log into the backup server.

Before You Begin

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

To add users, follow these steps:


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


Procedure


Step 1 From the Cisco ER 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 CUCM 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. See the "Managing Cisco Emergency Responder User Groups" section for details.

Step 7 Repeat this procedure on the other Cisco ER server in the Cisco ER server group.


Note To remove a user from a group, you must remove the user from groups on both the primary and standby servers.


Modifying Users

Once you have created a user, you can:

Change the User's Authentication Mode

Change Password for Local User

Change CUCM Cluster for Remote User

Change the User's Authentication Mode

To change the users authentication mode, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User.

The Find and List Users page appears.

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

Step 3 Click on the user name.

Step 4 The User Configuration—Modify User page appears.

Step 5 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 CUCM Cluster from the drop down box.

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

Step 6 Click Update.


Change Password for Local User

To change the password for a local user, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management  >  User.

The Find and List Users page appears.

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

Step 3 Click on the user name.

Step 4 The Modify User page, used for user configuration, appears.

Step 5 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 6 Click Update.


Change CUCM Cluster for Remote User

In Cisco ER 8.0, you can also change the CUCM cluster of an exisitng remote user to another CUCM Cluster.

To change the CUCM cluster for remote user, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User.

The Find and List Users page appears.

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

Step 3 If you select Remote as the authentication mode, select a CUCM Cluster from the drop down box.

Step 4 The User Configuration—Modify User page appears.

Step 5 Select the new CUCM Cluster for all the remote users.

Step 6 Click Update


Deleting Users

Cisco ER 8.0 enables you to perform batch operation in which you can either delete a single user or delete multiple users in bulk.

To delete single user or multiple users in bulk, follow these steps:


Note You cannot delete the default administrative user created at the time of installing Cisco ER.


Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User.

The Find and List Users page appears.

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

Step 3 Find the user you want to delete and click the Delete icon for that user.

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

Similarly select multiple users from the list, both local and remote, by selecting the checkbox and then click 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 Topics

Logging Into and Out of Cisco Emergency Responder

Preparing Users for Cisco Emergency Responder, page 11-1

Changing Users to Remote in Bulk

Cisco ER 8.0 allows you to change the user to either local or remote. A remote user will be authenticated using the CUCM Cluster.


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


To change the users authentication mode, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User.

The Find and List Users page appears.

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

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 a CUCM 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 you wish to change by selecting the check box and then click the Change to Remote Users button. Select the CUCM cluster from the drop down box, as described in Step 6 above.


Managing Cisco Emergency Responder Roles

When you install Cisco ER 8.0, the system defines six default roles (see the "Role Management" section for more information on the default roles). You can also define additional roles or modify existing roles.

These topics describe how to add new roles and how to modify and delete existing roles:

Adding Roles

Modifying Roles

Deleting Roles

Adding Roles

You can add additional roles to the system and assign resources to them.


Note The default roles cannot be removed or modified.


Before You Begin

Before you begin, you should decide what additional roles you want to create and determine if any existing default role meets your needs.

To add new roles, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > Roles.

The Find and List Roles page appears.

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, click 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 To verify that you successfully added the new role, go back to the User Management > Roles page and perform a role search. Enter search criteria to find the specific role you just created and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Verify that the new role is listed.


Modifying Roles

To modify existing roles, follow these steps:


Note You cannot modify default roles.


Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > Roles.

The Find and List Roles page appears.

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

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, click or unclick 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 To verify that you successfully modified the new role, go back to the User Management > Roles page and perform a role search. Enter search criteria to find the specific role you just modified and click Find, or click Find without any search criteria to display all configured roles. The search results appear. Click the role name and verify that the modified role information appears on the Role Configuration—Modify Role page.


Deleting Roles

To delete an existing role, follow these steps:


Note You cannot delete a default role.


Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > Roles.

The Find and List Roles page appears.

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

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 will be refreshed and the role will no longer be listed in the Role Names list.


Managing Cisco Emergency Responder User Groups

When you install Cisco ER 8.0, the system defines six default user groups (see the "User Group Management" section for more information on the default user groups). You can also define additional user groups or modify existing user groups.

These topics describe how to add new user groups and how to modify existing user groups:

Adding User Groups

Modifying User Groups

Deleting User Groups

Adding User Groups

You can add user groups to the system and assign users and roles to each new user group.

Before You Begin

Before you begin, you should decide what additional user groups you want to create and determine if any existing default user groups meets your needs.

To add new user groups, follow these steps:

Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User Group.

The Find and List User Groups page appears.

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 Click the check box to the left of the user name(s) to be added and click Add.

The User Name page closes and the added name(s) appears in the Add User to Group text box on User Group 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 Click the check box to the left of the role(s) to be added and click Add.

The Role Names page closes and the added role(s) appears in the Add Roles to Group text box on User Group Configuration page.


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


Modifying User Groups

To modify existing user groups, follow these steps:


Note You cannot modify default user groups.


Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User Group.

The Find and List User Groups page appears.

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

Step 3 Click the user group name.

The User Group Configuration—Modify User Group page appears.

Step 4 If desired, 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 "Adding User Groups" section.

To remove users, highlight the name of the user(s) 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 "Adding Roles" section.

To remove roles, highlight the name of the role(s) and click Remove Roles.

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

Step 8 To verify that you successfully modified the user group, go back to the User Management > User Group page and perform a search. Enter search criteria to find the specific user group you just modified and click Find, or click Find without any search criteria to display all configured user groups. The search results appear. Click the user group name and verify that the modified user group information appears on the User Group Configuration—Modify User Group page.


Deleting User Groups

To delete an existing user group, follow these steps:


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


Procedure


Step 1 From the Cisco ER Administration web interface, select User Management > User Group.

The Find and List User Groups page appears.

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

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


Logging Into and Out of Cisco Emergency Responder

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

Before You Begin

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

To log into Cisco ER, follow these steps:

Procedure


Step 1 From an Internet Explorer 6.0 / 7.0 browser, open this URL, where servername is the DNS name or IP address of the Cisco ER server: http://servername/ceradmin.

The browser opens the Cisco ER Server Administration page.

Step 2 Use the Navigation pulldown menu to select the website you wish to log into. The Cisco ER websites are as follows:

Cisco ER Serviceability

Cisco ER Administration

Cisco Unified OS Administration

Disaster Recovery System

Cisco ER User

Cisco ER Admin Utility

To open the Log-in page, click one of these links.

Step 3 Click Go.

The login screen for the selected website appears.

Step 4 Enter your user name and password, and click Login.

Cisco ER logs you into the selected website. Unless you log in as a system administrator, some commands in the menus may have lock icons. These locks indicate pages you cannot view because of your authorization level.

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



Note In Cisco ER 8.0 and above, the validation for Username is not case sensitive.


Related Topics

Managing Cisco Emergency Responder Users

Managing Cisco Emergency Responder Roles

Managing Cisco Emergency Responder User Groups

Preparing Users for Cisco Emergency Responder, page 11-1

Limiting the Number of Concurrent Sessions

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

Cisco ER 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 will be prevented, from logging in to Cisco ER and receive this an 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, added in Cisco ER.



Note This limit is imposed seperately for each CER website:
- Cisco ER Administration
- Cisco ER Serviceability
- Cisco ER User
- Cisco ER Admin Utility



Warning If a user logs in to a Cisco ER website and closes the browser without logging out, the session will remain 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 a Cisco ER server group.

To configure a Cisco ER server group, follow these steps:

Procedure


Step 1 Select System > Cisco ER Group Settings.

Cisco ER opens the Cisco ER Group Settings page.

Step 2 Select the Limit Concurrent Sessions check box. This 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 session, you want to impose on the Cisco ER user, from the Max. number of concurrent sessions drop down box.

Step 4 Click Update Settings button to apply the new change.



Note You can disable the maximum number of concurrent settings by going to System > Cisco ER Group Settings and deselect the Limit Concurrent Sessions check box.


Related Topics

Cisco ER Group Settings, page A-3

Configuring Servers and Server Groups

These topics describe how to configure Cisco ER servers and server groups, and the telephony connection between the Cisco ER groups and Cisco Unified CM:

Configuring a Cisco Emergency Responder Server Group

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

Configuring Cisco Emergency Responder Servers

Uploading the Cisco Emergency Responder License File

Identifying the Cisco Unified Communications Manager Clusters

Configuring a Cisco Emergency Responder Server Group

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

Consider placing the two servers in a group in separate physical locations not separated by a WAN link so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See the "Data Integrity and Reliability Considerations" section on page 1-16 for more information.

Before You Begin

You must have system administrator authority to configure a Cisco ER server group.

To configure a Cisco ER server group, follow these steps:

Procedure


Step 1 Select System > Cisco ER Group Settings.

Cisco ER opens the Cisco ER Group Settings page.

Step 2 Fill in the group settings, as described in the "Cisco ER Group Settings" section on page A-3. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:

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

SMTP Mail Server and Source Mail ID—If you want Cisco ER to send email alerts to your Cisco ER system administrator and/or onsite alert personnel (security), enter the IP address or DNS name of a mail server, and the name of an account on that server to use for sending email. If you configure email addresses for onsite alert personnel (see the "Identifying Security Personnel (Onsite Alert Personnel)" section), 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 Cisco ER 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 Cisco ER as a Cisco CallManager user

Enable Syslog and Syslog Server—If you are using CiscoWorks2000 as your network management software, you can configure Cisco ER to send log messages to the Syslog Collector. To use Syslog Collector, select Enable Syslog and enter the fully-qualified DNS name of the Syslog server.

Security end user web interface language—To display the Cisco ER User webpages in French (Canadian), select it in the drop-down box. The default language is English.

Step 3 When you are satisfied with your settings, click Update Settings.

Cisco ER creates the Cisco ER group.


Related Topics

Configuring Cisco Emergency Responder Servers

Cisco ER Group Settings, page A-3

Collecting Information from Syslog, page 12-31

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

You must configure the telephony settings to tell Cisco ER the phone numbers it should use for emergency calls and ELINs.

Before You Begin

You must have system administrator authority to configure the telephony settings.

Before you configure these settings, create the required route points and route patterns in Cisco Unified CM. See these topics for more information:

Creating the Emergency Call Route Points, page 4-5

Creating the Route Patterns for ELINs, page 4-10

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17

To configure telephony settings, follow these steps:

Procedure


Step 1 Select System > Telephony Settings.

Cisco ER opens the Telephony Settings page.

Step 2 Enter the telephony settings, as described in the "Telephony Settings" section on page A-5:

UDP Port Begin—The first UDP port Cisco ER can use for telephone calls. For example, 32000.

Inter Cisco ER Group Route Pattern—The route pattern that other Cisco ER groups will 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 Cisco ER primary server to use. For example, 711. You may change this number. See the "Modifying the Emergency Number" section.

Route Point for Standby Cisco ER Server—The route point you created for the Cisco ER standby server to use. For example, 912.

IP Type of Service (00-FF)—The value of the Type of Service (TOS) byte in the IP header. The default 0xB8 implies a TOS class of Priority Queue. It is recommended that this default value be used for Cisco ER.

Onsite Alert Prompt Repeat 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.


Modifying the Emergency Number

You can configure or modify the emergency number that was automatically set at installation time by entering the number in the Route Point for Primary Cisco ER Server field. Before you configure or change the emergency number, you must configure the new route point and associate it with the Cisco ER user in Cisco Unified CM.


Caution Modify the emergency number during off-peak hours.

To modify the emergency number, follow these steps:

Procedure


Step 1 Associate the new route point with the Cisco ER user in Cisco Unified CM. See "Creating a Cisco Emergency Responder Cisco Unified Communications Manager User" section on page 4-18.

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

Step 3 Click Update Settings.


Note Cisco ER can still support only one emergency number; once you change it, Cisco ER will start routing calls received at the new emergency number route point.



Related Topics

Telephony Settings, page A-5

Creating the Emergency Call Route Points, page 4-5

Creating the Route Patterns for ELINs, page 4-10

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications, page 4-17

Identifying the Cisco Unified Communications Manager Clusters

Configuring Cisco Emergency Responder Servers

After you create a Cisco ER group (see the "Configuring a Cisco Emergency Responder Server Group" section), you can use the Server Settings page to update Cisco ER server settings (for example, to change the server name or to change the trace and debug settings) and to delete servers.

Before You Begin

You must have system administrator authority to update or delete a Cisco ER server.

To configure Cisco ER servers, follow these steps:

Procedure


Step 1 Select System > Server Settings.

Cisco ER opens the Server Settings page.

Step 2 To change the server settings (Server Name or Debug Package List, or Trace Package List settings), select the server name in the left-hand Servers list. Cisco ER loads the server's settings into the edit boxes. Make your changes and click Update.

Step 3 To remove a server from the group, select the server and click Delete. If you are permanently removing the server from your network, ensure that you make any required changes to your telephony network so that calls are not misdirected or dropped.

Step 4 When you are satisfied with your settings, click Update.

Cisco ER saves your changes and displays them in the list of servers at the top of the page.


Related Topics

Installing Cisco Emergency Responder 8.0 on a New System, page 2-3

Configuring a Cisco Emergency Responder Server Group

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

Identifying the Cisco Unified Communications Manager Clusters

Server Settings for CERServerGroup, page A-7

Uploading the Cisco Emergency Responder License File

There are two options to upload a license file for the server group:

You can upload a valid server license file for the Publisher and a second server license file for the Subscriber in order to use Cisco ER 8.0.

You can also upload a license for a server group with node count of 2 instead of ordering seperate licenses for publisher and subscriber.

For more information, see the "Licenses for Cisco Emergency Responder 8.0" section on page 1-4.

You must have all server and user license files on hand before you begin this procedure.


Note If you are unsure about which license files you require, see the "Determining Your License Requirements" section on page 1-6.


Before You Begin

You must have system administrator authority to access the License Manager page.

To upload the Cisco ER license file, follow these steps:

Procedure


Step 1 From the Cisco ER Administration website, select System > License Manager.

Cisco ER opens the License Manager page. The details of the license for the server appear.

Step 2 Based on the server to which you will be uploading the license file, select the server name from the pulldown menu and click Upload License to upload the additional license file.

The Upload File page appears.

Step 3 Use the Browse button to navigate to the license file to be uploaded (which you received as an email attachment after registering your Cisco ER system on Cisco.com), highlight the file name, and click Open.

The name of the selected file appears in the Select file to be uploaded text box.

Step 4 Click Upload. Cisco ER uploads and installs the additional license file.



Note The License Manager page displays the following information:

Server license information for the server group.

Consolidated user license information (Publisher and Subscriber)


Related Topics

Licenses for Cisco Emergency Responder 8.0, page 1-4

License Manager, page A-9

Identifying the Cisco Unified Communications Manager Clusters

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

Cisco ER 8.0 provides three levels of CTI failover. To enable the three levels of CTI failover, enter an IP address or DNS name for the primary CTI Manager; the Backup CTI Manager 1; and the Backup CTI Manager 2.

Before You Begin

You must have system administrator or network administrator authority to identify the Cisco Unified CM clusters.

Every Cisco Unified CM server in the Cisco Unified CM cluster must be running SNMP services so that Cisco ER can obtain the required information from the server.

Before configuring these settings, create the required users and CTI ports. This information must be complete before Cisco ER tries to create a provider with the Cisco ER cluster. Cisco ER only registers the CTI ports and route points that are associated with the user when the provider is created. See these topics for more information:

Creating a Cisco Emergency Responder Cisco Unified Communications Manager User, page 4-18

Creating the Required CTI Ports, page 4-8

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

Procedure


Step 1 Select Phone Tracking > Cisco Unified Communications Manager Details.

Cisco Emergency Responder opens the Cisco Unified CM Details page.

Step 2 Enter the details for the Cisco Unified CM server:

Cisco Unified Communications Manager—The IP address or DNS name of the server. This server must be running Cisco Unified CM and SNMP services. Do not define more than one Cisco Unified CM server within the same Cisco Unified CM cluster in the Cisco ER 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 the "Creating a Cisco Emergency Responder Cisco Unified Communications Manager User" section on page 4-18 for more information.

CTI Manager Password—The user's 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 Cisco ER's use. See the "Creating the Required CTI Ports" section on page 4-8 for more information.

Number of Telephony Ports—The number of CTI ports in the sequence you created for Cisco ER's use.

Step 3 To establish secure JTAPI communications, do the following:

a. Click the Enable Secure Connection checkbox.

b. Enter the following required information:

TFTP Server IP Address

TFTP Server Port


Note The TFTP Server Port field is pre-populated with a default value. If in Cisco Unified 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 the "Configuring JTAPI Security" section on page 4-20 for details.


Step 4 Click Insert.

Cisco ER adds the Cisco Unified CM server to the list of servers. Repeat this procedure if you are supporting other Cisco Unified CM clusters with this Cisco ER group.



TipTo view or change a Cisco Unified CM server's settings, click the server in the list of servers. The settings are loaded into the edit boxes. To change a setting, edit it and click Update.

To remove a Cisco Unified CM server from the Cisco ER configuration, click it in the list of servers, then click Delete.


Related Topics

Cisco Unified Communications Manager Clusters, page A-40

Configuring the Cisco Emergency Responder Cluster and Cluster DB Host

To configure the Cisco ER cluster and the Cluster DB Host, follow these steps:

Procedure


Step 1 Identify the following:

All the Cisco ER groups participating in the Cisco ER cluster

One of the Cisco ER publishers as "Cluster DB Host"

A password that will be the same across the Cluster as "Cluster password"

Step 2 Using the Cisco ER 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 Cisco ER server group in the cluster.

Step 4 Restart Cisco ER services.


Note Cisco ER 8.0 server groups are able to communicate with Cisco ER 1.3 and Cisco ER 2.0 server groups in a Cisco ER cluster.



Related Topics

Update Cluster DB Host, page E-2

Updating the Cisco ER Cluster Database Host Details, page 10-2

Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder

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

To change the Cisco Unified CM cluster that is identified in Cisco ER to a different version, see the "Changing the Cisco Unified Communications Manager Version" section on page 10-1.

Working with Emergency Response Locations

An emergency response location (ERL) defines the area in which an emergency call is made. Security personnel and emergency response teams use ERL information to locate an emergency caller.


Note Cisco Unified CM 6.x introduces a new Do-Not-Disturb feature for IP phones. If this feature is enabled for phones identified as onsite security phones, emergency alerts from Cisco ER to those phones will not alert the onsite security personnel. It is important that the Do-Not-Disturb feature be disabled for phones used with the onsite alert feature.

Cisco Unified CM 7.x supports alerts to onsite security personnel from Cisco ER 8.0 on phones that have the Do-Not-Disturb feature enabled.


Cisco ER system administrators or ERL administrators can create and modify ERLs. These sections explain ERLs in greater detail and explain how to work with them in Cisco ER:

Understanding ERLs

Overview of ERL Management

Identifying Security Personnel (Onsite Alert Personnel)

Creating ERLs

Exporting ERL Information

Exporting ERL Information

Viewing the Audit Trail for an ERL

Understanding ERLs

An emergency response location (ERL) is a building, area within a building, or outside area (if you extend phone service outdoors) that is to be treated as a single location for emergency response purposes. All telephones within the ERL are treated as coming from the same location.

Thus, when someone makes an emergency call, the public safety answering point (PSAP) and your onsite alert (security) team are notified of the ERL. If the emergency requires locating the individual who placed the emergency call, the response teams will have to find the person within the ERL. You can include more specific information using the Phone Location field for individual switch ports. This level of detail is only available for automatically tracked phones, and only appears on the Web Alert screen for onsite alert personnel.

This is similar to the way emergency calls are handled for individual home users: emergency response teams know the house from which the call was placed, but have to search from room to room until they find the caller. The bigger the house, the longer the potential search. Likewise, the larger you make your ERLs, the longer it might take a response team to find an emergency caller.

The laws relating to size of ERLs can vary for different cities, states, and countries. You are responsible for learning your local statutes and developing ERLs that satisfy those statutes. Work with your telephone service provider; they can help you understand the laws. Ultimately, you will have to submit the automatic location information (ALI) for your ERLs to your service provider so that calls from your ERLs are routed to the appropriate PSAPs.

Here are some examples of possible ERLs:

You have a 25-story building, each floor has 10,000 square feet of office space. You might create 25 ERLs, one per floor. Better, you could divide each floor in half and create 50 ERLs, two per floor.

You have 5 buildings. Each building was a former home, and they are approximately 3000 square feet. You might create 5 ERLs, one per building, even though some of the buildings are multi-story.

You have a 5 story building, but the building is very large, so that each floor has 100,000 square feet of office space. You might create 20 ERLs per floor for a total of 100 ERLs, each ERL covering approximately 5,000 square feet.

You have a high concentration of telephones, and local standards require that an ERL have no more than 48 telephones. In this case, you will have to define zones based on telephone coverage, rather than on physical space. Try to create zones that are recognizable as a physical location, for example, BldJFloor5Row3.

Related Topics

Overview of ERL Management

Creating ERLs

Exporting ERL Information

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

What Happens When an Emergency Call Is Made, page 1-8

Overview of ERL Management

To establish a useful set of ERLs, consider following these steps:

1. Become familiar with local statutes on emergency call requirements. Local laws might have specific requirements or recommendations on the maximum size of an ERL (for example, no larger than 7,000 square feet).

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 you propose to use, because the ERL name will be one of the major data points they will use to locate the emergency caller.

Security personnel also can use these fields to help locate a caller:

The Location field in the ALI, which you can use to clarify ERL names, for example, by including the complete street address of the building. Although security can also view the ALI from the Cisco ER user interface, it takes a few extra steps to view the entire ALI, so including a complete address in the Location field can expedite response.

The Phone Location field associated to the switch port. You can use this field to fine-tune the location, for example, by specifying the office or cube number that the port serves.

4. Use Cisco ER to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition, you will assign personnel to each ERL. See the "Identifying Security Personnel (Onsite Alert Personnel)" section for more information.

5. Use Cisco ER to define the ERLs and their ALI. See the "Creating ERLs" section for more information.

6. Assign switch ports to the correct ERL and define the phone location for the port. See the "Configuring Switch Ports" section for more information. Someone with network administrator authority must first add the switches to the Cisco ER configuration before you can complete this task.

7. Define any phones that are not directly supported by Cisco ER. See the "Manually Defining a Phone" section, 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 the "Exporting ERL Information" section and the "Exporting ALI Information for Submission to Your Service Provider" section 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 re-export ALI data and submit it to your service provider.

Related Topics

Understanding ERLs

Understanding the ERL Administrator's Role, page 11-2

Identifying Security Personnel (Onsite Alert Personnel)

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

A web-based alert on the Cisco ER end-user interface.

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

A telephone call indicating that an emergency call was made.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

Collect information about all of your onsite alert personnel, including names, telephone numbers, and email addresses. Also, develop a unique identification name for each, if you do not already have one readily available (such as badge number).

To onsite security personnel, follow these steps:

Procedure


Step 1 Select ERL > Onsite Alert Settings.

Cisco ER opens the Onsite Alert Settings page.

Step 2 Enter the unique ID, name, telephone number, 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 will use this ID to assign the person to an ERL, so ensure that you use a naming strategy useful to you.

You can use an email-based paging address for the email address, so that onsite alert personnel receive a page rather than an email.

Step 3 Click Insert.

Cisco ER adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.



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


Related Topics

Onsite Alert Settings, page A-13

Creating ERLs

Creating ERLs

These sections describe how to create emergency response locations (ERLs):

Setting Up the Default ERL

Setting up ERLs for Non-PSAP Deployment

Setting Up an Individual ERL and Its Automatic Location Information (ALI)

Importing Several ERLs at Once

Setting Up the Default ERL

Cisco ER does not automatically assign new switch ports and unlocated phones to the Default emergency response location (ERL). New switch ports and unlocated phones are treated as "ERL not configured."

You must not configure the Default ERL to any of the Switch Ports, Unlocated Phones, Manually Configured Phones or IP Subnets. The Default ERL is used internally by Cisco ER only if no other ERL is configured for that phone.

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

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

You must first configure the required ELINs in Cisco Unified CM (see the "Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks" section on page 4-9).

To set up the default ERL, follow these steps:

Procedure


Step 1 Select ERL > Conventional ERL.

Cisco ER opens the Find Conventional ERL Data page.

Step 2 Click Configure Default ERL.

Cisco ER opens the ERL Information for Default window.

Step 3 Fill in the ERL Information for Default window. The "Add New ERL" section on page A-17 contains detailed explanations of each field.

Step 4 Click ALI Details.

Cisco ER opens the ALI Information window.

Step 5 Fill in the ALI Information window. The "ALI Information (for ERL Name)" section on page A-21 contains detailed explanations of each field.

When finished filling in the ALI, click Update ALI Info. Cisco ER saves your ALI. Click Close to close the window.

Step 6 Make the ERL Information for Default window the active window if it is not, and click Update.

Cisco ER saves the ERL and its ALI.

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 has been configured.


Related Topics

Conventional ERL, page A-15

Add New ERL, page A-17

ALI Information (for ERL Name), page A-21

Setting Up an Individual ERL and Its Automatic Location Information (ALI)

Understanding ERLs

Overview of ERL Management

Setting up ERLs for Non-PSAP Deployment

You may want to deploy Cisco ER for on-site alerts only. That is, instead of routing emergency calls to a public safety answering point (PSAP), you route emergency calls to a specified security phone.

There are two ways to set up non-PSAP deployments:

Configure Security IDs 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. Cisco ER then initiates a call to the configured security phone and plays prompts to alert security personnel to the emergency call.

To configure Security IDs only, follow these steps:

Procedure


Step 1 Identify the security personnel to be notified in case of an emergency call (see the "Identifying Security Personnel (Onsite Alert Personnel)" section).

For example, configure security A with directory number 1000.

Step 2 Add an ERL with no route pattern/ELIN but only with security IDs for that ERL (see the "Creating ERLs" section).

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 the "Configuring Switch Ports" section).

For example, associate switch ports of switch IP Y to ERL X.

All emergency calls from any phone connected to switch IP Y will use ERL X and ring on the security A directory number 1000.



Note If you use Layer 3 (IP) roaming for wireless IP phones and/or wireless phones register using their Wireless Access Point's IP address, then Cisco ER will not be able to automatically track movement of these phones. This is because Cisco ER uses the IP address of the phone to determine the phone's location. Do not use Layer 3 roaming if you need Cisco ER to automatically track movement of wireless phones in your network.


Configure Security IDs and Route/Translation 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. Cisco ER displays a popup warning message alerting you that this zone will not have an ELIN. The emergency call is routed using the route/translation pattern; If this fails, the default pattern is used. Cisco ER then initiates a call to the configured security phone and plays prompts to alert security personnel to the emergency call.


Note In this scenario, you must use a different route/translation pattern for each zone.


Setting Up an Individual ERL and Its Automatic Location Information (ALI)

This section explains how to define a single ERL. Because several ERLs often have similar information, see the "Importing Several ERLs at Once" section section for strategies for simplifying the definition of similar ERLs.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

To define a single ERL, follow these steps:

Procedure


Step 1 Select ERL > Conventional ERL.

Cisco ER opens the Find conventional ERLs page.

Step 2 Click Add New ERL.

Cisco ER opens the Add New ERL window.

Step 3 Fill in the Add New ERL window. The "Add New ERL" section on page A-17 contains detailed explanations of each field.

Step 4 Click the Add ALI button.

Cisco ER opens the ALI Information window.

Step 5 Fill in the ALI Information window. The "ALI Information (for ERL Name)" section on page A-21 contains detailed explanations of each field.

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.

Cisco ER saves the ERL and its ALI.

Step 7 Click Close to close the window.



TipTo create an ERL that is similar to an existing ERL, click Find to list the existing ERLs, then click copy for the similar ERL. Cisco ER creates a copy of some ERL and all ALI information, which you can modify for the new ERL.

You can create or update tags to simplify the ALI definition process. Navigate to the ALI Information window, and look for information about the location of the samplevalidate.txt file. The sample file explains how to set up tags. When you have created or updated the desired tags, select the tag name on the ALI Information window and the ALI fields are loaded with the settings associated with the tag.


Related Topics

Conventional ERL, page A-15

Add New ERL, page A-17

ALI Information (for ERL Name), page A-21

Importing Several ERLs at Once

Understanding ERLs

Overview of ERL Management

Importing Several ERLs at Once

Rather than defining ERLs one at a time, as described in the "Setting Up an Individual ERL and Its Automatic Location Information (ALI)" section, you can create a file that contains more than one ERL definition, and import these ERLs at the same time into your Cisco ER configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Cisco ER configuration using ERL data exported from Cisco ER.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

Prepare an import file. Cisco ER includes detailed information about the required file format on the Import ERL Data page. The page also includes the location in which you must place the file in order to import it.

You can import conventional, off-premise, or Intrado ERLs. The Import link in the upper-right corner in of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

For information on creating conventional ERLs, see the "Creating ERLs" section.

For information on creating Intrado ERLs, see the "Configuring Intrado ERLs" section on page 6-4.

For information on creating off-premise ERLs, see the "Configuring Off-Premise ERL" section on page 6-10.

Use the procedure below 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.

To import several ERLs at once, follow these steps:

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.

Cisco ER opens the Import ERL Data page.

Step 2 Select the format of your import file (csv or xml) from the pulldown menu.

Step 3 Click Upload to upload the file from your local machine. See the "Uploading a File" section for information on using the Upload utility.

Step 4 Select your import file.

Step 5 Click Import.

Cisco ER imports your ERL and associated ALI data, and displays the status of the import as it proceeds. The imported data overwrites existing conflicting data in the Cisco ER configuration.

Step 6 Click Close to close the Import ERL Data window.


Related Topics

Import ERL Data, page A-25

Setting Up an Individual ERL and Its Automatic Location Information (ALI)

Understanding ERLs

Overview of ERL Management

Converting ALI Data

Use the PS-ALI Converter tool to generate an ERL csv (Comma Separated Value) text file that can be accepted by the Cisco ER ERL. You must first upload an existing ALI file in NENA 2.0 format to Cisco ER before converting it.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

To convert ALI data, follow these steps:

Procedure


Step 1 Select Tools > PS-ALI Converter.

Cisco ER displays the PS-ALI Converter page.

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 "Uploading a File" section 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 located 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 Topics

Import ERL Data, page A-25

Setting Up an Individual ERL and Its Automatic Location Information (ALI)

Understanding ERLs

Overview of ERL Management

Configuring IP Subnet-based ERLs

In addition to supporting switch port-based ERLs, Cisco ER 7.0 supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco ER then routes the emergency calls based on the configured IP subnet and ERL associations.

This is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.


Note Be aware that subnet-based tracking covers only to the IP subnet level, not to the cubicle level.


Use IP subnet-based ERLs to locate and track 802.11b endpoints, such as Cisco Unified Wireless IP Phone 7920 devices and Cisco IP SoftPhones running on 802.11b. Cisco ER cannot locate or track 802.11b wireless endpoints to a Cisco Access Point. It is recommended that:

You configure a subnet-ERL for each access point.

You identify the switch port to which the access point is connected and you assign the 802.11b wireless endpoint to the subnet ERL that is configured for that access point.

Before You Begin

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

To configure IP subnet-based ERLs, follow these steps:

Procedure


Step 1 Select ERL Membership > IP Subnets and click the Add new IP Subnet link on the Find and List IP Subnets page.

Cisco ER opens the Configure IP Subnets page.

Step 2 At the Subnet ID field, enter the IP address of the subnet you want to define, for example,10.76.35.0.

Step 3 At the Subnet Mask field, enter the mask of the subnet 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 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 Topics

Find and List Synthetic Phones, page A-60

Add New Synthetic Phone, page A-60

Configuring Test ERLs

You can use Cisco Unified Operations Manager 2.01 to monitor the health and functionality of Cisco ER.

To use Cisco Unified Operations Manager with Cisco ER, you configure a test ERL 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, Cisco ER 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 Cisco ER testing must belong to one of the configured test ERLs. For phones used for test ERLs, you enter the MAC address or address range allotted for synthetic phones.

The following conditions apply to test ERLS:

Calls from synthetic phones will not be logged in Call History logs.

Web alerts will not be generated for emergency calls from synthetic phones.

Email alerts will not be generated for emergency calls from synthetic phones.

PS-ALI records for test ERLS will not be exported in NENA export files.


Tip You do not need to enter ALI data for test ERLs. Non-test ERLs must contain ALI data.


Before You Begin

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

To configure test ERLs, follow these steps:

Procedure


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 At the MAC Address field, enter the MAC address or the range of MAC addresses allotted for synthetic phone.

Enter the MAC address in this format:

xx-xx-xx-xx-xx-xx

or

xxxxxxxxxxxx

The synthetic MAC address must be within the following range:

00059a3b7700 - 0059a3b8aff

Step 7 At the ERL Name field, enter the test ERL that you want to assign to the synthetic phone. Select the configured test ERL from the drop-down list or type in a valid test ERL name.

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 Topics

Find and List Synthetic Phones, page A-60

Add New Synthetic Phone, page A-60

Exporting ERL Information

Use the Export ERL page to create ERL export files for your own use, for example, to back up or move an ERL configuration. You can export conventional, off-premise, or Intrado ERLs. The Export link in the upper-right corner in of the Find Conventional ERL Data Page, Find Off-Premises ERLs Data page, and the Find Intrado ERLs Data page.

For information on creating conventional ERLs, see the "Creating ERLs" section.

For information on creating Intrado ERLs, see the "Configuring Intrado ERLs" section on page 6-4.

For information on creating off-premise ERLs, see the "Configuring Off-Premise ERL" section on page 6-10.


Note Do not submit ERL export files to your service provider—they are not exported in a format your service provider can use.


For information on exporting ALI information, refer to the "Exporting ALI Information for Submission to Your Service Provider" section.

For information on how to reformat ALI data to be accepted by the ERL, see the "Exporting ALI Information for Submission to Your Service Provider" section.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.

To export ERL information, follow these steps:

Procedure


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

Cisco ER opens the Export ER Data window.

Step 2 Select the Export Format (csv or xml) from the pulldown menu.

Step 3 Enter the name of the file to be exported in the Enter Export File Name field.

Step 4 Click Export.

Cisco ER creates the export file, and tells you the location where the file was created and how many records were exported.

Step 5 Select the exported file from the pulldown menu and click Download to download it to your local machine.

Step 6 Click Close to close the Export ERL Data window.


Related Topics

Export ERL Data, page A-24

Understanding ERLs

Overview of ERL Management

Exporting ALI Information for Submission to Your Service Provider

Your service provider and their database provider need your automatic location information (ALI) so that emergency calls from your 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 the "Using the ALI Formatting Tool" chapter for information on sending ALI details to your service provider.

Before You Begin

You must log into Cisco ER with system administrator or ERL administrator authority.


Caution Ensure that you submit each ALI export file as you create it. The ALI export records include an indication that the record is either new or modified. If you do not submit an ALI export file, the subsequent file you submit might have incorrect status indications, which can result in your service provider rejecting some, or possibly all, of your submitted records.

To export ALI information for submission to your service provider, follow these steps:

Procedure


Step 1 Select Tools > Export PS-ALI Records.

Cisco ER opens the Export PS-ALI Records page.

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.

Step 5 Cisco ER automatically increments the Cycle Counter each time you export data. You do not need to change this counter unless you are redoing or correcting a previous exportation. However, changing the sequence number does not affect the data placed in the file—if you are redoing an export, you will have to manually edit the export file to change the record status fields.

Step 6 Click Export.

Cisco ER creates the export file and tells you how many records were exported.

Step 7 Click Download to download the file to your local machine.

Step 8 Click Close to close the Export ALI Records window.

Step 9 Use your service provider's method of transmitting the file to the service provider.


Related Topics

ALI Information (for ERL Name), page A-21

Export ERL Data, page A-24

Export PS-ALI Records, page A-73

Understanding ERLs

Overview of ERL Management

Viewing the Audit Trail for an ERL

You can view the audit trail for an ERL to determine how, when, and by whom an ERL was created or changed.

Before You Begin

You must have system administrator, ERL administrator, or network administrator authority to view the audit trail.

To view the audit trail for an ERL, follow these steps:

Procedure


Step 1 Select Reports > ERL Audit Trail.

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

a. Select the field you want to search on, select the search relationship, and enter the search string. For some fields, you can select valid strings from the right-most drop-down list.

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

c. Click Find when you have entered all of the search criteria.

Cisco ER lists the matching audit records. If there are a lot of matches, Cisco ER uses several pages to display them. Use the links at the bottom of the list to change pages.



Tip To view the audit trail of a specific ERL, click View in the Audit Trail column in a list of ERLs shown on the Find and List ERLs page.


Related Topics

ERL Audit Trail, page A-71

Working with Emergency Response Locations

Configuring Switches for Cisco Emergency Responder

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

Understanding Switch Requirements for Cisco Emergency Responder

Configuring the SNMP Connection

Defining the Phone Tracking and Switch Update Schedules

Identifying the LAN Switches

Manually Running the Switch-Port and Phone Update Process

Understanding Switch Requirements for Cisco Emergency Responder

Cisco ER uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Cisco ER must use the Content Addressable Memory (CAM) table on the switch to track phones. Using the CAM table is less efficient than using CDP.

If some of the phones on your network do not use CDP, Cisco ER tracks them using the CAM table.

Ensure that the switches to which phones are attached are supported by Cisco ER, and that the switches are running the required software version. The "Network Hardware and Software Requirements" section on page 1-4 lists the supported switches and software versions.

If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Cisco ER cannot work with a switch unless the switch has an IP address.

Related Topics

Configuring the SNMP Connection

Defining the Phone Tracking and Switch Update Schedules

Identifying the LAN Switches

Manually Running the Switch-Port and Phone Update Process

Configuring the SNMP Connection

Cisco ER uses SNMP to obtain information about the ports on a switch. Cisco ER must obtain this port information so that you can assign the ports to ERLs, and so that Cisco ER can identify phones that are attached to the ports and update their ERL assignments.

Cisco ER only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.

Before You Begin

You must have system administrator or network administrator authority to define the SNMP settings.

Obtain the read community strings from all of the switches you will define in Cisco ER. If you use different strings for different sets of switches, see if you can define an IP address pattern for these sets. For example, if you use the same string for all switches that begin with 10.1, and another string for switches that begin with 10.2, you can use the patterns 10.1.*.* and 10.2.*.*.

If two or more patterns match an IP address, Cisco ER uses the SNMP string associated with the most closely matching pattern. For example, if you define *.*.*.* and 10.1.*.*, and the IP address is 10.1.12.24, Cisco ER uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.

When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Cisco Unified CM servers. Cisco ER must be able to make SNMP queries of all Cisco Unified CM servers in the cluster that it supports.

If your Cisco Emergency Responder servers, Cisco Unified CM servers, and Cisco IP Phones are located 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 *.*.*.*.

To configure the SNMP connection, follow these steps:

Procedure


Step 1 Select Phone Tracking > SNMP Settings.

Cisco ER 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 Cisco ER only tries to contact the switches you identify on the LAN Switch Details page (see the "Identifying the LAN Switches" section 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 will only need to create one entry.

If subsets of your switches use the same strings, create a mask that covers those subsets, if possible. For simplicity, try to create the fewest number of patterns.

If you use a separate string for each switch, you must enter each switch on this page.

Step 3 Enter the timeout and retries values. These values work together to determine how often and how long Cisco ER tries to obtain SNMP information from a switch before giving up. The first attempt lasts as long as the timeout value. If you enter 1 or higher for retries, Cisco ER tries again, and each retry lasts twice as long as the previous try. For example, if you specify 10 for timeout, the first retry lasts for 20 seconds, the second retry lasts for 40 seconds, and so forth.

The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.

Step 4 Enter the read community string, for example, public.

Step 5 Click Insert.

Cisco ER adds the SNMP setting to the list of settings.

Step 6 If you need to create more than one setting, return to Step 2.



TipWhenever you change the SNMP read community string on a switch, you must update the associated setting in Cisco ER.

To change an SNMP setting, select it in the list. Cisco ER loads the setting in the edit boxes. Make your changes and click Update. Then, run the switch-port and phone update process on the switch after you update the SNMP setting. Select Phone Tracking > LAN Switch Details, select the switch in the LAN Switches list, and then click Locate Switch Ports. If you are changing the setting for a large number of switches, run the process on all switches by selecting Phone Tracking > Run Switch-Port & Phone Update.

To delete a setting, click the delete icon on the setting's entry.


Related Topics

SNMP Settings, page A-37

Identifying the LAN Switches

Defining the Phone Tracking and Switch Update Schedules

To track phones successfully, Cisco ER must periodically contact switches to obtain port and device information. Cisco ER updates network information using two processes:

Phone Tracking—A periodic comparison of the phones registered with Cisco Unified CM to the location information obtained from the switches. If a phone moves, Cisco ER updates the phone's ERL. Phones that cannot be located are classified as unlocated phones (see the "Identifying Unlocated Phones" section).


Note If you do not configure a switch port phone update schedule, the default schedule will run at midnight.


Switch-Port and Phone Update—The phone tracking process plus a more extensive check of the network switches, which can identify new or changed switch modules (additional or removed ports). Any newly-discovered ports are assigned to the Default ERL. Ensure that your ERL administrator updates the ERL assignment for new ports.

Before You Begin

You must have system administrator or network administrator authority to define the schedule.

To define the phone tracking and switch update schedules, follow these steps:

Procedure


Step 1 Select Phone Tracking > Schedule.

Cisco ER opens the Schedule page.

Step 2 Enter the incremental phone tracking schedule in minutes and click Update.

Cisco ER will run the phone tracking process this number of minutes after finishing the previous phone tracking process.

Step 3 Enter the schedule for the switch-port and phone update process. You should run this process at least once per day (but not more than four times per day).

For example, if you want to run the process at midnight Monday through Friday, but at 6 PM on Saturday and Sunday, create two schedule entries:

Select Mon, Tue, Wed, Thu, and Fri, and 00 for Hour, 00 for Minute, then click Insert. Cisco ER adds the schedule to the list.

Select Sat and Sun, and 18 for Hour, 00 for Minute, then click Insert. Cisco ER adds the schedule to the list.

If you define schedules that overlap, Cisco ER only runs one process.



Note The Cisco ER Administrator must ensure that ccmPhoneStatusUpdateStorePeriod (CISCO-CCM-MIB) value in Cisco Unified CM must be set to a value greater than the Cisco ER incremental phone tracking interval, for tracking phone changes efficiently.



TipTo change a switch-port and phone update schedule, click the schedule in the list. Cisco ER 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 Topics

Phone Tracking Schedule, page A-38

Manually Running the Switch-Port and Phone Update Process

Identifying the LAN Switches

You must tell Cisco Emergency Responder (Cisco ER) which switches to manage. Cisco ER tracks port changes, including changes to the devices connected to those ports, and can recognize which ports have phones connected to them. Identify all switches that might have phones attached to them, essentially all edge switches.

Because Cisco ER must obtain information from the switches, you must ensure that the information you supply to Cisco ER is correct and kept up-to-date. After you have created the initial switch list, you can make mass changes to switch definitions by exporting the switch definitions, editing the export file, and reimporting the file.

These topics describe how to identify switches to Cisco ER, and how to export switch information:

Identifying LAN Switches One At a Time

Importing a Group of Switches

Exporting Switch Information

Identifying LAN Switches One At a Time

You can enter switches into the Cisco ER configuration one at a time. If you have a large number of switches to add, consider creating an import file to add them instead of using this procedure. See the "Importing a Group of Switches" section 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, Cisco ER must use the CAM information on the switch to identify phones. See the "Network Hardware and Software Requirements" section on page 1-4 for information on which phones require CAM access.

Ensure that you configure the SNMP read community strings before adding switches. See the "Configuring the SNMP Connection" section for more information.


Note CER will perform a full discovery scan for all the switches when you either reboot the Cisco ER server or while upgrading to a higher version. This process can be time consuming, depending on network size/ number of switches.
Always delete the LAN Switches from Cisco ER Administration > Phone Tracking > LAN Switch Details, if this has been removed from the network.


To identify LAN switches one at a time, follow these steps:

Procedure


Step 1 Select Phone Tracking > LAN Switch Details.

Cisco ER opens the LAN Switch Details page.

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 is configured on the switch in the locations field in Cisco ER, select Use port description as port location.

Step 3 Click Insert to add the switch to the Cisco ER configuration.

Cisco ER asks if you want to run the switch-port and phone update process. You must run this process so that Cisco ER can identify the ports on the switch and so that your ERL administrator can then assign the ports to the right ERLs.

If you are adding more than one switch, you can skip running the process until you add the last switch. When you select to run the process, Cisco ER runs the process on all switches added since the last time the switch-port and phone update process was run.

If you do not choose to run the process, you can run it later by selecting Phone Tracking > Run Switch-Port & Phone Update.

In either case, newly discovered ports are assigned to the Default ERL.



Note CER expects only one IP address/hostname per chassis and needs access to the following MIBs:
- mib-2
- IF-MIB
- CISCO-CDP-MIB
- ENTITY-MIB
- CISCO-VLAN-MEMBERSHIP-MIB
- BRIDGE-MIB*
- CISCO-STACK-MIB
- Mib-2
- interface
- CISCO-2900-MIB



TipClick a switch in the LAN Switches list to view the switch's Cisco ER configuration. To change the configuration, make your changes and click Update.

Click Add LAN Switch to add another switch if you are viewing an existing 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, Cisco ER will identify any phones connected to the switch as unlocated phones.


Related Topics

Importing a Group of Switches

Exporting Switch Information

LAN Switch Details, page A-42

Understanding Switch Requirements for Cisco Emergency Responder

Importing a Group of Switches

You can define a large number of switches at one time by importing a file that contains the required switch information. You might be able to create this file by exporting switch information from your network management software, and then using a spreadsheet program to modify the records to match the Cisco ER file format requirements (that is, by deleting columns, adding columns, rearranging columns, and so forth).

If you have a large network, importing switch definitions can save you a lot of time.

Before You Begin

You must have system administrator or network administrator authority to import switch definitions.

Prepare an import file. Cisco ER includes detailed information about the required file format on the Import LAN Switch page. The page also includes the location in which you must place the file in order to import it. Use the procedure below to go to the page and view the format, create your file, copy the file to the required location, and then follow the procedure to import the file.

Ensure that you configure the SNMP read community strings before adding switches. See the "Configuring the SNMP Connection" section for more information.

To import a group of switches, follow these steps:

Procedure


Step 1 Select Phone Tracking > LAN Switch Details.

Cisco ER opens the LAN Switch Details page.

Step 2 Click Import in the left-hand switch list.

Cisco ER opens the Import LAN Switch page.

Step 3 Select the file format, and the name of the file you want to import. Then, select one of these:

Override with imported data—Trust the data in the import file, and use it to overwrite conflicting data in the Cisco ER configuration. This is valuable if you are importing a file that you exported from Cisco ER and then updated. Using this technique, you can update many entries at once.

Leave current data—Trust the Cisco ER configuration, and do not overwrite configuration data with conflicting data from the import file. This is the default.

Step 4 Click Import.

Cisco ER asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Cisco ER imports the switches but does not run the phone tracking process.

After you make your selection, Cisco ER adds the switch configurations and shows you the status of the import.

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

Cisco ER 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. This runs the process only on the selected switch.


Related Topics

Identifying LAN Switches One At a Time

Exporting Switch Information

LAN Switch Details, page A-42

Understanding Switch Requirements for Cisco Emergency Responder

Exporting Switch Information

You can export your Cisco Emergency Responder (Cisco ER) configuration. This can help you back up your data, or help you create a file you can use to update a large number of switch definitions in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.

Before You Begin

You must have system administrator or network administrator authority to export switch definitions.

To export switch information, follow these steps:

Procedure


Step 1 Select Phone Tracking > LAN Switch Details.

Cisco ER opens the LAN Switch Details page.

Step 2 Click Export in the switch list.

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

Cisco ER creates the export file. Click Close to close the window.


Related Topics

Identifying LAN Switches One At a Time

Importing a Group of Switches

LAN Switch Details, page A-42

Understanding Switch Requirements for Cisco Emergency Responder

Manually Running the Switch-Port and Phone Update Process

Before you can assign ERLs to switch ports, Cisco ER must identify the ports on the switch using the switch-port and phone update process. Although Cisco ER runs this process according to the schedule you set (see the "Defining the Phone Tracking and Switch Update Schedules" section 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 Cisco ER-tracking results. Alternatively, if you are only trying to update the results for a limited number of switches, you can run phone tracking on individual switches. Select Phone Tracking > LAN Switch Details and select the switch in the left-hand column; then click Locate Switch Ports.

These are some reasons you would run phone tracking on an individual switch:

You add a switch to Cisco ER. When you add a switch, Cisco ER asks if you want to run the process. If you select to run it at that time, you do not have to click Locate Switch Ports—Cisco ER runs the process for all switches you added to the Cisco ER configuration since the last time the full switch-port and phone update process was run.

You add, remove, or change a module in a switch already defined to Cisco ER.

You can add and delete IP subnet-based ERLs.

Manually run the switch-port and phone update process as described below if:

You want to refresh the Cisco ER-tracking results.

You add switches to Cisco ER by importing switch definitions, as described in the "Importing a Group of Switches" section, but you did not run phone tracking during the importation.

If you find a large number of entries in the unlocated phones list (see the "Identifying Unlocated Phones" section), run this process to see if Cisco ER can find some of those phones. See the "Too Many Unlocated Phones" section on page 12-2 for issues you should address to help resolve these problems before running the switch-port and phone update process.

Before You Begin

You must have system administrator or network administrator authority to manually run the switch-port and phone update process.

To manually run the switch-port and phone update process, follow these steps:

Procedure


Step 1 Select Phone Tracking > Run Switch-Port & Phone Update.

Cisco ER runs the process without changing the page you are viewing. Any newly-discovered ports are assigned to the Default ERL.


Related Topics

Defining the Phone Tracking and Switch Update Schedules

Identifying Unlocated Phones

Understanding Switch Requirements for Cisco Emergency Responder

Tracking Change of Switch IP Address Dynamically

Cisco ER 8.0 allows you to dynamically track the change in a LAN switch IP address managed by Cisco ER. This feature is intended for LAN switches that have been added using the switch hostname.

To dynamically track a LAN switch IP address, follow these steps:

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.

Cisco ER opens the Cisco ER 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 Cisco ER will detect the new IP address of the LAN switch and update its database. You will be notified of this change detection via an entry in the Cisco ER Event Viewer and also via an administrative email alert.



Note It is recommended that you enable Dynamic Tracking of Switch IP Address only during a scheduled maintainence 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, Cisco ER will be unable to 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 Topics

Cisco ER Group Settings, page A-3

Defining the Phone Tracking and Switch Update Schedules

Managing Phones

These topics describe how to assign switch ports and phones to the appropriate emergency response locations (ERLs), and how to view the history of emergency calls handled by Cisco ER:

Configuring Switch Ports

Identifying Unlocated Phones

Manually Defining a Phone

Viewing the Emergency Call History

Configuring Switch Ports

After the network administrator adds switches to the Cisco ER configuration, and runs the switch-port and phone update process, you can assign the switch ports to emergency response locations (ERLs). When you assign a port to an ERL, make sure that you assign the ERL based on the location of the device attached to the port, not the location of the port itself.

For example, your wiring closet is on Floor 1. Half of its ports serve Floor 1, the other half serve Floor 2. Also, you have defined two ERLs, Floor1 and Floor2. Although the switch is on Floor 1, only half its ports belong in the Floor1 ERL; the other half belong in the Floor2 ERL.

Before you assign ports to ERLs, ensure you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments will only be reliable if this map is kept static, that is, so long as wires are not indiscriminately moved from port to port on the switch. Work with your network administrator to ensure the integrity of the wiring closet. See the "Data Integrity and Reliability Considerations" section on page 1-16 for more information.

These topics describe how to assign switch ports to ERLs:

Configuring a Few Switch Ports at a Time

Configuring a Large Number of Ports at Once

Exporting Switch Port Information

Switch-port Change Reporting for Wired Cisco Unified IP Phones

Configuring a Few Switch Ports at a Time

You can assign switch ports to ERLs a few at a time. If you have a large number of ports to map, it is much easier to create an import file to add them instead of using this procedure. See the "Configuring a Large Number of Ports at Once" section for more information.

Before You Begin

You must have system administrator or ERL administrator authority to assign ports to ERLs.

You can only configure ports defined for the Cisco ER group to which you are logged in.

To configure switch ports, follow these steps:

Procedure


Step 1 Select ERL Membership  >  Switch Ports .

Cisco ER opens the Switch Port Details page.

Step 2 Enter search criteria to list the ports you want to configure.

Find will display 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 will display 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. Cisco ER 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 Cisco ER group you want to search. If your initial search does not list the ports you are looking for, it might be because the ports are managed by a different Cisco ER group. You can only search one Cisco ER group at a time.


Note Cisco ER remembers the previous search criteria for the login session.


Step 3 Assign ports to ERLs:

a. Check the checkbox 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 checkbox 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.

b. Select the ERL you want to assign to the ports.

c. Optionally, enter more specific location information in the Phone Location field. Click view to open a window so that you can enter information. For example, you could enter the cubical or office number that the port serves. This information is sent to the onsite alert (security) personnel to help them locate the emergency caller. You can only update the phone location information if you are logged into the primary Cisco ER server in the Cisco ER group.

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

e. Enter the ERL Search Parameters and click Find. The search results appear.

f. Click the radio button next to the ERL you want to assign to the switch port(s) and click Select ERL. The Find ERL page close.

g. Click Assign ERL.

Cisco ER assigns the ERL to the selected ports. You can continue assigning ports on this page of the ports list, but do not change the search results page before completing these steps.

Cisco ER commits your ERL assignments. From here, you can continue to the another page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.



TipClick 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 Cisco ER server. Back up this data regularly. See the "Backing Up and Recovering Data" section on page 12-31.


Related Topics

Switch Port Details, page A-46

Import Switch Ports, page A-49

Configuring a Large Number of Ports at Once

Exporting Switch Port Information

Working with Emergency Response Locations

Configuring a Large Number of Ports at Once

You can assign a large number of ports to ERLs at one time by importing a file that contains the required information.

If you have a large network, importing port-to-ERL mappings can save you a lot of time.

Before You Begin

You must have system administrator or ERL administrator authority to import switch port definitions.

Prepare an import file. The easiest way to create this file is to first export the switch port details from Cisco ER (see the "Exporting Switch Port Information" section), and then use a spreadsheet program to change the ERL to the desired ERL and add phone location information. Ensure that the switch-port and phone update process is run before creating the export file, so that the file includes records for every switch port.

Before you import the file, you must copy it to the location identified on the Import Switch Port page. The procedure below explains how to get to this page. Links on the page also will display the detailed information about the required file format for the import file if you need it.

Cisco ER must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Cisco ER.

You can only configure ports defined for the Cisco ER group to which you are logged in.

To configure a large number of ports at once, follow these steps:

Procedure


Step 1 Select ERL Membership > Switch Ports .

Cisco ER opens the Switch Port Details page.

Step 2 Click Import.

Cisco ER opens the Import Switch Ports page.

Step 3 Select the format of your import file (csv) from the pulldown menu.

Step 4 Click Upload to upload the file from your local machine. See the "Uploading a File" section for information on using the Upload utility.

Step 5 Select your import file using the Select File to Import pulldown menu.

Step 6 Click Import.

Cisco ER imports the file and shows you the import results. The ERL-to-port mappings and port location information in the import file overwrite any existing data in the Cisco ER configuration.

Step 7 Click Close to close the Import Switch Port page.


Related Topics

Switch Port Details, page A-46

Export Switch Ports, page A-48

Configuring a Few Switch Ports at a Time

Exporting Switch Port Information

Working with Emergency Response Locations

Exporting Switch Port Information

You can export your Cisco ER port configuration. This can help you back up your data, or help you create a file you can use to update a large number of switch port mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.

Before You Begin

You must have system administrator or ERL administrator authority to export switch port definitions.

To export switch port information, follow these steps:

Procedure


Step 1 Select ERL Membership > Switch Ports .

Cisco ER opens the Switch Port Details page.

Step 2 Click Export.

Cisco ER opens the Export Switch Ports page.

Step 3 Select the file format and enter the desired file name, and click Export.

Cisco ER 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 pulldown menu and click Download.

Step 5 Click Close to close the Export Switch Port page.


Related Topics

Switch Port Details, page A-46

Configuring a Few Switch Ports at a Time

Configuring a Large Number of Ports at Once

Working with Emergency Response Locations

Switch-port Change Reporting for Wired Cisco Unified IP Phones

Cisco ER detects changes in the switch-port association of wired Cisco Unified IP Phones. An incremental or full discovery cycle detects Cisco Unified IP Phones that have changed switch-port associations or are newly discovered. Cisco Unified IP Phones that become missing during a complete discovery are also reported. Cisco ER notifies the system administrator of these changes by email.


Note A missing Cisco Unified IP Phone is one that is registered in Cisco Unified Communications Manager but is not found behind a switch port of any switch tracked by Cisco ER. Cisco Unified IP Phones that appear on the Unlocated Phones page in Cisco ER Administration web interface are also included in the missing list. Switch-port Change Reporting reports the location changes for Cisco Unified IP Communicator when it is connected to a switch that is tracked by Cisco ER.


The change notification email contains the following information:

The time at which the change was detected. This is the approximate completion time of the discovery cycle that detected the change.

The previous switch IP and port number of the Cisco Unified IP Phone. If the Cisco Unified IP Phone is new, this field is blank.

The current switch IP and port number of the Cisco Unified IP Phone. If the Cisco Unified IP Phone is missing, this field is blank.

The details of the Cisco Unified IP Phone, including the MAC address, device name, Phone Type, IP address and IP phone extension(s).


Note Configure the email client settings to allow line breaks in the email to improve readability. For more information on configuring the email client, see the "Configuring a Cisco Emergency Responder Server Group" section.


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 Cisco Unified CM. The only exception for this rule is Cisco Unified IP Phones previously registered in Cisco 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, Cisco ER performs change detection and notification on the active Cisco ER server only.

Feature Activation—The change detection and notification feature requires manual activation.

To activate the feature change detection and notification, follow these steps:

Procedure


Step 1 Select System > Mail Alert Configurations.

The Email Alert Settings page appears.

Step 2 In the Misc parameters section, use the pulldown menu to set the Switch Port location change reporting parameter to True.

Step 3 Click Update Settings.


Change Notification conditions—Cisco ER sends change notification email when a full discovery cycle completes under any of these circumstances:

During a normally scheduled discovery.

After a manual start from the Cisco ER Administrator web interface.

As a result of a Cisco Unified 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.

As a result of a LAN switch addition to Cisco ER; the system administrator starts the discovery process.

As a result of the system administrator selecting the Locate Switch Ports button on the LAN switch details page.


Note An incremental discovery does not locate missing Cisco Unified IP Phones from Cisco Unified 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 CERServer starts following the first discovery cycle.

When a Publisher returns to an online state following the first discovery cycle.

When no phone location changes occur following a discovery cycle.

Identifying Unlocated Phones

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

These are some things that can prevent Cisco ER from locating a phone:

The phone is attached to a switch that is not defined in Cisco ER.

The phone is connected to an unsupported device, such as a router port, a hub connected to a router, or an unsupported switch.

The switch to which the phone is connected is currently unreachable, for example, it does not respond to SNMP queries.

The phone has moved to a switch served by a different Cisco ER group. If this is the case, the Cisco ER group name is shown for the phone in the unlocated phones list.

No IP subnet is configured for the phone.

Because Cisco ER cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing Cisco ER from locating these phones on your network. If you cannot resolve the problems by defining switches in Cisco ER, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See the "Too Many Unlocated Phones" section on page 12-2 for more detailed information on resolving these problems.

In addition, Cisco ER 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.

To identify unlocated phones, follow these steps:

Procedure


Step 1 Select ERL Membership > Unlocated Phones.

Cisco ER opens the Unlocated Phones page.

Step 2 Enter search criteria to list the unlocated phones.

Step 3 Check the checkbox next to the phone that you want to assign an ERL.

Step 4 To select the ERL you want to assign to the selected phone, 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 you want to assign to the unlocated phone(s) and click Select ERL. The Find ERL page close.

Step 7 Click Assign ERL button.

Cisco ER assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Cisco ER from locating this phone, Cisco ER removes it from the list and assigns it the correct ERL based on port assignment.


Note To unassign a ERL, select the phone(s) and click on Unassign ERL button.




TipYou can select all the phones on the displayed page by selecting the check box in the list title.

You can only assign phones to ERLs on a single page at a time. If there is more than one page of phones, use the links at the bottom of the list to move from page to page.



Note Cisco ER does not automatically discover analog phones or phones connected to PBXs. As a result, these phones do not appear on the Unlocated Phones list. These phones need to be manually configured. See the "Manually Defining a Phone" section for more information.


Related Topics

IP Subnet Phones, page A-52

Configuring Switch Ports

Manually Defining a Phone

Manually Defining a Phone

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

You need to manually define a phone if any of these conditions apply:

Cisco ER does not support automatic tracking of that type of phone, for example, if the phone is analog.

The phone is hosted on an unsupported port, such as a router port, a hub connected to a router, or a port on an unsupported switch.

No IP subnet is configured for the phone.

For any phones you must manually define, you should regularly audit the location of those phones to determine if you need to update the ERL assignment for the phone in Cisco ER.


Note New switch ports and unlocated phones will NOT be associated to Default ERLs automatically. They will be treated as "ERL not configured." The Default ERL is used only internally by Cisco ER if no other ERL is configured for that phone. Cisco ER will not allow the Default ERL to be configured to Switch Ports; Unlocated Phones; Manually Configured Phones; or IP Subnets.



Note You cannot manually add a phone that is used with Cisco Unified CM Extension Mobility. With Cisco 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 Cisco 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.

To define a phone manually, follow these steps:

Procedure


Step 1 Select ERL Membership > Manually Configured Phones .

Cisco ER opens a new page, the Find and List Manually Configured Phones page.

Step 2 To search for phones that you need to modify, enter the extension and click Find. Cisco ER performs a search and displays the results of your search.

From the search result on the Find and List Manually Configured Phones page, you can remove a phone, change an existing phone or add a new phone:

Step 3 To remove a phone, click the delete icon on the phone's entry.

Step 4 To change an existing phone:

a. Click the phone's entry in the list. Cisco ER opens the Add/Modify Phones page with the phone's information displayed in the edit boxes.

b. Make your changes and click Update. Cisco ER updates the phone.

c. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.

Step 5 To add a new phone:

a. Click Add New Manual Phone. Cisco ER opens the Add New Manual Phone page.

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

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

d. Enter the ERL Search Parameters and click Find. The search results appear.

e. Click the radio button next to the ERL you want to assign to the manual phone and click Select ERL. The Find ERL page close.

f. Click Insert. Cisco ER adds the phone to the list of manually defined phones.

g. Click Back to Phone Search to return to the Find and List Manually Configured Phones page.


Related Topics

Add New Manual Phone, page A-57

Identifying Unlocated Phones

Network Hardware and Software Requirements, page 1-4

Assigning a Large Number of Manually Configured Phones to ERLs at Once

Exporting Manually Configured Phone Information

Assigning a Large Number of Manually Configured Phones to ERLs at Once

You can assign a large number of manually configured phones to ERLs at one time by importing a file that contains the required information.

If you have a large network, importing manually-configured phone to ERL mappings can save you a lot of time.

Before You Begin

You must have system administrator or ERL administrator authority to import switch port definitions.

Prepare an import file. The easiest way to create this file is to first export the manually configured phone details from Cisco ER (see the "Exporting Manually Configured Phone Information" section), and then use a spreadsheet program to change the ERL to the desired ERL and add phone location information. Ensure that the manual phone configuration and phone update process is run before creating the export file, so that the file includes records for every manually configured phone.

Before you import the file, you must copy it to the location identified on the Import Manual Phones page. The procedure below explains how to get to this page. Links on the page also will display the detailed information about the required file format for the import file if you need it.

Cisco ER must already be aware of the manually configured phones before you import the file. Ensure that all manually configured phones you are importing have been located by Cisco ER.

You can only configure manually configured phones defined for the Cisco ER group to which you are logged in.

To assign a large number of manually-configured phones to ERLs at one time, follow these steps:

Procedure


Step 1 Select ERL Membership > Manually Configured Phones.

The Find and List Manually Configured Phones page appears.

Step 2 Click Import.

The Import Manually Configured Phones page appears.

Step 3 Select the Import Format (csv) using the pulldown menu.

Step 4 Click Upload to upload the file from your local machine. See the "Uploading a File" section for information on using the Upload utility.

Step 5 Select the import file using the Select File to Import pulldown menu.

Step 6 Click Import.

Cisco ER imports the file and shows you the import results. The ERL-to-port mappings and the location information for manually configured phones in the import file overwrite any existing data in the Cisco ER configuration.

Step 7 Click Close to close the Import Manually Configured Phone page.


Related Topics

Switch Port Details, page A-46

Export Switch Ports, page A-48

Configuring a Few Switch Ports at a Time

Exporting Switch Port Information

Working with Emergency Response Locations

Exporting Manually Configured Phone Information

You can export your Cisco ER manually configured phone configuration. This can help you back up your data, or help you create a file you can use to update a large number of manually configured phone mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.

Before You Begin

You must have system administrator or ERL administrator authority to export switch port definitions.

To export information about manually configured phones, follow these steps:

Procedure


Step 1 Select ERL Membership > Manually Configured Phones.

Cisco ER opens the Find and List Manually Configured Phones page.

Step 2 Click Export.

Cisco ER opens the Export Manual Phones page.

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.

Cisco ER 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 Topics

Manually Defining a Phone

Assigning a Large Number of Manually Configured Phones to ERLs at Once

Working with Emergency Response Locations

Adding Synthetic Phones

Adding Synthetic Phones

With Cisco ER 7.0, you can use Cisco Unified Operations Manager 1.0 to monitor the health and functionality of Cisco ER. To use Cisco Unified Operations Manager with Cisco ER, you configure a synthetic phone in Cisco ER and associate the synthetic phone to an ERL that will be used as a test ERL. When a synthetic phone makes an emergency call, Cisco ER uses the associated test ERL to route the call.


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, refer to the "Configuring Test ERLs" section.

Viewing the Emergency Call History

You can view the history of emergency calls made in your network that are handled by Cisco ER. Cisco ER sends emergency call notifications to the onsite alert personnel you identify in your ERLs, and these people react to the notifications. From the administrator's interface, you can view the same call history your onsite alert personnel can view, and see the comments they make about the calls. You might need to review the call history to report on usage or to troubleshoot call routing problems.


Tip From the Call History page, you can view detailed information on the 10,000 most recent calls. You can find records of older calls in Cisco ER's raw call log files. See the "Collecting Call History Logs" section on page 12-27 for more information.


To view the emergency call history, follow these steps:

Procedure


Step 1 Select Reports > Call History.

Cisco ER opens the Call History page.

Step 2 Click Find.

All call summary information appears.

Step 3 Enter the search criteria you want to use to create a list of emergency calls.

To view a list of all calls, click Find without entering any search criteria.

To narrow your search, select the item you on which you want to search, and click Find. For example, you can view calls that were made in a specific ERL, or calls that were made from a specific phone extension. If you want to search on more than one criteria, click More to add additional search fields. Then, select All at the top of the list to perform an AND search (a call only matches the search if each of the criteria is met), or Any for an OR search (a call matches the search if it matches one or more of the criteria).

Step 4 From the list of calls that Cisco ER shows you in response to your search criteria, you can:

View the call characteristics.

Click on the ERL name to view the ERL details. From the ERL details, you can also view the ALI for the call.

Click edit in the comment field to change the comment. Cisco ER opens a separate window where you make your editorial changes.



Tip If a large number of calls match your search criteria, Cisco ER uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.


Related Topics

Collecting Call History Logs, page 12-27