Cisco Emergency Responder Administration Guide 1.3(1)
Configuring Cisco CallManager 3.3 or 4.x for Cisco Emergency Responder 1.3(1)
Downloads: This chapterpdf (PDF - 368.0KB) The complete bookPDF (PDF - 2.77MB) | Feedback

Configuring Cisco Unified CallManager 3.3 or Cisco Unified CallManager 4.x for Cisco Emergency Responder 1.3(1)

Table Of Contents

Configuring Cisco Unified CallManager 3.3 or Cisco Unified CallManager 4.x for Cisco Emergency Responder 1.3(1)

Setting Up Phone Route Plans

Creating a Phone Partition

Creating a Phone Calling Search Space

Assigning the Partition and Calling Search Space to Phones

Setting Up Cisco Emergency Responder to Handle Emergency Calls

Creating a Cisco Emergency Responder Partition

Creating a Cisco Emergency Responder Calling Search Space

Creating the Emergency Call Route Points

Creating the Required CTI Ports

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Creating the Route Patterns for ELINs

Creating the Translation Patterns for ELINs

Creating the Translation Patterns for 9.911

Creating Alternate Emergency Call Numbers

Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

Creating a Cisco Emergency Responder Cisco Unified CallManager User


Configuring Cisco Unified CallManager 3.3 or Cisco Unified CallManager 4.x for Cisco Emergency Responder 1.3(1)


This chapter describes procedures for configuring Cisco Unified CallManager 3.3 or Cisco Unified CallManager 4.x for Cisco Emergency Responder 1.3(1). If you are running Cisco Unified CallManager 5.0, follow the procedures in "Configuring Cisco Unified CallManager 5.0 for Cisco Emergency Responder 1.3(1)."

These topics describe the items you must configure in Cisco Unified CallManager so that Cisco Emergency Responder (Cisco ER) can work in your telephone network.

These topics describe a sample Cisco Unified CallManager setup—the names chosen (for example, partition and calling search space names) are not required.

Setting Up Phone Route Plans

Setting Up Cisco Emergency Responder to Handle Emergency Calls

Creating a Cisco Emergency Responder Cisco Unified CallManager User

Understanding the Cisco Unified CallManager Examples

These sections represent an example setup, with sample values included for reference only. Your particular configuration depends on the needs of your network and your naming strategy.

For these examples, you will be working with the following calling search spaces and partitions:

PhoneCSS—includes the Phones partition.

E911CSS—includes the E911 and Phones partitions.

The examples are based on a single Cisco Unified CallManager cluster. If you have more than one cluster, you must repeat the configuration in each cluster, except for the emergency location identification number (ELIN) translation patterns. The ELIN translation patterns are only defined in the Cisco Unified CallManager cluster to which the gateway will send incoming calls from the public safety answering point (PSAP).

Setting Up Phone Route Plans

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

These sections provide an example setup for your network before adding Cisco ER:

Creating a Phone Partition

Creating a Phone Calling Search Space

Assigning the Partition and Calling Search Space to Phones

Creating a Phone Partition

If you have not already created a partition for the phones, follow this procedure to create one now.

Procedure


Step 1 Select Route Plan > Partition in Cisco Unified CallManager.

The Find and List Partitions page displays.

Step 2 Click Add a New Partition.

The Partition Configuration page displays.

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

Step 4 Click Insert to add the new partition.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Phone Calling Search Space

Assigning the Partition and Calling Search Space to Phones

Creating a Phone Calling Search Space

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

Procedure


Step 1 Select Route Plan > Calling Search Space in Cisco Unified CallManager.

The Find and List Calling Search Spaces page displays.

Step 2 Click Add a New Calling Search Space.

The Calling Search Space Configuration page displays.

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

Step 4 Select the Phones partition in the Available Partitions list box, and add it to the Selected Partitions list box by clicking the arrow buttons between the two list boxes.

Step 5 Click Insert to add the new calling search space.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Phone Partition

Assigning the Partition and Calling Search Space to Phones

Assigning the Partition and Calling Search Space to Phones

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

Before You Begin

You can use the Bulk Administration Tool (BAT) to change the partition and calling search space on telephones in much less time than it takes to make the changes to each phone individually. This procedure describes the phone-by-phone procedure.

Procedure


Step 1 Select Device > Phone.

Cisco Unified CallManager displays the Find and List Phones page.

Step 2 Select Device name is not empty in the search fields and click Find.

Cisco Unified CallManager lists all of the phones in the bottom frame.

Step 3 Click the phone whose configuration you want to change.

Cisco Unified CallManager displays the Phone Configuration page.

Step 4 Change the calling search space to PhoneCSS and click Update.

Step 5 Click the line number you want to configure in the left-hand column.

Cisco Unified CallManager displays the Directory Number Configuration page.

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

Step 7 Click Insert to save your changes.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Phone Partition

Creating a Phone Calling Search Space

Setting Up Cisco Emergency Responder to Handle Emergency Calls

To handle emergency calls, you must configure the emergency call numbers (such as 911) so that Cisco Emergency Responder (Cisco ER) intercepts them. Cisco ER can then route the calls to the correct public safety answering point (PSAP) and transform the call as required to route the call and to enable the PSAP operator to call back the emergency caller if the initial call is disconnected.

These topics describe how to define the Cisco Unified CallManager elements required for Cisco ER:

Creating a Cisco Emergency Responder Partition

Creating a Cisco Emergency Responder Calling Search Space

Creating the Emergency Call Route Points

Creating the Required CTI Ports

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Creating Alternate Emergency Call Numbers

Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

Creating a Cisco Emergency Responder Partition

Follow this procedure to create the Cisco Emergency Responder (Cisco ER) partition E911. This partition contains the numbers used by the PSAP to call into the network, and certain other CTI route points.


Caution When configuring Cisco Unified CallManager 4.1(2) or later and Cisco ER 1.3(1), you must not set the Time of Day feature in the E911 partition used for emergency calls.

Procedure


Step 1 Select Route Plan > Partition in Cisco Unified CallManager.

The Find and List Partitions page displays.

Step 2 Click Add a New Partition.

The Partition Configuration page displays.

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

Step 4 Click Insert to add the new partition.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Cisco Emergency Responder Calling Search Space

Setting Up Phone Route Plans

Creating the Emergency Call Route Points

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

Creating a Cisco Emergency Responder Calling Search Space

Follow this procedure to create the Cisco Emergency Responder (Cisco ER) calling search space.

Procedure


Step 1 Select Route Plan > Calling Search Space from Cisco Unified CallManager.

The Find and List Calling Search Spaces page displays.

Step 2 Click Add a New Calling Search Space.

The Calling Search Space Configuration page displays.

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

Step 4 In the Available Partitions list box, select the E911 partition and then select the Phones partition in that order; add them to the Selected Partitions list box by clicking the arrow buttons between the two list boxes. Arrange the partitions so that E911 is at the top of the list.

If you are using any other partitions, add them to this list after the E911 partition.


Note You must list the E911 partition before the Phones partition for the following reason: When the user configures the translation pattern 911 or 9.911 (see the "Creating the Translation Patterns for 9.911" section), the 911 Route Point will be in the E911 partition; phones cannot look into the E911 Partition. The 911 Translation Pattern is in the phones partition and gets the E911CSS. When the E911 partition is listed first, it matches the 911 Route Point and the call goes to the Cisco ER server as intended. If you make the error of listing the Phones partition first, the Translation Pattern keeps searching, resulting in a fast busy signal.


Step 5 Click Insert to add the new calling search space.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Cisco Emergency Responder Partition

Setting Up Phone Route Plans

Creating the Emergency Call Route Points

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Creating Alternate Emergency Call Numbers

Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP

Creating the Emergency Call Route Points

You must configure CTI route points in Cisco Unified CallManager for:

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


Note If you use 9 as the access code, see the "Creating the Translation Patterns for 9.911" section to configure Cisco ER.


The number that your standby Cisco Emergency Responder (Cisco ER) server should listen to, such as 912.

The number that incoming calls from the public safety answering point (PSAP) will use. Cisco ER modifies these calls based on your ELIN configuration to route the call to the person who initiated the emergency call, if the PSAP gets disconnected and needs to call the calling party. See the "Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks" section for information about the rest of the ELIN configuration.

Before You Begin

This procedure assumes you are using 911 as the main emergency call number. If a different number is used in your locale, substitute it for "911," and make similar substitutions for other numbers based on "911," such as "912." For example, if the emergency call number in your locale is 112, use 112, and perhaps 113, 114.

When you install Cisco ER, you are required to enter the emergency call number. In this procedure, configure the same number you specify during installation.

Use the following procedure to create the route points described in Table 3-1.

Table 3-1 Emergency Call Route Points 

Route Point Setting
Route Points
Primary Number (911)
Backup Number (912)
ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Cisco ER handles all calls to this number.

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

The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan.

The number can only consist of numbers and Xs.

Directory Number

911

912

913XXXXXXXXXX

Partition

Phones

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination: One of:1

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.2

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination: One of:

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination: One of:

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

1 Configuring call-forwarding numbers for the standby server ensures that calls are either routed to the PSAP servicing the default ERL, or onsite security, if the standby server cannot handle the call. If you do not install a standby server, use these settings for the primary server.

2 Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Cisco ER cannot handle the call.


Procedure


Step 1 In Cisco Unified CallManager, select Device > CTI Route Point.

The Find and List CTI Route Points page displays.

Step 2 Click Add a new CTI Route Point.

The CTI Route Point Configuration page displays.

Step 3 Fill in the CTI route point properties:

Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. Table 3-1 shows suggested names, but you can use any name you choose.

Select the appropriate device pool from the Device Pool menu.

Select the calling search space for the route point, as listed in Table 3-1.

Step 4 Click Insert to add the new CTI route point.

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

Cisco Unified CallManager opens the Directory Number configuration page.

Step 5 Enter the configuration for the line you are creating using the information in Table 3-1.

Step 6 Click Insert.

Cisco Unified CallManager adds the line to the device. Repeat this procedure until all devices described in Table 3-1 are configured.

For additional assistance, refer to the documentation and online help included with Cisco Unified CallManager.


Related Topics

Creating a Cisco Emergency Responder Partition

Creating a Cisco Emergency Responder Calling Search Space

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

Creating Alternate Emergency Call Numbers

Creating a Cisco Emergency Responder Cisco Unified CallManager User

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

Installing Cisco Emergency Responder 1.3(1) on a New System

Creating the Required CTI Ports

Cisco Emergency Responder (Cisco ER) uses CTI ports to call onsite alert (security) personnel when someone makes an emergency call. You should have enough CTI ports so that each person assigned to an ERL can receive a call. The number of ports you configure is the number of simultaneous calls Cisco ER can make to these personnel. It does not relate to the number of emergency calls Cisco ER can handle or forward to the PSAP—there is no configurable limitation to the number of simultaneous emergency calls that Cisco ER can handle.

Before You Begin

Cisco ER requires that the CTI port extension numbers be in succession, so you must find a block of unused extensions. For example, if you want to create four CTI ports starting at 3001, then 3001, 3002, 3003, and 3004 must all be available.

Procedure


Step 1 Select Device > Phone.

Cisco Unified CallManager opens the Find and List Phones page.

Step 2 Click Add a New Phone.

Cisco Unified CallManager opens the Add a New Phone page.

Step 3 Select CTI Port for Phone Type and click Next.

Cisco Unified CallManager opens the Phone Configuration page.

Step 4 Configure the CTI Port, entering this information:

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

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

Calling Search Space—Select PhoneCSS.

Step 5 Click Insert.

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

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

Partition—Select Phones.

Calling Search Space—Select PhoneCSS.


Note Configure only one line for each CTI port. Onsite security alert prompts may not get from one or more of these lines when the online alert notification is initiated through these ports.


Step 7 Click Insert.

Cisco Unified CallManager adds the line to the device. Repeat the procedure to create each CTI route port that you require.


Note All subsequent CTI ports you create must be consecutive from the first CTI port DN.



Related Topics

Creating a Cisco Emergency Responder Partition

Creating a Cisco Emergency Responder Calling Search Space

Creating a Cisco Emergency Responder Cisco Unified CallManager User

Identifying the Cisco Unified CallManager Clusters

Creating ERLs

Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks

Emergency calls are routed based on the calling party number, not the called party number. If an emergency call is disconnected for some reason (for example, the caller hangs up), the PSAP needs to be able to call back the emergency caller using the calling party number. The PSAP might also want to call back to obtain updated information after ending an emergency call normally.

Cisco Emergency Responder (Cisco ER) converts a caller's extension to an emergency location identification number (ELIN), and this number is used to route the call and to enable PSAP callbacks. Cisco ER reuses the same set of numbers, and keeps track of the internal extension of the phone from which the call was made for up to three hours.

To set up the ELIN numbers, you must first obtain direct inward dial (DID) numbers from your service provider. Because you must pay for each number, you might want to limit the number of DIDs you obtain to two or three per ERL. The DIDs must be unique for each ERL.

Cisco ER will reuse the ELIN numbers assigned to an ERL if necessary. For example, if you configure two numbers for an ERL, and three emergency calls are made within a three hour window, the first emergency caller's ELIN mapping is replaced by the third caller's extension. Thus, if the PSAP tries to call the first caller, the PSAP will reach the third caller. Keep this in mind as you determine the number of DIDs you will obtain for each ERL.

These topics describe how to set up the route patterns and translation patterns required to set up the ELIN numbers:

Creating the Route Patterns for ELINs

Creating the Translation Patterns for ELINs

See the "Creating ERLs" section for information on how to configure the ERLs with these numbers.

Creating the Route Patterns for ELINs

Cisco Emergency Responder (Cisco ER) uses route patterns to route emergency calls to the local public safety answering point (PSAP). In the route pattern, you are associating a pattern with a gateway that will connect to the PSAP. The gateway you choose depends on the emergency response location (ERL) to which you will assign the route pattern.

You must create one route pattern for every ELIN in your network. These are the direct inward dial (DID) numbers you obtain from your service provider for the purpose of allowing the PSAP to call into your network.

Before You Begin

Each ERL requires unique route patterns for the ELINs. Work with the ERL administrator to get an idea of how many route patterns are needed, and the locale of the ERLs so that you can select an appropriate gateway. The ERL administrator must enter the route patterns you create into the ERL definition. See the "Creating ERLs" section for information about ERLs.

Procedure


Step 1 Select Route Plan > Route Pattern.

Cisco Unified CallManager opens the Find and List Route Patterns page.

Step 2 Click Add a New Route Pattern.

Cisco Unified CallManager opens the Route Pattern Configuration page.

Step 3 Enter the information for the route pattern:

Route Pattern—A pattern that you can transform to the emergency call number, typically a number, a dot, and the emergency call number. For example, 10.911, 11.911, and so forth. The pattern can only contain numbers and dots.

Partition—Select E911.

Numbering Plan—Select the numbering plan for your area.

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

Route Option—Select Route this pattern.

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

Calling Party Transform Mask—Enter the direct inward dial (DID) number you obtained to allow the PSAP in this locale to dial into your network. This is the ELIN number the ERL administrator enters for this route pattern when creating the ERL.

Discard Digits—Select PreDot if you use the suggested pattern, such as 10.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).

Step 4 Click Insert.

Cisco Unified CallManager saves the route pattern. To add additional route patterns, return to Step 2.



Tip Consider developing a detailed naming strategy for the route patterns, because you might end up with a large number of them. For example, you could use a pattern such as xyzzaaab.911, where:

x is a Cisco ER cluster identifier.

y is a Cisco ER group identifier.

zz is the PSAP identifier.

aaa is the ERL identifier.

b is the ELIN identifier (within the ERL).


Related Topics

Creating the Translation Patterns for ELINs

Creating a Cisco Emergency Responder Partition

Understanding the Cisco Unified CallManager Examples

Understanding ERLs

Creating ERLs

Creating the Translation Patterns for ELINs

Create translation patterns that cover the direct inward dial (DID) numbers you are using for ELIN numbers. The PSAP uses these ELINs to call into your network. Cisco Emergency Responder (Cisco ER) needs to intercept these calls so it can route the call to the correct emergency caller. The translation pattern is required so that the a number is prefixed to the ELIN so that it becomes the route point you configured for PSAP callbacks, as explained in the "Creating the Emergency Call Route Points" section.

Before You Begin

Ensure you have a list of all the DIDs you are using for ELINs.

Procedure


Step 1 Select Route Plan > Translation Pattern.

Cisco Unified CallManager opens the Find and List Translation Patterns page.

Step 2 Click Add a New Translation Pattern.

Cisco Unified CallManager opens the Translation Pattern Configuration page.

Step 3 Create the translation pattern:

Translation Pattern—The DID you are using as an ELIN. If you can, use X variables to create a pattern that covers more than one DID (for example, 5555551XXX). If you cannot create a pattern, define translation patterns for each DID separately.

Partition—Select E911.

Numbering Plan—Select the numbering plan for your area.

Calling Search Space—Select E911CSS.

Route Option—Select Route this pattern.

Called Party Transformations, Prefix Digits (Outgoing Calls)—Enter the digits to prefix to the number. Enter the digits you used when creating the PSAP callback route point.

Step 4 Click Insert.

Cisco Unified CallManager saves the translation pattern. To add additional translation patterns, return to Step 2.


Related Topics

Creating the Route Patterns for ELINs

Understanding the Cisco Unified CallManager Examples

Understanding ERLs

Creating ERLs

Creating the Translation Patterns for 9.911

In systems where the external access code is 9, a CTI Route Point of 911 or 9.911 may interfere with the timing of secondary dialtone for users when they are attempting to dial external destinations. The creation of a translation pattern for 911 and 9.911 will eliminate the secondary dialtone timing.

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

Before You Begin

This procedure applies to systems where the external access code is 9. If the external access code is something other than 9, this procedure may not apply.

To complete this procedure, you must have already added the partitions and the calling search space for the Cisco Emergency Responder installation.

Use this procedure to create the translation patterns described in Table 3-2.

Table 3-2 Translation Patterns for External Access Code of 9

Translation Pattern
911
9.911

Partition

Phones

Phones

Calling Search Space

E911CSS

E911CSS

Route Option

Route this pattern

Route this pattern

Provide outside dial tone

Check this box

Check this box

Called Party Transformations, Discard Digits (Outgoing Calls)

None

PreDot


Procedure


Step 1 Select Route Plan > Translation Pattern.

Cisco Unified CallManager opens the Find and List Translation Patterns page.

Step 2 Click Add a New Translation Pattern.

Cisco Unified CallManager opens the Translation Pattern Configuration page.

Step 3 Create the translation pattern:

Translation Pattern—911

Partition—Phones

Numbering Plan—Select the numbering plan for your area.

Calling Search Space—Select E911CSS.

Route Option—Select Route this pattern.

Provide Outside Dial Tone—Make sure this box is checked.

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

Step 4 Click Insert.

Cisco Unified CallManager saves the translation pattern.

Step 5 Repeat Step 2 to Step 4 with the following changes:

Translation Pattern—9.911

Called Party Transformations, Discard Digits (Outgoing Calls)—PreDot


After you have configured the 9.911 translation patterns, you must create the route points. Use the following procedure to create the route points described in Table 3-3.


Note These route points are similar to the route points that you created in the "Creating the Emergency Call Route Points" section. In this case, you enter E911 for the partition instead of RP911.


Table 3-3 Emergency Call Route Points for 9.911 

Route Point Setting
Route Points
Primary Number (911)
Backup Number (912)
ELIN (913)

Device Name

RP911

RP912

RPELIN913

Description

The emergency call number for the area. Cisco ER handles all calls to this number.

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

The destination of all incoming calls from the PSAP. Cisco ER transfers these calls to the emergency caller. Route pattern is prefix (913) plus 10 Xs. Number of Xs should be the same as the standard phone number used in your locale based on your numbering plan.

The number can only consist of numbers and Xs.

Directory Number

911

912

913XXXXXXXXXX

Partition

E911

E911

E911

Calling Search Space

E911CSS

E911CSS

E911CSS

Forward Busy

Destination: 912

CSS: E911CSS

Destination: One of:1

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.2

CSS: E911CSS

Forward No Answer

Destination: 912

CSS: E911CSS

Destination: One of:

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

Forward On Failure

Destination: 912

CSS: E911CSS

Destination: One of:

Route pattern for default ERL.

Onsite security number.

CSS: E911CSS

Destination: Onsite security number.

CSS: E911CSS

1 Configuring call-forwarding numbers for the standby server ensures that calls are either routed to the PSAP servicing the default ERL, or onsite security, if the standby server cannot handle the call. If you do not install a standby server, use these settings for the primary server.

2 Configuring call-forwarding numbers for the ELIN route point ensures that PSAP callbacks go to onsite security if Cisco ER cannot handle the call.


Procedure


Step 1 In Cisco Unified CallManager, select Device > CTI Route Point.

The Find and List CTI Route Points page displays.

Step 2 Click Add a new CTI Route Point.

The CTI Route Point Configuration page displays.

Step 3 Fill in the CTI route point properties:

Enter a unique name, such as RP911, in the Device Name field to identify this as the emergency call number. Table 3-3 shows suggested names, but you can use any name you choose.

Select the appropriate device pool from the Device Pool menu.

Select the calling search space for the route point, as listed in Table 3-3.

Step 4 Click Insert to add the new CTI route point.

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

Cisco Unified CallManager opens the Directory Number configuration page.

Step 5 Enter the configuration for the line you are creating using the information in Table 3-3.

Step 6 Click Insert.

Cisco Unified CallManager adds the line to the device. Repeat this procedure until all devices described in Table 3-3 are configured.

For additional assistance, refer to the documentation and online help included with Cisco Unified CallManager.


Related Topics

Creating the Route Patterns for ELINs

Understanding the Cisco Unified CallManager Examples

Understanding ERLs

Creating Alternate Emergency Call Numbers

If your users are used to dialing 9 (or another number) to get an outside line, they might try to dial the emergency number by first dialing the outside line access number. For example, if the emergency number is 911, they might try to dial 9911. If you want to accommodate these possibilities, configure translation patterns for the numbers you think are likely to be used. This procedure shows how to set up 9911 as an alternate emergency call number.

Procedure


Step 1 Select Route Plan > Translation Pattern.

Cisco Unified CallManager opens the Find and List Translation Patterns page.

Step 2 Click Add a New Translation Pattern.

Cisco Unified CallManager opens the Translation Pattern Configuration page.

Step 3 Create the translation pattern:

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

Partition—Select Phones.

Numbering Plan—Select the numbering plan for your area.

Calling Search Space—Select E911CSS.

Route Option—Select Route this pattern.

Provide Outside Dial Tone—Select this.

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

Step 4 Click Insert.

Cisco Unified CallManager saves the translation pattern. To add additional translation patterns, return to Step 2.


Related Topics

Understanding the Cisco Unified CallManager Examples

Creating a Phone Partition

Creating a Phone Calling Search Space

Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP

You must set up a gateway to use a CAMA or PRI connection to the emergency network or PSTN so that emergency calls can be routed to the local PSAP. See the documentation for your gateway for information on setting up the gateway, and the Cisco Unified CallManager documentation for configuring the gateway. After you set up the gateway, you can follow this procedure to set up the calling search space for the gateway.

Procedure


Step 1 Select Device > Gateway.

Cisco Unified CallManager opens the Find and List Gateways page.

Step 2 Click Find without entering search criteria to list all of the gateways, or enter the search criteria required to list the gateway you want to configure and click Find.

Cisco Unified CallManager lists the gateways that match your criteria.

Step 3 Click the gateway you want to configure.

Cisco Unified CallManager opens the Gateway Configuration page.

Step 4 Select E911CSS for Calling Search Space.

Step 5 Click Update.

Cisco Unified CallManager saves your changes.


Related Topics

Creating a Cisco Emergency Responder Calling Search Space

Obtain CAMA or PRI Trunks to the PSTN

Deploying Cisco Emergency Responder

How Cisco Emergency Responder Fits Into Your Network

Creating Route Patterns for Inter-Cisco Emergency Responder-Group Communications

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

This procedure explains how to create the route pattern for one Cisco ER group. You must create this pattern in the Cisco Unified CallManager clusters that are not supported by the Cisco ER group. Consider the network setup in Figure 3-1.

For inter-group communications to work:

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

You must define the route pattern 1000.911 in Cisco Unified CallManager clusters CCM-C and CCM-D.

You must define the route pattern 2000.911 in Cisco Unified CallManager clusters CCM-A and CCM-B.

In Cisco ER group 1, define 1000.911 as the Inter Cisco ER Group Route Pattern.

In Cisco ER group 2, define 2000.911 as the Inter Cisco ER Group Route Pattern.

These definitions allow a call in an ERL managed by Cisco ER group 2 to be routed to Cisco ER group 2 even though the phone homes to Cisco Unified CallManager cluster CCM-B, which is serviced by Cisco ER group 1.

Figure 3-1 Understanding Inter Cisco Emergency Responder Group Route Patterns

Before You Begin

The dial plans must be unique between all Cisco Unified CallManager clusters supported by a Cisco ER cluster. For example, in the network shown in Figure 3-1, the extension 3003 can only be defined in Cisco Unified CallManager cluster CCM-B.

Procedure


Step 1 Select Route Plan > Route Pattern.

Cisco Unified CallManager opens the Find and List Route Patterns page.

Step 2 Click Add a New Route Pattern.

Cisco Unified CallManager opens the Route Pattern Configuration page.

Step 3 Enter the information for the route pattern:

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

Partition—Select E911.

Numbering Plan—Select the numbering plan for your area.

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

Route Option—Select Route this pattern.

Called Party Transformations, Discard Digits—Select PreDot if you use the suggested pattern, such as 1000.911. If using a different technique, select the appropriate setting and enter a Called Party Transform Mask if necessary (to dial the emergency number).

Step 4 Click Insert.

Cisco Unified CallManager saves the route pattern. To add additional route patterns, return to Step 2.

Step 5 Ensure you define the route pattern in all other Cisco Unified CallManager clusters serviced by Cisco ER groups other than the Cisco ER group whose inter Cisco ER group route pattern you are defining.


Related Topics

Creating a Cisco Emergency Responder Partition

Configuring Group Telephony Settings For the Cisco Emergency Responder Server

Installing Cisco Emergency Responder 1.3(1) on a New System

Creating a Cisco Emergency Responder Cisco Unified CallManager User

You need to add Cisco Emergency Responder (Cisco ER) as a Cisco Unified CallManager user. The settings you enter here are used when you configure the Cisco Unified CallManager settings for Cisco ER.

Procedure


Step 1 In Cisco Unified CallManager, select User > Add a New User.

Cisco Unified CallManager opens the User Information page.

Step 2 Complete the following required fields:

First Name—Use a descriptive name such as "Emergency"

Last Name—Use a descriptive name such as "Responder"

UserID—Use a descriptive name such as "CER"

User Password and Confirm Password—Enter a password and enter it again for confirmation

PIN and Confirm PIN—Enter a PIN and enter it again for confirmation

Enable CTI Application Use—Select this check-box.

Enable Calling Party Modification - Select this if you plan to use "Calling Party Modification" for Cisco ER.

Step 3 Click Insert to create the user.

Cisco Unified CallManager adds the user.

Step 4 Click Device Association in the left-hand column.

Cisco Unified CallManager opens the Assign Devices subpage of the User Information page.

Step 5 Enter search criteria to list the desired route points and CTI ports, or enter nothing to list all devices, and click Select Devices to list the devices.

Step 6 In the list that Cisco Unified CallManager produces, select these devices:

All CTI ports created for Cisco Emergency Responder's use. See the "Creating the Required CTI Ports" section for more information.

The primary emergency call number, for example, 911. Also, select this number as the user's primary extension.

The backup emergency call number, for example, 912.

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

Step 7 Click Update to save your changes.


Related Topics

Creating the Emergency Call Route Points

Creating the Required CTI Ports