Guest

Cisco MGX 8880 Media Gateways

Release Notes for Cisco Voice Interworking Service Module Release 3.2.11

 Feedback

Table Of Contents

Release Notes for Cisco Voice Interworking Service Module Release 3.2.11

Table of Contents

About Release 3.2.11

About Release 3.2.10

About Release 3.2

Overview

New Features in Release 3.2.10

Configurable TDM Companding Law

Programmable CAS Signaling Bit Mapping

Preferred Routes

E1 Trunk Conditioning

Display All Static Configuration

AIS Propagation Control

Bandwidth Utilization Enhancements

New Features in Release 3.2

VISM Management Information Base

VISM Redundancy

VISM Call Rate

Compatibility

Limitations and Restrictions

Upgrade Procedures

Prerequisites

Check Domain Name Length

Disable DSP RAS and Fixed Timestamp

VISM/VISM-PR Upgrades with PXM1

VISM-PR Upgrades with PXM1E and PXM45

VISM/VISM-PR Downgrade Procedure

VISM to VISM-PR Hardware Upgrade

Caveats in VISM Release 3.2.11

Resolved Caveats in 3.2.11

Open Caveats in Release 3.2.11

Caveats in VISM Release 3.2.10

Resolved Caveats in Release 3.2.10

Open Caveats in Release 3.2.10

Caveats in VISM Release 3.2

Resolved Caveats in Release 3.2

Open Caveats in Release 3.2

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco Voice Interworking Service Module Release 3.2.11


These release notes are part number OL-6273-01 Rev. B0, November 22, 2004.

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

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

Table of Contents

About Release 3.2.11

VISM/VISM-PR Release 3.2.11 is a maintenance release of Release 3.2.10 and contains no new features. For a list of open and resolved caveats in this release, see "Caveats in VISM Release 3.2.11" section.

In this release, DSP RAS and fixed timestamp are disabled by default. If you are upgrading from 3.2 or 3.2.10 with DSP RAS and fixed timestamp enabled, you must disable these features before performing the upgrade. For more information, see the "Disable DSP RAS and Fixed Timestamp" section.


Note The content of VISM Release 3.2.11 supersedes previous releases.


About Release 3.2.10

VISM/VISM-PR Release 3.2.10 is a maintenance release of Release 3.2 and contains the new features listed in New Features in Release 3.2.10.

For a list of open and resolved caveats in this release, see "Caveats in VISM Release 3.2.10" section.


Note The content of VISM Release 3.2.10 supersedes previous releases.


About Release 3.2

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

Overview

These release notes contain the following sections:

"New Features in Release 3.2.10" section

"New Features in Release 3.2" section

"VISM Management Information Base" section

"VISM Redundancy" section

"VISM Call Rate" section

"Compatibility" section

"Limitations and Restrictions" section

"Upgrade Procedures" section

"Caveats in VISM Release 3.2.11" section

"Caveats in VISM Release 3.2.10" section

"Caveats in VISM Release 3.2" section

"Related Documentation" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

New Features in Release 3.2.10

This section describes the following new features included in Release 3.2.10:

Configurable TDM Companding Law

Programmable CAS Signaling Bit Mapping

Preferred Routes

E1 Trunk Conditioning

Display All Static Configuration

Bandwidth Utilization Enhancements

AIS Propagation Control

Configurable TDM Companding Law

In standard companding law T1 lines support Mu Law, and E1 lines support A-Law.

In Release 3.2.10, VISM-PR supports companding law on the TDM interface. T1 lines support A-Law, and E1 lines support Mu Law.

This feature is typically used when one end has VISM-PR E1 lines connected to the PBX on the TDM side; the other end of the network has VISM-PR T1 lines connected to the PBX on the TDM side. Both the VISM-PR E1 and T1 lines are connected via the ATM cloud using AAL2 channel identifiers (CIDs).

This feature is only supported in trunking mode and is not supported in switching mode.

Configure Companding Law

To configure companding law for a T1 or E1 line, complete the following steps:


Step 1 Log in to the PXM card and cc to the VISM-PR card.

Step 2 Ensure the VISM-PR card is running in AAL2 trunking mode.

Step 3 To configure companding law, enter the cnflncompanding command.

nodename.1.5.VISM8.a > cnflncompanding <line_number> <companding>

Replace <line_number> with a value in the range 1-8.

Replace <companding> with one of the following values:

1 = U-Law (same as Mu Law)

2 = A-Law

The following example shows configuring VISM-PR E1 line 1 as Mu-Law.

nodename.1.5.VISM8.a > cnflncompanding 1 1

Step 4 For the companding law change to take effect, reset the VISM-PR card.

Or, you can delete and re-add the CIDs.


Step 5 Verify the companding law you configured by entering the dsplncompanding command.

nodename.1.5.VISM8.a > dsplncompanding <line_number>

Replace <line_number> with the line number you configured companding law in Step 3.

nodename.1.5.VISM8.a > dsplncompanding 1

  Line/Ds0      Companding
  --------      ----------
     1/ 1        U-Law
     1/ 2        U-Law
     1/ 3        U-Law
     1/ 4        U-Law
     1/ 5        U-Law
     1/ 6        U-Law
     1/ 7        U-Law
     1/ 8        U-Law
     1/ 9        U-Law
     1/10        U-Law
     1/11        U-Law
     1/12        U-Law
     1/13        U-Law
     1/14        U-Law
     1/15        U-Law
     1/16        U-Law
     1/17        U-Law
     1/18        U-Law
     1/19        U-Law
     1/20        U-Law
     1/21        U-Law
     1/22        U-Law
     1/23        U-Law
     1/24        U-Law

Programmable CAS Signaling Bit Mapping

International connections include both T1 and E1 trunk interfaces. Channel associated signaling (CAS) bits, ABCD, differ on T1 and E1 interfaces. These CAS bits carry signaling information that describe events, for example off-hook, on-hook, idle, and so forth. Typically, an external device (PBX) is used to map the ABCD signaling bits across the interfaces.

The CAS signaling mapping feature allows you to map the output ABCD bits to input ABCD bits on a signaling channel on the VISM-PR card instead of using a PBX or another external device.

This feature is supported in AAL2 trunking mode.

The VISM-PR stores the CAS signaling mapping information in a table. This table can be downloaded to the transmit and/or receive signaling channel of the endpoint on the TDM line.

Configure CAS Signaling Bit Mapping Templates

To create a CAS signaling table and apply it to the appropriate endpoint, complete the following steps:


Step 1 Log in to the PXM card and cc to the VISM-PR card.

Step 2 Ensure the VISM-PR is running in AAL2 trunking mode.

Step 3 To create a CAS signaling mapping table, enter the addcastranstbl command.

nodename.1.5.VISM8.a > addcastranstbl <table_name> <format> <abcd0> <abcd1> <abcd2> 
<abcd3> <abcd4> <abcd5> <abcd6> <abcd7> <abcd8> <abcd9> <abcd10> <abcd11> <abcd12> 
<abcd13> <abcd14> <abcd15>

Replace the above arguments with the values listed in Table 1. The following example shows adding the table, T1andE1trans, with the standard T1 and E1 seize and Idle conversions:

nodename.1.5.VISM8.a > addcastranstbl T1andE1trans 1 9 12 2 3 4 5 6 7 8 0 10 11 1 13 14 1

Table 1 Parameters for the addcastranstble Command 

Parameter
Description

table_name

Name of the new table. Range is 1-64 characters.

format

Type of format of the ABCD bits.

1 = abcd. For parameters abcd0-abcd15, use values 0-15 to create the table.

2 = swap abcd. For parameters abcd0-abcd3, use the following values to create the table:

1 = casBitNoAction

2 = casBitSetToZero

3 = casBitSetToOne

4 = casBitInvertBit

5 = casBitInvertABit

6 = casBitInvertBBit

7 = casBitInvertCBit

8 = casBitInvertDBit

9 = casBitABit

10 = casBitBBit

11 = casBitCBit

12 = casBitDBit

abcd0...abcd15

Parameter values.

For abcd0-abcd3, values are

1 = casBitNoAction

2 = casBitSetToZero

3 = casBitSetToOne

4 = casBitInvertBit

5 = casBitInvertABit

6 = casBitInvertBBit

7 = casBitInvertCBit

8 = casBitInvertDBit

9 = casBitABit

10 = casBitBBit

11 = casBitCBit

12 = casBitDBit

For abcd0-abcd15, values are 0-15.


Step 4 To display the mapping table configurations you defined in Step 3, enter the dspcastranstbl command.

nodename.1.5.VISM8.a > dspcastranstbl <table_name>

Replace <table_name> with the name of the table you created in Step 3.

The following example shows the CAS signaling bit mapping configurations in table T1andE1trans.

nodename.1.5.VISM8.a > dspcastranstbl T1andE1trans

CAS translation name = T1andE1trans
-------A--B--C--D--------
 0     1  0  0  1
 1     1  1  0  0
 2     0  0  1  0
 3     0  0  1  1
 4     0  1  0  0
 5     0  1  0  1
 6     0  1  1  0
 7     0  1  1  1
 8     1  0  0  0
 9     0  0  0  0
10     1  0  1  0
11     1  0  1  1
12     0  0  0  1
13     1  1  0  1
14     1  1  1  0
15     0  0  0  1

Step 5 To display the list of the CAS mapping tables on the VISM-PR card, enter the dspcastranstbls command.

nodename.1.5.VISM8.a > dspcastranstbls
Index  CasTblName
0      E1toT1trans
1      T1andE1trans

Step 6 To download the table to the signaling channel, enter the cnfcastransendpt command.

nodename.1.5.VISM8.a > cnfcastransendpt <endpt_number> <table_name> <direction>

Replace the above arguments with the values listed in Table 2. The following example shows the T1andE1trans table is applied to endpoint number 1 in the receive and transmit direction:

nodename.1.5.VISM8.a > cnfcastransendpt 1 T1andE1trans 3

The following example shows the E1toT1trans table is applied to endpoint number 2 in the receive direction:

nodename.1.5.VISM8.a > cnfcastransendpt 2 E1toT1trans 2

Table 2 Parameters for the cnfcastransendpt Command 

Parameter
Description

endpt_number

Endpoint number of which you want to apply the mapping table. Value is one of the following ranges:

For template number 1:

1-145 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 2:

1-192 for T1

1-248 for E1

For template number 3:

1-120 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 4:

1-64 for VISM (not applicable)

1-144 for VISM-PR

For template number 5:

1-192 for VISM-PR T1

1-248 for VISM-PR E1

table_name

Name of the table you created in Step 3. Range is 1-64 characters.

direction

Direction to or from the TDM interface where you want to apply the CAS signaling mapping table.

1 = Rx from TDM—Applies the mapping to the signaling bits received from the TDM. These bits are translated and then transmitted out the AAL2 trunk.

2 = Tx to TDM—Applies the mapping to the signaling bits received from the AAL2 trunk. These bits are translated and then transmitted out the TDM interface.

3 = Receive and Transmit—Applies the mapping to both the received and transmitted translations on the TDM interface.

4 = None—Removes the translation table from the endpoint.


Step 7 To display all endpoints that are associated with this table, enter the dspcastranstblendpts command.

nodename.1.5.VISM8.a > dspcastranstblendpts <table_name>

Replace <table_name> with the name of the table you created in Step 3. The following example shows the endpoints associated with the table T1andE1trans:

nodename.1.5.VISM8.a > dspcastranstblendpts T1andE1trans 
endptNum:    1

Number of endpoints configured with CAS translation table name:T1andE1trans: 1

Step 8 To display all endpoints and their associated CAS mapping table names, enter the dspcastransendpts command.

Note Direction column is in relationship to the AAL2 trunk.

nodename.1.5.VISM8.a > dspcastransendpts

Endpt  LineNum Ds0Num  TX to TDM     RX fr TDM   Direction 
-----  ------- ------ ------------- -----------  --------- 
1        1      1     T1andE1trans  T1andE1trans  bidirectional
2        1      2     E1toT1trans   none          receive

Step 9 To delete an existing CAS mapping table, enter the delcastranstbl command.

nodename.1.5.VISM8.a > delcastranstbl <table_name>

Replace <table_name> with the name of the table you want to delete.

Step 10 To verify that the table is deleted, enter the dspcastranstbls command.

Step 11 To delete a table that is associated with an endpoint, enter the delcastransendpt command.

nodename.1.5.VISM8.a > delcastransendpt <endpt_number> |<endpts_num>|

Replace <endpt_number> with the endpoint number from which you want to delete the mapping table. This value can also be the first endpoint number of a range of consecutive endpoints. Value is one of the following ranges:

For template number 1:

1-145 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 2:

1-192 for T1

1-248 for E1

For template number 3:

1-120 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 4:

1-64 for VISM (not applicable)

1-144 for VISM-PR

For template number 5:

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Replace the optional |endpts_num| with the number of endpoints you want to delete. Ranges are

For template number 1:

1-145 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 2:

1-192 for T1

1-248 for E1

For template number 3:

1-120 for VISM (not applicable)

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 4:

1-64 for VISM (not applicable)

1-144 for VISM-PR

For template number 5:

1-192 for VISM-PR T1

1-248 for VISM-PR E1


Preferred Routes


Note This feature is not supported with PXM1E and PXM45 software Releases 4.x and prior.


In a PNNI network with a large number of SPVCs, the Cisco MGX 8850 (PXM1E and PXM45) can route SPVCs and SPVPs over pre-defined trunk routes in a PNNI group. This capability alleviates the manual rerouting of a large amount of connections.

In Release 3.2.10, you can provision the VISM-PR card to specify a preferred route ID and a preference on how the routing is to be handled in case the preferred route is not available.

This feature is applicable to VISM-PR cards operating in AAL2 trunking or VoIP switching modes.

Preferred route configuration is done on the PXM card. Therefore, only VISM-PR SPVC connections that have master endpoints can be added as preferred routes.

For more information on configuring preferred routes refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Prerequisites

Before configuring your SPVC as a preferred route, complete the following prerequisites:

Ensure your PXM1E and PXM45 cards are running at least software Release 5.0.

Install and perform the following initial configurations on your VISM-PR card:

Operating mode (cnfvismmode)

Codec template (cnfcodectmpl)

Port (addport)

Resource partition (addrscprtn)

Configure Preferred Routes

To configure your VISM-PR card for preferred routes, complete the following steps:


Step 1 Log in to the PXM1E or PXM45 card and cc to the VISM-PR card.

Step 2 Ensure you have completed the initial configurations listed in the Prerequisites section.

Step 3 To add a PVC between the VISM-PR and PXM cards and associate the connection as a preferred route, enter the addcon command with the following arguments:


Note In Release 3.2.10 the existing addcon command has been modified with the <prefrte> and <direct> arguments to support the preferred route feature.


nodename.1.12.VISM8.a > addcon <localVCI> <preference> <pvc_type> <application> <PCR> 
<mastership> |<remoteConnId> <nodename.slot.port.vpi.vci>| |serviceType| |scr| |mbs| |prefrte| 
|direct|

Replace the above arguments with the values listed in Table 3. The following example shows a PVC is added as the master endpoint of a preferred route:

nodename.1.12.VISM8.a > addcon 131 1 2 2 50000 1 mgx8850.0.4.120.120 1 150 777 1

Table 3 Parameters for addcon Command 

Parameter
Description

localVCI

Local virtual channel identifier (VCI) to be used for the connection. Range is 131-510.

preference

Preference level of the local VCI.

1 = Primary

2 = Secondary (for redundancy)

pvc_type

AAL type of connection.

1 = AAL5

2 = AAL2

3 = AAL1

application

Connection application.

1 = Control

2 = Bearer

3 = Signaling

Note If the connection is used for bearer and signaling, specify 2 for bearer.

PCR

Peak cell rate defined as cells per second.

1-96000 for AAL5 bearer

1-20000 for AAL5 control PVC

1-50000 for T1 AAL2 PVCs

1-60000 for E1 AAL2 PVCs

1-400 for signaling PVCs in AAL2 trunking mode

Note If the serviceType argument is variable bit rate (VBR), the PCR argument value must be 15 or greater.

mastership

Type of connection.

1 = Master

2 = Slave

Set this value to 1.

|remoteConnId|

(Optional) Remote connection identifier.

Type the value in the following format: nodename.slot.port.vpi.vci

Note Use the optional |remoteConnId| argument only if you selected the mastership argument value of 1 (Master).

|serviceType|

Service type.

1 = Constant bit rate (CBR)

2 = Variable bit rate real time (rt-VBR)

3 = Variable bit rate non-real time (nrt-VBR)

4 = rt3VBR

5 = rt2VBR

6 = nrt2VBR

7 = nrt3VBR

|scr|

Sustainable cell rate (SCR) in the range from 15 to the value you specified for the PCR argument.

This argument is required if the serviceType is rt-VBR or nrt-VBR.

|mbs|

Maximum burst size (MBS) is the number of cells transmitted at the peak cell rate.

This value is in the range from 1 to 10 times the value you specified for the scr argument.

This argument is required if the serviceType is rt-VBR or nrt-VBR.

|prefrte|

(Optional) Unique identifier of the preferred route to which this connection is associated.

Range is 0-65535. Default is 0.

When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection.

|direct|

(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take.

1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified.

2 = No (Default)—The connection is allowed to try another alternate route if the preferred route is unavailable.

If the directed preferred route is unavailable, the connection is failed.


Step 4 To associate or disassociate the master endpoint of an SPVC connection to/from a preferred route, enter the cnfcon command.


Note In Release 3.2.10 the existing cnfcon command has been modified with the <prefrte> and <direct> arguments to support the preferred route feature.


nodename.1.12.VISM8.a > cnfcon <LCN> <PCR> <service_type> |SCR_ingress| |MBS_ingress| 
|prefrte| |direct|

Replace the above arguments with the values listed in Table 4. The following example associates the master endpoint of this connection to a preferred route:

nodename.1.12.VISM8.a > cnfcon 131 60000 1 777 1

where 777 is the preferred route ID, and 1 is a directed route.

Table 4 Parameters for cnfcon Command 

Parameter
Description

LCN

Logical channel number of the connection. Range is 131-510.

This value is the same as the localVCI value in the addcon command.

PCR

Peak cell rate (PCR) described in cells per second. Ranges are

1-400 = Signaling PVCs in AAL2 trunking mode

1-20000 = AAL5 control PVC

1-50000 = T1 AAL2 bearer PVCs

1-60000 = E1 AAL2 bearer PVCs

1-96000 = AAL5 bearer PVC

Note If the service_type argument value is a variable bit rate (VBR), the PCR argument value must be 15 or greater.

service_type

Service type. Values are

1 = Constant bit rate (CBR)

2 = Variable bit rate real time—rt-VBR

3 = Variable bit rate non-real time—nrt-VBR

4 = rt-VBR3

5 = rt-VBR2

6 = nrt-VBR

7 = nrt-VBR

|SCR_ingress|

(Optional) Sustainable cell rate (SCR). Range is from 15 to the value you configured for the PCR argument value.

Note This argument value is required if the service_type argument value is in the range 2-7.

|MBS_ingress|

(Optional) Maximum burst size (MBS)—maximum number of cells transmitted at the peak cell rate. Range is from 1 cell to 10 times the value you configured for the SCR_ingress argument value.

Note This argument value is required if the service_type argument value is in the range 2-7.

|prefrte|

(Optional) Unique identifier of the preferred route to which this connection is associated.

Range is 0-65535. Default is 0.

When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection.

|direct|

(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take.

1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified.

2 = No (Default)—The connection is allowed to try another alternate route if the preferred route is unavailable.

If the directed preferred route is unavailable, the connection is failed.


Step 5 To display the preferred route identifier and the directed route flag of an SPVC, enter the dspcon command.


Note In Release 3.2.10 the existing dspcon command has been modified with the preferred route ID and directed route information to support the preferred route feature.


nodename.1.12.VISM8.a > dspcon <LCN>

Replace <LCN> with the logical channel number of the SPVC you configured in Step 4. The following example shows the preferred route information for LCN 131:

nodename.1.12.VISM8.a > dspcon 131

ChanNum: 131
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: Failed
ChanRTDresult: 65535 ms
ChanPortNum: 255
ChanPvcType: AAL2
ChanConnectionType: PVC
ChanLocalVpi: 29
ChanLocalVci: 131
ChanLocalNSAP: 47009181000000000164444b9400000107ebff00
ChanRemoteVpi: 29
ChanRemoteVci: 131
ChanRemoteNSAP: 47009181000000000164444b9400000101180400
ChanMastership: Master
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction

Type <CR> to continue, Q<CR> to stop:
ChanConnPCR: 50000
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 50000
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: bearer
ChanServiceType: cbr
ChanScrIngress: 50000
ChanMbsIngress: 50000
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
Pref Rte Id : 777
Directed Route: Yes

For slave endpoints, the preferred route identifier value is 0, and the directed route flag is No.


E1 Trunk Conditioning

Currently, VISM-PR supports T1 line trunk conditioning to prevent the ATM network alarms from propagating to the TDM side. In Release 3.2.10, line trunk conditioning is supported on the E1 line.

E1 trunk conditioning handles ATM network alarms (CID and PVC alarms) and prevents them from propagating to the TDM side. This feature is applicable in AAL2 trunking mode.

In a trunk conditioning enabled mode (T1 or E1), the DS0 bearer is set to a configurable busy bearer pattern when the ATM network reports any alarms. VISM-PR can mark one or more unusable DS0s to the adjoining TDM switch without putting the whole line into alarm. The busy bearer code is configured by using the cnflntrunkcond command.

The following existing commands, which are used to enable/disable the line trunk conditioning flag, have been modified to specify the bearer alarm busy code:

cnflntrunkcond

dspln

cnflntrunkcond

To enable or disable trunk conditioning on a VISM-PR T1 or E1 card line if a network alarm is encountered, use the cnflntrunkcond command. This command has been modified to include the optional bearer code parameter.

cnflntrunkcond <line_number> <trunkCondType> |<bearer_code>|

Syntax Description

line_number

Line number for which you want enable or disable line conditioning. Range is 1-8.

trunkCondType

Line trunk conditioning status. Values are

1 = Enable. VISM-PR performs trunk conditioning on each affected DS0 if an alarm occurs on the ATM side.

2 = Disable. VISM-PR sends an alarm indication signal (AIS), blue alarm, or RAI to the line if an alarm occurs on the ATM side.

|bearer_code|

(Optional) Bearer code sent on a bearer channel in remote alarm. Range is 0-255.

For VISM-PR T1, default is 127.

For VISM-PR E1, default is 255.

This parameter can be specified only when the trunkCondType parameter is set to Enable for a line.


Command Modes

AAL2 trunking

Usage Guidelines

This command is not allowed if endpoints or CCS channels are enabled on the line.

Examples

The following example shows that line 1 is configured with line conditioning if an AAL2 alarm is encountered, and the bearer code is set to 255:

nodename.1.12.VISM8.a > cnflntrunkcond 1 1 255

Use the dspln command to view trunk conditioning information.

dspln

To display the configuration data of a VISM-PR line, use the dspln command. This command has been modified to show the bearer busy code.

dspln <line_number>

Syntax Description

line_number

Line number for which you want to display the configuration data. Range is 1-8.


Command Modes

AAL2 trunking

Usage Guidelines

Follow standard CLI procedures for this command.

Examples

The following example shows that line 1 is enabled for trunk conditioning, and the bearer code is set to the default (255):

nodename.1.12.VISM8.a > dspln 1
LineNum:                   1
LineConnectorType:         RJ-48
LineEnable:                Enabled
LineType:                  dsx1ESF
LineCoding:                dsx1B8ZS
LineLength:                0-131 ft
LineXmtClockSource:        LocalTiming
LineLoopbackCommand:       NoLoop
LineSendCode:              NoCode
LineUsedTimeslotsBitMap:   0x3
LineLoopbackCodeDetection: codeDetectDisabled
LineSignalingType:         No Signaling
LineCcsChannels:           0x0
LineTrunkConditioning:     disable
LineBearerBusyCode: 				 			 255
CircuitIdentifier:          
TxDigitOrder:              aniThenDnis
TonePlanRegion:             
TonePlanVersion:           0
RingingTO:                 180
RingBackTO:                180

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

BusyTO:                    30
ReorderTO:                 30
DialTO:                    16
StutterDialTO:             16
OffHookAlertTO:            5
RemoteRingbackMethod:      proxy

LineNumOfValidEntries: 8

Display All Static Configuration

VISM/VISM-PR 3.2.10 introduces a new command, dspall -config, for troubleshooting VISM/VISM-PR issues for static configurations.

The dspall -config command is available in all operating modes. This command displays all of the individual display command data for each operating mode. The display data differs depending on the mode.

The following example shows sample static output using the dspall -config command in the AAL2 trunking mode:

nodename.1.12.VISM8.a > dspall -config

--------------------  Displaying Card Level Configuration --------------------


dspaal2params
---------------

AAL2 DTMF RELAY:          Off
AAL2 CAS BITS TRANSPORT:  Off
AAL2 TYPE3 REDUNDANCY:    On
AAL2 VAD TIMER:           250
AAL2 CID FILL TIMER:      30



dspaissuppression
---------------
   ConnId                ChanNum      AIS Suppression Status    AIS Delay Time
   ------                -------      ----------------------    --------------
milwwi03.17.1.0.131        131            DISABLED                       30
milwwi03.17.1.0.132        132            DISABLED                       30




dspcarddsp
---------------

  IdlePattern:             54
  IdleDirection:           Both
  PacketSize:              80 bytes
  DB loss:                 sixdb
  Jitter buffer mode:      fixed
  Jitter buffer size:      forty msec
  Adaptive Gain Control:   off

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

The following sections list the display commands that are applicable to the dspall -config command. For more information on these commands, refer to the CLI section of the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.2.

VoIP Switching/VoIP Trunking

In the VoIP switching/VoIP trunking mode 1, issuing the dspall -config command shows the static data of the commands listed in Table 5.

Table 5 VoIP Switching/VoIP Trunking Display Commands 

Command
Description

dspcarddsp

Display card configuration parameters

dspcasendpts

Display CAS endpoint configuration

dspcasvars

Display parameters of all CAS variants

dspcasxgcps

Display CAS/xGCP timer parameters

dspco1timer

Display continuity test 1 timer value

dspco2timer

Display continuity test 2 timer value

dspco4timer

Display continuity test 4 timer value

dspcodecjtrdelays

Display codec jitter delay modes

dspcodecneg

Display codec negotiation option

dspcodecparams

Display codec parameters

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a channel

dspdnallips

Display all IP addresses for all domain names on the card

dspdynamicpayload

Display dynamic payload for the card

dspendpts

Display configuration for all endpoints

dspgwstate

Display gateway service state

dsplapds

Display configuration for all LAPD channels

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsplnstate

Display service state of the line

dsploops

Display all lines and DS0s in the loopback condition

dspmgcgrpprotocols

Display all MGC redundancy group protocols

dspmgcgrps

Display all configured MGC redundancy groups

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dsprscprtn

Display resource partition configuration

dsprtpcons

Display configuration for all RTP connections

dsprudptrunks

Display configuration for all RUDP sessions

dspsesgrps

Display configuration for all session groups

dspsidpacket

Display SID packet configuration for each line

dspt38fxlcos

Display fax handling instructions for all lines

dspt38nsetimeouts

Display NSE timeout for all lines

dspt38params

Display fax transfer parameters for a line

dspvbdcodec

Display upspeed codec for VBD

dspvbdpol

Display VBD policies

dspvismdn

Display domain name for card

dspvismparam

Display card configuration parameters

dspvoipparams

Display VoIP mode parameters

dspxgcpbt

Display bear type configuration

dspxgcppersistevts

Display all xGCP persistent events

version

Display version data


AAL2 Trunking

In the AAL2 trunking mode 2, issuing the dspall -config command shows the static data of the commands listed in Table 6.

Table 6 AAL2 Trunking Display Commands 

Command
Description

dspaal2params

Display AAL2 parameters

dspaissuppression

Display AIS suppression status

dspcarddsp

Display card configuration parameters

dspcasendpts

Display CAS endpoint configuration

dspcastransendpts

Display endpoints with their associated CAS mapping table names

dspcastranstbls

Display list of the CAS mapping tables

dspcasvars

Display parameters of all CAS variants

dspcasxgcps

Display CAS/xGCP timer parameters

dspccschans

Display CCS channels

dspcids

Display CIDs of LCN

dspcodecjtrdelays

Display codec jitter delay modes

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a channel

dspendpts

Display endpoints

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsploops

Display all lines and DS0s in the loopback condition

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dspprofparams

Display profile elements for all profiles

dsprscprtn

Display resource partition configuration

dspvbdpol

Display VBD policies

dspvismparam

Display card configuration parameters

dspxgcpbt

Display bear type configuration

version

Display version data


AAL1 Switching

In the AAL1 switching mode 3, issuing the dspall -config command shows the static data of the commands listed in Table 7.

Table 7 AAL1 Switching Display Commands 

Command
Description

dspaggsvcbw

Display configured bandwidth

dspcarddsp

Display card configuration parameters

dspco1timer

Display continuity test 1 timer value

dspco2timer

Display continuity test 2 timer value

dspco4timer

Display continuity test 4 timer value

dspcodecjtrdelays

Display codec jitter delay modes

dspcodecneg

Display codec negotiation option

dspcodecparams

Display codec parameters

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspdnallips

Display all IP addresses for all domain names on the card

dspdynamicpayload

Display dynamic payload for the card

dspendpts

Display endpoints

dspgwstate

Display gateway service state

dsplapds

Display configuration for all LAPD channels

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsplnstate

Display service state of the line

dsploops

Display all lines and DS0s in the loopback condition

dspmgcgrpprotocols

Display all MGC redundancy group protocols

dspmgcgrps

Display all configured MGC redundancy groups

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dsprscprtn

Display resource partition configuration

dspsesgrps

Display configuration for all session groups

dspsvcgw

Display SVC gateway parameters

dspsvcqosparam

Display Quality of Service parameters

dspvismdn

Display domain name for card

dspvismparam

Display card configuration parameters

dspxgcpbt

Display bear type configuration

dspxgcppersistevts

Display all xGCP persistent events

version

Display version data


Switched AAL2 SVC

In the switched AAL2 SVC mode 7, issuing the dspall -config command shows the static data of the commands listed in Table 8.

Table 8 Switched AAL2 SVC Display Commands 

Command
Description

dspaal2params

Display AAL2 parameters

dspaggsvcbw

Display configured bandwidth

dspaissuppression

Display AIS suppression settings

dspcarddsp

Display card configuration parameters

dspcastransendpts

Display endpoints with their associated CAS mapping table names

dspcastranstbls

Display list of the CAS mapping tables

dspco1timer

Display continuity test 1 timer value

dspco2timer

Display continuity test 2 timer value

dspco4timer

Display continuity test 4 timer value

dspcodecjtrdelays

Display codec jitter delay modes

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a connection

dspdnallips

Display all IP addresses for all domain names on the card

dspendpts

Display endpoints

dspgwstate

Display gateway service state

dsplapds

Display configuration for all LAPD channels

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsplnstate

Display service state of the line

dsploops

Display all lines and DS0s in the loopback condition

dspmgcgrpprotocols

Display all MGC redundancy group protocols

dspmgcgrps

Display all configured MGC redundancy groups

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dspprofparams

Display profile parameters

dsprscprtn

Display resource partition configuration

dspsesgrps

Display configuration for all session groups

dspsvcgw

Display SVC gateway parameters

dspsvcqosparam

Display Quality of Service parameters

dspvbdpol

Display VBD policies

dspvismdn

Display domain name for card

dspvismparam

Display card configuration parameters

dspxgcpbt

Display bear type configuration

dspxgcppersistevts

Display all xGCP persistent events

version

Display version data


Switched AAL2 PVC

In the switched AAL2 PVC mode 8, issuing the dspall -config command shows the static data of the commands listed in Table 9.

Table 9 Switched AAL2 PVC Display Commands 

Command
Description

dspaal2params

Display AAL2 parameters

dspaissuppression

Display AIS suppression status

dspcarddsp

Display card configuration parameters

dspcasendpts

Display CAS endpoint configuration

dspcastransendpts

Display endpoints with their associated CAS mapping table names

dspcastranstbls

Display list of the CAS mapping tables

dspcasvars

Display parameters of all CAS variants

dspcasxgcps

Display CAS/xGCP timer parameters

dspccschans

Display CCS channels

dspcids

Display CIDs of LCN

dspco1timer

Display continuity test 1 timer value

dspco2timer

Display continuity test 2 timer value

dspco4timer

Display continuity test 4 timer value

dspcodecjtrdelays

Display codec jitter delay modes

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a channel

dspdnallips

Display all IP addresses for all domain names on the card

dspendpts

Display configuration for all endpoints

dspgwstate

Display gateway service state

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsplnstate

Display service state of the line

dsploops

Display all lines and DS0s in the loopback condition

dspmgcgrpprotocols

Display all MGC redundancy group protocols

dspmgcgrps

Display all configured MGC redundancy groups

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dspprofparams

Display profile elements for all profiles

dsprscprtn

Display resource partition configuration

dspvbdpol

Display VBD policies

dspvccis

Display VCCI values

dspvismdn

Display domain name for card

dspvismparam

Display card configuration parameters

dspxgcpbt

Display bear type configuration

dspxgcppersistevts

Display all xGCP persistent events

version

Display version data


VoIP and AAL1 SVC

In the VoIP and AAL1 SVC mode 9, issuing the dspall -config command shows the static data of the commands listed in Table 10.

Table 10 VoIP and AAL1 Display Commands 

Command
Description

dspaggsvcbw

Display configured SVC bandwidth

dspcarddsp

Display card configuration parameters

dspcasendpts

Display CAS endpoint configuration

dspcasvars

Display parameters of all CAS variants

dspcasxgcps

Display CAS/xGCP timer parameters

dspco1timer

Display continuity test 1 timer value

dspco2timer

Display continuity test 2 timer value

dspco4timer

Display continuity test 4 timer value

dspcodecjtrdelays

Display codec jitter delay modes

dspcodecneg

Display codec negotiation option

dspcodecparams

Display codec parameters

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a channel

dspdnallips

Display all IP addresses for all domain names on the card

dspdynamicpayload

Display dynamic payload for the card

dspendpts

Display all endpoints

dspgwstate

Display gateway service state

dsplapds

Display configuration for all LAPD channels

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsplnstate

Display service state of the line

dsploops

Display all lines and DS0s in the loopback condition

dspmgcgrpprotocols

Display all MGC redundancy group protocols

dspmgcgrps

Display all configured MGC redundancy groups

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dsprscprtn

Display resource partition configuration

dsprtpcons

Display configuration for all RTP connections

dsprudptrunks

Display configuration for all RUDP sessions

dspsesgrps

Display configuration for all session groups

dspsidpacket

Display SID packet configuration for each line

dspsvcgw

Display SVC gateway parameters

dspsvcqosparam

Display Quality of Service parameters

dspt38fxlcos

Display fax handling instructions for all lines

dspt38nsetimeouts

Display NSE timeout for all lines

dspt38params

Display fax transfer parameters for a line

dspvbdcodec

Display upspeed codec for VBD

dspvbdpol

Display VBD policies

dspvismdn

Display domain name for card

dspvismparam

Display card configuration parameters

dspvoipparams

Display VoIP mode parameters

dspxgcpbt

Display bear type configuration

dspxgcppersistevts

Display all xGCP persistent events

version

Display version data


VoIP Trunking/AAL2 Trunking

In the VoIP trunking/AAL2 trunking mode 10, issuing the dspall -config command shows the static data of the commands listed in Table 11.

Table 11 VoIP Trunking/AAL2 Trunking Display Commands 

Command
Description

dspaal2params

Display AAL2 parameters

dspaissuppression

Display AIS suppression status

dspcarddsp

Display card configuration parameters

dspcasendpts

Display CAS endpoint configuration

dspcastransendpts

Display endpoints with their associated CAS mapping table names

dspcastranstbls

Display list of the CAS mapping tables

dspcasvars

Display parameters of all CAS variants

dspcasxgcps

Display CAS/xGCP timer parameters

dspccschans

Display CCS channels

dspcids

Display CIDs of LCN

dspcodecjtrdelays

Display codec jitter delay modes

dspcodecparams

Display codec parameters

dspcon

Display channel configuration

dspconcac

Display CAC configuration for a connection

dspcons

Display channel configuration for all connections

dspconvbdpol

Display VBD policies for a channel

dspdynamicpayload

Display dynamic payload for the card

dspendpts

Display configuration for all endpoints

dspln

Display configuration of a line

dsplncompanding

Display companding law on the line

dsplndsp

Display DSP data for a line

dsplns

Display configuration for all lines on the card

dsploops

Display all lines and DS0s in the loopback condition

dspoamloopcnt

Display OAM loop count

dspport

Display virtual port configuration

dspprofparams

Display profile elements for all profiles

dsprscprtn

Display resource partition configuration

dsprtpcons

Display configuration for all RTP connections

dsprudptrunks

Display configuration for all RUDP sessions

dspsidpacket

Display SID packet configuration for each line

dspt38fxlcos

Display fax handling instructions for all lines

dspt38nsetimeouts

Display NSE timeout for all lines

dspt38params

Display fax transfer parameters for a line

dspvbdcodec

Display upspeed codec for VBD

dspvbdpol

Display VBD policies

dspvismparam

Display card configuration parameters

dspxgcpbt

Display bear type configuration

version

Display version data


AIS Propagation Control

Currently, VISM/VISM-PR cards support alarm indication signal (AIS) suppression, which prevents the CPE from dropping calls when a network link failure is temporary.

In Release 3.2.10, you can configure the suppression of ATM network alarms for a particular duration. If the ATM network alarms persist beyond this duration, the alarms propagate onto the TDM line and are considered a permanent network failure.

This feature does not affect the AAL2 type 3 packet alarms (transmitted and received per CID), for example, external AIS and RDI and connection AIS and RDI. These alarms are generated when a T1/E1 line fails and are preserved since they allow a T1/E1 alarm to propagate to the remote end.

For more information about AIS suppression configuration, refer to the Alarm Suppression section of the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.2.

No new commands are introduced for this feature in Release 3.2.10. The following commands have been modified to support the timing option:

cnfaissuppression

dspaissuppression

dspconcnt

cnfaissuppression

To enable or disable AIS suppression, use the cnfaissuppression command. Use this command also to suppress the alarms for a certain duration before propagating.

cnfaissuppression <enableFlag> |LCN | |delay_time|

Syntax Description

enableFlag

Value that enables or disables AIS suppression.

1 = Enable

2 = Disable

|LCN|

Logical channel number (LCN). Range is 131-510. Or, type the ALL keyword.

The value ALL specifies configuration of all LCNs.

|delay_time|

Time that the alarm is suppressed before propagating to the line. Range is 1-60 seconds. Default is 30 seconds.

Note This value is only valid if the enableFlag parameter is 1.


Command Modes

AAL2 trunking

Examples

You can enable AIS suppression and configure the optional delay time for one PVC or all PVCs on a VISM/VISM-PR card.

The following example enables AIS suppression with an AIS delay of 30 seconds on all enabled PVCs:

nodename.1.12.VISM8.a > cnfaissuppression 1 ALL 30
nodename.1.12.VISM8.a >

The following example disables AIS suppression on all enabled PVCs:

nodename.1.12.VISM8.a > cnfaissuppression 2 ALL
nodename.1.12.VISM8.a >

The following example enables AIS suppression on PVC 131 with an AIS delay of 60 seconds.

nodename.1.12.VISM8.a > cnfaissuppression 1 131 60
nodename.1.12.VISM8.a >

The following example disables AIS suppression on only PVC 131:

nodename.1.12.VISM8.a > cnfaissuppression 2 131
nodename.1.12.VISM8.a >

Use the dspaissuppression command to show the AIS settings you configured.

dspaissuppression

To show the AIS suppression settings of each enabled PVC, use the dspaissuppression command. This command has been modified to include the AIS delay time.

dspaissuppression

Syntax Description

This command has no arguments or keywords.

Command Modes

AAL2 trunking

Examples

The following example shows the AIS suppression settings for each PVC.

nodename.1.17.VISM8.a > dspaissuppression

   ConnId                ChanNum      AIS Suppression Status    AIS Delay Time
   ------                -------      ----------------------    --------------
nodename.17.1.0.131        131            ENABLED                       30
nodename.17.1.0.132        132            ENABLED                       30

dspconcnt

To display the counters/statistics and connection state, use the dspconcnt command. This command has been modified to include the AIS successful suppression count for each PVC.

dspconcnt <LCN>

Syntax Description

LCN

Logical channel number for which to display counter configuration data. Range is 131-510.


Command Modes

VoIP switching/VoIP trunking, AAL2 trunking, AAL1 switching, switched AAL2 SVC, switched AAL2 PVC, VoIP and AAL1 SVC, VoIP trunking/AAL2 trunking

Examples

The following example shows the AIS suppression count for PVC 131:

nodename.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: 0x6
OAM Lpb Lost Cells: 89381
AAL2 HEC Errors: 23540
AAL2 CRC Errors: 0
AAL2 Invalid OSF Cells: 33493675
AAL2 Invalid Parity Cells: 0
AAL2 CPS Packet Xmt: 1532756592
AAL2 CPS Packet Rcv: 1820470968
AAL2 Invalid CID CPS: 0
AAL2 Invalid UUI CPS: 0
AAL2 Invalid Len. CPS: 3
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
AIS Successful Suppression Cnt: 30

Note If the VISM/VISM-PR card is not operating in the AAL2 trunking mode, AIS suppression count is 0. AIS suppression cannot be enabled in the other modes.


Bandwidth Utilization Enhancements

VISM-PR Release 3.2.10 includes the following bandwidth utilization features:

ATM Bandwidth Reuse for Non-overlapping Traffic

Dynamic PVC Bandwidth Management

Channel Current Peak Rates

ATM Bandwidth Reuse for Non-overlapping Traffic

This feature allows you to place an unused PVC out-of-service during nonservice hours and place another PVC in-service during the service window while utilizing the same ATM bandwidth. This feature is applicable to VISM-PR cards in PNNI networks.

When a PVC is placed out-of-service, the PVC does not utilize any bandwidth and does not generate any alarms towards the CPE.

This bandwidth enhancement requirement uses the existing dncon command. The dncon command is now supported on both the master-end and the slave-end of the connections and is also used to disable the OAM end-to-end loopback functionality.

Disabling the OAM end-to-end loopback functionality on both ends of the connection avoids generating alarms to the TDM side. Therefore, you do not see alarms during non-service hours. The row status is not affected for the slave-end connection, and only the connection administrative status is changed to Down.

The existing upcon command is modified for both the master and slave ends. On the master end, the upcon command causes the OAM end-to-end loopback functionality to be re-enabled and places the PVC back in-service. The connection is re-routed if enough bandwidth is present.

On the slave end, the upcon command causes OAM end-to-end loopback functionality to be re-enabled, so the PVC can be monitored for failure.

To place a PVC out-of-service/in-service without causing alarms on the PVC and TDM side, complete the following steps in the order listed below:


Step 1 Log in to the PXM card and cc to the VISM-PR card.

Step 2 Ensure that the VISM-PR card is operating in the AAL2 trunking mode.

Step 3 To take the slave-end of the connection out-of-service, enter the dncon command.

nodename.1.12.VISM8.a > dncon <LCN>

Replace <LCN> with the slave-end channel number of the connection.

The slave-end stops generating voice packets and also stops OAM end-to-end loopback request cell generation. However, incoming OAM end-to-end loopback request cells are processed, and appropriate OAM end-to-end loopback response cells are generated.

This process ensures that alarms are not generated on the slave-end when you perform Step 4.

Step 4 To take the master-end of the connection out of service, enter the dncon command.

nodename.1.12.VISM8.a > dncon <LCN>

Replace <LCN> with the master-end channel number of the connection.

The PVC is placed into an administratively down state. This state tears down the PVC, stops checking for OAM end-to-end loopback failures, and stops generating voice packets.

Step 5 To bring an administratively down connection back into service, enter the upcon command on the master-end of the connection.

nodename.1.12.VISM8.a > upcon <LCN>

Replace <LCN> with the master-end channel number of the connection.

Step 6 To bring the slave-end of the connection back into service, enter the upcon command.

nodename.1.12.VISM8.a > upcon <LCN>

Replace <LCN> with the slave-end channel number of the connection.



Dynamic PVC Bandwidth Management

In Release 3.2.10, you can dynamically change and manage PVC bandwidth on VISM-PR cards with calls present.

This feature also provides you with configurable administrative states at the CID (or bearer connection) level to manage the operations of used bandwidth. You can take put the PVC into a minimum mode configuration in which just enough bandwidth is used to maintain the signaling link. It is recommended that both sides of the connection be placed in a minimum mode.

The following new commands have been added to support this feature:

cnfcidis

cnfcidoos

cnfconbwtoggle

The following commands have been modified to support this feature:

dspcid

dspcon

To configure the administrative states and the bandwidth usage on the PVC, complete the following steps:


Step 1 Log in to the PXM card and cc to the VISM-PR card.

Step 2 Ensure that the VISM-PR card is operating in the AAL2 trunking mode.

Step 3 To configure a CID as in-service, use the cnfcidis command.

nodename.1.12.VISM8.a > cnfcidis <LCN> <cid_number> |<maxcid>|

In-service means the CID is enabled and operationally active. To place a CID in-service, enough bandwidth must exist.

Replace the above arguments with the values listed in Table 12. The following example shows CID 100 on LCN 131 is configured for in-service.

nodename.1.12.VISM8.a > cnfcidis 131 100

Table 12 Parameters for cnfcidis Command 

Parameter
Description

LCN

Logical channel number of the connection. Range is 131-510.

cid_number

Number of the CID you want to put in-service. Range is 8-255.

|maxcid|

(Optional) Maximum number of CIDs to configure as in-service in bulk mode.


Step 4 To configure a CID as out-of-service, use the cnfcidoos command.

nodename.1.12.VISM8.a > cnfcidoos <LCN> <cid_number> |<maxcid>|

An out-of-service state means that the CID(s) are disabled and not operationally active.

Replace the above arguments with the values listed in Table 13. The following example shows CID 8 on LCN 131 is configured for out-of-service.

nodename.1.12.VISM8.a > cnfcidoos 131 8

Table 13 Parameters for cnfcidoos Command 

Parameter
Description

LCN

Logical channel number of the connection. Range is 131-510.

cid_number

Number of the CID you want to take out-of-service. Range is 8-255.

|maxcid|

(Optional) Maximum number of CIDs to configure as out-of-service in bulk mode.


Step 5 To show the administrative state of the CID, enter the dspcid command.

nodename.1.12.VISM8.a > dspcid <LCN> <cid_number>

Replace <LCN> with the logical channel number of the CID, in the range 131-510.

Replace <cid_number> with the number of the CID, in the range 8-255.

The following example shows the CID 8 on LCN 131 is in the out-of-service administrative state:

nodename.1.12.VISM8.a > dspcid 131 8
LCN number : 131
CID number: 8
Endpoint number : 1
CidRowStatus: active
Type3redundancy: enabled
VAD: disabled
VADInitTimer: 250
Profile type: ITU
Profile number: 1
Codec type: G.711u
Cas transport: disabled
DTMF transport: enabled
Ecan on/off: enabled
ICS enable: Disabled
pkt period: 5
Cid state: Failed
Cid Fail Reason: Self
Cid Admin State: OOS

Step 6 To change the bandwidth usage either to a minimum usage mode or to the original PVC bandwidth configuration, enter the cnfconbwtoggle command.

nodename.1.12.VISM8.a > cnfconbwtoggle <LCN> <USER_BW_OPTIONS>

Replace <LCN> with the logical channel number, in the range 131-510.

Replace <USER_BW_OPTIONS> with one of the following bandwidth toggle options:

1 = BW Revert—Revert back to the original PVC bandwidth configuration.

2 = BW Minimum—Use the minimum bandwidth for the PVC.

Step 7 To display the current bandwidth values, use the dspcon command.

nodename.1.12.VISM8.a > dspcon <LCN>

Replace <LCN> with the logical channel number, in the range 131-510. The following example shows sample bandwidth values on LCN 131. The original PVC configured bandwidth is being used, shown in the ChanUserPcrNumber field (User BW Off). If the minimum bandwidth is used, the ChanUserPcrNumber field shows User BW Min.

mnodename.1.12.VISM8.a > dspcon 131
ChanNum: 131
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 ms
ChanPortNum: 1
ChanPvcType: AAL2
ChanConnectionType: PVC
ChanLocalVpi: 0
ChanLocalVci: 131
ChanLocalNSAP: 6d696c7777693033000000000000000015000100
ChanRemoteVpi: 0
ChanRemoteVci: 0
ChanRemoteNSAP: NULL NSAP
ChanMastership: Slave
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 255
ChanRestrictTrunkType: No Restriction
Type <CR> to continue, Q<CR> to stop:
ChanConnPCR: 10000
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 10000
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: bearer
ChanServiceType: cbr
ChanScrIngress: 10000
ChanMbsIngress: 10000
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
ChanPrefRouteId: 0
ChanDirectRoute: False
Type <CR> to continue, Q<CR> to stop:
ChanUserPcrNumber: User BW Off
ChanUserMinPCRBW: 10
ChanUserMaxPCRBW: 10000
ChanUserMaxScrBW: 0
ChanUserMaxMbsBW: 0
ChanNumNextAvailable: 132


Channel Current Peak Rates

Several real-time statistics can be collected and displayed for cell rates on the PVC.

To display the cell rate in cells per second (cps) per PVC, use the existing dspconcnt command.

nodename.1.12.VISM8.a > dspconcnt <LCN>

Replace <LCN> with the logical channel number, in the range 131-510. The following example shows sample cell rates values on LCN 131:

mnodename.1.12.VISM8.a > dspconcnt 131
ChanNum:                  131
Chan State:               alarm
Chan XMT ATM State:       Sending FERF OAM
Chan RCV ATM State:       OAM End-to-End Loopback Failure
Chan Status Bit Map:               0x4
OAM Lpb Lost Cells:                406799
AAL2 HEC Errors:                   0
AAL2 CRC Errors:                   0
AAL2 Invalid OSF Cells:            0
AAL2 Invalid Parity Cells:         0
AAL2 CPS Packet Xmt:               81848211
AAL2 CPS Packet Rcv:               0
AAL2 Invalid CID CPS:              0
AAL2 Invalid UUI CPS:              0
AAL2 Invalid Len. CPS:             0
Chan 24Hr Peak Xmt Cell Rate (CPS):185
Chan Current   Xmt Cell Rate (CPS):184
Chan 24Hr Peak Rcv Cell Rate (CPS):0
Chan Current   Rcv Cell Rate (CPS):0
AAL5 Invalid CPI:                  0
AAL5 oversized SDU PDU:            0

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

 Channel counters
AAL5 Invalid Len. PDU:             0
AAL5 PDU CRC32 Errors:             0
AAL5 Reassembly Timer expired PDU: 0
AIS Successful Suppression Count:  0

Note The 24 hr peak transmit and receive statistics are reset at midnight.


New Features in Release 3.2

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

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

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

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

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

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

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

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

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

VISM Management Information Base

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

VISM Redundancy

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

Table 14 Service Module Redundancy 

Front Card Model Number
Redundancy Support

MGX-VISM-8T1

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

MGX-VISM-8E1

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

MGX-VISM-PR-8T1

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

MGX-VISM-PR-8E1

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



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


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

VISM Call Rate

Software Release 3.2.11 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, Cisco MGX 8850 (PXM1, PXM1E, PXM45), and Cisco MGX 8880 platform software is listed in Table 15.

Table 15 VISM/VISM-PR Software Interoperability 

Product
CW2000 Name
Latest Firmware
Minimum Firmware

PXM1

MGX 8250/MGX 8850

1.3100

1.2.22

PXM1E

MGX 8850/MGX 8830

5.0.10

4.0.151

PXM45

MGX 8850/MGX 8880

5.0.10

4.0.15 1

RPM-PR

RPM-PR

12.2(8)T1

12.2(8)T1

RPM-XF

RPM-XF

12.2(15)T5

12.2(15)T5

SRM-E

SRM-E

FC-C0 BC-B0

FC-C0 BC-B0

SRM-C 3T3

SRM-C

FC-CA BC-A0

FC-CA BC-A0

AUSM

AUSM

10.3.01

10.2.00

AXSM

AXSM

5.0.10

4.0.15 1

CWM

CWM

15.0 Patch 2

15.0

1 The Preferred Routes feature is not supported with PXM1E, PXM45, and AXSM Software Release 4.0.15. This feature requires Software Release 5.0.00 or higher.



Note If you are running PXM1E, PXM45, and AXSM Software Release 5.0.00 or higher, you must run VISM/VISM-PR Release 3.2.10 or higher.


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

Table 16 VISM/VISM-PR Compatibility with PXM Cards

 
PXM1
PXM1E
PXM45 (A/B/C)

VISM

Yes

No

No

VISM-PR

Yes

Yes

Yes


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

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

 
Cisco MGX 8230
Cisco MGX 8250
Cisco MGX 8830
Cisco MGX 8850 (PXM1)
Cisco MGX 8850
(PXM1E or PXM45)
Cisco MGX 8880 (PXM45)

VISM

Yes

Yes

No

Yes

No

No

VISM-PR

Yes

Yes

Yes

Yes

Yes

Yes


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

Table 18 VISM/VISM-PR Release 3.2.11 Interoperability with Other Cisco Products 

Product
CW2000 Name
Latest Firmware
Minimum Firmware

BTS

BTS 10200

4.2(0)V07

4.1.1V00

PGW

PGW 2200

9.3(2)

9.3(2)

CISCO 3810

CISCO 3810

12.3.3

12.3.3

CISCO 2421

CISCO 2421

12.3.3

12.3.3

AS5400

AS5400

12.3.6 2T1

12.3.5

AS5300

AS5300

12.3.6 with vcware 11.32

12.3.5 with vcware 11.32


Table 19 describes the software images available for VISM/VISM-PR Release 3.2.11.

Table 19 Software Images for VISM/VISM-PR Release 3.2.11 

Product Name
Software Version
Firmware Image Name
Description

MGX-VISM-SW3211

003.002.011.200

vism-8t1e1-003.002.011.200.fw

This image does not support the CALEA1 feature.

MGX-VISM-LISW3211

003.052.011.200

vism-8t1e1-003.052.011.200.fw2

This image supports the CALEA 1 feature.

1 CALEA = Commission on Accreditation for Law Enforcement Agencies.

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


Table 20 describes the software boot code requirements for VISM/VISM-PR Release 3.2.11.

Table 20 VISM/VISM-PR Software 3.2.11 Boot Code Requirements 

Board Pair
Boot Code Image Name
Boot Code Version

MGX-VISM-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

VI8_BT_3.2.00


Limitations and Restrictions

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

If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.

Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.

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

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

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

The following commands are not supported:

cnfmaxconfnum

dspconferences

dspmaxconfnum

GR-303 is not supported for the LAPD commands.

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

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

Upgrade Procedures

This section describes the following upgrade procedures:

Prerequisites

VISM/VISM-PR Upgrades with PXM1

VISM-PR Upgrades with PXM1E and PXM45

VISM/VISM-PR Downgrade Procedure

VISM to VISM-PR Hardware Upgrade

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

From VISM 1.5 to VISM 3.2.11

From VISM 2.1 to VISM 3.2.11

From VISM 2.2 to VISM 3.2.11

From VISM 3.1(1) to VISM 3.2.11

From VISM 3.1(2) to VISM 3.2.11

From VISM 3.1.3 to VISM 3.2.11

From VISM 3.2 to VISM 3.2.11

From VISM 3.2.10 to VISM 3.2.11


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

Prerequisites

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

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 following documents:

Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3

Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3

Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5

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

Download software Release 3.2.11 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.

Before you upgrade to 3.2.11, delete all domain names that are greater than 32 characters on the VISM/VISM-PR card. See the Check Domain Name Length section. After you complete the upgrade to 3.2.11, add the domain names that are greater than 32 characters.

Ensure that DSP RAS and fixed timestamp are disabled. See the Disable DSP RAS and Fixed Timestamp section.

In Release 3.2.11, these features are disabled by default. In releases prior to 3.2.11, these features are enabled by default.

Check Domain Name Length

Before you upgrade to 3.2.11, delete all domain names and domain name IPs that are greater than 32 characters on the VISM/VISM-PR card. After the upgrade, re-add the domain names and domain name IPs.

Complete the following steps.


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

Step 2 Display the list of domain names by entering the dspdns command.

nodename.1.11.VISM8.a > dspdns

DomainNumber    DomainName               ResolutionType
------------  --------------             --------------
1      mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.com  internalOnly 
2      mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.dom  internalOnly 
3      mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.eom  internalOnly 

Step 3 For each domain number, count the number of characters in the DomainName field.

If the characters are greater than 32 for each domain number, go to Step 4.

Step 4 Check for the IP addresses associated with the domain names by entering the dspdnallips command.

nodename.1.11.VISM8.a > dspdnallips

ResolutionIndex    DomainName                     IP           State    Pref
---------------   ------------                ------------   ---------  -----
1 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.com  10.1.3.25 Inactive   1

Step 5 If IP addresses are present, make a note of them in the order that they appear.

Step 6 Since you cannot delete the domain name or domain name IPs if MGCs exist, use the following commands to check for MGCs and delete them if they exist for each domain name:

a. Check for the MGC group protocols by entering the dspmgcgrpprotocols command.

nodename.1.11.VISM8.a > dspmgcgrpprotocols

MgcGrp Prot    Qrntn     Qrntn      Sign           Prov      RspAck    Disc    Cancel  
 Num   Num     Persist    Def       OnOff          Resp       Attr      Proc   
Graceful
--------------------------------------------------------------------------------------
 1   MGCP 1.0     Qrtn StepProcess      DelNegEvt     Send     Send  Enable     Send

b. Check for MGC group entries by entering the dspmgcprpparams command.

nodename.1.11.VISM8.a > dspmgcgrpparams

Mgc Grp Num     Comm State    State Chg Notification    Priority
-----------     ----------    ----------------------    --------
     1           CommLoss              Enabled              1

c. Check for MGC entries by entering the dspmgcs command.

nodename.1.11.VISM8.a > dspmgcs

mgcNumber   mgcName
---------   -------
     1      mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.co

Step 7 If entries exist for the domain name in Step 6 a. to Step 6 c., delete the MGC entries by entering the following commands as required:

delmgcgrpprotocol

delmggrpentry

delmgc

Step 8 Delete the domain name IP address by entering the deldnip command.

Step 9 Delete the domain name by entering the deldn command.

Step 10 Perform the upgrade using the procedures in the "Upgrade VISM/VISM-PR Firmware with PXM1 Card" section or "Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards" section.

Step 11 After you complete the upgrade, add the domain name entries, IP addresses, and MGCs as previously configured using the following commands:

adddn

adddnip

addmgc

addmgcgrpentry

addmgcgrpprotocol

Step 12 To check that you added the entries successfully, use the corresponding display commands from Step 2 to Step 6.


Disable DSP RAS and Fixed Timestamp

To disable the DSP RAS feature, complete the following steps:


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

Step 2 To verify the current state of the DSP RAS feature, enter the dspexecdiag command.

nodename.1.27.VISM8.a > dspexecdiag

LineNo/Ds0No      DSP Exec Status
------------      ---------------
1/ 1               Enable
1/ 2               Enable
1/ 3               Enable
1/ 4               Enable
1/ 5               Enable
1/ 6               Enable
1/ 7               Enable
1/ 8               Enable
1/ 9               Enable
1/10               Enable
1/11               Enable
1/12               Enable
1/13               Enable
1/14               Enable
1/15               Enable
1/16               Enable
1/17               Enable
1/18               Enable
1/19               Enable
1/20               Enable
1/21               Enable
1/22               Enable
1/23               Enable
1/24               Enable
1/25               Enable
1/26               Enable
1/27               Enable
1/28               Enable
1/29               Enable
1/30               Enable
1/31               Enable

Step 3 To disable the DSP RAS feature, enter the cnfexecdiag command.

nodename.1.27.VISM8.a > cnfexecdiag <execdiag>

Replace the <execdiag> argument with the value 2 for disable.


Note A delay of a few seconds occurs before the prompt displays.


Step 4 To verify that the DSP RAS feature is disabled, enter the dspexecdiag command.

nodename.1.27.VISM8.a > dspexecdiag

LineNo/Ds0No      DSP Exec Status
------------      ---------------
1/ 1               Disable
1/ 2               Disable
1/ 3               Disable
1/ 4               Disable
1/ 5               Disable
1/ 6               Disable
1/ 7               Disable
1/ 8               Disable
1/ 9               Disable
1/10               Disable
1/11               Disable
1/12               Disable
1/13               Disable
1/14               Disable
1/15               Disable
1/16               Disable
1/17               Disable
1/18               Disable
1/19               Disable
1/20               Disable
1/21               Disable
1/22               Disable
1/23               Disable
1/24               Disable
1/25               Disable
1/26               Disable
1/27               Disable
1/28               Disable
1/29               Disable
1/30               Disable
1/31               Disable

Step 5 To check for the timestamp setting, enter the dspcodecjtrdelays command.

nodename.1.27.VISM8.a > dspcodecjtrdelays

  codecType        delay mode        timestamp     initial delay  
-------------      -----------      ---------     -------------
 1 - G.711u           adaptive         N/A             seventy
 2 - G.711a           adaptive         N/A             seventy
 3 - G.726-32K        adaptive         N/A             seventy
 4 - G.729a            fixed           Yes              twenty
 5 - G.729ab          adaptive         N/A             seventy
 6 - clr chan         adaptive         N/A             seventy
 7 - G.726-16K        adaptive         N/A             seventy
 8 - G.726-24K        adaptive         N/A             seventy
 9 - G.726-40K        adaptive         N/A             seventy
11 - G.723.1-H        adaptive         N/A             seventy
12 - G.723.1a-H       adaptive         N/A             seventy
13 - G.723.1-L        adaptive         N/A             seventy
14 - G.723.1a-L       adaptive         N/A             seventy
15 - Lossless         adaptive         N/A             seventy

Step 6 To disable the fixed timestamp, enter the cnfplayouttimestamp command.

nodename.1.27.VISM8.a > cnfplayouttimestamp <codecType> <timestamp> <jitter_initdelay>

Replace the arguments with the values listed in Table 21. The following example shows the syntax for disabling the timestamp on the G.729a codec:

nodename.1.27.VISM8.a > cnfplayouttimestamp 4 1 20

Table 21 Parameters for the cnfplayouttimestamp Command 

Parameter
Description

codecType

Codec value.

1 = G.711u

2 = G.711a

3 = G.726-32K

4 = G.729a

5 = G.729ab

6 = Clear Channel (VAD must be off when codec is Clear Channel)

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

15 = Lossless (VAD must be off when codec is Lossless)

timestamp

Value to enable or disable timestamp.

1 = Disable

2 = Enable

jitter_initdelay

Initial jitter delay (defined in milliseconds). Ranges are

For codec templates 1, 3, 4, and 5—0-100 in increments of 10.

For codec template 2—0-100 in increments of 5.

For Lossless codec, range is 0-50.


Step 7 To verify that the timestamp is disabled, enter the dspcodecjtrdelays command.

nodename.1.27.VISM8.a > dspcodecjtrdelays

  codecType        delay mode        timestamp     initial delay  
-------------      -----------      ---------     -------------
 1 - G.711u           adaptive         N/A             seventy
 2 - G.711a           adaptive         N/A             seventy
 3 - G.726-32K        adaptive         N/A             seventy
 4 - G.729a            fixed            No              twenty
 5 - G.729ab          adaptive         N/A             seventy
 6 - clr chan         adaptive         N/A             seventy
 7 - G.726-16K        adaptive         N/A             seventy
 8 - G.726-24K        adaptive         N/A             seventy
 9 - G.726-40K        adaptive         N/A             seventy
11 - G.723.1-H        adaptive         N/A             seventy
12 - G.723.1a-H       adaptive         N/A             seventy
13 - G.723.1-L        adaptive         N/A             seventy
14 - G.723.1a-L       adaptive         N/A             seventy
15 - Lossless         adaptive         N/A             seventy


VISM/VISM-PR Upgrades with PXM1

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

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

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


Step 1 Log in to your TFTP server.

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

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

a. tftp <node_name or IP address>

b. bin

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

d. quit

Step 4 Download the selected firmware file.

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

a. tftp <node_name or IP address>

b. bin

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

quit

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

quit


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


Step 5 Proceed to the "Upgrade Boot Code with PXM1 Cards" section to install the download.


Upgrade Boot Code with PXM1 Cards

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


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



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


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


Step 2 Execute the PXM1 install command.

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

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

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

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


Note Step 3 is optional.



Upgrade VISM/VISM-PR Firmware with PXM1 Card

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

The following versions of VISM software Release 3.2.11 are available:

003.002.011.200—without CALEA

003.052.011.200—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.2 and prior.

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

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


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

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

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

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

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

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

Step 4 Execute the PXM install command.

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

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

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


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

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

Step 5 Execute the PXM newrev command.

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

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

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

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

Step 6 Execute the PXM commit command.

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

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

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

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

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


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


Step 8 Perform the following verifications:

Make minor modifications to the configuration.

Check that the changes have been executed correctly.

Change the configuration back again.



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


VISM-PR Upgrades with PXM1E and PXM45

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

If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.

Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.

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

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


Step 1 Access the image on the Cisco Web site.

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

ftp node-ip

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

Step 3 Enter your user name and password.

Step 4 Enter bin.

Step 5 Access the appropriate directory.

cd C:FW

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

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

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

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

Step 7 To exit the download procedure, enter bye.


Upgrade Boot Code with PXM1E and PXM45 Cards

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


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

Step 2 Log in to the PXM1E or PXM45 card.

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

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

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

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

The following example shows the burnboot.

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

The card in slot 12 will be reset.
burnboot:Do you want to proceed (Yes/No)? yes

For VISM-PR cards without redundancy, the card automatically resets and becomes active with the latest boot code image.

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


Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards

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

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

003.002.011.200—without CALEA

003.052.011.200—with CALEA

Perform the firmware upgrade on the VISM-PR cards.


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

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

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

nodename.1.7.PXM.a > saveallcnf

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

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

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

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


Caution Temporary traffic loss occurs.

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


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


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

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

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

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


Caution Temporary traffic loss occurs.

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


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


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

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

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

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

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

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


VISM/VISM-PR Downgrade Procedure

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


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


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


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

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

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

Step 3 Execute the PXM clrsmcnf command:

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

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

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

Step 4 Execute the PXM restoresmcnf command:


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

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

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

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

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


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


Step 5 Reconfigure the redundancy group, if required.


VISM to VISM-PR Hardware Upgrade

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


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


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

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

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

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

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

Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to 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 do not have other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.

Step 9 Remove a standby VISM card from your chassis.

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

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

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


Caveats in VISM Release 3.2.11

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

Resolved Caveats in 3.2.11

Table 22 describes the caveats that have been resolved in VISM/VISM-PR Release 3.2.11 as of July 30, 2004.

Table 22 Resolved Caveats in VISM/VISM-PR Release 3.2.11 

DDTS Issue
Description

CSCee33552

Fax fails after VISM software upgrade—VISM only.

CSCee51696

Keepalives lost when BPX AutoRoute restricted to static load.

CSCee54848

After softswitch, the call drops for 10s—VISM and VISM-PR.

CSCee58292

VISM 3.2.10 COT failure and unstable—VISM only.

CSCee66023

DSPs failed when running calls on Clear Channel with timestamp enabled.

CSCee92298

Change RAS default to disable and fixed timestamp to no timestamp.

CSCef23824

VISM card resets when multiple DSPs fail.

CSCef26389

Clock slips on VISM while running load.


Open Caveats in Release 3.2.11

Table 23 describes the open caveats in VISM/VISM-PR Release 3.2.11 as of July 30, 2004.

Table 23 Open Caveats in VISM/VISM-PR Release 3.2.11 

DDTS Issue
Description

CSCec54765

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

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

Workaround: Ensure DTMF digits being detected have an on-time value greater than 50-60 ms, preferably greater than 60 ms.

CSCec68687

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

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

Workaround: Take the gateway out of service and back in service to clear all the ports.

CSCed10672

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

Conditions: Call attempts beyond 217 active calls are rejected.

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

CSCed59217

Symptom: VISM-PR keeps sending DTMF digits when no digits are pressed.

Conditions: This symptom occurs by randomly pressing the digits on both on-net and off-net phone or pressing the combination of various digits at the same time. The VISM-PR could send out the DTMF payload type 101 packets every 50 ms (similar to retransmission) even though no digits are entered from the TDM side.

Workaround: Clear the problem by pressing another digit in the normal fashion.

CSCee03210

Symptom:T.38 interop fails between VISM and 2421.

Conditions: This problem occurs when running T.38 fax calls between VISM and 2421 or VISM and 3810 IAD, and T.38 packet level redundancy is enabled.

Workaround: Disable T.38 packet level redundancy when making fax calls.

CSCee22756

Symptom: Media Start package—Packet detector works only on the first DSP channel.

Conditions: The first RTP packet detected is not reported through the observed event on some DSP channels when requested by the media start package. Two or more DSP channels that are associated with endpoints will fail.

Workaround: Add approximately 68 endpoints. These endpoints will be associated with the first DSP channel.

For existing configurations, verify the endpoint associated with the first DSP channel before initiating a call with the media start package.

CSCee27874

Symptom: In the AAL2 trunking mode, insufficient bandwidth on one side causes downspeed failure.

Conditions: Configure the PCR on the originating side of the fax call to be very low, so the upspeed fails but fax relay goes through. On the terminating side, have enough bandwidth. Make a fax call. The terminating side fails to downspeed.

Workaround: None.

CSCee32065

Symptom: 911 operator ringback fails on VISM.

Conditions: When making a 911 call through a T1 CAS trunk on VISM, the operator ringback function does not work if the subscriber hangs up first. VISM does not send an offhook signal to the operator after receiving the MGCP resume signal from the call agent.

Workaround: None.

CSCee73314

Symptom: VISM reboots while adding the sesgrp with a 64 character call agent domain name.

Conditions: This problem occurs when the domain name does not exist (not added using adddn command).

Workaround: Add the domain name before adding the sesgrp.

CSCee92429

Symptom: Voice quality issues occur due to AAL2 packet drops.

Conditions: Configure 248 CIDs with G.711a 5 ms with VAD off and subcell muxing enabled from one VISM-PR-E1 to another VISM-PR-E1.

Delete some CIDs on one VISM-PR and re-add. The following errors are seen on other side: AAL2 HEC errors, AAL2 Invalid OSF cells, and Invalid length thus causing voice quality issue.

Workaround:

1. Turn subcell muxing off and/or turn VAD on.

2. Use G.729 or other 10 ms/20 ms codecs.

CSCef32606

Symptom: DSP stops responding to ping after re-download is initiated when DSPs failed.

Conditions: This condition is random. Some DSPs might or might not re-download. This issue happens when you have connections that are associated with the DSPs prior to the failure.

DSP status is not in active state.

Workaround: Reset the card.

CSCef39465

Symptom: HEC Errors and Invalid OSF Cell counters increment on all VISM connections.

Conditions: When the cell rate on one of the VISM connections exceeds the PCR value, HEC Errors and Invalid OSF Cell counters start incrementing on all of the connections of the VISM card.

This problem occurs only in AAL2 trunking mode with sub-cell multiplexing on.

Workaround: Have sufficient PCR values on all of the VISM connections, so the cell rates on any of the connections exceeds the PCR values.


Caveats in VISM Release 3.2.10

This section describes the open and resolved software caveats for VISM/VISM-PR Release 3.2.10.

Resolved Caveats in Release 3.2.10

Table 24 describes the caveats that have been resolved in VISM/VISM-PR Release 3.2.10 as of March 29, 2004.

Table 24 Resolved Caveats in VISM/VISM-PR Release 3.2.10 

DDTS Issue
Description

CSCdy60189

Problems with rsvpIftable.

CSCeb74938

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

CSCec01946

Low PESQLQ scores on the G.729ab codec.

CSCec33133

Inconsistence between CLI configuration and DSP configuration.

CSCec48230

Able to add VISM port via SNMP to standby card (no redundancy).

CSCec49168

Invalid entry—display_table error for dsprsvpreqs command.

CSCec50657

The ds0CasVariantName should not return a space char when not configured.

CSCec53676

The vismCodecJItterInitialDelay MIB missing values for lossless codec.

CSCec62223

MIB default value in dsx0VismCnfEntry should match those in the CLI.

CSCec72650

The rsvpIfRefreshMultiple and rsvpIfRefreshInterval MIB default values.

CSCec72690

The rsvpIfEnabled should be modifiable based on MIB definition.

CSCec72727

The rsvpifRefreshMultiple value during creation of rsvp session.

CSCec75409

SNMP error message giving incorrect index for mgcResolution.

CSCed02188

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

CSCed10636

Using cnfcalea to disable CALEA on (NO CALEA) image fails.

CSCed19772

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

CSCed26721

Enhance DSP RAS to send RSIP and update CID parameters on recovery.

CSCed32738

Card description is given VISM-8T1 in SNMP upload file for VISM-PR.

CSCed37101

Enhance VISM parsing of RTPMAP/FMTP order and change NTE default PT.

CSCed39900

SS7 through AAL2 trunking does not come up on reboot of VISM.

CSCed45837

VISM line goes in alarm when OAM loopback count is configured for 1.

CSCed56363

VISM dspconcac shows wrong bandwidth usage for standby AAL5 bearer PVC.

CSCed63277

VISM has dangling connection and does not respond to the DLCX.

CSCed64147

VISM sends NTFY first to the inactive call agent.

CSCed60427

VISM DSPs lock up.

CSCed66304

Video conference freezing under mixed traffic condition.

CSCed74024

T.38 CA controlled mode calls fail after successful initial run.

CSCed79847

G.726-XX not working as a VBD codec in VoIP Switching.

Recommendation:

When configuring VoIP for modem or fax upspeed (passthrough), set the EventNegoPolicy of the cnfvoiptransparams command to the value all.

This configuration is required for all related upspeed codecs to function correctly. Upspeed codecs are defined as the codecs that are switched to currently G.711a/u law, clear channel, or G.726).

Note When using G.726xx as the upspeed codec, you must follow this configuration procedure.

G.711 and clear channel function without using this configuration. However, it is recommended to use this configuration method for all upspeed functions.

CSCed89176

Walk on rsvpIfRefreshInterval does not work.

CSCin52221

CRCX2 is acked during codec negotiation instead of 534 error.

CSCin68700

VISM-PR: Adding rsc prtn with TAG controller should throw correct err.


Open Caveats in Release 3.2.10

Table 25 describes the open caveats in VISM/VISM-PR Release 3.2.10 as of July 2, 2004.

Table 25 Open Caveats in VISM/VISM-PR Release 3.2.10 

DDTS Issue
Description

CSCec54765

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

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

Workaround: Ensure DTMF digits being detected have an on-time value greater than 50-60ms, preferably greater than 60 ms.

CSCec68687

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

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

Workaround: Take the gateway out of service and back in service to clear all the ports.

CSCed10672

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

Conditions: Call attempts beyond 217 active calls are rejected.

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

CSCee03210

Symptom:T.38 interop fails between VISM and 2421.

Conditions: This problem occurs when running T.38 fax calls between VISM and 2421 or VISM and 3810 IAD, and T.38 packet level redundancy is enabled.

Workaround: Disable T.38 packet level redundancy when making fax calls.

CSCee22756

Symptom: Media Start package—Packet detector works only on the first DSP channel.

Conditions: The first RTP packet detected is not reported through the observed event on some DSP channels when requested by the media start package. Two or more DSP channels that are associated with endpoints will fail.

Workaround: Add approximately 68 endpoints. These endpoints will be associated with the first DSP channel.

For existing configurations, verify the endpoint associated with the first DSP channel before initiating a call with the media start package.

CSCee33552

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

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

Workaround: Adding endpoints one by one resolves the issue.

CSCee54848

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

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

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

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

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

Workaround: None.

CSCee58292

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

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

Workaround: None.

CSCee66023

Symptom: No voice path exists, and the DSP stops responding to ping when running in VoIP mode.

Conditions: Enable timestamp in fixed mode with clear channel codec.

Workaround: Disable timestamp.

CSCee92298

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

dspds0execdiag

dspexecdiag

dsplnexecdiag

dspcodecjtrdelays

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

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

cnfexecdiag

cnflnexecdiag

cnfds0execdiag

Use the cnfplayouttimestamp command to disable timestamp.

CSCee92429

Symptom: Voice quality issue due to AAL2 packet errors.

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

Workaround: None.


Caveats in VISM Release 3.2

This section describes the open and resolved software caveats for VISM/VISM-PR Release 3.2.

Resolved Caveats in Release 3.2

Table 26 describes the caveats that have been resolved in VISM/VISM-PR Release 3.2 as of March 3, 2004.

Table 26 Resolved Caveats in VISM/VISM-PR Release 3.2 

DDTS Issue
Description

CSCdx94130

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

CSCea42208

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

CSCea43230

VISM fail to boot on reset in PXM45 chassis.

CSCea64302

VISM resets while running T.38 VoIP trunking load.

CSCeb05718

VISM locks out trunk after wink failure.

CSCeb32754

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

CSCeb59727

Send proper Severity Value in VISM traps.

CSCec47585

VISM E1 legacy card boots when multiple endpoints are deleted

CSCec52528

Configuration GUI - Cannot configure resource partition for VISM.

CSCin48395

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

CSCuk44619

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

CSCuk44700

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

CSCdy34426

The cnflnoos state is not maintained after switchover.

CSCdy47135

SNMP cannot write to vismRtpPaylodType.

CSCdy50374

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

CSCdy78548

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

CSCdy89525

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

CSCdz64206

Degradation of voice quality when multiple announcement RQNTs are sent.

CSCdz68518

Failed to set objects in srcpPeerGrpParamTable.

CSCdz72726

Incorrect error description for ds0CasGlareTime configuration.

CSCdz73119

VISM requires RtpConnMode be mandatory for configuration: MIB change.

CSCea02640

RSVP session table shows non-existent sessions.

CSCea05685

Calls get stuck after IP connection from CA is lost.

CSCea24522

Make OAM loop back timer configurable.

CSCea38658

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

CSCea62890

DSP crashes after failed T.38 fax call timeout.

CSCea76010

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

CSCea78849

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

CSCea81110

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

CSCeb21008

MGX log shows tDspmCot CC-4-IDX_OUT_OF_RANG.

CSCeb33989

Loss of IP connectivity causes backhaul buffer leak.

CSCeb34686

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

CSCeb34708

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

CSCeb39267

SPINI failure.

CSCeb56424

Deleting DN before deleting domain IPs causes configuration problems.

CSCeb65531

The sarSlotNum always indicates 1.

CSCeb67558

VISM crash playing announcement to TDM side without connection.

CSCeb72094

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

CSCeb77691

VISM returns 510 error when parse SDP messages from 827.

CSCeb85639

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

CSCeb85676

VISM does not handle glare properly with FGD outgoing CAS.

CSCec01686

Missing concealment for lost RTP packets in VoIP.

CSCec08071

VISM does not collect digits if CRCX after RQNT.

CSCec26651

Reading vismDynamicPT MIB crashes VISM card.

CSCin38082

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

CSCuk42130

The dspxgcpcon CLI command reports wrong timestamp information.

CSCdz86155

Tone plan file written in DOS format is not parsed.

CSCdw48826

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

CSCdz85907

Tone plan with status lostFile cannot be deleted.

CSCea57223

VISM-E1 does not send correct idle pattern.

CSCea60784

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


Open Caveats in Release 3.2

Table 27 describes the open caveats in VISM/VISM-PR Release 3.2 as of July 2, 2004.

Table 27 Open Caveats in VISM/VISM-PR Release 3.2 

DDTS Issue
Description

CSCeb74938

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

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

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

CSCeb76617

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

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

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

CSCec01946

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

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

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

CSCec30727

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

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

Workaround: Reset the VISM-PR card.

CSCec54765

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

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

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

CSCec68687

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

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

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

CSCec79013

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

Conditions: PXM1 VISM VBR3nrt connections.

Workaround: None.

CSCed10672

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

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

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

CSCed02188

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

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

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

CSCed15923

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

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

Workaround: None for AAL2 trunking mode.

CSCed19772

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

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

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

CSCed21523

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

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

Workaround: Turn off redundancy.

CSCed22458

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

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

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

CSCed24074

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

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

Workaround: None.

CSCee33552

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

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

Workaround: Adding endpoints one by one resolves the issue.

CSCee54848

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

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

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

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

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

Workaround: None.

CSCee58292

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

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

Workaround: None.

CSCee92298

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

dspds0execdiag

dspexecdiag

dsplnexecdiag

dspcodecjtrdelays

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

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

cnfexecdiag

cnflnexecdiag

cnfds0execdiag

Use the cnfplayouttimestamp command to disable timestamp.

CSCee92429

Symptom: Voice quality issue due to AAL2 packet errors.

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

Workaround: None.


Related Documentation

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

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

Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5

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

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

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at 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 send 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, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

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

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

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

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

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—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.

Severity 2 (S2)—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.

Severity 3 (S3)—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.

Severity 4 (S4)—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. Visit Cisco Marketplace, the company store, at this URL:

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

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. 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

World-class networking training is available from Cisco. You can view current offerings at this URL:

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