Release Notes for Cisco Voice Interworking Service Module

Release Notes for Cisco Voice Interworking Service Module Release 3.2.10.202

These release notes are part number OL-5959-01 Rev. A0, June 30, 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 ContentsTable of Contents ............................................................................................................................... 1

About Release 3.2.10.202 .................................................................................................................. 3

About Release 3.2.10.201 .................................................................................................................. 3

About Release 3.2.10 ......................................................................................................................... 3

About Release 3.2 .............................................................................................................................. 4

Overview............................................................................................................................................. 4

New Features in Release 3.2.10 ........................................................................................................ 4

Non-Standard Law Companding................................................................................................. 5

Configure Law Companding................................................................................................. 5

Programmable CAS Signaling Bit Mapping................................................................................ 6

Configure CAS Signaling Bit Mapping Templates .............................................................. 6

Preferred Routes ....................................................................................................................... 11

Prerequisites ...................................................................................................................... 12

Configure Preferred Routes ............................................................................................... 12

E1 Trunk Conditioning ............................................................................................................... 17

cnflntrunkcond ................................................................................................................... 18

dspln................................................................................................................................... 18

Corporate Headquarters:

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

Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Table of Contents

Display All Static Configuration................................................................................................. 19

VoIP Switching/VoIP Trunking ............................................................................................ 20

AAL2 Trunking .................................................................................................................... 22

AAL1 Switching .................................................................................................................. 23

Switched AAL2 SVC ........................................................................................................... 24

Switched AAL2 PVC............................................................................................................ 25

VoIP and AAL1 SVC ............................................................................................................ 27

VoIP Trunking/AAL2 Trunking............................................................................................. 28

AIS Propagation Control............................................................................................................. 29

cnfaissuppression ............................................................................................................... 30

dspaissuppression .............................................................................................................. 31

dspconcnt............................................................................................................................ 31

Bandwidth Utilization Enhancements........................................................................................ 32

ATM Bandwidth Reuse for Non-overlapping Traffic.......................................................... 32

Dynamic PVC Bandwidth Management ............................................................................. 33

Channel Current Peak Rates ............................................................................................... 36

New Features in Release 3.2 ............................................................................................................ 37

VISM Management Information Base .............................................................................................. 37

VISM Redundancy ............................................................................................................................. 38

VISM Call Rate .................................................................................................................................. 38

Compatibility ..................................................................................................................................... 38

Limitations and Restrictions.............................................................................................................. 40

Upgrade Procedures .......................................................................................................................... 41

Prerequisites .............................................................................................................................. 42

Check Domain Name Length...................................................................................................... 42

VISM/VISM-PR Upgrades with PXM1 ....................................................................................... 44

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

Upgrade Boot Code with PXM1 Cards ............................................................................... 45

Upgrade VISM/VISM-PR Firmware with PXM1 Card......................................................... 45

VISM-PR Upgrades with PXM1E and PXM45............................................................................ 47

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

Upgrade Boot Code with PXM1E and PXM45 Cards.......................................................... 48

Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards............................................ 48

VISM/VISM-PR Downgrade Procedure...................................................................................... 49

VISM to VISM-PR Hardware Upgrade ....................................................................................... 50

Caveats for Release 3.2.10.202 ........................................................................................................ 51

Resolved Caveats for Release 3.2.10.202 ................................................................................. 51

Open Caveats for Release 3.2.10.202........................................................................................ 52

Resolved Caveat for Release 3.2.10.201 .......................................................................................... 53

2Release Notes for Cisco Voice Interworking Service Module Release 3.2.10.202

Part Number OL-5959-01 Rev. A0, June 30, 2004

About Release 3.2.10.202

Caveats for VISM Release 3.2.10..................................................................................................... 54

Resolved Caveats in Release 3.2.10 ......................................................................................... 54

Open Caveats in Release 3.2.10 ............................................................................................... 55

Caveats for VISM Release 3.2.......................................................................................................... 57

Resolved Caveats in Release 3.2 .............................................................................................. 57

Open Caveats in Release 3.2 .................................................................................................... 59

Related Documentation.................................................................................................................... 62

Obtaining Documentation................................................................................................................. 62

Cisco.com .................................................................................................................................. 63

Ordering Documentation ........................................................................................................... 63

Documentation Feedback ................................................................................................................. 63

Obtaining Technical Assistance ....................................................................................................... 63

Cisco TAC Website ................................................................................................................... 64

Opening a TAC Case ................................................................................................................. 64

TAC Case Priority Definitions.................................................................................................... 64

Obtaining Additional Publications and Information ......................................................................... 65

About Release 3.2.10.202VISM/VISM-PR Release 3.2.10.202 is a patch release and contains no new features. For a list of the open and resolved caveats in this release, see the “Caveats in Release 3.2.10.202” section on page 51.

Note The content of VISM/VISM-PR Release 3.2.10.202 supersedes Release 3.2.10.201.

About Release 3.2.10.201VISM/VISM-PR Release 3.2.10.201 is a patch release of Release 3.2.10 and contains no new features. For information on the resolved caveat, see the “Resolved Caveat in Release 3.2.10.201” section on page 53.

Note The content of VISM/VISM-PR Release 3.2.10.201 supersedes Release 3.2.10.

About Release 3.2.10VISM/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” section on page 4.

For a list of open and resolved caveats in this release, see “Caveats in VISM Release 3.2.10” section on page 54.



About Release 3.2

Note The content of VISM Release 3.2.10 supersedes previous releases.

About Release 3.2The VISM/VISM-PR Release 3.2 is a new release. For a list of new features, see “New Features in Release 3.2” section on page 37. For a list of the open and resolved caveats in this release, see “Caveats in VISM Release 3.2” section on page 57.

OverviewThese release notes contain the following sections:

• “New Features in Release 3.2.10” section on page 4

• “New Features in Release 3.2” section on page 37

• “VISM Management Information Base” section on page 37

• “VISM Redundancy” section on page 38

• “VISM Call Rate” section on page 38

• “Compatibility” section on page 38

• “Limitations and Restrictions” section on page 40

• “Upgrade Procedures” section on page 41

• “Caveats in Release 3.2.10.202” section on page 51

• “Resolved Caveat in Release 3.2.10.201” section on page 53

• “Caveats in VISM Release 3.2” section on page 57

• “Related Documentation” section on page 62

• “Obtaining Documentation” section on page 62

• “Documentation Feedback” section on page 63

• “Obtaining Technical Assistance” section on page 63

• “Obtaining Additional Publications and Information” section on page 65

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

• Non-Standard Law Companding, page 5

• Programmable CAS Signaling Bit Mapping, page 6

• Preferred Routes, page 11

• E1 Trunk Conditioning, page 17

• Display All Static Configuration, page 19



New Features in Release 3.2.10

• Bandwidth Utilization Enhancements, page 32

• AIS Propagation Control, page 29

Non-Standard Law CompandingIn standard law companding T1 lines support Mu Law, and E1 lines support A-Law.

In Release 3.2.10, VISM-PR supports non-standard law companding 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 Law Companding

To configure law companding 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 law companding, 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 law companding change to take effect, reset the VISM-PR card.

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

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

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

Replace <line_number> with the line number you configured law companding 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 MappingInternational 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 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 addcastranstbl 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 010 1 0 1 011 1 0 1 112 0 0 0 113 1 1 0 114 1 1 1 015 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 CasTblName0 E1toT1trans1 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


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


– 1–192 for T1

– 1–248 for E1







– 1–144 for VISM-PR




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






– 1–192 for T1

– 1–248 for E1














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






– 1–192 for T1

– 1–248 for 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


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.

Table 3 Parameters for addcon Command (Continued)





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|

|mbs| Maximum burst size (MBS)—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.

Table 3 Parameters for addcon Command (Continued)





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


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.

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.




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: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: FailedChanRTDresult: 65535 msChanPortNum: 255ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 29ChanLocalVci: 131ChanLocalNSAP: 47009181000000000164444b9400000107ebff00ChanRemoteVpi: 29ChanRemoteVci: 131ChanRemoteNSAP: 47009181000000000164444b9400000101180400ChanMastership: MasterChanVpcFlag: VccChanConnServiceType: CBR

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

Table 4 Parameters for cnfcon Command (Continued)





ChanRoutingPriority: 8ChanMaxCost: 2147483647ChanRestrictTrunkType: No Restriction

Type <CR> to continue, Q<CR> to stop:ChanConnPCR: 50000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 50000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 50000ChanMbsIngress: 50000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalsePref Rte Id : 777Directed Route: Yes

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

E1 Trunk ConditioningCurrently, 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

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

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





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: 1LineConnectorType: RJ-48LineEnable: EnabledLineType: dsx1ESFLineCoding: dsx1B8ZSLineLength: 0-131 ftLineXmtClockSource: LocalTimingLineLoopbackCommand: NoLoopLineSendCode: NoCodeLineUsedTimeslotsBitMap: 0x3LineLoopbackCodeDetection: codeDetectDisabledLineSignalingType: No SignalingLineCcsChannels: 0x0LineTrunkConditioning: disableLineBearerBusyCode: 255CircuitIdentifier: TxDigitOrder: aniThenDnisTonePlanRegion: TonePlanVersion: 0RingingTO: 180RingBackTO: 180

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

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

LineNumOfValidEntries: 8

Display All Static ConfigurationVISM/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: OffAAL2 CAS BITS TRANSPORT: OffAAL2 TYPE3 REDUNDANCY: OnAAL2 VAD TIMER: 250AAL2 CID FILL TIMER: 30

dspaissuppression--------------- ConnId ChanNum AIS Suppression Status AIS Delay Time ------ ------- ---------------------- --------------milwwi03.17.1.0.131 131 DISABLED 30milwwi03.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


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



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 law companding 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

Table 5 VoIP Switching/VoIP Trunking Display Commands (Continued)

Command Description




AAL2 Trunking

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

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

Table 5 VoIP Switching/VoIP Trunking Display Commands (Continued)

Command Description

Table 6 AAL2 Trunking Display Commands

Command Description

dspaal2params Display AAL2 parameters

dspaissuppression Display AIS suppression status



dspcastransendpts Display endpoints with their associated CAS mapping table names

dspcastranstbls Display list of the CAS mapping tables



dspccschans Display CCS channels

dspcids Display CIDs of LCN






dspendpts Display endpoints











AAL1 Switching

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

dspprofparams Display profile elements for all profiles






Table 6 AAL2 Trunking Display Commands (Continued)

Command Description

Table 7 AAL1 Switching Display Commands

Command Description

dspaggsvcbw Display configured bandwidth


























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.






dspsvcgw Display SVC gateway parameters

dspsvcqosparam Display Quality of Service parameters






Table 7 AAL1 Switching Display Commands (Continued)

Command Description

Table 8 Switched AAL2 SVC Display Commands

Command Description


dspaggsvcbw Display configured bandwidth

dspaissuppression Display AIS suppression settings











dspconvbdpol Display VBD policies for a connection






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.













dspprofparams Display profile parameters











Table 8 Switched AAL2 SVC Display Commands (Continued)

Command Description

Table 9 Switched AAL2 PVC Display Commands

Command Description






































dspvccis Display VCCI values






Table 9 Switched AAL2 PVC Display Commands (Continued)

Command Description




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

















dspendpts Display all endpoints


















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.













dspvoipparams Display VoIP mode parameters




Table 10 VoIP and AAL1 Display Commands (Continued)

Command Description

Table 11 VoIP Trunking/AAL2 Trunking Display Commands

Command Description
















AIS Propagation ControlCurrently, 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.



























Table 11 VoIP Trunking/AAL2 Trunking Display Commands (Continued)

Command Description




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


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 30nodename.1.12.VISM8.a >

The following example disables AIS suppression on all enabled PVCs:

nodename.1.12.VISM8.a > cnfaissuppression 2 ALLnodename.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 60nodename.1.12.VISM8.a >

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.




The following example disables AIS suppression on only PVC 131:

nodename.1.12.VISM8.a > cnfaissuppression 2 131nodename.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.


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

milwwi03.1.17.VISM8.a > dspaissuppression

ConnId ChanNum AIS Suppression Status AIS Delay Time ------ ------- ---------------------- --------------milwwi03.17.1.0.131 131 ENABLED 30milwwi03.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

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

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




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

nodename.1.12.VISM8.a > dspconcnt 131

ChanNum: 131Chan State: alarmChan XMT ATM State: Sending FERF OAMChan RCV ATM State: Receiving AIS OAMChan Status Bit Map: 0x6OAM Lpb Lost Cells: 89381AAL2 HEC Errors: 23540AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 33493675AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 1532756592AAL2 CPS Packet Rcv: 1820470968AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 3AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0AIS 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 EnhancementsVISM-PR Release 3.2.10 includes the following bandwidth utilization features:

• ATM Bandwidth Reuse for Non-overlapping Traffic, page 32

• Dynamic PVC Bandwidth Management, page 33

• Channel Current Peak Rates, page 36

ATM Bandwidth Reuse for Non-overlapping Traffic

This feature allows you to place an unused PVC out-of-service during non-service 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 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 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

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 12 Parameters for cnfcidis Command



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.

Table 13 Parameters for cnfcidoos Command



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 8LCN number : 131CID number: 8Endpoint number : 1CidRowStatus: activeType3redundancy: enabledVAD: disabledVADInitTimer: 250Profile type: ITUProfile number: 1Codec type: G.711uCas transport: disabledDTMF transport: enabledEcan on/off: enabledICS enable: Disabledpkt period: 5Cid state: FailedCid Fail Reason: SelfCid 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 131ChanNum: 131ChanRowStatus: ModChanLocalRemoteLpbkState: DisabledChanTestType: TestOffChanTestState: NotInProgressChanRTDresult: 65535 msChanPortNum: 1ChanPvcType: AAL2ChanConnectionType: PVCChanLocalVpi: 0ChanLocalVci: 131ChanLocalNSAP: 6d696c7777693033000000000000000015000100




ChanRemoteVpi: 0ChanRemoteVci: 0ChanRemoteNSAP: NULL NSAPChanMastership: SlaveChanVpcFlag: VccChanConnServiceType: CBRChanRoutingPriority: 8ChanMaxCost: 255ChanRestrictTrunkType: No RestrictionType <CR> to continue, Q<CR> to stop:ChanConnPCR: 10000ChanConnPercentUtil: 100ChanPreference: 1ChanRemotePCR: 10000ChanRemotePercentUtil: 100ChanProtection: unprotectedChanActivityState: unknownChanLockingState: unlockChanApplication: bearerChanServiceType: cbrChanScrIngress: 10000ChanMbsIngress: 10000ChanVCCI: 0ChanFarEndAddrType: notapplicableChanFarEndE164Addr: 0ChanFarEndGWIDAddr: .ChanFarEndNSAPAddr: NULL NSAPChanAdminStatus: UpChanReroute: FalseChanPrefRouteId: 0ChanDirectRoute: FalseType <CR> to continue, Q<CR> to stop:ChanUserPcrNumber: User BW OffChanUserMinPCRBW: 10ChanUserMaxPCRBW: 10000ChanUserMaxScrBW: 0ChanUserMaxMbsBW: 0ChanNumNextAvailable: 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:

nodename.1.12.VISM8.a > dspconcnt 131ChanNum: 131Chan State: alarmChan XMT ATM State: Sending FERF OAMChan RCV ATM State: OAM End-to-End Loopback FailureChan Status Bit Map: 0x4OAM Lpb Lost Cells: 406799AAL2 HEC Errors: 0AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 0AAL2 Invalid Parity Cells: 0



New Features in Release 3.2

AAL2 CPS Packet Xmt: 81848211AAL2 CPS Packet Rcv: 0AAL2 Invalid CID CPS: 0AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0Chan 24Hr Peak Xmt Cell Rate (CPS):185Chan Current Xmt Cell Rate (CPS):184Chan 24Hr Peak Rcv Cell Rate (CPS):0Chan Current Rcv Cell Rate (CPS):0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0


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

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

New Features in Release 3.2VISM 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 BaseThe VISM Management Information Base (MIB) Version 0.0.35 is available by request through your Cisco VISM product marketing representative.



VISM Redundancy

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

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 RateSoftware Release 3.2.10.202 for VISM/VISM-PR handles 10 CAS, SS7, or PRI calls per second per VISM/VISM-PR card.

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

Table 15 VISM/VISM-PR Software Interoperability

Product CW2000 Name Latest Firmware Minimum Firmware

PXM1 MGX 8250/MGX 8850 1.3.00 1.2.21

PXM1E MGX 8850/MGX 8830 5.0.00 4.0.151

PXM45 MGX 8850/MGX 8880 5.0.00 4.0.151

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



Compatibility

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

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

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

AXSM AXSM 5.0.00 4.0.151

CWM CWM 15.0 12.0 Patch 2

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.

Table 15 VISM/VISM-PR Software Interoperability (Continued)


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 VISM/VISM-PR Compatibility with Cisco MGX Chassis

Cisco MGX 8230 Cisco MGX 8250 Cisco MGX 8830Cisco 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 VISM/VISM-PR Release 3.2.10.202 Interoperability with Other Cisco Products


BTS BTS 10200 4.1.1V00 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



Limitations and Restrictions

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

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

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

Limitations and Restrictions

Note Release 3.2.10.202 does not contain any new limitations or restrictions. The same limitations and restrictions in 3.2.10 apply to this release.

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

• Cisco recommends that you use the cnfcodecjtrdelay command to configure the fixed jitter-delay argument to 20 msec when using VISM 3.2.10.202.

• In a PNNI network, upspeeding SVC fax or modem calls requires an increase in bandwidth between the voice codec and the vbd codec. For fax calls to go through, you must disable policing.

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

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

Product Name Software Image Firmware Description

MGX-VISM-SW3210 003.002.010.202.FW vism-8t1e1-003.002.010.202.fw This image does not support the CALEA1 feature.

1. CALEA = Commission on Accreditation for Law Enforcement Agencies.

MGX-VISM-LISW3210 003.052.010.202.FW vism-8t1e1-003.052.010.202.fw This image supports the CALEA2 feature.

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

Table 20 VISM/VISM-PR Software 3.2.10.202 Boot and Run-time Firmware Requirements

Board Pair Boot Code Version

MGX-VISM-8T1 vism_8t1e1_VI8_BT_3.2.00.fw

MGX-VISM-8E1 vism_8t1e1_VI8_BT_3.2.00.fw

MGX-VISM-PR-8T1 vism_8t1e1_VI8_BT_3.2.00.fw

MGX-VISM-PR-8E1 vism_8t1e1_VI8_BT_3.2.00.fw



Upgrade Procedures

• 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 VISM-PR cards that are running on a PXM45 chassis, you can add connections to a maximum of 11 VISM-PR cards.

To add more cards and connections, you must enable the expanded memory option on the PXM45 card by using the cnfndparms (option 4) command.

• For a list of open issues and mitigations in VISM Release 3.2.10.202, see “Open Caveats in Release 3.2.10.202” section on page 52.

Upgrade ProceduresThis section describes the following upgrade procedures:

• Prerequisites, page 42

• VISM/VISM-PR Upgrades with PXM1, page 44

• VISM-PR Upgrades with PXM1E and PXM45, page 47

• VISM/VISM-PR Downgrade Procedure, page 49

• VISM to VISM-PR Hardware Upgrade, page 50

VISM/VISM-PR Release 3.2.10.202 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.10.202



• From VISM 3.1(1) to VISM 3.2.10.202

• From VISM 3.1(2) to VISM 3.2.10.202


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



Upgrade Procedures

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

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

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

For more information on adding redundancy, refer to the add redundancy, addred, command in the 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.10.202 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.10.202, 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.10.202, add the domain names that are greater than 32 characters.

Check Domain Name LengthBefore you upgrade to 3.2.10.202, 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.



Upgrade Procedures

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 any entries exist for the domain name in Step 6a. to Step 6c., 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 on page 45 or “Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards” section on page 48.



Upgrade Procedures

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.

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

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

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

Step 1 Log in to your TFTP server.

Step 2 Download the bootcode and firmware images from the Cisco website.

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

a. tftp <node_name or IP address>

b. bin

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

d. quit

Step 4 Download the selected firmware file.

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

a. tftp <node_name or IP address>

b. bin



Upgrade Procedures

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

quit

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

quit

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

Step 5 Proceed to the “Upgrade VISM/VISM-PR Firmware with PXM1 Card” section on page 45 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.

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.10.202 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_VI8_BT_3.2.00.fw.



Upgrade Procedures

The following versions of VISM software Release 3.2.10.202 are available:

• 003.002.010.202.FW—without CALEA

• 003.052.010.202.FW—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.10.202.

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:

savesmcnf <SM slot#>

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

Step 3 Execute the PXM install command:

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

where:

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

Caution Ensure that you perform Step 3. If you do not perform Step 3 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 4 Execute the PXM newrev command:

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

where:

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

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

Step 5 Execute the PXM commit command:

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

where:

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



Upgrade Procedures

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

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

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

It is also recommended that you perform the following verifications:

• Make minor modifications to the configuration.

• Check that the changes have been executed correctly.

• Change the configuration back again.

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

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

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

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

Step 1 Access the image on the Cisco Web site.

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

ftp node-ip

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

Step 3 Enter your user name and password.

Step 4 Enter bin.

Step 5 Access the appropriate directory.

cd C:FW



Upgrade Procedures

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, page 47.

Step 2 Log in to the active 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 bootcode 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 vism_8t1e1_VI8_BT_3.2.00.fw.

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

• 003.002.010.202.FW—without CALEA

• 003.052.010.202.FW—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.



Upgrade Procedures

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

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

loadrev sm-primary-slot-num new-rev

where sm-primary-slot-num is the slot number of the VISM-PR card in which you want to install the new software; and new-rev is the new firmware version number for the VISM-PR software.

Caution Temporary traffic loss occurs.

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

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

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

runrev sm-primary-slot-num new-rev

Caution Temporary traffic loss occurs.

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

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

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

commitrev sm-primary-slot-num new-rev

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

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

VISM/VISM-PR Downgrade ProcedureUse this procedure to downgrade VISM/VISM-PR software from software Release 3.2.10.201 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.



Upgrade Procedures

Complete the following steps to downgrade the VISM/VISM-PR software from software Release 3.2.10.201 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.

delred <SM slot#>

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

Step 3 Execute the PXM clrsmcnf command:

clrsmcnf <SM slot#>

where:

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

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

Step 4 If you are using PXM1 cards in your chassis, execute the restoresmcnf command:

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

where:

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

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

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

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.

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

Step 5 Reconfigure the redundancy group, if required.

VISM to VISM-PR Hardware UpgradeComplete 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.



Caveats in Release 3.2.10.202


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 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 Release 3.2.10.202This section describes the resolved and open caveats in VISM/VISM-PR Release 3.2.10.202. Caveats describe unexpected behavior or defects in VISM software.

Resolved Caveats in Release 3.2.10.202Table 21 describes the resolved software caveats in VISM/VISM-PR Release 3.2.10.202 as of June 28, 2004.

Table 21 Resolved Caveats in VISM/VISM-PR Release 3.2.10.202

DDTS Issue Description

CSCee54848 After softswitch, the call drops for 10s.

CSCee55681 VISM changes codec from G.729 to G.711 during voice calls.



Caveats in Release 3.2.10.202

Open Caveats in Release 3.2.10.202Table 22 describes the open caveats in VISM/VISM-PR Release 3.2.10.202 as of June 28, 2004.

Table 22 Open Caveats in VISM/VISM-PR Release 3.2.10.202


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.



Resolved Caveat in Release 3.2.10.201

Resolved Caveat in Release 3.2.10.201Table 23 describes the resolved software caveat in VISM/VISM-PR Release 3.2.10.201 as of April 27, 2004.

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

• dspds0execdiag

• dspexecdiag

• dsplnexecdiag

• dspcodecjtrdelays

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

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

• cnfexecdiag

• cnflnexecdiag

• cnfds0execdiag

Use the cnfplayouttimestamp command to disable timestamp.

CSCee92429 Symptom: Voice quality issue due to AAL2 packet errors.

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

Workaround: None.

Table 22 Open Caveats in VISM/VISM-PR Release 3.2.10.202 (Continued)


Table 23 Resolved Caveat in VISM/VISM-PR Release 3.2.10.201


CSCee31685 VISM sends extra concealment when dejitter buffer initial delay is set to 20 ms, and 3 consecutive packets were lost.



Caveats in VISM Release 3.2.10

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

Resolved Caveats in Release 3.2.10Table 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


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.




Open Caveats in Release 3.2.10Table 25 describes the open caveats in VISM/VISM-PR Release 3.2.10 as of June 28, 2004.

CSCed79847 g726-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.

Table 24 Resolved Caveats in VISM/VISM-PR Release 3.2.10 (Continued)


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


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




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.









Workaround: None.



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.

Table 25 Open Caveats in VISM/VISM-PR Release 3.2.10 (Continued)




Caveats in VISM Release 3.2

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

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


• dspds0execdiag

• dspexecdiag

• dsplnexecdiag




• cnfexecdiag

• cnflnexecdiag

• cnfds0execdiag




Workaround: None.

Table 25 Open Caveats in VISM/VISM-PR Release 3.2.10 (Continued)


Table 26 Resolved Caveats in VISM Release 3.2


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.

Table 26 Resolved Caveats in VISM Release 3.2 (Continued)





Open Caveats in Release 3.2Table 27 describes the open caveats in VISM/VISM-PR Release 3.2 as of June 28, 2003.

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.

Table 26 Resolved Caveats in VISM Release 3.2 (Continued)


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


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.

Table 27 Open Caveats in VISM/VISM-PR Release 3.2 (Continued)





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.









Workaround: None.



Workaround: None.





Related Documentation

Related DocumentationThe following documents contains information that may be useful to software Release 3.2.10.202 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 DocumentationCisco 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.


• dspds0execdiag

• dspexecdiag

• dsplnexecdiag




• cnfexecdiag

• cnflnexecdiag

• cnfds0execdiag




Workaround: None.





Documentation Feedback

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

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

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

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

Ordering DocumentationYou 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 FeedbackYou can submit e-mail comments about technical documentation to [email protected].

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 SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

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



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

http://www.cisco.com

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

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

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

Obtaining Technical Assistance

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

http://www.cisco.com/tac

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

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

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

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

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

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

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

TAC Case Priority DefinitionsTo ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.



http://www.cisco.com/tac

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

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

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

Obtaining Additional Publications and Information

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

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

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

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

• Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

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

http://www.cisco.com/packet

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

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

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

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

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

CCSP, the Cisco Square Bridge logo, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0406R)

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



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

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

http://www.ciscopress.com

http://www.cisco.com/packet

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

http://www.cisco.com/ipj

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

Obtaining Additional Publications and Information



Documents

Release Notes for Cisco Voice Interworking Service Module