|
Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 3.3.35.203
New Features Introduced in Release 3.3.35.203
New Features Introduced in Release 3.3.35
New Features Introduced in Release 3.3.30
Enhanced Support for Controlling the EcanControl for Clearchannel Codec
Interoperability with 1AESS Switch
Configuring VISM for 1AESS Signaling
New Features Introduced in Release 3.3.25
VISM-PR Alarm Events Reported in the MGX Log File
Configurable Loopback Cell Priority
History Statistics Enhancement
VISM Management Information Base
VISM/VISM-PR Upgrades with PXM1
Downloading VISM/VISM-PR Boot Code and Firmware to PXM1
Upgrading Boot Code with PXM1 Cards
Upgrading VISM/VISM-PR Firmware with PXM1 Card
Upgrading VISM-PR with PXM1E and PXM45
Downloading VISM-PR Boot Code and Firmware to PXM1E and PXM45
Upgrading Boot Code with PXM1E and PXM45 Cards
Upgrading VISM-PR Firmware with PXM1E and PXM45 Cards
Upgrading VISM to VISM-PR Hardware
Resolved Caveats in Release 3.3.35.203
Open Caveats in Release 3.3.35.203
Resolved Caveats in Release 3.3.35
Open Caveats in Release 3.3.35
Resolved Caveats in Release 3.3.30
Open Caveats in Release 3.3.30
Resolved Caveats in Release 3.3.25
Open Caveats in Release 3.3.25
Resolved Caveats in Release 3.3.20
Open Caveats in Release 3.3.20
Resolved Caveats in Release 3.3.10
Open Caveats in Release 3.3.10
Resolved Caveats in Release 3.3
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Voice Interworking Service Module Release 3.3.35.203
Revised: June 2009, OL-19871-01
The Voice Interworking Service Module (VISM) product is supported by Cisco 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.3, which is available at Cisco.com.
Contents
The content of this document is arranged into the following major sections:
New Features Introduced in Release 3.3.35.203
New Features Introduced in Release 3.3.35
New Features Introduced in Release 3.3.30
Enhanced Support for Controlling the EcanControl for Clearchannel Codec
Interoperability with 1AESS Switch
Configuring VISM for 1AESS Signaling
New Features Introduced in Release 3.3.25
VISM-PR Alarm Events Reported in the MGX Log File
Configurable Loopback Cell Priority
History Statistics Enhancement
VISM Management Information Base
VISM/VISM-PR Upgrades with PXM1
Downloading VISM/VISM-PR Boot Code and Firmware to PXM1
Upgrading Boot Code with PXM1 Cards
Upgrading VISM/VISM-PR Firmware with PXM1 Card
Upgrading VISM-PR with PXM1E and PXM45
Downloading VISM-PR Boot Code and Firmware to PXM1E and PXM45
Upgrading Boot Code with PXM1E and PXM45 Cards
Upgrading VISM-PR Firmware with PXM1E and PXM45 Cards
Upgrading VISM to VISM-PR Hardware
Resolved Caveats in Release 3.3.35.203
Open Caveats in Release 3.3.35.203
Resolved Caveats in Release 3.3.35
Open Caveats in Release 3.3.35
Resolved Caveats in Release 3.3.30
Open Caveats in Release 3.3.30
Resolved Caveats in Release 3.3.25
Open Caveats in Release 3.3.25
Resolved Caveats in Release 3.3.20
Open Caveats in Release 3.3.20
Resolved Caveats in Release 3.3.10
Open Caveats in Release 3.3.10
Resolved Caveats in Release 3.3
Obtaining Documentation, Obtaining Support, and Security Guidelines
About Release 3.3.35.203
VISM/VISM-PR Release 3.3.35.203 is a maintenance release of Release 3.3.35 and contains no new feature for VISM-PR.
For a list of the caveats in this release, see the "Caveats in Release 3.3.35.203" section.
About Release 3.3.35
VISM/VISM-PR Release 3.3.35 is a maintenance release of Release 3.3.30 and contains new features for VISM-PR. For a description of these features, see the "New Features Introduced in Release 3.3.35" section.
For a list of the caveats in this release, see the "Caveats in Release 3.3.35" section.
About Release 3.3.30
VISM/VISM-PR Release 3.3.30 is a maintenance release of Release 3.3.25 and contains new features for VISM-PR. For a description of this feature, see the "New Features Introduced in Release 3.3.30" section.
For a list of the caveats in this release, see the "Caveats in Release 3.3.30" section.
About Release 3.3.25
VISM/VISM-PR Release 3.3.25 is a maintenance release of Release 3.3.20 and contains new features for VISM-PR. For a description of these features, see the "New Features Introduced in Release 3.3.25" section.
For a list of the resolved caveats in this release, see the "Resolved Caveats in Release 3.3.25" section.
About Release 3.3.20
VISM/VISM-PR Release 3.3.20 is a maintenance release of Release 3.3 and contains the following new features:
•1560/980 Hz modem tones
•VQT statistics
•V.110
Note For a description of these features, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3.
For a list of the open and resolved caveats in this release, see the "Caveats in Release 3.3.20" section.
About Release 3.3.10
The VISM/VISM-PR Release 3.3.10 is a maintenance release of Release 3.3 and contains no new features. For a list of the open and resolved caveats in this release, see "Caveats in Release 3.3.10" section.
About Release 3.3
VISM/VISM-PR Release 3.3 is a new release. Table 1 summarizes the new features in VISM/VISM-PR Release 3.3.
Note For a description of these features, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3.
For a list of the open and resolved caveats this release, see "Caveats in Release 3.3" section.
Note The content of VISM Release 3.3 supersedes previous releases.
Overview
These release notes contain the following sections:
•"New Features Introduced in Release 3.3.35.203" section
•"New Features Introduced in Release 3.3.35" section
•"New Features Introduced in Release 3.3.30" section
•"New Features Introduced in Release 3.3.25" section
•"VISM Management Information Base" section
•"Limitations and Restrictions" section
•"Caveats in Release 3.3.35.203" section
•"Caveats in Release 3.3.35" section
•"Caveats in Release 3.3.30" section
•"Caveats in Release 3.3.20" section
•"Caveats in Release 3.3.10" section
•"Caveats in Release 3.3" section
•"Related Documentation" section
•"Obtaining Documentation, Obtaining Support, and Security Guidelines" section
New Features Introduced in Release 3.3.35.203
None.
New Features Introduced in Release 3.3.35
This section describes the following new features:
SNMP Support for Card Uptime
SNMP support is provided to the command dspcduptime. The dspcduptime command displays how long the card has been in the up condition. To add support for this feature, the object cefcModuleUptime is used. The MIB object returns only the system clock ticks. The operator has to find out the system availability using the clock ticks.
The following example shows the output of the command:
VISM8.a > dspcduptime
10 Days 16 Hours 58 Minutes 22 Seconds
New Features Introduced in Release 3.3.30
This section describes the following new features:
•Enhanced Support for Controlling the EcanControl for Clearchannel Codec
•Interoperability with 1AESS Switch
G.723 codec for VoATM
Release 3.3.30 supports the G.723 codec with upspeed option for VoATM circuits. G.723 codecs with a packetization period of 30 ms can reduce the bandwidth requirements for voice traffic and improve the bandwidth utilization of existing AAL2 trunks. To support fax/data modem traffic, an upspeed procedure can change from G.723 to G.711 after detection of fax/data modem tones. For more information about the upspeed option, see the "Codec Upspeed for Fax Modems" section.
A new custom profile supports the G.723 codec for VoATM. Table 2 shows the default values for custom profile 211.
The following commands are modified to accommodate custom profile 211. In each case, the command has a new parameter for selecting custom profile 211. The MIB for Release 3.3.30 supports this profile as well.
cnfprofparams
To configure a profile preference for a channel, use the cnfprofparams command.
cnfprofparams <profileType> <profileNumber> <profilePreference>
Syntax Description
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
Follow standard CLI procedures for this command.
Examples
In the following example, the ITU profile type, profile number 1 is configured with the midrange preference level of 4:
nodename.1.27.VISM8.a > cnfprofparams 1 1 4nodename.1.27.VISM8.a >Use the dspprofparams command to view the profile parameters.
Related Commands
cnfprofelemvoice
To configure the profile voice element, use the cnfprofelemvoice command.
cnfprofelemvoice <profileType> <profileNumber> <voice_codec_type> <pktPeriod> <sid>
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
Use the dspaal2profile command to identify valid combinations of codec type, packetization period, and SID.
The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.
Examples
In the following example, the ITU profile type on profile number 1 is configured with the G.711a codec type, a packetization period of 5 ms, and VAD enabled:
nodename.1.27.VISM8.a > cnfprofelemvoice 1 1 2 5 2nodename.1.27.VISM8.a >Use the dspprofparams to view your configurations.
Related Commands
cnfprofelemvbd
To configure the voiceband data (VBD) profile element for a profile, use the cnfprofelemvbd command.
cnfprofelemvbd <profileType> <profileNumber> <codecType> <pktPeriod>
Syntax Description
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
Use the dspaal2profile command to identify valid combinations of codec type, packetization period, and silence insertion descriptor.
The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.
Examples
In the following example, the ITU profile type, profile number 1 is configured with G.711a codec type and a 5-ms packetization period:
nodename.1.27.VISM8.a > cnfprofelemvbd 1 1 2 5nodename.1.27.VISM8.a >Use the dspprofparams to view your configurations.
Related Commands
Command DescriptionConfigures the voice profile element for a profile.
Displays AAL2 profile type and profile number data.
Displays the profile elements and the preferences for all profiles.
dspprofparams
To display the profile elements and the preferences for all profiles, use the dspprofparams command.
dspprofparams
Syntax Description
This command has no arguments or keywords.
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
When you execute this command, the display includes the default voice and voiceband data profile element that corresponds to each supported profile.
Examples
In the following example, the profile elements and preferences for all profiles are displayed:
nodename.1.5.VISM8.a > dspprofparams- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 1Profile Preference : 4Voice Profile Codec : G.711uVoice Profile Packetization-period(ms): fiveVoice Profile SID : VAD onVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 2Profile Preference : 3Voice Profile Codec : G.711uVoice Profile Packetization-period(ms): fiveVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 3Profile Preference : 1Voice Profile Codec : G.726-32KVoice Profile Packetization-period(ms): fiveVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 7Profile Preference : 2Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 8Profile Preference : 5Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : ITUProfile Number : 12Profile Preference : 10Voice Profile Codec : G.723.1a-HVoice Profile Packetization-period(ms): thirtyVoice Profile SID : sid723VBD Profile Codec : G.723.1-HVBD Profile Packetization-period (ms) : thirtyVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 100Profile Preference : 6Voice Profile Codec : G.726-32KVoice Profile Packetization-period(ms): tenVoice Profile SID : sidGenricVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 101Profile Preference : 7Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): tenVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 110Profile Preference : 8Voice Profile Codec : G.729abVoice Profile Packetization-period(ms): thirtyVoice Profile SID : sid729VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 200Profile Preference : 9Voice Profile Codec : clr chanVoice Profile Packetization-period(ms): fiveVoice Profile SID : VAD offVBD Profile Codec : clr chanVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 201Profile Preference : 11Voice Profile Codec : LosslessVoice Profile Packetization-period(ms): fiveVoice Profile SID : VAD offVBD Profile Codec : LosslessVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 210Profile Preference : 12Voice Profile Codec : G.729aVoice Profile Packetization-period(ms): twentyVoice Profile SID : VAD offVBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enable- - - - - - - - - - - - - - - - - - - - - -Profile Type : CustomProfile Number : 211Profile Preference : 13Voice Profile Codec : G.723.1a-HVoice Profile Packetization-period(ms): thirtyVoice Profile SID : sid723VBD Profile Codec : G.711uVBD Profile Packetization-period (ms) : fiveVBD Profile Ecan Control : enableRelated Commands
Command DescriptionConfigures the VBD profile element for a profile.
Configures the voice profile element for a profile.
Configures a profile preference.
dspaal2profile
To display data about a specified AAL2 profile type and profile number, use the dspaal2profile command.
dspaal2profile <profileType> <profileNumber>
Syntax Description
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
The AAL2 profiles correspond to the profile types ITU and ATMF as defined in the ITU-T I.366.2 and ATM forum AF-VTOA-0113 standards.
Examples
In the following example, the data for AAL2 profile type 3 and profile number 110 is displayed:
nodename.1.5.VISM8.a > dspaal2profile 3 211UUI Packet Packet Seq. No.Codepoint Length Time IntervalRange (octets) Codec SID M (ms) (ms)8-15 40 PCMU No SID 1 5 58-15 40 PCMA No SID 1 5 50-7 40 CCD No SID 40 5 50-15 24 G723AH SID723 1 30 50-15 24 G723H No SID 1 30 50-15 20 G723AL SID723 1 30 50-15 20 G723L No SID 1 30 5nodename.1.5.VISM8.a >Related Commands
There are no related commands.
Enhanced Support for Controlling the EcanControl for Clearchannel Codec
In Releases 3.3.10 and earlier, when a channel is configured to use clearchannel as the voiceband data (VBD) codec, the value of Ecan cancellation is not changed. Therefore, if the initial call was set up with echo cancellation on, it remains remain on even after upspeed to clearchannel.
Cisco recommends having Ecan cancellation off with clearchannel because the CCD vbd codec should be used for carrying transparent bit streams. With Ecan cancellation off, transparent bit streams are passed transparently through VISM without modification by echo cancellers.
In Release 3.3.20, as a fix for DDTS CSCef12950, when a channel is configured to use clearchannel as VBD codec, echo cancellation is set to off for that channel.
However, some fax adapters (Gammalink and Brooktrout) require Ecan cancellation to be on to eliminate echo on the tail circuit. To accommodate such fax adapters, Release 3.3.30 adds a parameter to the VBD codec commands to enhance control of the Ecan cancellation.
By default the EcanControl parameter is set to true for Clearchannel (Ecan Cancellation is turned off). For fax adapters that require echo cancellation, set EcanControl to false (Ecan cancellation remains unchanged).
Release 3.3.30 modifies the following commands to enhance echo cancellation control for clearchannel as the VBD codec.
•cnfvbdcodec—Configures Ecan Validation in VOIP mode
A new argument enables or disables Ecan validation for a clearchannel voiceband data (VBD) codec.
•dspvbdcodec—Displays Ecan Validation in VOIP mode
A new line displays the Ecan control state.
•cnfprofelemvbd—Configures Ecan Validation in AAL2 mode
A new argument enables or disables Ecan validation for a VBD profile.
•dspprofparams—Displays Ecan Validation in AAL2 mode
A new line displays the Ecan control state.
cnfvbdcodec
To configure voiceband data (VBD) upspeed codec on the VISM card, use the cnfvbdcodec command.
cnfvbdcodec <upspeedCodec> | <payload> <ecan_control> |
Syntax Description
Command Modes
VoIP switching/VoIP trunking
Usage Guidelines
VISM uses the configured codec even if, for example, the configured codec is G.726-32k and VISM is preconfigured with G.711.
If you configure clear channel, VISM does support a mixed system clock—VISM cannot be originated at a T1 line and terminated at an E1 line, or originated at an E1 line and terminated at a T1 line.
When VISM is configured with clearchannel VBD codec, the ecan_control parameter enables or disables Ecan validation. If ecan_control is enabled (default), then while upspeeding to clearchannel VBD codec, Ecan is disabled. If ecan_control is disabled, then while upspeeding to clearchannel VBD codec, Ecan is not disabled and the behavior remains as it was in release 3.2.11.
In AAL2 modes the VISM obtains the upspeed codec from the AAL2 profile table. AAL1 modes do not support compression and therefore do not require upspeed.
The G.723.1 codecs are supported for VISM-PR cards only.
Note We recommend that you not use upspeedCodec argument values 5 or 6 with this command.
Examples
In the following example, the VBD upspeed codec is configured as clearchannel, is assigned payload type 182, and Ecan validation is disabled:
nodename.1.27.VISM8.a > cnfvbdcodec 4 128 2nodename.1.27.VISM8.a >Related Commands
dspvbdcodec
To display the upspeed codec used for voiceband data (VBD) and the payload type, use the dspvbdcodec command.
dspvbdcodec
Syntax Description
This command has no arguments or keywords.
Command Modes
VoIP switching/VoIP trunking
Usage Guidelines
Follow standard CLI procedures for this command.
Examples
In the following example, the upspeed codec used for VBD, the default payload type, and Ecan Control appear:
nodename.1.28.VISM8.a > dspvbdcodecVBD UpSpeed Codec: ClearChannelPayload Type : 128Ecan Control : disablenodename.1.28.VISM8.a >Related Commands
cnfprofelemvbd
To configure the voiceband data (VBD) profile element for a profile, use the cnfprofelemvbd command.
cnfprofelemvbd <profileType> <profileNumber> <codecType> <pktPeriod> <ecan_control>
Syntax Description
Command Modes
AAL2 trunking, switched AAL2 SVC and switched AAL2 PVC
Usage Guidelines
Use the dspaal2profile command to identify valid combinations of codec type, packetization period, and silence insertion descriptor.
The G.723.1 codecs are supported for VISM-PR cards and are not supported for VISM cards.
When VISM is configured with clearchannel VBD codec, the ecan_control parameter enables or disables Ecan validation. If ecan_control is enabled (default), then while upspeeding to the clearchannel VBD codec, Ecan is disabled. If ecan_control is disabled, then while upspeeding to clearchannel VBD codec, Ecan is not disabled and the behavior remains as it was in release 3.2.11.
Examples
In the following example, the ITU profile type, custom profile number 100 is configured for a clearchannel codec type, a 5-ms packetization period, and disables Ecan validation:
nodename.1.27.VISM8.a > cnfprofelemvbd 3 100 6 5 2nodename.1.27.VISM8.a >Use the dspprofparams to view your configurations.
Related Commands
Codec Upspeed for Fax Modems
Release 3.3.30 has a new command (cnflnfaxmodem) that enables or disables the upspeed procedure after detection of fax/modem tones. The dspln command displays the fax/modem control.
cnflnfaxmodem
To enable or disable the upspeed procedure for a line, use the cnflnfaxmodem command.
cnflnfaxmodem <line_number> <faxModemType>
Syntax Description
line_number
Number of the line you to configure. Range is 1-8.
faxModemType
Controls the upspeed procedure. Values are:
•1 = Enable
•2 = Disable
Default: 1
Command Modes
VoIP switching/VoIP trunking, AAL2 trunking, switched AAL2 SVC, switched AAL2 PVC, and VoIP trunking/AAL2 trunking
Usage Guidelines
The cnflnfaxmodem command enables or disables the upspeed procedure for all DS0s on the specified line. To view the current setting for a line, enter the dspln command.
Examples
In the following example, the upspeed procedure is disabled for line 1:
nodename.1.27.VISM8.a > cnflnfaxmodem 1 2Related Commands
Note For an example of the dspln comand showing the status of LineFaxModem, see dspln.
Interoperability with 1AESS Switch
Release 3.3.30 extends VISM signaling capabilities to include interoperation with 1AESS switches.
1AESS Signaling Overview
The Lucent 1AESS local exchange telephone switching system was widely deployed in the 1970s across what was then the Bell System. Most 1AESS switches are replaced by the next-generation digital switches, such as the Lucent 5ESS and Nortel DMS-100. While few 1AESS switches remain, those still in service are generally heavily built-out. About 2 to 5 percent of lines are on 1AESS switches.
Service providers that offer wholesale dial, Internet/intranet, and access virtual private networks (VPNs) require remote access and expect to provide widely available service at the lowest cost. To do so, they must have Signaling System 7 (SS7) trunks to each local exchange in a service area. And for Internet service providers (ISP) or competitive local exchange carriers (CLEC) that want 100 percent dial coverage, an interface to the remaining 1AESS switches is mandatory.
Even though 1AESS switches use out-of-band SS7 signaling, they cannot disable robbed-bit signaling (RBS). Therefore, gateways that connect to the 1AESS switch must send a steady A/B bit status on specific SS7-controlled lines to prevent the 1AESS tandem from bringing trunks down and placing them in the out-of-service state. Any fluctuation in the received A/B bits might force the entire line on a 1AESS switch into the out-of-service state. To address the sensitivity of 1AESS switch to A/B bits, the connected MGX switch must send a steady stream of A/B bits towards 1AESS switch that corresponds the activity (call setup, call tear down, COT operations) on the DS0.
Configuring VISM for 1AESS Signaling
For VISM to interoperate with the 1AESS switch, you configure the VISM module to send a specific, steady A/B/C/D bit pattern to the 1AESS switch when the call is active (seize pattern) and another steady A/B/C/D bit pattern when there is no call (idle pattern). The cnflnsig command has a new signaling_type option for enabling this feature, and the dspln command displays the corresponding LineSignalingType.
Note The 1AESS feature is supported in VOIP switching mode only. Do not configure 1AESS signaling in any other mode (CSCek38088).
cnflnsig
To configure the signaling mode for a VISM/VISM-PR line, use the cnflnsig command.
cnflnsig <line_number> <signaling_type>
Syntax Description
Command Modes
VoIP switching/VoIP trunking, AAL2 trunking, AAL1 switching, switched AAL2 SVC, switched AAL2 PVC, VoIP and AAL1 SVC, and VoIP trunking/AAL2 trunking
Usage Guidelines
Confirm your entry when using this command to ensure that the signaling type is not changed while endpoints are configured for the line indicated by the line_number argument.
This command is not allowed when CIDs or CCS channels are present.
Configure the line type as either E1MF or E1MFCRC for E1 lines. Otherwise, this command is invalid.
Examples
In the following example, line 1 is configured for 1AESS:
nodename.1.27.VISM8.a > cnflnsig 1 4nodename.1.27.VISM8.a >Related Commands
dspln
To display the configuration data of a VISM card line, use the dspln command.
dspln <line_number>
Syntax Description
Command Modes
VoIP switching/VoIP trunking, AAL2 trunking, AAL1 switching, switched AAL2 SVC, switched AAL2 PVC, VoIP and AAL1 SVC, and VoIP trunking/AAL2 trunking
Usage Guidelines
Follow standard CLI procedures for this command.
Examples
In the following example, the configuration data for line number 1 is displayed:
nodename.1.27.VISM8.a >dspln 1LineNum: 1LineConnectorType: RJ-48LineEnable: ModifyLineType: dsx1ESFLineCoding: dsx1B8ZSLineLength: 0-131 ftLineXmtClockSource: LocalTimingLineLoopbackCommand: NoLoopLineSendCode: NoCodeLineUsedTimeslotsBitMap: 0x0LineLoopbackCodeDetection: codeDetectDisabledLineSignalingType: 1AESSLineCcsChannels: 0x0LineTrunkConditioning: disableLineBearerBusyCode: 127CircuitIdentifier:TxDigitOrder: aniThenDnisTonePlanRegion:TonePlanVersion: 0RingingTO: 180RingBackTO: 180Type <CR> to continue, Q<CR> to stop:BusyTO: 30ReorderTO: 30DialTO: 16StutterDialTO: 16OffHookAlertTO: 5RemoteRingbackMethod: proxyLineV110EnableFlag: disableLineFaxModem: enableLineNumOfValidEntries: 8nodename.1.27.VISM8.a >Related Commands
Command DescriptionAdds a T1 or E1 line to a VISM card.
cnfln
Configures characteristics for a VISM card line.
delln
Deletes a T1 or E1 line from a VISM card.
New Features Introduced in Release 3.3.25
This section contains the description of the following new features:
•"SPVC Capacity Expansion" section
•"VISM-PR Alarm Events Reported in the MGX Log File" section
•"Configurable Loopback Cell Priority" section
•"History Statistics Enhancement" section
SPVC Capacity Expansion
In this release, you can now configure a maximum of 248 PVCs on a VISM-PR-8E1 card and a maximum of 192 PVCs on a VISM-PR-8T1 card. The cards must be running in the AAL2 trunking mode.
Prior to Release 3.3.25, you could configure a maximum of 64 PVCs on a VISM-PR card.
With the increase in SPVC capacity now supported, you have the option of assigning each DS0 to a separate PVC.
VISM-PR Alarm Events Reported in the MGX Log File
Prior to Release 3.3.25, VISM-PR reported the Receive Line alarms to the PXM log file.
In Release 3.3.25, in addition to the Receive Line alarms, VISM-PR reports the following alarms in the PXM log file:
•Transmitted Line alarms
•Transmitted and Received PVC alarms
•Transmitted and Received Ds0 alarms
The reporting of these alarms is applicable to all of the VISM-PR modes.
The following new commands support this feature:
By default, the alarm log is disabled on all the lines, and the timer is set to 0.
cnflnalmlog
To enable or disable the reporting of VISM-PR line alarms to the PXM log file, use the cnflnalmlog command.
nodename.1.27.VISM8.a > cnflnalmlog <line_number> <logEnab> |LogTimer|Replace the above arguments with the values listed in Table 3.
In the following example, DS0-based alarm logging is enabled on line 1 for 1440 minutes (1 day):
nodename.1.27.VISM8.a > cnflnalmlog 1 1 1440
cnfpvcalmlog
To enable or disable the reporting of the alarms for all of the PVCs on a VISM-PR card to the PXM log file, use the cnfpvcalmlog command.
nodename.1.27.VISM8.a > cnfpvcalmlog <logEnab> <LogTimer>Replace the above arguments with the values listed in Table 4.
In the following example, alarm logging for all PVCs is enabled on line 1440 minutes (1 day):
nodename.1.27.VISM8.a > cnfpvcalmlog 1 1440
cnfallalmlog
To enable or disable the reporting of alarms on all of the lines and PVCs to the PXM log file, use the cnfallalmlog command. The default reporting time is 7200 minutes (5 days).
nodename.1.27.VISM8.a > cnfallalmlog <logEnab>Replace the <logEnab> argument with one of the following values to enable or disable the alarm reporting for all of the lines and PVCs on the VISM-PR card:
•1 = Enable
•2 = Disable
In the following example, alarm logging for all of the lines and PVCs on a VISM-PR card is enabled.
nodename.1.27.VISM8.a > cnfallalmlog 1nodename.1.27.VISM8.a >This command is valid when all of the lines on the card are enabled.
dspalmlog
To display the current settings for reporting VISM-PR line and PVC alarms to the PXM log file, use the dspalmlog command.
nodename.1.27.VISM8.a > dspalmlog
In the following example, the line and PVC alarm reporting settings are displayed:
8850.1.1.VISM8.a > dspalmlogDetailed PVC Alarms to Log: Enabled-----------------------------------Alarm Time Configured(minutes) Alarm Time Left(minutes)============================== ================================7200 7200Detailed Line Alarms to Log-----------------------------Line Number Timer Configured(minutes) Time Left(minutes)========== =============================== ========================1 1440 14402 7200 71983 Disabled4 Disabled5 Disabled6 Disabled7 Disabled8 DisabledConfigurable Loopback Cell Priority
The ATM OAM loopback cell is used to monitor the end to end connectivity of the PVC in an ATM network.The cell loss priority (CLP) bit in the ATM header is used to set the priority of the cell. A cell with CLP set to 0 has higher priority compared to a cell with CLP set to 1. During traffic congestion events, the lower priority cells are eligible first for discard.
The ATM OAM loopback cells in the VISM-PR card have the cell loss priority (CLP) bit set to 1 by default. These cells can be discarded during traffic congestion even though the class of service is configured to be constant bit rate (CBR). This discard can cause the SPVCs to go into alarm as a result of an OAM loopback timeout, which could result in the dropping of all calls on the SPVCs.
In Release 3.3.25, you can set the CLP bit of an OAM loopback cell to 0 on a VISM-PR card. This setting is propagated across the network to preserve the calls during traffic congestion.
CLP bit configuration is applicable to the OAM loopback cells in all configured PVCs of a VISM-PR card.
To configure the loopback cell priority, complete the following steps:
Step 1 Ensure you are logged in to a VISM-PR card and are operating in the VoIP switching/trunking or AAL2 trunking mode.
Step 2 To set the CLP bit in the OAM cell, enter the cnfoamloopbkclp command.
nodename.1.27.VISM8.a > cnfoamloopbkclp <ClpSetFlag>Replace the <ClpSetFlag> argument with one of the following values:
•1 = Enable (default). The CLP bit of the OAM cell is set to 1.
•2 = Disable. The CLP bit of the OAM cell is set to 0.
Step 3 To display the CLP bit settings for the OAM loopback cell, enter the dspvismparam command.
The following example shows the CLP bit of the OAM cell is set to 0.
nodename.1.27.VISM8.a > dspvismparam
VISM mode: voipSwitching/voipTrunkingVISM features Bit Map: 0x5bcFunctionModuleType: VISM-PR-8T1CAC flag: enableDS0s available: 192Template number: 2Percent of functional DSPs: 100IP address: 20.25.14.99Subnet mask: 255.255.255.0Bearer IP address: 0.0.0.0Bearer Subnet mask: 0.0.0.0Bearer IP ping: disableRTCP report interval: 5000 msecRTCP receive multiplier: 3RTP receive timer: disableControlPrecedence/Tos: 0x60BearerPrecedence/Tos: 0xa0Aal2 muxing status: disableTftp Server Dn TFTPDOMAINAggregate Clipping enableType <CR> to continue, Q<CR> to stop:Aggregate Svc Bandwidth 0Codec negotiation option 1Profile negotiation option 1VAD Duty Cycle 61VAD Tolerance 100VISM Initiated NW COT OffVISM CO4 Timer 1000 msecCALEA flag disableOam Loopback CLP Bit 0
Continuity Check Cell 1SupportdModuleType: VISM-PR-8T1.VismNSAP: 3838353000000000000000000000000001000100History Statistics Enhancement
In Release 3.3.25, the VISM-PR card can collect the following new statistics:
•OAM Loopback Timeout counts
•New OAM Loopback Timeout duration
•Active OAM Loopback Timeout Duration
•OAM Loopback Timeout Threshold
When all of the statistics are enabled, VISM-PR performance is not affected. All of the statistics are enabled by default except for the statistics upload file, which is enabled through CWM.
The following two commands are modified to include these new statistics:
•dsphistorystats
•dspconcnt
You can collect history statistics on PVCs 1-64. PVCs above the 64th PVC are not tracked in history statistics and cannot be displayed with the dsphistorystats command.
For more information about collecting history statistics and the commands, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide & Command Reference, Release 3.3 located at the following URL on Cisco.com:
http://www.cisco.com/en/US/products/hw/gatecont/ps3869/products_configuration_guide_book09186a0080301d30.html
To view the new OAM history statistics, use the dsphistorystats command.
nodename.1.5.VISM8.a > dsphistorystats <StatsType> <Interval> <InterfaceIndex>|InterfaceIndex2|Replace the above arguments with the values listed in Table 5.
In the following example the new OAM statistics are shown in bold.
pxm45-24.1.13.VISM8.a > dsphistorystats 1 80 132
PVC History Statistics: interval = 80, LCN = 132--------------------------------------------Valid Flag = VALIDLast Reset Uptime Ticks = 0Total ATM Xmt Cells = 33157Total ATM Rcv Cells = 31380Avg Per Sec ATM Xmt Cells = 36Avg Per Sec ATM Rcv Cells = 34Peak Per Sec ATM Xmt Cells = 49Peak Per Sec ATM Rcv Cells = 40Total OAM Xmt End-to-End Lpbk Req Cells = 874Total OAM Rcv End-to-End Lpbk Rsp Cells = 874Total OAM Xmt Segment Lpbk Cells = 0Total OAM Rcv Segment Lpbk Cells = 0Total OAM End-to-End Lpbk Lost Cells = 0Total Discarded Rcv OAM Cells = 0Total OAM Lpbk Timeout Cnts = 0
Total New OAM Lpbk Timeout Duration = 0
Total Active OAM Lpbk Timeout Duration = 0
OAM Lpbk Timeout Threshold = 5
Total AIS Suppress Cnts = 0Total Xmt AIS Cnts = 0Total Rcv AIS Cnts = 0Total Xmt FERF Cnts = 0Total Rcv FERF Cnts = 0Total Xmt AIS Cells = 0Total Rcv AIS Cells = 0Total Xmt FERF Cells = 0Total Rcv FERF Cells = 0Total AAL2 CPS Sent Pkts = 196985Total AAL2 CPS Rcvd Pkts = 223126Total AAL2 HEC Errors = 0Total AAL2 CRC Errors = 0Total AAL2 Invalid OSF Cells = 0Total AAL2 Invalid Parity Cells = 0Total AAL2 Invalid Cid Pkts = 12997Total AAL2 Invalid UUI Pkts = 0Total AAL2 Invalid Length Pkts = 0Total AAL5 PDU Sent Pkts = 0Total AAL5 PDU Rcvd Pkts = 0Total AAL5 Invalid CPI PDUs = 0Total AAL5 Oversized SDU Rcvd PDUs = 0Total AAL5 Invalid Length PDUs = 0Total AAL5 CRC32 Errored PDUs = 0Total AAL5 Reassembly Timer Expiry PDUs = 0Last Completed Interval Number is 81To view the real-time count and duration of OAM Loopback Timeouts, use the dspconcnt command.
nodename.1.5.VISM8.a > dspconcnt <LCN>Replace <LCN> with the number of the logical channel for which OAM loopback timeout information is to be displayed. Range is 131-510.
The following example shows the OAM Loopback Timer count and duration in bold.
pxm45-24.1.13.VISM8.a > dspconcnt 132ChanNum: 132Chan State: okayChan XMT ATM State: NormalChan RCV ATM State: NormalChan Status Bit Map: 0x0OAM Lpb Lost Cells: 0AAL2 HEC Errors: 0AAL2 CRC Errors: 0AAL2 Invalid OSF Cells: 0AAL2 Invalid Parity Cells: 0AAL2 CPS Packet Xmt: 3619340AAL2 CPS Packet Rcv: 3745789AAL2 Invalid CID CPS: 220398AAL2 Invalid UUI CPS: 0AAL2 Invalid Len. CPS: 0Chan 24Hr Peak Xmt Cell Rate (CPS): 192Chan Current Xmt Cell Rate (CPS): 38Chan 24Hr Peak Rcv Cell Rate (CPS): 160Chan Current Rcv Cell Rate (CPS): 36AAL5 PDU Packet Xmt: 0AAL5 PDU Packet Rcv: 0AAL5 Invalid CPI: 0AAL5 oversized SDU PDU: 0AAL5 Invalid Len. PDU: 0AAL5 PDU CRC32 Errors: 0AAL5 Reassembly Timer expired PDU: 0AIS Successful Suppression Count: 0AIS Alarm Transmitted Count: 0AIS Alarm Received Count: 0FERF Alarm Transmitted Count: 0FERF Alarm Received Count: 1OAM Loopback Timeout Count 0
OAM Loopback Timeout Duration(secs):0
VISM Management Information Base
VISM Release 3.3.35.203 uses Management Information Base (MIB) Version 85. VISM MIBs are compatible with both PXM1-based and PXM1E/PXM45-based chassis.
To access the MIBs, complete the following steps:
Step 1 Load the MIBs available with MGX Release 1.3.11 located at the following URL: http://www.cisco.com/public/sw-center/index.shtml
Step 2 Copy the modified MIBs that are contained in the MIBS.zip file, which is available at the same location as the firmware files for this release.
Note The MIB version number was last updated in Release 3.3.30.
VISM Redundancy
Table 6 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 (OC-3) cards. In a redundancy configuration VISM/VISM-PR cards in bulk distribution mode do not require any back cards.
VISM Call Rate
Software Release 3.3.35.203 for VISM/VISM-PR handles 10 CAS, SS7, or PRI calls per second per VISM/VISM-PR card.
Compatibility
VISM/VISM-PR software interoperability with Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8830, Cisco MGX 8850 (PXM1, PXM1E, PXM45), and Cisco MGX 8880 platform software is listed in Table 7.
Table 8 shows VISM and VISM-PR compatibility with the PXM controller cards.
Table 8 VISM/VISM-PR Compatibility with PXM Cards
PXM1 PXM1E PXM45 (A/B/C)VISM
Yes
No
No
VISM-PR
Yes
Yes
Yes
Table 9 shows VISM and VISM-PR compatibility with the Cisco MGX chassis.
Table 10 describes the VISM/VISM-PR software interoperability with other Cisco products.
Table 11 describes the software images available for Release 3.3.35.203 for VISM/VISM-PR.
Table 11 Software Images for VISM/VISM-PR Release 3.3.35.203
Product Name Software Version Firmware Image Name DescriptionMGX-VISM-SW3335
003.003.035.203.FW
vism_8t1e1_003.003.035.203.fw
This image does not support the CALEA1 feature.
MGX-VISM-LISW3335
003.053.035.203.FW
vism_8t1e1_003.053.035.203.fw
This image supports the CALEA2 feature.
1 CALEA = Commission on Accreditation for Law Enforcement Agencies.
2 The CALEA implementation supports the CALEA law intercept confirmation interface.
Table 12 describes the software boot code requirements for VISM/VISM-PR Release 3.3.35.203.
Limitations and Restrictions
The following limitations and restrictions are valid for software Release 3.3.35.203 for VISM/VISM-PR:
•In VISM Release 3.3.20 and later, the packetization period for G726-32K codec in custom profile 210 is 5 msec. In VISM Release 3.3.10 and earlier, this value was 10 msec. Because of this change, VISM Release 3.3.20 and later cannot interoperate with VISM Release 3.3.10 and earlier if the two releases have CIDs configured for custom profile 210 in AAL2 mode.
The packetization period change also made it difficult to upgrade from VISM Release 3.3.10 and earlier to VISM Releases 3.3.20 through 3.3.30, when CIDs were configured for G726-32K codec in custom profile 210 in AAL2 mode. The workaround was to clear the card configuration, upgrade the software, and then reconfigure the card.
VISM Release 3.3.30 resolves the upgrade problem (CSCek34084). You can now upgrade from all VISM releases to Release 3.3.30 normally, even when CIDs are configured with custom profile 210 in AAL2 mode. However for VISM Release 3.3.10 and earlier, you must increase the bandwidth of PVCs for CIDs that use custom profile 210 prior to the upgrade. This is because the upgrade automatically decreases the packetization period to 5 msec for CIDs using custom profile 210, but does not automatically increase the PVC bandwidth for those CIDS.
•If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
•Cisco recommends that you use the cnfcodecjtrdelay command to configure the fixed jitter-delay argument to 20 ms when using VISM-PR 3.3.35.203.
•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.
•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 the VISM cards 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.
•When configuring VoIP for modem or fax upspeed (passthrough), set the EventNegoPolicy parameter of the cnfvoiptransparams command to the value all.
This configuration is required for all related upspeed codecs to function correctly. An upspeed codec is defined as the codec that is switched to G.711a/u law, Clear Channel, or G.726.
•For a list of open issues and mitigations in VISM Release 3.3.35.203, see "Caveats in Release 3.3.35.203" section.
Upgrade Procedures
This section describes the following upgrade procedures:
•VISM/VISM-PR Upgrades with PXM1
•Upgrading VISM-PR with PXM1E and PXM45
•Upgrading VISM to VISM-PR Hardware
VISM/VISM-PR Release 3.3.35.203 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 3.2.11 to VISM 3.3.35.203
•From VISM 3.3 to VISM 3.3.35.203
•From VISM 3.3.20 to VISM 3.3.35.203
•From VISM 3.3.25 to VISM 3.3.35.203
•From VISM 3.3.30 to VISM 3.3.35.203
Prerequisites
To ensure that the VISM/VISM-PR configuration is preserved throughout the upgrade procedure, you must complete the prerequisites listed in this section.
Before starting the graceful upgrade procedure, complete the following prerequisites:
•Configure your MGX 8000 Series shelf with at least two VISM cards in a redundant configuration.
For more information on adding redundancy, refer to the add redundancy, addred, command in the Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8850 PXM1-based Command Reference documentation and the Cisco MGX 8830 and Cisco MGX 8850 PXM1E/ PXM45-based Command Reference documentation.
•Ensure that the VISM cards are running at least Release 2.1, and the VISM-PR cards are running at least Release 3.0.
•Download software Release 3.3.35.203 for VISM/VISM-PR to the MGX 8000 Series shelf.
•If you are using the CALEA feature, ensure that you have the version of VISM/VISM-PR software that supports CALEA.
VISM/VISM-PR Upgrades with PXM1
This section describes the procedures for upgrading VISM/VISM-PR software when the VISM/VISM-PR is used with a PXM1 card.
Downloading 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.
a. tftp <node_name or IP address>
b. bin
c. To upgrade all VISM cards:
put <FW file> POPEYE@SM_1_0.FW
quit
d. To upgrade an individual VISM card:
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 "Upgrading VISM/VISM-PR Firmware with PXM1 Card" section to install the download.
Upgrading 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:
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 to update the VISM/VISM-PR boot code.
Step 2 Execute the PXM1 install command.
nodename.1.27.VISM8.a > install [bt] [sm <slot>] <version>
Caution Do not touch the VISM/VISM-PR card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation corrupts the boot code, which cannot be recovered.
When the boot code is being written to PROM, you see comments displayed at the VISM/VISM-PR prompt. This behavior is normal and expected.
Step 3 Type the version command to verify the correct boot code.
Note Step 3 is optional.
Upgrading VISM/VISM-PR Firmware with PXM1 Card
Software Release 3.3.35.203 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.
The following versions of VISM software Release 3.3.35.203 are available:
•003.003.035.203.FW—without CALEA
•003.053.035.203.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.3.35.203.
Perform the firmware upgrade on the VISM or VISM-PR cards. Do not remove the VISM cards and replace them with VISM-PR cards at this time.
Step 1 Log in to the active PXM1 card (slot 7 or 8 for Cisco MGX 8250 and Cisco MGX 8850 chassis; slot 1 or 2 for Cisco MGX 8230 and Cisco MGX 8830 chassis).
Step 2 Save the existing configuration as a contingency plan by entering:
nodename.1.8.PXM.a > savesmcnf <SM slot#>This command saves the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure.
Step 3 To obtain the correct version of VISM/VISM-PR firmware, enter the dspfwrevs command.
nodename.1.8.PXM.a > dspfwrevs
Card Type Date Time Size Version File Name----------- ------------------- -------- -------------------------------------VISM-8T1E1 04/26/2004 20:06:04 248688 VI8_BT_3.2.00 sm150.btPXM1 01/04/2004 08:19:52 2602836 1.2.11 pxm_1.2.11.fwPXM1 01/04/2004 11:03:02 2620132 1.2.21 pxm_1.2.21.fwVISM-8T1E1 09/10/2004 16:22:32 4135208 003.003.000.200 sm150_12.fwVISM-8T1E1 09/10/2004 15:37:52 4077560 003.002.010.200 sm150.fwVISM-8T1E1 06/16/2004 13:29:38 3863768 003.051.002.000 sm150_11.fwPXM1 01/04/2004 11:01:56 1346844 1.2.21 pxm_bkup_1.2.21.fwVISM-8T1E1 03/08/2004 08:20:16 4037880 003.002.000.000 sm150_3.fwVISM-8T1E1 03/08/2004 08:19:44 248688 VI8_BT_3.2.00 sm150_3.btPXM1 01/04/2004 07:58:44 1345328 1.2.11 pxm_bkup_1.2.11.fwVISM-8T1E1 01/07/2004 23:33:02 3863768 003.051.002.000 sm150_2.fwVISM-8T1E1 03/08/2004 08:21:12 248688 VI8_BT_3.2.00 sm150_4.btVISM-8T1E1 05/10/2005 19:59:52 4037880 003.003.020.000 sm150.fwStep 4 Execute the PXM install command.
nodename.1.8.PXM.a > install sm <SM slot#> <new-rev>Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev > with the version of the new firmware (for example, 003.003.035.203.FW).
The install sm 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.
Caution Ensure that you perform Step 4. If you do not perform Step 4, the boot code is corrupted and not recoverable.
Step 5 Execute the PXM newrev command.
nodename.1.8.PXM.a > newrev sm <SM slot#> <new-rev>Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev> with the version of the new firmware.
The newrev command causes the primary VISM or VISM-PR card to reset. The secondary VISM or VISM-PR card becomes active and runs the new-rev firmware.
Step 6 Execute the PXM commit command.
nodename.1.8.PXM.a > commit sm <SM slot#> <new-rev>Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev> with the version of the new firmware.
The two VISM or VISM-PR cards are now back to their original condition, except that both cards are now running the new-rev firmware.
Step 7 Log in to the active VISM or VISM-PR card and use the display commands (for example, dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.
Note For more than one primary VISM or VISM-PR card in a redundancy group, ensure that the secondary card is in the standby state, and repeat Step 5 and Step 6 for each VISM/VISM-PR card in the redundancy group.
Step 8 Perform the following verifications:
•Make minor modifications to the configuration.
•Check that the changes have been executed correctly.
•Change the configuration back again.
Note If the VISM or VISM-PR card is not part of a redundancy group, complete only
Step 1 to Step 4.
Upgrading VISM-PR with PXM1E and PXM45
This section describes the procedures for upgrading VISM-PR software when the VISM-PR is used with a PXM1E or PXM45 card.
To upgrade the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
Downloading 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 boot code and firmware images on Cisco.com.
Step 2 To download the images, enter the ftp command.
ftp node-ip
The node-ip argument 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 Change to the C:FW directory.
cd C:FW
Step 6 Download the images 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.
The image-version argument is the image that you accessed in Step 1.
Step 7 To exit the download procedure, enter bye.
Upgrading 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 "Downloading VISM-PR Boot Code and Firmware to PXM1E and PXM45" section.
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 sample results from the burnboot command.
nodename.1.7.PXM.a > burnboot 12 3.2(0.0)
The card in slot 12 will be reset.burnboot:Do you want to proceed (Yes/No)? yesFor 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 and becomes the standby again, and the standby card is now active.
Upgrading VISM-PR Firmware with PXM1E and PXM45 Cards
Complete the steps in this section to upgrade the VISM-PR firmware. 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.3.35.203 are available:
•003.003.035.203.FW—Without CALEA
•003.053.035.203.FW—With CALEA
Caution If you plan to upgrade PXM cards and VISM-PR modules, upgrade the PXM cards first. Wait until the PXM cards are operating in active and standby modes with the correct software before upgrading the VISM-PR modules. Failing to upgrade the node in the correct order can fail VISM connections, causing significant service disruption.
Perform the firmware upgrade on the VISM-PR cards.
Step 1 Log in to the active PXM1E or PXM45 card.
Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.
Step 3 To save the existing configuration, enter the saveallcnf command.
nodename.1.7.PXM.a > saveallcnf
Step 4 To load the new software, enter the loadrev command.
nodename.1.7.PXM.a > loadrev <sm-primary-slot-num> <new-rev>
Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
Caution Temporary traffic loss occurs.
Step 5 Ensure that the redundant card is returned to the standby state by executing the dspcds command.
Note You must wait for the redundant card to return to the standby state. If you issue the runrev command too early, an error message is generated. The rev change does not occur.
Step 6 To execute the download, enter the runrev command.
nodename.1.7.PXM.a > runrev <sm-primary-slot-num> <new-rev>
Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
Caution Temporary traffic loss occurs.
Step 7 Ensure that the primary card completes booting up and goes into the standby state by executing the dspcds command.
Note You must wait for the primary card to finish booting up 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 states. For example, the original primary card might be left in standby, and the original redundant card might be left as active.
Step 8 To commit the new download to the VISM-PR card, enter the commitrev command.
nodename.1.7.PXM.a > commitrev <sm-primary-slot-num> <new-rev>Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
The commitrev command switches the primary card from a standby state to an active state and the redundant card from an active state back to a standby state.
Step 9 To verify the card states, execute the dspcds command.
Downgrading VISM/VISM-PR
Use this procedure to downgrade VISM/VISM-PR software from software Release 3.3.35 to an earlier VISM/VISM-PR release. If you use the downgrade procedure described here, you can retain the configurations after the downgrade.
Note The configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.
Complete the following steps to downgrade the VISM/VISM-PR software:
Step 1 If the VISM/VISM-PR card is in a redundancy group, remove the redundancy.
nodename.1.7.PXM.a > delred <SM slot#>Step 2 Download the old-rev firmware onto the MGX shelf.
Step 3 Execute the PXM clrsmcnf command.
nodename.1.7.PXM.a > clrsmcnf <SM slot#>Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.
Wait for the card to become active. The VISM/VISM-PR card resets after you execute this command.
Step 4 Execute the PXM restoresmcnf command.
nodename.1.7.PXM.a > restoresmcnf -f <filename> -s <SM slot#>
Replace <filename> with the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.
Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.
The VISM/VISM-PR card resets again. The card becomes active, running the old-rev firmware with the old configuration.
Note For PXM1E/PXM45 cards, you cannot restore the configuration for an individual VISM-PR service module. You can save and restore the configuration of all cards in a chassis using the saveallcnf and restoreallcnf commands.
Caution The restoreallcnf command reconfigures all of the cards in the chassis.
Step 5 Reconfigure the redundancy group, if required.
Upgrading VISM to VISM-PR Hardware
Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.
Caution For this procedure, 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 change 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 its slot in your chassis.
Step 2 Install a VISM-PR card in the same slot.
Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).
Step 4 Remove the now redundant VISM card from your chassis.
Step 5 Install a VISM-PR card in the slot from which you removed the VISM card in Step 4.
Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to ensure that the correct card type is shown.
Step 7 Log in to the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card.
If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM. Repeat the dspcd command to ensure that the correct card type is shown.
Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.
Step 9 Remove a standby VISM card from its slot in your chassis.
Step 10 Install a VISM-PR card in the same slot.
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 ensure that the correct card type is shown for each.
Caveats in Release 3.3.35.203
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.35.203.
Resolved Caveats in Release 3.3.35.203
Table 13 Resolved Caveats in Release 3.3.35.203
DDTS Issue DescriptionCSCee28948
Wrong values accepted for codec jitter delay parameter.
CSCsy79121
DSP release 3.6.37 incorporation checkin.
Open Caveats in Release 3.3.35.203
None.
Caveats in Release 3.3.35
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.35.
Resolved Caveats in Release 3.3.35
Open Caveats in Release 3.3.35
None.
Caveats in Release 3.3.30
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.30.
Resolved Caveats in Release 3.3.30
Table 15 describes the open caveats in VISM/VISM-PR Release 3.3.30.
Open Caveats in Release 3.3.30
Table 16 describes the open caveats in VISM/VISM-PR Release 3.3.30.
Caveats in Release 3.3.25
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.25.
Resolved Caveats in Release 3.3.25
Table 17 describes the caveats that have been resolved in Release 3.3.25 as of November 4, 2005.
Open Caveats in Release 3.3.25
Table 18 describes the open caveats in VISM/VISM-PR Release 3.3.25 as of November 17, 2005.
Caveats in Release 3.3.20
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.20.
Resolved Caveats in Release 3.3.20
Table 19 describes the caveats that have been resolved in Release 3.3.20 as of August 9, 2005.
Open Caveats in Release 3.3.20
Table 20 describes the open caveats in VISM/VISM-PR Release 3.3.20 as of July 19, 2005.
Caveats in Release 3.3.10
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.10.
Resolved Caveats in Release 3.3.10
Table 21 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.10.
Open Caveats in Release 3.3.10
Table 22 describes the open caveats in VISM/VISM-PR Release 3.3.10 as of March 11, 2005.
Caveats in Release 3.3
This section describes the resolved and open software caveats in VISM/VISM-PR Release 3.3.
Resolved Caveats in Release 3.3
Table 23 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.
Open Caveats
Table 24 describes the open caveats in VISM/VISM-PR Release 3.3 as of September 27, 2004.
Related Documentation
The following documents contain information that may be useful to software Release 3.3.35.203 for VISM/VISM-PR:
•Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3
•Cisco MGX 8800/8900 Hardware Installation Guide, Releases 2 - 5.2
•Cisco MGX 8800/8900 Series Configuration Guide, Release 5.5.10
•Cisco MGX 8800/8900 Series Command Reference, Release 5.2
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0903R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.