Guest

Cisco PGW 2200 Softswitch

E911 Mapping on the MGC 2200

  • Viewing Options

  • PDF (376.5 KB)
  • Feedback
E911 Mapping on the MGC 2200

Table Of Contents

E911 Mapping on the MGC 2200

Feature Overview

Benefits

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites for Using this Feature

Provisioning Procedures

Provisioning This Feature

Adding an E911PROF Result Type

Modifying an E911PROF Result Type

Deleting an E911PROF Result Type

Reference Information

Planning for Provisioning

Collecting E911PROF Data

Mapping Methods

Provisioning Basics

Starting a Provisioning Session

Saving and Activating Your Provisioning Changes

Ending a Provisioning Session Without Activating Your Changes

Retrieving Provisioning Data

Dial Plan Prerequisites

Dial Plan Basics

Adding Dial Plan Data

Modifying an Element of Your Dial Plan Data

Deleting an Element from Your Dial Plan Data

Retrieving Dial Plan Data

Retrieving Data for an Individual Component

Retrieving Data for All Components of a Particular Type

Result Type Definitions

Result Type Definition

Cause and Location Codes

Internal Cause Codes

Internal Cause Code Values

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Glossary


E911 Mapping on the MGC 2200


Document Release History

Publication Date
Comments

October 17, 2005

Initial version of the document.


Feature History

Release
Modification

9.5(2)

This feature was introduced on the Cisco MGC 2200 software Release 9.5(2)


This document describes the E911 Mapping on the MGC 2200 feature.

This feature is described in the following sections:

Feature Overview

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites for Using this Feature

Provisioning Procedures

Reference Information

Reference Information

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Glossary

Feature Overview

This feature provides support on the Cisco MGC to connect emergency calls that originated in a SIP network to the appropriate selective router (SR) connected to the Public Safety Answering Points (PSAPs). This feature on the Cisco MGC introduces a mapping table to support the various IAM formats or Centralized Automatic Message Accounting (CAMA) signaling that is required by the SRs in North America, including the sending of the Emergency Services Query Key (ESQK), which is used by the PSAP to find the calling party location and call-back numbers.

This feature

Supports mapping from an emergency call information from Session Initiation Protocol (SIP) message to ISDN User Part (ISUP).

Uses the Emergency Services Routing Number (ESRN) to select the outgoing route.

Benefits

Provides Connectivity Between SIP-based VoIP Networks and Existing Emergency Service Networks

Related Documents

This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are listed below:

Release Notes for Cisco Media Gateway Controller Software Release 9.5(2)

Cisco Media Gateway Controller Hardware Installation Guide

Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller

Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide

Cisco Media Gateway Controller Software Release 9 Provisioning Guide

Cisco Media Gateway Controller Software Release 9 Dial Plan Guide

Cisco Media Gateway Controller Software Release 9 MML Command Reference

Cisco Media Gateway Controller Software Release 9 Messages Reference Guide

Cisco Media Gateway Controller Software Release 9 Billing Interface Guide

Cisco Media Gateway Controller Software Release 9 Management Information Base Guide

Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide

Supported Platforms

The hardware platforms supported for the Cisco MGC software are described in the Cisco Media Gateway Controller Hardware Installation Guide.

Supported Standards, MIBs, and RFCs

Standards

No new or modified standards are supported by this feature.

MIBs

No new or modified MIBs are supported by this feature.

For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Management Information Base Guide.

RFCs

No new or modified RFCs are supported by this feature.

Prerequisites for Using this Feature

You must have Cisco Media Gateway Controller (MGC) software Release 9.5(2) and 9.5(2) patches gs041 and nn034. Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2).

In North America, for the MGC to support mapping from an emergency SIP message to ISUP, the SIP message must be in the following format: Request-URI = ESRN; FROM = Call Back Number (CBN); TO = 911; RPID = ESQK; PAI = ESQK.


Note ESQK is used for service providers that provide roaming capabilities to their subscribers.


The MGC uses the ESRN to select the appropriate SR. The SR can be connected by either ISUP or CAMA signaling.

For CAMA, the SIP INVITE is sent unchanged to an IOS gateway identified by IP address (or (Fully Qualified Domain Name (FQDN)) contained in the MGC SIP trunk. The IOS gateway provides SIP to CAMA mapping.

For ISUP, a dial plan result type provides the appropriate SR ISUP option from the E911 mapping table, as shown in Table 1. and Table 2

Provisioning Procedures

You must modify the provisioning data of your system to enable this feature. Before you begin provisioning this feature, we recommend that you plan your provisioning changes, as described in the "Planning for Provisioning" section.


Tip You can find information on starting and ending provisioning sessions and retrieving provisioning data in the "Provisioning Basics" section.


The following section describes the provisioning tasks related to this feature:

Provisioning This Feature

Provisioning This Feature

Provision the E911 Mapping on the MGC 2200 by setting the E911PROF result type dataword1 to a value from 1 through 35.

The MML provisioning command numan-add is used to define the E911PROF result type in a result table.


numan-<verb>:resulttable:custgrpid="<customer group id>",name="<result name>", 
resulttype="E911PROF",setname="<resultsetname>" 

This section covers the following provisioning topics:

Adding an E911PROF Result Type

Modifying an E911PROF Result Type

Deleting an E911PROF Result Type

Adding an E911PROF Result Type

To add an E911PROF result type to your provisioning data, perform the following steps:


Step 1 Start a provisioning session, as described in the "Starting a Provisioning Session" section.

Step 2 Enter the following command to add the E911PROF result type:

mml> numan-add:resulttable:custgrpid="T002",name="routetoSR",resulttype="E911PROF",dw1="1"
,setname="selectiverouter1" 

Where:

custgrpid—The name of a previously defined customer group ID. A string of four alphanumeric characters that uniquely defines the customer. The customer group ID should begin with a letter.

name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.

resulttype—The result type name.

dw1—The value of the IAM profile mapping. Valid profile values can be found in Table 4.

Step 3 Repeat Step 2 for each E911PROF result type you want to add to your provisioning data.

Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating Your Provisioning Changes" section.


Modifying an E911PROF Result Type

To modify an E911PROF result type, perform the following steps:


Step 1 Start a provisioning session, as described in the "Starting a Provisioning Session" section.

Step 2 Enter the following command to modify the E911PROF result type:

mml> numan-ed:resulttable:custgrpid="T002",name="result70",resulttype="E911PROF",dw1="11",
setname="selectiverouter1" 

Where:

custgrpid—The name of a previously defined customer group ID. A string of four alphanumeric characters that uniquely defines the customer. The customer group ID should begin with a letter.

name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.

resulttype—The result type name.

dw1—The value of the IAM profile mapping. Valid profile values can be found in Table 4.

Step 3 Repeat Step 2 for each E911PROF result type you want to modify.

Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating Your Provisioning Changes" section.


Deleting an E911PROF Result Type

To delete an E911PROF result type from your provisioning data, perform the following steps:


Step 1 Start a provisioning session, as described in the "Starting a Provisioning Session" section.

Step 2 Enter the following command to delete the E911PROF result type:

mml> numan-dlt:resulttable:custgrpid="T002",name="result70",resulttype="E911PROF",dw1="11"
,setname="selectiverouter1" 

Where:

custgrpid—The name of a previously defined customer group ID. A string of four alphanumeric characters that uniquely defines the customer. The customer group ID should begin with a letter.

name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.

resulttype—The result type name.

dw1—The value of the IAM profile mapping. Valid profile values can be found in Table 4.

Step 3 Repeat Step 2 for each E911PROF result type you want to delete.

Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating Your Provisioning Changes" section.


Reference Information

The following sections contain reference material related to this feature:

Planning for Provisioning

Provisioning Basics

Dial Plan Prerequisites

Dial Plan Basics

Result Type Definitions

Result Type Definitions

Cause and Location Codes

Planning for Provisioning

This section lists the data that you must gather to successfully provision this feature. For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Collecting E911PROF Data

The E911PROF result type represents the types of SR with which the MGC communicates. You must know the following about the SR:

ESRK delivery (See Table 1)

CPN and ESRD delivery (See Table 2)

Mapping Methods

Since the MGC does not support CAMA signaling natively, the CAMA interface is provided by an IOS gateway. Thus, after analyzing the ESRN number, MGC proxies the INVITE message from the SIP call server to the IOS gateway. The IOS gateway then routes the call to SR using CAMA signaling.

Depending on the version of SR and PSAP, the location key (ESQK) is delivered in a different parameter of the Initial Address Message (IAM). The MGC implements the following mapping methods:

Mapping method 1, ESRK, which is equivalent to ESQK in a Voice over IP (VoIP) network

Mapping method 2, ESRD, which is equivalent to ESQK in a VoIP network

The various IAM profiles are listed in Table 1 for ESRK delivery and in Table 2 for ESRD delivery.

Mapping Method 1: ESRK Delivery

Originally based on ESRK, Table 1 shows the possible alternatives for populating the parameters in the IAM. Mapping method 1 describes the mode where a Mobile Switching Center (MSC) uses ISUP protocol to send an ESRK to an E9-1-1 SR.

Table 1 ESRK Delivery 

ISUP Parameter Option
OLI Wireless
CpCAT Emergency
CDPN
CPN
CHGN
GDP
Note(s)

A1

No

Yes

911

ESRK

ESRK

Blank

1, 2

A2

No

Yes

911

ESRK

Blank

1, 2

A3

No

Yes

911

ESRK

Blank

1, 2

B1

No

No

911

ESRK

ESRK

Blank

1, 2

B2

No

No

911

ESRK

Blank

1, 2

B3

No

No

911

ESRK

Blank

1, 2

Note

1. This ISUP parameter option is widely supported in North America. It is estimated that 95% of the E9-1-1 SRs deployed in North America support this option when the SR has been equipped with wireless E9-1-1 features.

2. Blank—This parameter must not be populated.


Mapping Method 2: CBN and ESRD Delivery

Mapping method 2 describes the mode where an MSC uses the ISUP protocol to send the caller's CBN and ESRD to an E9-1-1 SR. Table 2 shows the possible alternatives for populating the parameters in the IAM.

Table 2 CBN and ESRD Delivery 

ISUP Parameter Option
OLI Wireless
CpCAT Emergency
CDPN
CPN
CHGN
GDP
Note(s)

A1

Yes

Yes

911

CBN

CBN

ESRD1

1

A2

Yes

Yes

911

CBN

ESRD

1

A3

Yes

Yes

911

CBN

ESRD

1

B1

Yes

No

911

CBN

CBN

ESRD

3

B2

Yes

No

911

CBN

ESRD

3

B3

Yes

No

911

CBN

ESRD

3

C1

No

Yes

911

CBN

CBN

ESRD

3

C2

No

Yes

911

CBN

ESRD

3

C3

No

Yes

911

CBN

ESRD

3

D1

No

No

911

CBN

CBN

ESRD

3

D2

No

No

911

CBN

ESRD

3

D3

No

No

911

CBN

ESRD

3

E1

Yes

Yes

ESRD

CBN

CBN

Blank

1, 2

E2

Yes

Yes

ESRD

CBN

Blank

1, 2

F1

Yes

No

ESRD

CBN

CBN

Blank

2, 3

F2

Yes

No

ESRD

CBN

Blank

2, 3

G1

No

Yes

ESRD

CBN

CBN

Blank

2, 3

G2

No

Yes

ESRD

CBN

Blank

2, 3

H1

No

No

ESRD

CBN

CBN

Blank

2, 3

H2

No

No

ESRD

CBN

Blank

2, 3

I1

Yes

Yes

ESRD

CBN

CBN

ESRD

1

I2

Yes

Yes

ESRD

CBN

ESRD

1

I3

Yes

Yes

ESRD

CBN

ESRD

3

J1

Yes

No

ESRD

CBN

CBN

ESRD

3

J2

Yes

No

ESRD

CBN

ESRD

3

K1

No

Yes

ESRD

CBN

CBN

ESRD

3

K2

No

Yes

ESRD

CBN

ESRD

3

L1

No

No

ESRD

CBN

CBN

ESRD

3

L2

No

No

ESRD

CBN

ESRD

3

Note

1. This ISUP parameter option is widely supported in North America. It is estimated that 95% of the E9-1-1 SRs deployed in North America support this option when the SR has been equipped with wireless E9-1- 1 features.

2. Blank—This parameter must not be populated.

3. This ISUP parameter option is available in some areas. It is estimated that 50% of the E9-1-1 SRs deployed in North America support this option when the SR has been equipped with wireless E9-1-1 features.

1 ESRD, in a mobile network, is equivalent to ESQK. in a VoIP network.


 

Provisioning Basics

The procedures in this section are for starting a provisioning session and saving and activating the changes you have made.

Starting a Provisioning Session

Saving and Activating Your Provisioning Changes

Ending a Provisioning Session Without Activating Your Changes

Retrieving Provisioning Data

For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Starting a Provisioning Session

You might need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-sta::srcver="curr_ver",dstver="mod_ver"

Where:

curr_ver—The name of the current configuration version. In place of the name of the current configuration version, you can also enter:

new—A new default session configuration; no existing source configuration is available.

active—Selects the active configuration as the source for configuration changes.


Note If you do not know the name of your current configuration session, you can use the procedure described in the "Retrieving Data on the Current Provisioning Session" section on page 7.


mod_ver—A new configuration version that contains your provisioning changes.

For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you enter the following command:

prov-sta::srcver="ver1",dstver="ver2"

Once a provisioning session is underway, you can use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, or delete components on your system. This document describes how to provision this feature. For more information on provisioning other components on your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

There are two ways to close your provisioning session: saving and activating your provisioning changes, as described in the "Saving and Activating Your Provisioning Changes" section or ending your provisioning session without saving and activating your changes, as described in the "Ending a Provisioning Session Without Activating Your Changes" section.

Saving and Activating Your Provisioning Changes

When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.


Caution Using the prov-cpy or prov-dply MML command can severely impact your system's call processing performance, depending on the extent of your provisioning changes. We recommend that these commands be issued during a maintenance window when traffic is minimal.

The prov-cpy MML command is used to save and activate your changes on simplex Cisco MGC (single host) systems.


Note When you enter the prov-cpy command, your provisioning session is also automatically ended. If you want to make additional provisioning changes, you must start a new provisioning session as described in the "Starting a Provisioning Session" section.



Caution Do not use the prov-cpy command to save and activate your changes on a continuous-service Cisco MGC (active and standby hosts) system. Saving and activating using prov-cpy on such a system would require using the prov-sync MML command to synchronize the provisioning data on the active and standby hosts. The system does not indicate when the synchronization process fails, which would create problems when a switchover operation occurs.

The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs in a continuous-service system. This command should not be used on a Cisco MGC in a simplex configuration.


Note When you enter the prov-dply command, your provisioning session is also automatically ended, unless an error occurs during execution. If you want to make additional provisioning changes, you must start a new provisioning session, as described in the "Starting a Provisioning Session" section.


Ending a Provisioning Session Without Activating Your Changes

If you want to end a provisioning session without saving and activating the changes you have entered, enter the prov-stp MML command. This command ends your current provisioning session and your changes are not entered.

Retrieving Provisioning Data

You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways you can use this command to retrieve provisioning data are described in the following sections:

Retrieving Data for an Individual Component

Retrieving Data for All Components

Retrieving Data for All Components of a Particular Type

Retrieving Data on the Current Provisioning Session

Retrieving Data on Supported Signaling Protocols

Retrieving Data for an Individual Component

You can retrieve provisioning data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-rtrv:component:name=MML_name

Where:

component—The MML component type associated with the desired component. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

MML_name—The MML name for the desired component. You can determine the MML names for the various components using the prov-rtrv:all MML command.

For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you would enter the following command:

prov-rtrv:ss7path:name="ss7svc1"

The response to the command is dependent upon the component type associated with the desired component. For example, to view the properties for an SUA routing key called suakey1, you would enter the following command:

prov-rtrv:suakey:name="suakey1"

Retrieving Data for All Components

You can retrieve data for all of the components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-rtrv:all

Retrieving Data for All Components of a Particular Type

You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-rtrv:component:"all"

Where: component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

For example, to view the provisioning data for all SS7 signaling services, you would enter the following command:

prov-rtrv:ss7path:"all"

Retrieving Data on the Current Provisioning Session

You can retrieve data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-rtrv:session

The system returns a response similar to the following:

MGC-02 - Media Gateway Controller 2005-01-13 13:39:19
M  RTRV
   "session=jtest:session"
   /*
Session ID = mml1
SRCVER = active
DSTVER = jtest
   */

Retrieving Data on Supported Signaling Protocols

You can retrieve protocol data for the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

prov-rtrv:variants

Dial Plan Prerequisites

This section lists the data that you must gather to successfully create a dial plan as part of this feature. For more information on planning dial plans for other functions of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Dial Plan Basics

The procedures in this section describe how to add, modify, and delete dial plan data and how to retrieve that data.

Adding Dial Plan Data

Modifying an Element of Your Dial Plan Data

Ending a Provisioning Session Without Activating Your Changes

Retrieving Provisioning Data

For more detailed information about creating a dial plan for your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Adding Dial Plan Data

The order in which you provision dial plan tables is important. Many tables refer to other tables that must be defined first. The following list identifies the recommended sequence for dial plan provisioning:

1. Create the dial plan file (unique CustGrpID)

2. Provision digit modification

3. Provision the Service

4. Provision the result and result sets

5. Provision the A-numbers and B-numbers

6. Provision CPC

7. Provision TMR analysis

8. Provision B-number NOA and NPI analysis

9. Provision TNS

10. Provision NANP B-number normalization

11. Provision the location value

12. Provision the cause value

13. Provision the A and B whitelist and blacklist screening files

To begin the process of creating a dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-add:component:custgrpid=cust_groupID,param_name="param_value",...

Where:

component—The name of the component type you want to add to your dial plan. A complete list of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

cust_groupID—Customer group ID number associated with your dial plan.

param_name—The name of the parameter you want to configure for the selected component in your dial plan. A complete list of the valid parameters for each dial plan component type can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

param_value—The value of the parameter you want to configure for the selected component in your dial plan. A complete list of the valid values for the parameters of each dial plan component type can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

For example, to provision a route result type called resultone, you would enter the following command:

mml> numan-add:resulttable:custgrpid="t777",resulttype="route",setname="setone", 
name="resultone",dw1="rtlistone"

Modifying an Element of Your Dial Plan Data

To modify an element of your dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-ed:component:custgrpid="cust_groupID",param_name="param_value",...

Where:

component—The name of the component type you want to modify in your dial plan. A complete list of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

cust_groupID—Customer group ID number associated with your dial plan.

param_name—The name of the parameter you want to configure for the selected component in your dial plan. A complete list of the valid parameters for each dial plan component type can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

param_value—The value of the parameter you want to configure for the selected component in your dial plan. A complete list of the valid values for the parameters of each dial plan component type can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

For example, to modify a result table, you would enter the following command:

mml> numan-ed:resulttable:custgrpid="t777",resulttype="route",setname="setone", 
name="resulttwo",dw1="rtlistone"

Deleting an Element from Your Dial Plan Data

To delete an element from your dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-dlt:component:custgrpid="cust_groupID",name="MML_name"

Where:

component—The name of the component type you want to delete from your dial plan. A complete list of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

cust_groupID—Customer group ID number associated with your dial plan.

MML_name—The MML name of the selected component you want to delete from your dial plan.

For example, to delete a result set called setone, you would enter the following command:

mml> numan-dlt:resultset:custgrpid="t001",name="setone"

Retrieving Dial Plan Data

You can use the numan-rtrv MML command to retrieve information about your current dial plan settings. The ways in which you can use this command to retrieve dial plan data are described in the following sections:

Retrieving Data for an Individual Component

Retrieving Data for All Components of a Particular Type


Note You can verify dial plans using the translation verification viewer on the Cisco MGC toolbar. For information on using the translation verification viewer, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.


Retrieving Data for an Individual Component

You can retrieve dial plan data for an individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-rtrv:component:custgrpid="cust_groupID",name="MML_name"

Where:

component—The name of the component type you want to retrieve from your dial plan. A complete list of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

cust_groupID—Customer group ID number associated with your dial plan.

MML_name—The MML name of the selected component you want to retrieve from your dial plan.

For example, to retrieve the settings for a result set called setone, you would enter the following command:

mml> numan-rtrv:resultset:custgrpid="t001",name="setone"

Retrieving Data for All Components of a Particular Type

You can retrieve dial plan data for all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-rtrv:component:custgrpid="cust_groupID","all"

Where:

component—The name of the component type you want to retrieve from your dial plan. A complete list of the valid dial plan component types can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

cust_groupID—Customer group ID number associated with your dial plan.

For example, to retrieve the settings for all result sets in your dial plan, you would enter the following command:

mml> numan-rtrv:resultset:custgrpid="t001","all"

Result Type Definitions

Result analysis provides you the capability to group actions into result sets that can be attached at different points of analysis. The main attachment points are Pre-analysis, A-number analysis, B-number analysis, and Cause analysis.

The following result type definition is added for this feature (see Table 3). For information on other result type definitions for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Table 3 New Result Type Definitions 

Result Number.
Result Type
Dataword1
Dataword2
Dataword3
Dataword4
Analysis Points
Result Type Valid For
Intermediate
End Point
A-digit analysis
B-digit analysis
Cause
Pre-analysis

70

E911PROF

Route Pref

0 (not used)

0 (not used)

0 (not used)

X

 

 

X

X

 


Result Type Definition

The following paragraph defines the E911PROF result type.

E911PROF

The E911PROF result type is returned from B-number analysis (the called number) indicating if the B-number is an emergency call and the profile mapping to apply to emergency numbers.

Valid E911PROF dataword1 values are listed in Table 4.

Table 4 E911PROF Dataword1 Result Type Mapping 

Dataword 1
ISUP Parameter Option
ESRK Delivery 1
CBN and ESRD Delivery 2

1

A1

 

2

A2

 

3

A3

 

4

B1

 

5

B2

 

6

B3

 

7

 

A1

8

 

A2

9

 

A3

10

 

B1

11

 

B2

12

 

B3

13

 

C1

14

 

C2

15

 

C3

16

 

D1

17

 

D2

18

 

D3

19

 

E1

20

 

E2

21

 

F1

22

 

F2

23

 

G1

24

 

G2

25

 

H1

26

 

H2

27

 

I1

28

 

I2

29

 

I3

30

 

J1

31

 

J2

32

 

K1

33

 

K2

34

 

L1

35

 

L2

1 Refer to Table 1 for ESRK delivery and ISUP parameter option values.

2 Refer to Table 2 for ESRD delivery and ISUP parameter option values.


Cause and Location Codes

The cause codes in this section are added for this feature. For information on other cause and location codes for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide. The new cause codes can be found in the following sections:

Internal Cause Codes

The cause codes listed in the following sections are defined by their individual explanations.

Internal Cause Codes

The cause code listed in Table 5 is generated internally when a call is rejected by, or clearance is initiated by the system.

Table 5 Internally Generated Cause Codes 

Internal Cause Code
Cause Code Explanation

IC_E911_RETRY

The MGC was not able to route the call to PSAP; or the call was not able to connect to PSAP.


Internal Cause Code Values

Table 6 lists the internal cause code and corresponding numerical value.

Table 6 Internal Cause Code Values 

Internal Cause Code
Value
Internal Cause Code
Value

IC_E911_RETRY

172

   

The internal cause value can be used to route the 911 call to a fixed location using cause analysis. For example, the fixed location could be a fixed SR.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

Glossary

Table 7 contains definitions of acronyms used in this feature module.

Table 7 Acronyms and Definitions

Acronym
Definition

CAMA

Centralized Automatic Message Accounting

CDPN

Called Party Number

CHGN

Charge Number

CPC

Calling Party Category

CPN

Calling Party Number

ESRN

Emergency Services Routing Number

ESQK

Emergency Services Query Key

FQDN

Fully Qualified Domain Name

GDP

Generic Digit Parameter

IAM

Initial Address Message

ISUP

ISDN User Part

MGC

Cisco Media Gateway Controller

OLI

Originating Line Identification

PSAP

Public Safety Answering Point

PGW

PSTN Gateway

SC

Signaling Controller

SR

Selective Router

SIP

Session Initiation Protocol

VSC

Virtual Switch Controller