Digit Buffering for International Gateways
Document Release History
Publication Date
Comments
March 12, 2007
Initial version of the document
Feature History
Release
Modification
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:
•
Feature Overview, page 1
•
Supported Standards, MIBs, and RFCs, page 3
•
Prerequisites for Using This Feature, page 3
•
Provisioning Tasks, page 4
•
Provisioning Example, page 8
•
Software Changes for This Feature Module, page 10
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page 11
•
Glossary, page 12
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 ability to limit the called party number in the ISUP IAM and SAM message
•
The option for direct connection between the PGW 2200 and certain international networks
The TBufferDigitLength property works with the following:
Cisco MGC Software Release 9.7(3)
1
Digit Buffering for International Gateways
Feature Overview
•
The built in digit length limit of the terminating protocol—The maximum number of digits allowed
in the outgoing IAM and SAM(s) is determined by the TBufferDigitLength and the build in protocol
limitation, whichever is less.
•
OD32DigitSupport (sigPath property) —Setting OD32DigitSupport to 1, sets the built-in digit
length limit to 32 digits.
•
TOverlap (sigPath property) —Setting TOverlap to 0, causes extra digits cut from the IAM to be
discarded. A SAM is not allowed on the terminating side.
•
TMaxDigits (sigPath property) —TMaxDigits ensures the total number of digit in the IAM and
SAM messages does not exceed the provisioned value.
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
Scenario
TOverlap
TMaxDigits
TBufferDigit OD32Digit
Length
Support
IAM
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 digits
1
32
18
1
18 digits
2 digits
4 digits +F
5 IAM – 14 digits
0
32
10
1
10 digits
6 IAM – 8 digits,
SAM – 32 digits
1
32
32
1
8 digits
SAM
Deleted
Digits
4 digits2
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.
Cisco MGC Software Release 9.7(3)
2
Digit Buffering for International Gateways
Supported Standards, MIBs, and RFCs
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.
Cisco MGC Software Release 9.7(3)
3
Digit Buffering for International Gateways
Provisioning Tasks
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Prerequisites, page 4
•
Provisioning Procedures, page 4
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:
•
MML name of the signaling service
•
Property name
•
Property value
You can define the parameters for this feature module in Table 1-3 in the “Properties” section on
page 11.
Provisioning Procedures
This section covers the following provisioning topics:
•
Provisioning Basics, page 11
•
Modifying a Signaling Service Property, page 7
•
Deleting a Signaling Service Property, page 8
Provisioning Basics
Use the procedures in this section to start a provisioning session, save, and activate the changes you have
made.
•
Starting a Provisioning Session, page 4
•
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 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:
Cisco MGC Software Release 9.7(3)
4
Digit Buffering for International Gateways
Provisioning Tasks
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 learn it by using the
procedure described in the “Retrieving Data on 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 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 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 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 PGW 2200
(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 4.
Cisco MGC Software Release 9.7(3)
5
Digit Buffering for International Gateways
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) system. Saving and activating using prov-cpy
on such a system requires that you use 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 could create 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 PGW 2200s in a continuous-service system. This command should not be used on a
Cisco PGW 2200 in a simplex configuration.
Note
When you enter the prov-dply command, your provisioning session is 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 4.
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 on the Current Provisioning Session, page 7
•
Retrieving Data on Supported Signaling Protocols, page 7
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_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 would enter
the following command:
prov-rtrv:ss7path:name="ss7svc1"
Cisco MGC Software Release 9.7(3)
6
Digit Buffering for International Gateways
Provisioning Tasks
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: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 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:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2004-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
Modifying a Signaling Service Property
Perform the following steps to edit the TBufferDigitLength signaling service property:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 4.
Cisco MGC Software Release 9.7(3)
7
Digit Buffering for International Gateways
Provisioning Example
Step 2
Enter the following command to edit the description of a Cisco PGW 2200 signaling service property:
mml> prov-ed:sigsvcprop:name="name",propertyname="value"
Where:
•
name—MML name of the previously defined signaling service to be modified.
•
value—An integer value of 0 or 1 through 32.
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
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 a Signaling Service Property
To delete a Cisco PGW 2200 signaling service property from your provisioning data, perform the
following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 4.
Step 2
Enter the following command to delete a Cisco PGW 2200 signaling service property:
mml> prov-dlt:sigsvcprop:name="name",propertyname
Where:
•
name—MML name of the previously defined signaling service to be modified.
•
propertyname—A valid signaling service property name.
For example, to delete the Cisco PGW 2200 signaling service property TBufferDigitLength, you enter
the following command:
mml> prov-dlt:sigsvcprop:name=“ss7svc1”,tbufferdigitlength
Step 3
Repeat the preceding steps for each signaling service property you want to delete from your provisioning
data.
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"
Cisco MGC Software Release 9.7(3)
8
Digit Buffering for International Gateways
Provisioning Example
________________________________________
; 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=2
prov-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=1
prov-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=0
prov-add:C7IPLNK:NAME="ls2lk1",DESC="SS7ANSI",LNKSET="ls2",SESSIONSET="slt1",SLC=0,
PRI=1,TIMESLOT=2
prov-add:C7IPLNK:NAME="ls1lk2",DESC="SS7ANSI",LNKSET="ls1",SESSIONSET="slt2",SLC=1,
PRI=1,TIMESLOT=0
prov-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"
Cisco MGC Software Release 9.7(3)
9
Digit Buffering for International Gateways
Software Changes for This Feature Module
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; 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:
Cisco MGC Software Release 9.7(3)
10
Digit Buffering for International Gateways
Obtaining Documentation, Obtaining Support, and Security Guidelines
•
Properties, page 11
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.
Table 1-2
Software Properties Related to this Feature
TBufferDigitLength
X
X
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SGCP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
Property Name
DPNSS
AVM
Parent Object
X
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-3
Properties
Property
Definition
TBufferDigitLength
Limits the maximum number of digits allowed in the outgoing
IAM and SAM. Valid Values: 0: Disable this functionality, or
1 through 32.
Valid Values: 0 through 32.
Default Value: 0
Table 1-4
Provisionable Properties
Property
Modified Value Takes Effect Without Restart
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
Cisco MGC Software Release 9.7(3)
11
Digit Buffering for International Gateways
Glossary
Glossary
Table 1-5 contains expansions of acronyms used in this feature module.
Table 1-5
Acronym Expansions
Acronym
Expansion
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.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a
service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS,
iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy,
Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a
partnership relationship between Cisco and any other company. (0705R)
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.
Cisco MGC Software Release 9.7(3)
12