Installation guide

38
Release Notes for Cisco Voice Interworking Service Module Release 3.0(0)
Part Number OL-2523-01 Rev. B0, January 9, 2004
Caveats
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 redundancy group, if required.
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 11 describes the caveats issued against VISM software that have been resolved in software Release
3.0(0) for VISM/VISM-PR.
Table 11 Resolved Caveats for Software Release 3.0(0) for VISM/VISM-PR
DDTs Issue Description
CSCdu11130 Title: CAS endpoint does not go idle after a failed call.
Description: When the terminating VISM is dialing the digits out (in immediate and
wink start) and times out waiting for DSPs acknowledgment (that the digits were
dialed out), CAS initiates a DLCX (E: could not dial digits) and goes to the wait for
idle signal from PBX state.
Workaround: None.
CSCdv20426 Title: The cnfgwoos 2 (2 = forceful) CLI command string fails to delete some
connections under error conditions.
Description: Upon a network COT failure—when network COT is initiated by the
terminating gateway—the terminating gateway sends DLCX to the call agent. If the
the call agent, upon receiving DLCX from the terminating gateway, sends DLCX with
R: (empty list in requested events) to the originating gateway to delete the connection.
The originating gateway fails to delete the connection and NACKs the DLCX. The
connection is hung in this situation. Now, after this failed operation, the originating
gateway does not delete the connection with the cnfgwoos 2 CLI command string and
the connection stays hung.
Workaround: None.