Cisco MGX 8880 Media Gateways

Table Of Contents

Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.5.11

Contents

About This Release

New Features in Release 5.5.11

DSP RAS and Memory Error Detection Mechanism

NSE Negotiation Based VXSM Up-speed

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

VXSM Management Information Base

Service Module Support by Platform

Upgrade Compatibility Matrix

Caveats for VXSM Release 5.5.11

Open Caveats in Release 5.5.11

Resolved Caveats in Release 5.5.11.202

Resolved Caveats in Release 5.5.11.201

Resolved Caveats in Release 5.5.11.200

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.5.11

---

Revised: August 19, 2010, OL-19886-02

Contents

About This Release

New Features in Release 5.5.11

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

VXSM Management Information Base

Service Module Support by Platform

Upgrade Compatibility Matrix

Caveats for VXSM Release 5.5.11

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

About This Release

The VXSM GA Release 5.5.11 follows VXSM Release 5.5.10. The resolved caveats for VXSM Release 5.5.11 are listed in Table 5.

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.

---

Note To verify that you have the latest version of Cisco IOS required to support the new features included in this release, please check Cisco IOS availability status at Cisco.com.

---

The VXSM software release notes are supported by Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.5 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.5, both of which are available on cisco.com.

New Features in Release 5.5.11

Release 5.5.11 is a patch release that introduces the following two features:

•DSP RAS and Memory Error Detection Mechanism

•NSE Negotiation Based VXSM Up-speed

DSP RAS and Memory Error Detection Mechanism

Before Release 5.5.11, when a DSP core fails in an active VXSM, the standby VXSM takes over the active card's role. If the DSP core fails in a standby VXSM, then it reboots the standby VXSM. In such a case, if the active VXSM also fails due to some reason, then there is a complete outage for 3 to 5 minutes. In case a DSP core fails in a standalone VXSM, then the failed DSP core is marked as a bad core along with other sibling cores in the DSP chip. In this case, the existing calls on the affected DSP chip are dropped and no new calls are allowed.

In Release 5.5.11, these issues are resolved by implementing the DSP RAS feature. When a DSP core fails, VXSM brings the core back to in-service by re-downloading the DSP image on the entire DSP chip. For active and standalone VXSMs, the existing calls on the chip are moved to other available cores before the image re-download. VBD-fax calls are moved as voice calls on the new DSP core. T38 fax calls will be dropped by VXSM during the call movement. Call movement will happen only if adequate DSP channels are available to accommodate the affected calls; otherwise card will be reset in case of redundant setup. For standalone VXSM, the card will continue to work with reduced capacity.

The memory error detection feature helps VXSM to detect the potential memory problems in DSP cores. On receiving a memory corruption indication from the DSP, VXSM takes appropriate recovery actions.

This feature is supported only in TGW codec template in xGCP protocol. The following commands are added to support this feature:

•cnfDspRedownload

•dspDspRedownload

NSE Negotiation Based VXSM Up-speed

From Release 5.5.11, in gateway controlled mode, VXSM upspeeds upon detecting the modem tones only when NSE negotiation is successful in the Call Signaling. You can enable the feature by using the cnfNseNegoUpspeed command. The command is supported only in xGCP mode.

Firmware Images

For each VXSM card type (OC-3/STM-1, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. When placing an order, the user must specify whether a Non-CALEA or CALEA image is required.

Both CALEA and Non-CALEA images supports three Media Gateway Control protocols, namely, H.248, MGCP, and TGCP. However, VXSM supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP protocols when the image is first loaded from the PXM using the setrev command.

The CALEA image supports LI based on SII architecture for H.248, TGCP and MGCP protocols. The PktCable CALEA is supported only with MGCP and TGCP protocols.

VXSM supports four different Codec templates; Tandem Gateway (TGW), Tandem Gateway 2, Fixed Mobile Convergence (FMC), and Cable. The Cable template can be used only in conjunction with TGCP.

Upgrading from an Earlier VXSM Release

VXSM can be gracefully upgraded (configuration is preserved) from VXSM Release 5.4.21 or later.

---

Note VXSM supports upgrade of non-CALEA to CALEA firmware. But upgrade from CALEA to non-CALEA is not supported.

---

When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution:

---

Caution Prior to upgrade, user should confirm that additional termtypes (other than the defaults) have not been configured for VXSM in H.248.

---

---

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.

In particular:
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:

resetcd <SecondarySlot>

Step 4 Both primary and secondary VXSM cards should now have their original SW image and original DB

---

VXSM Management Information Base

The VXSM Management Information Base (MIB) Version 5.5.11 is available to users with CCO accounts who can access the MIB and VXSM software on-line at: http://www.cisco.com/public/sw-center/index.shtml

---

Step 1 Log on to http://www.cisco.com/public/sw-center/index.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 5500) to display a list of downloadable files.

Step 4 Click on the desired file (for example, mgx8850-fw-5500.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 mgx8850rel5500mib.tar).

Step 9 Untar the MIB file to display its contents.

---

Service Module Support by Platform

Service Module	MGX8880	MGX8850
	PXM45/C	PXM1	PXM45/B	PXM45/C	PXM1E
MGX-RPM-XF-512	Yes		Yes	Yes	No
MGX-RPM-PR-512	Yes		Yes	Yes	Yes
VISM-PR-8T1	Yes	Yes	Yes	Yes	Yes
VISM-PR-8E1	Yes	Yes	Yes	Yes	Yes
AXSM-1-2488/B	Yes		Yes	Yes
AXSM-16-T3/E3/B	Yes		Yes	Yes
AXSM-16-155-XG	Yes		Yes	Yes
AXSM-8-622-XG	Yes		Yes	Yes
MGX-VXSM-155	Yes		No	Yes
MGX-VXSM-T1E1	Yes		No	Yes
MGX-VXSM-T3	Yes		No	Yes
MPSM-T3E3-155	No		Yes	Yes	Yes
MPSM-16-T1E1	Yes		Yes	Yes	Yes
RCON-1TO5-8850	Yes			Yes

Upgrade Compatibility Matrix

---

Note VXSM Release 5.5.11 is supported only with PXM-45/B and 45/C.

---

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 1 VXSM Software Upgrade Matrix

Product	Latest Firmware	Min. Firmware
PXM45	5.5.10	5.4.30
MGX-RPM-XF-512	12.4(15)T9	12.4(15)T1
CWM	16.0.00	15.4.00
CTM	9.1	8.5
VISM-PR	3.3.35.203	3.3.25
AXSM-16-T3/E3/B	5.5.10	5.4.30
AXSM-16-155-XG	5.5.10	5.4.30
AXSM-8-622-XG	5.5.10	5.4.30
MPSM-16-T1E1	5.5.10	5.4.30
MPSM-T3E3-155 (8850 only)	5.5.10	5.4.30
BTS	5.0(1) V05	5.0
PGW	9.8	9.8

Table 2 describes the software images available for Release 5.5.11 for VXSM.

Table 2 Software Images for Release 5.5.11 for VXSM 

Board Pair	Latest Boot Code Version	Minimum Boot Code Version	Firmware
MGX-VXSM-155, CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.055.011.202.fw
MGX-VXSM-155, Non-CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.005.011.202.fw
MGX-VXSM-T1E1, CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.055.011.202.fw
MGX-VXSM-T1E1, Non-CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.005.011.202.fw
MGX-VXSM-T3, CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.055.011.202.fw
MGX-VXSM-T3, Non-CALEA	vxsm_005.005.011.202_bt.fw	vxsm_005.004.021.201_bt.fw	vxsm_005.005.011.202.fw

Caveats for VXSM Release 5.5.11

This section describes software caveats for Release 5.5.11.

Open Caveats in Release 5.5.11

Table 3 describes the open caveats in VXSM Release 5.5.11.

Table 3 Open Software Caveats for VXSM Release 5.5.11

DDTS Issue	Description
CSCtf68851	Headline: CRML's cmReq buffers exhausted due to SSRC collisions on 48E1T1 VXSMs. Symptom: Customer is facing cause value 38 (SS7, Network Out of Order) in release message. On the VXSM-T1E1 card, error 435, error 500 are seen (H.248 through PDU), and after a VXSM reset, the REL 38 stops. Conditions: This issue is seen on the VXSM-T1E1 card. Workaround: resetcd <slot# of active VXSM>

.

Resolved Caveats in Release 5.5.11.202

Table 4 describes the caveats resolved in VXSM Release 5.5.11.202.

Table 4 Resolved Software Caveats for VXSM Release 5.5.11.202

DDTS Issue	Description
CSCtg93463	911 test call failed.
CSCtg22966	Hung CCB on CAS trunk.
CSCth02900	VXSM upgrade to 5.55.11 fails and cause loss of H248 associations.
CSCtg78564	VXSM resets due to SSI-3-EXCEPTION.
CSCth31330	Standby VXSM 5.5.10.200 rebooted after PGW did a failover.
CSCtg48922	Echo cancelor is not fully convergent in the beginning of the call.

.

Resolved Caveats in Release 5.5.11.201

Table 5 describes the caveats resolved in VXSM Release 5.5.11.201.

Table 5 Resolved Software Caveats for VXSM Release 5.5.11.201

DDTS Issue	Description
CSCsz72654	V23 calls fail when V23 FSK signals are followed.
CSCta56274	VXSM not retrying RSIP to MGC in case of no ACK.
CSCta63529	VXSM M3UA associations never establish to Master (Active) PGW only.
CSCtb09796	VXSM goes OOS when MGC send 506 "Transaction Pending Exceeded".
CSCtc10162	433 Termination Id is already in Context VXSM.
CSCte49204	VXSM sending NSE 194 for CA controlled VBD.
CSCte49639	INTEROP: Assoc not coming in IS with PGW after issuing OOS and INS.
CSCte52645	Journaling not taking place on standby, after core kill on active in SDH.
CSCte63347	V21 Modem False Tone Detection.
CSCte97017	DSP Image Checkin 11.03.602.01.
CSCtf19631	MGCP exception caused card reload.
CSCtf22258	MGCP: Avaliable signal capacity is 99% even if all the channels are used.
CSCtf27033	T.30 CRP timer on VXSM is too low for multihop fax transmission.
CSCtf35288	VXSM switchover due to DSP crash.
CSCtf48160	Standby reboots on 1st dsp core kill, in load with 1aess configuration.
CSCtf53488	T38-vbd: 904 observed on terminating gateway on sending fax.
CSCtf71812	H248: Audit truncates remote username in "o" line.
CSCtf95438	MGCP: Standby resets on sending 'invalid' mode in MDCX with r:cl.
CSCtf96226	VXSM fails to go for switchover on memory corruption.
CSCtf98136	Upgrade: V23 mode configuration gets lost during Calea to Calea upgrade.
CSCtf98814	Excpetion on active VXSM during core crash,with ras on in 1aess load.
CSCtg18937	H248: Wrong audit values shown for "s" line in the Local SDP.
CSCtg22200	Support for G.nX64,GnX64,G.Clear codec string in H.248.
CSCtg26770	Sending Modify in T38 causes Hung Termination.
CSCtg56421	Offline diagnostic failure in full mode.

.

Resolved Caveats in Release 5.5.11.200

Table 6 describes the caveats resolved in VXSM Release 5.5.11.200.

Table 6 Resolved Software Caveats for VXSM Release 5.5.11.200

DDTS Issue	Description
CSCtc05130	VXSM does not detect V21 after switchover in case of back to back CA -T38 FAX.
CSCtd08911	No GENERAL_ACK message for RTCP_SEND_PKT message from DSP to host.
CSCtd33828	ECAN mismatch in HS modem after mid call codec change.
CSCtd57955	Command crmlstats does not reset even after crmlclrstats.
CSCte01692	MGCP: End point getting deleted on back to back fax.
CSCte18735	MGCP: End point getting deleted on T38-fallback with none upscodec (cnfvbdprof).
CSCte44929	GW failed to downspeed on a particular sequence.
CSCte54762	GCP: Incorrect error messge on playing the cot tone on a connection ID.
CSCsz16419	VXSM CPU Utilization: Discrepancy in VXSM CPU utlisation between the VXSM command dsprscutil and shell command ccmAveCpuPrint.
CSCsy82133	VXSM card fails online diagnostic test.
CSCta22204	Cannot delete VIF when DS1 is in alarm after the far-end disconnect.
CSCta52456	Debug enhancements for Online Diagnostic feature.
CSCtb25255	Incorporating code review changes done for Online Diagnostic feature.
CSCtb36653	DCAP software exception log enhancement for task trace.
CSCtb90868	xGCP: DSP Redownload and Memory Error Detection.
CSCtd19129	DTMF is not regenerated due to ill-digits.
CSCta53565	VXSM does not send NSE on downspeed.
CSCta56274	VXSM not retrying RSIP to MGC in case of no ACK for forced line oos.
CSCtc66969	XGCP: Disable tone detection on NSE negotiation.
CSCtd54845	Hung connections detected after running mixed load of T.38 Fax and Voice .
CSCtd66554	VXSM shall support the mid call NSE negotiation.
CSCte19130	MGX 505: Unsupported remote connection descriptor.
CSCte48561	XGCP: DLCX not processed if previous transaction response is pending.
CSCtf35799	MGCP: VXSM generated DLCX contains invalid (0) conn-id.

.

Related Documentation

The following documents contains information that may be useful to software Release 5.5 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 5.5

•Cisco MGX 8880 Media Gateway, Release 5.5: A Guide to User Documentation.

•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.5.10

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

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco 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. (1002R)

Copyright © 2010, Cisco Systems, Inc. All rights reserved.