Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 2.2(1)
Features Introduced in Previous Releases of VISM Software
VISM Management Information Base
Installation and Upgrade Procedures
VISM Firmware Download Procedure
Installing VISM Software Updates
VISM Boot Code Upgrade Procedure
Upgrading VISM Software from 1.5(x) to 2.2(1)
Obtaining Technical Assistance
Release Notes for Cisco Voice Interworking Service Module Release 2.2(1)
July 2002
The Cisco Voice Interworking Service Module (VISM) product is supported by Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.
The VISM Release 2.2(1) is a maintenance upgrade of the VISM Release 2.2(0). There are no new features introduced with this release.
This release is compatible with the Cisco MGX 8850/8250/8230 Release 1.1.40 and 1.2.00 software.
The VISM Release 2.2(1) is supported by the Cisco VISM Installation and Configuration Guide, which is available on the Web at the following locations:
•http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/vism221
•http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/vism221
•http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/vism221
Contents
These release notes contain the following sections:
•"Installation and Upgrade Procedures" section
•"Related Documentation" section
•"Obtaining Documentation" section
•"Obtaining Technical Assistance" section
Features Introduced in Previous Releases of VISM Software
The following list describes the features introduced in previous VISM software releases. All previously released features are supported in VISM Release 2.2(1).
•Mid-Call DTMF
•Configurable Jitter Buffer
•Adjustable Gain
•Adjustable Music On-Hold Threshold
•Communication Assistance for Law Enforcement Act (CALEA)
•MGC Redundancy
•External DNS
•2 IP Address Support
•VoIP Trunking
•T.38 Fax Relay
•CAS Feature Enhancements:
–Programmable Tone Plans
–Loop Start, DID, and Delay Dial
–FGD
–Configure Flash Hook and Glare Condition Attributes
–Configure ANI and DNIS Digit Order
–RFC 3064 Package Support
•RFC 2833 Support
•VISM Network Continuity Test
•Configure PVC OAM Cell Parameters
•Verified MGCP 0.1 protocol compliance
•PBX CAS event delivery to a Call Agent using MGCP 0.1:
–DTMF: Wink and ground start
–MF: Wink
–TFTP download of CAS variant state machine
Note RFC 3064 CAS packages—BL, MS, and DT—are not supported.
•Interoperability enhancements:
–Configurable codec strings (IANA naming conventions as well as customized ones).
–Codec negotiation with configurable preference order.
•Exponential backoff for:
–XGCP retry timers.
–SRCP retry timers.
–Configurable per CAS variant.
•DTMF Relay using Cisco-rtp (FRF-11 Annex A based).
•Enhancement to Fax/modem up-speed/pass-through procedures:
–Configurable CAC failure and carrier loss policies.
–Up-speed to clear channel.
•Added support for G.726: 16, 24, 32, and 40 kbps, with packetization periods ranging from 10 to 40 ms.
•Support for VBR-rt (Variable Bit Rate-Real Time) and VBR-nrt (nonreal time) ATM traffic classes, including traffic shaping to the relevant traffic descriptors.
•Configurable VAD model parameter for traffic engineering.
•In E1 applications, support for 31 DS0 per span and a total of 248 channels per card.
•Tested CRTP support through RPM for voice and voice band data calls.
•Verified bearer interoperability with 3810.
•Switched PVCs using SGCP 1.5
–SDP and SGCP extensions allowing xGCP Call Agent control of AAL2 bearers.
–Support of SGCP 1.5 digit maps and error codes.
•Support for card level coexistence of switched AAL2 mode (under Call Agent control) and trunked AAL2 mode on PVCs, on an endpoint (DS0) basis.
•PBX CAS event delivery to a Call Agent using SGCP 1.5:
–DTMF: Wink and ground start.
–MF: Wink.
–TFTP download of CAS variant state machine.
•Interoperability and configurability enhancements:
–Configurable codec strings (IANA naming conventions as well as customized ones).
–Profile negotiation and configurable preference order.
–Configurable voice and VBD (i.e., up-speed codec) per profile.
•Exponential backoff for:
–XGCP retry timers.
–SRCP retry timers.
–Configurable per CAS variant.
•Added support for custom profile 110 and 200 (clear channel), ITU profiles 3 and 8.
•User-configurable AAL2 Silence Indicator Description (SID) for all profiles.
•Type 3 Packet Support for proxy ringback (xrbk), packet side bearer continuity check (co3/co4 COT), and midcall DTMF relay.
•Enhancement to Fax/modem up-speed/pass-through procedures:
–Configurable CAC failure and carrier loss policies.
–Up-speed to clear channel.
•Supports VBR-rt and VBR-nrt ATM traffic classes, including traffic shaping to the relevant traffic descriptors.
•Connection admission control (CAC) enhancements:
–Patented CAC method factoring in VAD and subcell multiplexing savings.
–Configurable VAD model parameter for traffic engineering.
•Configurable AAL2 cell fill timer.
•AAL2 alarm enhancements: per span, VC, and per channel (CID) conditioning.
•Display, clear, and reset AAL2 performance related counters.
•In E1 AAL2 trunking applications, support for 31 DS0 per span and a total of 248 channels per card.
•Verified bearer interoperability with 3810 and third-party vendors.
•Infrastructure work and enhanced support for three operating modes: VoIP switching, AAL2 trunking, and switched AAL2 PVC.
•Graceful upgrade VISM 2.0 and 2.0(1) to VISM 2.1(0).
•The ability to enable or disable the Call Agent protocol SDP OST feature in the event the peer gateway may or may not support SDP OST. This feature allows interoperability with the Cisco AS5300 Universal Access Server and other equipment.
•The ability for VISM to perform as either the network or user side of the LAPD protocol for PRI backhaul.
•CCS/PRI backhaul between VISM and a Call Agent in VoIP mode.
•Support VoIP G.729ab compression.
•Idle channel suppression.
•Support for setting the IP precedence bit.
•Support for Q.50 CAS signaling variant.
•Negotiable packetization period.
•AAL2 subcell multiplexing.
•E1 back card support in AAL2 trunking mode.
•E1 back card support (VoIP mode only).
•Provides eight standard T1 interfaces with B8ZS, AMI and HDB3 line coding.
•Support for voice over ATM using AAL2 cells (multiplexing only, no LLC/SNAP encapsulation).
•VoIP using AAL5 cells to RFC 1889.
•Support for both PCM a-law and u-law.
•Programmable 24, 32, 48, 64, 80, 96, 112, 128 ms near-end echo cancellation.
•Voice compression to G.711 and G.726-32K standards.
•Nx64 clear channel (N = 1 only) support.
•Voice activity detection (VAD) and comfort noise generation (CNG) using variable threshold energy (Cisco proprietary).
•Support for call agent Simple Gateway Control Protocol (SGCP) Version 1.0, SGCP 1.1+, and Media Gateway Control Protocol (MGCP) 0.1.
•Support for CCS signaling transport across an AAL5 trunk.
•Support for Fax and modem VoIP bearer transmissions.
•Support for dual (redundant) virtual circuits across the packet network.
•Support for full continuity testing (COT). Supports origination and terminating loopback and transponder COT toward the packet bearer and the TDM sides.
•Support for loop timing, payload and line loopbacks.
•1:N cold redundancy using SRM-3T3 capabilities (bulk mode support for T1 lines only) for switched calls.
•1:N hot redundancy for trunking applications only.
•Courtesy downing of ongoing voice calls when the VISM card is taken out of service for maintenance or other reasons.
Important Notes
This section describes the following elements of VISM Release 2.2(1):
•"VISM Management Information Base" section
•"Limitations and Restrictions" section
VISM Management Information Base
The VISM Management Information Base (MIB) Version 0.0.30 is provided with the delivery of VISM Release 2.2(1) software, which bundles with the MGX 8230, 8250 and 8850 Release 1 software on CCO and is located on the Web at the following location:
http://www.cisco.com/kobayashi/sw-center/beta/
When the selected FW *.tar file or FW*.zip file is downloaded, untar or unzip the file and you will find all the latest MIBs bundled with this release.
The MIB is in standard ASN.1 form and can be compiled with most standards-based MIB compilers. Refer to the MIB release notes on CCO.
VISM Redundancy
Refer to Table 1 for the support level for 1:N Service Module Redundancy (N = 1 through 11).
There is support for Bulk Distribution using the SRM-3T3B card.
VISM Call Rate
VISM Release 2.2(1) handles at least 10 CAS, SS7, or PRI calls per second per VISM card.
Compatibility
VISM software interoperability with MGX 8850, MGX 8250, and MGX 8230 platform software is listed in Table 2.
Table 2 VISM Software Interoperability
PCB Description CW2000 Name Latest Firmware Min. FirmwarePXM1
PXM-1
1.2.00
1.1.40
PXM1-2-T3E3
PXM1-2T3E3
1.2.00
1.1.40
PXM1-4-155
PXM1-4OC3
1.2.00
1.1.40
PXM1-1-622
PXM1-OC12
1.2.00
1.1.40
MGX-SRM-3T3/B
SRM-3T3
—
—
AX-CESM-8E1
CESM-8E1
10.2.00
10.0.22
AX-CESM-8T1
CESM-8T1
10.2.00
10.0.22
MGX-CESM-8T1/B
CESM-8T1/B
10.2.00
N/S
MGX-AUSM-8E1/B
AUSMB-8E1
10.2.00
10.0.23
MGX-AUSM-8T1/B
AUSMB-8T1
10.2.00
10.0.23
MGX-CESM-T3
CESM-T3
10.2.00
10.0.22
MGX-CESM-E3
CESM-E3
10.2.00
10.0.22
AX-FRSM-8E1/E1-C
FRSM-8E1
10.2.00
10.0.23
AX-FRSM-8T1/T1-C
FRSM-8T1
10.2.00
10.0.23
MGX-FRSM-HS2
FRSM-HS2
10.2.00
10.0.23
MGX-FRSM-HS2/B
FRSM-HS2/B
10.2.00
N/S
MGX-FRSM-2CT3
FRSM-2CT3
10.2.00
10.0.23
MGX-FRSM-2T3E3
FRSM-2T3
10.2.00
10.0.23
MGX-FRSM-2T3E3
FRSM-2E3
10.2.00
10.0.23
MGX-FRSM-HS1/B
FRSM-HS1/B
10.2.00
10.0.23
MGX-SRM-E
SRM-E
—
N/S
MGX-VISM-8T1
VISM-8T1
2.2(0)
2.2(0)
MGX-VISM-8E1
VISM-8E1
2.2(0)
2.2(0)
CWM
—
10.5.10
10.4.101
1 Cisco WAN Manager Release 10.4 does not support all of the new MIBs listed in the "VISM Management Information Base" section.
VISM software interoperability with other Cisco products is described in Table 3.
Table 4 describes the software boot code and run-time firmware requirements for VISM Release 2.2(1).
Note Loading this release of the backup bootcode is required for existing VISM cards not using this new release.
Limitations and Restrictions
The following limitations and restrictions are valid for VISM Release 2.2(x):
•VISM Release 2.2(x) requires you to use 64-Mb VISM cards exclusively.
•Table 5 describes the design constraints which are identified in VISM Release 2.2(1).
Installation and Upgrade Procedures
This section describes the following installation and upgrade procedures:
•"VISM Firmware Download Procedure" section
•"Installing VISM Software Updates" section
•"VISM Boot Code Upgrade Procedure" section
•"VISM Downgrade Procedure" section
•"Upgrading VISM Software from 1.5(x) to 2.2(1)" section
Caution If you are upgrading the VISM software from 1.5(x), refer to the "Upgrading VISM Software from 1.5(x) to 2.2(1)" section. VISM Release 2.1(0) does not provide a graceful upgrade procedure from 1.5(x) to 2.1(x).
VISM Firmware Download Procedure
Download the selected revision of service module firmware into the service module in the selected slot.
Step 1 Download the selected revision of service module firmware into the service module in the selected slot.
tftp <node_name or IP address>binput <backup boot> POPEYE@SM_1_<slot#>.BOOTquittftp <node_name or IP address>
Step 2 Proceed to Step 2a. to upgrade all VISM cards or proceed to Step 2b. to upgrade an individual VISM card.
a. put <FW file> POPEYE@SM_1_0.FW
quitb. 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 3 Proceed to the "Installing VISM Software Updates" section to install the download.
Installing VISM Software Updates
VISM Release 2.2 provides a procedure for the graceful upgrade (one in which the existing VISM configuration is preserved throughout the upgrade procedure) from the earlier VISM 2.0 release.
Caution Temporary traffic loss occurs during Step 4 and Step 5 of the VISM graceful upgrade procedure of the Upgrade Procedure for VISM Release 2.2.1.
Initial Conditions
The following initial conditions are required before the graceful upgrade procedure can be started:
•The MGX 8000 Series shelf must be configured with at least two VISM cards in a redundant configuration (refer to the add redundancy, addred, command in the MGX 8850, MGX 8250, and MGX 8230 command references for more information).
•The VISM cards must be running VISM 2.0 and be configured to the desired configuration.
•The VISM Release 2.2(1) software must have been already downloaded to the MGX shelf.
Upgrade Procedure
In the following procedure:
•Two VISM cards are involved, one initially active and one initially standby. The initially active VISM is identified as VISM 1 and the initially standby VISM as VISM 2.
•Old-rev refers to the firmware before the upgrade (2.0).
•New-rev refers to the firmware after the upgrade (2.1).
Complete the following steps to upgrade the VISM cards:
Step 1 Log in to the active PXM card (slot 7 or 8).
Step 2 Save the existing configuration as a contingency plan by entering:
savesmcnf <SM slot#>This will save 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 VISM 2 card and new-rev is the version number of the new firmware (for example, vism_8t1e1_002.001.000.000.fw).
This command causes the standby VISM 2 to reset and come up in the "hold" state, running the new-rev firmware. The active VISM 1 is unaffected by this command. At this point, the primary firmware is still the old-rev and the secondary firmware is new-rev.
Note If the VISM card is not part of a redundancy group, Step 1 to Step 3 are sufficient.
Step 4 Execute the PXM newrev command:
newrev sm <SM slot#> <new-rev>where:
SM slot# is the slot number of the VISM 2 and new-rev is the filename of the new firmware.
This command causes the VISM 2 to become the active VISM running the new-rev firmware. The previously active VISM 1 changes to a "hold" state and is still running the old-rev firmware. The primary and secondary firmware switches with the new-rev becoming the primary firmware.
Step 5 Execute the PXM commit command:
commit sm <SMslot#> <new-rev>where:
SM slot# is the slot number of the standby VISM 1 and new-rev is the filename of the new firmware.
This command causes both VISM cards to run the new-rev firmware. At first, VISM 2 is the active VISM with VISM 1 remaining in the hold state. After a short time, the cards switch automatically with VISM 1 becoming the active card and VISM 2 the standby card.
The two VISM cards are now back to their original condition except that both cards are now running the new-rev firmware.
Step 6 Log in to the active VISM card and use the display commands (dspendpts, dspcasvar, etc.) to confirm that the configuration has been preserved through the upgrade process.
It is also recommended that a further verification be performed by making some minor modifications to the configuration, checking that the changes have been executed correctly, and then changing the configuration back again.
VISM Boot Code Upgrade Procedure
There is a new backup boot code change from VISM Release 2.1(1) to VISM Release 2.2(0). Complete the following steps to upgrade the new backup boot code.
Note This procedure reprograms the VISM boot code for previous VISM cards using the VISM runtime image version 1.0 to 2.0.
Step 1 Telnet to MGX shelf and use the cc command to navigate to the VISM card.
Step 2 Type shellConn at the VISM card prompt.
Step 3 Type boot_permit = 1 at the shellConn prompt.
The boot_permit equals 0 by default, which does not allow an upgrade of boot code.
Note VISM must be in the active state in order to update the VISM boot code.
Step 4 Access the server where the VISM boot code resides and TFTP the VISM boot code to the VISM card with the following procedure:
a. Type tftp <IP address of the MGX shelf>.
b. Type bin at the tftp prompt.
Caution Ensure that you perform Step 4 b. If you do not perform Step 4 b. the boot code will be corrupted and not recoverable.
c. Type put <vism-backup-boot.fw> POPEYE@SM_1_<vism_slot_number>.BOOT
where <vism_slot_number> = the slot number where the VISM card is inserted.
Caution Do not touch the VISM card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation will corrupt the boot code and will not be recoverable.
When the boot code is being written to PROM, you will see comments displayed at the VISM prompt. This is normal and expected behavior.
Step 5 Use the resetcd command for VISM from the PXM card for the latest boot to take effect.
Step 6 (Optional) Type the version command to verify the correct boot code.
You have completed upgrading the new VISM backup boot code.
VISM Downgrade Procedure
Use this procedure to downgrade VISM software from VISM Release 2.2 to the earlier VISM Releases 2.1 and 2.0. By following the downgrade procedure described here, the configurations will be retained after downgrade.
Note The configurations that existed with old-rev firmware should have been saved earlier.
Complete the following steps to downgrade the VISM software from Release 2.2 to Release 2.1 or 2.0:
Step 1 If the VISM 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 card will be reset on executing this command. Wait for the card to come active.
Step 4 Execute the PXM restoresmcnf command:
restoresmcnf -f <filename> -s <SM slot#>where:
The filename is the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.
The SM slot# is the slot number of the VISM card to be downgraded.
The VISM card will be reset again. When the card comes active, it will have the old-rev firmware running and will have the old configuration.
Step 5 Reconfigure the redundancy group, if required.
Upgrading VISM Software from 1.5(x) to 2.2(1)
If upgrading from a VISM Release 1.5, execute clrallcnf and start loading the software as if it is a new system configuration or clrsmcnf for individual card configuration (verify that there are no connections configured first).
Note VISM 2.2(1) provides a procedure for a graceful upgrade from VISM 2.0(0).
Caveats
This section describes resolved and open software caveats for this release of VISM. Caveats describe unexpected behavior or defects in VISM software.
Resolved Caveats
Table 6 describes the caveats issued against VISM software that have been resolved in Release 2.2(1).
Open Caveats
Table 7 describes possible unexpected behavior by VISM Release 2.2(1).
Related Documentation
The following document contains information that may be useful to VISM Release 2.1(1):
•Cisco Voice Interworking Service Module Guide
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Feedback at the top of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.