|
|
These topics describe how to configure Emergency Responder:
After you install Emergency Responder and configure Cisco CallManager, you can configure Emergency Responder so that it begins managing emergency calls. Because using Emergency Responder requires different skill sets, you can set up different users to configure different aspects of the product. The "Creating Emergency Responder Users" section describes the user models Emergency Responder can accommodate.
This is an overview of the steps you need to complete to configure Emergency Responder, and indicates which user types can complete the tasks, with pointers to more detailed information. Some steps can be done in parallel.
Step 2 System administrator—Create and configure the CER groups:
a. Create the CER group. See the "Configuring a CER Server Group" section.
b. Configure the CER group's telephony settings. See the "Configuring CER Server Group Telephony Settings" section.
c. Add CER servers to the CER group. See the "Configuring CER Servers" section.
d. Enter the product license key. See the "Entering the Emergency Responder License Key" section.
e. Identify and configure the Cisco CallManager clusters whose emergency calls this CER group will handle. The network administrator can also perform this step. See the "Identifying the Cisco CallManager Clusters" section.
Step 3 Network Administrator—Identify the switches and configure the connection to them:
a. Enter the SNMP read community strings. See the "Configuring the SNMP Connection" section.
b. Define the schedule Emergency Responder should use for updating information from the switches. See the "Defining the Phone Tracking and Switch Update Schedules" section.
c. Identify the switches that can have phones connected to them. See the "Identifying the LAN Switches" section.
d. Run the switch-port and phone update process so that Emergency Responder can identify the ports on the switches and whether phones are attached to them. See the "Manually Running the Switch-Port and Phone Update Process" section.
Step 4 ERL Administrator—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.
a. Identify the onsite alert (security) personnel that should receive alerts from Emergency Responder. See the "Identifying Security Personnel (Onsite Alert Personnel)" section.
b. Create the ERLs. See the "Creating ERLs" section.
c. Assign the ERLs to switch ports. 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.
d. Add phones that Emergency Responder does not directly support. Emergency Responder does not automatically track the movement of these phones. See the "Manually Defining a Phone" section.
e. Identify the unlocated phones and work with the network administrator to resolve problems that are preventing Emergency Responder from locating these phones. Assign ERLs to the phones that remain. See the "Identifying Unlocated Phones" section.
f. Export the ALI and transmit it to your service provider. Work with your service provider to determine transmission requirements. See the "Exporting ERL and ALI Information for Submission to Your Service Provider" section.
Step 5 All administrators—Review these sections to understand your recurring tasks for Emergency Responder:
Before you can log into Emergency Responder, you must add users to the Emergency Responder groups. These groups are created during Emergency Responder installation, and are local to the Emergency Responder server.
There are four groups, which correspond to four user security levels:
You should include the same people (user names and passwords) in each group on both the primary and standby servers within a single CER group. However, access is allowed based on the union of the user groups defined on the two servers. Thus, if a user is only defined in the group on the primary server, that user can still log into the backup server.
Develop a list of users for each security level, based on Windows user name. You need to know the user names of all security personnel, and you should determine who should have access to each of the administration security levels.
You can always add or remove users later using this procedure.
Read the online help for this interface if you have questions about its use.
Step 2 In the Tree view (left pane), select System Tools>Local Users and Groups>Groups.
Computer Management shows the available groups in the right pane.
Step 3 Double-click the group to which you want to add users.
Computer Management opens the properties for the group.
Step 4 Click Add on the properties window.
Computer Management opens the Select Users or Groups window.
Step 5 In the Select Users or Groups window, select the user you want to add. You can select the Windows domain where the user is defined at the top of the window. Then, double-click each name you want to add. The names are transferred to the bottom pane when you add them.
When you have selected all the names you want to add, click OK. The names are added to the group. Click OK on the properties page to close the window.
Step 6 Repeat Step 3 to Step 5 until you have added the desired users to each of the groups. At minimum, you need at least one member of the CERSystemAdmin group. You should also assign all security personnel to the CERUser group. Adding members to the other groups is optional; you only need to add members if you want to control administrative access to the product.
When finished, close Computer Management.
Step 7 Repeat this procedure on the other CER server in the CER group.
You must log into the Emergency Responder administrative interface to view or change the system configuration. Access is controlled by Windows local groups on the Emergency Responder server. See the "Creating Emergency Responder Users" section for an explanation of setting up these groups.
Your user ID must be added to the appropriate Windows group before you can log into Emergency Responder. Contact the main Emergency Responder administrator if you cannot log into the interface and you are supposed to have administrative access.
The browser opens the Cisco Emergency Responder Server Administration page.
Step 2 Click the link corresponding to the type of access you are allowed to have to the product:
Clicking one of these links opens the Log-in page.
Step 3 Enter your user name and password, and click Login.
Emergency Responder logs you into the product. Unless you log in as a system administrator, some commands in the menus will have lock icons. These locks indicate pages you cannot view because of your authorization level.
If another administrator is logged in, you are asked if you want to invalidate the session and log in.
When you are finished, click Logout in the menu bar to log out.
These topics describe how to configure CER servers and server groups, and the telephony connection between the CER groups and Cisco CallManager:
To configure a CER server group, you must connect to the administration interface on one of the servers that will be part of the group. A CER server group consists of up to two CER servers, a primary and a standby, or backup, server. This redundancy helps ensure that Emergency Responder remains available in case one server becomes disabled. The standby server also can handle calls if the primary server is too busy handling other calls or tracking phone movements.
Consider placing the two servers in a group in separate physical locations so that problems that might affect one server do not affect the other, such as a fire, flood, or network disruption. See the "Data Integrity and Reliability Considerations" section for more information.
You must have system administrator authority to configure a CER server group.
Emergency Responder opens the CER Group Settings page.
Step 2 Fill in the group settings, as described in the "CER Group Settings" section. Many fields have defaults that should work for most networks. At minimum, you must configure these fields:
Step 3 When you are satisfied with your settings, click Update Settings.
Emergency Responder creates the CER group.
You must configure the telephony settings to tell Emergency Responder the phone numbers it should use for emergency calls and ELINs.
You must have system administrator authority to configure the telephony settings.
Before you configure these settings, create the require route points and route patterns in Cisco CallManager. See these topics for more information:
Emergency Responder opens the Telephony Settings page.
Step 2 Enter the telephony settings, as described in the "Telephony Settings" section:
Step 3 Click Update Settings to save your changes.
After you create a CER group (see the "Configuring a CER Server Group" section), you can add CER servers to the group.
You should always add two servers to a CER server group. This ensures that the primary system has a backup system.
You must have system administrator authority to configure a CER server.
When you install the primary server and its standby, you must select the same Cisco CallManager server as the group database. Do not try to group CER servers that are using different Cisco CallManager server databases.
A group can have a maximum of two servers.
Emergency Responder opens the Server Settings page.
Step 2 Identify the server that will be the primary server for the group. Emergency Responder makes the first server you identify the primary server.
Step 3 When you are satisfied with your settings, click Insert.
Emergency Responder saves your changes and adds the server to the list of servers in the left-hand column.
Step 4 Identify the backup server. Click New if the primary server's settings are displayed in the edit boxes to open a clean page for entering the backup server's settings. Enter the backup server's information and click Insert.
You must enter a valid license key to use Emergency Responder.
You must have system administrator authority to enter the license key.
Emergency Responder opens the License Manager page. The license you have already configured appears in the left-hand list.
Step 2 Enter the license key you obtained with the product in the License Key field and click Insert.
Emergency Responder replaces the any existing key with the key you enter.
You must identify one Cisco CallManager server per Cisco CallManager cluster you want to manage with the CER group you are configuring. Emergency Responder gets the list of phones registered with these Cisco CallManager servers and tracks the movements of these phones.
You must have system administrator or network administrator authority to identify the Cisco CallManager clusters.
Every Cisco CallManager server in the Cisco CallManager cluster must be running SNMP services so that CER can obtain the required information from the server.
Before configuring these settings, create the required users and CTI ports. See these topics for more information:
Emergency Responder opens the Cisco CallManager Details page.
Step 2 Enter the details for the Cisco CallManager server:
Step 3 Click Insert.
Emergency Responder adds the Cisco CallManager server to the list of servers in the left-hand column. Repeat this procedure if you are supporting other Cisco CallManager clusters with this CER group.
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.
Emergency Responder 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 Emergency Responder:
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:
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:
4. Use Emergency Responder to enter information about your security (onsite alert) personnel. You should enter this information before defining the ERLs, because during ERL definition, you will assign personnel to each ERL. See the "Identifying Security Personnel (Onsite Alert Personnel)" section for more information.
5. Use Emergency Responder 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 Emergency Responder configuration before you can complete this task.
7. Define any phones that are not directly supported by Emergency Responder. 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 and 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:
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.
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:
You must log into Emergency Responder with system administrator or ERL administrator authority.
Collect information about all of your onsite alert personnel, including names, telephone numbers, and email addresses. Also, develop a unique identification name for each, if you do not already have one readily available (such as badge number).
Emergency Responder opens the Onsite Alert Settings page.
Step 2 Enter the unique ID, name, telephone number, and email address of a security or onsite alert person.
Unique ID might be a badge number, email name, or other site-specific unique name. You will use this ID to assign the person to an ERL, so ensure that you use a naming strategy useful to you.
You can use an email-based paging address for the email address, so that onsite alert personnel receive a page rather than an email.
Step 3 Click Insert.
Emergency Responder adds the person to the list of onsite personnel. Repeat until you define all security or onsite personnel.
These sections describe how to create emergency response locations (ERLs):
Emergency Responder automatically assigns new switch ports and unlocated phones to the Default emergency response location (ERL). Thus, your Default ERL should be broad enough to cover the site managed by the CER group. However, because this location definition will be too broad to be useful (unless your site is small and only requires one ERL), ensure that you update switch ports to assign them to more specific ERLs. Also, regularly check for unlocated phones to resolve whatever issues are preventing them from getting the proper ERL assignment.
You must log into Emergency Responder with system administrator or ERL administrator authority.
You must first configure the required ELINs in Cisco CallManager (see the "Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks" section).
Emergency Responder opens the ERL Configuration page.
Step 2 Click Configure Default ERL.
Emergency Responder opens the ERL Information for Default window.
Step 3 Fill in the ERL Information for Default window. The "Add New ERL; ERL Information" section contains detailed explanations of each field.
Step 4 Click ALI Details.
Emergency Responder opens the ALI Information window.
Step 5 Fill in the ALI Information window. The "ALI Information (for ERL)" section contains detailed explanations of each field.
When finished filling in the ALI, click Update ALI Info. Emergency Responder saves your ALI. Click Close to close the window.
Step 6 Make the ERL Information for Default window the active window if it is not, and click Update.
Emergency Responder saves the ERL and its ALI.
Step 7 Click Close to close the window.
This section explains how to define a single ERL. Because several ERLs often have similar information, see the Tips section for strategies for simplifying the definition of similar ERLs.
You must log into Emergency Responder with system administrator or ERL administrator authority.
Emergency Responder opens the ERL Configuration page.
Step 2 Click Add New ERL.
Emergency Responder opens the Add New ERL window.
Step 3 Fill in the Add New ERL window. The "Add New ERL; ERL Information" section contains detailed explanations of each field.
Step 4 Click ALI Details.
Emergency Responder opens the ALI Information window.
Step 5 Fill in the ALI Information window. The "ALI Information (for ERL)" section contains detailed explanations of each field.
When finished filling in the ALI, click Save ALI Info. Emergency Responder saves your ALI. Click Close to close the window.
Step 6 Make the Add New ERL window the active window if it is not, and click Insert.
Emergency Responder saves the ERL and its ALI.
Step 7 Click Close to close the window.
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 Emergency Responder configuration. This is especially useful if you already have ERL definitions set up in a spreadsheet, or if you are recovering an Emergency Responder configuration using ERL data exported from Emergency Responder.
You must log into Emergency Responder with system administrator or ERL administrator authority.
Prepare an import file. Emergency Responder includes detailed information about the required file format on the Import ERL Data page. The page also includes the location in which you must place the file 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.
Emergency Responder opens the ERL Configuration page.
Step 2 Click Import ERL Data.
Emergency Responder opens the Import ERL Data page.
Step 3 Select the format of your import file, and select your import file.
Step 4 Click Import.
Emergency Responder imports your ERL and associated ALI data, and displays the status of the import as it proceeds. The imported data overwrites existing conflicting data in the CER configuration.
Step 5 Click Close to close the Import ERL Data window.
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.
You must log into Emergency Responder with system administrator or ERL administrator authority.
 |
Caution Ensure that you submit each ALI export file as you create it. The ALI export records include an indication that the record is either new or modified. If you do not submit an ALI export file, the subsequent file you submit might have incorrect status indications, which can result in your service provider rejecting some, or possibly all, of your submitted records. |
Emergency Responder opens the ERL Configuration page.
Step 2 Click Export ERL/ALI Data at the top of the window.
Emergency Responder opens the Export ERL/ALI Data window.
Step 3 Select the type of data you want to export, and the format you want to use for the export file.
If you export ALI data, ensure that you select the NENA format required by your service provider. Do not submit ERL export files—they are not exported in a format your service provider can use. ERL export files are for your own use, for example, to back up or move an ERL configuration.
Step 4 If you are exporting ALI data, enter your company name and the sequence number for this data export. Emergency Responder automatically increments this counter each time you export data, so you do not need to change it 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 5 Click Export.
Emergency Responder creates the export file, and tells you the location where the file was created and how many records were exported.
Step 6 Click Close to close the Export ERL/ALI Data window.
Step 7 If you exported ALI data, use your service provider's method of transmitting the file to the service provider.
You can view the audit trail for an ERL to determine how, when, and by whom an ERL was created or changed.
You must have system administrator, ERL administrator, or network administrator authority to view the audit trail.
Emergency Responder opens the ERL Audit Trail page.
Step 2 Enter search criteria to select the ERLs whose audit history you want to view.
To view all ERLs, click Find without entering any criteria.
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.
Emergency Responder lists the matching audit records. If there are a lot of matches, Emergency Responder uses several pages to display them. Use the links at the bottom of the list to change pages.
Before you can assign switch ports to ERLs, you must identify the switches used in your network to Emergency Responder. These topics describe the switch requirements and how to identify switches to Emergency Responder:
Emergency Responder uses Cisco Discovery Protocol (CDP) to locate phones, so you should enable CDP on all of your switches. If you do not enable CDP, Emergency Responder must use the CAM table on the switch to track phones. Using the CAM table is less efficient than using CDP.
If some of the phones on your network do not use CDP, Emergency Responder tracks them using the CAM table.
Ensure that the switches to which phones are attached are supported by Emergency Responder, and that the switches are running the required software version. The "Network Hardware and Software Requirements" section lists the supported switches and software versions.
If you are using Catalyst 3500 switch clusters, you must assign IP addresses to every switch. Emergency Responder cannot work with a switch unless the switch has an IP address.
Emergency Responder uses SNMP to obtain information about the ports on a switch. Emergency Responder must obtain this port information so that you can assign the ports to ERLs, and so that Emergency Responder can identify phones that are attached to the ports and update their ERL assignments.
Emergency Responder only reads SNMP information, it does not write changes to the switch configuration, so you only have to configure the SNMP read community strings.
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 Emergency Responder. 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, CER 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, CER uses the SNMP string defined for 10.1.*.*. The sequence of entries on this page does not affect the selection.
Emergency Responder opens the SNMP Settings page.
Step 2 Enter an IP address pattern to which you want to associate an SNMP read community string. Use the asterisk (*) as a wildcard character. You can also use number ranges for octets, such as 15-30. Because Emergency Responder only tries to contact the switches you identify on the LAN Switch Details page (see the "Identifying the LAN Switches" section for more information), it does not matter if the IP address patterns cover devices other than switches.
Step 3 Enter the timeout and retries values. These values work together to determine how often and how long Emergency Responder tries to obtain SNMP information from a switch before giving up. The first attempt lasts as long as the timeout value. If you enter 1 or higher for retries, Emergency Responder tries again, and each retry lasts twice as long as the previous try. For example, if you specify 10 for timeout, the first retry lasts for 20 seconds, the second retry lasts for 40 seconds, and so forth.
The optimal values are 10 to 15 seconds for timeout, and 2 to 3 for retries.
Step 4 Enter the read community string, for example, public.
Step 5 Click Insert.
Step 6 Emergency Responder adds the SNMP setting to the list of settings. If you need to create more than one setting, return to Step 2.
To track phones successfully, Emergency Responder must periodically contact switches to obtain port and device information. Emergency Responder updates network information using two processes:
You must have system administrator or network administrator authority to define the schedule.
Emergency Responder opens the Schedule page.
Step 2 Enter the incremental phone tracking schedule in minutes and click Update.
Emergency Responder 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:
If you define schedules that overlap, CER only runs one process.
You must tell Emergency Responder which switches to manage. Emergency Responder tracks port changes, including changes to the devices connected to those ports, and can recognize which ports have phones connected to them. Identify all switches that might have phones attached to them, essentially all edge switches.
Because Emergency Responder must obtain information from the switches, you must ensure that the information you supply to Emergency Responder is correct and kept up-to-date. After you have created the initial switch list, you can make mass changes to switch definitions by exporting the switch definitions, editing the export file, and reimporting the file.
These topics describe how to identify switches to Emergency Responder, and how to export switch information:
You can enter switches into the Emergency Responder configuration one at a time. If you have a large number of switches to add, consider creating an import file to add them instead of using this procedure. See the "Importing a Group of Switches" section for more information.
You must have system administrator or network administrator authority to add, remove, or change switch definitions.
Determine if your network includes phones that do not use the Cisco Discovery Protocol (CDP) to announce themselves to the network. For non-CDP phones, Emergency Responder must use the CAM information 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.
Emergency Responder opens the LAN Switch Details page.
Step 2 Enter information about the switch:
Step 3 Click Insert to add the switch to the Emergency Responder configuration.
Emergency Responder asks if you want to run the switch-port and phone update process. You must run this process so that Emergency Responder can identify the ports on the switch, so that your ERL administrator can 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, CER 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.
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 Emergency Responder file format requirements (that is, by deleting columns, adding columns, rearranging columns, and so forth).
If you have a large network, importing switch definitions can save you a lot of time.
You must have system administrator or network administrator authority to import switch definitions.
Prepare an import file. Emergency Responder includes detailed information about the required file format on the Import LAN Switch page. The page also includes the location in which you must place the file 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.
Emergency Responder opens the LAN Switch Details page.
Step 2 Click Import in the left-hand switch list.
Emergency Responder opens the Import LAN Switch page.
Step 3 Select the file format, and the name of the file you want to import. Then, select one of these:
Step 4 Click Import.
Emergency Responder asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Emergency Responder imports the switches but does not run the phone tracking process.
After you make your selection, Emergency Responder adds the switch configurations and shows you the status of the import.
Step 5 Click Close to close the window.
Step 6 If you did not run phone tracking on the imported switches, select Phone Tracking>Run Switch-Port & Phone Update.
Emergency Responder contacts each switch to discover the ports on the switch and any phones attached to the ports.
Alternatively, you can view each switch's configuration on the LAN Switch Details page and click Locate Switch Ports. This runs the process only on the selected switch.
You can export your Emergency Responder 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 Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.
You must have system administrator or network administrator authority to export switch definitions.
Emergency Responder opens the LAN Switch Details page.
Step 2 Click Export in the left-hand switch list.
Emergency Responder opens the Export LAN Switch page.
Step 3 Select the file type and enter the file name for the export file. Do not include a file extension.
Step 4 Click Export.
Emergency Responder creates the export file. Click Close to close the window.
Before you can assign ERLs to switch ports, Emergency Responder must identify the ports on the switch using the switch-port and phone update process. Although Emergency Responder runs this process according to the schedule you set (see 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 CER-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:
You must have system administrator or network administrator authority to manually run the switch-port and phone update process.
Emergency Responder runs the process without changing the page you are viewing. Any newly-discovered ports are assigned to the Default ERL.
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 Emergency Responder:
After the network administrator adds switches to the Emergency Responder configuration, and runs the switch-port and phone update process, you can assign the switch ports to emergency response locations (ERLs). When you assign a port to an ERL, make sure that you assign the ERL based on the location of the device attached to the port, not the location of the port itself.
For example, say your wiring closet is on Floor 1, and half 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:
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.
You must have system administrator or ERL administrator authority to assign ports to ERLs.
You can only configure ports defined for the CER group to which you are logged in.
Emergency Responder opens the Switch Port Details page. This page has two tabs, Find and Configure. Before you can configure a port, you must list it in the bottom frame using the Find tab.
Step 2 On the Find tab, enter search criteria to list the ports you want to configure.
Step 3 Click Configure.
Emergency Responder opens the Configure tab.
Step 4 Assign ports to ERLs:
a. In the list of ports in the bottom frame, select the ports you want to assign to a single ERL. If you want to assign all listed ports, select the check box in the title row. You can only assign ports on one page at a time, so if there is more than one page of ports in the listing, complete this task for each page separately.
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 CER server in the CER group.
Emergency Responder assigns the ERL to the selected ports. You can continue assigning ports on this page of the ports list, but do not change the search results page before completing these steps.
Emergency Responder commits your ERL assignments. From here, you can continue to the another page of the listed ports, or click Find to enter new search criteria to obtain another list of ports.
You can assign a large number of ports to ERLs at one time by importing a file that contains the required information.
If you have a large network, importing port to ERL mappings can save you a lot of time.
You must have system administrator or ERL administrator authority to import switch port definitions.
Prepare an import file. The easiest way to create this file is to first export the switch port details from Emergency Responder (see 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.
Emergency Responder must already be aware of the ports before you import the file. Ensure that all ports you are importing have been located by Emergency Responder.
You can only configure ports defined for the CER group to which you are logged in.
Emergency Responder opens the Switch Port Details page.
Step 2 Click Import.
Emergency Responder opens the Import Switch Port page.
Step 3 Select the file and file format, and click Import.
Emergency Responder imports the file and shows you the import results. The ERL-to-port mappings and port location information in the import file overwrite any existing data in the CER configuration.
Step 4 Click Close to close the Import Switch Port page.
You can export your Emergency Responder 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 Emergency Responder. You can edit the export file, make your changes, then reimport the file and overwrite the information in Emergency Responder.
You must have system administrator or ERL administrator authority to export switch port definitions.
Emergency Responder opens the Switch Port Details page.
Step 2 Click Export.
Emergency Responder opens the Export Switch Port page.
Step 3 Select the file format and enter the desired file name, and click Export.
Emergency Responder exports the file to the location described on the page.
Step 4 Click Close to close the Export Switch Port page.
If Emergency Responder cannot locate a phone, it places the phone in the Default ERL and puts it in a list of unlocated phones. Using this list, you can reassign the phones to a different ERL, or you can use the list to help identify the problems that are preventing Emergency Responder from locating the phones. These are some things that can prevent Emergency Responder from locating a phone:
Because Emergency Responder cannot assign an unlocated phone to the appropriate ERL, try to identify and resolve all problems that are preventing CER from locating these phones on your network. If you cannot resolve the problems by defining switches in Emergency Responder, or by moving phones to supported switch ports, you can manually assign a phone to an ERL. See the "Too Many Unlocated Phones" section for more detailed information on resolving these problems.
You must have system administrator or ERL administrator authority to view or configure unlocated phones.
Emergency Responder opens the Unlocated Phones page and lists all unlocated phones.
Step 2 To assign a phone to an ERL, select or enter the ERL, select the phone, and click Assign to ERL.
Emergency Responder assigns the phone to the ERL, but leaves it in this list. If you later resolve the problem that is preventing Emergency Responder from locating this phone, Emergency Responder removes it from the list and assigns it the correct ERL based on port assignment.
To manage all emergency calls in your network, Emergency Responder must know about every phone whose calls are routed by Cisco CallManager, even if Emergency Responder does not directly support the phone. Emergency Responder handles emergency calls from these manually-defined phones in the same way it handles calls from phones attached to supported switch ports. The only difference is that Emergency Responder cannot dynamically change the ERL of a manually-defined phone if that phone is moved.
You 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 Emergency Responder.
You must have system administrator or ERL administrator authority to manually define phones.
Emergency Responder opens the Add/Modify Phones page.
Step 2 Enter information about the phone you want to define. You must enter the phone's extension and select an ERL. If the phone is an IP phone, you must also enter the IP address and MAC address for the phone. Other fields are optional and are mainly for your information.
Step 3 Click Insert.
Emergency Responder adds the phone to the list of manually defined phones.
You can view the history of emergency calls made in your network that are handled by Emergency Responder. Emergency Responder sends emergency call notifications to the onsite alert personnel 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.
Emergency Responder opens the Call History page.
Step 2 Select whether you want to view a list of calls made in the last three months, or a summary of calls made from three to twelve months ago. You can only view detailed information on calls made within the last three months.
If you select to view call summary information for the period prior to the last three months, click Find without entering search criteria.
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 Emergency Responder shows you in response to your search criteria, you can:
If a large number of calls match your search criteria, Emergency Responder uses additional pages to list the calls. Use the links at the bottom of the list to move through these additional pages.
Posted: Sun Jan 19 06:49:24 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.