Release Notes for Cisco Voice Interworking Service Module Release 3.2

Table Of Contents

Release Notes for Cisco Voice Interworking Service Module Release 3.2

Table of Contents

About Release 3.2

Overview

New Features Introduced in Release 3.2

VISM Management Information Base

VISM Redundancy

VISM Call Rate

Compatibility

Limitations and Restrictions

Upgrade Procedures

Prerequisites

VISM/VISM-PR Upgrades with PXM1

VISM-PR Upgrades with PXM1E and PXM45

VISM/VISM-PR Downgrade Procedure

VISM to VISM-PR Hardware Upgrade

Caveats for VISM Release 3.2

Resolved Caveats in Release 3.2

Open Caveats in Release 3.2

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

Release Notes for Cisco Voice Interworking Service Module Release 3.2

These release notes are part number OL-5026-01 Rev. D0, July 26, 2004.

The Voice Interworking Service Module (VISM) product is supported by MGX Voice Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.

The VISM/VISM-PR software release notes are supported by the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference Release 3.2, which is available on cisco.com.

Table of Contents

About Release 3.2

The VISM/VISM-PR Release 3.2 is a new release. For a list of new features, see "New Features Introduced in Release 3.2" section. For a list of the open and resolved caveats in this release, see "Caveats for VISM Release 3.2" section.

Note The content of VISM Release 3.2 supersedes previous releases.

Overview

These release notes contain the following sections:

• "New Features Introduced in Release 3.2" section

• "VISM Management Information Base" section

• "VISM Redundancy" section

• "VISM Call Rate" section

• "Compatibility" section

• "Limitations and Restrictions" section

• "Upgrade Procedures" section

• "Caveats for VISM Release 3.2" section

• "Related Documentation" section

• "Obtaining Documentation" section

• "Documentation Feedback" section

• "Obtaining Technical Assistance" section

• "Obtaining Additional Publications and Information" section

New Features Introduced in Release 3.2

VISM Release 3.2 is applicable to VISM and VISM-PR hardware. New features and hardware applicability introduced in VISM Release 3.2 are:

•Lossless Compression—VISM-PR supports a new codec for Lossless compression.

•Call Progress Tones—VISM-PR detects a subset of commonly used call progress tones and reports these tones to the call agent.

•Wireless Tones—VISM-PR supports the addition of wireless tones to the set of call progress tones.

•Diagnostic Testing for DSP Failures—VISM-PR supports enabling DSP diagnostic testing.

•TGCP 1.0 (IT Packaging and Endpoint Naming)—VISM and VISM-PR support TGCP 1.0.

•AIS Alarm Suppression—VISM and VISM-PR support alarm suppression.

•G.729a with 20 ms—VISM and VISM -PR support the G.729a codec with 20 ms.

•E1 CAS Idle Code—VISM and VISM-PR support E1 CAS idle code.

VISM Management Information Base

The VISM Management Information Base (MIB) Version 0.0.35 is available by request through your Cisco VISM product marketing representative.

VISM Redundancy

Table 1 provides the support level for 1:N Service Module Redundancy (N = 1 through 11).

Table 1 Service Module Redundancy

Front Card Model Number

Redundancy Support

MGX-VISM-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-8E1

1:N redundancy (bulk mode support for E1 lines only).

MGX-VISM-PR-8T1

1:N redundancy (bulk mode support for T1 lines only).

MGX-VISM-PR-8E1

1:N redundancy (bulk mode support for E1 lines only).

Note You can use a VISM-PR card as a redundant card for a VISM card, but a VISM card cannot be used as a redundant card for a VISM-PR card.

VISM/VISM-PR cards support bulk distribution using the SRM-3T3 and SRM-E (OC3) cards. In a redundancy configuration VISM/VISM-PR cards in bulk distribution mode do not require any backcards.

VISM Call Rate

Software Release 3.2 for VISM/VISM-PR handles 10 CAS, SS7, or PRI calls per second per VISM/VISM-PR card.

Compatibility

VISM/VISM-PR software interoperability with Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8830, and Cisco MGX 8850 (PXM1, PXM1E, PXM45) platform software is listed in Table 2.

Table 2 VISM/VISM-PR Software Interoperability

Product

CW2000 Name

Latest Firmware

Minimum Firmware

PXM1

MGX 8850

1.2.21

1.2.20

PXM1E

MGX 8850/MGX 8830

4.0.1.2

3.0.23

PXM45

MGX 8850

4.0.1.2

3.0.23

RPM-PR

RPM-PR

12.2(8)T1

12.2(8)T1

RPM-XF

RPM-XF

12.2(15)T5

12.2(15)T5

SRME

SRM-E

FC-C0 BC-B0

FC-C0 BC-B0

SRM-3T3/C

SRM-C

FC-CA BC-A0

FC-CA BC-A0

AUSM

AUSM

10.2.21

10.2.00

AXSM

AXSM

4.0.12

3.0.23

CWM

CWM

12.0 Patch 2

12.0 Patch 2

Table 3 shows VISM and VISM-PR compatibility with the PXM controller cards.

Table 3 VISM/VISM-PR Compatibility with PXM Cards

PXM1

PXM1E

PXM45 (A/B/C)

VISM

Yes

No

No

VISM-PR

Yes

Yes

Yes

Table 4 shows VISM and VISM-PR compatibility with the Cisco MGX chassis.

Table 4 VISM/VISM-PR Compatibility with Cisco MGX Chassis

Cisco MGX 8230

Cisco MGX 8250

Cisco MGX 8830

Cisco MGX 8850 (PXM1)

Cisco MGX 8850
(PXM1E or PXM45)

VISM

Yes

Yes

No

Yes

No

VISM-PR

Yes

Yes

Yes

Yes

Yes

Table 5 describes the VISM/VISM-PR software interoperability with other Cisco products.

Table 5 Software Release 3.2 for VISM/VISM-PR Interoperability with Other Cisco Products

Product

CW2000 Name

Latest Firmware

Minimum Firmware

BTS

BTS 10200

4.1 (Q15)

4.1 (Q15)

PGW

PGW 2200

9.3(2)

9.3(2)

CISCO 2421

CISCO 2421

12.3.3

12.3.3

AS5400

AS5400

12.3.5

12.3.5

AS5300

AS5300

12.3.5 with vcware 11.32

12.3.5 with vcware 11.32

Table 6 describes the software images available for Release 3.2 for VISM/VISM-PR.

Table 6 Software Images for Release 3.2 for VISM/VISM-PR

Product Name

Software Version

Firmware Image Name

Description

MGX-VISM-SW3200

003.002.000.000

vism-8t1e1-003.002.000.000.fw

This image does not support the CALEA¹ feature.

MGX-VISM-LISW320

003.052.000.000

vism-8t1e1-003.052.000.000.fw²

This image supports the CALEA 1 feature.

¹CALEA = Commission on Accreditation for Law Enforcement Agencies.

²The CALEA implementation supports the CALEA law intercept confirmation interface.

Table 7 describes the software boot code requirements for VISM/VISM-PR Release 3.2.

Table 7 VISM/VISM-PR Software 3.2 Boot Code Requirements

Board Pair

Boot Code Image Name

Boot Code Version

MGX-VISM-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

Limitations and Restrictions

The VISM 3.2 software is applicable to VISM and VISM-PR. The following limitations and restrictions are valid for software Release 3.2 for VISM/VISM-PR:

•For the lossless codec, use the cnfcodecjtrdelay command to configure the fixed jitter-delay argument to 20 msec.

•In a PNNI network, upspeeding SVC fax or modem calls requires an increase in bandwidth between the voice codec and the vbd codec. For fax calls to go through, disable policing on the service modules (excluding VISM/VISM-PR).

•Switched AAL2 PVC mode is not recommended as this mode requires a meshed PVC network topology, which does not scale.

•The following commands are not supported:

–cnfmaxconfnum

–dspconferences

–dspmaxconfnum

•GR-303 is not supported for the LAPD commands.

•In AAL2 SVC mode, all active calls on VISMs are dropped upon PXM hard and soft switchover.

•For a list of open issues and mitigations in VISM Release 3.2, see "Open Caveats in Release 3.2" section.

Upgrade Procedures

This section describes the following upgrade procedures:

• Prerequisites

• VISM/VISM-PR Upgrades with PXM1

• VISM-PR Upgrades with PXM1E and PXM45

• VISM/VISM-PR Downgrade Procedure

• VISM to VISM-PR Hardware Upgrade

VISM/VISM-PR Release 3.2 provides a procedure for the graceful upgrade (one in which the existing VISM/VISM-PR configuration is preserved throughout the upgrade procedure) from one of the following releases:

•From VISM 1.5 to VISM 3.2

•From VISM 2.1 to VISM 3.2

•From VISM 2.2 to VISM 3.2

•From VISM 3.1(1) to VISM 3.2

•From VISM 3.1(2) to VISM 3.2

Caution Installing VISM software updates from VISM Release 2.2 with CALEA to VISM Release 3.2 without CALEA is not graceful.

Prerequisites

To ensure that the VISM/VISM-PR configuration is preserved throughout the upgrade procedure, you must complete the prerequisites listed in this section.

Before starting the graceful upgrade procedure, complete the following prerequisites:

•Configure your MGX 8000 Series shelf with at least two VISM cards in a redundant configuration.

For more information on adding redundancy, refer to the add redundancy, addred, command in the Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8850 PXM1-based Command Reference documentation and the Cisco MGX 8830 and Cisco MGX 8850 PXM1E/ PXM45-based Command Reference documentation.

•Ensure that the VISM cards are running at least Release 2.1, and the VISM-PR cards are running at least Release 3.0.

•Download software Release 3.2 for VISM/VISM-PR to the MGX 8000 Series shelf.

•If you are using the CALEA feature, ensure that you have the version of VISM/VISM-PR software that supports CALEA.

VISM/VISM-PR Upgrades with PXM1

This section describes the procedures for upgrading VISM/VISM-PR software when the VISM/VISM-PR is used with a PXM1 card.

Download VISM/VISM-PR Boot Code and Firmware to PXM1

To download the VISM/VISM-PR boot code and firmware to the PXM1 card, use TFTP.

Step 1 Log in to your TFTP server.

Step 2 Download the boot code and firmware images from the Cisco website.

Step 3 Download the selected revision of service module boot code into the service module.

a. tftp <node_name or IP address>

b. bin

c. put <backup boot> POPEYE@SM_1_0.BT

d. quit

Step 4 Download the selected firmware file.

To upgrade all VISM cards, proceed to Step 4 c. To upgrade an individual VISM card, proceed to Step 4 d.

a. tftp <node_name or IP address>

b. bin

c. put <FW file> POPEYE@SM_1_0.FW

quit

d. put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW

quit

Note Do not enter two put commands in the same TFTP session.

Step 5 Proceed to the "Upgrade VISM/VISM-PR Firmware with PXM1 Card" section to install the download.

Upgrade Boot Code with PXM1 Cards

Complete the following steps to upgrade the new backup boot code when you are using PXM1 cards in in a Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 chassis:

Note This procedure re-programs the VISM/VISM-PR boot code for previous VISM/VISM-PR cards using the VISM/VISM-PR runtime image version 1.0 to 2.0.

Step 1 Log in to the active PXM1 card (slot 7 or 8 for Cisco MGX 8250 and Cisco MGX 8850 chassis; slot 1 or 2 for Cisco MGX 8230 and Cisco MGX 8830 chassis).

Note VISM/VISM-PR must be in the active state in order to update the VISM/VISM-PR boot code.

Step 2 Execute the PXM1 install command.

nodename.1.27.VISM8.a > install [bt] [sm <slot>] <version>

Caution Do not touch the VISM/VISM-PR card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation corrupts the boot code, which cannot be recovered.

When the boot code is being written to PROM, you see comments displayed at the VISM/VISM-PR prompt. This behavior is normal and expected.

Step 3 Type the version command to verify the correct boot code.

Note Step 3 is optional.

Upgrade VISM/VISM-PR Firmware with PXM1 Card

Software Release 3.2 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of VI8_BT_3.2.00.

The following versions of VISM software Release 3.2 are available:

•003.002.000.000—without CALEA

•003.052.000.000—with CALEA

In this procedure the following conditions apply:

•If two VISM or VISM-PR cards are part of a redundancy group, initially the primary card is in the active state, and the secondary card is in the standby state.

•Old-rev refers to the firmware, Release 3.1(3) and prior.

•New-rev refers to the firmware after the upgrade, Release 3.2.

Perform the firmware upgrade on the VISM or VISM-PR cards. Do not remove the VISM cards and replace them with VISM-PR cards at this time.

Step 1 Log in to the active PXM1 card (slot 7 or 8 for Cisco MGX 8250 and Cisco MGX 8850 chassis; slot 1 or 2 for Cisco MGX 8230 and Cisco MGX 8830 chassis).

Step 2 Save the existing configuration as a contingency plan by entering the savesmcnf command:

nodename.1.8.PXM.a > savesmcnf <SM slot#>

This command saves the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure.

Step 3 To obtain the correct version of VISM/VISM-PR firmware, enter the dspfwrevs command.

nodename.1.8.PXM.a > dspfwrevs
Card Type Date Time Size Version File Name
----------- ------------------- -------- -------------------------------------
VISM-8T1E1 04/26/2004 20:06:04 248688 VI8_BT_3.2.00 sm150.bt
PXM1 01/04/2004 08:19:52 2602836 1.2.11 pxm_1.2.11.fw
PXM1 01/04/2004 11:03:02 2620132 1.2.21 pxm_1.2.21.fw
VISM-8T1E1 06/16/2004 13:29:38 3863768 003.051.002.000 sm150_11.fw
VISM-8T1E1 06/29/2004 15:35:12 3863688 003.051.002.211-A sm150_13.fw
PXM1 01/04/2004 11:01:56 1346844 1.2.21 pxm_bkup_1.2.21.fw
VISM-8T1E1 03/08/2004 08:20:16 4037880 003.002.000.000 sm150_3.fw
VISM-8T1E1 03/08/2004 08:19:44 248688 VI8_BT_3.2.00 sm150_3.bt
PXM1 01/04/2004 07:58:44 1345328 1.2.11 pxm_bkup_1.2.11.fw
VISM-8T1E1 01/07/2004 23:33:02 3863768 003.051.002.000 sm150_2.fw
VISM-8T1E1 03/08/2004 08:21:12 248688 VI8_BT_3.2.00 sm150_4.bt
VISM-8T1E1 04/05/2004 11:40:26 3865656 003.001.002.301-A sm150_29.fw
VISM-8T1E1 04/26/2004 19:59:52 4037880 003.002.000.000 sm150_1.fw
VISM-8T1E1 03/08/2004 08:20:58 4037880 003.002.000.000 sm150_4.fw

Step 4 Execute the PXM install command.

nodename.1.8.PXM.a > install sm <SM slot#> <new-rev>

Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.

Replace <new-rev > with the version of the new firmware (for example, 003.002.000.000).

Caution Ensure that you perform Step 4. If you do not perform Step 4, the boot code is corrupted and not recoverable.

This command causes the secondary VISM or VISM-PR card to reset and come up in the standby state, running the new-rev firmware. The primary VISM or VISM-PR card is unaffected by this command.

Step 5 Execute the PXM newrev command.

nodename.1.8.PXM.a > newrev sm <SM slot#> <new-rev>

Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.

Replace <new-rev> with the version of the new firmware.

This command causes the primary VISM or VISM-PR card to reset. The secondary VISM or VISM-PR card becomes active and is running the new-rev firmware.

Step 6 Execute the PXM commit command.

nodename.1.8.PXM.a > commit sm <SM slot#> <new-rev>

Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.

Replace <new-rev> with the version of the new firmware.

The two VISM or VISM-PR cards are now back to their original condition except that both cards are now running the new-rev firmware.

Step 7 Log in to the active VISM or VISM-PR card and use the display commands (for example, dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.

Note For more than one primary VISM or VISM-PR card in a redundancy group, ensure that the secondary card is in the standby state and repeat Step 5 and Step 6 for each VISM/VISM-PR card in the redundancy group.

Step 8 Perform the following verifications:

•Make minor modifications to the configuration.

•Check that the changes have been executed correctly.

•Change the configuration back again.

Note If the VISM or VISM-PR card is not part of a redundancy group, complete Step 1 to Step 4.

VISM-PR Upgrades with PXM1E and PXM45

This section describes the procedures for upgrading VISM-PR software when the VISM-PR is used with a PXM1E or PXM45 card.

Download VISM-PR Boot Code and Firmware to PXM1E and PXM45

To download the VISM-PR boot code and firmware to the PXM1E or PXM45 card, use FTP.

Step 1 Access the image on the Cisco Web site.

Step 2 To download the image, enter the ftp command.

ftp node-ip

where node-ip is the IP address of the node to which you want to download the image.

Step 3 Enter your user name and password.

Step 4 Enter bin.

Step 5 Access the appropriate directory.

cd C:FW

Step 6 Download the image to your C:FW directory.

a. To download one file at a time, use the put image-version command.

b. To download multiple files at the same time, use the mput <image-version> <image-version> command.

where image-version is the downloaded image from Step 1.

Step 7 To exit the download procedure, enter bye.

Upgrade Boot Code with PXM1E and PXM45 Cards

Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:

Step 1 Complete the steps in the Download VISM-PR Boot Code and Firmware to PXM1E and PXM45.

Step 2 Log in to the PXM1E or PXM45 card.

Step 3 To upgrade the VISM-PR boot, enter the burnboot command.

nodename.1.7.PXM.a > burnboot <slot> <revision>

Replace <slot> with the number of the VISM-PR card that you want to upgrade.

Replace <revision> with the version of the boot code you downloaded from Step 1.

The following example shows the burnboot.

nodename.1.7.PXM.a > burnboot 12 3.2(1.0)

The card in slot 12 will be reset.
burnboot:Do you want to proceed (Yes/No)? yes
For VISM-PR cards without redundancy, the card automatically resets and becomes active with the latest boot code image.

For VISM-PR cards with redundancy, the active card takes approximately 60 seconds to reset as standby. For the original standby card, complete Step 2- Step 3. This card now resets back to standby, and the standby card is now active.

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

Ensure that the VISM-PR cards have the minimum boot code version of VI8_BT_3.2.00.

The following versions of VISM-PR software Release 3.2 are available:

•003.002.000.000—without CALEA

•003.052.000.000—with CALEA

Perform the firmware upgrade on the VISM-PR cards.

Step 1 Log in to the active PXM1E or PXM45 card.

Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.

Step 3 To save the existing configuration as a contingency plan, enter the saveallcnf command.

nodename.1.7.PXM.a > saveallcnf

Step 4 To load the new software, enter the loadrev command.

nodename.1.7.PXM.a > loadrev <sm-primary-slot-num> <new-rev>

Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.

Replace <new-rev> with the new firmware version number for the VISM-PR software.

Caution Temporary traffic loss occurs.

Step 5 Ensure that the redundant card is returned to the standby state by executing the dspcds command.

Note You must wait for the redundant card to return to the standby state. If you issue the runrev command too early, an error message is generated. The rev change does not occur.

Step 6 To execute the download, enter the runrev command.

nodename.1.7.PXM.a > runrev <sm-primary-slot-num> <new-rev>

Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.

Replace <new-rev> with the new firmware version number for the VISM-PR software.

Caution Temporary traffic loss occurs.

Step 7 Ensure that the primary slot completes booting and goes into the standby state by executing the dspcds command.

Note You must wait for the primary slot to finish booting and get to standby state. Issuing the commitrev command early might be accepted without an error. However, the active and standby cards might not be swapped back to their original state. For example, the original primary card might be left in standby, and the original redundant card might be left as active.

Step 8 To commit the new download to the VISM-PR card, enter the commitrev command.

nodename.1.7.PXM.a > commitrev <sm-primary-slot-num> <new-rev>

Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.

Replace <new-rev> with the new firmware version number for the VISM-PR software.

The commitrev command switches the primary card from a standby state to an active state and the redundant card from an active state back to a standby state.

Step 9 To verify the card states, execute the dspcds command.

VISM/VISM-PR Downgrade Procedure

Use this procedure to downgrade VISM/VISM-PR software from software Release 3.2 to an earlier VISM/VISM-PR release. By following the downgrade procedure described here, the configurations are retained after the downgrade.

Note The configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.

Complete the following steps to downgrade the VISM/VISM-PR software from software Release 3.2 for VISM/VISM-PR to Release 3.1, 3.0, 2.2, 2.1, or 1.5:

Step 1 If the VISM/VISM-PR card is in a redundancy group, remove the redundancy.

nodename.1.7.PXM.a > delred <SM slot#>

Step 2 Download the old-rev firmware onto the MGX shelf.

Step 3 Execute the PXM clrsmcnf command:

nodename.1.7.PXM.a > clrsmcnf <SM slot#>

Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.

Wait for the card to become active. The VISM/VISM-PR card resets after you execute this command.

Step 4 Execute the PXM restoresmcnf command:

Caution The restoreallcnf command reconfigures all of the cards in the chassis.

nodename.1.7.PXM.a > restoresmcnf -f <filename> -s <SM slot#>

Replace <filename> with the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.

Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.

The VISM/VISM-PR card resets again. The card becomes active, running the old-rev firmware with the old configuration.

Note For PXM1E/PXM45 cards, you cannot restore the configuration for an individual VISM-PR service module. You can save and restore the configuration of all cards in a chassis using the saveallcnf and restoreallcnf commands.

Step 5 Reconfigure the redundancy group, if required.

VISM to VISM-PR Hardware Upgrade

Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.

Caution You must install the redundant (standby) VISM-PR card first. Failure to follow this recommendation results in traffic loss. In addition, do not remove an active VISM card from your chassis. Ensure that you configure an active VISM card to the standby state before you remove it and replace it with a VISM-PR card.

Step 1 Remove the redundant (standby) VISM card from your chassis.

Step 2 Install a VISM-PR card in the slot you removed the VISM card from in Step 1.

Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).

Step 4 Remove the now redundant VISM card from your chassis.

Step 5 Install a VISM-PR card in the slot you removed the VISM card from in Step 4.

Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to ensure that the correct card type is shown.

Step 7 Log in to the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card.

If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM. Repeat the dspcd command to ensure that the correct card type is shown.

Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.

Step 9 Remove a standby VISM card from your chassis.

Step 10 Install a VISM-PR card in the slot you removed the VISM card from in Step 9.

Step 11 Repeat Step 9 and Step 10 to remove any remaining VISM cards in your chassis and replace them with VISM-PR cards.

Step 12 Repeat Step 6 and Step 7 on the remaining VISM-PR cards to insure the correct card type is shown.

Caveats for VISM Release 3.2

This section describes the resolved and open software caveats for VISM/VISM-PR Release 3.2. Caveats describe unexpected behavior or defects in VISM software.

Resolved Caveats in Release 3.2

Table 8 describes the caveats that have been resolved in VISM/VISM-PR Release 3.2 as of December 30, 2003.

Table 8 Resolved Caveats for VISM Release 3.2

DDTS Issue

Description

CSCdx94130

VISM loses some DTMF digits when ON time is less than 45ms.

CSCea42208

VISM stuck in boot after switchcc; standby did not take over.

CSCea43230

VISM fail to boot on reset in PXM45 chassis.

CSCea64302

VISM resets while running T.38 VoIP trunking load.

CSCeb05718

VISM locks out trunk after wink failure.

CSCeb32754

Cannot establish calls on some of the endpoints after PXM switchover.

CSCeb59727

Send proper Severity Value in VISM traps.

CSCec52528

Configuration GUI - Cannot configure resource partition for VISM.

CSCin48395

Cannot modify/delete VISM/VISM-PR PVC/hybrid connection after VISM/VISM-PR card is reset.

CSCuk44619

VISM notifies correctly only the first 20 DTMF digits to CA.

CSCuk44700

Cracking noise on G.711a codec on VISM-PR.

CSCdy34426

The cnflnoos state is not maintained after switchover.

CSCdy47135

SNMP cannot write to vismRtpPaylodType.

CSCdy50374

VISM: Cannot create resource partitions for the first time through SNMP.

CSCdy78548

M: conttest needs to support both 1780 and 2010 go tones.

CSCdy89525

VISM missing endpoint domain name in response to AUEP */*/*.

CSCdz64206

Degradation of voice quality when multiple announcement RQNTs are sent.

CSCdz68518

Failed to set objects in srcpPeerGrpParamTable.

CSCdz72726

Incorrect error description for ds0CasGlareTime configuration.

CSCdz73119

VISM requires RtpConnMode be mandatory for configuration: MIB change.

CSCea02640

RSVP session table shows non-existent sessions.

CSCea05685

Calls get stuck after IP connection from CA is lost.

CSCea24522

Make OAM loop back timer configurable.

CSCea38658

UPGRD: VISM logs FIPC and unknown message for congestion management feature.

CSCea62890

DSP crashes after failed T.38 fax call timeout.

CSCea76010

VISM-PR card only supports 145 endpoints after card upgrade.

CSCea78849

ECAN tail length using cnfecantail is not applied to the endpoints.

CSCea81110

VISM does not duplicate call content for LI using MGCP MDCX.

CSCeb21008

MGX log shows tDspmCot CC-4-IDX_OUT_OF_RANG.

CSCeb33989

Loss of IP connectivity causes backhaul buffer leak.

CSCeb34686

Vism marking endpoints as disconnected when active call agent is present.

CSCeb34708

MGCP response takes too long to get to the call agent.

CSCeb39267

SPINI failure.

CSCeb56424

Deleting DN before deleting domain IPs causes configuration problems.

CSCeb65531

The sarSlotNum always indicates 1.

CSCeb67558

VISM crash playing announcement to TDM side without connection.

CSCeb72094

VISM sends wrong t: value in response to AUEP from BTS.

CSCeb77691

VISM returns 510 error when parse SDP messages from 827.

CSCeb85639

VISM does not send oc to call agent with FGD E911 call.

CSCeb85676

VISM does not handle glare properly with FGD outgoing CAS.

CSCec01686

Missing concealment for lost RTP packets in VoIP.

CSCec08071

VISM does not collect digits if CRCX after RQNT.

CSCec26651

Reading vismDynamicPT MIB crashes VISM card.

CSCin38082

The dspchan o/p of VISM-PR card is not proper.

CSCuk42130

The dspxgcpcon CLI command reports wrong timestamp information.

CSCdz86155

Tone plan file written in DOS format is not parsed.

CSCdw48826

The dspcodectmpls and cnfcodectmpl display for codec supported is not clear.

CSCdz85907

Tone plan with status lostFile cannot be deleted.

CSCea57223

VISM-E1 does not send correct idle pattern.

CSCea60784

Latency improvements for G.711, G.726, and G.Clear in VISM-PR.

Open Caveats in Release 3.2

Table 9 describes the open caveats in VISM/VISM-PR Release 3.2 as of June 28, 2004.

Table 9 Open Caveats for VISM/VISM-PR Release 3.2

DDTS Issue

Description

CSCeb74938

Symptom: End-to-end path verification failures with G.726-40 codec.

Conditions: The G.726-40 40 millisecond packetization period is not functioning.

Workaround: All other packetization periods for this codec and the other G.726 codecs are working correctly.

CSCeb76617

Symptom: Not able to pass VAD test for G.729ab codec (AAL2 trunking application).

Conditions: When the VAD is tested for the G.729ab codec through the VQT box, the test fails.

Workaround: VAD starts when the threshold is below -67 db. In the VQT box, the lowest value that can be set is -60 db. So, VAD cannot be tested using that box.

CSCec01946

Symptom: Low PESQLQ scores on G.729ab codecs.

Conditions: In VoIP and AAL2 trunking applications, G.729ab codec configuration shows lower PESQ scores than G.729a codec configuration.

Workaround: It is recommended that G.729a with generic VAD be utilized in place of G.729ab.

CSCec30727

Symptom: After the upgrading from 3.1.0 to 3.1.2, a couple of DSPs in a VISM-PR E1 card failed.

Conditions: After running load for 4 to 5 days, this problem seems to occur. The only difference between 3.1.0 and 3.1.2 is the POS application and Marconi application which are supported in 3.1.2.

Workaround: Reset the VISM-PR card.

CSCec54765

Symptom: VISM regenerates incorrect DTMF on-times in VoIP trunking mode.

Conditions: When DTMF digits with on-times of less than 50 ms are detected on the near-end VISM, the digits are regenerated with inconsistent on/off times on the far end VISM.

Workaround: Ensure DTMF digits being detected have an on-time value greater than 50-60 ms. The recommendation is greater than 60 ms.

CSCec68687

Symptom: Simultaneous ISDN call drops not clearing all the endpoints on VISM.

Conditions: This problem happens only when all the established calls drops simultaneously which is a rare situation under normal circumstances.

Workaround: Taking the gateway out of service and back in service clears all the ports and makes them available for the new calls.

CSCec79013

Symptom: PXM1 VISM VBR3nrt connections shown in CWM as VBR1nrt.

Conditions: PXM1 VISM VBR3nrt connections.

Workaround: None.

CSCed10672

Symptom: VISM supports 217 AAL2 SVC calls on VISM-PR-E1 only.

Conditions: VISM can do 217 simultaneous AAL2 SVC calls in VISM-PR-E1 card only. Call attempts beyond 217 active calls are rejected in CRCX.

Workaround: Configure the call agent to setup no more than 217 simultaneous AAL2 SVC calls on the VISM-PR-E1 card at any given time.

CSCed02188

Symptom: Running a load of 9 cps with CP tones causes DSP failure.

Conditions: When using VISM-PR in VoIP switching mode with call progress tone detection enabled, running a load of 9 calls per second can cause the VISM DSP to die. Therefore, the VISM cannot run more than 8 calls per second.

Workaround: Disable the call progress tone detection (default).

CSCed15923

Symptom: Terminating VISM attempt downspeed from VBD with Bell103 and V.22Bis modulations.

Conditions: In AAL2 Trunking mode, upspeed calls from modem/POS systems will not connect in Bell 103 and V.22bis modulations.

Workaround: None for AAL2 trunking mode.

CSCed19772

Symptom: VISM rejects SDP with SPACE as session name (s=).

Conditions: VISM parses out white space before processing the s= session name field.

Workaround: Request the SDP sender to replace the SPACE character with a DASH (s=-) in SDP.

CSCed21523

Symptom: Redundancy on modem pass call from 5xxx to VISM/VISM-PR fails.

Conditions: Modem passthrough calls with redundancy ON from the (5400/5300) to (VISM/VISM-PR) fail. The calls stay on ringing state for sometime and eventually drop. The modem passthrough calls are generated with V.90 client modems.

Workaround: Turn off redundancy.

CSCed22458

Symptom: Connectivity from VISM-PR to RPM-XF fails and calls are stuck.

Conditions: After running 10 cps load (with SS7 signalling) for two days, VISM fails to respond to a ping from the call agent.

Workaround: Configure VISM with two PVCs and two IP addresses: one for control traffic and one for voice traffic.

CSCed24074

Symptom: High bandwidth usage on E1 loopback and ICS disable in AAL2 trunking.

Conditions: All the CIDs on the VISM-PR-8E1 cards that are associated with these physical E1 lines must be deleted to save the bandwidth. When physical loopbacks are placed, these CIDs might not be useful for the trunking applications.

Workaround: None.

CSCee33552

Symptom: Fax calls fail when VISM software is upgraded from 2.1.0.0 to 3.2.0.0.

Conditions: Endpoints are added in one go. For an E1 line 31 endpoints are added at one go.

Workaround: Adding endpoints one by one resolves the issue.

CSCee54848

Symptom: This defect has been observed to have the following symptoms:

1. SMS tones are occasionally reported at times when no SMS tones are present. The consequence may be the loss of the voice channel for a few seconds or possibly permanently.

2. Lack of bearer voice path occurs for approximately 10 seconds when a softswitch is performed.

3. Unexpected upspeeds to G.711 codec in one direction from G.729 codec mid-way through a normal voice call results in poor voice quality.

Conditions: These symptoms occur when SMS tone detection is enabled.

Workaround: None.

CSCee58292

Symptom: VISM 3.2.00 and 3.2.10 releases have intermittent COT test failures. An SS7 COT fail message is seen, or NTFY on the COT tone is not seen.

Conditions: The problem occurs on the VISM card only, not on the VISM-PR card.

Workaround: None.

CSCee92298

Symptom: By default RAS is enable, and timestamp is enable as shown using the following commands:

•dspds0execdiag

•dspexecdiag

•dsplnexecdiag

•dspcodecjtrdelays

Conditions: The default configuration on RAS is enable, and default timestamp is enable.

Workaround: Use any of the following commands to disable RAS:

•cnfexecdiag

•cnflnexecdiag

•cnfds0execdiag

Use the cnfplayouttimestamp command to disable timestamp.

CSCee92429

Symptom: Voice quality issue due to AAL2 packet errors.

Conditions: Configure 200 CIDs from VISM-PR to VISM-PR in AAL2 trunking mode with subcellmux enabled. Make sure no packet errors exist. Delete some CIDs and re-add them on one side of the VISM-PR. Then, observe the AAL2 HEC, AAL2 Invalid OSF and Invalid length errors. Also, observe bad voice quality.

Workaround: None.

Related Documentation

The following documents contains information that may be useful to software Release 3.2 for VISM/VISM-PR:

•Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.2

•Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Command Reference, Release 4

•Cisco MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide, Release 4

•Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 4

Obtaining Documentation

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.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

•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 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

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:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case 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 listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—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.

Priority 2 (P2)—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.

Priority 3 (P3)—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.

Priority 4 (P4)—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. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

•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 online at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•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:

http://www.cisco.com/ipj

•Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

CCSP, the Cisco Square Bridge logo, Cisco Unity, Follow Me Browsing, FormShare, 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 Aironet, ASIST, 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, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, 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, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO 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. (0406R)
Copyright � 2004, Cisco Systems, Inc.
All rights reserved.

Front Card Model Number	Redundancy Support
MGX-VISM-8T1	1:N redundancy (bulk mode support for T1 lines only).
MGX-VISM-8E1	1:N redundancy (bulk mode support for E1 lines only).
MGX-VISM-PR-8T1	1:N redundancy (bulk mode support for T1 lines only).
MGX-VISM-PR-8E1	1:N redundancy (bulk mode support for E1 lines only).

Product	CW2000 Name	Latest Firmware	Minimum Firmware
PXM1	MGX 8850	1.2.21	1.2.20
PXM1E	MGX 8850/MGX 8830	4.0.1.2	3.0.23
PXM45	MGX 8850	4.0.1.2	3.0.23
RPM-PR	RPM-PR	12.2(8)T1	12.2(8)T1
RPM-XF	RPM-XF	12.2(15)T5	12.2(15)T5
SRME	SRM-E	FC-C0 BC-B0	FC-C0 BC-B0
SRM-3T3/C	SRM-C	FC-CA BC-A0	FC-CA BC-A0
AUSM	AUSM	10.2.21	10.2.00
AXSM	AXSM	4.0.12	3.0.23
CWM	CWM	12.0 Patch 2	12.0 Patch 2

Product	CW2000 Name	Latest Firmware	Minimum Firmware
BTS	BTS 10200	4.1 (Q15)	4.1 (Q15)
PGW	PGW 2200	9.3(2)	9.3(2)
CISCO 2421	CISCO 2421	12.3.3	12.3.3
AS5400	AS5400	12.3.5	12.3.5
AS5300	AS5300	12.3.5 with vcware 11.32	12.3.5 with vcware 11.32

Product Name	Software Version	Firmware Image Name	Description
MGX-VISM-SW3200	003.002.000.000	vism-8t1e1-003.002.000.000.fw	This image does not support the CALEA¹ feature.
MGX-VISM-LISW320	003.052.000.000	vism-8t1e1-003.052.000.000.fw²	This image supports the CALEA 1 feature.

Board Pair	Boot Code Image Name	Boot Code Version
MGX-VISM-8T1	vism_8t1e1_VI8_BT_3.2.00.fw	VI8_BT_3.2.00
MGX-VISM-8E1	vism_8t1e1_VI8_BT_3.2.00.fw	VI8_BT_3.2.00
MGX-VISM-PR-8T1	vism_8t1e1_VI8_BT_3.2.00.fw	VI8_BT_3.2.00
MGX-VISM-PR-8E1	vism_8t1e1_VI8_BT_3.2.00.fw	VI8_BT_3.2.00

DDTS Issue	Description
CSCdx94130	VISM loses some DTMF digits when ON time is less than 45ms.
CSCea42208	VISM stuck in boot after switchcc; standby did not take over.
CSCea43230	VISM fail to boot on reset in PXM45 chassis.
CSCea64302	VISM resets while running T.38 VoIP trunking load.
CSCeb05718	VISM locks out trunk after wink failure.
CSCeb32754	Cannot establish calls on some of the endpoints after PXM switchover.
CSCeb59727	Send proper Severity Value in VISM traps.
CSCec52528	Configuration GUI - Cannot configure resource partition for VISM.
CSCin48395	Cannot modify/delete VISM/VISM-PR PVC/hybrid connection after VISM/VISM-PR card is reset.
CSCuk44619	VISM notifies correctly only the first 20 DTMF digits to CA.
CSCuk44700	Cracking noise on G.711a codec on VISM-PR.
CSCdy34426	The cnflnoos state is not maintained after switchover.
CSCdy47135	SNMP cannot write to vismRtpPaylodType.
CSCdy50374	VISM: Cannot create resource partitions for the first time through SNMP.
CSCdy78548	M: conttest needs to support both 1780 and 2010 go tones.
CSCdy89525	VISM missing endpoint domain name in response to AUEP //*.
CSCdz64206	Degradation of voice quality when multiple announcement RQNTs are sent.
CSCdz68518	Failed to set objects in srcpPeerGrpParamTable.
CSCdz72726	Incorrect error description for ds0CasGlareTime configuration.
CSCdz73119	VISM requires RtpConnMode be mandatory for configuration: MIB change.
CSCea02640	RSVP session table shows non-existent sessions.
CSCea05685	Calls get stuck after IP connection from CA is lost.
CSCea24522	Make OAM loop back timer configurable.
CSCea38658	UPGRD: VISM logs FIPC and unknown message for congestion management feature.
CSCea62890	DSP crashes after failed T.38 fax call timeout.
CSCea76010	VISM-PR card only supports 145 endpoints after card upgrade.
CSCea78849	ECAN tail length using cnfecantail is not applied to the endpoints.
CSCea81110	VISM does not duplicate call content for LI using MGCP MDCX.
CSCeb21008	MGX log shows tDspmCot CC-4-IDX_OUT_OF_RANG.
CSCeb33989	Loss of IP connectivity causes backhaul buffer leak.
CSCeb34686	Vism marking endpoints as disconnected when active call agent is present.
CSCeb34708	MGCP response takes too long to get to the call agent.
CSCeb39267	SPINI failure.
CSCeb56424	Deleting DN before deleting domain IPs causes configuration problems.
CSCeb65531	The sarSlotNum always indicates 1.
CSCeb67558	VISM crash playing announcement to TDM side without connection.
CSCeb72094	VISM sends wrong t: value in response to AUEP from BTS.
CSCeb77691	VISM returns 510 error when parse SDP messages from 827.
CSCeb85639	VISM does not send oc to call agent with FGD E911 call.
CSCeb85676	VISM does not handle glare properly with FGD outgoing CAS.
CSCec01686	Missing concealment for lost RTP packets in VoIP.
CSCec08071	VISM does not collect digits if CRCX after RQNT.
CSCec26651	Reading vismDynamicPT MIB crashes VISM card.
CSCin38082	The dspchan o/p of VISM-PR card is not proper.
CSCuk42130	The dspxgcpcon CLI command reports wrong timestamp information.
CSCdz86155	Tone plan file written in DOS format is not parsed.
CSCdw48826	The dspcodectmpls and cnfcodectmpl display for codec supported is not clear.
CSCdz85907	Tone plan with status lostFile cannot be deleted.
CSCea57223	VISM-E1 does not send correct idle pattern.
CSCea60784	Latency improvements for G.711, G.726, and G.Clear in VISM-PR.

DDTS Issue	Description
CSCeb74938	Symptom: End-to-end path verification failures with G.726-40 codec. Conditions: The G.726-40 40 millisecond packetization period is not functioning. Workaround: All other packetization periods for this codec and the other G.726 codecs are working correctly.
CSCeb76617	Symptom: Not able to pass VAD test for G.729ab codec (AAL2 trunking application). Conditions: When the VAD is tested for the G.729ab codec through the VQT box, the test fails. Workaround: VAD starts when the threshold is below -67 db. In the VQT box, the lowest value that can be set is -60 db. So, VAD cannot be tested using that box.
CSCec01946	Symptom: Low PESQLQ scores on G.729ab codecs. Conditions: In VoIP and AAL2 trunking applications, G.729ab codec configuration shows lower PESQ scores than G.729a codec configuration. Workaround: It is recommended that G.729a with generic VAD be utilized in place of G.729ab.
CSCec30727	Symptom: After the upgrading from 3.1.0 to 3.1.2, a couple of DSPs in a VISM-PR E1 card failed. Conditions: After running load for 4 to 5 days, this problem seems to occur. The only difference between 3.1.0 and 3.1.2 is the POS application and Marconi application which are supported in 3.1.2. Workaround: Reset the VISM-PR card.
CSCec54765	Symptom: VISM regenerates incorrect DTMF on-times in VoIP trunking mode. Conditions: When DTMF digits with on-times of less than 50 ms are detected on the near-end VISM, the digits are regenerated with inconsistent on/off times on the far end VISM. Workaround: Ensure DTMF digits being detected have an on-time value greater than 50-60 ms. The recommendation is greater than 60 ms.
CSCec68687	Symptom: Simultaneous ISDN call drops not clearing all the endpoints on VISM. Conditions: This problem happens only when all the established calls drops simultaneously which is a rare situation under normal circumstances. Workaround: Taking the gateway out of service and back in service clears all the ports and makes them available for the new calls.
CSCec79013	Symptom: PXM1 VISM VBR3nrt connections shown in CWM as VBR1nrt. Conditions: PXM1 VISM VBR3nrt connections. Workaround: None.
CSCed10672	Symptom: VISM supports 217 AAL2 SVC calls on VISM-PR-E1 only. Conditions: VISM can do 217 simultaneous AAL2 SVC calls in VISM-PR-E1 card only. Call attempts beyond 217 active calls are rejected in CRCX. Workaround: Configure the call agent to setup no more than 217 simultaneous AAL2 SVC calls on the VISM-PR-E1 card at any given time.
CSCed02188	Symptom: Running a load of 9 cps with CP tones causes DSP failure. Conditions: When using VISM-PR in VoIP switching mode with call progress tone detection enabled, running a load of 9 calls per second can cause the VISM DSP to die. Therefore, the VISM cannot run more than 8 calls per second. Workaround: Disable the call progress tone detection (default).
CSCed15923	Symptom: Terminating VISM attempt downspeed from VBD with Bell103 and V.22Bis modulations. Conditions: In AAL2 Trunking mode, upspeed calls from modem/POS systems will not connect in Bell 103 and V.22bis modulations. Workaround: None for AAL2 trunking mode.
CSCed19772	Symptom: VISM rejects SDP with SPACE as session name (s=). Conditions: VISM parses out white space before processing the s= session name field. Workaround: Request the SDP sender to replace the SPACE character with a DASH (s=-) in SDP.
CSCed21523	Symptom: Redundancy on modem pass call from 5xxx to VISM/VISM-PR fails. Conditions: Modem passthrough calls with redundancy ON from the (5400/5300) to (VISM/VISM-PR) fail. The calls stay on ringing state for sometime and eventually drop. The modem passthrough calls are generated with V.90 client modems. Workaround: Turn off redundancy.
CSCed22458	Symptom: Connectivity from VISM-PR to RPM-XF fails and calls are stuck. Conditions: After running 10 cps load (with SS7 signalling) for two days, VISM fails to respond to a ping from the call agent. Workaround: Configure VISM with two PVCs and two IP addresses: one for control traffic and one for voice traffic.
CSCed24074	Symptom: High bandwidth usage on E1 loopback and ICS disable in AAL2 trunking. Conditions: All the CIDs on the VISM-PR-8E1 cards that are associated with these physical E1 lines must be deleted to save the bandwidth. When physical loopbacks are placed, these CIDs might not be useful for the trunking applications. Workaround: None.
CSCee33552	Symptom: Fax calls fail when VISM software is upgraded from 2.1.0.0 to 3.2.0.0. Conditions: Endpoints are added in one go. For an E1 line 31 endpoints are added at one go. Workaround: Adding endpoints one by one resolves the issue.
CSCee54848	Symptom: This defect has been observed to have the following symptoms: 1. SMS tones are occasionally reported at times when no SMS tones are present. The consequence may be the loss of the voice channel for a few seconds or possibly permanently. 2. Lack of bearer voice path occurs for approximately 10 seconds when a softswitch is performed. 3. Unexpected upspeeds to G.711 codec in one direction from G.729 codec mid-way through a normal voice call results in poor voice quality. Conditions: These symptoms occur when SMS tone detection is enabled. Workaround: None.
CSCee58292	Symptom: VISM 3.2.00 and 3.2.10 releases have intermittent COT test failures. An SS7 COT fail message is seen, or NTFY on the COT tone is not seen. Conditions: The problem occurs on the VISM card only, not on the VISM-PR card. Workaround: None.
CSCee92298	Symptom: By default RAS is enable, and timestamp is enable as shown using the following commands: •dspds0execdiag •dspexecdiag •dsplnexecdiag •dspcodecjtrdelays Conditions: The default configuration on RAS is enable, and default timestamp is enable. Workaround: Use any of the following commands to disable RAS: •cnfexecdiag •cnflnexecdiag •cnfds0execdiag Use the cnfplayouttimestamp command to disable timestamp.
CSCee92429	Symptom: Voice quality issue due to AAL2 packet errors. Conditions: Configure 200 CIDs from VISM-PR to VISM-PR in AAL2 trunking mode with subcellmux enabled. Make sure no packet errors exist. Delete some CIDs and re-add them on one side of the VISM-PR. Then, observe the AAL2 HEC, AAL2 Invalid OSF and Invalid length errors. Also, observe bad voice quality. Workaround: None.

Table Of Contents

Release Notes for Cisco Voice Interworking Service Module Release 3.2

Table of Contents

About Release 3.2

Overview

New Features Introduced in Release 3.2

VISM Management Information Base

VISM Redundancy

VISM Call Rate

Compatibility

Limitations and Restrictions

Upgrade Procedures

Prerequisites

VISM/VISM-PR Upgrades with PXM1

Download VISM/VISM-PR Boot Code and Firmware to PXM1

Upgrade Boot Code with PXM1 Cards

Upgrade VISM/VISM-PR Firmware with PXM1 Card

VISM-PR Upgrades with PXM1E and PXM45

Download VISM-PR Boot Code and Firmware to PXM1E and PXM45

Upgrade Boot Code with PXM1E and PXM45 Cards

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

VISM/VISM-PR Downgrade Procedure

VISM to VISM-PR Hardware Upgrade

Caveats for VISM Release 3.2

Resolved Caveats in Release 3.2

Open Caveats in Release 3.2

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information

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. (0406R)

Copyright � 2004, Cisco Systems, Inc.All rights reserved.

Copyright � 2004, Cisco Systems, Inc.
All rights reserved.