cc/td/doc/product/wanbu/mgx8850
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

1.5.05 Version Release Notes
Cisco MGX 8850 VISM

1.5.05 Version Release Notes
Cisco MGX 8850 VISM

About These Release Notes

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

About the 1.5.05 Release

The 1.5.05 release is a maintenance upgrade of the VISM 1.5.04 release with some minor feature enhancements and a small number of corrected anomalies. This release is compatible with the MGX 8850 release 1.1.24

About the 1.5.04 Release

The 1.5.04 release is a maintenance upgrade of the VISM 1.5.03 release with a small number of Anomalies being corrected. There is also better support for E1 lines. This release is compatible with the MGX 8850 release 1.1.23.

About the 1.5.03 Release

The 1.5.03 release is a maintenance upgrade of the VISM 1.5.02 release with a small number of Anomalies being corrected. This release is compatible with the MGX 8850 release 1.1.23.

About the 1.5.02 Release

The previous release of VISM, known as Release 1.5.01, was part of the general MGX 8850 Release 1.1.22.

VISM releases have now been unbundled from the MGX8850.

This VISM release, known as Release 1.5.02, is, therefore, an independent VISM software release that stands alone and is not part of a general MGX 8850 release. There are, however, compatibility issues regarding which release of VISM can operate with which release of the MGX 8850 and other Cisco products, see the Compatibility section of these release notes for details.

The update procedure included in these release notes should be noted to work around a clrsmcnf problem on slots with VISM cards.

Features

This section lists the features supported in each of the VISM 1.5.x releases.

Features Introduced in Release 1.5.05

Idle channel suppression.

Support for setting the IP precedence bit.

Support for Q.50 CAS signaling variant

Negotiable packetization period.

Features Introduced in Release 1.5.04

E1 Backcard support in AAL2 Trunking Mode.

AAL2 sub-cell multiplexing.

Features Introduced in Release 1.5.03

None

Features Introduced in Release 1.5.02

VISM 1.5.02 includes all the features included with Release 1.5.01 and introduces the following new features:

Features Introduced in Release 1.5.01

The features provided in VISM 1.5.01 are:

Release 1.5.05 VISM Hardware

VISM hardware consists of two versions of a front card, one supporting T1 and one supporting E1.

The following versions of back card are supported by VISM Rel. 1.5.05:

An 8-port T1 version using RJ48 connectors.
An 8-port E1 version using RJ48 connectors.
An 8-port E1 version using SMB connectors.

Each of the above backcards also has a redundant version.

Release 1.5.05 hardware front cards and back cards and their revisions that are supported are as follows:
Front card model # Rev # Back card model # Rev #

Ax-VISM-8T1

B1

AX-RJ48-8T1

A

AX-R-RJ48-8T1

A

AX-VISM-8E1

B1

AX-SMB-8/E1

A

AX-R-SMB-8E1

A

AX-RJ48-8/E1

A

AX-R-RJ48-8E1

A

Note The E1 versions of the above front and back cards are supported only when VISM is operating in VoIP mode.

VISM Hardware not supported on Release 1.5.05

None

Redundancy

Support for 1:N and 1:1 Service Module Redundancy, as indicated in the table below:
Front card model # Redundancy supported

MGX-VISM-8T1

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

MGX-VISM-8E1

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

Support for Bulk Distribution using SRM-3T3B card.

Features not Supported in this Release:

Note Code for the above features may be included in the VISM code image. However, no specific mechanism has been included to prevent the use of these unsupported features. If the user attempts to use these unsupported features, there is no guarantee that the features will operate correctly.

VISM MIB:

The VISM MIB is being provided with the delivery of Release 1.5.05 of the VISM software bundles with the MGX 8850 software on CCOand is located at:

http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml

Under MGX8850, select the release (in this case 1.1.24) and click GO.

When the selected FW *.tar file is downloaded, un tar the file & you will find all the latest MIBs bundled with this release.

The MIB is in standard ASN.1 formand may be compiled with most standards-based MIB compilers. For changes in this MIB from release 1.5.01 please refer to the MIB release notes on CCO.

Notes and Cautions for Release 1.5.05

Do NOT upgrade the VISM backup boot firmware as this may render the VISM card inoperable.

None -All other Notes and Cautions for Release 1.5.02 still apply (see below).

Notes and Cautions for Release 1.5.04

Do NOT upgrade the VISM backup boot firmware as this may render the VISM card inoperable.

None -All other Notes and Cautions for Release 1.5.02 still apply (see below).

Notes and Cautions for Release 1.5.03

Do NOT upgrade the VISM backup boot firmware as this may render the VISM card inoperable.

None - All other Notes and Cautions for Release 1.5.02 still apply (see below).

Notes & Cautions For Release 1.5.02

Do NOT upgrade the VISM backup boot firmware as this may render the VISM card inoperable.

CLI modification and changes:

addln "1" (Assuming line# 1)
cnflnsig "1 1" (Configuring line#1 for CAS signaling type 1)

The addcasvar command can now be executed in any order.
For example, to add wink-start MF variant.
addcasvar "winkmf wink-did-dod-mf.o"
this can be done at any time, irespective of whether you had configured the other cas variants or not.
If a valid filename is not entered, the command will displays and error saying that filename has to be one of the above.

Problems Fixed in Release 1.5.05

AAL2 Mode Anomalies.
Bug ID Description

CSCdr22479

Headline: PSQM high scores with VAC on.

Description: The PSQM threashold was set to be at 2.5 , however, the resulting scores were in the 6.5 range. Post analysis showed that leading edge and trailing edge were missing.

CSCdr26132

Headline: CAC was enabled even when the connection bandwidth was in excess of the allowed bandwidth.

Description: Added connetions (PVC) with a specific PCR, and added CIDS without CAC enabled. Reenabling CAC should fail to enable the CAC on the card because the current bandwidth was in excess of the allowed bandwidth.. Instead of failing to enable CAC, CAC is enabled.

CSCdr26900

Headline: Upspeeded CID is not down speeded when FAX call made

Description: When the FAX call was made with both the end of the connections were in MASTER mode of CAC, one end of CID upspeeded but the other end did not. After the FAX call was disconnected, the upspeeded end of the CID did not return to the original Codec type. Subsequent calls were not able to be made.

Workaround: Configure connection CAC to Slave before making any calls.

VoIP Mode Anomalies
Bug ID Description

CSCdr08976VoIP

Headline:E1 Vism allows calls with depleted bandwidth.

Description:After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls.This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls. Currently it does not.

CSCdr13493VoIP

Headline: Vism E1: Ecan/Vad not disabled during modem call detection

Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.

Problems Fixed in Release 1.5.04

AAL2 Mode Anomalies.
Bug ID Description

CSCdp49340

VoAAL2

Headline: cnfcon does not change the PCR

Description:When the value of the PCR parameter is changed through the cnfcon command, Vism does not change the value in the MIB

CSCdp72954

VoAAL2

Headline: LOS does not cause Vism to switch clock if vism is clocking the shelf

Description: When the VISM line is used to clock the MGX shelf , if the VISM gets a loss of signal on the T1 line, or, if the line from which clock is derived is deleted , the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down ( when a card is reset or if a port is deleted )..

CSCdr16013

VoAAL2

Headline: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx.

Description: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx. On testbed (pbx loop - ie no 4ESS connection), both 3810 & Vism are transmitting ones on ds0s 19 to 24.

VoIP Mode Anomalies
Bug ID Description

CSCdr17034

VoIP

Headline: Unable to detect co2 in transponder mode.

Description:The NTFY message is not forwarded to the CA and cot fails.

Problems Fixed in Release 1.5.03

Bug ID Description

CSCdr16005

VoAAL2

Headline:Manual call upspeeds by itself after static pops

Description:While testing CCS INC to Frame with 20 Hammer calls up, one modem call up and one manual call, the manual call would have a static pop and then upspeed and downspeed. Testing with CNN on one end of the call this was happening about every second. With two people talking, it happened much less offen but still happened.

CSCdr16020

VoAAL2

Headline: Vism sending packets to Cisco 3810 when no voice call is active.

Description:

CSCdr12039

VoAAL2

Headline: Vism bulk stress test call failure

Description:duing test using uising the VCO4k some degradation in tone shaping was detected. the VCO4k flag these calls as failed. No call drops resulted from this condition.

Problems Fixed in Release 1.5.02

Bug ID Description

CSCdp69061

Headline: vism cards reset during 15 cps test

Description:During a 15 cps test, all vism cards reset unexpectedly stopping all traffic.Cause is being investigated.

Workaround: None

CSCdp68582

Headline: Loss of voice quality on PXM to PXM calls

Description: Some voice dropout and clipping experienced during testing on PXM to PXM calls. Cause is being investigated.

Workaround: None.

CSCdp66621

Headline: Slower data rates when modem calls pass through vism cards

Description: When modem calls were passed through VISM, the achieved data rates were lower than expected.

Workaround: Modem support is limited to V.34 in this release

Compatibility Notes

VISM Software Interoperability with MGX 8850 Platform Software


Table 1: Image Configuration Matrix
Product Boot Image Firmware image

PXM1

pxm_bkup_1.1.24.fw

pxm_1.1.24.fw

PXM1-2-T3E3

pxm_bkup_1.1.24.fw

pxm_1.1.24.fw

PXM1-4-155

pxm_bkup_1.1.24.fw

pxm_1.1.24.fw

PXM1-1-622

pxm_bkup_1.1.24.fw

pxm_1.1.24.fw

AX-CESM-8E1

cesm_8t1e1_CE8_BT_1.0.02.fw

cesm_8t1e1_10.0.11.fw

AX-CESM-8T1

cesm_8t1e1_CE8_BT_1.0.02.fw

cesm_8t1e1_10.0.11.fw

MGX-AUSM-8E1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

ausm_8t1e1_10.0.11.fw

MGX-AUSM-8T1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

ausm_8t1e1_10.0.11.fw

MGX-CESM-T3

cesm_t3e3_CE8_BT_1.0.02.fw

cesm_t3e3_10.0.11.fw

MGX-CESM-E3

cesm_t3e3_CE8_BT_1.0.02.fw

cesm_t3e3_10.0.11.fw

AX-FRSM-8E1

frsm_8t1e1_FR8_BT_1.0.02.fw

frsm_8t1e1_10.0.11.fw

AX-FRSM-8E1-C

frsm_8t1e1_FR8_BT_1.0.02.fw

frsm_8t1e1_10.0.11.fw

AX-FRSM-8T1

frsm_8t1e1_FR8_BT_1.0.02.fw

frsm_8t1e1_10.0.11.fw

AX-FRSM-8T1-C

frsm_8t1e1_FR8_BT_1.0.02.fw

frsm_8t1e1_10.0.11.fw

MGX-FRSM-HS2

frsm_vhs_VHS_BT_1.0.02.fw

frsm_vhs_10.0.11.fw

MGX-FRSM-2CT3

frsm_vhs_VHS_BT_1.0.02.fw

frsm_vhs_10.0.11.fw

MGX-FRSM-2T3E3

frsm_vhs_VHS_BT_1.0.02.fw

frsm_vhs_10.0.11.fw

MGX-FRSM-HS1/B

frsm_hs1_HS1_BT_1.0.02.fw

frsm_hs1_10.0.11.fw

MGX-VISM-8T1

vism_8t1e1_VI8_BT_1.0.02.fw

vism_8t1e1_1.5.0_5.fw

MGX-VISM-8E1

vism_8t1e1_VI8_BT_1.0.02.fw

vism_8t1e1_1.5.0_5.fw

MGX-RPM-128M/B

rpm-boot-mz.121-1.T1

rpm-js-mz.121-1.T

    1. VISM 1.5.03 Software Interoperability with other Cisco Products

    Cisco 3810

    MC3810_A2JSV5_MZ.121_1.XA2

    Network Management Software:

    CWM 9.2.08 .SOL.Patch6.tar

    CiscoView:

    CV 4.2 WAN CV 2.09

    Virtual Switch Controller Software

    VSC 7.4(6)

    2. VISM 1.5.01 Software Boot and Runtime Firmware Requirements:
    Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware Latest Firmware Version Minimum Firmware Version

    MGX-VISM-8T1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.01

    vism_8t1e1_VI8_1.5_01fw

    1.5.01

    1.5.01

    MGX-VISM-8E1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.01

    vism_8t1e1_VI8_15_01.fw

    1.5.01

    1.5.01

    3. VISM 1.5.02 Software Boot and Runtime Firmware Requirements:
    Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware Latest Firmware Version Minimum Firmware Version

    MGX-VISM-8T1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_2.fw

    1.5.02

    1.5.02

    MGX-VISM-8E1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.5.02

    vism_8t1e1_1.5.0_2.fw

    1.5.02

    1.5.02

    4. VISM 1.5.03 Software Boot and Runtime Firmware Requirements:
    Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware Latest Firmware Version Minimum Firmware Version

    MGX-VISM-8T1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_2.fw

    1.5.03

    1.5.03

    MGX-VISM-8E1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_2.fw

    1.5.03

    1.5.03

    5. VISM 1.5.04 Software Boot and Runtime Firmware Requirements:
    Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware Latest Firmware Version Minimum Firmware Version

    MGX-VISM-8T1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_4.fw

    1.5.04

    1.5.04

    MGX-VISM-8E1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_4.fw

    1.5.04

    1.5.04

    6. VISM 1.5.05 Software Boot and Runtime Firmware Requirements:
    Board Pair Latest Boot Code Version Minimum Boot Code Version Firmware Latest Firmware Version Minimum Firmware Version

    MGX-VISM-8T1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_5.fw

    1.5.05

    1.5.05

    MGX-VISM-8E1

    vism_8t1e_VI8_BT_1.0.02.fw

    1.0.02

    vism_8t1e1_1.5.0_5.fw

    1.5.05

    1.5.05

Special Installation and Upgrade Requirements

VISM Firmware Download Procedure

Step 1 Download the selected revision of service module firmware into the service module in the selected slot.

      tftp <node_name or IP address> 
bin 
put <backup boot> POPEYE@SM_1_<slot#>.BOOT
quit
tftp <node_name or IP address>
put <FW file> POPEYE@SM_1_0.FW
quit

You cannot do two puts in the same tftp session.


Step 2	 Install bt SM slot version.



Step 3	 Answer Yes to the question the install command will ask.


 VISM Graceful Upgrade to 1.5.05


 VISM 1.5.05 provides a procedure for the graceful upgrade (one in which the existing VISM configuration is preserved throughout the upgrade procedure) from releases 1.5.03 and 1.5.04 .


 Initial Conditions


 The following intitial conditions are required before the graceful upgrade procedure can be started.



 Upgrade Procedure


 In the following procedure:




Step 1	 Logon to the active PXM card (slot 7 or 8).



Step 2	 Execute the PXM install command:


install sm<SM slot#><new-rev>

 


 where:


 SM slot# is the slot number of the VISM 2 card and new-rev is the file name ot the 1.5.05 firmware (vism_8t1e1_1.5.0_5.fw).


 This command causes the standby VISM 2 to reset and come up in the "hold" state, running the new-rev firmware.The active VISM 1 is unaffected by this command. At this point the primary firmware still the old-rev and the secondary firmware is new-rev.



Step 3	 Execute the PXM newrev command:


newrev sm<SM slot#><new-rev> 

 
where:


 SM slot# is the slot number of theVISM 2 and new-rev is the filename of the 1.5.05 firmware.


 This command causes the VISM 2 to become the active VISM running the new-rev firmware. The previously active VISM 1 changes to a "hold" state and is still running the old-rev firmware. The primary and secondary firmware switches with the new-rev becoming the primary firmware.



Step 4	 Execute the PXM commit command:


commit sm<SMslot#><new-rev>

 
where:


 SM slot# is the slot number of the standby VISM 1 and new-rev is the filename of the 1.5.05 firmware.


 This command causes both VISMs to run the new-rev firmware. At first, VISM 2 is the active VISM with VISM 1 remaining in the hold state. After a short time, the cards switch automatically with 
VISM 1 becoming the active card and VISM 2 the standby card.


 The two VISM cards are now back to their original condition exept that both cards are now running the new-rev (1.5.05) firmware.



Step 5	 Logon to the active VISM card and use the display commands (dspendpts, dspcasvar, etc.) to confirm that the configuration has been preserved through the upgrade process.

It is also recommended that a further verification be performed by making some minor modifications to the configuration, checking that the changes have been executed correctly, and then changing the configuration back again.


 VISM Upgrade from 1.5.01 and 1.5.02 to later releases


 VISM Releases 1.5.01 and 1.5.02 do not provide for graceful upgrades, upgrading from these releases requires the old configuration to be cleared. 



 Please follow the procedure below to sucessfully load the new VISM configuration.



Step 1	 With old PXM and VISM images still loaded, delete all:



 on the VISM cards.



Step 2	 Remove VISM cards from the shelf.







Note THIS STEP IS VERY IMPORTANT.





Step 3	 Now do clrsmcnf on all VISM cards.



Step 4	 Upgrade boot code on PXM using normal procedure



Step 5	 TFTP the new PXM firmware image and new VISM firmware image. See "Standard Service Module Download Procedure" below for this step.



Step 6	 resetsys --this will cause the shelf to reset.



Step 7	 Insert VISM cards back into the shelf. This will rebuild the proper databases with the new images.


 


 Standard Service Module Download Procedure


 The following step needs to be followed for service module upgrade. Service module firmware images cannot be downloaded as specific versions in MGX 8850 Release 1.1.22 because only one image can be present on the disk at one instance. Hence the user cannot revert back during the installation process.


 Download the service module firmware to the shelf:


        unix-prompt> tftp shelf.ip.address
        tftp> bin
        tptp>put vism_8t1e1_1.5.03.fw POPEYE@SM_1_0.FW
        Sent 1982672 bytes in 18.3 seconds

 Make sure that the transfer is successful, by looking at the message displayed on the PXM console after the transfer:


        Program length = 1982672
        Calculated checksum = 0xd9779bc6 stored checksum = 0xd9779bc6
        Fw checksum passed

 Repeat for each service module type and for each slot independent firmware.







Note There is no abort command for service module upgrade.




 Known Anomalies for VISM

 
 VISM 1.5.05 Anomalies


 The following is the list of known anomalies in the VISM service module, Release 1.5.05 delivery. Included with each is a brief discussion of the problem.


 VoIP Mode Anomalies 



Bug ID
Description



 CSCdr58602


  Headline: DTMF is not supported for G729 in VoIP.


 For VoIP application, DTMF digit relay fails for G.729a and G.729ab codecs. The failure is determined to be due to the digit being leaked out over bearer while simultaneously being relayed as NSE packet.


 Work around: None. Do not use G.729a, G.729ab for VoIP application.














 AAL2 Mode Anomalies. 



Bug ID
Description



 CSCdr63059


 Headline: DTMF Digits failure during the call


 Problem:When a call originates at VISM A and VISM B tests the speech path using digits transmitted from the terminating end (VISM B), a failure rate of .1% is observed for Digit ON time less than 80 - msecs (OFF time fixed at 60 msec). Failure rate increases as ON time is decreased.


 The failure rate is observed to be independent of DTMF digit relay being turned ON or turned OFF


 Work Around:Use a digit ON time greater than 120 msecs.














 VISM 1.5.04 Anomalies


 The following is the list of known anomalies in the VISM service module, Release 1.5.04 delivery. Included with each is a brief discussion of the problem.


 AAL2 Mode Anomalies. 



Bug ID
Description



 CSCdr22479


 Headline: PSQM high scores with VAC on.


 Description: The PSQM threashold was set to be at 2.5 ,  however, the resulting scores were in the 6.5 range. Post analysis showed that leading edge and trailing edge were missing.




 CSCdr26132


  Headline: CAC was enabled even when the connection bandwidth was in excess of the allowed bandwidth.


 Description: Added connetions (PVC) with a specific PCR, and added CIDS without CAC enabled. Reenabling CAC should fail to enable the CAC on the card because the current bandwidth was in excess of the allowed bandwidth.. Instead of failing to enable CAC, CAC is enabled.




 CSCdr26900


 Headline: Upspeeded CID is not down speeded when FAX call made


 Description: When the FAX call was made with both the end of the connections were in MASTER mode of CAC, one end of CID upspeeded but the other end did not. After the FAX call was disconnected, the upspeeded end of the CID did not return to the original Codec type. Subsequent calls were not able to be made. 


 Workaround: Configure connection CAC to Slave before making any calls.














 VoIP Mode Anomalies 



Bug ID
Description



 CSCdr08976VoIP


  Headline:E1 Vism allows calls with depleted bandwidth.


 Description:After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls.This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls.  Currently it does not.




 CSCdr13493VoIP


 Headline: Vism E1: Ecan/Vad not disabled during modem call detection


 Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.














 VISM 1.5.03 Anomalies


 The following is the list of known anomalies in the VISM service module, Release 1.5.03 delivery. Included with each is a brief discussion of the problem.


 AAL2 Mode Anomalies. 



Bug ID
Description



 CSCdp49340


 VoAAL2


 Headline:  cnfcon does not change the PCR


 Description:When the value of the PCR parameter is changed through the cnfcon command, Vism does not change the value in the MIB




 CSCdp72954


 VoAAL2


 Headline: LOS does not cause Vism to switch clock if vism clocking the shelf


 Description: When the VISM line is used to clock the MGX shelf , if the VISM gets a loss of signal on the T1 line (OR) if the line from which clock is derived is deleted , the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down ( when a card is reset or if a port is deleted )..




 CSCdr16013


 VoAAL2


 Headline: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx.


 Description: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx.  On testbed (pbx loop - ie no 4ESS connection), both 3810 & Vism are transmitting ones on ds0s 19 to 24. 














 VoIP Mode Anomalies 



Bug ID
Description



 CSCdr08976VoIP


  Headline:E1 Vism allows calls with depleted bandwidth.


 Description:After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls.This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls.  Currently it does not.




 CSCdr13493VoIP


 Headline: Vism E1: Ecan/Vad not disabled during modem call detection


 Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.




 CSCdr17034


 VoIP


 Headline: Unable to detect co2 in transponder mode.


 Description:The NTFY message is not forwarded to the CA and cot fails. 














 VISM 1.5.02 Anomalies


 The following is the list of known anomalies in the VISM service module, Release 1.5.02 delivery. Included with each is a brief discussion of the problem.


 AAL2 Mode Anomalies. 



Bug ID
Description



 CSCdp49340


 VoAAL2


 Headline:  cnfcon does not change the PCR


 Description:When the value of the PCR parameter is changed through the cnfcon command, Vism does not change the value in the MIB




 CSCdp72954


 VoAAL2


 Headline: LOS does not cause Vism to switch clock if vism clocking the shelf


 Description: When the VISM line is used to clock the MGX shelf , if the VISM gets a loss of signal on the T1 line (OR) if the line from which clock is derived is deleted , the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down ( when a card is reset or if a port is deleted )..




 CSCdr12039


 VoAAL2


  Headline: Vism bulk stress test call failure


 Description:duing test using uising the VCO4k some degradation in tone shaping was detected. the VCO4k flag these calls as failed. No call drops resulted from this condition.




 CSCdr16013


 VoAAL2


 Headline: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx.


 Description: Vism & 3810 Tx ones(seizures) on last 6 ds0s to pbx.  On testbed (pbx loop - ie no 4ESS connection), both 3810 & Vism are transmitting ones on ds0s 19 to 24. 




 CSCdr16005


 VoAAL2


 Headline:Manual call upspeeds by itself after static pops


 Description:While testing CCS INC to Frame with 20 Hammer calls up, one modem call up and one manual call, the manual call would have a static pop and then upspeed and downspeed.  Testing with CNN on one end of the call this was happening about every second. With two people talking, it happened much less offen but still happened.




 CSCdr16020


 VoAAL2


  Headline: Vism sending packets to Cisco 3810 when no voice call is active.


  Description:














 VoIP Mode Anomalies 



Bug ID
Description



 CSCdr08976VoIP


  Headline:E1 Vism allows calls with depleted bandwidth.


 Description:After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls.This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls.  Currently it does not.




 CSCdr13493VoIP


 Headline: Vism E1: Ecan/Vad not disabled during modem call detection


 Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.




 CSCdr17034


 VoIP


 Headline: Unable to detect co2 in transponder mode.


 Description:The NTFY message is not forwarded to the CA and cot fails. 














 VISM 1.5.01 Anomalies





 



 The following is the list of known anomalies in the VISM service module, Release 1.5.01 delivery. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator. 



Bug ID
Description



 CSCdp69061


 Headline:   vism cards reset during 15 cps test


 Description:During a 15 cps test, all vism cards reset unexpectedly stopping all traffic.Cause is being investigated.


 Workaround: None




 CSCdp68582


 Headline:   Loss of voice quality on PXM to PXM calls.


 Description: Some voice dropout and clipping experienced during testing on PXM to PXM calls. Cause is being investigated.


 Workaround: None.




 CSCdp66621


 Headline:   Slower data rates when modem calls pass through vism cards.


 Description: When modem calls were passed through VISM, the achieved data rates were lower than expected.


 Workaround: Modem support is limited to V.34 in this release.














 VISM 1.0 Anomalies


 The following is the list of known anomalies in the MGX 8850 VISM service module, Release 1.00 delivery. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator. 



Bug ID
Description



 CSCdp20174


 Symptom:


 VISM does not recognize LOS


 Description: 


 If T1 cables are disconnected from the VISM card, or the connected channel bank is powered off, the VISM card does not detect LOS.  The card still acts like the line is connected.  Reported by ATT Piscataway, MR:000233, Jan Sussman










 CSCdp21467


 Symptom:


 VISM ignores echo setting


 Description: 


 When sending SGCP messages that tell the VISM to turn on echo cancellation, the actual endpoints setup do not have ecan turned on.


 WorkAround:


 The work around for this issue in VISM 1.0 is to use the shellcon command  ccIgnoreLcoEcan. Please note that this change via the use of this command is not persistant. This command needs to be re-executed everytime VISM is reset/re-booted.














  CSCdp32764


 Symptom:


 Undeleted Connections existed on VISM after overnight calls


 Description: 


 We have set up the VISM to originate and terminate on same T1 line,  We ran the overnight calls  and we observed that each endpoint had connection associated with it. VSC was sending DLCX message but VISM was responding with 510 NACK message and reason code was -  CALL/Endpoint Unknown.




















 Obtaining Service and Support

 
 For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis. 







Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services.




 For service and support for a product purchased directly from Cisco, use CCO.


 Cisco Connection On-line

 
 Cisco Connection On-line (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.


 Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.


 CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.


 You can access CCO in the following ways:



 For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.







Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

  










hometocprevnextglossaryfeedbacksearchhelp


Posted: Thu Jul  6 12:22:59 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.