|
|
Table Of Contents
Configuring Cisco Emergency Responder 2.0
Overview of Cisco Emergency Responder Configuration
Cisco Emergency Responder Website Interfaces
Using the Upload and Download Utilities
Cisco Emergency Responder 2.0 Configuration Task Checklist
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 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
Identifying Security Personnel (Onsite Alert Personnel)
Configuring IP Subnet-based ERLs
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
Manually Running the Switch-Port and Phone Update Process
Viewing the Emergency Call History
Configuring Cisco Emergency Responder 2.0
After you install Cisco Emergency Responder (Cisco ER) and configure Cisco Unified Communications Manager, you can configure Cisco ER so that it begins managing emergency calls.
These topics describe how to configure Cisco Emergency Responder 2.0:
•
Overview of Cisco Emergency Responder Configuration
•
•
•
•
•
•
•
•
•
Overview of Cisco Emergency Responder Configuration
Cisco ER 2.0 provides several new features, including expanded administrative website interfaces, role-based user management, and upload/download utilities.
These topics provide an overview of configuring the Cisco ER:
•
•
•
Cisco Emergency Responder Website Interfaces
Cisco ER 2.0 provides several websites from which you can access and use different parts of the system. From the main Cisco ER 2.0 web page, you can access the following areas:
•
•
•
•
•
•
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 2.0 system is first installed, a default CERAdministrator user is created. The default CERAdministrator has full access to all websites except the Cisco Unified OS Administration and Disaster Recovery System websites, and has the ability to create users, roles, and user groups. The default CERAdministrator cannot be deleted from the system.
Related Topics
•
•
•
Role-Based User Management
Cisco ER 2.0 uses a role-based user management mechanism. The following topics describe this mechanism:
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
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
•
•
Role Management
On installation, the system creates six default roles. Table 5-1 lists and describes the default roles.
Note
When creating a new role or modifying an existing role, you specify which system resources will be assigned to the role. A resource is the same thing as a web page or a menu item within the Cisco ER 2.0 administration website. For example, the Find and List Roles web page is a resource, as is the User Management > Role menu item.
Table 5-2 shows the resources that are available to each default role.
Note
Related Topics
•
•
User Group Management
On installation, the system creates six default user groups. Table 5-3 lists and describes the default user groups.
Note
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
•
•
Using the Upload and Download Utilities
Cisco ER 2.0 includes download and upload utilities that allow you to transfer bulk data in the form of csv files from a Cisco ER server to a local system (download) and from a local system to a Cisco ER server (upload).
For example, you can export database details to a csv file and then download the csv file to a local system. On the local system, you can modify the csv file, upload it the Cisco ER server, and import the data in the csv file into the Cisco ER database.
Table 5-4 lists the Cisco ER administrative web pages from which you can use the upload and download utilities and gives the navigation path to each page.
Note
Downloading a File
To download a file from a Cisco ER 2.0 server to a local system, follow these steps:
Procedure
Step 1
Step 2
Step 3
Uploading a File
To upload a file from a local system to a Cisco ER 2.0 server, follow these steps:
Before You Begin
Before beginning the procedure, make sure the file to be uploaded exists on your local system. The file can be one that was previously downloaded from a Cisco ER 2.0 server, or one that you created.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Related Topics
•
•
•
•
•
Cisco Emergency Responder 2.0 Configuration Task Checklist
This checklist provides information on the tasks that need to be completed to configure Cisco ER and indicates which user types can complete the tasks, with pointers to more detailed information.
Note
Table 5-5 Configuration Task Checklist
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 Communications Manager clusters whose emergency calls this Cisco ER group will handle.
Note
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.
Identify the switches and configure the connection to them.
Enter the SNMP read community strings.
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.
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.
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
See the "Configuring Switch Ports" section.
Add phones that Cisco ER does not directly support.
Note
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.
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.
Managing Cisco Emergency Responder Users
When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines one default CERAdministrator user (see the "User Management" section 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
You can add additional users to the system and then assign them to user groups. The security levels for new users are determined by which user groups you assign them to.
You can add users to either the primary and standby servers within a single Cisco ER group. Since access is allowed based on the combination of the user groups defined on the two servers, a user that is defined only on the primary server will still be able to log into the backup server.
Before You Begin
Develop a list of users for each security level. You need to know the user names of all onsite alert personnel, and you should determine who should have access to each of the administration security levels.
To add users, follow these steps:
Note
Procedure
Step 1
The Find and List Users page appears.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Note
Modifying Users
Once you have created a user, you can modify the user's password.
To modify the user's password, follow these steps:
Procedure
Step 1
The Find and List Users page appears.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Deleting Users
To delete a user, follow these steps:
Note
Procedure
Step 1
The Find and List Users page appears.
Step 2
Step 3
The system displays a warning prompting you to confirm the deletion.
Step 4
Related Topics
•
•
Managing Cisco Emergency Responder Roles
When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines six default roles (see the "Role Management" section 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
You can add additional roles to the system and assign resources to them.
Note
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
The Find and List Roles page appears.
Step 2
The Role Configuration page appears.
Step 3
Step 4
Step 5
Step 6
Modifying Roles
To modify existing roles, follow these steps:
Note
Procedure
Step 1
The Find and List Roles page appears.
Step 2
Step 3
The Role Configuration—Modify Role page appears.
Step 4
Step 5
Step 6
Step 7
Deleting Roles
To delete an existing role, follow these steps:
Note
Procedure
Step 1
The Find and List Roles page appears.
Step 2
Step 3
A warning message displays asking you to verify that you want to delete the role.
Step 4
The Find and List Roles page will be refreshed and the role will no longer be listed in the Role Names list.
Managing Cisco Emergency Responder User Groups
When you install Cisco Emergency Responder (Cisco ER) 2.0, the system defines six default user groups (see the "User Group Management" section 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
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
The Find and List User Groups page appears.
Step 2
The User Group Configuration—Add User Group page appears.
Step 3
Step 4
The User Names page appears.
Step 5
Step 6
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
Step 7
The Role Names page appears.
Step 8
Step 9
The Role Names page closes and the added role(s) appears in the Add Roles to Group text box on User Group Configuration page.
Note
Step 10
Modifying User Groups
To modify existing user groups, follow these steps:
Note
Procedure
Step 1
The Find and List User Groups page appears.
Step 2
Step 3
The User Group Configuration—Modify User Group page appears.
Step 4
Step 5
To remove users, highlight the name of the user(s) and click Remove Users.
Step 6
To remove roles, highlight the name of the role(s) and click Remove Roles.
Step 7
Step 8
Deleting User Groups
To delete an existing user group, follow these steps:
Note
Procedure
Step 1
The Find and List User Groups page appears.
Step 2
Step 3
Note
A warning message appears asking you to verify that you want to delete the user group.
Step 4
The Find and List Roles page will be refreshed and the deleted user group will no longer be listed in the User Groups list.
Logging Into and Out of Cisco Emergency Responder
You must log into the Cisco Emergency Responder (Cisco ER) web interfaces to view or change the system configuration. The system administrator controls access using the Role-Based User Management mechanism. See the "Role-Based User Management" section 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
The browser opens the Cisco ER Server Administration page.
Step 2
•
•
•
•
•
•
To open the Log-in page, click one of these links.
Step 3
The login screen for the selected website appears.
Step 4
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.
Related Topics
•
•
•
•
Configuring Servers and Server Groups
These topics describe how to configure Cisco Emergency Responder (Cisco ER) servers and server groups, and the telephony connection between the Cisco ER groups and Cisco Unified Communications Manager:
•
•
•
•
•
Configuring a Cisco Emergency Responder Server Group
To configure a Cisco Emergency Responder (Cisco ER) server group, you must connect to the administration interface on one of the servers that will be part of the group. A Cisco ER server group consists of up to two Cisco ER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Cisco ER remains available in case one server becomes disabled.
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 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
Cisco ER opens the Cisco ER Group Settings page.
Step 2
•
•
•
•
Step 3
Cisco ER creates the Cisco ER group.
Related Topics
•
•
•
Configuring Group Telephony Settings For the Cisco Emergency Responder Server
You must configure the telephony settings to tell Cisco Emergency Responder (Cisco ER) the phone numbers it should use for emergency calls and ELINs.
Before You Begin
You must have system administrator authority to configure the telephony settings.
Before you configure these settings, create the required route points and route patterns in Cisco Unified Communications Manager. See these topics for more information:
•
•
•
To configure telephony settings, follow these steps:
Procedure
Step 1
Cisco ER opens the Telephony Settings page.
Step 2
•
•
•
•
•
•
•
•
Step 3
Modifying the Emergency Number
You can configure or modify the emergency number that was automatically set at installation time by entering the number in the Route Point for Primary Cisco ER Server field. Before you configure or change the emergency number, you must configure the new route point and associate it with the Cisco ER user in Cisco Unified Communications Manager.
Caution
To modify the emergency number, follow these steps:
Procedure
Step 1
Step 2
Step 3
Note
Related Topics
•
•
•
•
•
Configuring Cisco Emergency Responder Servers
After you create a Cisco Emergency Responder (Cisco ER) group (see the "Configuring a Cisco Emergency Responder Server Group" section), 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
Cisco ER opens the Server Settings page.
Step 2
Step 3
Step 4
Cisco ER saves your changes and displays them in the list of servers at the top of the page.
Related Topics
•
•
•
•
•
Uploading the Cisco Emergency Responder License File
You must upload a valid server license file for the Publisher and a second server license file for the Subscriber in order to use Cisco Emergency Responder (Cisco ER) 2.0. Each server license file also provides for 100 users. For all users over the 200 provided for by the server licenses, you must order and upload additional user licenses. For more information, see the "Licenses for Cisco Emergency Responder 2.0" section.
You must have all server and user license files on hand before you begin this procedure.
Note
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
Cisco ER opens the License Manager page. The details of the license for the server appear.
Step 2
The Upload File page appears.
Step 3
The name of the selected file appears in the Select file to be uploaded text box.
Step 4
Note
•
•
Related Topics
•
Identifying the Cisco Unified Communications Manager Clusters
You must identify one Cisco Unified Communications Manager server per Cisco Unified Communications Manager cluster that you want to manage with the Cisco ER group you are configuring. Cisco ER gets the list of phones registered with these Cisco Unified Communications Manager servers and tracks the movements of these phones
Cisco ER 2.0 provides three levels of CTI failover. To enable the three levels of CTI failover, enter an IP address or DNS name for the primary CTI Manager; the Backup CTI Manager 1; and the Backup CTI Manager 2.
Before You Begin
You must have system administrator or network administrator authority to identify the Cisco Unified Communications Manager clusters.
Every Cisco Unified Communications Manager server in the Cisco Unified Communications Manager cluster must be running SNMP services so that Cisco ER can obtain the required information from the server.
Before configuring these settings, create the required users and CTI ports. This information must be complete before Cisco ER tries to create a provider with the Cisco ER cluster. Cisco ER only registers the CTI ports and route points that are associated with the user when the provider is created. See these topics for more information:
•
•
To identify one Cisco Unified Communications Manager server per Cisco Unified Communications Manager cluster that you want to manage with the Cisco ER group you are configuring, follow these steps:
Procedure
Step 1
Cisco Emergency Responder opens the Cisco Unified Communications Manager Details page.
Step 2
•
•
•
•
•
•
•
•
Step 3
a.
b.
–
–
Note
–
–
Note
–
–
–
–
Note
Step 4
Cisco ER adds the Cisco Unified Communications Manager server to the list of servers. Repeat this procedure if you are supporting other Cisco Unified Communications Manager clusters with this Cisco ER group.
Tip
•
Related Topics
•
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
•
•
•
Step 2
Step 3
Step 4
Note
Related Topics
•
•
Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder
If you change or upgrade the Cisco Unified Communications Manager cluster identified in Cisco Emergency Responder (Cisco ER) to a later version, you must use the Admin Utility to identify Cisco ER with the later Cisco Unified Communications Manager version.
Note
To change or upgrade the Cisco Unified Communications Manager cluster identified in Cisco ER to a later version, see the "Changing the Cisco Unified Communications Manager Version" section.
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 Emergency Responder (Cisco ER) system administrators or ERL administrators can create and modify ERLs. These sections explain ERLs in greater detail and explain how to work with them in Cisco ER:
•
•
Understanding ERLs
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:
•
•
•
•
Related Topics
•
•
Overview of ERL Management
To establish a useful set of ERLs, consider following these steps:
1.
2.
3.
Security personnel also can use these fields to help locate a caller:
–
–
4.
5.
6.
7.
8.
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
9.
–
–
–
–
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
•
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:
•
•
•
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
Cisco ER opens the Onsite Alert Settings page.
Step 2
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
Cisco ER adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.
Tip
•
Related Topics
•
Creating ERLs
These sections describe how to create emergency response locations (ERLs):
•
•
•
Setting Up the Default ERL
Cisco Emergency Responder (Cisco ER) does not automatically assign new switch ports and unlocated phones to the Default emergency response location (ERL). New switch ports and unlocated phones are treated as "ERL not configured."
You must not configure the Default ERL to any of the Switch Ports, Unlocated Phones, Manually Configured Phones or IP Subnets. The Default ERL is used internally by Cisco ER only if no other ERL is configured for that phone.
Cisco ER also uses the Default ERL for all emergency calls when the Cisco ER server is first started (or restarted when there is no standby Cisco ER server) until the initial switch port update is finished. (This process is started immediately.)
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority.
You must first configure the required ELINs in Cisco Unified Communications Manager (see the "Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks" section).
To set up the default ERL, follow these steps:
Procedure
Step 1
Cisco ER opens the Find and List ERLs page.
Step 2
Cisco ER opens the ERL Information for Default window.
Step 3
Step 4
Cisco ER opens the ALI Information window.
Step 5
When finished filling in the ALI, click Update ALI Info. Cisco ER saves your ALI. Click Close to close the window.
Step 6
Cisco ER saves the ERL and its ALI.
Step 7
Tip
Related Topics
•
•
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
For example, configure security A with directory number 1000.
Step 2
For example, add ERL X with security A.
Step 3
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
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
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 Emergency Responder (Cisco ER) with system administrator or ERL administrator authority.
To define a single ERL, follow these steps:
Procedure
Step 1
Cisco ER opens the Find and List ERLs page.
Step 2
Cisco ER opens the Add New ERL window.
Step 3
Step 4
Cisco ER opens the ALI Information window.
Step 5
When finished filling in the ALI, click Save and Close.
Step 6
Cisco ER saves the ERL and its ALI.
Step 7
Tip
•
Related Topics
•
•
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 Emergency Responder (Cisco ER) configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Cisco ER configuration using ERL data exported from Cisco ER.
Before You Begin
You must log into Cisco ER with system administrator or ERL administrator authority.
Prepare an import file. Cisco ER includes detailed information about the required file format on the Import ERL Data page. The page also includes the location in which you must place the file in order to import it. Use the procedure below to go to the page and view the format, create or update your file, copy the file to the required location, and then follow the procedure to import the file.
To import several ERLs at once, follow these steps:
Procedure
Step 1
Cisco ER opens the Find and List ERLs page.
Step 2
Cisco ER opens the Import ERL Data page.
Step 3
Step 4
Step 5
Step 6
Cisco ER imports your ERL and associated ALI data, and displays the status of the import as it proceeds. The imported data overwrites existing conflicting data in the Cisco ER configuration.
Step 7
Related Topics
•
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
Cisco ER displays the PS-ALI Converter page.
Step 2
Step 3
Step 4
Step 5
Step 6
The generated csv file is located in the following folder:
%cerroot%/importYou can import the file or download the file using the File Manager utility.
Step 7
Step 8
Related Topics
•
Configuring IP Subnet-based ERLs
In addition to supporting switch port-based ERLs, Cisco Emergency Responder (Cisco ER) 2.0 supports IP subnet-based (Layer 3) ERLs. You can configure IP subnets and assign ERLs to the configured IP subnets; Cisco ER then routes the emergency calls based on the configured IP subnet and ERL associations.
This is useful in environments where strict IP addressing rules are followed and cubicle-level location is not required, such as configurations with wireless phones.
Note
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:
•
•
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
Cisco ER opens the Configure IP Subnets page.
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
A popup message requests that you force a switch port update. You can do this after all the IP subnets have been added.
Step 8
Step 9
Related Topics
•
•
Configuring Test ERLs
You can use Cisco Unified Operations Manager 2.01 to monitor the health and functionality of Cisco ER.
To use Cisco Unified Operations Manager with Cisco ER, you configure a test ERL, then add a synthetic phone and associate the synthetic phone to the test ERL. When a synthetic phone makes an emergency call, Cisco ER uses the associated test ERL to route the call.
Note
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:
•
•
•
•
Tip
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
Step 2
Step 3
Note
Note
Step 4
Step 5
Step 6
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
Step 8
Step 9
Related Topics
•
•
Exporting ERL Information
Use the Export ERL page to create ERL export files for your own use, for example, to back up or move an ERL configuration. Do not submit ERL export files to your service 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
Cisco ER opens the Find and List ERLs page.
Step 2
Cisco ER opens the Export ER Data window.
Step 3
Step 4
Step 5
Cisco ER creates the export file, and tells you the location where the file was created and how many records were exported.
Step 6
Step 7
Related Topics
Exporting ALI Information for Submission to Your Service Provider
Your service provider and their database provider need your automatic location information (ALI) so that emergency calls from your ERLs can be routed to the correct public safety answering point (PSAP). The PSAP can also use this information to dispatch emergency response teams (such as police, fire, medical) to deal with the emergency. As you create and update your ERLs and their ALIs, make sure that you export the data and send it to your service provider or the database provider they identify.
See the "Using the ALI Formatting Tool" chapter for information on sending ALI details to your service provider.
Before You Begin
You must log into Cisco Emergency Responder (Cisco ER) with system administrator or ERL administrator authority.
Caution
To export ALI information for submission to your service provider, follow these steps:
Procedure
Step 1
Cisco ER opens the Export PS-ALI Records page.
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco ER creates the export file and tells you how many records were exported.
Step 7
Step 8
Step 9
Related Topics
•
•
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
Cisco Emergency Responder (Cisco ER) opens the ERL Audit Trail page.
Step 2
To view all ERLs, click Find without entering any criteria.
To narrow your search:
a.
b.
c.
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
Related Topics
•
Configuring Switches for Cisco Emergency Responder
Before you can assign switch ports to ERLs, you must identify the switches used in your network to Cisco Emergency Responder (Cisco ER). These topics describe the switch requirements and how to identify switches to Cisco ER.
•
•
•
•
•
Understanding Switch Requirements for Cisco Emergency Responder
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 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
Cisco Emergency Responder (Cisco ER) uses SNMP to obtain information about the ports on a switch. Cisco ER must obtain this port information so that you can assign the ports to ERLs, and so that Cisco ER can identify phones that are attached to the ports and update their ERL assignments.
Cisco ER only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.
Before You Begin
You must have system administrator or network administrator authority to define the SNMP settings.
Obtain the read community strings from all of the switches you will define in Cisco ER. If you use different strings for different sets of switches, see if you can define an IP address pattern for these sets. For example, if you use the same string for all switches that begin with 10.1, and another string for switches that begin with 10.2, you can use the patterns 10.1.*.* and 10.2.*.*.
If two or more patterns match an IP address, Cisco ER uses the SNMP string associated with the most closely matching pattern. For example, if you define *.*.*.* and 10.1.*.*, and the IP address is 10.1.12.24, Cisco ER uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.
When you configure the SNMP strings for your switches, you must also configure the SNMP strings for your Cisco Unified Communications Manager servers. Cisco ER must be able to make SNMP queries of all Cisco Unified Communications Manager servers in the cluster that it supports.
To configure the SNMP connection, follow these steps:
Procedure
Step 1
Cisco ER opens the SNMP Settings page.
Step 2
•
•
•
Step 3
The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.
Step 4
Step 5
Cisco ER adds the SNMP setting to the list of settings.
Step 6
Tip
•
•
Related Topics
•
Defining the Phone Tracking and Switch Update Schedules
To track phones successfully, Cisco Emergency Responder (Cisco ER) must periodically contact switches to obtain port and device information. Cisco ER updates network information using two processes:
•
Note
•
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
Cisco ER opens the Schedule page.
Step 2
Cisco ER will run the phone tracking process this number of minutes after finishing the previous phone tracking process.
Step 3
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:
•
•
If you define schedules that overlap, Cisco ER only runs one process.
Tip
•
Related Topics
•
•
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
You can enter switches into the Cisco Emergency Responder (Cisco ER) configuration one at a time. If you have a large number of switches to add, consider creating an import file to add them instead of using this procedure. See the "Importing a Group of Switches" section 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 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.
To identify LAN switches one at a time, follow these steps:
Procedure
Step 1
Cisco ER opens the LAN Switch Details page.
Step 2
•
•
Step 3
Cisco ER asks if you want to run the switch-port and phone update process. You must run this process so that Cisco ER can identify the ports on the switch and so that your ERL administrator can then assign the ports to the right ERLs.
If you are adding more than one switch, you can skip running the process until you add the last switch. When you select to run the process, Cisco ER runs the process on all switches added since the last time the switch-port and phone update process was run.
If you do not choose to run the process, you can run it later by selecting Phone Tracking > Run Switch-Port & Phone Update.
In either case, newly discovered ports are assigned to the Default ERL.
Tip
•
•
Related Topics
•
•
•
•
Importing a Group of Switches
You can define a large number of switches at one time by importing a file that contains the required switch information. You might be able to create this file by exporting switch information from your network management software, and then using a spreadsheet program to modify the records to match the Cisco Emergency Responder (Cisco ER) file format requirements (that is, by deleting columns, adding columns, rearranging columns, and so forth).
If you have a large network, importing switch definitions can save you a lot of time.
Before You Begin
You must have system administrator or network administrator authority to import switch definitions.
Prepare an import file. Cisco ER includes detailed information about the required file format on the Import LAN Switch page. The page also includes the location in which you must place the file in order to import it. Use the procedure below to go to the page and view the format, create your file, copy the file to the required location, and then follow the procedure to import the file.
Ensure that you configure the SNMP read community strings before adding switches. See the "Configuring the SNMP Connection" section for more information.
To import a group of switches, follow these steps:
Procedure
Step 1
Cisco ER opens the LAN Switch Details page.
Step 2
Cisco ER opens the Import LAN Switch page.
Step 3
•
•
Step 4
Cisco ER asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Cisco ER imports the switches but does not run the phone tracking process.
After you make your selection, Cisco ER adds the switch configurations and shows you the status of the import.
Step 5
Step 6
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
•
•
•
•
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
Cisco ER opens the LAN Switch Details page.
Step 2
Cisco ER opens the Export LAN Switch page.
Step 3
Step 4
Cisco ER creates the export file. Click Close to close the window.
Related Topics
•
•
•
•
Manually Running the Switch-Port and Phone Update Process
Before you can assign ERLs to switch ports, Cisco Emergency Responder (Cisco ER) must identify the ports on the switch using the switch-port and phone update process. Although Cisco ER runs this process according to the schedule you set (see the "Defining the Phone Tracking and Switch Update Schedules" section 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:
•
•
•
Manually run the switch-port and phone update process as described below if:
•
•
•
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
Cisco ER runs the process without changing the page you are viewing. Any newly-discovered ports are assigned to the Default ERL.
Related Topics
•
•
•
Managing Phones
These topics describe how to assign switch ports and phones to the appropriate emergency response locations (ERLs), and how to view the history of emergency calls handled by Cisco Emergency Responder (Cisco ER):
•
•
Configuring Switch Ports
After the network administrator adds switches to the Cisco Emergency Responder (Cisco ER) configuration, and runs the switch-port and phone update process, you can assign the switch ports to emergency response locations (ERLs). When you assign a port to an ERL, make sure that you assign the ERL based on the location of the device attached to the port, not the location of the port itself.
For example, your wiring closet is on Floor 1. Half of its ports serve Floor 1, the other half serve Floor 2. Also, you have defined two ERLs, Floor1 and Floor2. Although the switch is on Floor 1, only half its ports belong in the Floor1 ERL; the other half belong in the Floor2 ERL.
Before you assign ports to ERLs, ensure you have a reliable mapping of switch ports to their end points (for example, cubicle numbers or office numbers). Your assignments will only be reliable if this map is kept static, that is, so long as wires are not indiscriminately moved from port to port on the switch. Work with your network administrator to ensure the integrity of the wiring closet. See the "Data Integrity and Reliability Considerations" section for more information.
These topics describe how to assign switch ports to ERLs:
•
•
•
•
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 Emergency Responder (Cisco ER) group to which you are logged in.
To configure a few switch ports at a time, follow these steps:
Procedure
Step 1
Cisco ER opens the Switch Port Details page. This page has two tabs, Find and Configure. Before you can configure a port, you must list it in the bottom frame using the Find tab.
Step 2
•
•
•
•
Step 3
Cisco ER opens the Configure tab.
Step 4
a.
b.
c.
d.
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.
e.
Cisco ER commits your ERL assignments. From here, you can continue to the another page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.
Tip
•
Related Topics
•
•
•
•
•
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
Cisco ER opens the Switch Port Details page.
Step 2
Cisco ER opens the Import Switch Ports page.
Step 3
Step 4
Step 5
Step 6
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
Related Topics
•
•
•
•
•
Exporting Switch Port Information
You can export your Cisco Emergency Responder (Cisco ER) port configuration. This can help you back up your data, or help you create a file you can use to update a large number of switch port mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.
Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.
To export switch port information, follow these steps:
Procedure
Step 1
Cisco ER opens the Switch Port Details page.
Step 2
Cisco ER opens the Export Switch Ports page.
Step 3
Cisco ER exports the file to the export location.
Step 4
Step 5
Related Topics
•
•
•
•
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
The change notification email contains the following information:
•
•
•
•
Note
Supported Cisco Unified IP Phones—This feature supports only wired Cisco Unified IP Phones that meet both of these conditions:
•
•
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
The Email Alert Settings page appears.
Step 2
Step 3
Change Notification conditions—Cisco ER sends change notification email when a full discovery cycle completes under any of these circumstances:
•
•
•
Similarly, a partial discovery cycle sends email notifications under these circumstances:
•
•
•
Note
The following events do not result in a change notification:
•
•
•
Identifying Unlocated Phones
If Cisco Emergency Responder (Cisco ER) cannot locate a phone, it places the phone in the Default ERL and puts it in a list of unlocated phones. Using this list, you can reassign the phones to a different ERL, or you can use the list to help identify the problems that are preventing Cisco ER from locating the phones.
These are some things that can prevent Cisco ER from locating a phone:
•
•
•
•
•
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 for more detailed information on resolving these problems.
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
Cisco ER opens the Unlocated Phones page and lists all unlocated phones.
Step 2
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.
Tip
•
Note
Related Topics
Manually Defining a Phone
To manage all emergency calls in your network, Cisco Emergency Responder (Cisco ER) must know about every phone whose calls are routed by Cisco Unified Communications Manager, even if Cisco ER does not directly support the phone. Cisco ER handles emergency calls from these manually-defined phones in the same way it handles calls from phones attached to supported switch ports. The only difference is that Cisco ER cannot dynamically change the ERL of a manually-defined phone if that phone is moved.
You need to manually define a phone if any of these conditions apply:
•
•
•
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
Note
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
Cisco ER opens a new page, the Find and List Manually Configured Phones page.
Step 2
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
Step 4
a.
b.
c.
Step 5
a.
b.
c.
d.
Related Topics
•
•
•
•
•
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
The Find and List Manually Configured Phones page appears.
Step 2
The Import Manually Configured Phones page appears.
Step 3
Step 4
Step 5
Step 6
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
Related Topics
•
•
•
•
•
Exporting Manually Configured Phone Information
You can export your Cisco Emergency Responder (Cisco ER) manually configured phone configuration. This can help you back up your data, or help you create a file you can use to update a large number of manually configured phone mappings in Cisco ER. You can edit the export file, make your changes, then reimport the file and overwrite the information in Cisco ER.
Before You Begin
You must have system administrator or ERL administrator authority to export switch port definitions.
To export information about manually configured phones, follow these steps:
Procedure
Step 1
Cisco ER opens the Find and List Manually Configured Phones page.
Step 2
Cisco ER opens the Export Manual Phones page.
Step 3
Step 4
Cisco ER exports the file to the export location.
Step 5
Step 6
Related Topics
•
•
Adding Synthetic Phones
With Cisco Emergency Responder (Cisco ER) 2.0, you can use Cisco Unified Operations Manager 1.0 to monitor the health and functionality of Cisco ER. To use Cisco Unified Operations Manager with Cisco ER, you configure a synthetic phone in Cisco ER and associate the synthetic phone to an ERL that will be used as a test ERL. When a synthetic phone makes an emergency call, Cisco ER uses the associated test ERL to route the call.
For more information, refer to the "Configuring Test ERLs" section.
Viewing the Emergency Call History
You can view the history of emergency calls made in your network that are handled by Cisco Emergency Responder (Cisco ER). Cisco ER sends emergency call notifications to the onsite alert personnel you identify in your ERLs, and these people react to the notifications. From the 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
To view the emergency call history, follow these steps:
Procedure
Step 1
Cisco ER opens the Call History page.
Step 2
All call summary information appears.
Step 3
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
•
•
•
Tip
Related Topics
Posted: Fri Jun 8 00:12:08 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
