Table Of Contents
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3
These release notes are part number OL-10285-01 Rev. A0, May 5, 2006.
The Voice Switch Service Module (VXSM) product is supported by the MGX 8880 Media Gateway and the MGX 8850 Multiservice Switch. Refer to their respective release notes for platform and version level support guidelines.
The VXSM software release notes are supported by the Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.3 and the Cisco Voice Switch Services (VXSM) Command Reference, Release 5.3, both of which are available on cisco.com.
Table of Contents
About Release 5.3.00
The VXSM Release 5.3.00 follows VXSM Release 22.214.171.124
New Features in Release 5.3.00
Release 5.3.00 is a significant release with several major new software features over Release 126.96.36.199. This release has no new VXSM hardware features. These new software features are:
Voice Quality Monitoring
The VXSM Voice Quality Monitoring (VQM) feature provides the ability to monitor, collect, and report a set of voice quality metrics to the remote Media Gateway. Together, the values of the collected metrics represent a measure of the quality of voice calls transmitted across the network. Service providers can use these metrics to observe and diagnose quality problems and to provide a measure for Service Level Agreements between the provider and its customers.
For H.248 switched applications, a VXSM card has the capability of being partitioned into a number of Virtual Media Gateways (VMGs) where each VMG is a logical entity residing within a physical VXSM card. This feature can be used in applications in which a single Media Gateway Controller (MGC) does not have the capacity to control one VXSM gateway. By partitioning the VXSM card into several VMGs, the control of VXSM's physical and ephemeral terminations can be distributed among several Media Gateway Controllers.
SS7 - Signaling Gateway
A VXSM Release 5.3 card in an MGX 8880 and functioning as a media gateway can also be configured to provide the functions of a signaling gateway between SS7 and IP networks. By this means, communication can be established between entities, such as Signaling End Points, on a SS7 network and Application Servers, such as a Media Gateway Controller, on an IP network.
VXSM supports one instance of a Signaling Gateway that can operate concurrently with one or several instances of Media Gateways.
Additional Backhauling Protocols
For applications in which the signaling lines or channels are connected directly to VXSM, VXSM can be configured to relay the signaling messages to the Media Gateway Controller (MGC) for call control processing. This relay function, known as Backhauling, consists of extracting the level 3 signaling message from the level 2 transport protocol, encapsulating it into the IP protocol stack, and relaying it onto the MGC.
In order to meet the requirements of various Service Provider networks, VXSM Release 5.3 now supports a number of additional TDM side and IP side protocol stacks for this purpose. VXSM supported backhaul protocols are shown in the following table.
TDM Network Side IP Network Side
ISDN D-channel (Q.931, Q.921)
ISDN D-channel (Q.931, Q.921)
SCTP = Streaming Control Transmission Protocol
RUDP = Reliable UDP
IUA = ISDN Q921-User Adaptation
AXSM Configurable Alarm Integration Parameter
For VXSM applications in which the interface to the packet network is an AXSM card (for example, AAL2 Trunking), the configure line (cnfln) command on the AXSM card now has a parameter to configure the Alarm Integration Time.
This parameter, intgTime, is basically a Loss of Signal alarm integration timer. The timer has a range from 100 ms to 2500 ms in increments of 100 ms. Under a line alarm condition, the Loss of Signal is checked for duration against the value of the intgTime parameter. If Loss of Signal exists for the intgTime value or more, the line is declared as Los of signal. The port will go down and hence e-ais is generated. The default value for intgTime is 2500 milliseconds (2.5 sec).
The syntax for the AXSM cnfln command is now:
For a SONET line:
cnfln -sonet <bay.line> -slt <LineType> -clk <clockSource> -intgTime <alarm integration time>
For a T3 line:
cnfln -ds3 <bay.line> -len <LineLength> -clk <clockSource> -lt <LineType> -oof <OOFCriteria>
-cb <AIScBitsCheck> -rfeac <RcvFEACValidation> -intgTime <alarm integration time>
For an E3 line:
cnfln -ds3 <bay.line> -len <LineLength> -clk <clockSource> -txtrace <TraceString>
-intgTime <alarm integration time>
In each case, the intgTime parameter is an integer in the range of 100 to 2500 ms, in increments of 100.
The configured value can be displayed using the dspln command, for example:Unknown.1.AXSM.a > dspln -sonet 1.1Line Number : 1.1Admin Status : Up Alarm Status : ClearLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable Number of ports : 0Xmt Clock source : localTiming Number of partitions: 0Line Type : sonetStm1 Number of SPVC : 0Medium Type(SONET/SDH) : SDH Number of SPVP : 0Medium Time Elapsed : 81902 Number of SVC : 0Medium Valid Intervals : 91 AlarmIntgTime (msec): 1000Medium Line Type : MMF
The intgTime value is stored in the RAM and DB. Hence on reset of the AXSM card the configured value will be retained. Also, modified value will be updated on to the standby card. Hence on switchredcd the new active AXSM card will have modified value.
Extended Bearer Trace Capability
The number of bearer trace probes has been increased (see following table)
H.248 Congestion and Overload
VXSM supports the H.248.10 Congestion Control Package, and the H.248.11, Overload Control Package.
The H.248.10 MG Congestion Control Package is used to exchange congestion information between the MG and the MGC. VXSM reports congestion events to the MGC if congestion control has been enabled and MG detects a congestion event.
The H.248.11 MG Overload Control feature protects VXSM from processing overload that prevents the timely execution of H.248.1 transactions. MG Overload happens when the utilization of resources crosses a threshold and MG is close to being unable to respond to MGC transactions in a sufficiently timely manner to avoid the calling customer abandoning the call in setup.
T.38 Fax with H.248
VXSM 5.3 supports Call Agent (CA) controlled T.38 Fax Relay with H248 call signaling protocol. This is in addition to the previously supported Gateway controlled T.38 Fax Relay feature. CA controlled T.38 relay is based on packages defined in H.248.2
Support for new H.248 packages
The following new H.248 packages are now supported:
GRI, DS, BCG, Detailed Termination Information, H.248.30, H.248.2 and H.248.11
VXSM now supports codec negotiation in H.248. Codec Negotiation allows two GWs to agree on a single codec to use for the new call that is being setup. The codec selected depends on the capabilities of each of the gateways and the order of priority of each codec on that specific GW, as well as the resources available on the GW when the call is being setup.
New Codecs Support
VXSM now supports the G.723.1, dual rate speech codec standard from ITU-T for compresssing toll quality speech. VXSM supports G.723 H, G.723 AH, G.723 L and G.723 AL which specify different rate of the codec with or without silence suppression. G.723.1 is supported for both H.248 and MGCP protocols but not in AAL2 trunking. VXSM support a maximum of 3024 G.723.1 calls on an OC3 card, and 1152 such calls on a 48E1/T1 card due to the complexity of this codec requiring increased DSP resources.
Enhancements to VBD support in H.248
VXSM now supports low speed modems (V.21, V.23,Bell MOdem, Bell 202 and V.8Bis) and TTY in H.248 mode. VXSM also supports V.32Ext Modems. VXSM has added support detecting tones on the IP side for 2100 Hz, 2100 PR and Bell Modem tones.
Extended Statistics Commands
VXSM 5.3 has a number of new statistics commands for the displaying and clearing of several statistics counters. These new statistics provide information on number of connected media streams per codec, number of H.248 messages, bearer PVC utilization, call durations and number of calls, response time per each command category, and number of fax modem calls on the system.
For each VXSM card type (OC-3, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. At order time, the user must specify whether a Non-CALEA or CALEA image is required.
The Non-CALEA image supports three Media Gateway Call Control (MGC) protocols, namely, H.248, MGCP, and TGCP. However, the image supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP versions when the image is first loaded from the PXM using the setrev command.
The CALEA image supports TGCP and MGCP only. The protocol must be explicitly selected when the image is loaded from the PXM using the setrev command.
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from any VXSM Release 5.2.x.x so long as the original and the upgraded images are of the same version (for example Non-CALEA, TGCP to Non-CALEA, TGCP). When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution.
Warning Many of the commands involved in loading or upgrading boot and runtime images can take several minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a loading or upgrading process, the card can easily be damaged even to the extent that it must be returned to the factory for repair.
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade
THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.
After the execution of the burnboot, clrsmcnf, loadrev, or setrev commands, the user must execute either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded or upgraded is either Active, Standby, or Failed.
ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT STEP.
If the upgrade procedure is interrupted for reasons outside the control of the user (for example, a power outage), see "Interrupted Procedure Recovery" below for instructions.
Interrupted Procedure Recovery
In the event that a VXSM software upgrade procedure is interrupted (for example, power outage), and both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure
Step 1 Execute the abortrev command:
abortrev <PrimarySlot> <NewImageRevision>
Step 2 If the primary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command
resetcd <PrimarySlot> (
Step 3 If the secondary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command:
Step 4 Both primary and secondary VXSM cards should now have their original SW image and original DB
Call Rate Performance Support
VXSM OC3 card supports the following call rates:
•In MGCP, the maximum CPS supported is 60 (without signaling). If signaling (M3UA/IUA/RUDP) is configured, then the maximum supported CPS is 35.
•In H.248, the maximum CPS supported is 65 (without signaling). If signaling (M3UA/IUA) is configured, then the maximum supported CPS is 35.
MIB for RTCPXR statistics collection
The current design of VXSM Release 5.3 cRtcpXrProfileTable in the CISCO-RTCPXR-EXT-MIB contains both VBD and CODEC threshold settings for RTCPXR statistics collection. To accommodate new CODEC support in future releases, this design will be changed to separate CODEC threshold settings into a new MIB table in the next VXSM release.
For this reason, the CISCO-RTCPXR-EXT-MIB file is not being posted to CCO for Release 5.3. The traps related to the objects defined in CISCO-RTCPXR-EXT-MIB are in the Release 5.3 and these traps will be supported without any change in the next VXSM release.
If any Network Management System would like to implement the trap manager receiving these traps in Release 5.3, the MIB can be provided by the VXSM team upon request.
Online Diagnostic feature as applied to VXSM.
The online diagnostics feature as implemented on the PXM45 card is supported on VXSM. When enabled, using the PXM45 cnfdiag command, this feature performs non-intrusive diagnostic tests that use four of the VXSM's DSP codecs.
If the user executes the VXSM dspdspcodecpools command, the resulting display shows the four codecs being used (for diagnostics) and subtracts them from the remaining available codecs (see example below).ns1_knodar.3.VXSM.a > dspdspcodecpools=====================================================================DSP codec capacity usage=====================================================================Codec pool Current utilized Current availablecapacity (#DSP chans) capacity (#DSP chans)========== ===================== =====================G711 family/HDLC 179 7885G729/G726/T.38 family 0 3919G723 family 0 2911
The online diagnostics feature does not reduce the maximum number of 8064 codecs available for calls on the VXSM card. If the number of call requests on the VXSM is sufficiently high, the online diagnostic feature is disabled automatically and the four codecs are made available for active calls.
DSP Resources under Mixed Codec Conditions
When the same codec is used to setup calls on the gateway the available DSP resources will be fully utilized. However when different codecs are used to setup calls the amount of utilizable DSP resources may be limited in certain cases due to fragmentation.
Fragmentation is said to have occurred when the available capacities on two different DSP resources have enough available capacity to support a call of a particular codec type but cannot support that codec type individually.
Consider two DSP resources whose available capacity is 1 unit each making the total available capacity 2 units. However a codec that requires 2 units cannot be supported in the system because the available capacities have been fragmented across the individual DSP resources.
The DSP allocation algorithm on VXSM does make an attempt to smooth the effects of fragmentation but towards the end, fragmentation could happen as the future pattern of calls cannot be predicted beforehand.
Configuring Switching and Trunking Applications
The simultaneous operation of mixed applications (Switched VoIP applications and Non-switched Trunking applications) is now supported on the same VXSM card.
VXSM Management Information Base
The VXSM Management Information Base (MIB) Version 5.3 is available by request through your Cisco VXSM product marketing representative.
Alternatively, users with CCO accounts can access the MIB and VXSM software on-line at:
The procedure is:
Step 1 Log on to http://www.cisco.com/public/sw-center/sw-wan.shtml
Step 2 Locate the VXSM platform (either VXSM 8880 or VXSM 8850) and click the down arrow to expand the "Select Release Level" drop down menu.
Step 3 Select the desired MIB release level (for example, Release 5300) to display a list of downloadable files.
Step 4 Click on the desired file (for example, mgx8850-fw-5300.tar).
Step 5 Read the license agreement and, if approved, click Accept.
Step 6 In the Software Download dialog box, click on Download: filename (where filename is the name of the file selected for download). This step starts the download procedure.
Step 7 Follow the normal file download procedure for your computer.
Step 8 When the file has been downloaded, untar or unzip the downloaded file. The MIB file is included in the downloaded file and is listed as a tar file (for example mgx8850rel5300mib.tar).
Step 9 Untar the MIB file to display its contents.
Service Module Support By Platform
Note VXSM Release 5.3.00 is supported only with PXM-45.
VXSM software interoperability with the MGX 8880 Media Gateway or the Cisco MGX 8850 (PXM45) Multiservice Switch platform software is listed in Table 1.
Table 2 describes the software images available for Release 5.3.00 for VXSM.
Caveats for VXSM Release 5.3.00
This section describes software caveats for Release 5.3.00
Open Caveats in Release 5.3.00
Table 3 describes the open caveats in VXSM Release 5.3.00
Resolved Caveats in Release 5.3.00
Table 4 describes the caveats that were open in Release 188.8.131.52 but are now resolved in VXSM Release 5.3.00
Removed Caveats in Release 5.3.00
Table 5 lists caveats that were listed as open in Release 184.108.40.206 but have been removed because they are unreproducible or otherwise invalid.
The MGX-VXSM-155 card is also known as the MGX-VXSM-4OC card.
The MGX-VXSM-T1/E1 card is also known as the MGX-VXSM-48T1/E1 card.
The MGX-VXSM-T3 card is also known as the MGX-VXSM-6T3 card.
The following documents contains information that may be useful to software Release 5.3 for VXSM:
•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide, Releases 2 Through 5.3
•Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2
•Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4
•Cisco MGX 8880 Media Gateway, Release 5.3: A Guide to User Documentation.
•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.3
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.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
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:
You can find instructions for ordering documentation at this URL:
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
•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).
You can send comments about technical documentation to firstname.lastname@example.org.
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:
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:
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:
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:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — email@example.com
•Nonemergencies — firstname.lastname@example.org
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:
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:
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:
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 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:
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:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•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:
•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:
•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:
•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:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, 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, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, 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. (0601R)
Copyright © 2006, Cisco Systems, Inc.
All rights reserved.