Guest

Cisco MGX 8800 Series Switches

Release Notes for Cisco Voice Interworking Service Module Release 3.1.3.1

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Release Notes for Cisco Voice Interworking Service Module Release 3.1.3.1

Table of Contents

About Release 3.1.3.1

About Release 3.1.3

About Release 3.1(2)

Overview

New Features Introduced in Release 3.1.3.1

Features in Previous Release 3.1.3

Alarm Suppression Feature in Release 3.1.3

Configure AIS Suppression

Configure OAM Loop Count

Display Alarms

Alarms not Suppressed

Upgrade Notes

G.729a Codec with 20 ms

addcid

cnfprofparams

cnfprofelemvoice

dspprofparams

dspaal2profile

E1 CAS Idle Code

Configure the Idle Code

CAS Code Sent When Adding a CID

CAS Code Sent When Deleting a CID

Upgrade Notes

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 VISM/VISM-PR Firmware with PXM1 Card

Boot Code Upgrade Procedure with PXM1 Cards

VISM-PR Upgrades with PXM1E and PXM45

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

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

VISM/VISM-PR Downgrade Procedure

VISM to VISM-PR Hardware Upgrade

Resolved Caveat for Release 3.1.3.1

Caveats for VISM/VISM-PR Release 3.1.3

Resolved Caveats for Release 3.1.3

Open Caveat in Release 3.1.3

Caveats for VISM/VISM-PR Release 3.1(2)

Resolved Caveats in Release 3.1(2)

Open Caveats in Release 3.1(2)

Anomaly Status Changes in Release 3.1(2)

Caveats Resolved in Release 3.1(1)

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

These release notes are part number OL-5350-01 Rev A0, December 30, 2003.

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 VISM Installation and Configuration Guide, which is available on cisco.com.

Table of Contents

About Release 3.1.3.1

The VISM/VISM-PR 3.1.3.1 Release is a patch release of the VISM/VISM-PR 3.1.3 Release and contains no new features. See the "Resolved Caveat for Release 3.1.3.1" section for information on the resolved caveat, CSCed12399.

Note The content of VISM/VISM-PR Release 3.1.3.1 supersedes Release 3.1.3.

About Release 3.1.3

The VISM/VISM-PR 3.1.3 Release is a patch release of the VISM/VISM-PR 3.1.2 Release and contains the following features:

•"Alarm Suppression Feature in Release 3.1.3" section.

•"G.729a Codec with 20 ms" section

•"E1 CAS Idle Code" section

For information on the caveats that are resolved in this release, see the "Resolved Caveats for Release 3.1.3" section.

Note If you have a VISM-E1 card with G.711 or Clear Channel codecs in template 2, and you have added more than 240 endpoints per card, see the "Open Caveat in Release 3.1.3" section for the workaround options.

About Release 3.1(2)

The VISM/VISM-PR 3.1(2) Release is a maintenance release of the VISM/VISM-PR 3.1 Release and contains no new features. This release is a general availability (GA) firmware release for VISM/VISM-PR. See the "Resolved Caveats in Release 3.1(2)" section for information on the caveat resolutions introduced with this release.

Note The content of VISM/VISM-PR Release 3.1(2) supersedes Release 3.1(1) and all previous releases.

Overview

These release notes contain the following sections:

•"New Features Introduced in Release 3.1.3.1" section

•"Features in Previous Release 3.1.3" section

•"VISM Management Information Base" section

•"VISM Redundancy" section

•"VISM Call Rate" section

•"Compatibility" section

•"Limitations and Restrictions" section

•"Upgrade Procedures" section

•"Resolved Caveat for Release 3.1.3.1" section

•"Caveats for VISM/VISM-PR Release 3.1.3" section

•"Caveats for VISM/VISM-PR Release 3.1(2)" section

•"Caveats Resolved in Release 3.1(1)" section

•"Related Documentation" section

•"Obtaining Documentation" section

•"Obtaining Technical Assistance" section

•"Obtaining Additional Publications and Information" section

New Features Introduced in Release 3.1.3.1

None.

Features in Previous Release 3.1.3

VISM/VISM-PR software Release 3.1.3 contains the following new features:

•"Alarm Suppression Feature in Release 3.1.3" section

•"G.729a Codec with 20 ms" section

•"E1 CAS Idle Code" section

Alarm Suppression Feature in Release 3.1.3

The purpose of this feature is to prevent the CPE from dropping calls when a network link failure is temporary.

If the endpoint is in AAL2 trunking mode, the VISM/VISM-PR propagates network alarms to the T1/E1 line that is associated with the network link. The CPE equipment (PBX) receives this alarm and drops the calls.

VISM/VISM-PR processes several alarms. However, for this feature, only the following alarms are suppressed:

•OAM Alarm Indication Signal (AIS)

•OAM Far End Receive Failure (FERF)

•OAM Remote Defect Indication (RDI)

In this release only, these alarms do not propagate onto the T1/E1 lines as line alarms, which cause call drops.

Since this alarm suppression causes network link failures to be ignored, the OAM end-to-end loopback monitoring function must be configured to detect permanent network failures.

Configure AIS Suppression

By default, AIS suppression is disabled. VISM/VISM-PR cards on both ends of the AAL2 trunk need to be loaded with firmware that supports and enables AIS suppression.

To enable AIS suppression, complete the following steps.

Note You can only enable or disable AIS suppression in the AAL2 trunking mode. The other modes do not support this function.

Step 1 Ensure that the VISM/VISM-PR card is in AAL2 trunking mode. 

cvgmgx1a.1.12.VISM8.a > cnfvismmode 2

WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? yes

INFORMATION: The new 'aal2Trunking' mode has 182 CLI commands.

Step 2 To enable AIS suppression, use the cnfaissuppression command. 

mgx.1.12.VISM8.a > cnfaissuppression <enableFlag>

Replace <enableFlag> with 1 to enable AIS suppression. 

mgx.1.12.VISM8.a > cnfaissuppression 1

INFORMATION: Successfully Enabled AIS Suppression.

If you attempt to enable AIS suppression when it is already enabled, the following message displays: 

WARNING: AIS Suppression is already enabled.

Step 3 To show that AIS suppression has been enabled, use the dspaissuppression command. 

mgx.1.12.VISM8.a > dspaissuppression 

AIS Suppression : ENABLED

Step 4 To disable AIS suppression, use the cnfaissuppression command with the value of 2. 

mgx.1.12.VISM8.a > cnfaissuppression 2

INFORMATION: Successfully Disabled AIS Suppression.

Configure OAM Loop Count

Since an OAM end-to-end loopback failure can still cause line alarms, you must configure the OAM loop count to be longer than the expected duration of the temporary network outage due to a reroute.

Note The OAM end-to-end loopback functionality has not been changed.

Step 1 Ensure that the VISM/VISM-PR is in AAL2 trunking mode. 

mgx.1.12.VISM8.a > cnfvismmode <2>

Step 2 To check the OAM loop count, enter the dspoamloopcnt command. 

mgx.1.12.VISM8.a > dspoamloopcnt

The loop count is displayed with the default value of 5 seconds. 

OAM Loopback Cell Timeout Count:       5

Step 3 To configure the OAM loop count, enter the cnfoamloopcnt command. 

mgx.1.12.VISM8.a > cnfoamloopcnt <count>

Replace <count> with the number of seconds in the range 5 to 60.

Display Alarms

With this feature, VISM/VISM-PR discovers network outages via OAM end-to-end loopback failures. Lost OAM loopback cells can be monitored by using the following command:

dspconcnt <LCN>

The following example shows the output: 

mgx.1.12.VISM8.a > dspconcnt 131

ChanNum:                   131

Chan State:                alarm

Chan XMT ATM State:        Sending FERF OAM

Chan RCV ATM State:        Receiving AIS OAM

Chan Status Bit Map:                0x2

OAM Lpb Lost Cells:                 20

AAL2 HEC Errors:                    2

AAL2 CRC Errors:                    0

AAL2 Invalid OSF Cells:             1

AAL2 Invalid Parity Cells:          0

AAL2 CPS Packet Xmt:                118467937

AAL2 CPS Packet Rcv:                116227849

AAL2 Invalid CID CPS:               0

AAL2 Invalid UUI CPS:               0

AAL2 Invalid Len. CPS:              0

AAL5 Invalid CPI:                   0

AAL5 oversized SDU PDU:             0

AAL5 Invalid Len. PDU:              0

AAL5 PDU CRC32 Errors:              0

AAL5 Reassembly Timer expired PDU:  0

OAM AIS and FERF cells that are transmitted and received are accounted for via counters. With this feature, an alarm is not generated on the line.

The following examples show alarms after an OC-3 failure. AIS alarm cells are received, and FERF cells are transmitted in response.

•Use the dspsarcnt <LCN> command to show the number of AIS, FERF, OAM end-to-end loopback, and total cells that are received and transmitted. 

mgx.1.12.VISM8.a > dspsarcnt 131


                          SarShelfNum:         1

                          SarSlotNum:          5

                          SarChanNum:          131

                                Tx                      Rx

                          ---------------       ---------------

  Total Cells:            406656                333840

  Total CellsCLP:         0                     0

  Total CellsAIS:         0                     13

  Total CellsFERF:        12                    0

  Total CellsEnd2EndLpBk: 85                    69

  Total CellsSegmentLpBk: 0                     0

  RcvCellsDiscOAM:                              0

•Use the dspalm -ds1 <LineNum> command to show the line alarm state with the AIS suppression feature. The LineAlarmState does not show any alarms. With the alarm suppression feature, no alarms are generated on the line in response to the OAM AIS alarm received. 

mgx.1.12.VISM8.a > dspalm -ds1 1

LineNum:                   1

LineAlarmState:            No Alarms

LineStatisticalAlarmState: Alarm(s) On --

                                SEFS24hrAlarm

                                UAS24hrAlarm

Note Once the configured number of OAM end-to-end loopback cells are lost, the dspalm status shows that the lines are in alarm.

Without the AIS suppression feature, the LineAlarmState shows XmtAIS and RcvRAI. 

mgx.1.12.VISM8.a > dspalm -ds1 1


LineNum:                   1

LineAlarmState:            Alarm(s) On --

                                RcvRAI

                                XmtAIS

LineStatisticalAlarmState: Alarm(s) On --

                                SEFS24hrAlarm

                                UAS15minAlarm

                                UAS24hrAlarm

Alarms not Suppressed

Alarm suppression does not affect the following AAL2 type 3 packet alarms (transmitted and received per CID):

•external AIS

•external RDI

•connection AIS

•connection RDI

These alarms allow the line alarms that are received due to a T1/E1 failure to be propagated to the remote end.

Upgrade Notes

The default for AIS suppression in Release 3.1.3 is disabled. If you upgrade to Release 3.1.3 from a release with AIS suppression enabled, you must re-enable AIS suppression.

After the upgrade, enable AIS suppression using the cnfaissuppression command.

G.729a Codec with 20 ms

In Release 3.1.3, VISM/VISM-PR cards contain a new custom profile to support G.729a with
20 milliseconds (ms) packetization period.

The new Custom profile type, 210, supports upspeeding from G.729a with 20 ms packetization period to other codecs, for example, G.711 mu/A law.

G.729a with 20 ms packetization period is supported for AAL2 trunking and applies to templates 1, 3, and 4 on the VISM/VISM-PR cards.

The following commands have been modified to support this feature:

•addcid

•cnfprofparams

•cnfprofelemvoice

•cnfprofelemvbd

•dspprofparams

•dspaal2profile

addcid

To add an AAL2 channel identifier (CID) on a VISM/VISM-PR card, use the addcid command.

addcid <endpt_num> <LCN> <cid_num> <codec_type> <profile_type> <profile_number> <voice_activity_detection> <vad_init_timer> <echo_cancellation> <triple_redundancy_protection> <cas_signaling_transport> <dtmf_tone_transport_as_AAL2> <ICS_enable> <pktPeriod>

Syntax Description

endpt_num

Endpoint number which is to be related to the LCN/CID pair being added.

•For template number 1:

–For VISM, from 1 to 145

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 2:

–For VISM T1, from 1 to 192

–For VISM E1, from 1 to 248

•For template number 3:

–For VISM, from 1 to 120

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 4:

–For VISM, from 1 to 64

–For VISM-PR, from 1 to 144

LCN

Logical channel number (LCN) of the LCN/CID pair. Range is 131-510.

cid_num

Channel identification number of the LCN/CID pair. Range is 8-255.

codec_type

Type of coding/decoding to be performed on the data stream.

•1 = G.711u

•2 = G.711a

•3 = G.726-32k

•4 = G.729a

•5 = G.729ab

•6 = Clear channel (VAD must be off)

•7 = G.726-16k

•8 = G.726-24k

•9 = G.726-40k

•11 = G.723.1-H

•12 = G.723.1a-H

•13 = G.723.1-L

•14 = G.723.1a-L

profile_type

(Optional) Profile type to be used for the CID.

•1 = International Telecommunication Union (ITU) I.366.2

•3 = Custom

Note If profile_type and profile_number argument values are both 1, you cannot turn VAD on.

profile_number

(Optional) Number of the profile.

•1 = ITU profile

•2 = ITU profile

•3 = ITU profile

•7 = ITU profile

•8 = ITU profile

•12 = ITU profile

•100 = Custom profile

•101 = Custom profile

•110 = Custom profile

•200 = Custom profile

•210 = Custom profile

|voice_activity_detection|

(Optional) Value to enable or disable voice activity detection (VAD).

•1 = On

•2 = Off (Default)

Note If profile_type and profile_number argument values are both 1, you cannot turn VAD on.

|vad_init_timer|

(Optional) VAD initial (holdover) timer. Range is 250-65535 ms. Default is 250 ms.

|echo_cancellation|

(Optional) Value to enable or disable echo cancellation (ECAN).

•1 = On (Default)

•2 = Off

|triple_redundancy_protection|

(Optional) Value to enable or disable triple redundancy protection for type 3 packets.

•1 = On

•2 = Off

Note If you select 1 for this argument value, either the cas_signaling_transport or dtmf_tone_transport_as_AAL2 argument value must be set to 1 (on).

|cas_signaling_transport|

(Optional) Value to enable or disable channel associated signaling (CAS) transport as AAL2 type3 packets.

•1 = On (Default)

•2 = Off

This parameter does not affect any inbound signaling.

|dtmf_tone_transport_as_AAL2|

(Optional) Value to enable or disable DTMF tone transport as AAL2 type 3 packets. It can be one of the following values:

•1 = On (Default)

•2 = Off

Note The dtmf_tone_transport_as_AAL2 argument value must be set to 1 (on) when the codec_type is configured for codecs other than G.711 and G.726.

|ICS_enable|

(Optional) Value to enable or disable idle code suppression (ICS) for the CID.

•1 = Enable

•2 = Disable

|pktPeriod|

(Optional) Packetization period (defined in milliseconds). This parameter applies only to G.729a compression.

•10 ms

•20 ms

•30 ms

Note The pktPeriod argument applies only to G.729a compression (codec_type argument value = 4). If you have selected any other compression value, ignore this argument.


Command Modes

AAL2 trunking

Usage Guidelines

This command establishes a relationship between an endpoint and an LCN/CID pair. The endpoint is bound to a DS0, and the CID binds a DS0 to a logical channel—ensuring an endpoint-to-endpoint trunk. The following conditions must be met before you use this command:

•A previously added endpoint must exist.

•PVC must be of bearer type and provisioned using the addcon command.

•The current DSP template must contain the desired codec type.

This command can be used on an endpoint that has no associated CAS variant. However, if a CAS variant is specified for the endpoint, it must be Q.50 variant (file q50.o)—the only CAS variant supported by this command.

The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.

The following example creates a CID for endpoint 10, LCN 140, with a CID number of 10. The codec type is 4 (G.729a), profile type is 3 (Custom), profile number is 210 (Custom), VAD is 1 (on), VAD holdover is 300 milliseconds, echo cancelling is 1 (on), type 3 redundancy is 1 (on), CAS transport is 1 (on), DTMF transport is 1 (on), idle code suppression is 1 (on) and the packet period is 20 milliseconds. 

mgx.1.14.VISM8.a > addcid 10 140 10 4 3 210 1 300 1 1 1 1 1 20

cnfprofparams

To configure a profile preference, use the cnfprofparams command.

cnfprofparams <profileType> <profileNumber> <profilePreference>

Syntax Description

profileType

Profile type to be used for the CID.

•1 = International Telecommunication Union (ITU) I.366.2

•3 = Custom

profileNumber

Number of the profile.

•1 = ITU profile

•2 = ITU profile

•3 = ITU profile

•7 = ITU profile

•8 = ITU profile

•12 = ITU profile

•100 = Custom profile

•101 = Custom profile

•110 = Custom profile

•200 = Custom profile

•210 = Custom profile

profilePreference

Profile preference. It can be one of the following values:

•0 = No preference; exclude the profile from xGCP profile negotiation

•1-11 where 1 is the highest preference (default) and 11 is the lowest preference


Command Modes

Switched AAL2 PVC and AAL2 trunking

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example shows that the Custom profile type, profile number 210, is configured with the midrange preference level of 4: 

mgx.1.14.VISM8.a > cnfprofparams 3 210 4

cnfprofelemvoice

To configure the profile voice element, use the cnfprofelemvoice command.

cnfprofelemvoice <profileType> <profileNumber> <voice_codec_type> <pktPeriod > <sid>

Syntax Description

profileType

Profile type to be used for the CID.

•1 = International Telecommunication Union (ITU) I.366.2

•3 = Custom

profileNumber

Number of the profile.

•1 = ITU profile

•2 = ITU profile

•3 = ITU profile

•7 = ITU profile

•8 = ITU profile

•12 = ITU profile

•100 = Custom profile

•101 = Custom profile

•110 = Custom profile

•200 = Custom profile

•210 = Custom profile

voice_codec_type

Type of coding/decoding to be performed on the data stream.

•1 = G.711u

•2 = G.711a

•3 = G.726-32k

•4 = G.729a

•5 = G.729ab

•6 = Clear channel (VAD must be off)

•7 = G.726-16k

•8 = G.726-24k

•9 = G.726-40k

•11 = G.723.1-H

•12 = G.723.1a-H

•13 = G.723.1-L

•14 = G.723.1a-L

pktPeriod

Voice packetization period (defined in milliseconds).

•5

•10

•20

•30

•40

sid

Silence insertion descriptor (SID).

•1 = VAD off

•2 = VAD on

•3= SID generic

•4 = SID 729

•5 = SID 723


Command Modes

Switched AAL2 PVC and AAL2 trunking

Usage Guidelines

Use the dspaal2profile command to identify the valid combinations of codec type, packetization period, and SID.

The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.

Examples

The following example shows that the Custom profile type, profile number 210, is configured with the G.729a codec type (4), a packetization period of 20 ms, and VAD enabled: 

mgx.1.14.VISM8.a > cnfprofelemvoice 3 210 4 20 2

dspprofparams

To display the profile elements and the preference for all profiles, use the dspprofparams command.

dspprofparams

Syntax Description

This command has no arguments or keywords.

Command Modes

Switched AAL2 PVC and AAL2 trunking

Usage Guidelines

When you execute this command, the display includes the default voice and voiceband data profile element which correspond to each supported profile.

Examples

The following example shows the profile elements and preferences for all profiles, including the results of the cnfprofparams and cnfprofelemvoice commands. 


mgx.1.14.VISM8.a > dspprofparams


      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 1

      Profile Preference                    : 4

      Voice Profile Codec                   : G.711u    

      Voice Profile Packetization-period(ms): five  

      Voice Profile SID                     : VAD on   

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five  

      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 2

      Profile Preference                    : 3

      Voice Profile Codec                   : G.711u    

      Voice Profile Packetization-period(ms): five  

      Voice Profile SID                     : sidGenric

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five 


Type <CR> to continue, Q<CR> to stop: 


- - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 3

      Profile Preference                    : 1

      Voice Profile Codec                   : G.726-32K 

      Voice Profile Packetization-period(ms): five  

      Voice Profile SID                     : sidGenric

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five  

      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 7

      Profile Preference                    : 2

      Voice Profile Codec                   : G.729ab   

      Voice Profile Packetization-period(ms): ten   

      Voice Profile SID                     : sid729   

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five 


Type <CR> to continue, Q<CR> to stop: 


      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 8

      Profile Preference                    : 5

      Voice Profile Codec                   : G.729ab   

      Voice Profile Packetization-period(ms): ten   

      Voice Profile SID                     : sid729   

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five  

      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : ITU

      Profile Number                        : 12

      Profile Preference                    : 10

      Voice Profile Codec                   : G.723.1a-H

      Voice Profile Packetization-period(ms): thirty

      Voice Profile SID                     : sid723   

      VBD Profile Codec                     : G.723.1-H 

      VBD Profile Packetization-period (ms) : thirty


Type <CR> to continue, Q<CR> to stop: 


      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : Custom

      Profile Number                        : 100

      Profile Preference                    : 6

      Voice Profile Codec                   : G.726-32K 

      Voice Profile Packetization-period(ms): ten   

      Voice Profile SID                     : sidGenric

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five  

      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : Custom

      Profile Number                        : 101

      Profile Preference                    : 7

      Voice Profile Codec                   : G.729ab   

      Voice Profile Packetization-period(ms): ten   

      Voice Profile SID                     : sid729   

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five 


Type <CR> to continue, Q<CR> to stop: 


      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : Custom

      Profile Number                        : 110

      Profile Preference                    : 8

      Voice Profile Codec                   : G.729ab   

      Voice Profile Packetization-period(ms): thirty

      Voice Profile SID                     : sid729   

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five  

      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : Custom

      Profile Number                        : 200

      Profile Preference                    : 9

      Voice Profile Codec                   : clr chan  

      Voice Profile Packetization-period(ms): five  

      Voice Profile SID                     : VAD off  

      VBD Profile Codec                     : clr chan 

      VBD Profile Packetization-period (ms) : five 


Type <CR> to continue, Q<CR> to stop: 


      - - - - - - - - - - - - - - - - - - - - - -

      Profile Type                          : Custom

      Profile Number                        : 210

      Profile Preference                    : 4

      Voice Profile Codec                   : G.729a    

      Voice Profile Packetization-period(ms): twenty

      Voice Profile SID                     : VAD off  

      VBD Profile Codec                     : G.711u   

      VBD Profile Packetization-period (ms) : five

dspaal2profile

To display data about a specified AAL2 profile type and profile number, use the dspaal2profile command.

dspaal2profile <profileType> <profileNumber>

Syntax Description

profileType

Profile type to be used for the CID.

•1 = International Telecommunication Union (ITU) I.366.2

•3 = Custom

profileNumber

Number of the profile.

•1 = ITU profile

•2 = ITU profile

•3 = ITU profile

•7 = ITU profile

•8 = ITU profile

•12 = ITU profile

•100 = Custom profile

•101 = Custom profile

•110 = Custom profile

•200 = Custom profile

•210 = Custom profile


Command Modes

AAL2 trunking

Usage Guidelines

The AAL2 profiles correspond to the profile types ITU and ATMF as defined in the ITU-T I.366.2 and ATM forum AF-VTOA-0113 standards respectively.

Examples

The following example shows that the data for AAL2 profile type 3 and profile number 210 is displayed: 

mgx.1.14.VISM8.a > dspaal2profile 3 210


   UUI      Packet                          Packet  Seq. No.

Codepoint   Length                           Time   Interval

  Range    (octets)  Codec       SID     M   (ms)     (ms)  

   0-7        40     PCMU        No SID  1    5        5    

   0-7        40     PCMA        No SID  1    5        5    

   8-15       40     G726-32     No SID  2    10       5    

   8-15       20     G729ab      SID729  2    20       5    

   8-15       20     G729a       No SID  2    20       5

E1 CAS Idle Code

In Release 3.1.3 when VISM/VISM-PR is configured for E1 channel associated signaling (CAS) transport in AAL2 trunking mode, the default idle signaling pattern is 13.

Configure the Idle Code

You can change the default idle ABCD CAS code on endpoint basis on the VISM/VISM-PR E1 cards. ABCD refers to the robbed-bit signaling bits that are sent in CAS lines.

Step 1 Log in to your VISM/VISM-PR card.

Step 2 Ensure that you are in the AAL2 trunking mode.

Step 3 To configure the idle CAS code as 4, enter the cnfcascode command.

Note The cnfcascode command can be used only on existing endpoints. 

mgx.1.14.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> [endpts_num]

Replace the arguments with the values listed in Table 1.

The following example shows the idle CAS code as 4 on endpoints 1-6. Seized code is not used for AAL2 trunking. 

mgx.1.14.VISM8.a > cnfcascode 1 4 6 5


NOTE:In order for VISM card to use the new Idle Code :

 Either Reset the Card OR re-add the Cids

Table 1 Parameters for the cnfcascode Command 

Parameter
Description

endpt_num

Endpoint number which is to be configured with CAS idle code and seized code. Value is one of the following ranges:

•For template number 1:

–For VISM, from 1 to 145

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 2:

–For VISM T1, from 1 to 192

–For VISM E1, from 1 to 248

•For template number 3:

–For VISM, from 1 to 120

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 4:

–For VISM-PR, from 1 to 144

Note If the second (optional) endpts_num argument is specified, this argument value is the first endpoint in a consecutive number of endpoints.

idle_code

Four-bit idle code. Value can be in the range from 0-15. This argument represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively, with bit 3 the most significant.

seized_code

Four-bit seized code. Value can be in the range from 0-15. This arguments represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively, with bit 3 the most significant.

[endpts_num]

(Optional) Total consecutive range of endpoints on which the cnfcascode command is applied. Value is from one of the following ranges:

•For template number 1:

–For VISM, from 1 to 145

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 2:

–For VISM T1, from 1 to 192

–For VISM E1, from 1 to 248

•For template number 3:

–For VISM, from 1 to 120

–For VISM-PR T1, from 1 to 192

–For VISM-PR E1, from 1 to 248

•For template number 4:

–For VISM-PR, from 1 to 144


Step 4 To show the configured idle code on endpoint 1, enter the dspds0cascode command. 

mgx.1.14.VISM8.a > dspds0cascode <line_number> <ds0_number>

Replace the line_number argument with a value 1-8 and ds0_number with a value 1-24 for T1 lines or 1-31 for E1 lines.

The following example show the idle CAS code on endpoint 1 that you configured in Step 3. 

mgx.1.14.VISM8.a > dspds0cascode 1 1


Ds1 line number: 								1

ds0 number: 								1

Ds0 If Index: 								1

Ds0 Idle Code : 								4

Ds0 Seized Code: 								6

Step 5 To view the status of all the DS0s on a line, enter the dsplndsx0s command. 

mgx.1.14.VISM8.a > dsplndsx0s <line_number>

The following example shows the idle code you configured using the cnfcascode command on line 2. 

mgx.1.14.VISM8.a > dsplndsx0s 1


Ds0 If  Robbed Bit  Idle  Seized  EndPt    If            Variant   Cadence   Cadence

Index   Signaling   Code   Code    Num    Type           Name      OnTime  OffTime

------  ----------  ----- ------- ------ --------------  --------- --------  --------

  1       False      4      6       1    bearer                       75     75

  2       False      4      6       2    bearer                       75     75

  3       False      4      6       3    bearer                       75     75

  4       False      4      6       4    bearer                       75     75

  5       False      4      6       5    bearer                       75     75

  6       False      4      6       6    bearer                       75     75

  7       False      2      4       7    bearer                       75     75

  8       False      2      4       8    bearer                       75     75

  9       False      2      4       9    bearer                       75     75

 10       False      2      4      10    bearer                       75     75

 11       False     13     15      -1    -                            75     75

 12       False     13     15      -1    -                            75     75

 13       False     13     15      -1    -                            75     75

 14       False     13     15      -1    -                            75     75

 15       False     13     15      -1    -                            75     75

 16       False     13     15      -1    -                            75     75

 17       False     13     15      -1    -                            75     75

 18       False     13     15      -1    -                            75     75

 19       False     13     15      -1    -                            75     75

 20       False     13     15      -1    -                            75     75

 21       False     13     15      -1    -                            75     75

 22       False     13     15      -1    -                            75     75

 23       False     13     15      -1    -                            75     75

 24       False     13     15      -1    -                            75     75

 25       False     13     15      -1    -                            75     75

 26       False     13     15      -1    -                            75     75

 27       False     13     15      -1    -                            75     75

 28       False     13     15      -1    -                            75     75

 29       False     13     15      -1    -                            75     75

 30       False     13     15      -1    -                            75     75

 31       False     13     15      -1    -                            75     75

Step 6 To update the new CAS code on previously existing endpoints, reset the VISM/VISM-PR card.

CAS Code Sent When Adding a CID

If the local end CID is added first, the VISM/VISM-PR continues to provide the configured idle code on the DS0 (TDM interface) until the remote AAL2 CID is added and starts sending the CAS signaling traffic over the ATM network.

If the local end CID is added after the remote end CID is added, the VISM/VISM-PR is already receiving a CAS signaling pattern from the remote AAL2 CID. The VISM/VISM-PR begins propagating the received signaling code on the line side (TDM interface).

Note It is assumed the AAL2 CIDs that are added have CAS transport enabled on them. If CAS transport is disabled, the CAS signaling bits do not propagate end-to-end.

CAS Code Sent When Deleting a CID

If the remote end AAL2 CID is deleted first, the VISM/VISM-PR continues to send the last received CAS signaling pattern from the remote CID to the line side (TDM interface).

If the local end CID is deleted first, the VISM/VISM-PR sends the idle code (configured on this endpoint) to the line side (TDM interface).

Upgrade Notes

Before upgrading from 3.1.x to 3.1.3, configure the CAS code on the endpoints on the previous release. This step ensures that the configured idle code is carried over to the upgraded VISM/VISM-PR and used on all the endpoints.

If you install a new VISM/VISM-PR card with Release 3.1.3, and you want to configure a new CAS code on some endpoints, the new idle code is used on the CIDs which are added after configuring the CAS code.

Note VISM/VISM-PR Release 3.1.3 supports the same elements as 3.1(2).

VISM Management Information Base

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

VISM Redundancy

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

Table 2 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.1.3.1 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 3.

Table 3 VISM/VISM-PR Software Interoperability 

Product
CW2000 Name
Latest Firmware
Min. Firmware

PXM1

MGX 8850

1.2.21

1.2.10

PXM1E

MGX 8850/MGX 8830

3.0.23

3.0.10

PXM45

MGX 8850

3.0.23

3.0.10

SES

SES

3.0.23

3.0.10

BPX

BPX

9.4.00

9.3.42

RPM-PR

RPM-PR

12.2.15-T2

12.2.13-T4

RPM-XF

RPM-XF

12.2.15-T2

12.2.15

SRM-E

SRM-E

—

—

SRM-C

SRM-C

—

—

AUSM

AUSM

10.2.20

10.2.10

AXSM

AXSM

3.0.23

3.0.10

CWM

CWM

12.0.00

12.0.00


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

Table 4 VISM/VISM-PR Compatibility with PXM Cards

 
PXM1
PXM1E
PXM45 (A/B/C)

VISM

Yes

No

No

VISM-PR

Yes

Yes

Yes


VISM/VISM-PR software interoperability with other Cisco products is described in Table 5.

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

Cisco 3810

12.2(8)T1

AS5400

122-10.7

PGW Software

9.3.2


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

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

Product Name
Software Image
Firmware
Description

MGX-VISM-SW3130

003.001.003.001.FW

vism-8t1e1-003.001.003.001.fw

This image does not support the CALEA1 feature.

MGX-VISM-LISW3130

003.051.003.001.FW

vism-8t1e1-003.051.003.001.fw2

This image supports the CALEA1 feature.

1 CALEA = Commission on Accreditation for Law Enforcement Agencies.

2 The CALEA implementation supports the CALEA law intercept confirmation interface.S


Table 7 describes the software boot code and run-time firmware requirements for VISM/VISM-PR Release 3.1.3.1.

Table 7 VISM/VISM-PR 3.1.3.1 Software Boot and Run-time Firmware Requirements 

Board Pair
Boot Code Version

MGX-VISM-8T1

vism_8t1e1_VI8_BT_3.1.01.fw

MGX-VISM-8E1

vism_8t1e1_VI8_BT_3.1.01.fw

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.1.01.fw

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.1.01.fw


Note Loading this release of the backup bootcode is required for existing VISM/VISM-PR cards not using this new release.

Limitations and Restrictions

Note Release 3.1.3.1 does not contain any new limitations or restrictions. The same limitations and restrictions in 3.1(3) apply to this release.

The following limitations and restrictions are valid for software Release 3.1.3.1 for VISM/VISM-PR:

•Software Release 3.1.3.1 for VISM/VISM-PR requires you to use 64 Mb VISM cards or VISM-PR cards exclusively.

•Cisco recommends that you use the cnfcodecjtrdelay command to configure the jitter-delay argument to 20 ms when using DSP firmware versions 3.4 and 3.6.

•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, you must disable policing.

•For improved voice quality, Cisco recommends that you use G.729a codec instead of the G.729ab codec. If VAD is required, use the generic VAD algorithm.

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

•AAL1 switching and Switched AAL2 SVC modes (7 and 9) are not recommended because during a redundancy switchover all active calls are dropped.

Upgrade Procedures

This section describes the following upgrade procedures:

•"Prerequisites" section

•"VISM/VISM-PR Upgrades with PXM1" section

•"VISM-PR Upgrades with PXM1E and PXM45" section

•"VISM/VISM-PR Downgrade Procedure" section

•"VISM to VISM-PR Hardware Upgrade" section

VISM/VISM-PR Release 3.1.3.1 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.1.3.1

•From VISM 2.1 to VISM 3.1.3.1

•From VISM 2.2 to VISM 3.1.3.1

•From VISM 3.0 to VISM 3.1.3.1

•From VISM 3.1(0) to VISM 3.1.3.1

•From VISM 3.1(1) to VISM 3.1.3.1

•From VISM 3.1(2) to VISM 3.1.3.1

•From VISM 3.1(3) to VISM 3.1.3.1

Caution Installing VISM software updates from VISM Release 2.2 with CALEA to VISM Release 3.1.3.1 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/VISM-PR cards are running at least Release 2.0.

•Download software Release 3.1.3.1 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 bootcode 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 4c. To upgrade an individual VISM card, proceed to Step 4d.

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 VISM/VISM-PR Firmware with PXM1 Card

Software Release 3.1.3.1 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_BT_3.1.00.fw.

The following versions of VISM software Release 3.1.3.1 are available:

•003.001.003.001—without CALEA

•003.051.003.001—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.1.3.1.

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

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

savesmcnf <SM slot#>

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

Step 3 Execute the PXM install command:

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

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the file name of the new firmware (for example, vism_8t1e1_003.001.003.001.fw).

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 4 Execute the PXM newrev command:

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

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename of the new firmware.

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

Step 5 Execute the PXM commit command:

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

where:

SM slot# is the slot number of the primary VISM or VISM-PR card and new-rev is the filename 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 6 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 4 and Step 5 for each VISM card in the redundancy group.

It is also recommended that you 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 3.

Boot Code Upgrade Procedure 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 Telnet to MGX shelf and cc to the VISM/VISM-PR card.

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

Step 2 Access the server where the VISM/VISM-PR boot code resides and TFTP the VISM/VISM-PR boot code to the VISM/VISM-PR card:

a. Type tftp <IP address of the MGX shelf>

b. Type bin at the tftp prompt.

Caution Ensure that you perform Step 2b. If you to not perform Step 2b., the boot code is corrupted and not recoverable.

c. Type install [bt] [sm <slot>] <version> at the PXM prompt.

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 For the latest boot to take effect, use the resetcd command for VISM/VISM-PR from the PXM card prompt.

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

Note Step 4 is optional.

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

put image-version

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

Step 7 To exit the download procedure, enter bye.

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

Ensure that the VISM-PR cards have the minimum boot code version of vism_8t1e1_BT_3.1.00.fw.

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

•003.001.003.001—without CALEA

•003.051.003.001—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.

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

loadrev sm-primary-slot-num new-rev

where sm-primary-slot-num is the slot number of the VISM-PR card in which you want to install the new software; and new-rev is 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.

runrev sm-primary-slot-num new-rev

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.

commitrev sm-primary-slot-num new-rev

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.

Boot Code Upgrade Procedure with PXM1E and PXM45 Cards

The boot code has not changed from VISM Release 3.1(3) to Release 3.1.3.1. Therefore, the procedure in this section is the same as the upgrade procedure for Release 3.1(3).

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 VISM-PR Upgrades with PXM1E and PXM45.

Step 2 Log in to the PXM1E or PXM45 card.

Step 3 Use the burnboot sm-primary-slot-num new-rev command, where sm-primary-slot-num is the slot number of the VISM-PR card you want to upgrade and new-rev is the firmware version number of the new VISM-PR software, to upgrade the VISM-PR boot code.

The VISM-PR card automatically resets and becomes active with the latest boot code image. You have completed the boot code upgrade procedure.

VISM/VISM-PR Downgrade Procedure

Use this procedure to downgrade VISM/VISM-PR software from software Release 3.1.3.1 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.1.3.1 for to Release 3.1, 3.0, 2.2, 2.1, or 2.0:

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

delred <SM slot#>

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

Step 3 Execute the PXM clrsmcnf command:

clrsmcnf <SM slot#>

where:

SM slot# is the slot number of the VISM/VISM-PR card to be downgraded.

The VISM/VISM-PR card resets on executing this command. Wait for the card to become active.

Step 4 Execute the PXM restoresmcnf command:

restoresmcnf -f <filename> -s <SM slot#>

where:

The filename is 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.

The SM slot# is the slot number of the VISM/VISM-PR card to be downgraded.

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

Step 5 Reconfigure 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 insure 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 and repeat the dspcd command to insure 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.

Resolved Caveat for Release 3.1.3.1

Table 8 describes the resolved caveat in Release 3.1.3.1 as of December 23, 2003. Caveats describe unexpected behavior or defects in VISM/VISM-PR software.

Table 8 Resolved Caveat for VISM Release 3.1.3.1 

DDTS Issue
Description

CSCed12399

VISM does not outpulse multiple DTMF tones to TDM side.


Caveats for VISM/VISM-PR Release 3.1.3

This section describes resolved and open software caveats for Release 3.1.3 of VISM/VISM-PR.

Resolved Caveats for Release 3.1.3

Table 9 describes the caveats that have been resolved in VISM/VISM-PR Release 3.1.3.

Table 9 Resolved Caveats for VISM/VISM-PR Release 3.1.3 

DDTS Issue
Description

CSCea64302

VISM resets while running T.38 VoIP trunking load.

CSCeb65531

sarSlotNum always indicates 1.

CSCeb77267

Crackling noise when running load on G.711 VISM template 2.

CSCeb77691

VISM returns 510 error when parsing SDP messages from 827 (MGTS).

CSCec01686

Missing concealment for lost RTP packets in VoIP.

CSCuk44619

VISM notifies correctly only the first 20 DTMF digits to the call agent.

CSCuk44700

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


Open Caveat in Release 3.1.3

Table 10 describes the open caveat in VISM/VISM-PR Release 3.1.3.

Table 10 Open Caveat for VISM Release 3.1.3 

DDTS Issue
Description

CSCec47585

Symptom: VISM-E1 card boots when multiple endpoints are deleted.

Conditions: This condition occurs when you have the following configuration: VISM-E1 card with template 2, G.711 or Clear Channel, and more than 240 endpoints added to the card.

Note This anomaly does not occur on VISM-T1, VISM-PR-T1, or VISM-PR-E1 cards.

Workaround:

1. Upgrading to Release 3.1.3—If the number of endpoints configured on the VISM-E1 exceeds 248, delete enough endpoints to ensure the count does not exceed 240. Proceed with the upgrade to 3.1.3.

2. Currently running Release 3.1.3—If your VISM-E1 cards are configured with more then 240 endpoints, delete enough endpoints to bring the count to 240. Reset the card.

If you currently have fewer endpoints configured on the VISM-E1 card but plan to add more in the future, ensure the total endpoint count does not exceed 240 per card.


Caveats for VISM/VISM-PR Release 3.1(2)

This section describes resolved and open software caveats for Release 3.1(2) of VISM/VISM-PR.

Resolved Caveats in Release 3.1(2)

Table 11 describes the caveats that have been resolved in VISM/VISM-PR Release 3.1(2).

Table 11 Resolved Caveats for VISM/VISM-PR Release 3.1(2) 

DDTS Issue
Description

CSCdy67348

AAL2 SVCs: Path confirmation fails on some endpoints with 248 SVCs.

CSCdx68992

AAL1 SVC: DSP failed to detect tones in AAL1 encapsulation.

CSCdy73727

NY: VISM gets a dummy PXM switchover message, unable to make further SVC calls.

CSCdy57985

VISM requires RtpConnMode be mandatory for configuration.

CSCdz32849

Announcement file on VISM-PR is distorted due to different SSRC.

CSCdz37440

VISM crashes running SPVC load with statistics enabled from CWM.

CSCdz43252

VISM switchover causes entire SPVC network into line alarm.

CSCdz49351

Heavy noise distortion VISM VOIP solution Call Manager.

CSCdz58275

VISM: VISM considers M: connection mode parameter to be mandatory in MDCX.

CSCdz89440

PRI sessions are not switching when Call Agents switch over.

CSCea15910

MGCP on VISM cannot parse SIP messages from 827.

CSCdy19561

VISM rejects call with supported codec (G.723.1-H).

CSCdy73454

No MGCP response with mgciSendUdpPacket failure.

CSCdy82378

NY: RTP trunked connections remain in alarm when PVC goes in/out of alarm.

CSCdz30279

VISM needs to support case insensitivity of DNS and MGCs.

CSCdz64830

Broadcast T.38 Fax relay calls on 40+ endpoints on the VISM fails.

CSCdz65510

T.38 calls fail in VoIP trunking.

CSCdz69373

Voice quality issues with fixed jitter mode on G726-32K.

CSCdz74863

VISM does not resolve domain names after a shelf reset.

CSCdz75592

TI POS fix, reduce POS detection time to 100ms.

CSCdz75653

TI fix, use configurable dual tone detector for Marconi phones.

CSCin12468

The addses command accepts session priority > 4.

CSCdx58768

HI: G.723.1 codecs not displayed properly in dspcodecparams output.

CSCdx80992

PCR > 50000 allowed for vbr-rt AAL2 bearer application for VISM-8T1.

CSCdz27893

VISM 3.1 doesnt notify ORBK when flash is detected on 911 trunks.

CSCdz83314

DSP does not suppress the mid-call dtmf tones on the bearer in SVC.

CSCea03861

AUEP with F: s,e,r,n gets strange string in response

CSCea14620

VISM: MGCP parse error for AS53xx SDP string with T.38 parameters

CSCea24517

COT testing with CRCX M:loopback failed for switched AAL2 PVC mode

CSCea24522

make oam loop back timer configurable

CSCea53197

loud noise heard when line alarm is being cleared

CSCea53238

bad announcement file causes VISM to reboot


Open Caveats in Release 3.1(2)

Table 12 describes the open caveats in VISM/VISM-PR Release 3.1(2).

Table 12 Open Caveats for Software Release 3.1(2) for VISM/VISM-PR 

DDTS Issue
Description

CSCdx94130

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

Conditions: VISM randomly fails to detect some of the digits resulting in call failure.

Workaround: The equipment should generate DTMF digits with ON time greater than or equal to 45ms.

CSCdy60917

Symptom: NY: VISM resets when connection on PXM1 is misconfigured.

Conditions: None.

Workaround: To configure a PXM1 connection, refer to the Cisco MGX 8850 Multiservice Switch Installation and Configuration Guide.

CSCdy82951

Symptom: VISM-PR card reboots when all E1 lines with CIDs goes into alarm.

Conditions: None.

Workaround: None.

CSCdz64206

Symptom: Degradation of voice quality occurs when sending announcement RQNTs on 240 endpoints. Voice quality is good up to 185 endpoints, but quality starts to progressively deteriorate up to 240 endpoints.

Conditions: When more than 145 concurrent announcements exist on VISM and VISM-PR cards, traffic is lost on multiple endpoints. This symptom occurs on MGX 8850 with VISM cards running Release 3.1.0.35-I.

Workaround: Limit concurrent announcements on VISM and VISM-PR cards to 130.

CSCdz65552

Symptom: Running Fax Pass-Thru load over ISDN PRI fails in VoIP Switching mode

Description: On a VISM-T1 in Voip Switching mode, running a fax pass thru call load over ISDN PRI for extended periods of time causes call completion rate to go down.

Workaround: None.

CSCea13662

Symptom: Latency increases when VAD Off is selected from cnfprofelemvoice.

Conditions: None.

Workaround: Disable VAD using the MGCP message.

CSCea42208

Symptom: VISM card stuck in boot after switchcc; standby VISM does not take over.

Conditions: Shelf is moderately loaded with light traffic.

Workaround:

1. Reset the card that is stuck in boot, which makes standby take over.

2. Softswitch to make primary card active.

CSCea45931

Symptom: VISMs do not recover after a power outage on the node.

Conditions: None.

Workaround: Physically remove and reinsert the VISM cards.

CSCea62890

Symptom: DSP crashes after a failed T.38 fax call timeout. After a failed T.38 fax call, the call timeouts. VISM attempts to recover the call by sending the compression DSP idle mode command and voice mode commands.

The voice mode command has 22 (T.38) as the payload type and 0 as the payload size, which makes the compression DSP crash.

Conditions: This symptom occurs when the VISM has already switched to T.38 fax mode, and the T.38 fax has failed.

Workaround: None.

CSCea64244

Symptom: VISM reset due to CTRL-X.

Conditions: User reset by CTRL-X is a generic message that is used when the reset reason is unknown.

Workaround: Unknown.

CSCea64302

Symptom: VISM resets while running T.38 VoIP trunking and VoIP switching load.

Conditions: This problem is associated with running a load of T.38 fax calls over a VISM T1 card configured for PRI D-channel signaling.

Workaround: Use T1 in CAS signaling mode when running more than two spans of T.38 fax calls.

CSCea74389

Symptom: 5ms of VAD delay even when VAD is off and not running.

Conditions: None.

Workaround: None.

CSCea76010

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

After upgrading from a VISM legacy card to a VISM-PR card, you cannot add endpoints beyond 145 if you are using codec template 1.

The VISM-PR card must be reset to add the additional endpoints.

Conditions: This symptom occurs on the MGX 8850 while upgrading from a VISM legacy card to a VISM-PR card running release 3.1.0.59.

Workaround: Reset the VISM-PR card by using the resetcd or softswitch commands from PXM.

CSCea86291

Symptom: AAL2 switched virtual circuit (SVC) active calls are dropping during PXM45 switchover.

Conditions: If voice calls are configured on an MGX utilizing AAL2 SVCs, the voice calls are dropped when a manual or automatic PXM switch-over occurs.

Workaround: None.


Anomaly Status Changes in Release 3.1(2)

The following table lists anomalies that have changed status since in Release 3.1(2). Changed status means that the anomaly went from open to a state other than resolved. The status field states whether the anomaly is closed, junked, duplicated, or unreproducible.

Bug ID
Status

CSCdy88166

Voice clipping with buffer overflow; Closed.

Workaround: If you use AAL2 trunking, it is recommended that you use the cnfcodecjtrdelay "codecType jitter_mode jitter_initdelay" to set the jitter_mode to fixed and the init_delay to 20 ms.


Caveats Resolved in Release 3.1(1)

Table 13 describes the caveats issued against VISM/VISM-PR software that have been resolved in software Release 3.1(1).

Table 13 Resolved Caveats for Software Release 3.1(1) for VISM/VISM-PR 

DDTS Issue
Description

CSCuk38197

VISM replies Line Out Of Service to AUEP after cnflnoos/cnflnis.

CSCdw65362

Announcement file play volume is too high, causes distortion.

CSCdy26382

VISM encapsulates UDPTL for T.38 over RTP

CSCdy36418

CSCdy36418 VISM-PR card must be reset after initial installation into MGX shelf

CSCdy39693

Demotion from GW to Line is not happening

CSCdy46975

vismscalarchange trap not generated with ip address change

CSCdy87408

POS problem, modem calls failing with G729 codec

CSCdy89344

endpts stay active even when gw. is forced oos

CSCdy89423

DLCX always sent to Inactive call agent

CSCdy89462

need a command to display VCCI

CSCdy89474

cnfoamparams / dspoamparams should be accessible in all mode

CSCdy89494

dspmgcgrps and dspdnallips show different status for MGC

CSCdz00374

POS problem, modem calls failing with G729 codec

CSCdz01636

VISM Reboots when Domain Name has a lengthy name

CSCdz06991

E1 CCS NFAS bits not configurable

CSCdz12617

T38 Fax call made on VISM to 5400 causes VISM DSP to crash

CSCdz32964

Dynamic Payload broken due to file merge


Related Documentation

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

•Cisco VISM Installation and Configuration Guide, Release 3.0

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

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

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

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

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, 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, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, 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 U.S. and certain other countries.

All other trademarks mentioned in this document or Web site 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. (0304R)

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