Table Of Contents
Support for MGX 8880 with VXSM Trunking Gateway
Supported Standards, MIBs, and RFCs
Prerequisites for Using This Feature
Adding Cisco Media Gateway External Nodes
Entering an Invalid Sigslot Value
Entering an Invalid Sigport Value
Entering an Invalid Priority Value
Deleting an Invalid D-channel Value
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Support for MGX 8880 with VXSM Trunking Gateway
Document Release History
Feature History
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:
•
Supported Standards, MIBs, and RFCs
•
•
•
•
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
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:
•
•
•
–
–
•
•
–
–
–
–
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:
•
•
•
•
•
•
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).
Provisioning Tasks
The following sections describe the MGC provisioning related to this feature:
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:
•
•
•
•
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
Use these procedures to start a provisioning session and to save and activate the changes you have made:
•
•
•
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver="curr_ver",dstver="mod_ver"Where:
•
–
–
Note
•
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
The prov-cpy MML command is used to save and activate your changes on simplex Cisco MGC (single host) systems.
Note
Caution
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
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
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_nameWhere:
•
•
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you enter the following command:
prov-rtrv:ss7path:name="ss7svc1"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:allRetrieving 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:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Adding Components
This section and the following subsections identify the steps you take to provision this feature as part of initial provisioning.
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
To add Cisco media gateway external nodes to your provisioning data, perform the following steps:
Step 1
Step 2
mml> prov-add:extnode:name="name",desc="description",type="as",isdnsigtype="n/a"Where:
•
•
•
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=0Step 3
Step 4
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
Step 2
mml> prov-ed:extnode:name="name",desc="description"Where:
•
•
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
Step 4
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
Step 2
Step 3
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
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________________________________________________________________________________; 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/DS1- 0/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.
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:
•
The D-channel component structure is shown in Table 1.
The following rules apply when you are creating or editing D-channels:
•
•
•
•
•
•
External Node
The external node component represents another node with which the MGC communicates. Its MML name is as follows:
•
The parameters for EXTNODE are defined in Table 2.
Table 2 External Node Component Structure
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.
TYPE
The type of the external node
Valid values can be found in the "External Node Types" section. 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).
Note
The following rules apply when you are creating or editing external nodes:
•
•
•
•
External Node Types
Table 3 lists the external node MML name type and the signaling service types the node supports.
Reference Information
The following sections contain reference material related to this feature. Information is included on the following areas:
Endpoint Naming
Support for the VXSM endpoint naming convention is as follows:
•
•
•
•
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=1MGC-02 - Media Gateway Controller 2005-02-28 22:58:23.113 ESTM DENYSROF"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=167MGC-02 - Media Gateway Controller 2005-02-28 23:50:03.021 ESTM DENYSROF"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=0MGC-02 - Media Gateway Controller 2005-02-28 22:59:54.422 ESTM DENYSROF"DCHAN:VXSM-D:SIGPORT should be 1-336"/* Status, Requested Operation Failed on the component */;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=337MGC-02 - Media Gateway Controller 2005-02-28 23:01:25.412 ESTM DENYSROF"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=168MGC-02 - Media Gateway Controller 2005-02-28 23:49:41.866 ESTM DENYSROF"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=336MGC-02 - Media Gateway Controller 2005-02-28 23:04:03.766 ESTM DENYSROF"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 ESTM DENYSROF"DCHAN:MGX8850-D:The D Channel :mgx8850-d: does not exists."/* Status, Requested Operation Failed on the component */;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
va-8850-37
MGX8850
IPFAS
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:
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 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:
•
http://www.cisco.com/en/US/partner/ordering/
•
Documentation Feedback
You can send comments about technical 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-9883We 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:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
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:
•
•
Tip
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:
•
•
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
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-2447For 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.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 5 contains definitions of acronyms and technical terms used in this feature module.
