Posted by: Mudassir Ali | May 26, 2010

Cisco Emergency Responder

On Cisco Emergency Responder, emergency calls are not routed to the correct PSAP

Core Issue

There are several possible causes for emergency calls to not route to the correct Public Safety Answering Point (PSAP).

Resolution

Check whether the route patterns used for the Emergency Response Location (ERL) from which the call was made and for the default ERL are configured and use the correct partitions and calling search spaces. Refer to the Creating the Route Patterns for emergency location identification numbers (ELINs) section of Configuring Cisco CallManager for Cisco Emergency Responder.

Ensure that the partitions and calling search spaces for the gateways are correct. Refer to the Configuring the Calling Search Space for the Gateways Used to Connect to the PSAP section of Configuring Cisco CallManager for Cisco Emergency Responder.

If an emergency call successfully leaves your network but does not get routed to the correct PSAP, refer to these possible points of failure:

Is Cisco Emergency Responder configured to assign the correct Emergency Location Identification Number (ELIN) to the ERL assigned to the phone? Emergency calls are routed based on the ELIN, so if you assign the wrong ELIN, the call is not routed correctly. Refer to the Creating ERLs section of Configuring Cisco Emergency Responder.

 If the ELIN is correct, is the ELIN’s route pattern configured to use the correct gateway? If you select the wrong gateway, the call might be routed to a part of the service provider’s network that cannot connect to the desired PSAP. Consult with your service provider to determine gateway requirements. Refer to the following topics:

 The Setting Up the ELIN Numbers to Route Emergency Calls and Enable PSAP Callbacks section of Configuring Cisco CallManager for Cisco Emergency Responder.

 The Deploying Cisco Emergency Responder in One Main Site with Two or More PSAPs section of Planning for Cisco Emergency Responder

 Does the service provider’s automatic location information (ALI) database contain the correct information for the ELIN? Emergency call routing outside your network is based on the information in the service provider’s database, not on the information in your local network. Refer to the Exporting ERL and ALI Information for Submission to Your Service Provider section of Configuring Cisco Emergency Responder.

 Does the emergency caller’s phone register with a Cisco CallManager cluster supported by a different Cisco Emergency Responder group than the Cisco Emergency Responder group that supports the originating switch port? Then you might have a miss-configured Cisco Emergency Responder cluster.

Note: If the call reaches the PSAP, but the PSAP cannot talk to the caller, ensure that the Cisco CallManager for the remote Cisco Emergency Responder group has the Cisco CallManager for the local Cisco Emergency Responder group defined as a gateway.

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 on page 5-28 for information about ERLs.

To create the route patterns for ELINs, follow these steps:

Procedure

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: