cc/td/doc/product/access/sc/rel9/mgcfm
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Support of SIP-T and SIP-GTD

Feature Overview

Benefits

Restrictions

Related Features and Technologies

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Provisioning Tasks

Planning for Provisioning

Provisioning Procedures

Troubleshooting Tips

Provisioning Examples

Command Reference

Modified MML Commands

Reference Information

Properties

External Node Types

Provisioning Worksheets

Mapping GTD Codes for ISUP Messages and Parameters

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


Support of SIP-T and SIP-GTD

Document Release History

Publication Date
Comments

September 9, 2003

Initial version of the document.

November 11, 2003

Corrected information for the sipMimeBodySupport property.

December 22, 2005

Corrected errors in the Feature Overview.


Feature History

Release
Modification

9.4(1)

This feature was introduced on the Cisco MGC software.


This document describes the Support of Session Initiated Protocol (SIP) for Telephones (SIP-T) and SIP Generic Transparency Descriptor (GTD) Feature. This feature is described in the following sections:

• Feature Overview

• Supported Platforms

• Supported Standards, MIBs, and RFCs

• Prerequisites

• Provisioning Tasks

• Provisioning Examples

• Command Reference

• Reference Information

• Obtaining Documentation

• Documentation Feedback

• Cisco Product Security Overview

• Obtaining Technical Assistance

• Obtaining Additional Publications and Information

• Glossary

Feature Overview

The introduction of the Support for SIP-T and SIP-GTD feature allows the Cisco MGC to send ISDN User Part (ISUP) parameters through SIP networks. This feature also enables the Cisco MGC to support end-to-end ISUP transparency.

This feature supports the encapsulation of MIME-encoded binary ISUP within SIP messages using SIP-T, and MIME-encoded GTD within SIP messages. SIP-T is used where use of open protocols is most important. SIP-T enables end-to-end ISUP transparency between networks using German ISUP.

SIP-GTD is used to enable connection between networks using different ISUP types, provide the ability to transfer a subset of parameters to reduce overhead as compared to SIP-T (with Native ISUP). SIP-GTD can be provisioned on outgoing SIP trunk groups.

Benefits

This feature has the following benefits:

Enables end-to-end ISUP transparency through SIP networks

In a plain SIP network, some ISUP parameters are interworked with SIP information in the messages. There is no one-to-one mapping for the ISUP parameters. By using SIP-T or SIP-GTD, the ISUP parameters can be transported from ingress to egress.

Use of ISUP parameters in SIP networks

Not all ISUP parameters are interworked with SIP. Using SIP-GTD, a subset or all of the ISUP parameters can be exposed in SIP networks.

Restrictions

This feature has the following restrictions:

•It can only be used with connections to media gateways or softswitches that support SIP-T and/or SIP-GTD.

•SIP-T is only supported for German ISUP.

•SIP-T works only when both Cisco MGCs are configured for German ISUP.

Related Features and Technologies

This feature is related to the feature that adds support of GTD to SIP media gateways.

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.4(1)

•Cisco Media Gateway Controller Hardware Installation Guide

•Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller

•Cisco Media Gateway Controller Software Release 9Installation 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 Guide

•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 MIB 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 Release Notes for Cisco Media Gateway Controller Software Release 9.4(1).

Supported Standards, MIBs, and RFCs

This feature supports the following standards, MIBs, and RFCs.

Standards

This feature supports the following ITU SG11 drafts:

•Q.GTD.1—Generic Transparency Descriptor Syntax Definition

•Q.GTD.2—Generic Transparency Descriptor Usage Rules and Mappings

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 Release 9 MIB Guide.

RFCs

This feature supports the following RFC: RFC-3352—Session Initiation Protocol for Telephones (SIP-T): Context and Architectures.

Prerequisites

You must have Cisco Media Gateway Controller (MGC) software Release 9.4(1). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.4(1).

Provisioning Tasks

This section contains the tasks required to provision this feature. For information on provisioning the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

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 SS7 Signaling Service Data

This component type represents an SS7 signaling path. You must be ready to enter the following data:

•Man-Machine Language (MML) name

•Component description

•Protocol file name (should be Q761_GERMAN for SIP-T)

•Destination point code (DPC)

•Origination point code (OPC)

•Customer Group Identification

You can define the parameters for your external nodes in Table 4 in the "Provisioning Worksheets" section.

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

•The type of the external node

•ISDN signaling type (only if your external node and MGC use an IUA interface)

You can define the parameters for your external nodes in Table 5 in the "Provisioning Worksheets" section.

Collecting SIP Signaling Service Data

This component type represents a SIP path. You must be ready to enter the following data:

•MML name

•Component description

•Protocol File Name (this should be IETF_SIP)

You can define the parameters for your SIP signaling services in Table 6 in the "Provisioning Worksheets" section.

Collecting SIP IP Link Data

This component type represents a link to a SIP device. You must be ready to enter the following data:

•MML name

•Component description

•Port

•Priority

•IP address

•Associated SIP signaling service

You can define the parameters for your SIP IP links in Table 7 in the "Provisioning Worksheets" section.

Collecting Trunk Group Data

This component type represents a group of trunks. You must be ready to enter the following data:

•MML name

•MML name of a previously provisioned signaling service

•Trunk group type (either SIP_IN or IP_SIP)

•Select sequence

•Associated timeslot - does it support queuing?

You can define the parameters for your trunk groups in Table 8 in the "Provisioning Worksheets" section.

Collecting Switched Trunk Data

This component type represents a switched trunk. You must be ready to enter the following data:

•Trunk ID

•Trunk group number

•Span

•Circuit Identification Code (CIC)

•Coding unit

•End point

•Span size

You can define the parameters for your switched trunks in Table 9 in the "Provisioning Worksheets" section.

Collecting Trunk Group Properties Data

This component type represents properties for an existing trunk group. All of the trunk group properties have default values. You must be ready to enter data for the properties you are going to modify. For information on all of the trunk group properties, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

You can define the new values for the trunk group properties s in Table 10 in the "Provisioning Worksheets" section.

Collecting Domain Name Server Parameters Data

This component type represents Domain Name Server (DNS) parameters for a DNS group. Some of the DNS parameters have default values. You must be ready to enter data for the parameters you are going to modify.

You can define the new values for the DNS parameters in Table 11 in the "Provisioning Worksheets" section.

Provisioning Procedures

The provisioning procedures for this feature can be found in the following sections:

• Provisioning Basics

• Adding Support of SIP-T and SIP-GTD

• Modifying SIP-T and SIP-GTD values

• Disabling Support of SIP-T and SIP-GTD

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 PGW 2200, 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 into the active Cisco MGC, start an MML session, and enter the following command:

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

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

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

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

Note You can use new as the source configuration only when there is no existing, active set of provisioning data in the configuration library. Therefore, new cannot be used as the source configuration once a provisioning session has been saved and activated by using prov-cpy or prov-dply. Once you have saved and activated a set of data, you must use either active or the name of the set of provisioning data as the source configuration.

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

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

Once a provisioning session is underway, you may use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, and delete components on your system. For more information on provisioning other functions on your Cisco MGC software, 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 the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.

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 Using the prov-sync MML command can severely impact your system's call processing performance. We recommend that this command be issued during a maintenance window when traffic is minimal.

Note When the prov-sync MML command is used to synchronize the provisioning settings on the standby MGC host with current settings on the active MGC host, the system does not indicate when the synchronization process has failed.

The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in high-availability or continuous-service configurations. 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

You may find that you want to end a provisioning session without saving and activating the changes you have entered during your session. If this is the case, you can 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 in which 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:

mml>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 value of GTD properties for a GTD parameter set called t3, you would enter the following command:

mml>prov-rtrv:gtdparam:name="t3"

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:

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

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

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

mml>prov-rtrv:session

The system returns a response similar to the following:

MGC-02 - Media Gateway Controller 2003-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:

mml>prov-rtrv:variants

Adding Support of SIP-T and SIP-GTD

This section contains the procedures that you must perform to add SIP-T and SIP-GTD support to your Cisco MGC software provisioning data. When provisioning the components that enable the Cisco MGC software to support SIP-T and SIP-T, perform the procedures in the following order.

• Adding SS7 signaling services

• Adding External Nodes

• Adding SIP Signaling Services

• Adding SIP IP Links

• Adding Trunk Groups

• Adding Switched Trunks

• Adding SIP-T and SIP-GTD Support

• Provisioning GTD Parameter Sets

• Enabling the Early Backward ISUP Message

• Enabling GTD Parameter Sets

• Adding DNS Parameters

Note To begin the provisioning session, perform the steps in the "Starting a Provisioning Session" section. Once you have finished provisioning the SIP-T and SIP-GTD data, save and activate your provisioning data by performing the steps in the "Saving and Activating your Provisioning Changes" section.

Adding SS7 signaling services

To provision SS7 signaling services, perform the following steps:

Step 1 Enter the following command to provision an SS7 signaling service:

mml>prov-add:ss7path:name="name", desc="description", mdo="Q761_GERMAN", dpc="dest", opc="orig"

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

•dest—The MML name of a previously provisioned DPC.

•orig—The MML name of a previously provisioned OPC.

For example, to provision an SS7 signaling service to support SIP-T and SIP-GTD, you would enter the following command:

mml>prov-add:ss7path:name="ss7svc1", mdo="Q761_GERMAN", dpc="dpc1", opc="opc", custgrpid="1111", desc="SS7 service to DPC-2-2-2"

Step 2 Repeat Step 1 for each SS7 signaling service you want to provision.

Adding External Nodes

To provision external nodes, perform the following steps:

Step 1 Enter the following command to provision an external node:

mml>prov-add:extnode:name="name", desc="description", type="trans"

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

•type—External node type. A list of valid external node types can be found in Table 3.

For example, to provision an external node to support SIP-T, you would enter the following command:

mml>prov-add:extnode:name="mgcp1", desc="external node - mgcp1", type="AS5300"

Step 2 Repeat Step 1 for each external node you want to provision.

Adding SIP Signaling Services

To provision SIP signaling services, perform the following steps:

Step 1 Enter the following command to provision a SIP signaling service:

mml>prov-add:sippath:name="name", desc="description", mdo="IETF_SIP"

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

For example, to provision a SIP signaling service, you would enter the following command:

mml>prov-add:sippath:name="sip-sigpath",mdo="IETF_SIP",desc="SIP sigpath"

Step 2 Repeat Step 1 for each SIP signaling service you want to provision.

Adding SIP IP Links

To provision SIP IP links, perform the following steps:

Step 1 Enter the following command to provision a SIP IP link:

mml>prov-add:siplnk:name="name", desc="description", ipaddr1="addr1", ipaddr2="addr2", svc="sigsrv", port=pnum, pri=priority

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

•addr1—First local IP address for a LAN interface. IP address should be one of the following property names defined in the XECfgParm.dat file:

–IP_Addr1 (supports existing SIP automatic switchover method)

–IP_Addr2 (supports existing SIP automatic switchover method)

–IP_Addr3 (supports existing SIP automatic switchover method)

–IP_Addr4 (supports existing SIP automatic switchover method)

–Virtual_IP_Addr1 (supports SIP automatic switchover using dual-VLAN method)

–Virtual_IP_Addr2 (supports SIP automatic switchover using dual-VLAN method)

•addr2—Second local IP address for a LAN interface. IP address should be one of the following property names defined in the XECfgParm.dat file, excluding the property name selected in addr1:

–IP_Addr1 (supports existing SIP automatic switchover method)

–IP_Addr2 (supports existing SIP automatic switchover method)

–IP_Addr3 (supports existing SIP automatic switchover method)

–IP_Addr4 (supports existing SIP automatic switchover method)

–Virtual_IP_Addr1 (supports SIP automatic switchover using dual-VLAN method)

–Virtual_IP_Addr2 (supports SIP automatic switchover using dual-VLAN method)

•sigsrv—The MML name of a previously provisioned SIP signaling service.

•pnum—Local IP port number. Valid value is any integer above 1024. For SIP IP links, we recommend that you use 5060.

•priority—Priority setting for this SIP IP link. Valid value is any integer above 0. Default value is 1.

For example, to provision a SIP IP link, you would enter the following command:

mml>prov-add:siplnk:name="sip-sigchan", ipaddr1="IP_Addr1", ipaddr2="IP_Addr2", svc="sip-sigpath", port=5060, pri=1, desc="SIP sigchan"

Step 2 Repeat Step 1 for each SIP IP link you want to provision.

Adding Trunk Groups

To provision trunk groups, perform the following steps:

Step 1 Enter the following command to provision a trunk group:

mml>prov-add:trnkgrp:name="num", clli="code", svc="sigsrv", type="tgtype", selseq="select", qable="x"

Where:

•num—Number of the trunk group. The value must be an integer between 1 and 65535.

•clli—Associated common language location identifier, represented by an alphanumeric string of up to 11 characters.

•sigsrv—The MML name of a previously provisioned SS7, IP Facility Associated Signaling (FAS), FAS, or SIP signaling service.

•tgtype—Trunk group type. Select from the following types:

–ATM

–IP—Used with EISUP signaling services.

–IP_SIP—Used for SIP signaling services at the terminating side.

–SIP_IN—Used for SIP signaling services at the originating side. Only one such trunk group can be configured on each Cisco MGC node.

–TDM_ISUP—Used with SS7 signaling services with switch types of 0 (No switch-specific logic for signaling service), 5 (BTNUP), 20 (SS7 Clear), 23 (SS7 ANSI), and 40 (SS7 ITU).

–TDM_CAS—Used with CAS signaling services. This option is not currently supported.

–TDM_TUP—Used with SS7 signaling services with switch type of 5 (BTNUP).

–TDM_GEN—Used with SS7 signaling services with other switch types including 26 (DPNSS), 27 (NET5), 10 (SS7 Japan), 29 (QSIG Master), 30 (QSIG Slave), 17 (5ESS), and 22 (NI2).

–TDM_DPNSS—Used with signaling services with the protocol family of DPNSS

–TDM_PRI—Used with IPFAS or FAS signaling services with the protocol family of ISDNPRI.

–TDM_BTNUP—Used with SS7 signaling services with SS7-UK variants with switch type of 5 (BTNUP).

•select—Select sequence. Select from the following:

–LIDL

–MIDL

–ASC

–DESC

–RDM

–EDESC

–ODESC

–EASC

–OASC

–CASC

–CDESC

–ITU2

•x—Flag to identify whether the packets for the associated timeslot can be queued. Valid values are Y and N. Default value is N.

For example, to provision a trunk group, you would enter the following command:

mml>prov-add:trnkgrp:name="1000", clli="tttt-ss-xxx", svc="sp1-mgcp1", type="tdm_gen", selseq="lidl", qable="n"

Step 2 Repeat Step 1 for each trunk group you want to provision.

Adding Switched Trunks

To provision switched trunks, perform the following steps:

Step 1 Enter the following command to provision switched trunks:

mml>prov-add:switchtrnk:name="num", trnkgrpnum="tgnum", span="spannum", cic=cicnum, cu="codeunit", spansize=size, endpoint="end"

Where:

•num—Number of the trunk. The value must be an integer greater than 0.

•tgnum—Number of a previously provisioned trunk group.

•spannum—Span. The value must be an integer between 1 and 65535 or FFFF.

•cicnum—Circuit identification code. The value must be an integer between 1 and 65535.

•codeunit—MML name of a previously provisioned code unit.

•size—Number of trunks per span. The value must be an integer between 1 and 31. The default value is 1.

•end—Name of the end point.

For example, to provision switched trunks, you would enter the following command:

mml>prov-add:switchtrnk:name="1", trnkgrpnum="1000", span="ffff", cic=25, cu="gw1", spansize=6, endpoint="S0/DS1-1/6@li-5300-3"

Step 2 Repeat Step 1 for each set of switched trunks you want to provision.

Adding SIP-T and SIP-GTD Support

To add SIP-T or SIP-GTD support to your system, you must set two properties in both the ingress SS7 trunk group and in the SIP trunk group. To do this, perform the following steps:

Step 1 Enter the following command to enable SIP-T or SIP-GTD on an ingress SS7 trunk group:

mml>prov-add:trnkgrpprop:name="num", sipMimeBodySupport ="siptype", IsupTransparencyDisabled=0

Where:

•num—Number of a previously provisioned ingress SS7 trunk group.

•siptype—Determines whether this trunk group supports SIP-T or SIP-GTD using the following values:

–1—SIP-T supported

–2—SIP-GTD supported

Note The IsupTransparencyDisabled property appears above because enabling SIP-T/SIP-GTD support requires that ISUP transparency be enabled on the selected trunk group.

For example, to add support of SIP-T to a trunk group, you would enter the following command:

mml>prov-add:trnkgrpprop:name="550", sipMimeBodySupport ="1", IsupTransparencyDisabled=0

Step 2 Repeat Step 1 for the SIP trunk group on which you want to activate SIP-T or SIP-GTD support.

Provisioning GTD Parameter Sets

To provision GTD parameter sets, perform the following steps:

Step 1 Enter the following command to provision a GTD parameter set:

mml>prov-add:gtdparam:name="name", desc="description", gtdparamstring="gtdparams"

Note The overridestring GTD subcommand is not valid for use with SIP.

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

•gtdparams—A string of parameters that defines the ISUP messages and parameters that are transparently transported by the Cisco MGC. The maximum length of the string is 460 characters. The valid values are as follows:

–ALL

–Individual ISUP parameter codes (a complete list of valid ISUP parameter codes can be found in Table 12 and Table 13.)

Note If you enable GTD on your system, the following ISUP parameter codes are always allowed, regardless of your individual selections: EVI, GCI, PCI, PRN, MCI and FDC.

For example, to provision a GTD parameter set that supports all of the GTD parameters, you would enter the following command:

mml>prov-add:gtdparam:name="t1", gtdparamstring="ALL"

In another example, you can provision a GTD parameter set that supports select GTD parameters by entering the following command:

mml>prov-add:gtdparam:name="t2", gtdparamstring="BCI, CPC, CGN, CIC, CPN, MCR"

Step 2 Repeat Step 1 for each set of GTD parameters you want to provision.

Enabling the Early Backward ISUP Message

To enable the early backward ISUP message on GTD-enabled SIP trunk groups, perform the following steps:

Step 1 Enter the following command to enable the early backward ISUP message on a SIP trunk group:

mml>prov-ed:trnkgrpprop:name="num", IsupTransEarlyBackwardDisabled="0"

Where num is the number of a previously provisioned trunk group.

Note The default value for this property is 1 (Disabled).

For example, to enable the early backward ISUP message on trunk group 1000, you would enter the following command:

mml>prov-ed:trnkgrpprop:name="1000", IsupTransEarlyBackwardDisabled="0"

Step 2 Repeat Step 2 for each SIP trunk group on which you want to enable the early backward ISUP message.

Enabling GTD Parameter Sets

To enable GTD parameter sets on GTD-enabled trunk groups, perform the following steps:

Step 1 Enter the following command to enable a GTD parameter on a trunk group:

mml>prov-ed:trnkgrpprop:name="num", gtdcaptypeprop="paramstring"

Where:

•num—Number of a previously provisioned trunk group.

•paramstring—String identifying which set of GTD parameters are applied to this trunk group. Valid value are:

–MML name of a previously provisioned GTD parameter set.

–t0—No GTD parameter set (default)

For example, to enable a GTD parameters set on trunk group 1000, you would enter the following command:

mml>prov-ed:trnkgrpprop:name="1000", gtdcaptypeprop="t2"

Step 2 Repeat Step 2 for each trunk group on which you want to enable a GTD parameter set.

Adding DNS Parameters

To provision DNS parameters, enter the following command:

mml>prov-add:dnsparam:dnsserver1="serv1", dnsserver2="serv2", cachesize="cache", ttl="timlive", policy="pol_type", querytimeout="qtimout", keepalive="kptime"

Where:

•serv1—IP address of primary DNS server.

•serv2—IP address of secondary DNS server. This is an optional parameter.

•cache—Maximum number of cache entries used to hold DNS entries. Valid value is any integer greater than 0. The default value is 500.

•timlive—Time-to-live interval for DNS entries, expressed in seconds. Valid value is any integer greater than 0. The default value is 3600.

•pol_type—Policy type used for selecting DNS entries. Valid values are hierarchy and round-robin. The default value is hierarchy.

•qtimout—Timeout interval for DNS queries, expressed in milliseconds. Valid value is any integer greater than 0. The default value is 1000.

•kptime—Time interval to determine whether DNS server is responding, expressed in seconds. Valid value is any integer greater than 0. The default value is 30.

For example, to provision DNS parameters, you would enter the following command:

mml>prov-add:dnsparam:dnsserver1="172.22.121.42", dnsserver2="171.69.2.133", cachesize="500", ttl="3600", policy="hierarchy", querytimeout="1000", keepalive="30"

Modifying SIP-T and SIP-GTD values

This section contains procedures that you can use to modify the SIP-T and SIP-GTD settings in your Cisco MGC software provisioning data. These procedures are as follows:

• Modifying GTD Parameter Set Values

• Disabling the Early Backward ISUP Message

• Changing GTD Parameter Sets

Modifying GTD Parameter Set Values

To provision GTD parameter sets, 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 provision a GTD parameter set:

mml>prov-ed:gtdparam:name="name", desc="description", gtdparamstring="gtdparams"

Note The overridestring GTD subcommand is not valid for use with SIP.

Where:

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

•description—The long name assigned that can be as many as 128 alphanumeric characters in length.

•gtdparams—A string of parameters that defines the ISUP messages and parameters that are transparently transported by the Cisco MGC. The maximum length of the string is 460 characters. The valid values are as follows:

–ALL

–Individual ISUP parameter codes (a complete list of valid ISUP parameter codes can be found in Table 12 and Table 13.)

Note If you enable GTD on your system, the following ISUP parameter codes are always allowed, regardless of your individual selections: EVI, GCI, PCI, PRN, MCI and FDC.

For example, to modify a GTD parameter set to support all of the GTD parameters, you would enter the following command:

mml>prov-ed:gtdparam:name="t1", gtdparamstring="ALL"

In another example, you can modify a GTD parameter set to supports select GTD parameters by entering the following command:

mml>prov-ed:gtdparam:name="t2", gtdparamstring="BCI, CPC, CGN, CIC, CPN, MCR"

Step 3 Repeat Step 1 for each set of GTD parameters 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.

Disabling the Early Backward ISUP Message

To disable the early backward ISUP message on GTD-enabled SIP trunk groups, 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 disable the early backward ISUP message on a SIP trunk group:

mml>prov-ed:trnkgrpprop:name="num", IsupTransEarlyBackwardDisabled="1"

Where num is the number of a previously provisioned trunk group.

For example, to disable the early backward ISUP message on trunk group 1000, you would enter the following command:

mml>prov-ed:trnkgrpprop:name="1000", IsupTransEarlyBackwardDisabled="1"

Step 3 Repeat Step 2 for each SIP trunk group on which you want to disable the early backward ISUP message.

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.

Changing GTD Parameter Sets

To change GTD parameter sets on GTD-enabled trunk groups, 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 enable a GTD parameter on a trunk group:

mml>prov-ed:trnkgrpprop:name="num", gtdcaptypeprop="paramstring"

Where:

•num—Number of a previously provisioned trunk group.

•paramstring—String identifying which set of GTD parameters are applied to this trunk group. Valid value are:

–MML name of a previously provisioned GTD parameter set.

–t0—No GTD parameter set (default)

For example, to enable a different GTD parameters set on trunk group 1000, you would enter the following command:

mml>prov-ed:trnkgrpprop:name="1000", gtdcaptypeprop="t3"

Step 3 Repeat Step 2 for each trunk group on which you want to enable a GTD parameter set.

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.

Disabling Support of SIP-T and SIP-GTD

To disable support of SIP-T and SIP-GTD, you must modify the value of a property for the ingress SS7 and SIP trunk groups. To do this, 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 disable support of SIP-T and SIP-GTD on the ingress SS7 trunk group:

mml>prov-ed:trnkgrpprop:name="name", sipMimeBodySupport="0"

Where: name is the MML name of the previously configured ingress SS7 trunk group.

For example, to disable support of SIP-T on trunk group 1000, you would enter the following command:

mml>prov-ed:trnkgrpprop:name="1000", sipMimeBodySupport="0"

Step 3 Repeat Step 2 for the SIP trunk group.

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.

Troubleshooting Tips

There are no alarms specific to this feature. If you find that you are having trouble with your system and you suspect a SIP-T or SIP-GTD error, verify the provisioning data for the system. If your system is incorrectly configured, fix the faulty data. If that does not resolve the problem, or if your system is correctly configured, contact the Cisco TAC for assistance. Refer to "Obtaining Documentation" section on page 36 for more information about contacting the Cisco TAC.

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.

Provisioning Examples

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

prov-add:gtdparam:name="t3", desc="GTD subset 3", gtdparamstring="CPC, CGN, BCI, CPN, CID, OBI, OCN, RBI, CHN, HOC, RGN", overrideString="CGN.noa, CPN.noa"
prov-add:gtdparam:name="t1",gtdparamstring="ALL"
prov-add:gtdparam:name="t5",gtdparamstring="CPN,CGN,CIC,CPC,BCI"
prov-add:trnkgrpprop:name="2222",custgrpid="1111",sipMimebodySupport=1, gtdcaptypeprop="t3",GtdMsgFmt="c",IsupTransEarlyBackwardDisabled=0, IsupTransparencyDisabled=0
prov-sta::srcver="new",dstver="sip_0109"
prov-add:opc:name="opc",netaddr="1.1.1",netind=2,type="TRUEOPC",desc="The pgw point code"
prov-add:dpc:name="dpc1",netaddr="2.2.2",netind=2,desc="Orig. point code"
prov-add:extnode:name="SLT1",type="SLT",desc = "SLT-c2600"
prov-add:ss7path:name="ss7svc1",mdo="Q761_GERMAN",dpc="dpc1",opc="opc",custgrpid="1111",de sc="SS7 service to DPC-2-2-2"
prov-add:lnkset:name="linkset1",desc="Linkset 1",apc="dpc1",type="IP",proto="SS7-ITU"
prov-add:SESSIONSET:name="c7-2611",ipaddr1="IP_Addr1",port=7000,peeraddr1="172.22.121.246" ,peerport=7000,extnode="SLT1",type="BSMV0"
prov-add:ss7route:name="route1",opc="opc",dpc="dpc1",lnkset="linkset1",pri=1,desc="Route to DPC-2-2-2"
prov-add:c7iplnk:name="slink1-1",Pri=1,slc=0,lnkset="linkset1",sessionset="c7-2611",timesl ot=0,desc="Signal link 1-1"
prov-add:extnode:name="mgcp1",desc = "external node - mgcp1",type="AS5300"
prov-add:mgcppath:name="sp1-mgcp1",desc = "signal service - mgcp1",extnode = "mgcp1"
prov-add:iplnk:name="sc1-mgcp1",desc = "sigchannel 1 for mgcp sig path 1",svc = "sp1-mgcp1",ipaddr = "IP_Addr1",port = 2427,peeraddr = "172.22.121.164",peerport = 2427,pri = 1
prov-add:files:name="TKGFile",file="two_trunkgroup.dat",action="import"
prov-add:files:name="BCFile",file="two_bear.dat",action="import"
numan-add:dialplan:custgrpid="1111"
numan-add:resultset:custgrpid="1111", name="rset1"
numan-add:resultset:custgrpid="1111", name="rset2"
prov-add:rttrnkgrp:name="1000",type=1,reattempts=3,queuing=0,cutthrough=1
prov-add:rttrnkgrp:name="2000",type=1,reattempts=3,queuing=0,cutthrough=1
prov-add:rttrnk:name="rtnk2", trnkgrpnum=2000
prov-add:rttrnk:name="rtnk1", trnkgrpnum=1000
prov-add:rtlist: name="rlst1", rtname="rtnk1"
prov-add:rtlist: name="rlst2", rtname="rtnk2"
numan-add:resulttable:custgrpid="1111",name="rtab1",resulttype="ROUTE",dw1="rlst1", setname="rset1"
numan-add:resulttable:custgrpid="1111",name="rtab2",resulttype="ROUTE",dw1="rlst2", setname="rset2"
numan-add:bdigtree:custgrpid="1111",digitstring="510",callside="originating",setname="rset 1"
numan-add:bdigtree:custgrpid="1111",digitstring="520",callside="originating",setname="rset 2"
prov-add:trnkgrpprop:name="1000",sipMimeBodySupport="1", IsupTransparencyDisabled=0
prov-add:sippath:name="sip-sigpath",mdo="IETF_SIP",desc="SIP sigpath"
prov-add:siplnk:name="sip-sigchan",ipaddr="IP_Addr1",svc="sip-sigpath",port=5060,pri=1,des c="SIP sigchan"
prov-add:siplnk:name="sip-sigchan1",ipaddr="IP_Addr2",svc="sip-sigpath",port=5060,pri=2,de sc="SIP sigchan"
prov-add:trnkgrp:name="3333",svc="sip-sigpath",type="SIP_IN"
prov-add:trnkgrpprop:name="3333",custgrpid="1111",Support183="3",Localport="5060",MGCdomai n="172.22.121.157",MGCsipversion="SIP/2.0",InvitetimerT1 ="1000",gentimerT1="500",Fromfield="anonymous",maxRedirectCnt="5"
prov-add:trnkgrp:name="2222",svc="sip-sigpath",type="IP_SIP"
prov-add:trnkgrpprop:name="2222",custgrpid="1111",MGCdomain="172.22.121.157"
prov-add:siprttrnkgrp:name="2222",url="172.22.121.158",srvrr=0,sipproxyport=5060,version=" 2.0",cutthrough=1,extsupport=1
prov-add:rttrnk:name="rlst333",trnkgrpnum=2222
prov-add:rtlist:name="rlst333",rtname="rlst333"
numan-add:resultset:custgrpid="1111", name="rset333"
numan-add:resulttable:custgrpid="1111",name="rtab333",resulttype="ROUTE",dw1="rlst333", setname="rset333"
numan-add:bdigtree:custgrpid="1111",digitstring="333",callside="originating",setname="rset 333"
numan-add:bdigtree:custgrpid="1111",digitstring="999",callside="originating",setname="rset 333"
numan-add:bdigtree:custgrpid="1111",digitstring="666",callside="originating",setname="rset 333"
numan-add:bdigtree:custgrpid="1111",digitstring="555",callside="originating",setname="rset 333"
prov-add:trnkgrp:name="7777",svc="sip-sigpath",type="IP_SIP"
prov-add:trnkgrpprop:name="7777",custgrpid="1111",MGCdomain="172.22.121.157"
prov-add:siprttrnkgrp:name="7777",url="172.22.121.233",srvrr=0,sipproxyport=5060,version=" 2.0",cutthrough=1,extsupport=1
prov-add:rttrnk:name="rlst777",trnkgrpnum=7777
prov-add:rtlist:name="rlst777",rtname="rlst777"
numan-add:resultset:custgrpid="1111", name="rset777"
numan-add:resulttable:custgrpid="1111",name="rtab777",resulttype="ROUTE",dw1="rlst777", setname="rset777"
numan-add:bdigtree:custgrpid="1111",digitstring="777",callside="originating",setname="rset 777"
prov-add:trnkgrp:name="550",svc="sip-sigpath",type="IP_SIP"
prov-add:trnkgrpprop:name="550",custgrpid="1111",MGCdomain="172.22.121.157",gtdmsgfmt="c", isuptransearlybackwarddisabled="0",gtdcaptypeprop="t1",sipMimeBodySupport ="1", IsupTransparencyDisabled=0
prov-add:gtdparam:name="t1",gtdparamstring="ALL"
prov-add:siprttrnkgrp:name="550",url="172.22.121.158",srvrr=0,sipproxyport=5060,version="2 .0",cutthrough=1,extsupport=1
prov-add:rttrnk:name="rlst550",trnkgrpnum=550
prov-add:rtlist:name="rlst550",rtname="rlst550";
numan-add:resultset:custgrpid="1111", name="rset550"
numan-add:resulttable:custgrpid="1111",name="rtab550",resulttype="ROUTE",dw1="rlst550", setname="rset550"
numan-add:bdigtree:custgrpid="1111",digitstring="550",callside="originating",setname="rset 550"
prov-add:trnkgrp:name="408",svc="sip-sigpath",type="IP_SIP"
prov-add:trnkgrpprop:name="408",custgrpid="1111",MGCdomain="172.22.121.157",sipMimeBodySup port="1"
prov-add:siprttrnkgrp:name="408",url="172.22.121.158",srvrr=0,sipproxyport=5060,version="2 .0",cutthrough=1,extsupport=1
prov-add:rttrnk:name="rlst408",trnkgrpnum=408
prov-add:rtlist:name="rlst408",rtname="rlst408"
numan-add:resultset:custgrpid="1111", name="rset408"
numan-add:resulttable:custgrpid="1111",name="rtab408",resulttype="ROUTE",dw1="rlst408", setname="rset408"
numan-add:bdigtree:custgrpid="1111",digitstring="408",callside="originating",setname="rset 408"
prov-add:dnsparam:dnsserver1="172.22.121.42",dnsserver2="171.69.2.133",cachesize="500",ttl ="3600",policy="hierarchy",querytimeout="1000",keepalive="30"
prov-cpy
prov-stp

Command Reference

This section documents modified Man-Machine Language (MML) commands. All other commands are documented in the Cisco Media Gateway Controller Software Release x MML Command Reference Guide.

Modified MML Commands

This section contains the MML commands that were modified for this feature.

PROV-ADD—Add Provisioning Component

Purpose:

This MML command adds a component to the Cisco MGC configuration.

Syntax:

prov-add:<comp>:name="<MML name>",<param name>=<param value>,...
prov-add:lnksetprop:name="<protocol family>",<param name>=<param value>,...

Input Description:

•lnksetprop—MML NE component consisting of parameters for which you can tune linkset communications. See Appendix A of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a list of linkset property parameters.

•comp—MML component type name for the type of configuration you are creating. The component type must match one of the component types listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide. If <comp> is EXTNODE, then the <param name> TYPE must be present and needs to take a set of values (refer to the second example below).

•name—MML component name for the new object you are creating (as many as ten characters).

•protocol family—Name of the protocol family for which you are provisioning linkset properties. Use PROV-RTRV:VARIANTS for a list of protocol families configured for your system.

•param name—The name of a valid configuration parameter for the specified component type. Parameter names are listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

•param value—The value you want to assign to the parameter. If the parameter value is a string, it should be surrounded by quotation marks.

To define more than one parameter, enter additional param name=param value descriptions on the command line.

Example:

The MML command shown in the following example adds the origination point code for the MGC configuration:


mml> PROV-ADD:opc:NAME="opc",DESC="Point code of CP1",netaddr="0.0.1", netind=2,type="TRUEOPC"
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;

Example:

The MML command shown in the following example adds an external node to the MGC configuration:


mml> PROV-ADD:EXTNODE:NAME="TOTO2",DESC="TATA",TYPE="MGX8260"
Media Gateway Controller - MGC-02 2000-05-08 18:05:55
M COMPLD
"extnode"
;

Comments:

Performance Impact Category: B

Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a description of using the PROV commands for provisioning and for a description of components, parameter names, and parameter values used in provisioning the MGC.


PROV-ED—Modify Provisioned Component

Purpose:

This MML command modifies a provisioned component.

Note Only those parameters that need to be modified must be entered.

Syntax:

prov-ed:<comp>:name="<MML name>",<param name>=<param value>,...
prov-add:lnksetprop:name="<protocol family>",<param name>=<param value>,...

Input Description:

•lnksetprop—MML NE component consisting of parameters for which you can tune linkset communications. See Appendix A of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a list of linkset property parameters.

•comp—MML component type name for the type of component you are modifying. The entered parameter must match one of the component types listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

•name—MML name for the component you are modifying. You cannot change the component name.

•protocol family—Name of the protocol family for which you are provisioning linkset properties. Use PROV-RTRV:VARIANTS for a list of protocol families configured for your system.

•param name—The name of each configuration parameter you want to change. The parameter names must be valid for the specified component type. Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a description of components, parameter names, parameter descriptions, and parameter values.

•param value—The new value you want to assign to the parameter. If the parameter value is a string, it should be surrounded by quotation marks.

Note To modify more than one parameter, enter additional param name=value descriptions on the command line.

Example:

The MML command shown in the following example changes the description of the provisioned point code "opc":

mml> PROV-ED:opc:NAME="opc", DESC="Point code for this SSP"
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;

Comments:

Perform PROV-STA—Start Provisioning Session before using this command.

Performance Impact Category: B

Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for information on using the PROV commands for provisioning and for a description of components, parameter names, and parameter values used in provisioning.


Reference Information

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

• Properties

• External Node Types

• Provisioning Worksheets

• Mapping GTD Codes for ISUP Messages and Parameters

Properties

The properties in this section are added or modified for this feature. For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

The parent objects for the properties involved in this feature are found in Table 1.

Table 1 Software Properties Related to this Feature

Property Name
Parent Object
AVM
DPNSS
EISUP
IOCC
ISDNPRI
MGCP
RLM
SESSION
SGCP
SS7-ANSI
SS7-China
SS7-ITU
SS7-Japan
SS7-UK
TALI-IOCC
TCAPOverIP
TrunkGroup
VSI

GtdCapTypeProp

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

X

 

GtdMsgFmt

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

X

 

IsupTransparencyDisabled

       

X

       

X

 

X

       

X

 

IsupTransEarlyBackwardDisabled

 

 

 

 

X

 

 

 

 

 

 

 

 

 

 

 

X

 

sipMimeBodySupport

 

 

 

 

 

 

 

 

 

X

 

X

X

X

 

 

X

 


The properties added and modified for this feature are described in Table 2.

Table 2 Properties 

Property
Definition

*.GtdCapTypeProp

This property is used by the MGC as a pointer to the subset of GTD parameters that the user desires to support. Value range: t0 (no GTD support) to any string of 1 through 20 characters that identifies a GTD parameter string.

Default: t0

*.GtdMsgFmt

Indicates the GTD message format mode. The format can be compact or verbose mode. Compact mode is the short format and the field names are not passed in the GTD parameter string. When in verbose mode, both the field names and the values are passed. Values: c (compact) or v (verbose).

Default: c

*.IsupTransparencyDisable

Permits disabling of the ISUP Transparency feature for a particular trunk group.

Values:

1-True, ISUP Transparency feature is disabled
0-False, ISUP Transparency feature is enabled

Default: 1

IsupTransEarlyBackwardDisable

Indicates if the egress MGC is to send an end-to-end message, called Early Backward Call Setup Message, immediately after receiving the call setup message with GTD information about the outgoing protocol variant. Values: 0 (enable) or 1 (disable).

Default: 0

sipMimeBodySupport

Determines whether SIP-T or SIP-GTD special processing of data is supported on a trunk group.

Valid Values:
0-None
1-SIP-T supported
2-SIP-GTD supported

Default Value: 0 - None


External Node Types

This section lists the valid external node types for this release of Cisco MGC software.

Table 3 External Node Types  

External Node MML Name
Supported Signaling Service Types
AS3660

MGCP IPFAS NAS

AS5200

IPFAS NAS

AS5300

MGCP IPFAS NAS

AS5350

MGCP IPFAS NAS BSMV0

AS5400

MGCP IPFAS NAS BSMV0

AS5800

IPFAS NAS

AS5850

IPFAS NAS

AS7200

MGCP IPFAS NAS

CAT8510

MGCP

CAT8540

MGCP

H323

EISUP

LS1010
MGCP
MC3810

MGCP IPFAS

MGC

EISUP

MGX8260

MGCP IPFAS NAS

MGX8850

MGCP IPFAS

SLT

BSMV0

TALISS7

SS7SG

ITP

M3UA SUA

UNKNOWN

UNKNOWN


Provisioning Worksheets

The tables in this section are for planning your provisioning data, specific to this feature. For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Table 4 SS7 Signaling Service Worksheet  

Name
Side
MDO
DPC
CustgrpId
OPC
Description

ss7svc1 

n/a

Q761_GERMAN

dpc1 

1111 

opc1

SS7 service to DPC 2-2-2

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

 

 

 

 

 

   

Table 5 External Node Worksheet Example  

Name
Type
ISDN Signaling Type
Group
Description

mgcp1

AS5300

n/a

n/a

external node - mgcp1

         
         
         
         
         
         
         
         
         

Table 6 SIP Signaling Service Worksheet  

Name
MDO
Description

sip-sigpath 

IETF_SIP

SIP sigpath

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Table 7 SIP IP Link Worksheet  

Name
Port
Priority
IP Address
SIP Path
Description

sip-sigchan 

5060

1

IP_Addr1 

sip-sigpath 

SIP signaling channel

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Table 8 Trunk Group Worksheet  

Name
Signaling Service
Type
Select Sequence
Timeslot Queuing

7777

sip-sigpath

IP_SIP

n/a

N

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

 

 

     

Table 9 Switched Trunk Worksheet 

Trunk ID
Trunk Group Number
Span
CIC
Coding Unit
End Point
Span Size

10101

25535

100

1

signal1

fixed

1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 10 Modified Trunk Group Property Values Worksheet  

Name
Value
   

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 11 Modified DNS Parameter Values Worksheet  

Name
Value
   

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Mapping GTD Codes for ISUP Messages and Parameters

Table 12 lists the GTD codes associated with ISUP message types. The parameter names are derived from the Q.763 1993 specification.

Table 12 GTD Codes for Q.763 1993 Messages  

Q.763 1993 Message Type
GTD Base Message Type

Address Complete

ACM

Answer

ANM

Call Progress

CPG

Charge Information

CRG

Confusion

CFN

Connect

CON

Continuity

COT

Facility

FAC

Facility Accepted

FAA

Facility Reject

FRJ

Facility Request

FAR

Forward Transfer

FOT

Identification Request

IDR

Identification Response

IRS

Information

INF

Information Request

INR

Initial Address

IAM

Network Resource Management

NRM

Overload

OLM

Pass Along

PAM

Release

REL

Release Complete

RLC

Resume

RES

Segmentation

SGM

Subsequent Address

SAM

Suspend

SUS

User-to-user Information

USR


Table 13 lists the GTD codes associated with ISUP parameter types. The parameter names are derived from the Q.763 1993 specification.

Table 13 GTD Codes for Q.763 1993 Parameters  

Q.763 1993 Parameter
GTD Base Parameter

Access Delivery Information

ADI

Access Transport

ATP

Automatic Congestion Level

ACL

Backward Call Indicators

BCI

Call Diversion Information

CDI

Call History Information

CHI

Call Reference

CRF

Called Party Number

CPN

Calling Party Number

CGN

Calling's Party Category

CPC

Cause Indicators

CAI

Closed User Group Interlock Code

GIC

Connected Number

CNN

Connection Request

CNR

Continuity Indicators

CTI

Echo Control Information

ECI

End of Optional Parameters Indicator (Not Applicable)

 

Event Information

EVI

Facility Indicators

FAI

Forward Call Indicators

FCI

Generic Digits

GED

Generic Notification

GNO

Generic Number

 

Generic Reference

GRF

Information Indicators

INI

Information Request Indicators

IRI

Location Number

LON

MCID Request Indicator

MRI

MCID Response indicator

MCR

Message Compatibility Information

MCI

MLPP precedence

MLP

Nature of Connection Indicators

NOC

Network Specific Facilities

NSF

Optional Backward Call Indicators

OBI

Optional Forward Call Indicators

OFI

Original Called Number

OCN

Originating ISC point Code

ISC

Parameter Compatibility Information

 

Propagation Delay Counter

PDC

Redirecting Number

RGN

Redirection Information

RNI

Redirection Number

RNN

Redirection Number Restriction

RNR

Remote Operations

RMO

Service Activation

SEA

Signalling Point Code

SPC

Subsequent Number

SUN

Suspend/Resume Indicators

SRI

Transit Network Selection

TNS

Transmission Medium Requirement

TMR

Transmission Medium Requirement Prime

 

Transmission Medium Used

TMU

User Service Information

USI

User Service Information Prime

USP

User Teleservice Information

UTI

User-To-User Indicators

UUI

User-To-User Information

UUS


Table 14 lists the GTD codes associated with ISUP message types. The parameter names are derived from the ANSI T1.1133 1995 specification

Table 14 GTD Codes for ANSI T1.1133 1995 Messages  

ANSI T1.1133 1995 Message Type
GTD Base Message Type

Address Complete

ACM

Answer

ANM

Call Progress

CPG

Confusion

CFN

Continuity

COT

EXIT

EXM

Facility

FAC

Forward Transfer

FOT

Information

INF

Information Request

INR

Initial Address

IAM

Pass Along

PAM

Release

REL

Release Complete

RLC

Resume

RES

Suspend

SUS

User-to-user Information

USR


Table 13 lists the GTD codes associated with ISUP parameter types. The parameter names are derived from the Q.763 1993 specification.

Table 15 GTD Codes for ANSI T1.1133 1995 Parameters  

ANSI T1.113 1995 Parameter
GTD Base Parameter

Access Transport

ATP

Automatic Congestion Level

ACL

Backward Call Indicators

BCI

Business Group

BSG

Called Party Number

CPN

Calling Party Number

CGN

Calling's Party Category

CPC

Carrier Identification

CID

Carrier Selection Information

CSI

Cause Indicators

CAI

Charge Number

CHN

Connection Request

CNR

Continuity Indicators

CTI

Egress Service

EGR

End of Optional Parameters Indicator (Not Applicable)

 

Event Information

EVI

Forward Call Indicators

FCI

Generic Address

GEA

Generic Digits

GED

Generic Name

GEN

Hop Counter

HOC

Information Indicators

INI

Information Request Indicators

IRI

Jurisdiction Information

JUR

Nature of Connection Indicators

NOC

Network Specific Facilities

NSF

Network Transport

NET

Notification Indicator

GNO

Operator Services Information

OSI

Optional Backward Call Indicators

OBI

Original Called Number

OCN

Originating Line Information

OLI

Outgoing Trunk Group Number

OTN

Precedence

MLP

Propagation Delay Counter

PDC

Redirecting Number

RGN

Redirection Information

RNI

Remote Operations

RMO

Service Code

SEA

Special Processing Request

SPR

Suspend/Resume Indicators

SRI

Transaction Request

TRR

Transit Network Selection

TNS

Transmission Medium Used

TMU

User Service Information

USI

User Service Information Prime

USP

User-To-User Indicators

UUI

User-To-User Information

UUS


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

Table 16 Glossary  

Term
Definition

APC

Alternate Point Code

ANSI

American National Standards Institute

ATM

Asynchronous Transfer Mode

BTNUP

British Telecom Network User Part

CAS

Channel Associated Signaling

CIC

Carrier Identification Code

DNS

Domain Name Server

DPC

Destination Point Code

DPNSS

Digital Private Network Signaling System

FAS

Facility Associated Signaling

IETF

Internet Engineering Task Force

IP

Internet Protocol

ISDN

Integrated Services Digital Network

ISUP

ISDN User Part

ITU

International Telecommunication Union

IUA

ISDN Q.921 User Adaptation Layer

MGC

Media Gateway Controller

MGCP

Media Gateway Control Protocol

MIB

Managed Information Base

MIME

Multipurpose Internet Mail Extensions

MML

Man-Machine Language

OPC

Originating Point Code

PRI

Primary Rate Interface

Q.GTD.1

ITU SG11 draft for Generic Transparency Detector Syntax Definition

Q.GTD.2

ITU SG11 draft for Generic Transparency Detector Usage Rules and Mappings

QSIG

Unified International corporate network signaling standard.

RFC

Return For Comment—A proposed standards document. SIP-T conforms to an RFC.

SIP

Session Initiation Protocol

SIP-GTD

Session Initiation Protocol - Generic Transparency Descriptor

SIP-T

Session Initiation Protocol for Telephones

SS7

Signaling System 7

TDM

Time-Division Multiplexing

TUP

Telephone User Part


hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Mar 12 16:49:10 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.