Cisco Emergency Responder Administration Guide 8.0
Chapter 6: Using Cisco Emergency Responder with Intrado V9-1-1 Enterprise Services
Downloads: This chapterpdf (PDF - 465.0KB) The complete bookPDF (PDF - 13.77MB) | Feedback

Using Cisco Emergency Responder with Intrado V9-1-1 Enterprise Services

Table Of Contents

Using Cisco Emergency Responder with Intrado V9-1-1 Enterprise Services

How Cisco Emergency Responder Supports Intrado V9-1-1 for Enterprise Service

What Happens When an Emergency Call Is Made with Intrado V9-1-1 for Enterprise Service

Configuring Cisco Emergency Responder to support Intrado V9-1-1 for Enterprise Service

Configuring Intrado VUI Settings

Configuring Intrado Route Patterns on Cisco Emergency Responder

Configuring Intrado ERLs

Importing Intrado ERLs

Exporting Intrado ERL Information

Reconciling ALI Discrepancies

Migrating ERL Data

Migrating Conventional ERL Data to Intrado ERL Data

Migrating Intrado ERL Data to Conventional ERL Data

Setting up Cisco ER to Support Off-Premise Users

Configuring Cisco ER Location Management in Cisco Unified Communications Manager

Configuring the AXL Application User

Configuring AXL Authentication

Configuring Off-Premise ERL

Importing Off-Premises ERLs

Exporting Off-Premise ERL Information

Scheduling Intrado Updates


Using Cisco Emergency Responder with Intrado V9-1-1 Enterprise Services


Cisco Emergency Responder (Cisco ER) 8.0 supports Intrado V9-1-1 for Enterprise Service in the Cisco Unified Communications environment as an alternative to direct connection with the Local Exchange Carrier (LEC). The Intrado V9-1-1 for Enterprise Service provides local routing and emergency service response for Intrado customers. Cisco ER works in conjunction with Intrado to provide emergency services to phones that are located on the corporate network (on-premise) and phones that are located away from the corporate network (off-premise).

For more information on configuring Cisco ER, managing Cisco ER users, working with ERLs, and other related topics, see the "Related Topics" section.

These topics provides an overview of how Cisco ER operates with Intrado V9-1-1 for Enterprise Service and how to configure and use Cisco ER to support Intrado V-9-1-1 Enterprise users.

How Cisco Emergency Responder Supports Intrado V9-1-1 for Enterprise Service

Configuring Cisco Emergency Responder to support Intrado V9-1-1 for Enterprise Service

Migrating ERL Data

Setting up Cisco ER to Support Off-Premise Users

How Cisco Emergency Responder Supports Intrado V9-1-1 for Enterprise Service

If you are a subscriber to IntradoV9-1-1 for Enterprise Service, you can use Cisco ER to simplify emergency call management. Cisco ER provides an interface that allows you to enter and synchronize location information directly to Intrado's database. Cisco ER provides location information for emergency calls for both on-premise phones and off-premise phones and works with Intrado and Cisco Unified CM to complete emergency calls.

Cisco ER tracks IP phones by the IP subnet or when someone manually configures and assigns the MAC Address. Cisco ER maintains the status of the phones (on-premise, off-premise, unlocated), and passes on any ALI/ELIN information to Intrado. Users with on-premise phones rely on Cisco Unified Communications to route their emergency calls to Intrado and the designated emergency provider.

Users with off-premise phones cannot make emergency calls until the users enter in their location and associate this information with their directory number. Once the location information has been verified, emergency calls placed from off-premise phones can be completed.


Note Users can only configure one off-premise location for each DN. This applies to shared lines. If two off-premise phones share a DN, the user can only associate one location to the DN.


Figure 6-1 shows the interactions between users, Cisco ER, and Intrado.

Figure 6-1 Understanding the Interactions between Users, Cisco ER, and Intrado

What Happens When an Emergency Call Is Made with Intrado V9-1-1 for Enterprise Service

When a user makes an emergency call:

1. Cisco Unified CM routes the call to Cisco ER.

2. Cisco ER routes the call to Intrado.

3. Intrado receives the 10-digit ELIN for the calling party and fetches the ALI data for the caller from this calling party number.

4. Intrado completes the call.

Configuring Cisco Emergency Responder to support Intrado V9-1-1 for Enterprise Service

Once you have confirmed your emergency service support with Intrado, you must configure Cisco ER to support Intrado V9-1-1 for Enterprise Service.

You must complete the tasks described in Table 6-1 prior to creating Intrado ERLs. For additional information on supporting off-premise users, see the "Setting up Cisco ER to Support Off-Premise Users" section.

Table 6-1 Task List for Configuring Cisco ER for Intrado 

Task
Description
Notes

1.

Configure the following in the Validation and Update Interface (VUI).

a. Upload the certificate provided by Intrado.

b. Validate the certificate.

c. Configure Intrado Account Information.

See the "Configuring Intrado VUI Settings" section.

2.

Configure Route Patterns for routing calls to Intrado on the Cisco ER server.

See the "Configuring Intrado Route Patterns on Cisco Emergency Responder" section.

3.

Configure Route Patterns and gateway for routing calls to Intrado on Cisco Unified CM server.

Refer to the "Understanding Route Plans," chapter in Cisco Unified CM System Guide and the "Gateway Configuration," chapter in the Cisco Unified CM Administration Guide.

4.

Create Intrado ERL and verify the validity and consistency of the ALI data for the Intrado ERL against the Intrado TN database.

See the "Configuring Intrado ERLs" section and the "Reconciling ALI Discrepancies" section.

5.

Assign Intrado ERLs to switch ports, IP Subnets, and Unlocated phones.

For information on assigning ERLs to switch ports, see the "Configuring Switch Ports" section on page 5-52.

For information on assigning ERLs to IP subnets, see the "Configuring IP Subnet-based ERLs" section on page 5-37.

For information on assigning ERLs to unlocated phones, see the "Identifying Unlocated Phones" section on page 5-57.


Configuring Intrado VUI Settings

Before you can configure Intrado VUI settings, you must have your account information and a certificate from Intrado.


Note To continue emergency service support when there is a failover to the Cisco ER subscriber, you must upload the certificate file to the CER subscriber seperately.


To configure Intrado VUI settings, follow these steps:

Procedure


Step 1 From Cisco ER, choose System >  Intrado VUI Settings.

The Intrado VUI Settings page displays.

Step 2 Click Upload Certificate. An Upload Certificate window opens. Use the Browse button to locate the Intrado certificate file, highlight the file, and click the Upload button.

Step 3 Enter the Certificate Password and the VUI URL in the adjacent text boxes. Click Test and Validate.

Step 4 Enter the Account Information.

VUI Schema URL

Intrado Account ID

Max VUI Connections

Step 5 Click Update.

For more information on the Intrado VUI settings, see "Intrado VUI Settings" section on page A-12.


Related Topics

Configuring Intrado Route Patterns on Cisco Emergency Responder

Configuring Intrado ERLs

Reconciling ALI Discrepancies

Configuring Intrado Route Patterns on Cisco Emergency Responder

Before any emergency calls can be completed by Intrado V9-1-1 for Enterprise Service, you must configure the route patterns for routing the call to Intrado.

To create a route pattern for Intrado, follow these steps:

Procedure


Step 1 From Cisco ER, Choose System >Telephony Settings.

The Telephony Settings page displays.

Step 2 Under Intrado Route Pattern Settings, enter the Intrado Route/ Translation Pattern and click the Add button.


Configuring Intrado ERLs

You must first configure Intrado route patterns before you can add any Intrado ERLs.


Note Intrado ERLs differ from conventional ERLs in the following ways:

You can only select route patterns from a pre-configured list in the Telephony Settings webpage.

You can query and validate ALI data from Intrado by using Intrado VUI (Validation & Update interface).

You must submit ALI data (TN Update) to Intrado by using Intrado VUI before an emergency call can be successfully routed.


To set up the Intrado ERL, follow these steps:

Procedure


Step 1 From Cisco ER, choose ERL>Intrado ERL>Intrado ERL(Search and List).

The Find Intrado ERL Data page displays.

Step 2 Click the Add New ERL button.

Cisco ER opens the Add New ERL window. See Intrado ERL (Search and List), page A-30 for a detail explanation of each field.

Step 3 Fill in the ERL Information.

Step 4 Click ALI Details

Cisco ER opens the ALI Information window.

Step 5 Enter the ALI Information. To look up an address in the Intrados MSAG database, click Query from Intrado.

Step 6 When finished entering in the ALI Information, click Pre-validate from Intrado.

Step 7 Make the Add New ERL window the active window if it is not, and click Insert.

Cisco ER saves the ERL and its ALI.


Importing Intrado ERLs

If you have multiple ERLs, and you want to add them all at once, you can create a file that contains more than one ERL definition, and import all the ERLs at the same time into your Cisco ER configuration. For more information on importing ERLs, see Importing Several ERLs at Once, page 5-35.

Exporting Intrado ERL Information

Use the Export ERL page to create ERL export files for our own use, for example, to back up or move an ERL configuration. For more information on importing ERLs, see Exporting ERL Information, page 5-40.

Related Topics

Configuring Intrado VUI Settings

Configuring Intrado Route Patterns on Cisco Emergency Responder

Reconciling ALI Discrepancies

Reconciling ALI Discrepancies

You can use Cisco ER to compare the records from Intrado VUI with the records in it's database and displays ALI records that have discrepancies. You can examine each record and choose to update the local record with information from Intrado or update Intrado's record.

To reconcile ALI discrepancy records, follow these steps:

Procedure


Step 1 In Cisco ER Administration, choose ERL>Intrado  ERL>View ALI Discrepancies.

The View Intrado ALI Discrepancies page appears.

Step 2 Enter search criteria to find any specific ELINS and click Find, or click Find without any search criteria to display all Intrado ALI discrepancies. The search results appear.

Step 3 Click on the radio button next to the ELIN that you want to view or click on the View ALI Discrepancies button to launch the View Intrado ALI discrepancies for a particular ELIN.

The View Intrado ALI Discrepancies for a particular ELIN window appears.

Step 4 Choose the correct data from either the local Cisco ER database or from Intrado.

Step 5 To save changes to the local Cisco ER database, click Save. To save changes to Intrado VUI, click Save Intrado ALI Info.

Step 6 To close this window, click Close.


Related Topics

Configuring Intrado VUI Settings

Configuring Intrado Route Patterns on Cisco Emergency Responder

Configuring Intrado ERLs

Migrating ERL Data

Cisco ER supports migrating existing conventional ERLs to Intrado ERLs and vice versa.

Migrating Conventional ERL Data to Intrado ERL Data

To migrate conventional ERLs to Intrado ERLs, follow these steps:

Procedure


Step 1 In Cisco ER Administration, choose ERL>ERL Migration Tool.

The ERL Migration Tool page appears.

Step 2 Choose Conventional ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 3 Select the ERLs that you wish to migrate by checking the checkbox next to the ERL name.

The Enter Route Patterns for ERL Migration window appears.

Step 4 Choose an updated route pattern from the drop-down menu.

Step 5 Click on Migrate to Intrado ERL.


Related Topics

Configuring Cisco Emergency Responder to support Intrado V9-1-1 for Enterprise Service

Migrating Intrado ERL Data to Conventional ERL Data

Migrating Intrado ERL Data to Conventional ERL Data

To migrate Intrado ERLs to conventional ERLs, follow these steps:

Procedure


Step 1 In Cisco ER Administration, choose ERL> ERL Migration Tool.

The ERL Migration Tool page appears.

Step 2 Choose Intrado ERL in the search parameter drop-down box, enter the search criteria, and click Find.

Step 3 Select the ERLs that you wish to migrate by checking the checkbox next to the ERL name.

The Enter Route Patterns for ERL Migration window appears.

Step 4 Enter an updated route/pattern translation pattern in the adjacent text box.

Step 5 Click on Migrate to Conventional ERL.


Related Topics

Migrating Conventional ERL Data to Intrado ERL Data

Understanding ERLs, page 5-28

Setting up Cisco ER to Support Off-Premise Users

Cisco Emergency Responder 8.0 allow users, who are located outside of the corporate network (off-premise) to make emergency calls. Off-premise emergency call support requires the following:

Cisco Emergency Responder 8.0

Cisco Unified CM 7.0 or later version.

Intrado V9-1-1 Enterprise Services

Complete the following tasks to set up Cisco ER support for off-premise users:

Table 6-2 Task List for configuring Off-Premise Users

Task
Description
Notes

1.

Configure Cisco ER for use with Intrado.

See Configuring Cisco Emergency Responder to support Intrado V9-1-1 for Enterprise Service.

2.

Enable Cisco ER Location Management in Cisco Unified CM for off-premise support.

See Configuring Cisco ER Location Management in Cisco Unified Communications Manager.

3.

Configure the AXL application user for CER in Cisco Unified CM.

See Configuring the AXL Application User.

4.

Configure AXL authentication with Cisco Unified Communications Manager.

See Configuring AXL Authentication.

5.

Configure Off-Premise ERLs.

See Configuring Off-Premise ERL.

6.

Assign off-premise ERLs to IP subnets and unlocated phones.

For information on assigning ERLs to IP subnets, see "Configuring IP Subnet-based ERLs" section on page 5-37.

For information on assigning ERLs to unlocated phones, see "Identifying Unlocated Phones" section on page 5-57.

Note You cannot assign off-premise ERLs to switch ports.


Once you have configured the off-premise ERLs, users can enter their location information for off-premise phones from the Cisco Unified CM User Option page.

Related Topics

Configuring Cisco ER Location Management in Cisco Unified Communications Manager

Configuring the AXL Application User

Configuring AXL Authentication

Configuring Off-Premise ERL

Configuring Cisco ER Location Management in Cisco Unified Communications Manager

You must configure the Cisco ER Location Management server on the Cisco Unified CM server before your users can use it to enter their off-premise locations.

To enable Cisco Emergency Location Manager in Cisco Unified CM, follow these steps:

Procedure


Step 1 From Cisco Unified CM Administration, choose System > Application Server.

Step 2 Click the Add New button.

The Application Server Configuration page displays.

Step 3 From the Application Server Type drop-down box, choose CER Location Management. Click Next.

Step 4 Enter a name that identifies Cisco ER Off-Premise application.

The name is displayed in the navigation drop-down box on the User Option page and will be selected by the user to navigate to the Cisco ER Off-Premise page.

Step 5 Enter the URL for the Cisco ER Off-Premise page. The URL takes the form of http://cer_host/ofpuser, where cer_host is the name or IP address of the Cisco ER publisher or Cisco ER subscriber.


Note You must enter both the Cisco ER publisher and Cisco ER subscriber as separate application servers on Cisco Unified CM Administration.


Step 6 Click Save.


Related Topics

Configuring the AXL Application User

Configuring AXL Authentication

Configuring Off-Premise ERL

Configuring the AXL Application User

You must configure the AXL application user for Cisco ER on Cisco Unified CM, so that an off-Premises user can log in to the CER's off-premises user website.

To configure the AXL application, follow these steps:

Procedure


Step 1 In Cisco Unified Communications Manager, choose User Management > Application User. Click the Add New button.

Cisco Unified Communications Manager displays the Application User Configuration page.

Step 2 Complete the following required fields:

User ID—Use a descriptive name such as "AXL Application User."

Password—Enter a password for this user.

Confirm Password—Re-enter the password for this user.

Step 3 Click Save.

Step 4 In the Cisco Unified Communications Manager menu at the top, choose User Management > User Group.

The user group search page appears.

Step 5 At search criterion, enter standard and click Find.

The list of user groups starting with the name standard appears.

Step 6 Click the Standard CCM Admin Users link to display the User Group configuration page.

Step 7 Click Add App Users to Group.

The Find and List Application Users pop-up window appears.

Step 8 Enter the User ID created in Step 2 as the search criterion and click Find.

The list of Applications users appears.

Step 9 Click the checkbox next to the user ID and click Add Selected.

Cisco Unified Communications Manager adds the selected user to the Standard CCM Admin Users user group.

Step 10 Choose User Management > User Group.

The user group search page appears.

Step 11 Enter standard as the search criterion and click Find.

The list of user groups starting with the name Standard appears.

Step 12 Click the Standard TabSync User group.

Step 13 To add the user to the Standard TabSync User group and to, repeat steps 7 through 9.

Step 14 Choose User Management > User Group.

The user group search page appears.

Step 15 Enter standard as the search criterion and click Find.

The list of user groups starting with the name Standard appears.

Step 16 Click the Standard RealtimeAndTraceCollection group.

Step 17 Repeat steps 7 through 9 to add the user to the Standard RealtimeAndTraceCollection group.


Configuring AXL Authentication

To configure AXL authentication between Cisco ER and Cisco Unified Communications Manager, follow these steps:


Step 1 From Cisco ER, choose Phone Tracking > Cisco Unified Communications Manager.

Step 2 Under AXL Setting, enter the following information:

AXL Username

AXL Password

AXL Port Number

Step 3 Click Insert.


Configuring Off-Premise ERL

Unlike conventional ERLs, off-premise ERLs do not need to enter ELIN or ALI information. The ERL for a phone is tracked by it's IP subnet and the phone's MAC address assignment.


Note You can only assign off-premise ERLs to IP subnets, unlocated phones, and manual phones. You can not assign off-premise ERLs to switch ports.


To configure an off-premise ERL, follow these steps:

Procedure


Step 1 From Cisco ER, choose ERL> Off-Premises ERL> Off-Premises ERL (Search and List)

Step 2 Click on the Add New ERL button.

Step 3 Fill in the following information in the Add New ERL window and click Insert.

ERL Name

Description

Intrado route pattern/translation Pattern

Onsite Alerts

Fill in the information in the Add New ERL window. See the "Off-Premises ERL (Search and List)" section on page A-26 for detailed explanations of each field.


Note You must add Intrado route patterns before you can add off-premise ERLs.



Importing Off-Premises ERLs

If you have multiple ERLs, and you want to add them all at once, you can create a file that contains more than one ERL definition, and import all the ERLs at the same time into your Cisco ER configuration. For more information on importing ERLs, see Importing Several ERLs at Once, page 5-35.

Exporting Off-Premise ERL Information

Use the Export ERL page to create ERL export files for our own use, for example, to back up or move an ERL configuration. For more information on importing ERLs, see Exporting ERL Information, page 5-40.

Scheduling Intrado Updates

You can create ALI and Secondary Status update schedules between Cisco ER and Intrado. A scheduled ALI update sends newly created TN records to Intrado. A scheduled Secondary Status update sends queries to Intrado requesting information on records with errors that have been corrected.

To Add a scheduled update between Cisco ER and Intrado, follow these steps:

Procedure


Step 1 From Cisco ER, choose ERL>Intrado ERL>Intrado Schedule.

The Intrado Schedule page appears.

Step 2 Choose the days of the week and the time of day that you want to schedule an update.

Step 3 Check the Enable Schedule box if you want to activate this schedule.

Step 4 Choose either ALI Update Schedule or Secondary Status Update Schedule.

Step 5 Click Add to add the schedule to the list of schedules


To update a scheduled update between Cisco ER and Intrado, follow these steps:

Procedure


Step 1 From Cisco ER, choose ERL>Intrado ERL>Intrado Schedule.

The Intrado Schedule page appears.

Step 2 Click the Edit link adjacent to the schedule that you want to update.

Step 3 Choose the days of the week and the time of day.

Step 4 To activate this schedule, check the Enable Schedule box.

Step 5 Click Update to change the schedule on the list of schedules.


Related Topics

Overview of Cisco Emergency Responder Configuration, page 5-1

Managing Cisco Emergency Responder Users, page 5-9

Managing Cisco Emergency Responder Roles, page 5-13

Managing Cisco Emergency Responder User Groups, page 5-15

Logging Into and Out of Cisco Emergency Responder, page 5-18

Configuring Servers and Server Groups, page 5-20

Configuring the Cisco Emergency Responder Cluster and Cluster DB Host, page 5-27

Changing the Cisco Unified Communications Manager Cluster Identified with Cisco Emergency Responder, page 5-27

Working with Emergency Response Locations, page 5-28

Configuring Switches for Cisco Emergency Responder, page 5-43

Managing Phones, page 5-52

Secondary Status, page A-32

Intrado Schedule, page A-33