Cisco PGW 2200 Softswitch

Table Of Contents

Support for Three Tuple Media Gateways

Feature Overview

Benefits

Restrictions

Related Features

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites for Using This Feature

Provisioning Tasks

Adding DPNSS Signaling Services

Adding D-Channels

Modifying Cisco 1700, 2600 or 3700 Series External Nodes To Use Old Interface Numbering Method

Provisioning Examples

Command Reference

PROV-ADD:dchan—Provision a D-Channel (Release 9.5(2))

PROV-ADD:dpnsspath—Adding a DPNSS Signaling Service (Release 9.5(2))

PROV-ED:dchan—Modify a D-Channel (Release 9.5(2))

PROV-ED:dpnsspath—Modifying a DPNSS Signaling Service (Release 9.5(2))

Reference Information

Provisioning Prerequisites

Collecting DPNSS Signaling Service Data

Collecting D-Channel Data

Provisioning Basics

Starting a Provisioning Session

Saving and Activating Your Provisioning Changes

Ending a Provisioning Session Without Activating Your Changes

Retrieving Provisioning Data

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

Components

D-Channel

DPNSS Signaling Service

External Node

External Node Types

Provisioning 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

Support for Three Tuple Media Gateways

---

Document Release History

Publication Date	Comments
October 7, 2005	Initial version of the document.

Feature History

Release	Modification
Release 9.5(2)	This feature was introduced in this release.

This document describes the Support for Three Tuple Media Gateways (MGWs) 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

•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

This feature provides support in the Cisco Media Gateway Controller (MGC) software for the Cisco MGWs that use the three tuple format for addressing the interfaces on the platform. There are several Cisco MGWs that use the three tuple format. This enhanced interface numbering method available with Cisco IOS Release 12.3(11)T and later. The enhanced numbering method adds the ability to configure the value of the subunit for MGWs that use three tuples (slot, subunit, and port) to define interfaces. In prior Cisco IOS releases, the subunit value was always set to 0 when three tuples were required. This feature modifies the interface definitions in the Cisco MGC software for the provisioning components that are used for data paths with the Cisco MGWs that use the three tuple format.

The Cisco MGC software still supports the existing interface numbering method. However, this feature introduces adds the string "_OLD" to external node type file names for the MGWs listed below to enable support for the old methold. If your system is going to use the existing interface numbering method and it interfaces with one of the following MGWs, you must use the prov-ed:extnode MML command to change the external node type to the new file name.

•Cisco 1751

•Cisco 1760

•Cisco 2600

•Cisco 2610XM

•Cisco 2611XM

•Cisco 2620

•Cisco 2621

•Cisco 2650X

•Cisco 2651XM

•Cisco 2691

•Cisco 3725

•Cisco 3745

Benefits

This feature provides the benefit described below.

Ensures that the Cisco PGW 2200 Interworks with the latest Cisco MGWs

This feature enables the Cisco PGW 2200 to interwork with the latest Cisco MGWs, and the latest versions of the Cisco IOS software.

Restrictions

This feature can be used only with the Cisco media gateways listed below and the media gateways must be running Cisco IOS 12.3(11)T and higher.

•Cisco 1751

•Cisco 1760

•Cisco 2600

•Cisco 2610XM

•Cisco 2611XM

•Cisco 2620

•Cisco 2621

•Cisco 2650X

•Cisco 2651XM

•Cisco 2691

•Cisco 2801

•Cisco 2811

•Cisco 2821

•Cisco 2851

•Cisco 3725

•Cisco 3745

•Cisco 3825

•Cisco 3845

Related Features

This feature is related to the enhanced interface numbering functionality introduced in Cisco IOS Release 12.3(11)T. You can find more information on this functionality at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vvfax_c/callc_c/ccm_c/int_bri.htm

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 that support the Cisco MGC software are described in the Cisco Media Gateway Controller Hardware Installation Guide.

Supported Standards, MIBs, and RFCs

Standards

No standards are associated with this feature.

MIBs

No new or modified MIBs are supported by this feature. Existing MIBs are used to support this feature. For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Release 9 Management Information Base Guide.

RFCs

No RFCs are associated with this feature.

Prerequisites for Using This Feature

You must have Cisco MGC software Release 9.5(2) to use this feature. Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2).

The Cisco MGWs associated with your Cisco PGW 2200 must be running Cisco IOS 12.3(11)T and higher.

Provisioning Tasks

This section covers the following provisioning topics:

•Adding DPNSS Signaling Services

•Adding D-Channels

•Modifying Cisco 1700, 2600 or 3700 Series External Nodes To Use Old Interface Numbering Method

Adding DPNSS Signaling Services

To add MGCP signaling services to your provisioning data, perform the following steps:

---

Step 1 If you do not already have an active provisioning session, start one as described in the "Starting a Provisioning Session" section.

Step 2 Enter the following command to add a DPNSS signaling service:

mml>prov-add:dpnsspath:name="name", desc="description", extnode="mgw", 
mdo="dpnss_btnr188", custgrpid="idnum", sigslot=sslot, sigport=sport, subunit=sunit

Where:

•name—The name you want to give to the DPNSS signaling service. 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—An assigned name. It can be as many as 128 alphanumeric characters in length.

•mgw—MML name of a previously defined DPNSS external node.

•idnum—VNET ID, a four-digit ID; (0000).

•sslot—Physical slot on the Cisco media gateway on which the link is terminated.

–For Cisco 2600, 3600, and 3700 series media gateways, the valid values are integers from
0 to 63. Default value is 0.

–For all other media gateways, the valid values are integers from 0 to 15. Default value is 0.

•sport—Physical port of the associated slot on the Cisco media gateway. Valid values are integers from 0 to 167. Default value is 0.

•sunit—Physical subunit on the Cisco media gateway. Valid values are 0 and 1. Default value is 0.

For example, to add a DPNSS signaling service named brisvc1, you would enter the following command:

mml>prov-add:dpnsspath:name="brisvc1", extnode="dpnss-01", desc="DPNSS service", 
mdo="dpnss_btnr188", custgrpid="V123", sigslot=4, sigport=1, subunit=1

Step 3 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.

---

Adding D-Channels

To add D-channels to your provisioning data, perform the following steps:

---

Step 1 If you do not already have an active provisioning session, start one as described in the "Starting a Provisioning Session" section.

Step 2 Enter the following command to add a D-channel:

mml>prov-add:dchan:name="name", desc="description", svc="BRI", pri=1, 
[sessionset="ssetname"|tcplink="lnkname"], sigslot=sslot, sigport=sport, subunit=sunit

Where:

•name—The name you want to give to the D-channel. 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—An assigned name. It can be as many as 128 alphanumeric characters in length.

•ssetname—MML name of a previously provisioned session set (used for PRI connections only).

•lnkname—MML name of a previously provisioned Backhaul TCP link (used for BRI connections only).

•sslot—Physical slot on the Cisco media gateway on which the link is terminated.

–For Cisco 2600, 3600, and 3700 series MGWs, the valid values are integers from 0 to 63. Default value is 0.

–For all other MGWs, the valid values are integers from 0 to 15. Default value is 0.

---

Note This parameter must be set to 0 for QSIG/Q.931 over BRI Backhaul D-channels when the associated external node is a Cisco 17xx.

---

•sport—Physical port of the associated slot on the Cisco MGW. Valid values are integers from 0 to 167. Default value is 0.

•sunit—Physical subunit on the Cisco MGW. Valid values are 0 through 3. Default value is 0.

For example, to add an QSIG/Q.931 over BRI Backhaul D-channel named bridchan1, enter the following command:

mml>prov-add:dchan:NAME="bridchan1",DESC="QSIG BRI D channel 1", SVC="BRI", PRI="1", 
TCPLINK="britcp1", sigslot="4", sigport="1", subunit="1"

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

---

Modifying Cisco 1700, 2600 or 3700 Series External Nodes To Use Old Interface Numbering Method

To modify a Cisco 1700, 2600, or 3700 series external node to use the old interface numbering method, 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 edit the MDO file of the external node:

mml>prov-ed:extnode:name="name", type="old_type"

Where:

•name—MML name of the Cisco media gateway external node to be modified.

•old_type—File name of the MDO file name to support the old interface numbering method, from the following list:

–C1751_OLD

–C1760_OLD

–C2600_OLD

–C2610XM_OLD

–C2611XM_OLD

–C2620_OLD

–C2621_OLD

–C2650X_OLD

–C2651XM_OLD

–C2691_OLD

–C3725_OLD

–C3745_OLD

For example, to modify a Cisco 2691 external node named va-2691-01, you enter the following command:

mml>prov-ed:extnode:name="va-2691-01", type="C2691_OLD"

Step 3 Repeat the above step for each external node you want to modify in your provisioning data.

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

---

Provisioning Examples

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

prov-add:extnode:name="bri-2600-1",desc="BRI Backhaul C2600",type="C2600"

prov-add:bripath:name="brisvc1",extnode="bri-2600-1",desc="BRI service to 
C2600",mdo="ETS_300_172",side="network",custgrpid="V123",crlen="2"

prov-add:mgcppath:name="mgcpsvc1",extnode="bri-3640-01",desc="MGCP service to C2600"

prov-add:tcplink:name="tcp1",ipaddr="IP_Addr1",port=7000,peeraddr="5.5.5.6",peerport=8001, 
extnode="bri-2600-1",type="BRI"

prov-add:splnk:name="mgcpsigchan1", ipaddr="IP_Addr1", peeraddr="147.28.210.65", 
svc="mgcpsvc1", port=2427, peerport=2427, iproute1=iproute1, pri=1, desc="MGCP sigchan 1"

prov-add:dchan:name="dchan1",desc="BRI D Channel 1", pri=1,svc="brisvc1",tcplink="tcp1", 
sigslot=1, sigport=1,subunit=0

prov-rtrv:bripath:"all"

Command Reference

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

PROV-ADD:dchan—Provision a D-Channel (Release 9.5(2))

 

Purpose:	This MML command represents a D-channel used on the Cisco MGC.
Syntax:	prov-add:dchan:name="name", desc="description", svc="BRI", pri=1, [sessionset="ssetname"|tcplink="lnkname"], sigslot=sslot, sigport=sport, subunit=sunit
Input Description:	Where: •name—The name you want to give to the D-channel. 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—An assigned name. It can be as many as 128 alphanumeric characters in length. •ssetname—MML name of a previously provisioned session set (used for PRI connections only). •lnkname—MML name of a previously provisioned Backhaul TCP link (used for BRI connections only). •sslot—Physical slot on the Cisco media gateway on which the link is terminated. –For Cisco 2600, 3600, and 3700 series MGWs, the valid values are integers from 0 to 63. Default value is 0. –For all other MGWs, the valid values are integers from 0 to 15. Default value is 0. Note This parameter must be set to 0 for QSIG/Q.931 over BRI Backhaul D-channels when the associated external node is a Cisco 17xx. •sport—Physical port of the associated slot on the Cisco MGW. Valid values are integers from 0 to 167. Default value is 0. •sunit—Physical subunit on the Cisco MGW. Valid values are 0 through 3. Default value is 0.
Provisioning Rules:	The following rules apply when you are creating or editing D-channels: •Backup D-channels for QSIG/Q.931 Over BRI Backhaul signaling services are not supported. •The priority for QSIG/Q.931 Over BRI Backhaul D-channels should be set to 1. •Session sets are used only in support of IPFAS D-channels. •TCP links are used only in support of QSIG/Q.931 Over BRI Backhaul D-channels. •Up to 1000 D-channels can be provisioned against a single IP address and port combination used by your Backhaul TCP links. Since the Cisco MGC supports a maximum of two IP address and port combinations, you can provision a maximum of 1000 D-channels for a QSIG/Q.931 Over BRI Backhaul signaling service.
Example:	The MML command shown in the following example provisions an IP link: mml>prov-add:dchan:NAME="bridchan1",DESC="QSIG BRI D channel 1", SVC="BRI", PRI="1", TCPLINK="britcp1", sigslot="4", sigport="1", subunit="1"

PROV-ADD:dpnsspath—Adding a DPNSS Signaling Service (Release 9.5(2))

 

Purpose:	This MML command represents a DPNSS path backhauled over IP to a media gateway.
Syntax:	prov-add:dpnsspath:name="name", desc="description", extnode="mgw", mdo="dpnss_btnr188", custgrpid="idnum", sigslot=sslot, sigport=sport, subunit=sunit
Input Description:	Where: •name—The name you want to give to the DPNSS signaling service. 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—An assigned name. It can be as many as 128 alphanumeric characters in length. •mgw—MML name of a previously defined DPNSS external node. •idnum—VNET ID, a four-digit ID; (0000). •sslot—Physical slot on the Cisco media gateway on which the link is terminated. –For Cisco 2600, 3600, and 3700 series media gateways, the valid values are integers from 0 to 63. Default value is 0. –For all other media gateways, the valid values are integers from 0 to 15. Default value is 0. •sport—Physical port of the associated slot on the Cisco media gateway. Valid values are integers from 0 to 167. Default value is 0. •sunit—Physical subunit on the Cisco media gateway. Valid values are 0 and 1. Default value is 0.
Provisioning Rules:	The following attributes cannot be modified: •NAME •EXTNODE The following rules apply when creating/editing DPNSS signaling paths: •The maximum number of combined DPNSSPATHs and NASPATHs per IUA External Node is IUA.maxSigPathsPerExtNode = 112 from XECfgParm.dat. Since DPNSSPATHs and NASPATHs can share the same association, the existing IUA.maxNasPathsPerExtNode will be renamed to IUA.maxSigPathsPerExtNode in order to support both. •The maximum number of combined DPNSSPATHs and IUA NASPATHs is IUA.maxSigPaths = 1500 from XECfgParm.dat. The existing IUA.maxNasPaths will be renamed to IUA.maxSigPaths in order to support both with the same validation limit. •Check the maximum number of external nodes with IUA type using the parameter IUA.maxExtNodes = 256. This parameter will be shared by both naspath and dpnsspath. The existing parameter IUA.maxNasExtNodes will be renamed to IUA.maxExtNodes. •An ASSOCIATION must be define with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn't been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still hasn't been defined when provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped. •If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message will be issued to inform the user that the DPNSSPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped.
Example:	prov-add:dpnsspath:name="brisvc1", extnode="dpnss-01", desc="DPNSS service", mdo="dpnss_btnr188", custgrpid="V123", sigslot=4, sigport=1, subunit=1

PROV-ED:dchan—Modify a D-Channel (Release 9.5(2))

 

Purpose:	This MML command represents a D-channel used on the Cisco MGC.
Syntax:	prov-ed:dchan:name="name", desc="description", svc="BRI", pri=1, [sessionset="ssetname"|tcplink="lnkname"], sigslot=sslot, sigport=sport, subunit=sunit
Input Description:	Where: •name—The name of a previously provisioned D-channel. •description—An assigned name. It can be as many as 128 alphanumeric characters in length. •ssetname—MML name of a previously provisioned session set (used for PRI connections only). •lnkname—MML name of a previously provisioned Backhaul TCP link (used for BRI connections only). •sslot—Physical slot on the Cisco media gateway on which the link is terminated. –For Cisco 2600, 3600, and 3700 series MGWs, the valid values are integers from 0 to 63. Default value is 0. –For all other MGWs, the valid values are integers from 0 to 15. Default value is 0. Note This parameter must be set to 0 for QSIG/Q.931 over BRI Backhaul D-channels when the associated external node is a Cisco 17xx. •sport—Physical port of the associated slot on the Cisco MGW. Valid values are integers from 0 to 167. Default value is 0. •sunit—Physical subunit on the Cisco MGW. Valid values are 0 through 3. Default value is 0.
Provisioning Rules:	The following rules apply when you are creating or editing D-channels: •Backup D-channels for QSIG/Q.931 Over BRI Backhaul signaling services are not supported. •The priority for QSIG/Q.931 Over BRI Backhaul D-channels should be set to 1. •Session sets are used only in support of IPFAS D-channels. •TCP links are used only in support of QSIG/Q.931 Over BRI Backhaul D-channels. •Up to 1000 D-channels can be provisioned against a single IP address and port combination used by your Backhaul TCP links. Since the Cisco MGC supports a maximum of two IP address and port combinations, you can provision a maximum of 1000 D-channels for a QSIG/Q.931 Over BRI Backhaul signaling service.
Example:	The MML command shown in the following example modifies a D-channel: mml>prov-ed:dchan:NAME="bridchan1", sigslot="3"

PROV-ED:dpnsspath—Modifying a DPNSS Signaling Service (Release 9.5(2))

 

Purpose:	This MML command modifies a DPNSS path backhauled over IP to a media gateway.
Syntax:	prov-ed:dpnsspath:name="name", desc="description", custgrpid="idnum", sigslot=sslot, sigport=sport, subunit=sunit
Input Description:	Where: •name—The name of a previously provisioned DPNSS signaling service. •description—An assigned name. It can be as many as 128 alphanumeric characters in length. •idnum—VNET ID, a four-digit ID; (0000). •sslot—Physical slot on the Cisco media gateway on which the link is terminated. –For Cisco 2600, 3600, and 3700 series media gateways, the valid values are integers from 0 to 63. Default value is 0. –For all other media gateways, the valid values are integers from 0 to 15. Default value is 0. •sport—Physical port of the associated slot on the Cisco media gateway. Valid values are integers from 0 to 167. Default value is 0. •sunit—Physical subunit on the Cisco media gateway. Valid values are 0 and 1. Default value is 0.
Provisioning Rules:	The following attributes cannot be modified: •NAME •EXTNODE The following rules apply when creating/editing DPNSS signaling paths: •The maximum number of combined DPNSSPATHs and NASPATHs per IUA External Node is IUA.maxSigPathsPerExtNode = 112 from XECfgParm.dat. Since DPNSSPATHs and NASPATHs can share the same association, the existing IUA.maxNasPathsPerExtNode will be renamed to IUA.maxSigPathsPerExtNode in order to support both. •The maximum number of combined DPNSSPATHs and IUA NASPATHs is IUA.maxSigPaths = 1500 from XECfgParm.dat. The existing IUA.maxNasPaths will be renamed to IUA.maxSigPaths in order to support both with the same validation limit. •Check the maximum number of external nodes with IUA type using the parameter IUA.maxExtNodes = 256. This parameter will be shared by both naspath and dpnsspath. The existing parameter IUA.maxNasExtNodes will be renamed to IUA.maxExtNodes. •An ASSOCIATION must be define with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn't been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still hasn't been defined when provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped. •If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message will be issued to inform the user that the DPNSSPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped.
Example:	prov-ed:dpnsspath:name="brisvc1", sigslot=3

Reference Information

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

•Provisioning Prerequisites

•Provisioning Basics

•Components

•External Node Types

•Provisioning Worksheets

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

The DPNSS signaling service component type represents a DPNSS signaling path that is back-hauled over IP to/from a Network Access Server (destination). You must be ready to enter the following data:

•MML name

•Description of this component

•MDO file name (only one file currently supports DPNSS - dpnss_btnr188.mdo)

•MML name of associated external node

•Customer group ID

•Physical slot number on voice gateway

•Physical port number for slot on voice gateway

•Local subunit

You can define the parameters for your DPNSS Signaling Services in Table 0-5 in the "Provisioning Worksheets" section.

Collecting D-Channel Data

The D-channel component type represents the connection between the Cisco PGW 2200 and a Cisco BRI or PRI voice gateway. You must be ready to enter the following data:

•MML name

•Description of this component

•Signaling type

•Priority

•MML name of associated session set (for PRI connections only)

•MML name of associated Backhaul TCP link (for BRI connections only)

•Physical slot number on voice gateway

•Physical port number for slot on voice gateway

•Local subunit

You can define the parameters for your D-channels in Table 0-6 in the "Provisioning Worksheets" section.

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 might need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:

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

Where:

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

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

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

---

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

---

•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 or prov-dply MML command can severely impact your system's call processing performance, depending on the extent of your provisioning changes. We recommend that these commands be issued during a maintenance window when traffic is minimal.

---

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

---

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

---

---

Caution Do not use the prov-cpy command to save and activate your changes on a continuous-service Cisco MGC system (one with active and standby hosts). 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 for any future switchover operations.

---

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

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 for any individual component of 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 a 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.

Retrieving Data for All Components

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

prov-rtrv:all

Retrieving Data for All Components of a Particular Type

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

prov-rtrv:component:"all"

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

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

prov-rtrv:ss7path:"all"

Retrieving Data on the Current Provisioning Session

You can retrieve 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 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:

prov-rtrv:variants

Components

The sections below discuss the provisioning components that are modified for this feature. For information on the rest of the components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

D-Channel

The D-channel component type represents a D-channel used on the Cisco MGC. There can be a maximum of two channels per IPFAS (one primary and one backup). Its MML name is as follows:

• MML Name—DCHAN

The D-channel component structure is shown in Table 1.

Table 1 DCHAN Component Structure 

Parameter MML Name	Parameter Description	Parameter Value (Default)
NAME	Unique component name used in MML commands	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to 128 characters.
PRI	Priority	1 through 65535; (1).
SVC	MML name of the supported signaling service	MML name of a previously configured signaling service (IPFAS or QSIG/Q.931 Over BRI Backhaul only).
SESSIONSET	MML name of session set (restricted)	MML name of a previously provisioned session set. This parameter is used only for D-channels associated with IPFAS signaling services.
TCPLINK	MML name of TCP link (restricted)	MML name of a previously provisioned TCP link. This parameter is used only for D-channels associated with QSIG/Q.931 Over BRI Backhaul signaling services.
SIGSLOT	Physical slot on the media gateway on which the associated T1/E1 is terminated	•Cisco 2600, 3600, and 3700 series media gateways—Integer 0 through 63; (0). •All other media gateways—Integer 0 through 15; (0). Note This parameter must be set to 0 for IQSIG/Q.931 Over BRI Backhaul D-channels when the associated external node is a Cisco 17xx.
SIGPORT	Physical port of the associated slot on the media gateway	Integer 0 through 167; (0). Note This parameter can be set to either 0 or 1 for QSIG/Q.931 Over BRI Backhaul D-channels.
SUBUNIT	Physical subunit on the media gateway	Integer 0 through 3; (0).

The following rules apply when you are creating or editing D-channels:

•Backup D-channels for QSIG/Q.931 Over BRI Backhaul signaling services are not supported.

•The priority for QSIG/Q.931 Over BRI Backhaul D-channels should be set to 1.

•Session sets are used only in support of IPFAS D-channels.

•TCP links are used only in support of QSIG/Q.931 Over BRI Backhaul D-channels.

•Up to 1000 D-channels can be provisioned against a single IP address and port combination used by your Backhaul TCP links. Since the Cisco MGC supports a maximum of two IP address and port combinations, you can provision a maximum of 1000 D-channels for a QSIG/Q.931 Over BRI Backhaul signaling service.

DPNSS Signaling Service

The DPNSS signaling service component represents a DPNSS path backhauled over IP to a media gateway. Its MML name is as follows:

• MML Name—DPNSSPATH

The DPNSS signaling service component structure is shown in Table 2.

Table 2 DPNSSPATH Component Structure 

Parameter MML Name	Parameter Description	Parameter Value (Default)
NAME	Unique component name used in MML commands	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to 128 characters.
EXTNODE	MML name of external node	MML name of a previously provisioned QSIG/Q.931 BRI voice gateway external node.
MDO	MDO file name	A valid protocol name. You can use the following file name: DPNSS_BTNR188.
CUSTGRPID	VNET ID	Four digit ID; (0000).
SIGSLOT	Physical slot on the media gateway on which the associated T1/E1 is terminated	•Cisco 2600, 3600, and 3700 series media gateways—Integer 0 through 63; (0). •All other media gateways—Integer 0 through 15; (0).
SIGPORT	Physical port of the associated slot on the media gateway	Integer 0 through 167; (0).
SUBUNIT	Physical subunit on the media gateway	Integer 0 through 3; (0).

The following attributes cannot be modified:

•NAME

•EXTNODE

The following rules apply when creating/editing DPNSS signaling paths:

•The maximum number of combined DPNSSPATHs and NASPATHs per IUA External Node is IUA.maxSigPathsPerExtNode = 112 from XECfgParm.dat. Since DPNSSPATHs and NASPATHs can share the same association, the existing IUA.maxNasPathsPerExtNode will be renamed to IUA.maxSigPathsPerExtNode in order to support both.

•The maximum number of combined DPNSSPATHs and IUA NASPATHs is IUA.maxSigPaths = 1500 from XECfgParm.dat. The existing IUA.maxNasPaths will be renamed to IUA.maxSigPaths in order to support both with the same validation limit.

•Check the maximum number of external nodes with IUA type using the parameter IUA.maxExtNodes = 256. This parameter will be shared by both naspath and dpnsspath. The existing parameter IUA.maxNasExtNodes will be renamed to IUA.maxExtNodes.

•An ASSOCIATION must be define with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn't been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still hasn't been defined when provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped.

•If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message will be issued to inform the user that the DPNSSPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped.

External Node

The external node component represents another node with which the MGC communicates. Its MML name is as follows:

•MML Name—EXTNODE

The external node component structure is shown in Table 3.

Table 3 EXTNODE Component Structure 

Parameter MML Name	Parameter Description	Parameter Value (Default)
NAME	Unique component name used in MML commands	The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
DESC	Component description	The description can be up to 128 characters.
TYPE	The type of the external node	Valid values can be found in the "External Node Types" section.
ISDNSIGTYPE	ISDN signaling type	Valid values are IUA or N/A (default is N/A). This parameter is added in software Release 9.4(1).
GROUP	M3UA/SUA group number	Value is 1-100 for M3UA or SUA nodes. Value is 0 for nodes that do not support M3UA or SUA. This parameter is added in software Release 9.4(1).

The description parameter (DESC) is the only parameter for this command that can be modified, except in case of the Support of Enhanced Interface Numbering feature. In this case, you can change the type from the current setting to the same value with the "_OLD" string added to the name.

The following rules apply when you are creating or editing external nodes:

•TYPE must be one of the valid external node types.

•The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.

External Node Types

Table 4 lists the external node types, the software release in which they were introduced, and the signaling service types they support.

Table 4 External Node Types 

External Node MML Name	Valid Release	Supported Signaling Service Type
AS3600	Release 9.1(5) and up	MGCP IPFAS NAS IUA
AS3660	Release 9.1(5) and up	MGCP IPFAS NAS IUA
AS5200	Release 9.1(5) and up	IPFAS NAS
AS5300	Release 9.1(5) and up	MGCP IPFAS NAS IUA
AS5350	Release 9.2(2) and up	MGCP IPFAS NAS BSMV0 IUA
AS5400	Release 9.2(2) and up	MGCP IPFAS NAS BSMV0 IUA
AS5800	Release 9.1(5) and up	IPFAS NAS
AS5850	Release 9.1(5) and up	IPFAS NAS
AS7200	Release 9.1(5) and up	MGCP IPFAS NAS
CAT8510	Release 9.1(5) and up	MGCP
CAT8540	Release 9.1(5) and up	MGCP
C1751	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C1751_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C1760	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C1760_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2600	Release 9.4(1) and up	MGCP IPFAS IUA BRI
C2600_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2610XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2610XM_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2611XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2611XMOLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2620XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2620XM_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2621XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2621XM_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2650XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2650XM_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2651XM	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2651XM_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2691	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2691_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2801	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2811	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2821	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C2851	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3640	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3640A	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3660	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3725	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3725_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3745	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3745_OLD	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3825	Release 9.5(2) and up	MGCP IPFAS IUA BRI
C3845	Release 9.5(2) and up	MGCP IPFAS IUA BRI
H323	Release 9.1(5) and up	EISUP
ITP	Release 9.4(1) and up	M3UA SUA
LS1010	Release 9.1(5) and up	MGCP
MC3810	Release 9.1(5) and up	MGCP IPFAS
MGC	Release 9.1(5) and up	EISUP
MGX8260	Release 9.1(5) and up	MGCP IPFAS NAS
MGX8850	Release 9.1(5) and up	MGCP SGCP IPFAS
SLT	Release 9.2(2) and up	BSMV0
TALISS7	Release 9.1(5) and up	SS7SG
UNKNOWN	Release 9.1(5) and up	UNKNOWN

Provisioning Worksheets

This section contains worksheets for the provisioning components required for 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 0-5 DPNSS Signaling Service Worksheet Example 

Name	External Node	Customer Group ID	Slot	Port	Subunit	Description
dpnsssvc1	dpnss-01	V123	1	1	1	DPNSS path to 2600

Table 0-6 D-Channel Worksheet Example 

Name	Signaling Type	Priority	Link	Slot	Port	Subunit	Description
brichan1	bri	1	britcp1	0	4	1	bri d-channel 1

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

Table 7 Acronyms  

Acronym	Definition
BRI	Basic Rate Interface. ISDN interface composed of two B-channels and one D-channel for circuit-switched communication of voice, video, and data.
IOCC	I/O Channel Controller.
IOCM	I/O Channel Manager.
IP	Internet Protocol.
ISDN	Integrated Services Digital Network. Communication protocol offered by telephone companies that permits telephone networks to carry data, voice, and other source traffic.
MGC	(Cisco) Media Gateway Controller.
MGCP	Media Gateway Control Protocol.
PRI	Primary Rate Interface. ISDN interface to primary rate access. Primary rate access consists of a single 64-kbps D-channel plus 23 (T1) or 30 (E1) B-channels for voice or data.
Q.931	ISDN Level 3 ITU standard.
RSIP	Restart in progress. MGCP command used to indicate that a span (or collection of spans) has come into service, has gone out of service, or is about to go out of service.
TCP	Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack.