Guest

Cisco PGW 2200 Softswitch

Fax and Data Call Translation on the PGW 2200

  • Viewing Options

  • PDF (360.2 KB)
  • Feedback
Fax and Data Call Translations on the PGW 2200

Table Of Contents

Fax and Data Call Translations on the PGW 2200

Feature Overview

Benefits

Restrictions

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites for Using This Feature

Provisioning Tasks

Provisioning Prerequisites

Collecting External Node Data

Provisioning Procedures

Provisioning Basics

Creating Dial Plan Data

Dial Plan Prerequisites

Dial Plan Basics

Dial Plan Procedures

Adding the BCMOD Result Type

Modifying the BCMOD Result Type

Deleting the BCMOD Result Type

Adding the HLCMOD Result Type

Modifying the HLCMOD Result Type

Deleting the HLCMOD Result Type

Troubleshooting Dial Plan Data

Signaling Channel Troubleshooting Procedures

Dial Plan Examples

Reference Information

Result Type Definitions

Result Type Definitions

Dial Plan Worksheets

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


Fax and Data Call Translations on the PGW 2200


Document Release History

Publication Date
Comments

December 29, 2005

Initial version of the document.

July 17, 2006

Added a note on page 16 to resolve CSCsc75586.


Feature History

Release
Modification

9.5(2)

This feature was introduced on the PGW 2200 software Release 9.5(2).


This document describes the Fax and Data Call Translations on the PGW 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 Tasks

Creating Dial Plan Data

Dial Plan Examples

Reference Information

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Glossary

Feature Overview

The Fax and Data Call Translations on the PGW 2200 feature provides the ability to change an ISUP call to a fax or data call. This feature provides support on the Cisco PGW 2200 to change the Bearer Capability and High Layer Compatibility information elements (IEs) in outgoing Initial Address Messages (IAMs) based on the dialed called party number. The Cisco MGC can use the BCMOD and HLCMOD result types to change outgoing IAM message parameters to allow calls from the public switched telephone network (PSTN) to called (B-numbers) in the Global System for Mobile Communications (GSM) network for ISUP calls.

This feature provides the following:

The ability to change the Bearer Capability IE in outgoing IAMs for data or fax calls.

The ability to change the High Layer Compatibility IE in outgoing IAMs for data or fax calls.

Benefits

Ability to Change an ISUP Call to a Fax Call

By changing the Bearer Capability IE in the outgoing IAM, an ISUP call from the PSTN can be translated to a fax call in the GSM network.

Ability to Change an ISUP Call to a Data Call

By changing the High Layer Compatibility IE in the outgoing IAM, an ISUP call from the PSTN can be translated to a data call in the GSM network.

Restrictions

If there are HLCMOD or BCMOD result type-related dial plan provisioning changes made after the gs049/nn041 upgrade, then there is a need to downgrade to the previous patch level. You must use the config-lib utility to revert back to the latest configuration used at that downgraded patch level.

Call translation works for scenarios in which the terminating call control (TCC) is ISUP.

Currently only ITU ISUP variants are supported.

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 MGC software Release 9.5(2). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2).

Provisioning Tasks

The following sections describe the provisioning tasks related to this feature:

Provisioning Prerequisites

Provisioning Procedures

Provisioning Prerequisites

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 External Node Data

The external node component type represents another node with which the MGC communicates. You must be ready to enter the following data about the node:

MML name

Component description

External nodes for each device connected to the network

Point codes (OPC, APC, and DPC)

Interface cards

SS7 signaling service

Media gateway signaling service

Linksets

C7 IP links (redundant)

IP links

SS7 routes

SS7 subsystem

Trunks (x24 or x31)

ISDN signaling type

Provisioning Procedures

Provision the transport path between the Cisco PGW 2200 and the external Cisco media gateway nodes. Communication between the Cisco PGW 2200 and the Cisco media gateways is provisioned so that there is a reliable communication path between the two platforms.

This provisioning is performed when a new external node is added to the Cisco PGW 2200. This section covers the following provisioning topics:

Provisioning Basics, page 11

Provisioning Basics

The procedures in this section describe how to start a provisioning session and how to save and activate 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 may 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 learn it by using the procedure described in the "Retrieving Data on the Current Provisioning Session" section on page 7.


mod_ver—A new configuration version name 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 would enter the following command:

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

Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML commands to add, modify, and 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 and prov-dply MML commands 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 system (one with 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 in 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 on 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 provisioning 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 2004-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 

Creating Dial Plan Data

The following sections describe the tasks related to creating a dial plan for this feature:

Dial Plan Prerequisites

Dial Plan Basics

Dial Plan Procedures

Troubleshooting Dial Plan Data

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

Use the procedures in this section describe how to add, modify, and delete dial plan data and 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 Dial Plan 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 existing 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 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:

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 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:

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—The 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" 

Dial Plan Procedures

This section contains the procedures required for provisioning the dial plan data for this feature. For more information on creating dial plans for other functions of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Adding the BCMOD Result Type

To create the bearer capability table and add the BCMOD result type, complete the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command to add a dial plan:

mml> numan-add:dialplan:custgrpid="dpl1",overdec="yes" 

Step 2 Enter the following command to add a result set:

mml> numan-add:resultset:custgrpid="dpl1",name="set1" 

Step 3 Enter the following command to add the BC table entry:

mml> numan-add:BC:cusgrpid="dpl1",name="bc-04",ocval="9090A3" 

Step 4 Now add the BCMOD result type to a result set and define the result set in the result table:

mml> numan-add:resulttable:custgrpid="dp11",resulttype="BCMOD",dw1="bc-04",setname="set1",
name="bc1" 

Where:

custgrpid—Customer group ID. A 4-digit alphanumeric string (enclosed in straight quotes) to identify the dial plan.

resulttype—Result type. Indicates the result type being provisioned. Any valid result type name is allowed. The result type for this feature is BCMOD or high-level capability (HLCMOD).

overdec—Over decadic. A 2- or 3-character string that identifies the overdecadic dial plan status. Valid values are: yes (overdecadic) and no (decadic).

ocval—Octet coding. A string of as many as 32 hexadecimal characters that identify the BC or HLC coding used for the outgoing fax or data call. You can enter as many as 32 hexadecimal characters enclosed in straight quotes.

setname—Result set name. The name you give to the result set. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

name—Name. The name you give to the component. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

Step 5 Repeat Step 4, as necessary, to add new rows to the bearer capability table.


Modifying the BCMOD Result Type

The BCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-ed MML command to modify the bearer capability table.

To modify the BCMOD result type, complete the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command to modify a line in the BCMOD table:

mml> numan-ed:resulttable:cusgrpid="dpl1",resulttype="BCMOD",dw1="bc-05",setname="set1", 
name="bc1" 

Where:

custgrpid—Customer group ID. A 4-digit alphanumeric string (enclosed in straight quotes) to identify the dial plan.

resulttype—Result type. Indicates the result type being provisioned. Any valid result type name is allowed. The result type for this feature is BCMOD or high-level capability (HLCMOD).

overdec—Over decadic. A 2- or 3-character string that identifies the overdecadic dial plan status. Valid values are: yes (overdecadic) and no (decadic).

ocval—Octet coding. A string of as many as 32 hexadecimal characters that identify the BC or HLC coding used for the outgoing fax or data call. You can enter as many as 32 hexadecimal characters enclosed in straight quotes.

setname—Result set name. The name you give to the result set. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

name—Name. The name you give to the component. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

This command modifies the BCMOD result type in the result table.

Step 2 To verify that the command was executed successfully, enter the following command:

mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1" 

Step 3 Repeat Steps 1 and 2, as necessary, to modify the BCMOD result type in the dial plan.


Deleting the BCMOD Result Type

The BCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-dlt MML command to delete an entry in the bearer capability table.

To delete an entry in the bearer capability table, complete the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-dlt:resulttable:cusgrpid="dpl1",resulttype="BCMOD",dw1="bc-05",setname="set1", 
name="bc1" 

This command deletes the BCMOD result type from the result table.


Step 2 To verify that the command was executed successfully, enter the command:

mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1" 

Step 3 Repeat Steps 1 and 2, as necessary, to remove BCMOD result type from the result table.


Adding the HLCMOD Result Type

Create the high-level capability table and add the high-level capability result type (HLCMOD) to the dial plan to modify the high level capability in the outgoing IAM by performing the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command to add a dial plan:

mml> numan-add:dialplan:custgrpid="dpl2",overdec="yes" 

Step 2 Enter the following command to add a result set:

mml> numan-add:resultset:custgrpid="dpl2",name="set3" 

Step 3 Enter the following command to add the HLC table entry:

mml> numan-add:HLC:cusgrpid="dpl1",name="hlc-04",ocval="9184" 

Step 4 Now add the HLCMOD result type to a result set and define the result set in the result table:

mml> numan-add:resulttable:custgrpid="dp12",resulttype="HLCMOD",dw1="hlc-04", 
setname="set3",name="result03" 

Where:

custgrpid—Customer group ID. A 4-digit alphanumeric string (enclosed in straight quotes) to identify the dial plan.

resulttype—Result type. Indicates the result type being provisioned. Any valid result type name is allowed. The result type for this feature is BCMOD or HLCMOD.

overdec—Over decadic. A 2- or 3-character string that identifies the overdecadic dial plan status. Valid values are: yes (overdecadic) and no (decadic).

ocval—Octet coding. A string of as many as 32 hexadecimal characters that identify the BC or HLC coding used for the outgoing fax or data call. You can enter as many as 32 hexadecimal characters enclosed in straight quotes.

setname—Result set name. The name you give to the result set. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

name—Name. The name you give to the component. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

Step 5 Repeat Step 4, as necessary, to add HLCMOD result types to the result table.


Modifying the HLCMOD Result Type

The HLCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-ed MML command to modify the bearer capability table.

To modify the HLCMOD result type, complete the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command to modify a line in the HLCMOD table:

mml> numan-ed:resulttable:cusgrpid="dpl1",resulttype="HLCMOD",dw1="hlc-05",setname="set1",
name="result03" 

Where:

custgrpid—Customer group ID. A 4-digit alphanumeric string (enclosed in straight quotes) to identify the dial plan.

resulttype—Result type. Indicates the result type being provisioned. Any valid result type name is allowed. The result type for this feature is BCMOD or high-level capability (HLCMOD).

overdec—Over decadic. A 2- or 3-character string that identifies the overdecadic dial plan status. Valid values are: yes (overdecadic) and no (decadic).

ocval—Octet coding. A string of as many as 32 hexadecimal characters that identify the BC or HLC coding used for the outgoing fax or data call. You can enter as many as 32 hexadecimal characters enclosed in straight quotes.

setname—Result set name. The name you give to the result set. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

name—Name. The name you give to the component. The name can be as many as 20 alphanumeric characters enclosed in straight quotes. The name should begin with a letter.

This command modifies the HLCMOD result type in the result table.

Step 2 To verify that the command was executed successfully, enter the following command:

mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1" 

Step 3 Repeat Steps 1 and 2, as necessary, to modify the HLCMOD result type in the dial plan.


Deleting the HLCMOD Result Type

The HLCMOD result type is used during A-number or B-number analysis to modify the high-level capability in the outgoing IAM. You can use the numan-dlt MML command to delete an entry in the high-level capability table.

To delete an HLCMOD result type from the result table, complete the following steps:


Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command:

mml> numan-dlt:esulttable:cusgrpid="dpl1",resulttype="HLCMOD",dw1="hlc-05",setname="set1",
name="result03" 

This command deletes the HLCMOD result type from the result table.


Step 2 To verify that the command was executed successfully, enter the following command:

mml> numan-rtrv:BC:custgrpid="dpl1",setname="set3" 

Step 3 Repeat Steps 1 and 2, as necessary, to remove HLCMOD result types from the result table.


Troubleshooting Dial Plan Data

The following sections contain troubleshooting procedures related to dial plan creation:

Signaling Channel Troubleshooting Procedures

For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.

Signaling Channel Troubleshooting Procedures

The following sections are procedures used to resolve problems associated with the Cisco MGC node's signaling connections to other networks:

Verifying Proper Loading of a Dial Plan

Verifying Proper Loading of a Dial Plan


Step 1 Search the active system log file, as described in the "Viewing System Logs" section on page 8-4, for logs that indicate that the dial plan was loaded incorrectly.

If the dial plan was not loaded correctly, reload the dial plan by saving and activating your dial plan again as described in the "Saving and Activating Your Provisioning Changes" section.

If there are no logs that indicate that the dial plan was loaded incorrectly, proceed to Step 2.

Step 2 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.


Dial Plan Examples

This section provides the following examples of dial plan provisioning for this feature. Additional examples of dial plan provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

mml> prov-sta::srcver="new",dstver="mod_ver01",confirm
mml> numan-add:dialplan:custgrpid="T005",overdec="YES"
mml> numan-add:resultset:custgrpid="T005",name="set001"
mml> numan-add:resulttable:custgrpid="T005",setname="set001",name="result-bc", 
resulttype="BCMOD",dw1="data-2400-bc02"
mml> numan-add:resulttable:custgrpid="T005",setname="set001",name="result-hlc", 
resulttype="HLCMOD",dw1="fax-hlc01"

Reference Information

The following sections contain reference material related to this feature. Information is included on the following areas:

Result Type Definitions

Dial Plan Worksheets

Result Type Definitions

Result analysis provides 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 definitions are added for this feature. 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 1 shows the result type added for this feature.

Table 1 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

73

BCMOD

BC Name

0 (not used)

0 (not used)

0 (not used)

X

 

X

X

 

 

74

HLCMOD

HLC Name

0 (not used)

0 (not used)

0 (not used)

X

 

X

X

 

 


Result Type Definitions

The following paragraphs contain definitions of the result types listed in Table 1.

BCMOD

The BCMOD result type is returned from A-number (the calling number) or B-number analysis (the called number) analysis indicating if the bearer capability name. The BCMOD result type dataword1 value indicates the bearer channel characteristics as being either fax or data and a baud rate.

Valid dataword1 BC Name values are: A string of as many as 20 alphanumerical characters


Note The BCMOD result type is applied to the bearer capability in the incoming IAM, not to the modified A-number or B-number. Routing analysis does not occur on the BCMOD result value. Therefore, the bearer capability after the BCMOD Result type is applied must be the desired bearer capability.


Table 2 provides an example BCMOD result type values for dataword1 and a corresponding octet values (ocval).

Table 2 BCMOD Result Type BC Name and Octet Coding Value 

BC Name
Octet Coding

fax-bc01

9090A3

data-2400-bc02

90902343403BD3

data-4800-bc03

90902345403BDC

data-9600-bc04

90902348403BDC


HLCMOD

The HLCMOD result type is returned from A-number (the calling number) or B-number analysis (the called number) indicating if the high layer compatibility name. The HLCMOD result type dataword1 value indicates the high layer compatibility characteristics as being either fax or data and a baud rate.

Valid dataword1 HLC Name value is: A string of as many as 20 alphanumerical characters

Table 3 is an example of an HLCMOD result type value for dataword1 and a corresponding octet value (ocval).

Table 3 HLCMOD Result Type HLC Name and Octet Coding Value 

HLC Name
Octet Coding

fax-hlc01

9184


Dial Plan Worksheets

This section contains worksheets for the dial plan components required for this feature. For worksheets covering the rest of the dial plan components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Table 4 can be used for planning the BCMOD or HLCMOD result type and corresponding table entry.

Table 4 BCMOD / HLCMOD Result Type Worksheet

Parameter

Dial plan

             

Result set name

             

Result table name

             

Result type

             

—dw1

             

—dw2

             

—dw3

             

—dw4

             

Set name

             

BC/HLC table entry

             

BCMOD/HLCMOD

             

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 the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Cisco Marketplace:

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/

Cisco will continue to support documentation orders using the Ordering tool:

Registered Cisco.com users (Cisco direct customers) can order documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Instructions for ordering documentation using the Ordering tool are at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

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.htm

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 5 contains expansions of acronyms and technical terms used in this feature module.

Table 5 Acronym Expansions

Acronym
Expansion

APC

Adjacent Point Code

DPC

Destination Point Code

GSM

Global System for Mobile Communications

GTD

Generic Transparency Descriptor

HLC

high-level capability

IAM

Initial Address Message

IE

information element

ISUP

ISDN User Part

MGC

(Cisco) Media Gateway Controller

NANP

North American Numbering Plan

NOA

nature of address

NPI

Number Plan Indicator

PGW

PSTN Gateway

PSTN

public switched telephone network

SC

Signaling Controller

SIP

Session Initiation Protocol

SS7

Signaling System 7

TMR

Transmission Medium Requirement

TNS

transit network selection

VSC

Virtual Switch Controller