Support for MGX 8880 with VXSM Trunking
Gateway
Document Release History
Publication Date
Comments
July 12, 2005
Initial documentation release.
Feature History
Release
Modification
9.5(2)
This feature was introduced on the Cisco MGC Software Release 9.5(2).
This document describes new properties and naming conventions for provisioning the Voice Switch
Service Module (VXSM) on the Cisco PGW 2200 Softswitch, also known as the Cisco Media Gateway
Controller (MGC).
This feature is described in the following sections:
•
Feature Overview, page 2
•
Supported Platforms, page 3
•
Supported Standards, MIBs, and RFCs, page 3
•
Prerequisites for Using This Feature, page 3
•
Provisioning Tasks, page 4
•
Provisioning Example, page 9
•
Command Reference, page 10
•
Reference Information, page 14
•
Obtaining Documentation, page 17
•
Documentation Feedback, page 18
•
Cisco Product Security Overview, page 18
•
Obtaining Technical Assistance, page 19
•
Obtaining Additional Publications and Information, page 21
•
Glossary, page 21
Cisco MGC Software Release 9.5(2)
1
Support for MGX 8880 with VXSM Trunking Gateway
Feature Overview
Feature Overview
This feature provides support on the Cisco MGC to extend provisioning and range modification for the
MGX8000 chassis, including the Voice Interworking Service Module (VISM) and the Voice Switch
Service Module (VXSM).
This feature provides the following support:
Note
•
External node type VISM
•
External node type VXSM
•
VXSM endpoint name convention: DS/S-0/DS1-#/#@gateway, DS/S-0/DS1-#/*@gateway and
*@gateway
•
Hairpin call handing for VISM and VXSM
The use of external node type MGX is still available for VISM, but is not preferred.
Benefits
This feature provides the following benefits:
Support External Node Type VISM
Add a new external node type of VISM. For new deployments, VISM can be selected as the external
node.
Support External Node Type VXSM
Add a new external node type of VXSM. For new deployments, VXSM can be selected as the external
node.
Restrictions
This feature is for use with the following Cisco media gateways:
•
MGX 8850 Media Gateway
•
MGX 8880 Media Gateway
•
After switchover of the VXSM from active to standby, active, stable voice calls are maintained. For
data calls (for example, fax and modem calls), only the bearer path for the call is maintained upon
a switchover.
– Bearer path after switchover will revert to a voice call; it is up to the end data devices to
resynchronize/reattempt their data transmission to maintain the data flow.
– Transient data calls (i.e. voice calls in the process of being converted to a data call) will not be
preserved on the newly active VXSM.
•
To avoid MGC overload conditions, set the VXSM configuration for the MGCP DLCX (Delete
Connection) value to not exceed 24 messages a second for each VXSM.
•
Dual Tone Multifrequency (DTMF) support
– In-band DTMF (G.711) - no issues
Cisco MGC Software Release 9.5(2)
2
Support for MGX 8880 with VXSM Trunking Gateway
Supported Platforms
– RFC 2833 - no issues
– SIP Subscribe/Notify - not supported after switchover
– H.245 alphanumeric method - not supported after switchover
Related Documents
This document contains information that is related strictly to this feature. The documents that contain
additional information related to the Cisco MGC are listed below:
•
Release Notes for Cisco Media Gateway Controller Software Release 9.5(2)
•
Cisco Media Gateway Controller Hardware Installation Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning 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 Operations, Maintenance, and
Troubleshooting Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Cisco Media
Gateway Controller Hardware Installation Guide. The supported software version is the Cisco MGC
software Release 9.5(2), and later.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway
Controller Software Release 9 Management Information Base Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites for Using This Feature
You must have Cisco MGC software Release 9.5(2) and you must have installed the latest 9.5(2) patch
set. Prerequisites for this release can be found in the Release Notes for Cisco Media Gateway Controller
Software Release 9.5(2).
Cisco MGC Software Release 9.5(2)
3
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Tasks
Provisioning Tasks
The following sections describe the MGC provisioning related to this feature:
•
Provisioning Prerequisites, page 4
•
Provisioning Procedures, page 4
•
Adding Components, page 7
Provisioning Prerequisites
This section lists the data that you must gather to provision this feature. For more information on
planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Collecting External Node Data
The external node component type refers to any node with which the MGC communicates. You must be
ready to enter the following data about the node:
•
Man-Machine Language (MML) name
•
Component description
•
External node type
•
ISDN signaling type
Provisioning Procedures
Provisioning of the external nodes to which the Cisco MGC is connected is described in the following
sections.
This provisioning is performed when an external node type of VISM or VXSM is added or modified
during a provisioning session. This section covers the following provisioning topics:
•
Provisioning Basics, page 4
•
Adding Cisco Media Gateway External Nodes, page 8
Provisioning Basics
Use these procedures to start a provisioning session and to save and activate the changes you have made:
•
Starting a Provisioning Session, page 5
•
Saving and Activating Your Provisioning Changes, page 5
•
Ending a Provisioning Session Without Activating Your Changes, page 6
•
Retrieving Provisioning Data, page 6
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Cisco MGC Software Release 9.5(2)
4
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Tasks
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
•
curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
– new—A new default session configuration; no existing source configuration is available.
– active—Selects the active configuration as the source for configuration changes.
Note
•
If you do not know the name of your current configuration session, you can use the procedure
described in the “Retrieving Data for the Current Provisioning Session” section on page 7.
mod_ver—A new configuration version name that contains your provisioning changes.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you
would enter the following command:
prov-sta::srcver=”ver1”,dstver=”ver2”
Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML
commands to add, modify, and delete components on your system. This document describes how to
provision this feature. For more information on provisioning other components on your Cisco MGC,
refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes,
as described in the “Saving and Activating Your Provisioning Changes” section on page 5 or ending your
provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating Your Changes” section on page 6.
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 you issue these
commands 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 on page 5.
Cisco MGC Software Release 9.5(2)
5
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Tasks
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 requires 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 creates
problems when a switchover operation occurs.
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs in a continuous-service system. This command should not be used on a Cisco MGC in a
simplex configuration.
Note
When you enter the prov-dply command, your provisioning session is also automatically ended, unless
an error occurs during execution. If you want to make additional provisioning changes, you must start a
new provisioning session, as described in the “Starting a Provisioning Session” section on page 5.
Ending a Provisioning Session Without Activating Your Changes
If you want to end a provisioning session without saving and activating the changes you have entered,
enter the prov-stp MML command. This command ends your current provisioning session and your
changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning
settings. The ways you can use this command to retrieve provisioning data are described in the following
sections:
•
Retrieving Data for an Individual Component, page 6
•
Retrieving Data for All Components, page 7
•
Retrieving Data for All Components of a Particular Type, page 7
•
Retrieving Data for the Current Provisioning Session, page 7
•
Adding Components, page 7
Retrieving Data for an Individual Component
You can retrieve provisioning data for an individual component on your system. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:name=MML_name
Where:
•
component—The MML component type associated with the desired component. You can find a
complete list of MML component types in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
•
MML_name—The MML name for the desired component. You can determine the MML names for
the various components using the prov-rtrv:all MML command.
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you enter the
following command:
prov-rtrv:ss7path:name="ss7svc1"
Cisco MGC Software Release 9.5(2)
6
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Tasks
The response to the command depends on the component type associated with the desired component.
For example, to view the properties for an SUA routing key called suakey1, you enter the following
command:
prov-rtrv:suakey:name="suakey1"
Retrieving Data for All Components
You can retrieve data for all of the components provisioned on your system. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:all
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data for all components of a particular type on your system. To do this,
log in to the active Cisco MGC, start an MML session, and enter the following command:
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 enter the following
command:
prov-rtrv:ss7path:"all"
Retrieving Data for the Current Provisioning Session
You can retrieve provisioning 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: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
*/
Adding Components
This section and the following subsections identify the steps you take to provision this feature as part of
initial provisioning.
Cisco MGC Software Release 9.5(2)
7
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Tasks
Adding Cisco Media Gateway External Nodes
This section contains the procedures that you must perform to add a VISM or VXSM as an external node
type to your Cisco MGC provisioning data. When provisioning the components that enable the
Cisco MGC to support VISM or VXSM external node types, perform the following procedure:
•
Adding Cisco Media Gateway External Nodes, page 8
Adding Cisco Media Gateway External Nodes
To add Cisco media gateway external nodes to your provisioning data, perform the following steps:
Step 1
Start a provisioning session, as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to add a Cisco media gateway external node:
mml> prov-add:extnode:name="name",desc="description",type=”as”,isdnsigtype=”n/a”
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—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
as—The MML name for the type of Cisco media gateway. Valid values can be found in the “External
Node Types” section on page 13.
For example, to add a Cisco media gateway external node named mgx8850-207-01, enter the following
command:
mml> prov-add:extnode:name="mgx8850-207-01",desc="External Node for VXSM on 8850-207 Slot
01",type="VXSM",isdnsigtype="n/a",group=0
Step 3
Repeat Step 2 for each Cisco media gateway external node you want to add to your provisioning data.
Step 4
If there are no other nodes that you want to add, end your provisioning session as described in the
“Saving and Activating Your Provisioning Changes” section on page 5.
Modifying Components
Use the following procedure for modifying the external nodes connected to your Cisco MGC:
Modifying Cisco Media Gateway External Nodes
Desc is the only parameter that can be modified for an existing Cisco media gateway external node. To
edit the description of a Cisco media gateway external node, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 5.
Step 2
Enter the following command to edit the description of a Cisco media gateway external node:
mml> prov-ed:extnode:name="name",desc="description"
Where:
•
name—MML name of the Cisco media gateway external node to be modified.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
Cisco MGC Software Release 9.5(2)
8
Support for MGX 8880 with VXSM Trunking Gateway
Provisioning Example
For example, to modify a Cisco media gateway external node named mgx8850-207-01, you enter the
following command:
mml> prov-ed:extnode:name="mgx8850-207-01",desc="External Node for VXSM on 8850-207 Slot
01"
Step 3
Repeat the above steps for each Cisco media gateway 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 on page 5.
Deleting Components
Use the following procedure for deleting the external node connections to your Cisco MGC 2200.
Deleting Cisco Media Gateway External Nodes
To delete Cisco media gateway external nodes from your provisioning data, perform the following steps:
Step 1
Set the interface on the external node that is associated with the Cisco MGC software to the
out-of-service (OOS) state. Refer to the documentation for your media gateway for more information on
taking interfaces OOS.
Step 2
If your system uses IP routes for this external node, delete the IP routes.
Step 3
Enter the following command to delete a Cisco media gateway external node:
mml> prov-dlt:extnode:name="name"
Where name is the MML name of the Cisco media gateway external node to be deleted.
For example, to delete a Cisco media gateway external node named mgx8850-207-01, you enter the
following command:
mml> prov-dlt:extnode:name="mgx8850-207-01"
Step 4
Repeat the above steps for each Cisco media gateway external node you want to delete from your
provisioning data.
Provisioning Example
This section provides a provisioning example for this feature. Not all of the provisioning commands are
included, only the commands specific to this feature are included in the provisioning example.
Additional provisioning examples for the Cisco MGC software can be found in the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
________________________________________
; External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:EXTNODE:NAME="mgx8850-207-01",DESC="External Node for VXSM on 8850-207 Slot
01",TYPE="VXSM",ISDNSIGTYPE="N/A",GROUP=0
________________________________________
Cisco MGC Software Release 9.5(2)
9
Support for MGX 8880 with VXSM Trunking Gateway
Command Reference
________________________________________
; MGCP Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:MGCPPATH:NAME="mgcp8850-207-01",DESC="MGCP service",EXTNODE="mgx8850-207-01"
________________________________________
; MGCP Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:IPLNK:NAME="mgcp-8850-207-01-lk1",DESC="MGCP link 1 to
mgcp8850-207-01",SVC="mgcp8850-207-01",IPADDR="IP_Addr2",PORT=2427,
PEERADDR="172.16.0.1",PEERPORT=2427,PRI=1,IPROUTE="vxsm-7200-2"
________________________________________
________________________________________
; Signaling Service Property
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:NAME="mgcp8850-207-01",mgcpDomainNameRemote="DS/S-0/DS1-0/1@mgx8850-20
7-1"
________________________________________
________________________________________
; Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:TRNKGRP:NAME="2110",CLLI="CLLIDPC1",SVC="ss7svc2",TYPE="TDM_ISUP",SELSEQ="ASC",QA
BLE="N"
________________________________________
________________________________________
; Trunk Group Property
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrpprop:name="2110",CustGrpId="DP1A"
________________________________________
________________________________________
; Switch Trunk
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:switchtrnk:name="20101",trnkgrpnum="2101",span="ffff",cic=1,endpoint="DS/S-0/DS10/1@mgx8850-207-1",spansize=31,cu="mgx8850-207-01"
prov-add:switchtrnk:name="20102",trnkgrpnum="2102",span="ffff",cic=32,endpoint="DS/S-0/DS1
-1/1@mgx8850-207-1",spansize=31,cu="mgx8850-207-01"
________________________________________
Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other
MML commands are documented in the Cisco Media Gateway Controller Software Release 9 MML
Command Reference Guide.
Modified Components
The following components are modified for this feature.
Cisco MGC Software Release 9.5(2)
10
Support for MGX 8880 with VXSM Trunking Gateway
Command Reference
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 IP Facility Associated Signaling (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 MML name of a previously provisioned TCP link.
(restricted)
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
Integer 0 through 63; (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.
Note
This parameter must be set to 0 when
VXSM is the external node TYPE
selection.
Cisco MGC Software Release 9.5(2)
11
Support for MGX 8880 with VXSM Trunking Gateway
Command Reference
Table 1
DCHAN Component Structure (continued)
Parameter MML
Name
SIGPORT
SUBUNIT
Parameter Description
Parameter Value (Default)
Physical port of the
associated slot on the
media gateway
Integer: 0 through 336 (0). Must be 0–167 for
non-VXSM external node types, or 1–336 for
VXSM external node type.
Required for
QSIG/Q.931 over BRI
Backhaul D-channels
Note
This parameter can be set to either 0 or 1
for QSIG/Q.931 Over BRI Backhaul
D-channels.
Note
When VXSM is the selected external node
TYPE parameter, SIGSLOT must be set to
0, and the SIGPORT value is an integer of
1 through 336.
Integer 0 or 1; (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.
•
For an external node TYPE selection of VXSM, the SIGPORT range is 1–336 and SIGSLOT must
be set to 0.
External Node
The external node component represents another node with which the MGC communicates. Its MML
name is as follows:
•
MML Name—EXTNODE
The parameters for EXTNODE are defined in Table 2.
Table 2
External Node Component Structure
Parameter MML
Name
Parameter Description
Parameter Values (Default)
NAME
MML name
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.
Cisco MGC Software Release 9.5(2)
12
Support for MGX 8880 with VXSM Trunking Gateway
Command Reference
Table 2
Note
External Node Component Structure (continued)
TYPE
The type of the external
node
Valid values can be found in the “External Node
Types” section on page 13. The TYPE parameter
is case sensitive.
ISDNSIGTYPE
ISDN signaling type
Valid values are IUA or N/A (default is N/A). This
parameter was 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 was added in software
Release 9.4(1).
DESC is the only parameter for this command that can be modified:
The following rules apply when you are creating or editing external nodes:
•
TYPE must be one of the valid external node types.
•
The TYPE parameter is case sensitive.
•
The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.
•
The MGCP endpoint notation for the DS1 number range is 0–335.
External Node Types
Table 3 lists the external node MML name type and the signaling service types the node supports.
Table 3
ExtNode
MML Type
External Node Types for Cisco MGC Software Release 9.5(2)
SGCP
MGCP
AS5200
IPFAS
IUA
BRI
IPFAS
NAS
MGCP
ANNO
MGCP
IVR
SUA
Other
NAS
AS5300
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
AS5350
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
AS5400
SGCP
MGCP
IPFAS
IUA
NAS
MGCP
ANNO
MGCP
IVR
BSMV0
NAS
MGCP
ANNO
NAS
MGCP
ANNO
AS5800
IPFAS
AS5850
MGCP
IPFAS
MGCP
IPFAS
C1751
MGCP
IPFAS
IUA
BRI
C1760
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
AS7200
C2600
C2610XM
SGCP
SGCP
IUA
MGCP
IVR
NAS
Cisco MGC Software Release 9.5(2)
13
Support for MGX 8880 with VXSM Trunking Gateway
Reference Information
Table 3
External Node Types for Cisco MGC Software Release 9.5(2) (continued)
ExtNode
MML Type
MGCP
IPFAS
IUA
BRI
C2611XM
MGCP
IPFAS
IUA
BRI
C2620XM
MGCP
IPFAS
IUA
BRI
C2621XM
MGCP
IPFAS
IUA
BRI
C2650XM
MGCP
IPFAS
IUA
BRI
C2651XM
MGCP
IPFAS
IUA
BRI
C2691
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
C3640
MGCP
IPFAS
IUA
BRI
C3640A
MGCP
IPFAS
IUA
BRI
MGCP
IPFAS
IUA
BRI
C3725
MGCP
IPFAS
IUA
BRI
C3745
MGCP
IPFAS
IUA
BRI
C3600
C3660
SGCP
SGCP
SGCP
CAT8510
SGCP
MGCP
CAT8540
SGCP
MGCP
NAS
MGCP
ANNO
MGCP
IVR
SUA
NAS
H323
EISUP
ITP
SUA
LIMD
LS1010
M3UA
LI
SGCP
MC3810
MGCP
MGCP
IPFAS
MGC
EISUP
MGX8260
MGX8850
Other
MGCP
SGCP
IPFAS
NAS
MGCP
SCP
TCAPIP
SLT
BSMV0
TALISS7
SS7SG
UNKNOWN
UNKNOWN
VISM
SGCP
MGCP
IPFAS
VXSM
SGCP
MGCP
IPFAS
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
External Node Types, page 13
•
Error Messages, page 15
•
Provisioning Worksheets, page 17
Cisco MGC Software Release 9.5(2)
14
Support for MGX 8880 with VXSM Trunking Gateway
Reference Information
Endpoint Naming
Support for the VXSM endpoint naming convention is as follows:
•
DS/S-0/DS1-#/#@gateway,
•
DS/S-0/DS1-#/*@gateway, or
•
*@gateway.
•
For the MGCP endpoint notation, DS1 # range is from 0 to 335.
Error Messages
This section contains error messages that might occur while you are using the MML commands.
Entering an Invalid Sigslot Value
Entering an invalid sigslot value (1) when VXSM is the external node type.
va-saturn mml> prov-add:DCHAN:NAME="VXSM-D",DESC="Dchannel INET port 5 on
vxsm-TEST",SVC="VXSM-1",PRI=1,SESSIONSET="ses-vXSM",SIGSLOT=1,SIGPORT=1
MGC-02 - Media Gateway Controller 2005-02-28 22:58:23.113 EST
M DENY
SROF
"DCHAN:VXSM-D:Invalid sigslot value. Slot must be 0 for external node type: VXSM"
/* Status, Requested Operation Failed on the component */
;
va-saturn mml>
Entering an invalid sigslot value (64) when VISM is the external node type.
va-saturn mml> prov-add:DCHAN:NAME="VISM-D",DESC="Dchannel INET port 5 on
vism-TEST",SVC="VISM-1",PRI=1,SESSIONSET="ses-vISM",SIGSLOT=64,SIGPORT=167
MGC-02 - Media Gateway Controller 2005-02-28 23:50:03.021 EST
M DENY
SROF
"DCHAN:VISM-D:Invalid sigSlot value: 64"
/* Status, Requested Operation Failed on the component */
;
va-saturn mml>
Entering an Invalid Sigport Value
Entering an invalid sigport value (0) when VXSM is the external node type.
va-saturn mml> prov-add:DCHAN:NAME="VXSM-D",DESC="Dchannel INET port 5 on
vxsm-TEST",SVC="VXSM-1",PRI=1,SESSIONSET="ses-vXSM",SIGSLOT=0,SIGPORT=0
MGC-02 - Media Gateway Controller 2005-02-28 22:59:54.422 EST
M DENY
SROF
"DCHAN:VXSM-D:SIGPORT should be 1-336"
/* Status, Requested Operation Failed on the component */
;
Cisco MGC Software Release 9.5(2)
15
Support for MGX 8880 with VXSM Trunking Gateway
Reference Information
va-saturn mml>
Entering an invalid sigport value (337) when VXSM is the external node type.
va-saturn mml> prov-add:DCHAN:NAME="VXSM-D",DESC="Dchannel INET port 5 on
vxsm-TEST",SVC="VXSM-1",PRI=1,SESSIONSET="ses-vXSM",SIGSLOT=0,SIGPORT=337
MGC-02 - Media Gateway Controller 2005-02-28 23:01:25.412 EST
M DENY
SROF
"DCHAN:VXSM-D:SIGPORT should be 1-336"
/* Status, Requested Operation Failed on the component */
;
va-saturn mml>
Entering an invalid sigport value (168) when VISM is the external node type.
mml> prov-add:DCHAN:NAME="VISM-D",DESC="Dchannel INET port 5 on
vism-TEST",SVC="VISM-1",PRI=1,SESSIONSET="ses-vISM",SIGSLOT=63,SIGPORT=168
MGC-02 - Media Gateway Controller 2005-02-28 23:49:41.866 EST
M DENY
SROF
"DCHAN:VISM-D:SIGPORT should be 0-167"
/* Status, Requested Operation Failed on the component */
;
Entering an Invalid Priority Value
Entering a priority value of 1 when another priority value of 1 already exists.
va-saturn mml> prov-add:DCHAN:NAME="VXSM-D2",DESC="Dchannel INET port 5 on
vxsm-TEST",SVC="VXSM-1",PRI=1,SESSIONSET="ses-vXSM",SIGSLOT=0,SIGPORT=336
MGC-02 - Media Gateway Controller 2005-02-28 23:04:03.766 EST
M DENY
SROF
"DCHAN:VXSM-D2:There can only be one D Channel with a priority of 1 for SVC vxsm-1."
/* Status, Requested Operation Failed on the component */
;
Deleting an Invalid D-channel Value
Entering an invalid D-channel value to delete when VXSM is the external node type.
va-saturn mml> prov-dlt:DCHAN:NAME="MGX8850-D",DESC="Dchannel INET port 5 on
MGX8850-TEST",SVC="MGX8850-1",PRI=1,SESSIONSET="ses-MGX8850",SIGSLOT=0,SIGPORT=168
MGC-02 - Media Gateway Controller 2005-03-01 00:08:57.711 EST
M DENY
SROF
"DCHAN:MGX8850-D:The D Channel :mgx8850-d: does not exists."
/* Status, Requested Operation Failed on the component */
;
Cisco MGC Software Release 9.5(2)
16
Support for MGX 8880 with VXSM Trunking Gateway
Obtaining Documentation
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 4
External Node Worksheet Example
Name
Type
ISDN Signaling Type Group
va-8850-37
MGX8850 IPFAS
Description
BRI to va-8850-37
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/univercd/home/home.htm
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
Documentation DVD
Cisco documentation and additional literature are available in a Documentation DVD package, which
may have shipped with your product. The Documentation DVD is updated regularly and may be more
current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco 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 MGC Software Release 9.5(2)
17
Support for MGX 8880 with VXSM Trunking Gateway
Documentation Feedback
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
•
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 send comments about technical documentation to [email protected].
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
Cisco MGC Software Release 9.5(2)
18
Support for MGX 8880 with VXSM Trunking Gateway
Obtaining Technical Assistance
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:
Tip
•
Emergencies — [email protected]
•
Nonemergencies — [email protected]
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 that has the most recent creation date in this public key server list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an emergency, you can also reach PSIRT by telephone:
•
1 877 228-7302
•
1 408 525-6532
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco
Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical
Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical
Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service
contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support 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,
365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support 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
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
Cisco MGC Software Release 9.5(2)
19
Support for MGX 8880 with VXSM Trunking Gateway
Obtaining Technical Assistance
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 TAC 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 TAC 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.
Cisco MGC Software Release 9.5(2)
20
Support for MGX 8880 with VXSM Trunking Gateway
Obtaining Additional Publications and Information
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, 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
•
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
•
World-class networking training is available from Cisco. You can view current offerings at
this URL:
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 5 contains definitions of acronyms and technical terms used in this feature module.
Table 5
Acronyms and Definitions
Acronym
Definition
DLCX
Delete Connection
DTMF
Dual Tone Multifrequency
IPFAS
IP Facility Associated Signaling
MGC
Cisco Media Gateway Controller
MML
Man-Machine Language
Cisco MGC Software Release 9.5(2)
21
Support for MGX 8880 with VXSM Trunking Gateway
Glossary
Table 5
Acronyms and Definitions (continued)
Acronym
Definition
PGW
PSTN Gateway
SC
Signaling Controller
SIP
Session Initiation Protocol
VSC
Virtual Switch Controller
VISM
Voice Interworking Service Module
VXSM
Voice Switch Service Module
Cisco MGC Software Release 9.5(2)
22