|
These topics describe the fields on the pages of the Emergency Responder administrator's interface.
The CER Group Settings page displays when you log into the system or when you select CER Groups>CER Group Settings.
You must have system administrator authority to access this page.
Use the CER Group Settings page to define the operational characteristics of a CER server group.
The Telephony Settings page displays when you select CER Groups>Telephony Settings.
You must have system administrator authority to access this page.
Use the Telephony Settings page to define the telephone numbers and telephony ports used by the CER group.
Field | Description | Notes |
---|---|---|
The start of the range of UDP ports that the CER server will use for telephone calls. |
||
The route pattern that other CER groups will use to route emergency calls to this group, for example, 1000.911. |
See the "Creating Route Patterns for Inter-CER-Group Communications" section for a more detailed explanation of this number. |
|
The CTI route point you defined to receive calls from the public safety answering point (PSAP). For example, 913XXXXXXXXXX (913 plus ten Xs). |
See the "Creating the Emergency Call Route Points" section for more information. |
|
The digits to strip from the beginning of the PSAP Callback Route Point Pattern, for example, 913. The number that results from stripping the pattern should be the ELIN numbers that the PSAP can use to call into your network. |
This string must be part of the PSAP Callback Route Point Pattern. |
|
The CTI route point that the standby server should use, such as 912. Configure this number as the call forward number for the primary emergency number. |
See the "Creating the Emergency Call Route Points" section for more information. |
|
Click Cancel Changes to change the fields on this page back to the last saved settings. |
The Server Settings page displays when you select CER Group> Server Settings. The name of the page includes the name of the associated CER group.
You must have system administrator authority to access this page.
Use the Server Settings page to identify and configure the CER servers in the CER group. The first server you configure for a group becomes the primary server. You must first install both servers so that they use the same Cisco CallManager database for CER group configuration information. See the "Installing Cisco Emergency Responder on a New System" section for more information.
Field | Description | Notes |
---|---|---|
A list of servers you already created. Click on a server to see the settings for that server. |
You can configure a maximum of two servers per server group. |
|
Click Cancel Changes to change the fields on this page back to the last saved settings. |
||
Only available when viewing the settings of an existing server. |
||
Click Delete when viewing a server's settings to delete the server from the group. |
Only available when viewing the settings of an existing server. |
|
Click Update when viewing an existing server's settings to save changes you make to the settings. |
Only available when viewing the settings of an existing server. |
|
The first server you configure for a group becomes the primary server. |
||
The DNS name or IP address of the CER server. Cisco recommends that you use the IP address. |
If you use a DNS name, that name must be reachable by all other CER servers that are in the same CER cluster. |
|
A selection of subsystems for which you need to collect detailed debug information. Debug information includes trace messages as well as more detailed messages. Only select subsystems at the request of Cisco Technical Support; the debug information is for Cisco's use to help resolve problems that you cannot solve yourself. |
See the "Collecting Trace and Debug Information" section for an explanation of each field. |
|
A selection of subsystems for which you need to collect brief trace information. Only select subsystems at the request of Cisco Technical Support; the trace information is for Cisco's use to help resolve problems that you cannot solve yourself. If you select a subsystem for debug, you do not have to select it for trace. |
See the "Collecting Trace and Debug Information" section for an explanation of each field. |
The License Manager page displays when you select CER Group>License Manager.
You must have system administrator authority to access this page.
Use the License Manager page to enter the product license for Cisco Emergency Responder.
The Control Center page displays when you select CER Group>Control Center.
You must have system administrator authority to access this page.
Use the Control Center page to start and stop CER servers within the CER group.
Field | Description | Notes |
---|---|---|
Each CER server in the group is listed along with its current status. If a server is not running, the Start button appears, and you can restart the server by clicking Start. If a server is running, the Stop button appears, and you can stop it by clicking Stop. |
See the "Starting and Stopping a CER Server" section for information on the meaning of the icons shown on this page. |
The ERL Configuration page displays when you select ERL>ERL Details.
You must have system administrator or ERL administrator authority to access this page.
Use the ERL Configuration page to define the emergency response locations (ERLs) for your company. An ERL might be a whole building (if it is small), the floor of a building, or an area on a floor. Each community can have different laws concerning the size of an ERL, so consult your local ordinances and with your service provider before deciding on your ERLs. The ERLs you create will be used by emergency response teams to locate the emergency, so the ERL should be small enough that these teams can locate the caller within a reasonable time.
Field | Description | Notes |
---|---|---|
Select search criteria and click Find to list existing ERLs. To list all ERLs, click Find without entering any criteria. From the search results list, you can:
|
When copying an ERL, information that must be unique in an ERL is not copied. See the "Add New ERL; ERL Information" section for more information. |
|
See the "Add New ERL; ERL Information" section for more information. |
||
Click Configure Default ERL to create the ERL that will be used as the initial ERL assigned to switch ports when they are first discovered. |
Unless you are using Emergency Responder to manage a single small building (in which case you only need one ERL), the default ERL is not typically used as the permanent ERL for any switch port or phone. See the "Add New ERL; ERL Information" section for more information. |
|
Click Export ERL/ALI Data to create a file containing your ERL/ALI configuration. Send this file to your service provider so that they can update the required databases. See the "Export ERL/ALI Data" section for information on exporting ERL data. |
You must export ERL/ALI data and submit it to your service provider so emergency calls are routed to the correct public safety answering point (PSAP) and so that the PSAP has access to the location information when receiving an emergency call. |
|
Click Import ERL Data to create ERLs using information stored in a separate file. By importing ERL data, you can create many ERLs at one time. |
See the "Import ERL Data" section for information on importing ERL data. |
The Add New ERL and ERL Information pages are essentially the same:
You must have system administrator or ERL administrator authority to access this page.
Use the Add New ERL page to create a new emergency response location (ERL). Alternatively, you can create many ERLs at once by importing predefined ERL information from a separate file. See the "Import ERL Data" section for more information.
Use the ERL Information page to view or update an existing ERL.
Field | Description | Notes |
---|---|---|
The name of the ERL. The naming strategy you use is critical. The ERL name is one of the primary pieces of information your security team will see when alerted to an emergency call. If the name is easy to understand and very descriptive, it can help your team respond quickly to a call. For example, if you are creating an ERL for each floor in a three story building called Building J, your ERL names might be BldgJ-Floor1, BldgJ-Floor2, BldgJ-Floor3. Work with your security team to develop and ERL naming strategy. |
You cannot change the name of an existing ERL. To change an ERL name, create a new ERL, then delete the old ERL. |
|
These notes are not available to CER end users (security personnel). |
||
The combination of a route pattern and a telephone number that jointly route the emergency call to the PSAP and provide the PSAP with a call-back number if the PSAP needs to call the emergency caller after disconnecting the call.
To add a route point-ELIN combination, enter the information and click Add. |
To change an existing combination, select it in the list, change the information in the edit boxes, and click Update. To remove a combination, select it in the list and click Remove. See the "Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks" section for information on configuring these numbers in Cisco CallManager. Each ERL must have unique ELINs. The number of ELINs you define determines how many callbacks you can support. ELINs are used in order as emergency calls are made, and recycled as needed. For example, if you define two ELINs for an ERL, and three emergency calls are made, the PSAP will not be able to recontact the first emergency caller. However, concurrent emergency calls are not limited by the number of ELINs: you could have ten active emergency calls even if you only have two ELINs. The number of ELINs only controls PSAP callback capability. |
|
Select the onsite alert (security) personnel assigned to the ERL. These are the people who are notified when an emergency call is made from the ERL. |
You must first add the person to Emergency Responder. See the "Onsite Alert Settings" section for more information. |
|
Click ALI Details to view or change the automatic location information (ALI) of an ERL. The ALI provides detailed information about the location of the ERL, such as street address and phone number. |
See the "ALI Information (for ERL)" section for information about the ALI fields. |
|
The Insert button is only available when creating a new ERL. |
||
Click Cancel Changes to change the fields on this page back to the last saved settings. |
||
The Update button is only available when changing an existing ERL. |
||
Click Copy to create a duplicate of the ERL and its associated ALI. |
||
Click Close to close the window. You must click Update or Insert to save your changes before clicking Close. |
The ALI Information page displays when you do one of these:
You must have system administrator or ERL administrator authority to access this page.
Use the ALI Information page to enter the automatic location information (ALI) for an emergency response location (ERL). You will eventually send this information to your service provider, who will ensure it gets into the required database so that calls from your ELINs can get routed to the local PSAP and so that public safety answering points (PSAPs) can locate an emergency caller.
The data requirements for these fields might differ from service provider to service provider. Contact your service provider to determine their requirements. The descriptions of the fields in Table A-8 are based on the National Emergency Number Association's (NENA) Version 2 standards (USA).
Caution The quality of the information you enter here is critical. This information is displayed to emergency call operators and to your local response team. They use this information to locate emergency callers. If the data is incorrect or difficult to understand, emergency response can be delayed, which might result in casualties that could have been prevented. |
The Export ERL/ALI Data page displays when you select Export ERL/ALI Data on the ERL Configuration page (opened when you select ERL>ERL Details).
You must have system administrator or ERL administrator authority to access this page.
Use the Export ERL/ALI Data page to create a file that you can send to your service provider to update their ALI data for your organization. Your service provider needs this information so that emergency calls from your ERLs can be routed to the correct public safety answering point (PSAP).
You can also use export files to back up your ERL/ALI configuration.
Note If you change the customer code in your ALI record, CER generates two records when exporting ALI: a Delete record to remove the ALI with the old code, and an Insert record to add the ALI with the new code. This Delete/Insert sequence is only generated the first time you export ALI after changing the code: you must ensure you submit this export file to the service provider. See the "ALI Information (for ERL)" section for information about ALI fields. |
The Import ERL Data page displays when you select Import ERL Data on the ERL Configuration page (opened when you select ERL>ERL Details).
You must have system administrator or ERL administrator authority to access this page.
Use the Import ERL Data page to create many ERLs at once from a file in which you have defined the ERL and ALI data. Create this file using a spreadsheet that can save the information in one of the required formats. View the samples from this page before attempting to create an import file.
If you need to update a lot of ERLs, you can export the ERL/ALI data, update the export file, and reimport the file.
The Security Settings page displays when you select ERL>Onsite Alert Settings.
You must have system administrator or ERL administrator authority to access this page.
Use the Onsite Alert Settings page to add information about your security personnel. When you configure ERLs, you assign these personnel to them. Cisco ER will alert the assigned personnel when an emergency call is made within the zone.
The SNMP Settings page displays when you select Phone Tracking>SNMP Settings.
You must have system administrator or network administrator authority to access this page.
Use the SNMP Settings page to define the SNMP read community string used by your switches.
Field | Description | Notes |
---|---|---|
The IP address or host name of a switch whose SNMP read community string you are defining. If you use the same read community string for all switches, you only need to define one entry: *.*.*.*. If you use different read community strings for sets of switches, you can define each set, using variables and ranges. For example, if you have 10 switches from 10.1.115.0 to 10.1.125.0, you can use 10.1.115-125.0 as the IP address. You can also mix ranges and variables, such as *.*.115-125.*. |
You are not defining your switches on this page, you are only associating IP address patterns to read community strings. Emergency Responder only tries to use the string with the specific switches you identify on the LAN Switch Details page. See the "LAN Switch Details" section for more information. If two or more patterns match an IP address, CER uses the SNMP string associated with the most closely matching pattern. |
|
The time, in seconds, in which Emergency Responder should consider an attempted SNMP connection to a switch to have failed. See the explanation of Retries for more information. |
Default is 10 seconds. The optimal value is 10 to 15 seconds. |
|
The number of times Emergency Responder should attempt to contact a switch. With each retry, the previous timeout is multiplied by 2, to ensure the switch has enough time to respond. For example, if you specify 10 for timeout, the first attempt times out in 10 seconds, the second attempt times out in 20 seconds, the third attempt times out in 40 seconds, and so forth. |
Default is 2 retries. This does not include the initial attempt, that is, if retries is 2, Emergency Responder will attempt to contact a switch up to 3 times (the initial attempt plus 2 retries). |
|
Default is public for any IP address not covered in the SNMP settings list. |
||
Click Update when viewing an existing setting to save changes you make to the setting. |
||
Click Cancel Changes to change the fields on this page back to the last saved settings. |
||
A list of SNMP settings that you have already defined. To change an entry, click the entry to load the details into the edit boxes at the top of the page. Then make your changes and click Update. |
The Schedule page displays when you select Phone Tracking>Schedule.
You must have system administrator or network administrator authority to access this page.
Use the Schedule page to define Emergency Responder's schedule for updating phone and switch information from the network. Emergency Responder updates network information using two processes:
The Cisco CallManager Details page displays when you select Phone Tracking>Cisco CallManager Details.
You must have system administrator or network administrator authority to access this page.
Use the Cisco CallManager Details page to identify the Cisco CallManager clusters whose emergency calls this Emergency Responder (CER) group will handle. Only assign a Cisco CallManager cluster to a single CER group. Emergency Responder gets the list of phones registered with these Cisco CallManager servers and tracks the movements of these phones.
Field | Description | Notes |
---|---|---|
A list of Cisco CallManager servers defined for this CER group. Click a server to view the Emergency Responder configuration for the server. |
||
Click Insert to add the Cisco CallManager server to the list of servers. |
||
Click Update when viewing an existing server to save changes you make to the server. |
||
Click Delete when viewing a server to delete that server from the Emergency Responder configuration. |
||
Click Cancel Changes to change the fields on this page back to the last saved settings. |
||
The IP address or DNS name of a Cisco CallManager server that is running Cisco CallManager and SNMP services. Only add one server per Cisco CallManager clusterEmergency Responder can identify the other servers in the cluster. The Cisco CallManager server you specify will represent the cluster in which it is a member. |
When viewing a previously-defined Cisco CallManager server, Emergency Responder displays a CCM List link. Click CCM List to view a list of the Cisco CallManager servers that belong to the same cluster as the selected server. |
|
The IP address or DNS name of the CTI Manager used by the specified Cisco CallManager server. |
||
The name of the user created in the Cisco CallManager server for Emergency Responder's use. |
This user must have specific characteristics and device assignments. See the "Creating an Emergency Responder Cisco CallManager User" section for specific information. |
|
The IP address or DNS name of the backup CTI Manager used by the specified Cisco CallManager server. |
||
The number of the first CTI port to use for calling onsite alert (security) personnel. When an emergency call is made, Emergency Responder calls the onsite alert personnel for the originating ERL using the telephony ports you configure here. |
You must first create this port in Cisco CallManager. See the "Creating the Required CTI Ports" section for more information. |
|
The number of CTI ports. Enter the number of CTI ports you created in Cisco CallManager. The number of ports is the number of concurrent calls Emergency Responder can make to onsite alert personnel. |
The ports used are in sequence from the beginning port. For example, if you enter 3000 for the begin port, and 4 for number of ports, Emergency Responder uses 3000, 3001, 3002, and 3003. |
The LAN Switch Details page displays when you select Phone Tracking>LAN Switch Details.
You must have system administrator or network administrator authority to access this page.
Use the LAN Switch Details page to add, remove, or change the switches that Emergency Responder manages. Ensure you identify all switches that might have phones attached to them. You can only assign switch ports to ERLs if you enter the switches on this page. Any phones attached to unidentified switches or ports are listed as unlocated phones in Emergency Responder, and are assigned to the Default ERL.
Field | Description | Notes |
---|---|---|
A list of the switches you have already defined, plus these commands:
|
||
Click Insert to add the switch to the list of switches. When you click Insert, Emergency Responder asks if you want to run the switch-port and phone update process on the switch right away. Click OK to run the process now, or click Cancel to simply add the switch to the configuration without running the process immediately. |
See the "Manually Running the Switch-Port and Phone Update Process" section for information on running the process if you select not to run it immediately. Discovered switch ports are initially assigned to the Default ERL. |
|
Click Update when viewing an existing switch to save changes you make to the switch. |
||
Click Delete when viewing a switch to delete that switch from the Emergency Responder configuration. |
||
Click Cancel Changes to change the fields on this page back to the last saved settings. |
||
Click Locate Switch Ports to have Emergency Responder contact the switch and perform the switch-port and phone update process. |
||
Select this if there might be phones attached to this switch that do not use the Cisco Discovery Protocol (CDP) to announce themselves to the network. For non-CDP phones, Emergency Responder must use the CAM information on the switch to identify phones. |
The Export LAN Switch page displays when you click Export in the LAN Switch Details page (opened when you select Phone Tracking>LAN Switch Details).
You must have system administrator or network administrator authority to access this page.
Use the Export LAN Switch page to create a file containing the Emergency Responder switch configuration.
If you need to update several switch entries in Emergency Responder, you can export the switch information, make your changes in the export file using a spreadsheet, then reimport the file.
The Import LAN Switch page displays when you click Import in the LAN Switch Details page (opened when you select Phone Tracking>LAN Switch Details).
You must have system administrator or network administrator authority to access this page.
Use the Import LAN Switch page to add several switches at once to the Emergency Responder configuration. You might be able to create an appropriate import file using your network management software.
Field | Description | Notes |
---|---|---|
Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. Use this sample information to create your import file in a spreadsheet, or to determine if your network management software can create the required format. |
||
Select the file from which you want to import data. Before you can import a file, you must place it in the folder mentioned on this page. |
||
Select how Emergency Responder should handle conflicts between information in the import file and information already defined in the Emergency Responder configuration:
|
||
Click Import to add data from the information in the import file to your Emergency Responder configuration. Emergency Responder asks you whether you want to run phone tracking on the imported switch. You must run phone tracking before you can configure the switch ports, so normally you should select OK. If you select Cancel, Emergency Responder imports the switches but does not run the phone tracking process. |
If you elect not to run the phone tracking process, after importing the file, run the switch-port and phone update process. See the "Manually Running the Switch-Port and Phone Update Process" section. |
|
The Switch Port Details page displays when you select Port/Phone>Switch Port Details.
You must have system administrator or ERL administrator authority to access this page.
Use the Switch Port Details page to assign switch ports to ERLs. This assignment allows Emergency Responder to assign the correct ERL to phones that connect to the network through the configured ports.
Field | Description | Notes |
---|---|---|
Find tab | ||
Enter search criteria to select the ports you want to view or configure. To view all ports, click Find without entering any criteria.
|
If you are configuring ports, you must first generate a list of ports on the Find tab. |
|
The list of switch ports that match your search criteria, one line per port. You can change the fields shown in the list, and change their order, by clicking on Edit Table View. This opens a separate window:
Click Apply to save your changes on the Edit Table View page. Click Close to close the window without making changes. |
If a large number of ports match your search criteria, Emergency Responder uses several pages to display them. Use the First, Previous, Next, and Last links at the bottom of the page to move between pages. You can also enter a specific page number in the Page field and press Enter to move to that page. |
|
Configure tab | ||
Select the ports you want to configure by checking the corresponding box in the search results list. To select all ports in the displayed list, check the box in the list heading. Note You can only configure ports on one page at a time. If you select all ports, the selection does not include any other pages you might have generated in your port search. |
Before you can configure a port, you must use the Find tab to list the port in the interface. |
|
Select the ERL you want to assign to the selected ports. You can type in the ERL name if you prefer. You can also update the phone location for the selected ports. 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. |
All selected ports are assigned to the same ERL. Ensure that the ERL you choose reflects the location of the device connected to the port, not the location of the switch. For example, if you have two floors, one ERL per floor, and one switch that is used by both floors, that switch should have ports in each ERL. |
|
Click Configure Ports to map the selected ports to the selected ERL. You can continue to Step 4 or return to Step 1 to map additional ports. However, you must complete Step 4 before you can configure ports on additional pages of the search results. |
||
Click OK to commit your changes, Cancel to undo your changes. |
||
Export | Click Export to export the ERL to switch port configuration to another file. See the "Export Switch Port" section for more information. |
|
Import | Click Import to import a set of ERL-to-port mappings into the Emergency Responder configuration. See the "Import Switch Port" section for more information. |
The Export Switch Port page displays when you click Export in the Switch Port Details page (opened when you select Port/Phone>Switch Port Details).
You must have system administrator or ERL administrator authority to access this page.
Use the Export Switch Port page to create a file containing the Emergency Responder switch port configuration.
If you need to make changes to a large number of port-to-ERL assignments, you can export a file, make your changes in the file using a spreadsheet, and then reimport the file.
The Import Switch Port page displays when you click Import in the Switch Port Details page (opened when you select Port/Phone>Switch Port Details).
You must have system administrator or ERL administrator authority to access this page.
Use the Import Switch Port page to add several switch port configurations at once to the Emergency Responder configuration. Switch port configurations are mappings of ports to ERLs. You can create the import file using a spreadsheet program that can save the file in the required format.
Field | Description | Notes |
---|---|---|
Select the format used in the file you are importing. After you select the format, click view sample file to see an example of the expected format and sequence of values. You can use this sample information to create your import file in a spreadsheet, but it is easier to export the switch port information from CER, modify the export file using a spreadsheet program, and then import the modified file. |
See the "Exporting Switch Port Information" section for information on exporting switch port information. |
|
Select the file from which you want to import data. Before you can import a file, you must place it in the folder mentioned on this page. |
||
Click Import to add data from the information in the import file to your Emergency Responder configuration. ERL assignments in the import file override assignments that already exist in the CER configuration. |
Port ERL configurations are only updated if Emergency Responder has discovered the port before you import the port configuration. |
|
The Unlocated Phones page displays when you select Port/Phone>Unlocated Phones.
You must have system administrator or ERL administrator authority to access this page.
Use the Unlocated Phones page to identify phones that are registered with Cisco CallManager, but which Emergency Responder cannot locate. This can happen for several reasons:
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 might have to manually assign a phone to an ERL on this page. See the "Too Many Unlocated Phones" section for troubleshooting information.
The Add/Modify Phones page displays when you select Port/Phone> Add/Modify Phones.
You must have system administrator or ERL administrator authority to access this page.
Use the Add/Modify Phones page to manually define a phone's ERL. You need to manually define a phone if any of these conditions apply:
For manually-defined phones, Emergency Responder cannot automatically locate and update ERL information. You should regularly review manual phone configurations to ensure they are correct.
The Call History page displays when you select Reports>Call History.
You must have system administrator, ERL administrator, or network administrator authority to access this page.
Use the Call History page to view the history of emergency calls made from your network.
Field | Description | Notes |
---|---|---|
Enter search criteria to select the emergency calls you want to view. To view all emergency calls, click Find without entering any criteria.
|
You can see either detailed call information, or summary information: |
|
A list of emergency calls that match your search criteria.
|
If a large number of calls match your search criteria, Emergency Responder uses several pages to display them. Use the First, Previous, Next, and Last links at the bottom of the page to move between pages. You can also enter a specific page number in the Page field and press Enter to move to that page. CER only displays up to 400 call records for a given month. If there were more than 400 calls in a month, look at the call history logs for the call information for these calls. See the "Collecting Call History Logs" section for more information. |
The CER Server Groups in Cluster page displays when you select Reports>CER Groups in Cluster.
You must have system administrator, ERL administrator, or network administrator authority to access this page.
Use the CER Server Groups in Cluster page to view the CER groups that form a CER cluster. You can view which CER servers belong to each CER group within the cluster.
Field | Description | Notes |
---|---|---|
A list of the Emergency Responder server groups that have are using the same Cisco CallManager database as the CER cluster database. |
The CER cluster consists of this set of CER groups. You create the cluster when installing CER servers. See the "Installing Cisco Emergency Responder on a New System" section. |
|
Click Delete to remove the CER group you are viewing from the CER cluster. |
Only system administrators can delete a CER group from the cluster. Delete a group from the cluster before you uninstall a CER group. |
|
The IP address or DNS name of the primary server in the group. |
||
The IP address or DNS name of the standby, or backup server in the group. |
The ERL Audit Trail page displays when you do one of these:
You must have system administrator, ERL administrator, or network administrator authority to access this page.
Use the ERL Audit Trail page to view the change history for ERLs.
Posted: Sun Jan 19 06:51:00 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.