Guest

Cisco MGX 8880 Media Gateways

Cisco VXSM Release Notes_5.6.21

  • Viewing Options

  • PDF (170.2 KB)
  • Feedback
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.21

Table Of Contents

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

Contents

About This Release

Enhancements in Release 5.6.21

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

Feature Clarifications

Call Rate Performance Support

Restrictions

Online Diagnostics Feature as Applied to VXSM

DSP Resources Under Mixed Codec Conditions

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.21

Open Caveats in Release 5.6.21

Resolved Caveats in Release 5.6.21

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


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


Revised: June 12, 2012, OL-23364-05

Contents

About This Release

Enhancements in Release 5.6.21

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

Feature Clarifications

Call Rate Performance Support

Online Diagnostics Feature as Applied to VXSM

DSP Resources Under Mixed Codec Conditions

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.21

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

About This Release

The VXSM Release 5.6.21 follows VXSM Release 5.6.20. The resolved caveats for VXSM Release 5.6.21 are listed in Table 4.

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.6.10 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.6.10, both of which are available on Cisco.com.

Enhancements in Release 5.6.21

The Release 5.6.21 includes the following enhancements for the Cisco VXSM platforms:

Debugging Enhancements

Commands for Capturing the Configuration on VXSM

Bearer Traces Based on DS1/DS0

Command for Capturing Signaling Messages in H.248 and MGCP

User configurable options for the cnfgwparams command:

Default T.38 attributes, which can be sent in the Session Description Protocol (SDP) response

Induced automated switchover upon agere queue failure

Digital signal processor (DSP) tone parameters such as, hangover and Solution Reference Network Design (SNRD)

Commands for Capturing the Configuration on VXSM

In release 5.6.21, a few commands are added to capture the VXSM configuration. By using these commands on the VXSM console, you can capture the important part of the VXSM configuration.

The following commands are added:

debughelp-Info

debughelp-All

debughelp-Config

debughelp-MGCP

debughelp-PVC

debughelp-XUA

debughelp-SS7

debughelp-SCTP

debughelp-CAS

debughelp-AAL2

debughelp-DebugStats

Bearer Traces Based on DS1/DS0

Before 5.6.21, bearer tracing was performed based on the line number in dotted format, using the addbearertraceendpt command. Effective with release 5.6.21, using the addbearertraceendpt command, you can provide the line number either in the dotted format or the DSX1 format.

Command for Capturing Signaling Messages in H.248 and MGCP

Effective with Release 5.6.21, the debughelp {-FileSigMsg | -FTPSigMsg} command is added to capture the signaling messages between VXSM and Media Gateway Controller (MGC). To debug, you need to capture the signaling messages and understand the call flow. Using this command, you can capture the signaling messages either in the processor switch module (PXM) memory (Hard Disk) or in a Server using FTP.

debughelp-FileSigMsg: This command stores signaling messages in MGX hard disk at the C:vxsmlogs directory. It supports a maximum of 5 calls.

debughelp-FTPSigMsg: This command stores signaling messages in a server. It can run for a maximum of 15 minutes at a maximum of 10 CPS. Ensure sufficient space on the server.

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 support 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 upgraded (configuration is preserved) from VXSM Release 5.5.11 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 If an H.248 association is active with SrvChgProfile (used in service change message) as BT_TGW in 5.3.x.x release, after graceful upgrade to supported releases, the association will continue to use BT_TGW, but new association(s) cannot be added with SrvChgProfile as BT_TGW.

From the 5.4.00 release onwards, the BT_TGW SrvChgProfile is no longer available. All new associations must be added using either etsi_tgw or CISCO_TGW.

Before upgrading, you must confirm that the additional term types (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

Feature Clarifications

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 50.

In H.248, the maximum CPS supported is 85 (without signaling). If signaling (M3UA/IUA) is configured, then the maximum supported CPS is 50.

Restrictions

This section includes information about restrictions pertaining to performance and the recommended actions:

If the G.723 codec is not used as a voice codec, then disable all variants of the G.723 codec using the cnfcodecparam command.

If the G.723 codec is enabled but not used in voice calls, then ensure that the codec list is specified without the G.723 codec while creating a call. If no codec is specified while creating a call on VXSM, then the resources for the G.723 codec are reserved. This affects the normal resource allocation algorithm, which in turn results in anomalous behavior of VXSM.

Online Diagnostics 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 diagnostics tests that use four of the VXSM G711 DSP resources.

If the user executes the VXSM dspdspcodecpools command, the resulting display shows the four G711 DSP resources being used (for diagnostics) and subtracts them from the remaining available Codecs (see example below).

mgx.3.VXSM.a > dspdspcodecpools
=====================================================================
                    DSP codec capacity usage
=====================================================================
 
   
Codec pool                Current utilized        Current available
                        capacity (#DSP chans)   capacity (#DSP chans)
==========              =====================   =====================
G711 family/HDLC            179                       7885             
G729/G726/T.38 family       0                         3919             
G723 family                 0                         2911 
 
   

In this example, 175 G711 calls have been established along with four G711 resources used for diagnostics.

The online diagnostics feature does not reduce the maximum number of 8064 G711 DSP resources 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 resource 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. Fragmentation can happen because the pattern of future calls cannot be predicted beforehand.

VXSM Management Information Base

The VXSM Management Information Base (MIB) Version 5.6.21 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

 

Compatibility


Note VXSM Release 5.6.21 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 Interoperability 

Product
Latest Firmware
Min. Firmware

PXM45

5.6.21

5.5.10

MGX-RPM-XF-512

12.4(15)T17

12.4(24)T5

12.4(15)T14

12.4(24)T4

CWM

NA

NA

CTM

9.2 build: 492 patches: 1

9.2 build: 492 patches: 1

VISM-PR

3.3.35.203

3.3.25

AXSM-16-T3/E3/B

5.6.00

5.5.10

AXSM-16-155-XG

5.6.01

5.5.11

AXSM-8-622-XG

5.6.01

5.5.11

MPSM-16-T1E1

5.6.00

5.5.10

MPSM-T3E3-155 (8850 only)

5.6.00

5.5.10

BTS

6.0

6.0

PGW

9.8(1)S12P12

9.8

Cisco 2600 Series Routers

c2600-ipvoice-mz.123-9.14.T

c2600-ipvoice-mz.123-9.14.T

Cisco 2600 for use as an IP Transfer Point

c2600-itp-mz.122-21.SW bin

c2600-itp-mz.122-21.SW bin

Cisco 3700 Series Routers

c3725-ipvoice-mz,123-9.14.T

c3725-ipvoice-mz,123-9.14.T

Cisco ATA 188

3.2.0 for SIP/MGCP/H323

3.2.0 for SIP/MGCP/H323

Linksys PAP2 Phone Adapter

Version 2.0.6 (LS)

Version 2.0.6 (LS)

Linksys RT31 Router

Version 1.27.01

Version 1.27.01

Sipura 2100 ATA

Version 3.2.3

Version 3.2.3


Table 2 describes the software images available in Release 5.6.21 for VXSM.

Table 2 Software Images for the VXSM Release 5.6.21 

Board Pair
Latest Boot Code Version
Minimum Boot Code Version
Firmware

MGX-VXSM-155, CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.056.021.200.fw

MGX-VXSM-155, Non-CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.006.021.200.fw

MGX-VXSM-T1E1, CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.056.021.200.fw

MGX-VXSM-T1E1, Non-CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.006.021.200.fw

MGX-VXSM-T3, CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.056.021.200.fw

MGX-VXSM-T3, Non-CALEA

vxsm_005.006.021.200_bt.fw

vxsm_005.005.010.200_bt.fw

vxsm_005.006.021.200.fw


Caveats for VXSM Release 5.6.21

This section describes software caveats for the VXSM Release 5.6.21.

Open Caveats in Release 5.6.21

Table 3 describes the open caveats in the VXSM Release 5.6.21.

Table 3 Open Software Caveats for VXSM Release 5.6.21  

DDTS Issue
Description

CSCua07013

VXSM does not send the RELEASE_IND to MGC when E1 is administratively down.

CSCty81151

V.21 +DIS signal is lost on a VXSM gateway in the T.38 mode.


.

Resolved Caveats in Release 5.6.21

Table 4 describes the caveats resolved in the VXSM Release 5.6.21.

Table 4 Resolved Software Caveats for VXSM Release 5.6.21  

DDTS Issue
Description

CSCtl42931

Noticed database inconsistency issue after upgrading to 5.5.10.

CSCtu08316

VXSM missing notify with V.21 flag.

CSCtu66366

Same valid port is returned in the T.38 descriptor when first SDP has the same port.

CSCtu67395

A few characters are not allowed in origin line of SDP.

CSCtw29644

Debug enhancements for standby memory leak.

CSCtx54585

MGX DSP CM Fax tone detected incorrect behavior.

CSCtx65325

Fax call fails over SIP trunk due to SDP with IP:0.0.0.0 in the T.38 mode.

CSCtx97804

Incorrect AMR SDP creates 501 even when AMR is not negotiated.

CSCty66577

MGX unable to handle CRCX with 2 media ports where the first port is 0.

CSCtz10549

Loopback enable, by default, causes one way voice.

CSCty90137

VXSM sends traps even after the alarms are cleared.


.

Related Documentation

The following documents contain information related to the VXSM Release 5.6.21:

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.6.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