 Feedback
|
Table Of Contents
Digit Buffering for International Gateways
Supported Standards, MIBs, and RFCs
Prerequisites for Using This Feature
Modifying a Signaling Service Property
Deleting a Signaling Service Property
Software Changes for This Feature Module
New, Modified, and Deleted Elements
Obtaining Documentation, Obtaining Support, and Security Guidelines
Digit Buffering for International Gateways
Document Release History
Feature History
9.7(3)
TheDigit Buffering for International Gateways feature was introduced on the Cisco MGC software.
This document describes the Digit Buffering for International Gateways feature.
This feature is described in the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
•
Feature Overview
This feature adds a sigPath property (TBufferDigitLength) that allows you to limit the digit length of the called party number (B-number) in the outgoing ISUP IAM and SAM(s). If the number of digits in the next SAM is also greater than the limit, the number of digits in the SAM is limited again, until all digits are passed in SAM(s). This is required for proper interconnection to certain international networks.
This feature provides the following:
•
•
The TBufferDigitLength property works with the following:
•
•
•
•
If TOverlap is set to 1, the maximum number of digits allowed in the outgoing IAM and SAM(s) is determined by the TBufferDigitLength setting and the TMaxDigits setting, whichever is lower. If TOverlap is set to 0, the maximum number of digits allowed in the outgoing IAM is determined by the TBufferDigitLength setting. The TMaxDigits setting determines the maximum number of digits allowed in the outgoing IAM and SAM(s). Additionally, if OD32DigitSupport is set to 1, the maximum terminating protocol digit support is 32 digits, instead of the protocol digit limit (for example, 16 digits for ITU). Table 1-1 provides an indication of how ingress digits in the ISUP IAM and SAM(s) are treated.
Table 1-1 Ingress Digit Scenarios for Egress ISUP IAM and SAM
1 IAM - 14 digits
1
32
0
0
14 digits +F
2 IAM - 30 digits
1
32
24
0
16 digits1
14 digits +F
3 IAM - 30 digits
1
32
24
1
24 digits
6 digits +F
4 IAM - 20 digits,
SAM - 4 digits1
32
18
1
18 digits
2 digits
4 digits +F
5 IAM - 14 digits
0
32
10
1
10 digits
4 digits2
6 IAM - 8 digits,
SAM - 32 digits1
32
32
1
8 digits
24 digits +F
8 digits3
1 Sixteen digits are the maximum number of digits allowed in an IAM by SS7 protocol ITU-T Q.763 (03/93). Other protocols may allow more than 16 digits to be in the IAM.
2 Four digits are deleted because TOverlap is disabled (set to 0) and the TBufferDigitLength is 10.
3 Eight digits are deleted because the TMaxDigits is set to 32.
The software changes in the PGW 2200 that support the Digit Buffering for International Gateways feature are listed in "Software Changes for This Feature Module."
Benefits
This feature provides the benefits described in the following paragraphs.
Limiting the Number of Digits in the IAM Called Party Number
This feature on the PGW 2200 enables you to limit the called party number in the ISUP IAM and SAM message to a provisioned value, followed by one or more SAM(s) with the remaining digits. This feature is provisionable on an outgoing sigPath basis.
When the number of digits in the ISUP IAM called party number is greater than the number of digits allowed for the outgoing trunk group, the additional digits are stripped and buffered into the SAM. If the number of the digits in the SAM is also greater than the number of digits allowed for the trunk group, the remaining called party number digits are removed, buffered, and inserted into the following SAM(s) until all of the called party number digits are passed in SAMs.
Allows Service Providers to Directly Connect to Certain International Networks
With the addition of support for limiting the number of digits in the outgoing IAM and SAM(s), service providers can now directly send calls from the Cisco PGW 2200 out on certain international trunks.
Restrictions
This feature is supported starting in Release 9.7(3) of the PGW 2200 software.
The value provisioned for the TBufferDigitLength property does not overwrite the built-in protocol digit length limit. When TBufferDigitLength is provisioned with a value greater than the protocol digit length value, the protocol limit takes effect.
Related Documents
This document contains information that is related to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are at the following url:
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html
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
The Cisco PGW 2200 must be running Cisco MGC software Release 9.7(3). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.7(3) at:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/relnote/rn973.htm.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
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 Provisioning Data
You must be ready to enter the following provisioning data for this feature:
•
•
•
You can define the parameters for this feature module in Table 1-3 in the "Properties" section.
Provisioning Procedures
This section covers the following provisioning topics:
•
•
•
Provisioning Basics
Use the procedures in this section to start a provisioning session, save, and activate the changes you have made.
•
•
•
For more detailed information about provisioning your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You might need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco PGW 2200, 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 PGW 2200, 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 PGW 2200 (single-host) systems.
Note
Caution
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco PGW 2200s in a continuous-service system. This command should not be used on a Cisco PGW 2200 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 on any individual component in your system. To do this, log in to the active Cisco PGW 2200, 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 would enter the following command:
prov-rtrv:ss7path:name="ss7svc1"The response to the command dependents on the type for the component associated with the desired component. For example, to view the properties for an SUA routing key called suakey1, you would enter the following command:
prov-rtrv:suakey:name="suakey1"Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active Cisco PGW 2200, 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 on all components of a particular type on your system. To do this, log in to the active Cisco PGW 2200, 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:sigsvcprop:name="ss7svc1"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 PGW 2200, 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 2004-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = 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:variantsModifying a Signaling Service Property
Perform the following steps to edit the TBufferDigitLength signaling service property:
Step 1
Step 2
mml> prov-ed:sigsvcprop:name="name",propertyname="value"Where:
•
•
For example, to modify the Cisco PGW 2200 signaling service property TBufferDigitLength to 16, you enter the following command:
mml> prov-ed:sigsvcprop:name="ss7svc1",tbufferdigitlength="16"Step 3
Deleting a Signaling Service Property
To delete a Cisco PGW 2200 signaling service property from your provisioning data, perform the following steps:
Step 1
Step 2
mml> prov-dlt:sigsvcprop:name="name",propertynameWhere:
•
•
For example, to delete the Cisco PGW 2200 signaling service property TBufferDigitLength, you enter the following command:
mml> prov-dlt:sigsvcprop:name="ss7svc1",tbufferdigitlengthStep 3
Provisioning Example
The following is 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.
________________________________________; IP Route;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:IPROUTE:NAME="iprte1",DEST="10.82.80.0",NETMASK="255.255.255.0", NEXTHOP="10.82.82.1",IPADDR="IP_Addr1",DESC="IP Route 1"prov-add:IPROUTE:NAME="iprte2",DEST="10.82.81.0",NETMASK="255.255.255.0", NEXTHOP="10.82.82.1",IPADDR="IP_Addr2",DESC="IP Route 2"________________________________________; SS7 External Node;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:extnode:NAME="va-2600-165",TYPE="SLT",DESC="2611 SLT RUDP E1"prov-add:extnode:NAME="va-2600-166",TYPE="SLT",DESC="2611 SLT RUDP E1"________________________________________; Point Codes;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:OPC:NAME="opc",DESC="Own pointcode",NETADDR="1.1.3",NETIND=2,TYPE="TRUEOPC"prov-add:DPC:NAME="dpc1",DESC="Destination pointcode1",NETADDR="1.1.1",NETIND=2prov-add:DPC:NAME="dpc2",DESC="Destination pointcode2",NETADDR="1.1.2",NETIND=2________________________________________; Signal Services to Inet via SLT;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 service to dpc1",MDO="Q761_BASE", CUSTGRPID="2222",SIDE="network",DPC="dpc1",OPC="opc"prov-ed:sigsvcprop:name="ss7svc1",tbufferdigitlength="10"________________________________________; SS7 linksets;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:LNKSET:NAME="ls1",DESC="linkset 1 to dpc1",APC="dpc1",PROTO="SS7-ITU",TYPE="IP"prov-add:LNKSET:NAME="ls2",DESC="linkset 2 to dpc2",APC="dpc2",PROTO="SS7-ITU",TYPE="IP"________________________________________; SS7 route;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:SS7ROUTE:NAME="rte1",DESC="SS7 Rte 1-dpc1",OPC="opc",DPC="dpc1", LNKSET="ls1",PRI=1prov-add:SS7ROUTE:NAME="rte2",DESC="SS7 Rte 2-dpc2",OPC="opc",DPC="dpc2", LNKSET="ls2",PRI=1________________________________________; Sessionset;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:sessionset:NAME="slt1",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",PORT=7000, PEERADDR1="10.82.80.188",PEERADDR2="10.82.81.165",PEERPORT=7000,extnode="va-2600-165", TYPE="BSMV0",IPROUTE1="iprte1", IPROUTE2="iprte2"prov-add:sessionset:NAME="slt2",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",PORT=7000, PEERADDR1="10.82.80.191",PEERADDR2="10.82.81.166",PEERPORT=7000,extnode="va-2600-166", TYPE="BSMV0",IPROUTE1="iprte1",IPROUTE2="iprte2"________________________________________; C7IPLinks;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:C7IPLNK:NAME="ls1lk1",DESC="SS7ANSI",LNKSET="ls1",sessionset="slt1",SLC=0, PRI=1,TIMESLOT=0prov-add:C7IPLNK:NAME="ls2lk1",DESC="SS7ANSI",LNKSET="ls2",sessionset="slt1",SLC=0, PRI=1,TIMESLOT=2prov-add:C7IPLNK:NAME="ls1lk2",DESC="SS7ANSI",LNKSET="ls1",sessionset="slt2",SLC=1, PRI=1,TIMESLOT=0prov-add:C7IPLNK:NAME="ls2lk2",DESC="SS7ANSI",LNKSET="ls2",sessionset="slt2",SLC=1, PRI=1,TIMESLOT=2;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; NAS External Node;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:EXTNODE:NAME="va-5400-36",TYPE="AS5400",DESC="RLM"prov-add:EXTNODE:NAME="va-5400-37",TYPE="AS5400",DESC="IUA NAS",ISDNSIGTYPE="IUA";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; NAS Path;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:NASPATH:NAME="nassvc1",EXTNODE="va-5400-36",prov-add:NASPATH:NAME="nassvc2",EXTNODE="va-5400-37",SIGPORT=0,SIGSLOT=0;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; NAS IP Links;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:IPLNK:NAME="nas1-lnk1",IF="hme0",IPADDR="IP_Addr1",PORT=3001, PEERADDR="10.82.80.29",PEERPORT=3001,PRI=1,IPROUTE="iprte1",SVC="nassvc1"prov-add:IPLNK:NAME="nas1-lnk2",IF="hme1",IPADDR="IP_Addr2", PORT=3001, PEERADDR="10.82.81.29",PEERPORT=3001, PRI=1,IPROUTE="iprte2",SVC="nassvc1";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Dial Plan;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:DIALPLAN:CUSTGRPID="2222",OVERDEC="NO"Software Changes for This Feature Module
Feature Summary
CSCsa60885 introduced the software changes in the PGW 2200 to support the Digit Buffering for International Gateways feature. The following is a summary of the software changes.
New, Modified, and Deleted Elements
Components
None.
Parameters
Added TBufferDigitLength sigPath property.
Measurements
None.
Alarms
None.
Logs
None.
CDBs
None.
The following sections contain reference material related to this feature. Information is included on the following areas:
Properties
The properties in this section are used for this feature. For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The parent objects for the property involved in this feature are found in Table 1-2.
The property used for this feature is described in Table 1-3 and its dynamically provisionable status is listed in Table 1-4.
Table 1-4 Provisionable Properties
TBufferDigitLength
Yes
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Glossary
Table 1-5 contains expansions of acronyms used in this feature module.
Table 1-5 Acronym Expansions
IAM
Initial Address Message
CDR
call detail record
MGC
Cisco Media Gateway Controller
PGW
PSTN Gateway
SAM
Subsequent Address Message
This document is to be used in conjunction with the documents listed in the Related Documents section.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
