Guest

Cisco Unity

Release Notes for Cisco Unity Release 3.1(5)

 Feedback

Table Of Contents

Release Notes for Cisco Unity Release 3.1(5)

Contents

System Requirements, and Supported Hardware and Software

Compaq Service Pack for ProLiant DL380 G2 Server

Security Issues

Microsoft Security Update Q326830

Nimda Virus

Compatibility Matrix: Cisco Unity 3.1(5), the Cisco Unity-CM TSP, and Cisco CallManager

Compatibility Matrix: Cisco Unity 3.1(5) and the Software on Client Workstations

Compatibility Matrix: Cisco Unity 3.1(5), and Required and Optional Third-Party Service Packs

Determining the Software Version

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector

RealSpeak Engine

AMIS and Voice Connector Requirements for Upgrading to Cisco Unity 3.1(5)

AMIS on a Cisco Unity 3.1(2) System with the Voice Connector for Exchange 2000

AMIS on a Cisco Unity 3.0(x) Through 3.1(1) System

Cisco Unity 2.4(6.x) Through 3.1(2) Servers That Use the Voice Connector for Messaging

Uninstalling the Cisco Unity Voice Connector

Upgrading to Cisco Unity 3.1(5) from Version 3.0 or 2.4(6)

Task List for Upgrading to Cisco Unity Version 3.1(5) from Version 3.0 or 2.4(6)

Upgrading to Cisco Unity 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs

Task List for Upgrading to Cisco Unity Version 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs

New and Changed Support

New and Changed Support—Release 3.1(5)

Additional Counters in Performance Analysis Tool

Optional Microsoft Service Packs Qualified for Use with Cisco Unity

Symantec pcAnywhere No Longer Required

Updated and New Tools in Tools Depot

New and Changed Support—Release 3.1(4)

Automatic Gain Control Registry Settings Can Be Updated with the Set Volume Utility

Backup and Restore Procedures for the Servers on a Cisco Unity Failover System

Exchange 2000 Service Pack 2 Required

Tools Depot

New and Changed Support—Release 3.1(3)

AMIS-Compliant Voice Messaging Systems Qualified for Use with Cisco Unity

Automatic Gain Control

NetIQ VoIP Manager 2.0 for Cisco Unity

Octel Analog Networking

Permissions Wizard

Phone System Integrations Qualified for Use with Cisco Unity

SQL Server 2000 Hot Fix

Telecommunications Data Card Qualified for Use with the Cisco Unity Bridge

Tools Depot

Virus Scanning Software Qualified for Use with Cisco Unity

New and Changed Support—Release 3.1(2)

AMIS Support

IBM X232 and X250 Servers

New and Changed Support—Release 3.1(1)

AMIS Support

Integrations

TOPCALL Fax

New and Changed Functionality

New and Changed Functionality—Release 3.1(5)

Bridge Traffic Analyzer Utility

Cisco Unity Conversation Available in New Languages

Connecting Cisco Unity to a Different Exchange 2000 Server

Full-Mailbox Check for Outside Callers

Message Store Monitor Service

Migrate Subscriber Data Utility

Warning Tone for End of Recording Can Be Enabled in Cisco CallManager Integrations

New and Changed Functionality—Release 3.1(4)

Automatic Gain Control Minimum Threshold Registry Setting

Cisco Unity Automatically Moves Undeliverable Messages to the Failed Directory

Cisco Unity Conversation Available in Taiwan Mandarin

Cisco Unity Is Globally Thread Safe

Speed Control During Message Playback

New and Changed Functionality—Release 3.1(3)

AMIS

Cisco Unity Bridge

Cisco Unity Visual Messaging Interface Address Book

Cisco Unity Visual Messaging Interface Message Notification

Message Addressing Option

New and Changed Functionality—Release 3.1(2)

AMIS

Enhanced Failover

New and Changed Functionality—Release 3.1(1)

Accessing the Cisco Unity Administrator on Another Server

Account Used to Initially Access the Cisco Unity Administrator

Advanced Settings Tool

Allowing Multiple Domain Accounts to Map to a Single Subscriber Account

"All Ports Busy" Message in Event Notification Utility

Automatic Gain Control

Bulk Edit Utility

Bulk Logout Utility

Cisco Unity Customization Worksheets

Cisco Unity Diagnostic Tool

Cisco Unity Import Utility

Cisco Unity Visual Messaging Interface

Delete Voice Messages Only Option

Enhanced Failover

GrantUnityAccess Utility

Identified Subscriber Messaging

Increased Class of Service Granularity

Moving Subscribers in Exchange 2000

Private Messages Are Announced

Speed Control During Message Playback

Trivial Subscriber Phone Password Check

Installation and Upgrade Notes

Automatic Gain Control Setting Adjustment

Failover and AMIS: Restriction Table Is Not Automatically Replicated Between Servers

Physical Storage and Disk Configuration for Cisco Unity

Upgrade Effect on Diagnostic Traces and the Dialogic Quiet Parameter

Upgrading from Cisco Unity Version 2.x

Using Japanese Text to Speech

Installing an External Modem on a Cisco MCS-7835

Limitations and Restrictions

Dual NICs

Failover and the Cisco Unity Bridge

Search Scope for the Cisco Unity Visual Messaging Interface Address Book

Search Scope for Inbound Messages from the Cisco Unity Bridge

Subscriber Lookups Fail to Find Subscriber Names in Japanese

Windows Terminal Services

Workaround for Installing Cisco Unity by Using Terminal Services

Caveats

Open Caveats—Release 3.1(5)

Resolved Caveats—Release 3.1(5)

Resolved Caveats—Release 3.1(4)

Resolved Caveats—Release 3.1(3)

Resolved Caveats—Release 3.1(2c)

Resolved Caveats—Release 3.1(2b)

Resolved Caveats—Release 3.1(2)

Documentation Updates

Errors

Automatic Gain Control Setting: Online Help in Advanced Settings Tool

Recording Phone Calls with Live Record: Cisco Unity System Administration Guide and Cisco Unity User Guide

Setting Up the Secondary Server for Failover: Cisco CallManager 3.x Integration Guide

Uninstalling Failover on a Cisco Unity 3.1 System: Cisco Unity Failover Guide

Changes

Backup and Restore: Cisco Unity System Administration Guide and Cisco Unity Troubleshooting Guide

Cisco Unity-CM TSP: Cisco Unity Integration Guides for Various Phone Systems

Default Diagnostic Traces: Cisco Unity Troubleshooting Guide

RJ-11 Connector Pinout: Cisco Unity Installation Guide

Set Volume Utility: Cisco Unity Troubleshooting Guide

Omissions

Configuring Failover on the Primary and Secondary Servers: Cisco Unity Failover Guide

Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes: Cisco Unity System Administration Guide and Networking in Cisco Unity

Replacing the Exchange Server: Cisco Unity Installation Guide

Upgrading a Cisco Unity 3.0 or 3.1 System When Failover Is Configured: Cisco Unity Installation Guide

Upgrading from Exchange 5.5 to Exchange 2000: Cisco Unity Installation Guide

Upgrading from Exchange 5.5 to Exchange 2000 When Failover Is Configured: Cisco Unity Installation Guide

Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes

Unity Messaging System Mailbox

UAmis Mailbox

UOmni Mailbox

Replacing the Exchange Server

Task List for Replacing the Exchange 2000 Server

Task List for Replacing the Exchange 2000 Server When Failover Is Configured

Task List for Replacing the Exchange 5.5 Server

Task List for Replacing the Exchange 5.5 Server When Failover Is Configured

Task List for Replacing Exchange 2000 Installed on the Cisco Unity Server with Exchange 2000 Installed on a Separate Server

Task List for Replacing Exchange 5.5 Installed on the Cisco Unity Server with Exchange 5.5 Installed on a Separate Server

Uninstalling Cisco Unity on the Secondary Server

Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured

Task List for Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured

Confirming That the Secondary Server Is Inactive

Disabling Automatic Failover

Configuring Failover on the Primary Server

Configuring Failover on the Secondary Server

Troubleshooting

Cisco Unity Demonstration System

Limits on a Cisco Unity Demonstration System

Using a Dual Phone System Integration with a Cisco Unity Demonstration System

Converting a Cisco Unity Demonstration System to a Standard System

Cisco Unity Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center


Release Notes for Cisco Unity Release 3.1(5)


Revised October 25, 2002

These release notes describe upgrade instructions, new and changed support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Unity Release 3.1(5).

Access the latest software upgrades for Cisco Unity on the Cisco Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Contents

These release notes contain the following sections:

System Requirements, and Supported Hardware and Software

Determining the Software Version

AMIS and Voice Connector Requirements for Upgrading to Cisco Unity 3.1(5)

Upgrading to Cisco Unity 3.1(5) from Version 3.0 or 2.4(6)

Upgrading to Cisco Unity 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs

New and Changed Support

New and Changed Functionality

Installation and Upgrade Notes

Limitations and Restrictions

Caveats

Documentation Updates

Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes

Replacing the Exchange Server

Uninstalling Cisco Unity on the Secondary Server

Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured

Troubleshooting

Cisco Unity Demonstration System

Cisco Unity Documentation

Obtaining Documentation

Obtaining Technical Assistance

System Requirements, and Supported Hardware and Software

Refer to Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

Compaq Service Pack for ProLiant DL380 G2 Server

A customer-provided Compaq ProLiant DL380 G2 server with a Magma expansion chassis requires installation of service pack SP20496, available from the Compaq website at ftp://ftp.compaq.com/pub/softpaq/sp20001-20500/sp20496.exe.

Security Issues

Microsoft Security Update Q326830

Cisco Unity servers are vulnerable to the types of attacks described in Microsoft Security Bulletin MS02-045 on the Microsoft TechNet website. This vulnerability allows an attacker to send a specially crafted packet request that causes denial of service on the target server and compromises the system.

To ensure that Cisco Unity is not affected, we strongly recommend that you download and install Security Update Q326830 from the Microsoft website.

Nimda Virus

To prevent the Cisco Unity server from being infected with the Nimda virus, install the Nimda patch as documented in the "Installing the Nimda Patch and Connecting the Cisco Unity Server to the Network" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.

For additional information about the Nimda virus and about security in general, refer to:

Cisco Unity: Interim Process for Preventing and Recovering from the Nimda Virus on Cisco.com at http://www.cisco.com/warp/public/788/AVVID/nimda_fix_unity.html.

White Paper: Security Best Practices for Cisco Unity 3.0 on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/security.htm.

Compatibility Matrix: Cisco Unity 3.1(5), the Cisco Unity-CM TSP, and Cisco CallManager

Cisco Unity version 3.1(5) has been qualified for the following version combinations with the Cisco Unity-CM TSP and Cisco CallManager.


Note Note that Cisco CallManager Support Patch (sp) releases are not listed in the table unless they affect compatibility with Cisco Unity or the Cisco Unity-CM TSP. If not listed, a support patch has the same compatibility as the base release. In addition, rereleased versions—for example, 3.x(xa) rereleased as 3.x(xb)—are assumed to have the same compatibility unless noted.


Table 1 Supported Version Combinations for Cisco Unity 3.1(5), the Cisco Unity-CM TSP, and Cisco CallManager

Cisco Unity
Cisco Unity-CM
TSP
Cisco CallManager

3.1(5)

6.0(2b),
6.0(2a),
6.0(2)

3.2(2), 3.2(1), 3.1(4), 3.1(3), 3.1(2), 3.1(1), 3.0(12), 3.0(11), 3.0(10), 3.0(9)



Note For the most current list of all qualified version combinations—including combinations qualified since the release of Cisco Unity 3.1(5)—refer to Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/tspmtrx.htm.


Compatibility Matrix: Cisco Unity 3.1(5) and the Software on Client Workstations

Cisco Unity version 3.1(5) has been qualified for the following version combinations with the software on client workstations. Windows 95 and Outlook 97 are not supported.

Table 2 Supported Version Combinations for Cisco Unity 3.1(5) and the Software on Client Workstations

Cisco Unity
Cisco Unity ViewMail
for Microsoft Outlook
Operating System
Messaging Client
Internet Browser

3.1(5)

3.1(x),
3.0(x)

Windows XP,
Windows 2000,
Windows NT 4.0,
Windows ME,
Windows 98

Outlook 2002 (XP),
Outlook 2000,
Outlook 98

Internet Explorer 6.0,
Internet Explorer 5.5 (plus Service Pack 2)



Note For the most current list of all qualified version combinations—including combinations qualified since the release of Cisco Unity 3.1(5)—refer to Compatibility Matrix: Cisco Unity and the Software on Client Workstations on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/clientmx.htm.


Compatibility Matrix: Cisco Unity 3.1(5), and Required and Optional Third-Party Service Packs

Cisco Unity version 3.1(5) has been qualified for the following version combinations with required and optional third-party service packs.

Table 3 Supported Version Combinations for Cisco Unity 3.1(5), and Required and Optional Third-Party Service Packs 

Cisco Unity
Required Third-Party Service Packs
Optional Third-Party Service Packs

3.1(5)

Exchange 2000 SP 2,
Exchange 5.5 SP 4,
Internet Explorer 5.5 SP 2,
MSXML3 SP 1,
SQL Server 2000 SP 1,
SQL Server 2000 hot fix (Knowledge Base
article Q315395),
Windows 2000 SP 2

Exchange 2000 SP 3,
SQL Server 2000 SP 2,
Windows 2000 SP 3


Determining the Software Version

This section contains procedures for determining the version in use for the following software:

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector

RealSpeak Engine

Cisco Unity

To determine the Cisco Unity version in use by using the Cisco Unity Administrator


In the Cisco Unity Administrator, go to the System > Configuration > Software Versions page. The Cisco Unity version is displayed in the Cisco Unity Version field.


Note This procedure does not work to determine if Cisco Unity version 3.1(2c) or 3.1(2b) is in use. Instead, see the following procedures, "To determine the Cisco Unity version in use by using the AvCsMgr.exe file (for version 3.0(4) and later only)" or "To determine if Cisco Unity version 3.1(2b) is in use."



To determine the Cisco Unity version in use by using the AvCsMgr.exe file (for version 3.0(4) and later only)


Step 1 Browse to the CommServer directory.

Step 2 Right-click AvCsMgr.exe, and click Properties.

Step 3 In the Properties window, click the Version tab.

Step 4 In the Item Name list, click Product Version. The Cisco Unity version is displayed in the Value window.


Note This procedure does not work to determine if Cisco Unity version 3.1(2b) is in use. Instead, see the following procedure, "To determine if Cisco Unity version 3.1(2b) is in use."



To determine if Cisco Unity version 3.1(2b) is in use


Step 1 Browse to the directory CommServer\ConfigurationSetup.

Step 2 Locate the Setup.exe file. If the file date is 2/1/2002 12:46AM, and the file size is 896 KB, the version is 3.1(2b).


Cisco Unity-CM TSP

To determine the Cisco Unity-CM TSP version in use


Step 1 Browse to the WinNT\System32 directory.

Step 2 Right-click the Avskinny.tsp file, and click Properties.

Step 3 In the Properties window, click the Version tab. The Cisco Unity-CM TSP version is displayed in the Product Version setting.


Cisco Unity Voice Connector

To determine the Voice Connector for Exchange 2000 version in use


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to
C:\Program Files\Exchsrvr\VoiceGateway\bin\LocalizedFiles\ENU.

Step 3 Right-click SetupRes.dll, and select Properties.

Step 4 Click the Version tab in the Properties window to view the File Version.


To determine the Voice Connector for Exchange 5.5 version in use


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Windows Explorer or My Computer, browse to
C:\Exchsrvr\connect\voice\bin\LocalizedFiles\ENU.

Step 3 Right-click SetupRes.dll, and select Properties.

Step 4 Click the Version tab in the Properties window to view the File Version.


RealSpeak Engine

To determine the RealSpeak ENU language engine version in use


Step 1 Browse to the CommServer\RealSpeak\Engine directory.

Step 2 Right-click the file Enu_g2p.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The DLL version is displayed in the Value window and corresponds to the following RealSpeak versions:

2.1.0.0 = RealSpeak ENU language engine version 2.0(1)

2.11.0.0 = RealSpeak ENU language engine version 2.1(1)

3.6.0.0 = RealSpeak ENU language engine version 3.0(1)


To determine the RealSpeak base engine version in use


Step 1 Browse to the CommServer\RealSpeak\Api\Lib directory.

Step 2 Right-click the file Lhstts.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The DLL version is displayed in the Value window and corresponds to the following RealSpeak versions:

2.1.0.0 = RealSpeak base engine version 2.0(1)

2.11.0.0 = RealSpeak base engine version 2.1(1)

2.12.0.0 = RealSpeak base engine version 3.0(0)

2.13.0.0 = RealSpeak base engine version 3.0(1)


AMIS and Voice Connector Requirements for Upgrading to Cisco Unity 3.1(5)


Note If the Cisco Unity system is version 3.1(3) or later, skip this section.


Depending on the Cisco Unity system configuration, do the task(s) in the applicable section before you upgrade to Cisco Unity version 3.1(5):

AMIS on a Cisco Unity 3.1(2) System with the Voice Connector for Exchange 2000

AMIS on a Cisco Unity 3.0(x) Through 3.1(1) System

Cisco Unity 2.4(6.x) Through 3.1(2) Servers That Use the Voice Connector for Messaging

AMIS on a Cisco Unity 3.1(2) System with the Voice Connector for Exchange 2000


Note If the Cisco Unity Voice Connector is installed on an Exchange 5.5 server, skip this section.


An upgrade from Cisco Unity version 3.1(2) requires reinstalling the Cisco Unity 3.1(x) Voice Connector for Exchange 2000.

Before upgrading to Cisco Unity 3.1(5), uninstall all instances of the Voice Connector for Exchange 2000. See the procedure "To uninstall the Cisco Unity 3.1(x) Voice Connector for Exchange 2000" in the "Uninstalling the Cisco Unity Voice Connector" section.

Note that you reinstall the Voice Connector for Exchange 2000 during the upgrade to Cisco Unity 3.1(5).

AMIS on a Cisco Unity 3.0(x) Through 3.1(1) System

An upgrade from Cisco Unity versions 3.0(x) through 3.1(1) requires reinstalling the AMIS feature and the Cisco Unity Voice Connector. Before upgrading to Cisco Unity 3.1(5):

1. Uninstall all instances of the Voice Connector. See the applicable procedures in the "Uninstalling the Cisco Unity Voice Connector" section.

2. Record the Names, Dial IDs, Node IDs, and Delivery Phone Numbers of all AMIS locations.

3. Record the AMIS subscriber information. See the procedure "To use the Subscriber Information Dump utility to record AMIS subscriber information" in this section.

4. Delete all AMIS locations. See the procedure "To delete AMIS locations," in this section.

5. Delete all AMIS subscriber accounts. See the procedure "To delete AMIS subscribers" in this section.

Note that you reinstall AMIS (and the Voice Connector) during the upgrade to Cisco Unity 3.1(5).

To use the Subscriber Information Dump utility to record AMIS subscriber information


Step 1 Go to the Cisco Unity Utilities page of the Software Center website at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-util.

Step 2 Download the latest version of the Subscriber Information Dump utility (SubscriberInfoDump.zip) to the Cisco Unity server. The utility dumps out specific information about subscribers to a comma-separated value (CSV) file.

Step 3 On the Cisco Unity server, start the Subscriber Information Dump utility.

Step 4 Specify the file name and location for the resulting CSV file.

Step 5 In the Data to Include in Output File list, select Alias, First Name, Last Name, Primary Extension, and Location Name.

Note that as of this writing, the Subscriber Information Dump utility does not dump out the Remote Mailbox Number of AMIS subscribers. This information must be recorded manually and added to the CSV file.

Step 6 Click Start. The utility creates the CSV file in the specified location.

Step 7 Open the CSV file in a spreadsheet program or a text editor.

The first row contains the names of the column headers, and the subsequent rows contain subscriber data. AMIS subscribers are associated with AMIS locations, and the rows of subscriber data are grouped by Location Name.

Step 8 Modify the CSV file so that it can be used with the External User Import utility to import the AMIS subscriber information after upgrading Cisco Unity:

a. Either delete all rows that contain data for non-AMIS subscribers and save the file, or copy all the rows that contain data for AMIS subscribers to another file and save it.

b. Change the column header names in the first row as follows:

ALIAS
FIRST_NAME
LAST_NAME
EXTENSION
DISPLAY_NAME

Step 9 Add a column header called REMOTE_USER_ID to the first row. Add the Remote Mailbox Numbers for the AMIS subscribers.

Step 10 Save and close the file.


To delete AMIS locations


Step 1 In the Cisco Unity Administrator, go to Network > Locations.

Step 2 Click the Find icon.

Step 3 Select an AMIS location to be deleted from the list, and click View.

Step 4 If you have not already done so, record the information on the page.

Step 5 Click the Delete icon, and click OK in the warning dialog box.

Step 6 Repeat steps 2 through 5 to find and delete all AMIS locations.


To delete AMIS subscribers


Step 1 In the Cisco Unity Administrator, go to any Subscribers > Subscribers page.

Step 2 Click the Find icon.

Step 3 Indicate whether to search by alias, extension, first name, or last name.

Step 4 Enter the appropriate name, alias, or extension. You can also enter * to display a list of all subscribers, or enter one or more characters or values followed by * to narrow your search.

Step 5 Click Find.

Step 6 In the list of matches, click the name of the subscriber to display the record.

Step 7 Click the Delete icon, and click OK in the warning dialog box.

Step 8 Repeat steps 2 through 7 to find and delete all AMIS subscribers.


Cisco Unity 2.4(6.x) Through 3.1(2) Servers That Use the Voice Connector for Messaging

In an installation that has multiple Cisco Unity servers that access separate directories, the Cisco Unity Voice Connector is used when subscribers on one Cisco Unity server send messages by using blind addressing to subscribers on another Cisco Unity server. An upgrade from Cisco Unity versions 2.4(6.x) through 3.1(2) requires reinstalling the Voice Connector.

Before upgrading to Cisco Unity 3.1(5), uninstall all instances of the Voice Connector. See the applicable procedures in the "Uninstalling the Cisco Unity Voice Connector" section.

Note that you reinstall the Voice Connector during the upgrade to Cisco Unity 3.1(5).

Uninstalling the Cisco Unity Voice Connector

The uninstall procedure that you use depends on the Cisco Unity Voice Connector version and whether the Voice Connector is installed on an Exchange 2000 server or on an Exchange 5.5 server:

To uninstall the Cisco Unity 3.1(x) Voice Connector for Exchange 2000

To uninstall the Cisco Unity 3.0(x) Voice Connector for Exchange 2000

To uninstall the Cisco Unity 3.1(2) or later Voice Connector for Exchange 5.5

To uninstall the Cisco Unity 3.1(1), 3.0(x), or 2.4(6.x) Voice Connector for Exchange 5.5

The Voice Connector version is displayed on the wizard during installation. To determine the version for an already installed Voice Connector, see the procedures in the "Cisco Unity Voice Connector" section in the "Determining the Software Version" section.

To uninstall the Cisco Unity 3.1(x) Voice Connector for Exchange 2000


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Add/Remove Programs in Windows Control Panel, select the Voice Connector.

Step 3 Follow the on-screen prompts to uninstall the Voice Connector.


To uninstall the Cisco Unity 3.0(x) Voice Connector for Exchange 2000


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 Confirm that the Windows Services program is closed.

Step 3 Open the Exchange System Manager. (On the Windows Start menu, click Programs > Microsoft Exchange > System Manager.)

Step 4 Expand Connectors.

Step 5 Right-click the Voice Connector, and click Stop.

Step 6 After the service stops, right-click the Voice Connector, and click Delete.

Step 7 Expand Servers\<Server name>\<Storage group>\Mailbox Store\Mailboxes for the server on which the Voice Connector was installed.

The mailboxes are listed in the right pane. The mailbox name for the Voice Connector is AvExchangeIVC.

Step 8 Right-click Mailboxes, and click Run Cleanup Agent.

Step 9 After the Cleanup Agent has run, right-click the mailbox, and select Purge. Click Yes in the warning dialog box.

Step 10 Close the Exchange System Manager.


To uninstall the Cisco Unity 3.1(2) or later Voice Connector for Exchange 5.5


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In Add/Remove Programs in Windows Control Panel, select the Voice Connector.

Step 3 Follow the on-screen prompts to uninstall the Voice Connector.


To uninstall the Cisco Unity 3.1(1), 3.0(x), or 2.4(6.x) Voice Connector for Exchange 5.5


Step 1 Log on to the Exchange server on which the Voice Connector is installed.

Step 2 In the CD-ROM drive, insert Cisco Unity Disc 1 for the version of the Voice Connector that is installed, and browse to the VoiceGateway folder.

Step 3 Double-click Setup.exe, and click Next. The Setup program detects that the Voice Connector is already installed, so the Uninstall dialog box appears.

Step 4 Click Next, and click Yes in the warning dialog box.

Step 5 When the uninstall is complete, click Finish to exit the program and restart the server.


Upgrading to Cisco Unity 3.1(5) from Version 3.0 or 2.4(6)

For upgrades from version 3.0 or 2.4(6), you download the applicable full Cisco Unity 3.1(5) compact disc images from the Software Center website, and install from those disc images.

Table 4 Cisco Unity 3.1(5) Compact Disc Images and File Sizes 

Number
Contents
Download File
Extracted Files
Download File Plus
Extracted Files
CD1

Cisco Unity application files and
ENU language files

390 MB

658 MB

1048 MB

CD2

ENG, ENA, and ENZ language files

297 MB

370 MB

667 MB

CD3

DEU, NOR, and NLD language files

328 MB

404 MB

732 MB

CD4

FRA, SVE, and ITA language files

310 MB

384 MB

694 MB

CD5

ESP, ESO, and PTB language files

360 MB

436 MB

796 MB

CD6

JPN, CHS, CHT, and KOR language files

341 MB

449 MB

790 MB

CD7

Voice card driver files

228 MB

316 MB

544 MB


You also download the Service Packs compact disc images from the Software Center website.

The Cisco Unity 3.1(5) disc images contain only Cisco Unity. They do not contain any third-party software.

The third-party software and an activation code (which is provided through the regular upgrade or new system order process) are required to do an upgrade from version 2.4(6) and to do a new installation.


Caution Diagnostic traces that were set before an upgrade are not preserved and must be reset after the upgrade.

Task List for Upgrading to Cisco Unity Version 3.1(5) from Version 3.0 or 2.4(6)

1. If you are not upgrading from Cisco Unity 3.0 simple failover to Cisco Unity 3.1 enhanced failover, skip to Task 2.

If you are upgrading from Cisco Unity 3.0 simple failover to Cisco Unity 3.1 enhanced failover, uninstall simple failover. Refer to the "Uninstalling Simple Failover on a Cisco Unity 3.0 System" section in the appendix "Uninstalling Failover on a Cisco Unity System" of the Cisco Unity Failover Guide (available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/fail/fail31/fog_300.htm).

2. Use Table 4 to determine which compact disc images to download, and confirm that the computer you are using has enough hard disk space for the applicable full Cisco Unity 3.1(5) images and at least another 1.5 GB of hard disk space for the Service Packs images.

3. On a computer with a high-speed Internet connection, go to the Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

4. Click Cisco Unity 3.1 under "Cisco Unity Software."

5. Download CiscoUnity3.1.5ServicePacks-ENU-CD1of3.exe and CiscoUnity3.1.5ServicePacks-ENU-CD2of3.exe, which contain required service packs, and optionally, CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe., which contains optional service packs (Windows 2000 Service Pack 3 and Exchange 2000 Service Pack 3).

6. Return to the Cisco Unity 3.1 Software Download page, and click Download Full CD Images of 3.1 Software.

7. Enter your contact information, and click Submit.

8. Use Table 4 to determine which compact disc images to download, and download only those images. You always need Disc 1.

9. When all downloads are complete, extract the files for each disc to a separate directory:

a. In Windows Explorer, double-click the file.

b. In WinZip, specify a directory to which the files will be extracted.

The default locations of the unzipped Service Packs files are:

Exchange 2000
Service Pack 2

CiscoUnity3.1.5ServicePacks-ENU-CD2of3\Exchange_2k_sp2\update.exe

Exchange 2000
Service Pack 3

CiscoUnity3.1.5ServicePacks-ENU-CD3of3\Exchange_2k_sp3\update.exe

SQL Server 2000
Service Pack 1

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1\x86\setup\setupsql.exe

SQL Server 2000
hot fix

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1_Patch\Sqlservr.exe

and

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1_Patch\exe\Sqlservr.pdb

Windows 2000
Service Pack 2

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\Win2K_SP2\w2ksp2.exe

Windows 2000
Service Pack 3

CiscoUnity3.1.5ServicePacks-ENU-CD3of3\Win2K_SP3\w2ksp3.exe


Note We recommend that you disable the Windows 2000 Updater program that gets installed and enabled by default with Service Pack 3.



10. If you plan to install the 3.1(5) upgrade from new compact discs, create a new 3.1(5) Cisco Unity Disc <N> with each updated image.

11. Delete the files CiscoUnity3.1.5ServicePacks-ENU-CD1of3.exe, CiscoUnity3.1.5ServicePacks-ENU-CD2of3.exe, and CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe, if applicable, to free disk space.

12. Begin the upgrade process. Refer to the instructions in the applicable chapter of the Cisco Unity Installation Guide (available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm):

"Upgrading a Cisco Unity 3.0 or 3.1 System."


Caution When upgrading from Cisco Unity 3.0, confirm that the system key is plugged into the server when you run the Cisco Unity Setup program. Otherwise, the system key will not be updated with Cisco Unity 3.1 features, and Cisco Unity may not start.

"Upgrading a Cisco Unity 2.x System to Version 3.1."

When you are ready to upgrade the Cisco Unity software:

a. If the system is using Exchange 2000: Install Exchange 2000 Service Pack 2 by double-clicking CiscoUnity3.1.5ServicePacks-ENU-CD2of3\Exchange_2k_sp2\Update.exe and following the on-screen prompts.

b. If you created new compact discs, insert the 3.1(5) Cisco Unity Disc 1 in the CD-ROM drive.

Otherwise, browse to the location of the updated Cisco Unity Disc 1 image.

c. Double-click Setup.exe.

d. Restart the server a second time to ensure that all of the Cisco Unity services start correctly. (See caveat CSCdx05115.)

13. If you are required to reinstall AMIS: Reinstall AMIS. Refer to the Networking in Cisco Unity guide: Follow the "Task List: Setting Up Cisco Unity to Use AMIS" in the "AMIS Networking" chapter. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm. (Note that installing the Voice Connector is part of setting up AMIS, so skip to Task 15.)

14. If you are required to reinstall the Voice Connector but not to reinstall AMIS: Reinstall the Voice Connector. Refer to the Networking in Cisco Unity guide: Do the applicable procedure(s) for your version of Exchange in the "Setting Up the Voice Connector" section in the "SMTP Networking" chapter. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

15. Enable automatic gain control, and adjust the volume of recordings for greetings and recorded names. See the "Automatic Gain Control" section.


Upgrading to Cisco Unity 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs

For upgrades from any previous version of Cisco Unity 3.1(x), you download the self-extracting patch file for Cisco Unity version 3.1(5) from the Software Center website, then update the Cisco Unity version 3.1(3) or Cisco Unity version 3.1(1) compact disc images with the Cspatch executable file. You can then make new compact discs to install the upgrade or install directly from updated disc images on the Cisco Unity server. (Cisco Unity versions 3.1(4) and 3.1(2) were available only from the Software Center website, so there are no 3.1(4) or 3.1(2) patch files available.)

Table 5 Updated Cisco Unity 3.1(5) Disc Images 

Number
Contents
CD1

Cisco Unity application files and ENU language files

CD2

ENG, ENA, and ENZ language files

CD3

DEU, NOR, and NLD language files

CD4

FRA, SVE, and ITA language files

CD5

ESP, ESO, and PTB language files

CD6

JPN, CHS, CHT, and KOR language files

CD7

Voice card driver files


You also download the Service Packs compact disc images from the Software Center website.

If you plan to make new compact discs, use a computer with a read/write CD-ROM drive to do the upgrade.

Note that if you do not have Cisco Unity version 3.1(3) or 3.1(1) compact disc images, follow the task list in the "Upgrading to Cisco Unity 3.1(5) from Version 3.0 or 2.4(6)" section.


Caution Diagnostic traces that were set before an upgrade are not preserved and must be reset after the upgrade. Dialogic quiet parameters are preserved in an upgrade only if the voice card software is not reinstalled during the Cisco Unity Setup program. If the Install Voice Card Software check box is checked during Setup, quiet parameters will be lost and must be reset after the upgrade.

Task List for Upgrading to Cisco Unity Version 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs

1. Confirm that the computer you are using has at least 400 MB of hard disk space available to download a self-extracting patch file and at least another 1.5 GB available for the Service Packs images.

2. On a computer with a high-speed Internet connection, go to the Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

3. Click Cisco Unity 3.1 under "Cisco Unity Software."

4. Download one of the following files, depending on the version of Cisco Unity compact discs that you want to update:

CiscoUnity3.1.5PatchFrom3.1.3.exe

Will update all Cisco Unity 3.1(3) discs

CiscoUnity3.1.5PatchFrom3.1.3-CD1-only.exe

Will update only Cisco Unity 3.1(3) Disc 1 (Cisco Unity application files and ENU language files)

CiscoUnity3.1.5PatchFrom3.1.1.exe

Will update all Cisco Unity 3.1(1) discs

CiscoUnity3.1.5PatchFrom3.1.1-CD1-only.exe

Will update only Cisco Unity 3.1(1) Disc 1 (Cisco Unity application files and ENU language files)


5. Return to the Cisco Unity 3.1 Software Download page, and download CiscoUnity3.1.5ServicePacks-ENU-CD1of3.exe and CiscoUnity3.1.5ServicePacks-ENU-CD2of3.exe, which contain required service packs, and optionally, CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe, which contains optional service packs (Windows 2000 Service Pack 3 and Exchange 2000 Service Pack 3).

6. In Windows Explorer, double-click CiscoUnity3.1.5PatchFrom<Version>.exe or CiscoUnity3.1.5PatchFrom<Version>-CD1-only.exe.

7. In WinZip, specify a directory to which the files will be extracted. Within the directory you specify, files are extracted to the directory CiscoUnity3.1.5PatchFrom<Version> or CiscoUnity3.1.5PatchFrom<Version>-CD1-only, with subdirectories CD1, CD2, CD3, CD4, CD5, CD6, and CD7, as applicable.

8. Extract the files for each Service Packs disc—CiscoUnity3.1.5ServicePacks-ENU-CD1of3.exe, CiscoUnity3.1.5ServicePacks-ENU-CD2of3.exe, and optionally, CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe—to a separate directory:

a. In Windows Explorer, double-click the file.

b. In WinZip, specify a directory to which the files will be extracted.

The default locations of the unzipped Service Packs files are:

Exchange 2000
Service Pack 2

CiscoUnity3.1.5ServicePacks-ENU-CD2of3\Exchange_2k_sp2\update.exe

Exchange 2000
Service Pack 3

CiscoUnity3.1.5ServicePacks-ENU-CD3of3\Exchange_2k_sp3\update.exe

SQL Server 2000
Service Pack 1

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1\x86\setup\setupsql.exe

SQL Server 2000
hot fix

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1_Patch\Sqlservr.exe

and

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\SQL2000_SP1_Patch\exe\Sqlservr.pdb

Windows 2000
Service Pack 2

CiscoUnity3.1.5ServicePacks-ENU-CD1of3\Win2K_SP2\w2ksp2.exe

Windows 2000
Service Pack 3

CiscoUnity3.1.5ServicePacks-ENU-CD3of3\Win2K_SP3\w2ksp3.exe


Note We recommend that you disable the Windows 2000 Updater program that gets installed and enabled by default with Service Pack 3.



9. Delete the following files to free disk space:

CiscoUnity3.1.5ServicePacks-ENU-CD1of3.exe

CiscoUnity3.1.5ServicePacks-ENU-CD2of3.exe

CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe (if applicable)

CiscoUnity3.1.5PatchFrom<Version>.exe or CiscoUnity3.1.5PatchFrom<Version>-CD1-only.exe

10. Go to a partition with at least 3GB of free disk space.

11. Using Table 5, determine which compact disc images you need to patch. You always need Disc 1.

12. On the partition, create a CiscoUnity3.1.3 or CiscoUnity3.1.1 directory, and create subdirectories for the compact discs you need to patch (for example, CD1, CD2, and so on).

13. Copy the Cisco Unity 3.1(3) or Cisco Unity 3.1(1) discs that you need to patch to the corresponding subdirectories.

14. In the CiscoUnity3.1.5PatchFrom<Version> or CiscoUnity3.1.5PatchFrom<Version>-CD1-only directory, browse to a CD<N> subdirectory, and double-click Cspatch.exe.

15. In the Patch window, choose the language in which you want to see the Cspatch.exe information.

16. Follow the on-screen prompts. You will be prompted to browse to the subdirectories that you created in Task 12. for each disc image. The patch may take several minutes. When you see the message "The patch succeeded," continue with Task 17.

If the patch process fails or is canceled, the 3.1(3) Cisco Unity Disc <N> or 3.1(1) Cisco Unity Disc <N> image that you made in Task 13. is restored to its original state. Correct any problems, and begin again with Task 14.

17. If you plan to install the 3.1(5) upgrade from new compact discs, create a new 3.1(5) Cisco Unity Disc <N> with the updated image.

18. Repeat Tasks 14. through 17. for each of the remaining Cisco Unity 3.1(3) or Cisco Unity 3.1(1) disc images. All of the disc images that you want to use for the upgrade must be updated before continuing with the next task.

19. If you are upgrading from Cisco Unity version 3.1(2) or 3.1(1): Install the SQL Server 2000 hot fix. Refer to the "Installing SQL Server Hot Fix for Service Pack 1" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.

20. If the system is using Exchange 2000: Install Exchange 2000 Service Pack 2 by double-clicking CiscoUnity3.1.5ServicePacks-ENU-CD2of3\Exchange_2k_sp2\update.exe and following the on-screen prompts.

21. Upgrade Cisco Unity. Refer to the instructions in the applicable section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide:

"Upgrading Cisco Unity Software, or Adding or Changing Licensed Features."

"Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured."

When you are ready to upgrade the Cisco Unity software:

a. If you created new compact discs, insert the 3.1(5) Cisco Unity Disc 1 in the CD-ROM drive.

Otherwise, browse to the location of the updated Cisco Unity Disc 1 image.

b. Double-click Setup.exe.

c. Restart the server a second time to ensure that all of the Cisco Unity services start correctly. (See caveat CSCdx05115.)

22. If you are required to reinstall AMIS: Reinstall AMIS. Refer to the Networking in Cisco Unity guide: Follow the "Task List: Setting Up Cisco Unity to Use AMIS" in the "AMIS Networking" chapter. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm. (Note that installing the Voice Connector is part of setting up AMIS, so skip to Task 24.)

23. If you are required to reinstall the Voice Connector but not to reinstall AMIS: Reinstall the Voice Connector. Refer to the Networking in Cisco Unity guide: Do the applicable procedure(s) for your version of Exchange in the "Setting Up the Voice Connector" section in the "SMTP Networking" chapter. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

24. Enable automatic gain control, and adjust the volume of recordings for greetings and recorded names. See the "Automatic Gain Control" section.


New and Changed Support

New and Changed Support—Release 3.1(5)

Additional Counters in Performance Analysis Tool

Cisco Unity and third-party software performance counters have been added to the Performance Analysis tool, for use in monitoring and collecting Cisco Unity performance data on systems running Exchange 2000, either on the Cisco Unity server or on a separate server. When Exchange is on a separate server, warning messages are generated in the Event Viewer for counters that are not tracked for the configuration.

For information on setting up and running the Performance Analysis tool, refer to White Paper: Monitoring Cisco Unity Performance, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/perfmon.htm.

Optional Microsoft Service Packs Qualified for Use with Cisco Unity


Note Before installing any qualified optional service pack on the Cisco Unity server, confirm that the manufacturer of any optional third-party software or hardware that you plan to install on the Cisco Unity server—or that is already installed—also supports the service pack for use with its product.


The following Microsoft service packs have been qualified for optional use with Cisco Unity 3.1(x):

Microsoft Exchange 2000 Service Pack 3

Windows 2000 Service Pack 3 (We recommend that you disable the Windows 2000 Updater program that gets installed and enabled by default with Service Pack 3.)


Note At the time these release notes were published, there were known issues with Cisco IDS Host Sensor and Windows 2000 Service Pack 3. If you plan to install the Cisco IDS Host Sensor Agent on the Cisco Unity server or if it is already installed, we recommend that you confirm that Cisco IDS Host Sensor has resolved the issues before you install Service Pack 3.


The service packs are available on the downloadable disc image CiscoUnity3.1.5ServicePacks-ENU-CD3of3.exe, on the Software Center website.

For the most current list of all supported Microsoft service packs—including service packs qualified since the release of Cisco Unity version 3.1(5)—refer to the "Supported Optional Microsoft Service Packs" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

Symantec pcAnywhere No Longer Required

With Cisco Unity version 3.1(5) and later, Symantec pcAnywhere is no longer a software requirement. A remote administration application is still required, however, and pcAnywhere and Windows Terminal Services are supported for use with Cisco Unity. (See also the "Windows Terminal Services" section.)

Terminal Services is included with Windows 2000, which is included with a Cisco Unity baseline system but must be purchased from another vendor for a Cisco Unity component system. pcAnywhere must be purchased from another vendor for Cisco Unity baseline and component systems (it is no longer shipped with Cisco Unity).

Updated and New Tools in Tools Depot

The following tools have been updated or are new in the Tools Depot. The Tools Depot icon is available on the Cisco Unity server desktop.

Table 6 Changes to the Tools Depot

Updated Tools
New Tools

Advanced Settings Tool

Bulk Edit

Codec Checker

Disaster Recovery Backup

Disaster Recovery Restore

External User Import

Set Volume

Subscriber Information Dump

For information on the changes to a tool, see the revision history in online Help for the tool.

Bridge Traffic Analyzer

Gather Unity System Info

Migrate Subscriber Data

Port Usage Analyzer

Schedule Unity Restart

For information on how a tool works, see online Help for the tool.


The left pane of the Tools Depot lists all available tools by category. To display online Help for a tool, click the name in the left pane. To run the tool, double-click the name.

Some tools work only with selected versions of Cisco Unity. If a tool does not appear in the Tools Depot, it does not work with the version of Cisco Unity currently running.

New and Changed Support—Release 3.1(4)

Automatic Gain Control Registry Settings Can Be Updated with the Set Volume Utility

The registry settings for AGCtargetDB, AGCsampleSize, AGCgainThreshold, and AGCminimumThreshold can be updated on a Cisco Unity 3.1(4) system by using the Set Volume utility. The default values for the registry settings should be used for all Cisco Unity version 3.1(2c) and later upgrades.

Confirm that you have the latest version of the Set Volume utility by doing the procedure "To download and install the latest version of the Set Volume utility" in the "Automatic Gain Control" section.

If you are upgrading to Cisco Unity version 3.1(4), do the procedure "To adjust greeting and name recordings by using the Set Volume utility (version 3.1(3) and later only)" in the "Automatic Gain Control" section.

Backup and Restore Procedures for the Servers on a Cisco Unity Failover System

Procedures for backing up and restoring the primary and secondary servers on a failover system are currently being devised and tested. Afterward, the procedures will be published in a tech tip on Cisco.com, at http://www.cisco.com/warp/public/788/AVVID/vmum.shtml.

Exchange 2000 Service Pack 2 Required

Exchange 2000 Service Pack 2 is required for Cisco Unity version 3.1(4), on a system running Exchange 2000.

For the most current list of all software requirements, refer to the "Software Requirements" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

Tools Depot

The following tools have been updated or are new in the Tools Depot. The Tools Depot icon is available on the Cisco Unity server desktop.

Table 7 Changes to the Tools Depot

Updated Tools
New Tools

Advanced Settings

Bulk Edit

DbWalker

FullDBExport/Import

Global Subscriber Manager

PublicDL Builder

Subscriber Information Dump

Uninstall

Volume Adjust

For information on the changes to a tool, see the revision history in online Help for the tool.

Codec Checker

Disaster Recovery Backup

Disaster Recovery Restore

Permissions Wizard

Remove Subscriber Properties

Set WAV Format

For information on how a tool works, see online Help for the tool.


The left pane of the Tools Depot lists all available tools by category. To display online Help for a tool, click the name in the left pane. To run the tool, double-click the name.

Some tools work only with selected versions of Cisco Unity. If a tool does not appear in the Tools Depot, it does not work with the version of Cisco Unity currently running.

New and Changed Support—Release 3.1(3)

AMIS-Compliant Voice Messaging Systems Qualified for Use with Cisco Unity

The following AMIS-compliant voice messaging systems have been qualified for use with Cisco Unity:

Avaya Interchange with Intuity Audix Multimedia Message System, for use with Cisco Unity version 3.1(3) and later.

Centigram Voice Mail, for use with Cisco Unity version 3.1(2) and later.


Note When using AMIS networking with voice gateways, make sure the gateways can pass DTMF in both directions and that both the sending and receiving nodes can detect these digits. Otherwise, AMIS messages may be lost or misdirected, or other malfunctions may occur.


For the most current list of all supported AMIS-compliant voice messaging systems—including systems qualified since the release of Cisco Unity version 3.1(3)—refer to the "Supported AMIS-Compliant Voice Messaging Systems" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

Automatic Gain Control

Cisco Unity automatic gain control gives subscribers consistent message playback levels through the normalization of recordings. Automatic gain control (AGC) affects only recordings.

AGC is on by default and set to a target value of -26 dB in all new Cisco Unity version 3.1(2c) and later installations, and in upgrades from version 3.0(x) and 2.4(6.x). For Cisco Unity version 3.1(x) systems upgraded to 3.1(2c) and later, AGC is off by default, and the target dB value is not changed from the pre-upgrade setting.

AGC does not improve the quality of recordings (for example, garbled incoming messages). It addresses only volume issues, and is applied to voice samples after they have passed through all external hardware.

Because automatic gain control is enabled by default in Cisco Unity version 3.1(2c) and later, systems upgraded to 3.1(2c) and later may experience a problem where the existing greeting and name recordings sound louder than new greetings and names recorded after the upgrade. To avoid this problem, use the Set Volume utility to match the existing greeting and name recordings to the gain levels of Cisco Unity after the upgrade.

If the Cisco CallManager region is set to use the G.711 codec, the record and playback settings in the Cisco Unity-CM TSP also may need to be changed prior to adjusting the greetings and names.

The Set Volume Utility

Confirm that you have the latest version of the Set Volume utility by doing the first procedure, "To download and install the latest version of the Set Volume utility."

The second procedure, "To adjust greeting and name recordings by using the Set Volume utility (version 3.1(3) and later only)," levels all WAV files on the Cisco Unity server to the same value, and provides instructions to adjust the playback level if needed.

Do these procedures on a Cisco Unity system upgraded to version 3.1(2c) or later.

To download and install the latest version of the Set Volume utility


Step 1 Go to the Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Step 2 Click Cisco Unity Utilities under "Cisco Unity Software."

Step 3 Compare the version of the file SetVolume.zip in the table to the Set Volume utility version on the Cisco Unity system.

Step 4 If the version in the table is later than the version currently installed on the system, download the file SetVolume.zip.

Step 5 Specify a directory to which the files will be downloaded.

Step 6 In Winzip, double-click Setup.exe.

Step 7 Click OK.

Step 8 Click Change Directory, and browse to the directory CommServer\Utilities\VolumeAdjust.

Step 9 Follow the on-screen prompts to complete the installation.


To adjust greeting and name recordings by using the Set Volume utility (version 3.1(3) and later only)


Step 1 Exit the Cisco Unity Administrator.

Step 2 On the Cisco Unity server desktop, double-click the Tools Depot icon.

Step 3 If you do not have a Cisco CallManager or a dual integration, skip to step Step 5.

If you have a Cisco CallManager or a dual integration, and the Cisco CallManager region is set to use the G.711 codec, in the left pane, under Administrative Tools, double-click Wave Gain.

Step 4 Confirm that both Record Gain and Playback Gain are set to 0.

Step 5 In the left pane of the Tools Depot window, go to Audio Management Tools, and double-click Set Volume.

Step 6 In the Set Greetings and Voice Names window, click Select All.

Step 7 Confirm that the Save Original Files check box is checked, then enter the location to which the backup copy of the original recorded names and greetings files will be saved.

Step 8 In the Options section, verify the following values:

New Target dB

-26

Sample Size

8000

Max dB Adjustment

5

Min. dB Threshold

-45


Step 9 Confirm that the Save Above Volume Options check box is checked. Note that setting New Target dB to a value other than zero turns on automatic gain control.

Step 10 Click Set Volume Level.

Step 11 When "Done" appears in the Set Volume window, all existing greeting and name recordings have been adjusted to the New Target dB level. Click OK, then click Exit.

Step 12 If you do not have a Cisco CallManager or a dual integration, you have completed all necessary steps in this procedure.

If you have a Cisco CallManager or a dual integration, and the Cisco CallManager region is set to use the G.711 codec, start the Cisco Unity Administrator.

Step 13 Listen to a recording (for example, a subscriber greeting) by using the Media Master and TRaP (Telephony Record and Playback).

If the volume of the recording is acceptable, you have completed all necessary steps in this procedure.

If the volume of the recording is too quiet, continue with Step 14.

Step 14 In the left pane of the Tools Depot window, under Audio Management Tools, double-click Wave Gain.

Step 15 Increase the Playback Gain value by one or two dB. Listen to the volume of a recording.

If the volume of the recording is acceptable, note the Playback Gain value and continue with Step 16.

If the volume of the recording is still too quiet, repeat this step.

Step 16 In the left pane of the Tools Depot window, under Administrative Tools, double-click Advanced Settings Tool.

Step 17 In the Cisco Unity Settings pane, click Set Wave Gain dB Adjustment for Playback.

Step 18 Enter the new value determined in Step 15, and click Set.

Step 19 Click Exit.


NetIQ VoIP Manager 2.0 for Cisco Unity

Installing the agent for NetIQ VoIP Manager 2.0 for Cisco Unity on the Cisco Unity server is supported for use with Cisco Unity version 3.1(1) and later. NetIQ VoIP Manager monitors system status, availability, and performance for the components on a Cisco Unity server.

Octel Analog Networking

Octel Analog Networking is supported. Octel Analog Networking allows Cisco Unity—together with the Cisco Unity Bridge—to exchange voice messages with other voice messaging systems that support Octel Analog Networking. The following systems are supported:

Avaya Octel 100

Avaya Octel 200/300

Avaya Octel 250/350

Avaya Unified Messenger

Octel Digital Networking is not supported.


Note When using the Bridge, if your network configuration includes voice gateways, make sure the gateways can pass DTMF in both directions and that both the sending and receiving nodes can detect these digits. Otherwise, messages may be lost or misdirected, or other malfunctions may occur.


For more information, refer to the "Bridge Networking" chapter in Networking in Cisco Unity, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Permissions Wizard

The Permissions Wizard utility is available on the Cisco Software Center website. Permissions Wizard automatically grants many of the permissions required by the installation and service accounts. (In addition, if you are setting up failover, the wizard can also grant permissions for the failover account.) The Help file for the wizard explains which permissions still need to be granted manually after the wizard finishes. Download PermissionsWizard.exe and PermissionsWizard-Readme.zip from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml. (Click Cisco Unity Utilities under "Cisco Unity Software.")

Phone System Integrations Qualified for Use with Cisco Unity

The Intecom E14 Millennium has been qualified for use with Cisco Unity version 3.1(3) and later.

For the most current list of all supported phone system integrations, refer to the "Supported Phone System Integrations" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

SQL Server 2000 Hot Fix

The SQL Server 2000 hot fix that is described in Microsoft Knowledge Base article Q315395 is required for Cisco Unity 3.1(3), both for a system running SQL Server 2000 and for a system running MSDE 2000. For download instructions, see the "Upgrading to Cisco Unity 3.1(5) from Version 3.0 or 2.4(6)" section or the "Upgrading to Cisco Unity 3.1(5) by Using Version 3.1(3) or Version 3.1(1) Compact Discs" section, as applicable. Installation instructions are available in the Cisco Unity Installation Guide (required for the upgrade) on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.

Telecommunications Data Card Qualified for Use with the Cisco Unity Bridge

The Brooktrout Technology TR114+P4L PCI analog telecommunications data card has been qualified for use on the Cisco Unity Bridge server only, version 2.0(1) and later. (The card is not supported on the Cisco Unity server.) For information on the card, refer to Appendix A of the Cisco Unity Bridge Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge/big/index.htm.

For the most current list of all supported voice cards, refer to the "Supported Voice Cards" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

Tools Depot

Tools Depot gathers a wide range of Cisco Unity utilities in one location. To access Tools Depot, browse to the directory CommServer\Utilities\ToolsDepot, and double-click ToolsDepot.exe.

The left pane of the Tools Depot lists all of the available tools by category. To display Help for a tool, click the name in the left pane. To run the tool, double-click the name.

Some tools work only with selected versions of Cisco Unity. If a tool does not appear in the Tools Depot, it does not work with the version of Cisco Unity currently running.

Virus Scanning Software Qualified for Use with Cisco Unity

Computer Associates InoculateIT for Microsoft Windows NT and Windows 2000, version 4.53, build 627 or later, has been qualified for use with Cisco Unity version 3.1(1) and later.

For the most current list of all supported virus-scanning software, refer to the "Supported Optional Third-Party Software" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

New and Changed Support—Release 3.1(2)

AMIS Support

An upgrade from Cisco Unity version 3.0(x) to 3.1(2) requires reinstalling the AMIS feature, as we have included comprehensive improvements to AMIS functionality in version 3.1(2). For upgrade information, see the "AMIS and Voice Connector Requirements for Upgrading to Cisco Unity 3.1(5)" section. For details on functionality improvements, see "AMIS" in the "New and Changed Functionality—Release 3.1(2)" section.

IBM X232 and X250 Servers

The IBM X232 and X250 servers are qualified for use only with Cisco Unity version 3.1(2) and later.

If you are using one of the IBM servers with Dialogic D/240PCI-T1 voice cards and Cisco Unity does not start, do the following procedure.

To disable the Remote Access Connection Manager


Step 1 On the Windows Start menu, click Settings > Control Panel > Services.

Step 2 Right-click the Remote Access Connection Manager service, and click Properties.

Step 3 On the General tab, set the Remote Access Connection Manager service to Disabled, then click OK.

Step 4 Restart the Cisco Unity server.

Step 5 After Cisco Unity starts, on the Windows Start menu, click Settings > Control Panel > Services.

Step 6 Right-click the Remote Access Connection Manager service, and click Properties.

Step 7 On the General tab, change the Startup Type to Manual.

Step 8 Click Start, then click OK. The Remote Access Connection Manager service will start manually. (It is important to make sure that the Remote Access Connection Manager service manually starts again, as you cannot access the system remotely by using pcAnywhere or Windows Terminal Services when it is not running.)


New and Changed Support—Release 3.1(1)

AMIS Support

An upgrade from Cisco Unity version 3.0(x) to 3.1(2) will require reinstalling the AMIS feature, as we have included comprehensive improvements to AMIS functionality in version 3.1(2). We recommend that you wait until the release of Cisco Unity 3.1(2) for optimum AMIS functionality.

Integrations

Cisco Unity version 3.1 integrates with the following additional phone systems:

Cisco CallManager version 3.2 (IP integration)

For the most current list of all supported integrations, refer to the "Supported Phone System Integrations" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

TOPCALL Fax

All versions of the TOPCALL third-party fax product are supported with Cisco Unity version 3.1(1) and later.

For the most current list of all qualified third-party fax server products, refer to the "Supported Fax Server Software" section in Cisco Unity 3.1 System Requirements, and Supported Hardware and Software on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/31_sysrq.htm.

New and Changed Functionality

New and Changed Functionality—Release 3.1(5)

Bridge Traffic Analyzer Utility

The Bridge Traffic Analyzer is a report-generation utility that reads the call and queue log files on the Cisco Unity Bridge server and generates a graph and a summary table that can be saved as a comma-separated value (CSV) file. The Bridge Traffic Analyzer is available in Tools Depot. The Tools Depot icon is available on the Cisco Unity server desktop. The Bridge Traffic Analyzer is also available on the Cisco Unity Utilities page of the Software Center website at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-util.

For more information, refer to the "Bridge Traffic Analyzer" section in the "Bridge Networking" chapter of Networking in Cisco Unity, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm. Also refer to the Help file that comes with the Bridge Traffic Analyzer.

Cisco Unity Conversation Available in New Languages

The Cisco Unity conversation (telephone user interface, or TUI) is now available in the following languages:

Brazilian Portuguese

Korean

For information on making a Cisco Unity phone language available for use, refer to the "Multiple Languages" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Connecting Cisco Unity to a Different Exchange 2000 Server

It is no longer necessary to manually disconnect Cisco Unity from an Exchange 2000 server when you want to connect to a different Exchange 2000 server. Rerunning the Cisco Unity Server Configuration wizard overwrites old settings and moves the Unity_<servername> mailbox.

When Cisco Unity is connected to an Exchange 5.5 server, you must manually disconnect Cisco Unity from the Exchange server before running the Cisco Unity Server Configuration wizard to connect to an Exchange 2000 server.

Note that disconnecting Cisco Unity from Exchange 2000 and reconnecting to Exchange 5.5 is not supported. In addition, disconnecting Cisco Unity from Exchange 5.5 and reconnecting to Exchange 2000 when Cisco Unity is configured for Digital Networking is not recommended.

Full-Mailbox Check for Outside Callers

Cisco Unity can be set to check if a subscriber mailbox is full when an outside caller tries to leave a message for the subscriber. When the mailbox is full, the outside caller hears the following prompt: "Sorry. You cannot record a message for <Subscriber>. This mailbox is full." After playing the prompt, Cisco Unity transfers the caller back to the Opening Greeting and logs the following message to the Windows Application Event log: "The mailbox for [Alias: subscriber alias] is full. The subscriber cannot send or receive new voice messages until mailbox size is reduced. Mailbox size limits are specified in the message store, not Cisco Unity."

By default, the feature is turned off, and Cisco Unity does not check if a subscriber mailbox is full before allowing an outside caller to leave a message. Messages that are left for subscribers with full mailboxes are delivered to the Unaddressed Messages distribution list, which should be monitored by the Cisco Unity system administrator or another subscriber.

To enable the feature, you edit two registry keys:

A key to allow you to specify whether Cisco Unity checks if a subscriber mailbox is full when an outside caller wants to leave a message.

A key to allow you to enable or disable the prompt that informs callers that they cannot leave a message when the mailbox is full. (Editing this key is optional.)

See the procedure "To enable the full-mailbox check and prompt for outside callers," in this section, for detailed instructions. Note that enabling full-mailbox checks for outside callers does not affect how Cisco Unity handles messages from other Cisco Unity subscribers to a full mailbox; Cisco Unity sends a non-delivery receipt (NDR) to subscribers who send messages to a full mailbox. Also, Cisco Unity behaves as if the full-mailbox check feature is disabled when:

An outside caller leaves a message for a call handler whose recipient is a distribution list (for example, the default recipient for the Operator call handler is the Unaddressed Messages list).

An outside caller leaves a message for an interview handler.


Note A typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated.


To enable the full-mailbox check and prompt for outside callers


Step 1 On the Cisco Unity server desktop, double-click the Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Full Mailbox Check Feature.

Step 4 From the New Value list, click 1, and then click Set so that Cisco Unity checks to see if a subscriber mailbox is full when an outside caller wants to leave a message, and that when it is full, Cisco Unity does not allow the caller to leave a message.

Step 5 When prompted, click OK. You do not need to restart Cisco Unity to enable the registry change.

Step 6 In the Unity Settings pane, click Full Mailbox Check Prompt.

Step 7 From the New Value list, click 1, and then click Set so that Cisco Unity plays a prompt to inform callers that they cannot leave a message when the mailbox is full.

Step 8 When prompted, click OK. You do not need to restart Cisco Unity to enable the registry change.

Step 9 Click Exit.


Message Store Monitor Service

The Message Store Monitor service (AvMsgStoreMonitorSvr) notifies the Cisco Unity service (AvCsMgr) when it detects a new or changed message in a subscriber mailbox. The Cisco Unity service then activates notification devices such as MWIs and pagers appropriately. Previously, both services were integrated. The separation improves performance and stability of the system. During upgrades, a version of the Cisco Unity Server Configuration wizard separately registers the Message Store Monitor service.

Migrate Subscriber Data Utility

If the Cisco Unity system uses AMIS or the Cisco Unity Bridge to network with another voice messaging system, you may want to use the Migrate Subscriber Data utility when the time comes to migrate the AMIS or Bridge subscribers to Cisco Unity. If the AMIS or Bridge subscribers have existing Exchange mailboxes, the Migrate Subscriber Data utility creates a Cisco Unity subscriber account by combining the Cisco Unity-specific data from an existing AMIS or Bridge subscriber account (such as the recorded name) with an existing mail user. The utility then deletes the AMIS or Bridge subscriber account and, optionally, deletes the associated Active Directory contact (or Exchange 5.5 custom recipient).

The Migrate Subscriber Data utility is available in the Tools Depot. The Tools Depot icon is available on the Cisco Unity server desktop. The Migrate Subscriber Data utility is also available on the Cisco Unity Utilities page of the Software Center website at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-util. Refer to the Help file that comes with the utility for more information.

Warning Tone for End of Recording Can Be Enabled in Cisco CallManager Integrations

This feature applies only to integrations with Cisco CallManager.

Cisco Unity can be set to sound a warning tone before reaching the maximum allowable message length while callers record their messages. By default, the warning tone is disabled. There are two settings that can be customized:

Record Termination Warning Time

The number of milliseconds before reaching the maximum message length when the warning tone will sound. A setting greater than 0 enables the warning tone.

Minimum Recording Length
for Termination Warning

The maximum recording length in milliseconds for which no warning tone will sound. This setting prevents the warning tone from sounding for shorter recordings such as voice names.


For example, if the maximum message length is set for 300 seconds and the Record Termination Warning Time setting is set for 10 seconds, the warning tone will sound after 290 seconds of recording—10 seconds before the recording limit is reached and the recording session is terminated.

To enable the warning tone for the end of recording


Step 1 On the Cisco Unity server, on the Windows Start menu, click Run.

Step 2 In the Open field, enter Regedit, and press Enter.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for a Cisco Unity failover system, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 4 Go to HKEY_LOCAL_MACHINE\Software\ActiveVoice\MIU\1.0\Initialization.

Step 5 In the subkey, on the Edit menu, click New > DWORD Value. A new value appears in the subkey.

Step 6 Enter the name Record Termination Warning Time, and press Enter.

Step 7 Double-click the Record Termination Warning Time value. The Edit DWORD Value dialog box appears.

Step 8 Under Base, click Decimal.

Step 9 In the Value Data field, enter the time in milliseconds before reaching the maximum message length when the warning tone will sound (we recommend entering 10000), and click OK.

Step 10 On the Edit menu click New > DWORD Value. A new value appears in the subkey.

Step 11 Enter the name Minimum Recording Length for Termination Warning, and press Enter.

Step 12 Double-click the Minimum Recording Length for Termination Warning value. The Edit DWORD Value dialog box appears.

Step 13 Under Base, click Decimal.

Step 14 In the Value Data field, enter the maximum recording length in milliseconds for which no warning tone will sound (we recommend entering 30000), and click OK.

Step 15 Close the Registry Editor.

Step 16 For the settings to take effect, exit and restart the Cisco Unity software.


New and Changed Functionality—Release 3.1(4)

Automatic Gain Control Minimum Threshold Registry Setting

The AGCminimumThreshold registry setting controls the minimum dB level of an incoming recording that Cisco Unity attempts to adjust. The setting prevents silence in a message and background hiss from being adjusted. The AGCminimumThreshold has a default setting of -45 dB and an allowable range of -35 dB to -55 dB. See caveat CSCdx18244.

Cisco Unity Automatically Moves Undeliverable Messages to the Failed Directory

The registry key HKEY_LOCAL_MACHINE/Software/Active Voice/UnityUMR/1.0/ MtaFailedPath has been added to automatically move blocking messages to the directory (<Drive on which Cisco Unity is installed>:\CommServer\UnityMTA\Failed.

Messages to subscribers without mail user records can prevent other messages from being delivered. When a message is moved to the Failed directory, the following error message appears in the Event log: "AvUMR_MC Error UMR Thread Error 101."

To avoid subscriber perception of delayed message delivery or lost messages, review any message(s) from the Failed directory at least once per day. Determine the affected subscriber(s) from the Event log error message, and repair or recreate the account(s) on Cisco Unity. Possible causes for a Cisco Unity subscriber without a mail user record include no Exchange mailbox, or a failed import during an upgrade from version 2.4(6). Note that the import tool can create subscribers with spaces following the last name if the CSV file itself has entries with spaces.

When the problem with the subscriber account is resolved, move the message(s) from the Failed directory back to the UnityMTA folder for a second delivery attempt.

You can set up an automatic notification of a message being placed in the Failed directory by using the Event Notification utility.

To set up automatic notification when a message is moved to the Failed directory


Step 1 On the Cisco Unity server desktop, double-click the Tools Depot icon.

Step 2 In the left pane of the Tools Depot window, under Reporting Tools, double-click Event Notification Utility.

Step 3 In the Notification Utility Administrator window, click File > New Event > NT Event Log.

Step 4 In the Event window, enter an Event Display Name, and check the Active check box.

Step 5 In the Source field, enter AvUMR_MC.

Step 6 In the Event ID field, enter 101.

Step 7 Choose a message notification type (e-mail, voice message, or SMTP message) and click the corresponding tab.

Step 8 Check the Send Message check box, complete the fields in the tab window, and click OK.

Step 9 Close the Notification Utility Administration and the Tools Depot windows.


For information on the problem that resulted in this new functionality, see caveat CSCdw41721.

Cisco Unity Conversation Available in Taiwan Mandarin

The Cisco Unity conversation (telephone user interface, or TUI) is available in Taiwan Mandarin.

For information on making a Cisco Unity phone language available for use, refer to the "Multiple Languages" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Cisco Unity Is Globally Thread Safe

An application-level workaround has been implemented by default in Cisco Unity version 3.1(4) and later that makes Cisco Unity interact with Windows Audio Compression Manager (ACM) in a globally thread-safe manner.

The workaround was developed for a problem that a few sites experienced when using both G.711 and G.729a codecs with Cisco Unity. Most sites running Cisco Unity in a dual codec environment did not experience the problem. The problem is recorded in Bug Toolkit, ID CSCae08069.

The change can have a performance impact on larger systems and may require a registry setting to be disabled (the performance impact increases as the number of ports increases). To disable the registry setting, do the following procedure.

To disable the ForceGlobalAcmThreadSafety registry setting


Step 1 Start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 3 Expand the key
HKEY_LOCAL_MACHINE\Software\ActiveVoice\UnityAvWav\1.0.

Step 4 If the UnityAvWav\1.0\ForceGlobalAcmThreadSafety key exists, skip to Step 11.

Otherwise continue with Step 5.

Step 5 On the Edit menu, from HKEY_LOCAL_MACHINE\Software\ActiveVoice,

click New Key.

Step 6 Name the new key UnityAvWav.

Step 7 Click the new UnityAvWav key, then on the Edit menu, click New Key.

Step 8 Name the new key 1.0.

Step 9 Click the new 1.0 key, then on the Edit menu, click New Dword.

Step 10 Name the new Dword ForceGlobalAcmThreadSafety.

Step 11 Double-click ForceGlobalAcmThreadSafety, and set the Value to 0.

Note that a value of 1 enables Global ACM Thread Safety.

Step 12 Close the Registry Editor.

Step 13 For the settings to take effect, restart the Cisco Unity server.


Speed Control During Message Playback

The Cisco Unity conversation lets subscribers toggle among the following speed settings while listening to a message over the phone:

Press 4 once

Slow playback

Press 4 again

Slower playback

Press 6 once

Fast playback

Press 6 again

Faster playback


Note that the speed-control feature is disabled in Cisco Unity versions 3.1(2c) and 3.1(3) to address port lock-up issues related to caveat CSCdw88890. It has been re-enabled in version 3.1(4).

For more information about the speed-control options available with Cisco Unity 3.1(4), refer to the "To Change Playback Speed" section in the "Changing Recording and Playback Settings" chapter of the latest Cisco Unity User Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/ug/index.htm.

New and Changed Functionality—Release 3.1(3)

AMIS

The search scope of inbound AMIS messages is now controlled by the settings in the Cisco Unity Administrator on the Network > Primary Location > Addressing Options page. For more information, refer to the "Primary Location Settings" chapter of Networking in Cisco Unity, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Cisco Unity Bridge

The Cisco Unity Bridge acts as a networking gateway between a Cisco Unity system and an Octel system on an Octel analog network. The Bridge communicates with Octel servers by using the Octel analog networking protocol and with Cisco Unity servers by using the Digital Networking protocol, which is based on the Voice Profile for Internet Mail (VPIM) protocol, with proprietary extensions. The Bridge acts as a gateway between two different messaging servers, and it must be installed on a separate and dedicated platform.

For more information, refer to the following documents:

Cisco Unity Bridge Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge/big/index.htm.

"Bridge Networking" chapter of Networking in Cisco Unity, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Cisco Unity Visual Messaging Interface Address Book

A link to the global address book has been added to the navigation bar in the Cisco Unity Visual Messaging Interface (VMI). Subscribers can use it to search for subscriber names and extensions, or to play the recorded names for subscribers. Each address book search returns up to 15 possible matches. Public and private distribution lists are not included. Detailed instructions on performing address book searches are available to subscribers in Cisco Unity VMI online Help.

The Cisco Unity VMI is a system key-controlled feature and can be accessed only if it is purchased. A subscriber with the proper class of service rights can access Cisco Unity VMI at the following URL: http://<Cisco Unity server name>/web/vmi.

Cisco Unity Visual Messaging Interface Message Notification

Cisco Unity Visual Messaging Interface (VMI) message notification is now available so that Cisco Unity VMI subscribers who do not use ViewMail for Microsoft Outlook can receive an e-mail whenever a new voice message arrives. When a Cisco Unity VMI message notification is set up, the URL for the Cisco Unity VMI Inbox is automatically included as a link in the notification that is sent to the subscriber via e-mail. As with previous versions of Cisco Unity, a site must have an SMTP gateway to send text message notifications to text pagers, cell phones, or e-mail addresses.

For information on setting up Cisco Unity VMI notifications for subscribers, refer to the "Subscriber Message Notification Settings" section in the "Subscriber Settings" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm. Detailed instructions on setting up Cisco Unity VMI notifications are available to subscribers in the Cisco Unity User Guide, ActiveAssistant online Help, and Cisco Unity VMI online Help.

The Cisco Unity VMI is a system key-controlled feature and can be accessed only if it is purchased. A subscriber with the proper class of service rights can access Cisco Unity VMI at the following URL: http://<Cisco Unity server name>/web/vmi.

Message Addressing Option

An additional message addressing option is now available that is helpful for organizations with overlapping dial plans on their networked Cisco Unity servers. When subscribers address a message by entering a number, they can enter one number that is made up of the location Dial ID and the extension of the recipient. Cisco Unity first searches for an extension that matches the number. If a match is not found, then Cisco Unity parses the number to find a matching location Dial ID and subscriber extension at that location. For example, if a subscriber addresses a messages to 5551212 and there is a location Dial ID 555 and a subscriber at that location with the extension 1212, then the sender gets a voice name confirmation.

Both primary and delivery locations are included in the search. The scope of the search is dictated by the "Subscriber Searches: Limit Searches To" setting on the Network > Primary Locations > Addressing Options page. For more information refer to the "Digital Networking" and "Primary Location Settings" chapters of Networking in Cisco Unity, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

New and Changed Functionality—Release 3.1(2)

AMIS

AMIS functionality has changed in version 3.1(2). This section summarizes the changes. For more information, refer to the "AMIS Networking" chapter of the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Several pages in the Network section of the Cisco Unity Administrator have been changed to differentiate between the primary location (which identifies the Cisco Unity server to other voice messaging servers) and delivery locations (which contain addressing information about other voice messaging servers). Because of these changes, any AMIS locations created in Cisco Unity prior to version 3.1(2) must be deleted before upgrading Cisco Unity.

AMIS subscribers must be associated with an AMIS delivery location, so the Add Subscriber page in the Cisco Unity Administrator has been changed to enforce this requirement. All AMIS subscriber accounts created in Cisco Unity prior to version 3.1(2) must be deleted before upgrading Cisco Unity.

The External User Import utility is a new utility that creates multiple AMIS subscriber accounts at the same time by using a comma-separated value (CSV) file. The External User Import utility is located on Cisco Unity Disc 1 in the MigrationTools directory.

In installations with two or more Cisco Unity servers networked together, when subscribers address messages to an AMIS delivery location (by using blind addressing) or to an AMIS subscriber, the AMIS transmission originates from the Cisco Unity server on which the AMIS delivery location was created.

This means that only one Cisco Unity server in the network needs to be set up for AMIS. However, all subscribers, no matter which Cisco Unity server they are associated with, can send messages to an AMIS delivery location or AMIS subscriber. The Cisco Unity server configured for AMIS acts as the AMIS "bridgehead" server for the other Cisco Unity servers in the network.

The Cisco Unity Voice Connector has been modified to support AMIS bridgehead topologies. Because of the modifications, the Voice Connector that shipped with Cisco Unity prior to 3.1(2) should be uninstalled before upgrading Cisco Unity.

Enhanced Failover

The secondary Cisco Unity server can initiate failover if the primary Cisco Unity server does not answer a call by the time the secondary server answers it. For traditional, circuit-switched phone systems, this feature requires setting the Dialogic voice messaging ports on the secondary server to answer in three rings (the ports on the primary server are left at the default setting of one ring). For Cisco CallManager, this feature requires setting up the voice messaging ports to forward calls to the secondary server only when the primary server does not answer.

Cisco Unity version 3.1(2) is required for enhanced failover. To use this feature, you must upgrade from Cisco Unity version 3.1(1) to 3.1(2).

Information on installing and maintaining failover is included in the Cisco Unity Installation Guide, the Cisco Unity integration guides, and the Cisco Unity System Administration Guide. The guides are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/index.htm.

If you are upgrading from Cisco Unity 3.0 simple failover to Cisco Unity 3.1 enhanced failover, you must uninstall simple failover first. See "Uninstalling Cisco Unity 3.0 Simple Failover," which is available on Cisco.com at http://www.cisco.com/warp/customer/788/AVVID/vmum.shtml.

New and Changed Functionality—Release 3.1(1)

Accessing the Cisco Unity Administrator on Another Server

When two or more Cisco Unity servers are networked together in an installation, you can access subscriber accounts and the data for other Cisco Unity objects by running the Cisco Unity Administrator on the server on which the object was created. Each Cisco Unity Administrator provides links to the Cisco Unity Administrators on other networked servers on the Unity Servers > Server Chooser page.

The Find Subscriber page in the Cisco Unity Administrator now provides access to subscriber accounts created on other Cisco Unity servers. For more information, refer to the "Cisco Unity Administrator Scope" section in the "Digital Networking" chapter of the Networking in Cisco Unity guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm. Note that this functionality is available only when the subscriber account that is being accessed is associated with a server running Cisco Unity version 3.1(1) or later. Although subscribers associated with a 3.0 Cisco Unity server can be located, an error results when you attempt to access the account.

Account Used to Initially Access the Cisco Unity Administrator

During the Cisco Unity Setup program, you are asked to choose the account that you want to use to administer Cisco Unity for initial setup of the system. You can choose the account that you used to install Cisco Unity, or you can choose another domain account (as long as it is a member of the Local Administrators group on the Cisco Unity server). The account you choose is automatically given access to the Cisco Unity Administrator, by association with a built-in account called Unity Installer_<server name>.

Advanced Settings Tool

The Advanced Settings Tool allows system administrators to safely edit many of the Cisco Unity registry settings. The tool gives a brief overview of each setting, limits edits to specific value ranges, and ensures that edits are consistent with the installed Cisco Unity version. For details, refer to the "Advanced Settings Tool" section in the "Utilities" chapter of the Cisco Unity Troubleshooting Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/tsg/index.htm.

Allowing Multiple Domain Accounts to Map to a Single Subscriber Account

To grant one or more domain accounts access to the Cisco Unity Administrator on one or more Cisco Unity servers without adding a new subscriber account on each server that an administrator needs to access, use the GrantUnityAccess utility. For details, refer to the "Granting Administrative Rights to Other Cisco Unity Servers" section in the "Network Settings" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

"All Ports Busy" Message in Event Notification Utility

A new error message—"All Ports Busy notification"—has been added to the Event Notification utility. The error message is generated when the voice server detects that all of the ports set to answer calls are busy.

Automatic Gain Control

Cisco Unity automatic gain control gives subscribers consistent message playback levels through the normalization of recordings. It is controlled by registry settings, and applied to voice samples after they have passed through all external hardware.

Bulk Edit Utility

Instead of changing subscriber settings on individual subscriber pages in the Cisco Unity Administrator, you can customize the settings for multiple subscribers at the same time by using the Bulk Edit utility. For example, you can change the settings for a group of subscribers associated with an extension range, a class of service, distribution list, or a phone system so that callers phoning these selected subscribers hear a particular language or are transferred to a different operator.

For information on using the utility, see the readme file provided in the BulkEdit.cab file in the Bulk Edit directory (the default location is C:\CommServer\Utilities). Note that the utility is supported by Cisco TAC, despite statements to the contrary in the readme file.

Bulk Logout Utility

When moving users in Exchange 5.5, you can use the Bulk Logout utility instead of DohPropTest to direct the Cisco Unity server(s) to log out of any mailboxes that you plan to move. Unlike DohPropTest, which allowed you to log Cisco Unity out of only one subscriber mailbox at a time, the Bulk Logout utility allows you to log Cisco Unity out of multiple subscriber mailboxes at once. For information on using the utility, refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

The BulkLogout.cab file is located in the Bulk Logout directory (the default location is C:\CommServer\Utilities). Note that the utility is supported by Cisco TAC, despite statements to the contrary in the readme file.

Cisco Unity Customization Worksheets

Two worksheets have been added to Cisco Unity Customization Worksheets:

Ports

System Configuration

The Customization Worksheets are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/wsheets/index.htm.

Cisco Unity Diagnostic Tool

The Cisco Unity Diagnostic Tool allows creating and viewing of diagnostic log files to troubleshoot problems. The tool replaces the diagnostic log functionality in Maestro Tools, and allows the system administrator or Cisco TAC staff to selectively run diagnostic traces at the macro and micro levels. It also allows the system administrator or Cisco TAC staff to create new log files on demand, to configure log settings, to quickly gather Microsoft Windows and Cisco Unity logs, and to disable all traces. For details, refer to the "Cisco Unity Diagnostic Tool" section in the "Utilities" chapter of the Cisco Unity Troubleshooting Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/tsg/index.htm.

Cisco Unity Import Utility

The Cisco Unity Import utility allows you to create multiple subscriber accounts at the same time, either by using information from Exchange mailboxes or from a comma-separated value (CSV) file. The following CSV column headers are either new or have new meanings: ALIAS, DOMAIN_LOCATION, NT40_ALIAS, PAGER1_NUMERIC_AFTER_DIALDIGITS, PAGER1_NUMERIC_DIAL_DELAY, PAGER1_NUMERIC_PHONE_NO, PAGER1_TEXT_SMTP_ADDRESS, PAGER1_TEXT_AFTER_DIALDIGITS, SUBSCRIBER_TYPE, and UPDATE_SUBSCRIBER_ACCOUNT.

For details, refer to the "Preparing for a CSV Import" section in the "Creating Subscriber Accounts" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Cisco Unity Visual Messaging Interface

The Cisco Unity Visual Messaging Interface (VMI) website lets subscribers listen to, compose, reply to, forward, and delete voice messages from a "virtual" Inbox. A subscriber can access Cisco Unity VMI at the following URL: http://<Cisco Unity server name>/web/vmi. Note that the Cisco Unity VMI is not available across a firewall.

To view the Cisco Unity VMI pages, the computer that a subscriber uses to access the site must be configured so that:

Microsoft Internet Explorer allows the scripting of Java applets and Active Scripting, and has Java permissions enabled.

If the virus scanner scans downloaded files, it scans only program files.

When accessing Cisco Unity VMI over a modem connection for the first time, note that the Cisco Unity VMI file is more than 1 MB in size and, therefore, may take longer for a subscriber to download than expected. Detailed instructions on using Cisco Unity VMI are available to subscribers in online Help.

The Cisco Unity VMI is a class of service licensed feature. For information on setting it up for subscribers, refer to the "Class of Service Licensed Features Settings" section in the "Class of Service Settings" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm. Establish trusts across domains so that subscribers do not have to log on each time that they want to play a message.

The Cisco Unity VMI is a system key-controlled feature and can be accessed only if it is purchased.

Delete Voice Messages Only Option

The Cisco Unity conversation offers subscribers the option of deleting only old voice messages, or all old messages—including e-mail and fax messages—from the Deleted Items folder in Outlook. For details, refer to the "Checking Messages" chapter of the Cisco Unity User Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/ug/index.htm.

Enhanced Failover

With the appropriately enabled system key, you can set up a secondary Cisco Unity server for the enhanced failover feature. The primary Cisco Unity server replicates subscriber data on the secondary server at configurable intervals. When the primary server becomes inactive (for example, when you perform maintenance on the server), the secondary server takes over its functions. This feature can be enabled only if you purchase and install an upgrade for the system key.

Cisco Unity version 3.1(2) is required for enhanced failover. To use this feature, you must upgrade from Cisco Unity version 3.1(1) to 3.1(2).

Information on installing and maintaining failover is included in the Cisco Unity Installation Guide, the Cisco Unity integration guides, and the Cisco Unity System Administration Guide. The guides are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/index.htm.

GrantUnityAccess Utility

GrantUnityAccess is a command line utility, located on the Cisco Unity server in the directory in which Cisco Unity was installed (the default location is C:\CommServer). You can use the GrantUnityAccess utility to:

Grant one or more domain accounts access to the Cisco Unity Administrator on one or more Cisco Unity servers without adding a new subscriber account on each server that an administrator needs to access. For details, refer to the "Granting Administrative Rights to Other Cisco Unity Servers" section in "Network Settings" chapter of the Cisco Unity System Administration Guide.

Provide Cisco Unity information about old domain accounts that were migrated from Windows NT to Windows 2000 by using a tool that did not support the SidHistory attribute. This allows Cisco Unity to recognize such accounts when subscribers authenticate by using their old domain accounts. For details, refer to the "About Migrating Users from Windows NT to Windows 2000" section in "Creating Subscriber Accounts" chapter of the Cisco Unity System Administration Guide.

The Cisco Unity System Administration Guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Identified Subscriber Messaging

The Subscribers Are Identified as Message Senders Only If They Log On box on the Configuration > Settings page in the Cisco Unity Administrator allows identified subscriber messaging to be disabled system-wide. The field is applicable only if the phone system provides caller and called-party information to Cisco Unity.

Increased Class of Service Granularity

The class of service (COS) system access settings specify which tasks, if any, that subscribers—including other system administrators—can perform in the Cisco Unity Administrator. By using the new fields on the Subscribers > Class of Service > System Access page in the Cisco Unity Administrator, an administrator can customize access to Cisco Unity in several ways. For example, an administrator can:

Deny access to the Cisco Unity Administrator, or to specific pages in the Cisco Unity Administrator, such as COS, subscriber, or distribution list pages.

Specify read, edit, add, or delete privileges for specific pages in the Cisco Unity Administrator.

Allow access to subscriber pages only for the purpose of unlocking subscriber accounts or changing subscriber passwords.

For more information, refer to the "Class of Service System Access Settings" section in the "Class of Service Settings" of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Moving Subscribers in Exchange 2000

It is now possible to move subscriber mailboxes in Exchange 2000 without having to use the DohPropTest or Bulk Logout utilities to direct the Cisco Unity server(s) to log out of the mailboxes that you plan to move. (The same is not true, however, when you move subscriber mailboxes in Exchange 5.5. For details, see the "Bulk Logout Utility" section.)

The following types of Exchange 2000 mailbox moves are supported:

Moves between Exchange servers.

Moves between Exchange storage groups.

Moves across routing groups.

You are not required to shut down the Cisco Unity server or exit the software to move subscribers between Exchange servers. For more information, refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Private Messages Are Announced

When a message is marked private, the Cisco Unity conversation notifies the subscriber during the message summary.

Speed Control During Message Playback

The Cisco Unity conversation lets subscribers toggle among the following speed settings while listening to a message over the phone:

Press 4 once

Slow playback.

Press 4 again

Slower playback.

Press 6 once

Fast playback.

Press 6 again

Faster playback.


Note that the speed-control feature is disabled in Cisco Unity versions 3.1(2c) and 3.1(3) to address port lock-up issues related to caveat CSCdw88890. It has been re-enabled for 3.1(4).

For more information about the speed-control options available with Cisco Unity 3.1(1), refer to the "To Change Playback Speed" section in the "Changing Recording and Playback Settings" chapter of the Cisco Unity User Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/ug/index.htm.

Trivial Subscriber Phone Password Check

You can set up Cisco Unity to confirm that the digits in the phone passwords that subscribers use to log on to Cisco Unity are not consecutive (for example, 1234). For more information, refer to the "Phone Password Settings" section in the "Account Policy Settings" chapter of the Cisco Unity System Administration Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Installation and Upgrade Notes

For detailed information on upgrading to Cisco Unity version 3.1, refer to the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.

Automatic Gain Control Setting Adjustment

To ensure that automatic gain control settings are correct, do the procedure "To adjust greeting and name recordings by using the Set Volume utility (version 3.1(3) and later only)" in the "Automatic Gain Control" section.

Failover and AMIS: Restriction Table Is Not Automatically Replicated Between Servers

With primary and secondary servers set up for failover, AMIS restriction table settings are currently not replicated. As a result, you must manually set the same AMIS restriction table settings on both servers. For more information, refer to the "AMIS Delivery Options Settings" section in the "AMIS Networking" chapter of Networking in Cisco Unity. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

Physical Storage and Disk Configuration for Cisco Unity

Physical storage and disk configuration recommendations for Cisco Unity, including the use of RAID, have been updated. Refer to White Paper: Physical Storage Best Practices for Cisco Unity with Microsoft Exchange, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/storage.htm. See related caveat CSCdx35168.

Upgrade Effect on Diagnostic Traces and the Dialogic Quiet Parameter

Diagnostic traces that were set before an upgrade are not preserved and must be reset after the upgrade.

The Dialogic quiet parameter is preserved in an upgrade only if the voice card software is not reinstalled during the Cisco Unity Setup program. If the Install Voice Card Software check box is checked during Setup, the quiet parameter will be lost and must be reset after the upgrade.

Upgrading from Cisco Unity Version 2.x

Customers with Cisco Unity versions earlier than 2.3(4.104) must get a new system key to run Cisco Unity version 3.1.

Customers with Cisco Unity version 2.3(4.104) or later need an activation code to upgrade the system key during the Cisco Unity Setup program.

Using Japanese Text to Speech

If you set up Japanese text to speech, confirm that:

The Regional Options fields Your Locale and Language Settings for the System are set to Japanese on the Cisco Unity server (on the Windows Start menu, click Settings > Control Panel > Regional Options > General).

System Locale is set to Japanese on the Cisco Unity server (on the Windows Start menu, click Settings > Control Panel > Regional Options > General > Set Default).

If you make any changes, restart the Cisco Unity server.

Installing an External Modem on a Cisco MCS-7835

Do the following procedure for a Cisco Unity system installed on a Cisco MCS-7835. An external modem requires a serial port connection. U.S. Robotics modems are recommended.

To install an external modem on a Cisco MCS-7835


Step 1 Exit the Cisco Unity software, if it is running, and shut down the server.

Step 2 Connect the modem to an available COM port on the Cisco Unity server.

Step 3 Connect a phone line from the Telco phone jack on the modem to a public phone line.

Step 4 Plug the modem's power connector into a wall outlet, and turn on the modem.

Step 5 Turn on the Cisco Unity server.

Step 6 Follow the manufacturer instructions to configure the modem. Include the following values:

Auto Answer

First ring

Carrier Detect

Normal

Data Terminal Ready

Normal


Step 7 When you are finished configuring the modem, confirm that the LED status indicators for the following functions are lit: Auto Answer, Clear to Send, and Data Terminal Ready.


Limitations and Restrictions

Dual NICs

Cisco Unity is qualified for dual network interface cards (NIC) configured only in adaptive fault-tolerant mode (AFT is the abbreviation used by Dell and IBM), which is also known as network fault-tolerant mode (NFT is the abbreviation used by Compaq). The supported configuration is one NIC designated as primary and the other as secondary, with a single IP address (the NICs do not have individual IP addresses) and both cards connected to the same network. The configuration uses currently supported hardware and applies to all shipping versions of Cisco Unity.

Failover and the Cisco Unity Bridge

When the Cisco Unity server is configured for failover, the Cisco Unity subscriber directory is not synchronized with the Bridge directory while the secondary server is active. When the primary server becomes active again, synchronization resumes automatically. Enhanced failover provides for replication of subscriber data between the primary and secondary Cisco Unity servers, so existing directory information will be available to subscribers no matter which server is active.

When the secondary server is active, subscribers on Cisco Unity and the Octel system can still send and receive messages, but changes to Cisco Unity subscriber accounts will not be replicated to the Bridge immediately. (For example, if you add subscriber accounts on the active secondary server, this information is not replicated to the Bridge until the primary becomes active again.)

Search Scope for the Cisco Unity Visual Messaging Interface Address Book

The Cisco Unity Visual Messaging Interface (VMI) address book does not allow subscribers to search for subscribers associated with other Cisco Unity servers within a dialing domain or in the global directory, regardless of the settings specified on the Network > Primary Location > Addressing Options Page in the Cisco Unity Administrator. Instead, the Cisco Unity VMI address book contains only subscribers who are associated with the local Cisco Unity server. For more details, refer to caveat CSCdx00462. (If you have an account with Cisco.com, you can use Bug Toolkit to find caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.)

Search Scope for Inbound Messages from the Cisco Unity Bridge

The search scope for a matching subscriber extension for inbound messages sent via the Bridge from an Octel user is set to the global directory. There is no way to limit the inbound search scope to either a dialing domain or to the local Cisco Unity server. This limitation is relevant to large organizations that use dialing domains to manage duplicate subscriber extensions.

When a message from the Bridge is received by the Voice Connector, the Voice Connector searches the global directory for a matching subscriber extension. If more than one extension is found, the message is not delivered. The Voice Connector logs an error to the Windows Application Event Log and sends a non-delivery receipt to the sender.

Subscriber Lookups Fail to Find Subscriber Names in Japanese

When a subscriber name is entered in Japanese on the Add Subscriber Page in the Cisco Unity Administrator on a fully localized Japanese version of Cisco Unity, callers cannot find the subscriber name by using directory assistance (pressing 555).

In addition, subscribers cannot easily address messages to a subscriber with a Japanese name in spelling mode; instead, subscribers should address messages by using the subscriber extension.

When a subscriber name is entered in English on the Add Subscriber Page in the Cisco Unity Administrator on a fully localized Japanese version of Cisco Unity, Cisco Unity does not exhibit this behavior. For more details, refer to caveat CSCdv63037. (If you have an account with Cisco.com, you can use Bug Toolkit to find caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.)

Windows Terminal Services

Windows Terminal Services is supported in the following cases:

For use on a Cisco Unity Bridge server with version 2.0(1) and later.

For use with the limitations listed in Table 8 on a Cisco Unity server with version 3.1(4) and later.

Table 8 Windows Terminal Services Limitations with Cisco Unity

Remote Functionality
Cisco Unity
3.1(4) and later
Cisco Unity
3.0(1)-3.1(3)

Install Cisco Unity

Supported with the workaround documented in the "Workaround for Installing Cisco Unity by Using Terminal Services" section

Not supported

Add or delete a subscriber by using the Cisco Unity Administrator

Supported

Not supported

Use the Cisco Unity Diagnostic Tool

Supported

Not supported

Use the Status Monitor in Tools Depot

Not supported

Not supported

Set the dB level of recorded names and greetings by using the Set Volume utility

Not supported

Not supported

Convert recorded names and greetings to a different codec by using the Set Wav Format utility

Not supported

Not supported

Test the Cisco Unity-CM TSP

Not supported

Not supported


Workaround for Installing Cisco Unity by Using Terminal Services

When the Sentinel system driver is not installed on the Cisco Unity server before you try to run the Cisco Unity Setup program by using Terminal Services, the error message "While trying to install the Sentinel System Driver, Windows Installer returned a failure code: 3" appears.

The Sentinel system driver cannot be installed by using Terminal Services. Install the driver by doing the following procedure on the Cisco Unity server before you run the Cisco Unity Setup program.

To install the Sentinel system driver before you run Cisco Unity Setup by using Terminal Services


Step 1 On the Cisco Unity server, insert Cisco Unity Disc 1 in the CD-ROM drive.

Step 2 Browse to the Security Key Setup directory.

Step 3 Double-click SentinelSystemDriver.msi.

Step 4 Follow the on-screen prompts to complete installation of the Sentinel system driver.


Caveats

This section describes severity 1, 2, and select severity 3 caveats.

If you have an account with Cisco.com, you can use Bug Toolkit to find more information on the caveats in this section, in addition to caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

Open Caveats—Release 3.1(5)

Table 9 Cisco Unity Release 3.1(5) Open Caveats 

Caveat Number
Description

CSCae08096

The fail-safe prompt "The system is not available to process your call, please try again later" is heard when Cisco Unity is called, and an AvPhraseServer_MC error is logged in the Application event log.

The problem has been seen in Cisco Unity version 2.4(6) and later, and is due to AvPhraseServerSvr.dll not being registered properly.

Workaround

1. At a command prompt, browse to the CommServer\Components directory.

2. Enter Regsvr32 AvPhraseServerSvr.dll, and press Enter.

CSCae08168

Sometimes adding a new restriction table to the Restriction Tables page in the Cisco Unity Administrator results in a run-time error message. This usually only occurs the first time a system administrator accesses the page. The error prevents the table information from appearing properly on the page.

Workaround

Refreshing the browser page (click Refresh or press F5) will correct the information in the table.

CSCdu25037

During the Cisco Unity Server Configuration wizard, the following error appears: "Failed to reassign the installer's account to the current user."

Workaround

1. Start RegEdit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

2. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

3. Determine if the following key exists:
HKEY_LOCAL_MACHINE\Software\ActiveVoice\CommserverSetup\1.0\Properties\
InstallerObjectId = {XXX}

4. If the key exists, the problem is not CSCdu25037.

If the key does not exist and if you are using SQL Server 2000, open SQL Query Analyzer, open the UnityDB database, run the following query, and copy the resulting ID:

select subscriberobjectid from subscriber where alias = 'Installer'

If the key does not exist and if you are using MSDE 2000, run DohPropTest, and copy AVP_OBJECT_ID for the Installer account from the { to the end of the value.

5. In RegEdit, expand the key
HKEY_LOCAL_MACHINE\Software\ActiveVoice\CommserverSetup\1.0\Properties

6. Add the string key (including the brackets, {} )
InstallerObjectId = {<the ID you copied from SQL>}

7. Rerun the Cisco Unity Server Configuration wizard.

CSCdu37182

IMALEx_MC: Error while trying to log on to MAPI mailbox on a system running Exchange 5.5.

Workaround

Stop and restart the UMR service.

CSCdu74580

In the Cisco Unity Administrator, on the Subscribers > Account Policy > Phone Password Restrictions page, the Number of Passwords to Remember option under Phone Password Uniqueness does not work. Cisco Unity will not recall the last password used, so the same password can be used repeatedly.

There is no workaround.

CSCdv20412

Subscribers are unable to hear and listen to messages when the domain controller in a domain goes down.

There is no workaround.

CSCdv23449

When accessing the Import utility, it does not always display in the GUI language that was selected at the time of installation. The display depends on the order in which the localized versions were built and on which GUI language was selected.

Workaround

1. Browse to the directory CommServer\Multi\Release\Localize\Import, and copy Avimport.exe for the language that is needed.

2. Browse to the directory CommServer\Multi\Release\Apps, and paste the copied file to replace the existing file.

CSCdv77509

When upgrading the Japanese version of Cisco Unity 3.1(x) to 3.1(5), the process fails while copying files. The Japanese error message is "The token `;' could not be parsed."

Workaround

1. In each of the following directories, rename all *_a.txt files to *._a.old:

C:\CommServer\Setup\Common

C:\CommServer\Setup\Commserver

C:\CommServer\Setup\Commserver\<LANG> —for all installed languages

C:\CommServer\Setup\Dialogic\IWF (only if the Cisco Unity server contains Dialogic voice cards)

2. In the same directories, convert all .txt files from Unicode to ANSI encoding. To convert the files, open each file in Notepad, click File > Save As, change Encoding to ANSI, and overwrite the file.

CSCdw00609

When running the Cisco Unity Server Configuration wizard, if you log on to Windows by using a local administrator account instead of a domain administrator account, Syscheck displays the following errors:

"Domain - The specified domain either does not exist or could not be contacted."

"Exchange 2000 - Unable to get basic LDAP information."

Workaround

Log on by using a domain administrator account before you run the Cisco Unity Server Configuration wizard.

CSCdw04464

CSCdw50196

When attempting to import a subscriber Exchange record that contains quotation marks or an apostrophe by using the Cisco Unity Import (AvImport) utility or the Cisco Unity Administrator, the Cisco Unity Administrator Subscriber Profile fields are not populated.

Workaround

Remove the quotation marks or apostrophe from the subscriber Exchange record, and reimport it.

CSCdw10149

After upgrading from Cisco Unity 3.0 to 3.1, Cisco Unity subscribers hear the fail-safe greeting. This occurs when the Cisco Unity services AvCsGateway, AvCsMgr, AvGaenSvr, and AvUMRSyncSvr were running under the Unity_<Servername> account before the upgrade and you rerun the Cisco Unity Server Configuration wizard after the upgrade.

Workaround

If the Active Directory Connector uses a two-way connection agreement between Exchange 5.5 and Windows 2000, do the procedure in the tech tip Configuring Cisco Unity in Mixed Mode When Exchange 5.5 Servers Are in NT 4 Domains. Do the procedure even if the Exchange 5.5 servers are in Windows 2000 domains. The tech tip is available on Cisco.com at http://www.cisco.com/warp/public/788/AVVID/exchange-svr-nt4.html.

If the Active Directory Connector uses a one-way connection agreement between Exchange 5.5 and Windows 2000, do the procedure in the "Configuring a System That Includes Exchange 2000 and Exchange 5.5 Servers" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide. The guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/index.htm.

CSCdw18468

The upgrade to Cisco Unity 3.1 fails if the company name contains a "#" symbol. During the upgrade, a dialog box appears that says, "Invalid directive following `#'."

The text also appears near the bottom of the Tempu.log file.

Workaround

1. Find all IWF files on the system.

2. In each file, search for Company.

3. Remove all "#" symbols from the company name, and save your changes.

4. Rerun the Cisco Unity Setup program.

CSCdw24271

No e-mail is sent to the system administrator when the All Subscribers report is complete.

Workaround

View the report state on the Status Monitor > Report Queue page.

CSCdw29133

Message-store-related functionality appears unstable. Among other symptoms, the Cisco Unity Administrator does not display the Import and Add Subscriber pages correctly, so you cannot import or add Cisco Unity subscribers. The problem occurs when you run the Cisco Unity Server Configuration wizard and choose Exchange 5.5 for the message store, then run the wizard a second time and choose Exchange 2000 for the message store when no Exchange 2000 server is available. This leaves Cisco Unity partially configured for each message store.

Workaround

Rerun the Cisco Unity Server Configuration wizard, and specify the correct version of Exchange.

CSCdw36215

The Cisco Unity Setup program fails and displays the error message: "Insufficient memory available to run Setup. Close all other applications to make more memory available, and try to run Setup again. Error 111." Closing all other applications and rerunning Setup produces the same error. This happens if there is a /3GB switch in the Boot.ini file on the Cisco Unity server.

Workaround

Remove the /3GB switch, rerun the Setup program, and replace the /3GB switch after the Setup program is complete.

CSCdw49611

Transferred calls indicate an incorrect source (Cisco CallManager integration only).

Example: Phone A calls Phone B. Phone B answers the call and transfers to the voice mail of Phone C. When Phone C listens to the message, Cisco Unity plays "Message from Phone B." It should play "Message from Phone A."

There is no workaround.

CSCdw58815

The following error message appears once per second in the Application Event log and in the Events table in the ReportsDB SQL database:

"EventID:100 Source: AvVs_MC Type: Error Exception occurred and handled in File: h:\CommSvr\Sources\Common\Src\AvVariant.cpp at Line:1582 - Error: 80004005H Call stack: 0x0040F7AD AVSCAV~1.EXE: <unknown symbol> xFEDCBA98 <unknown module>: :<unknown symbol> 0x89ABCDEF <unknown module>: :<unknown symbol> 0x77D5298F RPCRT4.dll: RpcRevertToSelf + 858 bytes."

The Application Event log and the Events table will continue to grow in size and can eventually fill up the hard disk.

Workaround

1. Stop the AvRepDirSvrSvc service.

2. Clear the Application Event log.

3. Restart the AvRepDirSvrSvc service.

This is only a temporary solution, and it is likely that the problem will reoccur.

You can disable the AvRepDirSvrSvc service, which prevents the error messages from being generated. Disabling the service does not affect Cisco Unity operation; however, the system will no longer be able to generate reports.

CSCdw59188

The Cisco Unity Administrator does not use the fully qualified domain name when selecting users. If a system administrator uses a workstation that has a different fully qualified domain name than the Cisco Unity server, clicking a subscriber from the search page can result in a 404 error in Internet Explorer.

Workaround

On the computer on which you are having the problem, add the DNS suffix of the Cisco Unity server to the list of suffixes that will be searched by the computer. For Windows 2000 and Windows XP:

1. On the Windows Start menu, click Settings > Network and Dialup Connections.

2. Click the network adapter currently in use.

3. Click Properties.

4. Click Internet Protocol (TCP/IP), and click Properties.

5. Click Advanced.

6. Click the DNS tab.

7. Click Append These DNS Suffixes (In Order).

8. Add the DNS suffix of the computer on which you are having the problem.

9. Add the DNS suffix of the Cisco Unity server.

CSCdw72505

When using the Bulk Edit Utility Overview screen, the Help, Previous, Next, and Exit buttons are protruded. On the Select Subscribers screen, the Japanese Display Name, First Name, and Last Name are corrupted. The same corruption occurs in Public Distribution List display. This defect exists in Cisco Unity JPN.

There is no workaround.

CSCdw74772

Stopping the Cisco Unity Voice Connector for Exchange 5.5 from the Windows Services Control Panel displays a warning that the service terminated unexpectedly, and en error is logged in the Windows System Event log.

This has been seen on installations using AMIS messaging. Sometimes when the Voice Connector is in this state, AMIS messages cannot be delivered. The problem usually happens after the Exchange server on which the Voice Connector is installed has been restarted.

Workaround

Manually stop and start the Voice Connector service until it does not terminate unexpectedly.

CSCdw83879

When trying to create a subscriber using the Cisco Unity Administrator, the error message "Cannot add subscriber" appears. The event can occur when the account used to run the Cisco Unity Administrator is not a member of the Domain Administrators group.

Workaround

Add the Cisco Unity Administrator account to the Domain Administrators group.

CSCdw86051

Cisco Unity does not find matches for three-digit location IDs whose values range from 001 to 020.

See related caveat CSCdw84233.

Workaround

Revise any existing three-digit location IDs in the 001-020 range so that they do not begin with a zero (0). Do not create new location IDs that begin with zero (0).

CSCdw89000

The Cisco Unity Voice Connector for Exchange 2000 private byte memory (or virtual memory) usage increases over time proportionate to the total number of messages processed. The memory consumption is known to happen only on systems using the Voice Connector for Exchange 2000, which includes Cisco Unity 3.1(3) and later installations using either AMIS or the Cisco Unity Bridge for messaging between other voice messaging systems.

Workaround

1. Open the Windows 2000 Task Manager on the Exchange server on which the Voice Connector is installed.

2. Click the Processes tab.

3. Click View > Select Columns.

4. Check the Virtual Memory Size check box.

5. Click OK.

6. Monitor the VM Size column every one to two weeks, or as needed, to see the virtual memory consumed by the Voice Connector, which has the executable name Gwivc.exe.

7. If the Voice Connector consumes more than 150 MB of virtual memory, stop and restart the Voice Connector service by using the Services Control Panel. The service can be stopped and restarted at any time without negatively impacting message delivery.

After restarting the Voice Connector service, initial virtual memory usage will be 3 to 5 MB and will increase gradually over time. The rate of virtual memory consumption is approximately 1 MB per 1,200 messages processed. So a leak of approximately 1 MB per hour would be seen on a Voice Connector processing 1,200 messages per hour. This would be comparable to the traffic handled for a Cisco Unity Bridge server with 16-20 of the Bridge analog ports in continuous use. If this type of traffic continued 24 hours per day, the Voice Connector would require a restart approximately every 5 to 6 days.

CSCdw92582

During the Cisco Unity Server Configuration wizard, the error message "The selected user is not a member of the local administrator's group" may incorrectly appear. The installation account may be a member of the local administrator group but does not have another user right such as "Access this computer from the network." In addition, Tempu.log does not have the exact error message that was returned by the operating system, so troubleshooting is not possible.

Workaround

Run Permissions Wizard to automatically grant permissions required by the installation and service accounts. Download PermissionsWizard.exe and PermissionsWizard-Readme.zip from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml. (Click Cisco Unity Utilities under "Cisco Unity Software.")

CSCdx02239

If you chose Japanese for one of the GUI languages when you installed Cisco Unity, when you run Syscheck, the Check Results table is blank.

CSCdx03440

After upgrading, a Cisco Unity subscriber cannot log on to the Cisco Unity Administrator or the ActiveAssistant without using a local system administrator account.

The problem is due to AvLogMgrSvr.dll not being registered properly.

Workaround

1. At a command prompt, browse to the CommServer\Components directory.

2. Enter Regsvr32 AvLogMgrSvr.dll, and press Enter.

CSCdx05115

When upgrading from some versions of Cisco Unity, you need to restart the server twice before Cisco Unity starts correctly.

CSCdx07945

If you add a member to a distribution list by using Active Directory, the newly added member is not displayed in the Cisco Unity Administrator. Also, if you create a distribution list in Active Directory, add members, and import the distribution list into Cisco Unity, the member list is empty when viewed by using the Cisco Unity Administrator.

Workaround

Add members to a distribution list by using the Cisco Unity Administrator, not Active Directory.

CSCdx08725

For a few minutes after creating a new subscriber account, all messages left by outside callers to the new subscriber are not delivered. The messages are lost and are never delivered to the new subscriber mailbox. A few minutes after the subscriber has been created, messages from outside callers are delivered correctly.

When subscribers try to leave a message to a newly created subscriber, they get a conversation that tells them they cannot address a message to the newly created subscriber. Outside callers do not get this conversation.

The problem occurs with Cisco Unity version 3.0 and later on servers connected to Exchange 2000.

Workaround

Wait a few minutes before leaving messages for a newly created subscriber and before notifying anyone that the subscriber account is available.

Note that the amount of time to wait before leaving messages for a newly created subscriber decreases when Exchange 2000 SP2 or later is installed.

CSCdx13954

Subscriber mailbox extensions in Cisco Unity may disappear at random. It may happen to the same subscriber repeatedly, or multiple subscribers, all at different time intervals. The extension will be missing from the Cisco Unity Administrator and the DOH.

Upon dialing into Cisco Unity, the subscriber hears the opening greeting. Pressing the * key to log on results in the prompt "Sorry, but that is an unrecognized extension."

Workaround

In the Cisco Unity Administrator, enter the extension to the mailbox for the subscriber.

CSCdx14565

Resynchronizing message waiting indicators (MWIs) for all subscribers causes errors from the Notifier component to appear in the Event log. The errors state, "No suitable port."

The problem occurs in Cisco Unity version 3.x for DTMF integrations with circuit-switched phone systems when MWIs are resynchronized, either initiated according to the schedule set up in Cisco Unity or initiated manually in the Cisco Unity Administrator.

Workaround

In the Cisco Unity Administrator, setting more voice messaging ports to Dialout MWI may decrease the number of errors that appear in the Event log.

CSCdx15372

In a dual-phone system environment on a Cisco Unity 2.x or 3.x system, Cisco Unity administrators are not prompted to restart Cisco Unity when changing the port assignments on the System > Ports page in the Cisco Unity Administrator. Administrators should be prompted to restart the system after making changes because changing the port assignments without restarting could result in integration failures or delays.

Workaround

Restart Cisco Unity anytime a change is made to the port assignments on the Ports page.

CSCdx18736

Holiday settings play the closed greeting rather than a holiday greeting.

Workaround

Go into call handlers and manually change the closed greeting to reflect the special holiday message instead of the usual closed message.

CSCdx24379

The Message Notification and Private Lists pages in the ActiveAssistant are unavailable to subscribers who are associated with a class of service (COS) that allows access to other subscriber pages in the Cisco Unity Administrator for the purpose of unlocking subscriber accounts or changing subscriber passwords.

Workaround

Set up notification options and private lists for the subscribers by using the Cisco Unity Administrator, or assign the Default Subscriber COS to the subscribers.

CSCdx25672

Subscribers are not able to change the call transfer and screening options in the ActiveAssistant, even if the class of service (COS) that they are assigned allows them to do so. Administrators could also not adjust the call transfer and screening options for such subscribers in the Cisco Unity Administrator. This occurs with Cisco Unity version 3.1(1) and later.

There is no workaround.

CSCdx29139

When Cisco Unity failover is installed, the MWI for a subscriber is turned on even though there are no messages for that subscriber. After resynchronizing the MWI for the subscriber by using the Cisco Unity Administrator, the following warning appears in the Event log:

Event Type: Warning
Event Source: AvExchangeMonitor_MC
Event Category: Run
Event ID: 1006
Date: 4/10/2002
Time: 4:56:43 PM
User: N/A
Computer: NA2U2
Description: Received message event for user that is not monitored.

The behavior can occur after the following sequence of events:

1. The mailbox for the subscriber is moved to a different server.

2. Failover occurs.

3. The secondary server becomes active.

Workaround

Wait for the primary server to become active, and restart the secondary server.

CSCdx35975

Cannot access the Cisco Unity Administrator. The following error appears: "Access denied. Your browser must have cookies enabled to access the Cisco Unity web pages."

The event occurs for one of two reasons:

Cookies are not enabled per session in the Intranet security options.

You are using either Internet Explorer 5.5 or 6.0 with the Q313675 patch and have a non-DNS character in the name of the Cisco Unity server, such as an underscore (_) or exclamation mark (!).

Workarounds

Do one of the following:

Rebuild the system with non-DNS characters in the server name.

Use an Internet Explorer browser that does not have the Q313675 patch. Note that this may only be a short-term solution because all service packs for Internet Explorer will eventually have this fix.

Use the IP address to browse to the system if the server name has non-DNS characters. Note that you may run into caveat CSCdw55925 if you use the IP address.

CSCdx44689

When ports on the primary Cisco Unity server are in a locked state, they do not successfully unregister, even though failover has occurred. This problem can occur on Cisco Unity version 3.1 and later systems with enhanced failover, and is most often seen on systems using the Cisco Unity-CM TSP to connect to Cisco CallManager. A port in a locked state, when viewed using the Status Monitor, appear s to be processing a call for several hours or longer, even though no calls are actually taking place on the port.

Workaround

Stop the primary Cisco Unity server. This will clear the locked ports condition and the ports will fail over properly to the backup server.

CSCdx46888

When a subscriber is deleted, Cisco Unity does not check to see if the subscriber is an owner, message recipient, or member (as applicable) of other Cisco Unity entities, such as call handlers and public distribution lists.

Related to caveat CSCdx46851.

Workaround

Before deleting a subscriber, assign a valid subscriber to the applicable Cisco Unity entities to replace the subscriber you plan to delete.

CSCdx48779

Installation of Microsoft SQL Desktop Edition (MSDE) Service Pack 1 fails with one of the following errors:

When running SQL2000_SL1\MSDE\Setup.exe /p SQLRUN1, the /p switch is not recognized.

When installing SQL Server 2000 Service Pack 1 Desktop Engine from the CD-ROM drive, Error 1706 appears.

Workaround

Install the latest qualified SQL Server 2000 service pack.

CSCdx52339

After Cisco Unity unexpectedly stops, starting Cisco Unity again results in a blue-screen error.

Workaround

Restart the server before trying to start Cisco Unity again.

CSCdx61880

Dialogic ports lock up and the call to acmStreamClose fails with error(5) when an external caller dials in to leave or retrieve a message. This behavior occurs in an environment where prompts and greetings are recorded in the G.711 format, and the message is recorded in the G.729a format. The error in the Event log is an AvMiu_MC error indicating a failure in AvWav. The Dialogic ports stop answering calls, and Cisco Unity does not answer.

Workaround

Running in a pure G.711 environment does not produce these problems.

CSCdx62296

With a large number of voice messaging ports (for example, 64 to 72 ports), Cisco Unity may experience AvMiu errors that indicate an error in UnityAvWav where the Beginthreadex command fails. The error occurs primarily in all G.711 systems (refer to CSCdu67587, in Bug Toolkit). If the system transcodes between G.711 and G.729a, Cisco Unity may experience errors in the conversations indicating missing files, which lead to errors indicating that some processes are out of memory. Systems with 48 or fewer voice messaging ports do not exhibit these errors.

Workaround

Do one of the following:

If the system transcodes between G.711 and G.729a, turn off transcoding, and restore the system to an all-G.711 region or to an all-G.729a region.

Reduce the number of voice messaging ports to 48 ports or fewer.

Systems that use transcoding with 48 voice messaging ports or fewer must have the critical section workaround enabled. It is enabled by default for Cisco Unity 3.1(4). For Cisco Unity releases earlier than 3.1(4), refer to the workaround section of the release-note enclosure for CSCae08069, in Bug Toolkit.

CSCdx62431

When starting Microsoft Outlook XP with ViewMail loaded, subscribers intermittently get the following error: "Outlook experienced a serious error the last time the add-in c:\program files\viewmail\tfxext32.dll was opened. Would you like to disable this add-in?"

There is no workaround.

CSCdx65193

After successfully running the failover configuration wizard on both the primary and secondary servers, SQL replication is not configured.

There is no workaround.

CSCdx67490

When the Voice Connector for Exchange 2000 attempts to send a message to a subscriber whose primary e-mail address alias in Active Directory matches the primary e-mail address alias of another account (not necessarily another Cisco Unity subscriber), the Voice Connector crashes. This happens in Cisco Unity version 3.1(2) and when the Voice Connector for Exchange 2000 is used for AMIS or Bridge networking.

Workaround

If possible, change the e-mail address alias of the subscriber that is receiving the Bridge message to a unique e-mail address alias in Active Directory, and restart the Exchange Voice Connector service.

CSCdx67868

Changes to the Text Pager1 notification device cannot be saved if you change the values for the device, then make more changes. When you click Save the second time, the previous values reappear.

CSCdx67871

In the Cisco Unity Administrator, after editing any subscriber's message notification devices, the "Example Administrator" record is corrupted. The problem has been observed in stand-alone voice messaging configurations of Cisco Unity 3.1(3). It occurs after multiple edits to a subscriber notification device.

There is no workaround.

CSCdx68920

Cisco Unity intermittently crashes with a Dr. Watson error that points to an exception occurring in the AvCSMgr.exe process. The Drwtsn.log points to an exception number: c0000005 (Access violation).

The cause is currently unknown.

CSCdx70947

Cisco Unity installation fails during default configuration.

Workaround

1. Run SQL Server Enterprise Manager.

2. In the left pane, expand Microsoft SQL Servers > SQL Server Group > <Server_name> > Security > Logins.

3. In the right pane, right-click the BUILTIN\Administrators account, and click Properties.

4. Click the Server Roles tab, and confirm that all check boxes except the last, Bulk Insert Administrators, are checked.

5. Repeat Steps 3 and 4 for the NT AUTHORITY\System account.

CSCdx77631

In the Cisco Unity Administrator, when attempting to import an existing Exchange user by entering the wildcard "*" in the Find field on the Find and Select Exchange User to Import page, the search could result in a wait of 20 minutes or more before the new subscriber page appears. The problem occurs when there is a large number of subscribers and a large number of Exchange servers (on the order of 200,000 users and 300+ servers).

Workaround

Do one of the following:

Narrow the search scope by entering at least one letter of the user name or alias followed by "*" in the Find field.

Import Exchange users with the Cisco Unity Import utility.

CSCdx82421

When Cisco Unity failover is set up and failover or failback occurs, two information messages may appear in the Event log indicating that a server has become active several minutes before the server actually becomes active. When the server becomes active, the same two messages appear again in the Event log.

The two messages that appear are:

Event Source: AvDirynch_MC; Event ID: 1077; Description: This Unity server has become the active server and will start monitoring the Exchange 5.5 directory for changes.

Event Source: AvCsNodeMgr_MC; Event ID: 1047; Description: Service AvCsMgr is active.

There is no workaround.

CSCdx83741

When an external caller calls into a call handler and the transfer type is "Release to Switch," if the caller hangs up while Cisco Unity is in the process of transferring the call, the port locks.

The following error appears in the Application event log: "Component Miu: Thread 0x00000CD4 had a Failure on Port 21 in Method CAvMiuLine::Transfer(eMIU_XFER_RELEASE). Description: HardFailure in Wait after lineBlindTransfer."

The problem occurred on a Cisco Unity 3.1.3 serial integration using a Dialogic 240PCI T1 card.

Workaround

Configure all subscribers to use supervised transfer.

Alternatively, if release transfer must be used, restart the Cisco Unity server on a regular basis to recover locked ports. Use the Status Monitor to determine the number of locked ports. A port in a locked state, when viewed using the Status Monitor, appear s to be processing a call for several hours or longer, even though no calls are actually taking place on the port.

CSCdx86232

The Event Notification utility error messages are not useful to customers.

CSCdx87461

The upgrade to Cisco Unity 3.1 fails during migration. The following error appears: "Failed to upgrade Application Data." The Migration.log file also shows that migration failed.

The event occurs when the following registry key value is missing:

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors\
DirSynchAD\1.00\Domains\<DomainName.com>\MailUsers\
Root = {cn=Users,DC=<DomainName>,DC=com}

Workaround

1. Start RegEdit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

2. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

3. Determine if the following key value exists:
HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors\
DirSynchAD\1.00\Domains\<DomainName.com>\MailUsers\
Root = {cn=Users,DC=<DomainName>,DC=com}

If the key value does not exist, copy the value from the following registry key and paste it into the empty registry key.

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors\
DirSynchAD\1.00\Domains\<DomainName.com>\DistributionLists\
Root = {cn=Users,DC=<DomainName>,DC=com}

4. Close the registry.

5. Rerun the Cisco Unity Setup program.

CSCdx89770

After installing McAfee NetShield 4.5 Service Pack 1 on an on-box Exchange Cisco Unity server, TTS (text-to-speech) stops working.

Workaround

Disable NetShield, and restart the Cisco Unity server.

CSCdx94582

The Unity Diagnostic Tool crashes when the Unity diagnostic logs folder contains more than 2,000 files.

Workaround

Stop the service that is filling up the logs folder, and/or periodically delete the log files in the logs folder.

CSCdx95695

Problems with Cisco Unity, in addition to the following error appearing in the application event log:

Event Type: Error
Event Source: AvCs_MC
Event Category: None
Event ID: 100
Description:
Exception occurred and handled in File: ...

Contact Cisco TAC, and ask that the problem be escalated to ECSBU.

CSCdy01230

When Cisco Unity receives an incoming call that is transferred via release (or blind) transfer to the WebAttendant or IVR, the call is dropped. The caller hears nothing (only dead air). The problem does not occur when an incoming call is transferred to an IP phone.

Workaround

Configure Cisco Unity to use supervised transfer.

CSCdy01456

If a subscriber account is locked after the subscriber enters the wrong PIN or password, the Cisco Unity Administrator shows the account as unlocked on the Subscriber > Account page. The problem has been observed on Cisco Unity versions 3.1(1) and 3.1(3).

Workaround

1. In the Cisco Unity Administrator, go to the Subscriber > Account page for the subscriber who has been locked out.

2. Check the Cisco Unity Account Status: Locked check box, and click the Save icon.

3. Uncheck the Cisco Unity Account Status: Locked check box, and click the Save icon.

The subscriber can now log on to Cisco Unity.

CSCdy01857

The Unity Diagnostic Tool default log file size should be 100MB. If diagnostic traces have been enabled without establishing the maximum file size, the log files generated can become too large for efficient file transfer and review.

Workaround

Establish the Maximum file size allowed from the Unity Diagnostic Tool before collecting traces.

CSCdy01893

When diagnostic traces are enabled on Cisco Unity 3.x, errors related to wave operations in the MIU such as "Exception caught in Method WavReadFormatPlay" appear in the Event log.

Workaround

Disable diagnostic tracing.

CSCdy02120

When using the Cisco Unity Administrator to import users, the following error is displayed, "An unrecognized error has occurred. The subscriber has not been added." Despite the error message, however, the subscriber is actually partially added, and even shows up in a subscriber search in the Cisco Unity Administrator, though you cannot browse to the subscriber page.

Workaround

Confirm that the Cisco Unity service account has sufficient permissions to import a user.

CSCdy03292

The Cisco Unity Voice Connector for Exchange 2000 service stops unexpectedly.

The behavior has been seen when using the Voice Connector that ships with Cisco Unity 3.1(4) when processing an extreme number of Cisco Unity Bridge voice messages for multiple Cisco Unity/Bridge bridgehead pairs in a less-than-adequate Exchange resource environment. When the behavior was observed, the Voice Connector was processing SMTP voice messages being sent and received between three separate Cisco Unity bridgehead servers and their associated Bridge servers. The approximate message traffic was greater than 15,000 60-second voice messages per 24 hours. The behavior was observed twice under such conditions. The Exchange 2000 server on which the Voice Connector was installed was also in the role of DCGC, and was the home Exchange server for an on-box Cisco Unity installation and two off-box Cisco Unity servers. The server was a dual-500-MHz CPU with 256 MB RAM; these resources are far below those recommended for such a situation.

Workaround

Restart the Voice Connector service by using the Windows Services Control Panel.

CSCdy04329

A Cisco Unity subscriber can change the List In Phone Directory setting on the Personal Settings page of the ActiveAssistant even when the subscriber does not have the proper class of service privileges to do so.

There is no workaround.

CSCdy09164

Cisco Unity subscribers may occasionally be denied access to their Exchange mailboxes because Cisco Unity does not recognize their passwords.

Workaround

Stop and restart Cisco Unity services.

CSCdy10837

ADSchemaSetup fails and displays the error message: "The role owner attribute could not be read." The ldif.err file displays "Add error on line 37: Busy."

The error has been seen when each domain controller is using Windows 2000 Service Pack 2 and at least one is off line.

Workaround

Confirm that all domain controllers are on line before making the schema updates.

CSCdy11225

The upgrade to Cisco Unity 3.1 fails while old components are being removed. During the upgrade, a dialog box appears that says, "Value is not a valid enumeration." The Tempu.log file also displays the message.

The behavior has been seen when the use of virus-scanning software during an upgrade corrupts the uninstall file.

Workaround

Rename or delete the file CommServer\Setup\CommServer\CommsvrCoreIWF.txt.

CSCdy13016

Depending on whether there are available licenses for mailboxes, Cisco Unity behaves differently when adding Internet subscribers:

When there are mailbox licenses available, Internet subscribers can be added and do not count against the overall license count.

When there are no mailbox licenses available, Internet subscribers cannot be added and the following pop-up box appears: "Couldn't create the object because no more licenses were available."

The behavior occurs regardless of the class of service and subscriber template assigned to the new Internet subscribers.

Workaround

At least one mailbox license needs to be available. If the Example Subscriber still exists within Cisco Unity, that account is safe to delete as it serves no real function and needlessly uses a mailbox license.

CSCdy13810

If the AvCsMgr service stops unexpectedly, you may get a general protection fault when you restart the service.

Workaround

Instead of restarting the service, restart the Cisco Unity server.

You can also set the Recovery options of the AvCsMgr service to launch a file on failure. The file can display a warning telling you to restart the Cisco Unity server.

1. Open the Services MMC panel.

2. Double-click the AvCsMgr service.

3. Click the Recovery tab.

4. In the First Failure list, click Run a File.

5. Enter the location of the file to run.

6. Click OK.

CSCdy16295

The failover configuration wizard does not successfully complete and displays a message that it is unable to remove duplicate objects or is unable to configure SQL replication.

The message does not necessarily indicate what the actual cause of the problem is while deleting duplicate accounts or while configuring SQL replication because there are multiple steps for each task. If any of the steps fail, the same error message appears for each failed step.

Workaround

To determine the actual cause of the problem, examine the entries in the failover configuration log.

CSCdy21304

After you restart the Cisco Unity server, Cisco Unity fails to start. The system event log contains event ID 10005, with the description "DCOM got error `The service did not start due to a logon failure.' attempting to start the service <Service_name> with arguments "-Service" in order to run the server." The problem occurs only when the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services are logging on using a domain account and the account is not explicitly granted the "Log on as a batch job" right.

Workaround

1. Grant the "Log on as a batch job" right to the Windows account that the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services are logging on with.

2. In Services (on the Windows Start menu, click Programs > Administrative Tools > Services), reapply the password used for the account logging on to the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services.

3. In a Command Prompt window, run:

secedit /refreshpolicy user_policy /enforce

4. Start Cisco Unity by right-clicking the tray icon.

CSCdy25862

When installing Cisco Unity, the Cisco Unity Server Configuration wizard fails, displaying a message that it could not start the Cisco Unity services.

The problem is that AvCsGateway does not start and therefore cannot start the AvMsgStoreMonitorSvr service.

Workaround

Restart the Cisco Unity server.

CSCdy27769

ADSchemaSetup fails with the error "Setup failed to query the safety interlock."

The problem occurs when the Remote Registry service is disabled.

Workaround

1. Start the Remote Registry service.

2. Rerun ADSchemaUpdate.

3. Disable the Remote Registry service.

CSCdy27775

The Remote Registry service is disabled and the failover configuration wizard is not successful. Specifically, CAvRegistry::OpenRemoteKey fails. The resulting error code from RegConnectRegistry is ERROR_BAD_NETPATH. The name of the service is RemoteRegistry and appears as Remote Registry Service in the SCM.

There is no workaround.

CSCdy28293

Cisco Unity does not recognize new mailbox limits after the appropriate replication has occurred. The problem may occur when Cisco Unity has been configured previously to connect to an Exchange 5.5 server and the USN value for the mail store on the previous Exchange 5.5 server is higher than the USN values of the mail store on the currently connected Exchange 5.5 server. When the condition occurs, the values in the MailStore table in the UnityDB database will not be updated.

Workaround

1. Stop the AvDSEx55 service.

2. Start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

3. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

4. Browse to:
HKEY_LOCAL_MACHINE\Software\Active Voice \DirectoryConnectors\DirSynchEx55.

5. Double-click LastUSN.

6. Enter 0 in the Value Data box.

7. Close Regedit.

8. On the Windows Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.

9. Expand the tree on the left to locate the UnityDB database.

10. Click Tables.

11. Right-click MailboxStore, and click Open Table > Return All Rows.

12. In the ObjectChangedId column, enter 0 for all of the affected mail stores.

13. Close Microsoft SQL Enterprise Manager.

14. Start the AvDSEx55 service.

CSCdy29087

On a Cisco Unity server that uses more than one language, after the server has been restarted several times, the Cisco Unity Administrator does not display the full list of languages that have been installed on the server.

The problem has been observed in Cisco Unity 3.0(4) on an MCS-7835 server, with multiple installed languages.

There is no workaround.

CSCdy29120

Outside-caller messages are not arriving in subscriber mailboxes. Subscriber-to-subscriber messaging may be working fine. The problem has been observed on Cisco Unity with Microsoft Exchange 2000 when one of the Cisco Unity default accounts, Unity_<servername>, does not have an SMTP address.

There is no workaround in Cisco Unity. The issue is indicative of a problem with the Recipient Update Service (RUS) in Exchange. To learn how to properly configure and troubleshoot RUS, consult the Microsoft Knowledge Base.

CSCdy31720

A subscriber is able to record a name, and to record and listen to messages when the system uses the G.729a codec. After making the initial recording of a name, the subscriber cannot listen to it.

When the subscriber logs on to Cisco Unity and presses 4-3-2 on the phone keypad, the conversation plays the prompt "Your recorded name is" but then drops the call. The Event Viewer displays a number of MIU errors.

Workaround

Configure Cisco Unity to use G.711.

CSCdy36517

When subscribers use the phone to check their messages, large delays are experienced in the Cisco Unity conversation. The delays get longer as a user mailbox gets larger.

Usually the delays are only noticeable when the subscriber has a very large mailbox (in excess of a few thousand messages). But the delays vary depending on the configuration, hardware, and network conditions.

Workaround

Decrease the number of messages in the mailbox until the delays are acceptable.

CSCdy36967

SMTP networking between Cisco Unity servers in different directories fails for a variety of reasons, depending on the version of Cisco Unity. The failure means that subscribers on one Cisco Unity server cannot exchange voice messages with subscribers on another Cisco Unity server that accesses a different directory.

This problem exists in:

All versions of Cisco Unity 3.0 and later in which either the sending or receiving Cisco Unity server uses Exchange 2000.

Cisco Unity version 3.1(5) in which both the sending and receiving Cisco Unity servers use Exchange 5.5.

This problem does not exist in Cisco Unity versions 2.4(6) through 3.1(4) in which both the sending and receiving Cisco Unity servers use Exchange 5.5.

Workarounds

The workaround depends on the version of Cisco Unity installed:

For Cisco Unity 3.1(5)—Install a hot fix for the Cisco Unity Voice Connector on all Exchange servers on which the Voice Connector is installed.

For Cisco Unity 3.1(4)—There are two solutions:

Upgrade to Cisco Unity 3.1(5), and install the hot fix for the Voice Connector.

Install multiple hot fixes designed for Cisco Unity 3.1(4), and install the hot fix for the Voice Connector. The following hot fixes resolve the following defects in 3.1(4):

Unity3.1(4)_Hotfix2 - CSCdx69645

Unity3.1(4)_Hotfix3 - CSCdy02968 (only needed if using Exchange 5.5)

Unity3.1(4)_Hotfix4 - CSCdx90566

Unity3.1(4)_Hotfix5 - CSCdy15617 (only needed if using Exchange 5.5)

For Cisco Unity 3.1(3) and earlier versions that use Exchange 2000—Upgrade to Cisco Unity 3.1(5), and install the hot fix for the Voice Connector.

Contact Cisco TAC for information about obtaining the hot fix that is appropriate for your version of Cisco Unity.

Detailed Problem Description

As of Cisco Unity 3.1(5), extension addresses are not auto-generated for Cisco Unity subscribers. Because the older version of the Voice Connector requires the extension addresses for SMTP Networking, you will need to install the hot fix for the Voice Connector.

In Cisco Unity 3.1(4), the extension addresses are generated when the Voice Connector is installed. When the hot fix for the Voice Connector is installed, to get SMTP Networking to function properly in Cisco Unity 3.1(4), you will also need to install the hot fixes listed above.

Updated instructions for configuring the Cisco Unity server for SMTP Networking are included with the hot fix for the Voice Connector.

CSCdy39650

When Cisco Unity transfers a call from a call handler to a subscriber, it cannot find the subscriber. The Cisco Unity Global Location table was not synchronized with the Active Directory database and with the Cisco Unity Location table. Resynchronizing using the Active Directory monitor and the Global Catalog monitor does not resolve the problem.

Workaround

Check the application event log and DbWalker to see if there are any location-related errors. Copy the LocationObjectID and SystemID from the Location table to the LocationObjectID and SystemID of the Global Location table.

CSCdy41298

In the Cisco Unity Administrator (Subscriber > Messages), you cannot change the after-message action from the default value of "Say goodbye" for anyone except the Example Administrator and the Example Subscriber. When you click Save, the value changes back to "Say goodbye."

CSCdy41441

When a caller presses a valid input key followed by the pound (#) key during a call handler greeting, Cisco Unity does not immediately perform the action that is assigned to the input key. Instead, before performing the action assigned to the input key, Cisco Unity waits the time specified in the Milliseconds to Wait for Additional Digits field on the Call Management > Call Handlers > Caller Input Page in the Cisco Unity Administrator for that call handler (1500 milliseconds is the default).

Workaround

There is no workaround.


Resolved Caveats—Release 3.1(5)

Table 10 Cisco Unity Release 3.1(5) Resolved Caveats 

Caveat Number
Description

CSCae05933

When subscriber data in a CSV file contains spaces after the last or first name is imported into Cisco Unity by using the Cisco Unity Import (AvImport) utility, messages are not delivered, even though the messages are in the UnityMTA directory. In addition, a search for subscribers in the Cisco Unity Administrator may not display all subscribers.

CSCdu26009

Using the directory handler to search for a subscriber whose last name begins with A, B, or C results in the fail-safe conversation when the Example Administrator is listed in the subscriber directory. When the Example Administrator is the first match on the directory handler search, the fail-safe conversation is heard immediately.

CSCdw14656

Imported distribution lists are deleted after approximately five minutes. The behavior occurs in Cisco Unity versions 3.0(2) and 3.0(3).

CSCdw22983

When installing Cisco Unity, the dialog box that displays information about licensed features does not include the setting for failover.

CSCdw41721

New messages from an outside caller are not delivered.

CSCdw58477

After disconnecting Cisco Unity from Exchange 2000 and restarting the Cisco Unity server, you cannot run the Cisco Unity Server Configuration wizard to connect with another Exchange server, or Cisco Unity will not start after you reconnect to another Exchange server.

CSCdw73581

Cisco Unity is unresponsive to voice mail calls. Attempts made to access Cisco Unity are met with a fast-busy tone, and the CPU shows the processor running at 98 to 100 percent. AvGaenSvr.exe is using approximately 85 percent of the CPU, with the remaining 15 percent consumed by Services.exe.

CSCdw84233

The minimum location DTMF access ID length defaults to one (1), which may cause Cisco Unity to fail to find location IDs in the range of 1-20 because they conflict with private distribution lists and Cisco Unity assumes that the caller is trying to address a message to a private list rather than to a location ID.

CSCdx00823

When using the Exchange2000 Cisco Unity Import utility, the list of returned users contains all users from the chosen Exchange server, not just those on the server and who also have accounts in the chosen domain. The behavior occurs in a multiple-domain, multiple-Exchange 2000 server environment.

CSCdx03440

After upgrading, a Cisco Unity subscriber cannot log on to the Cisco Unity Administrator or the ActiveAssistant without using a local system administrator account because AvLogMgrSvr.dll is not registered properly.

CSCdx03853

Cisco Unity Internet subscribers hear the fail-safe conversation when leaving a message for other subscribers, and sometimes when performing other tasks over the phone.

CSCdx08769

Attempts to use TRaP in either the Cisco Unity Administrator, ActiveAssistant, ViewMail for Outlook, or the Cisco Unity Visual Messaging Interface (VMI) result in failure. The problem occurs when the last port that is enabled for TRaP is no longer operational.

CSCdx08791

When a subscriber tries to play or record messages by using ViewMail or VMI, or to play or record names and greetings through the ActiveAssistant or the Cisco Unity Administrator, the following message plays: "Unknown problems are preventing the connection to the server."

The behavior occurs when the port that Cisco Unity is trying to use for phone record and playback has gone bad.

CSCdx16901

There is a lengthy pause in the subscriber conversation after the current greeting is played over the phone. The behavior occurs when a subscriber logs on to Cisco Unity, and presses 4-1-1. After Cisco Unity plays the current greeting, there is a four- to five-second pause before the conversation prompts the subscriber to rerecord the greeting, hear other greetings, or choose other greeting options.

Cisco Unity exhibits the behavior on 3.0(x) and 3.1(1) through 3.1(4) systems.

CSCdx23069

The Cisco Unity Administrator does not correctly display all existing Exchange subscribers from a selected domain when you try to create new Cisco Unity subscribers by importing them from Exchange.

CSCdx23845

The Weekdays schedule is the only schedule that can be selected for the Default Schedule field on the System > Configuration > Settings page in the Cisco Unity Administrator. The schedule that is selected for the field is used for all Cisco Unity operations unless specifically changed for a call handler, subscriber account, or call routing table.

CSCdx27600

Win32 calls in the AvWav do not log extended error information when the information is available.

CSCdx31427

If the account that owned SQL Server services did not have the right to write to the registry, then when you tried to add a subscriber, Cisco Unity logged an exception in the event log, and the DTMF name was not generated. Cisco Unity now logs an error instead of an exception in the event log. The error description recommends that you check the rights on that account.

CSCdx31530

The Failedloginsa table grows large enough to crash a Cisco Unity server.

CSCdx33245

System administrators have deleted default database items, not realizing the adverse effect on Cisco Unity.

Added "Do not delete" to the default opening greeting, operator, and goodbye call handlers, the example administrator and the example subscriber.

CSCdx35168

On a Cisco-provided small-scale Cisco Unity server such as the MCS-7835, there is only 4 GB of space on the C drive. After completing the Windows 2000 setup, only 700 MB of free space remains on the C drive. Installing Cisco Unity and other software on the C drive can cause problems by filling up the drive.

To implement the fix

Install everything but the OS and page file on another partition (for example, D or E). The software to install on the other partition includes:

Cisco Unity, trace logs, and Unity Messaging Repository (UMR).

Exchange and logs.

SQL and logs.

The workaround applies to small-scale systems using a monolithic disk or single RAID-1 configuration, as well as to medium- and large-scale servers.

For more information, refer to White Paper: Physical Storage Best Practices for Cisco Unity with Microsoft Exchange, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/storage.htm.

CSCdx36760

Attempting to run the Cisco Unity server with an Intel Dialogic board in PCI bus number 16 or higher fails with the error message: "Error starting service."

The following warnings appear in the event log:

StartDev.exe: Error: Failed to start device dxxx B1 with error 1F
StartDrv.exe -LstartDrv.log returned fatal error. Dialogic system service stopping.
StopDev.exe: Error: failed to stop the device: dxxx B1 with error e000000c
CTBBAPI.exe 01.50 bld 3(release) 0x20000000: CTBB_Error_Success: Function completed properly.
Exit value 0x0
StopDev.exe -LstopDev.log returned fatal error- ignoring Dialogic System Service stopped.
The Dialogic System service terminated with service specific error 16383.

CSCdx41200

When attempting to import subscribers by using the Cisco Unity Administrator, you get the error: "An unrecognized error has occurred. The new subscriber was not successfully added." However, you can add new subscribers by using the Cisco Unity Administrator. There are no error messages recorded in the event logs for the error.

CSCdx44295

If the Cisco Unity server name is changed after SQL Server 2000 or MSDE 2000 is installed and before the Cisco Unity Server Configuration wizard is run, Cisco Unity does not start.

To implement the fix

The following steps must be performed in SQL after the server name has been changed.

1. Open query analyzer, and run the following commands:
sp_dropserver `<oldservername>'
GO

sp_addserver `<newservername>', `local'

2. Stop and start the SQL services. Once it restarts, use query analyzer and enter:
SELECT @@SERVERNAME

Confirm that is the new server name.

CSCdx46167

The greeting for a call handler does not play, and in the Cisco Unity Administrator on the Call Handlers > Greetings page, the Play button on the Media Master control is grayed out.

When a new call handler is created that is based on an existing call handler, changing the standard greeting on the new one deletes the standard greeting on the original. The problem happens when the original call handler has a recorded name or an alternate greeting already recorded.

CSCdx46333

Subscribers who are associated with a class of service that allows access to other subscriber pages in the Cisco Unity Administrator for the purpose of unlocking subscriber accounts or changing subscriber passwords can also change other settings, such as those on the Network > Primary Locations > Profile page.

CSCdx48691

If phone systems are numbered incorrectly (because Cisco Unity has been reconfigured from a dual phone system integration to a single phone system integration), MWIs are not activated, and several errors appear in the event log.

CSCdx53816

MWIs are not activated when the phone system has variable-length extensions in a serial (SMDI) integration with Cisco Unity.

CSCdx56923

Subscribers cannot listen to some messages over the phone, even though the messages are included in the message count. For example, when the behavior occurs, a subscriber hears: "You have one new message. New messages. End of new messages. You still have one new message."

CSCdx58407

The called-party extension (forwarding extension) may be padded with one or more zeros whenever the extension contains fewer digits than the configured default extension length. In this case, Cisco Unity will not route the call to the correct call handler.

CSCdx58453

In SMDI or serial integrations, Cisco Unity receives a caller ID for external calls with one or more additional zeros on the left side of the number. Cisco Unity then attempts to process the number with the zeros.

CSCdx61671

Diagnostic logs were exceeding the value assigned to the registry key HKLM\Software\ActiveVoice\AvLogMgr\1.0\Diagnostic Megabytes Saved. (The default setting is 400 MB. The value can be changed in the Advanced Settings tool in Tools Depot.) The setting applies only to diagnostic logs, not to other files stored in CommServer\Logs (for example, data files, SqlSync logs, or osqldump logs).

CSCdx62964

The Unity Message Repository (UMR) fails to send messages.

CSCdx63261

In the Cisco Unity Administrator, a run-time error is displayed when you try to add new subscribers.

CSCdx63632

In the Cisco Unity Administrator, when you select a delivery location from the Find dialog box, the location that you selected is not the one that is displayed.

CSCdx68377

Access violation in AvCsMgr is caused by CAvMiu::UseNewTtsMgr.

CSCdx68421

When installing Cisco Unity as a member server in a Windows 2000 child domain using a Domain Admin account in the child domain, the installation fails with the error: "The account does not have full control on CiscoECSBUUMLocationObjectID."

CSCdx69645

When subscribers use the phone to blind address messages by using SMTP Networking to remote subscribers, the messages are not delivered.

To implement the fix

Although this caveat is resolved in 3.1(5), a hot fix for the Voice Connector is also required. Contact Cisco TAC for more information.

CSCdx71538

The CPU usage on the Cisco Unity server shows 80% even though the Cisco Unity system is not under load. When the CPU begins to hover around 80%, error messages are logged in the Application event log because messages are stuck in the UnityMTA folder and are not being delivered.

CSCdx75263

When the secondary server was installed, a different Exchange server was specified than was specified on the primary server. After running the failover configuration wizard on the secondary server, Cisco Unity will not start and the Application log displays several errors.

CSCdx76289

During the Cisco Unity Server Configuration wizard, clicking Back to select a different Exchange server does not work.

CSCdx78152

When subscribers press 4 during message playback to slow down a message that was recorded on a phone using the G729a codec, Cisco Unity stops message playback prematurely. Related to caveat CSCdy15708.

CSCdx78628

For integrations that use Dialogic voice cards, recording or playing back WAV files that are saved with a low-bandwidth codec (for example, GSM or G.729a), voice messaging ports may lock up. Port 1 is most frequently affected, but other ports may also be affected. When a port locks up, other ports continue to function normally.

CSCdx81348

In the Cisco Unity Administrator on the Subscriber > Alternate Extensions page, the following ASP script error is displayed when trying to save the record: "Type Mismatch: `UBound.' AddAltExtBody.asp not found." The record is not saved.

CSCdx81862

When existing Active Directory users are imported from a CSV file into Cisco Unity by using the Cisco Unity Import (AvImport) utility, their Windows NT passwords are reset unless the CSV file contains the column header UPDATE_SUBSCRIBER_ACCOUNT, and the value for each applicable user is set to 1.

CSCdx82377

When Exchange access fails because of a network outage or some other reason, Cisco Unity stores new messages on the Cisco Unity server in the UnityMTA folder. After access to Exchange is restored, the messages will be delivered to the appropriate mailboxes. However, subscribers may receive messages in the reverse order from how they were sent.

CSCdx84857

Importing from a CSV file into Cisco Unity with Exchange  2000 by using the Cisco Unity Import (AvImport) utility fails when the CSV file contains mailbox data from a server in a different domain than Cisco Unity.

CSCdx85834

On a Cisco Unity server that has been configured as an AMIS bridgehead server, Cisco Unity may stop answering calls. This happens when the Cisco Unity server is assigned to a Dialing Domain and in the Cisco Unity Administrator, the Subscriber Search / Limit Searches To setting is set to Dialing Domain on the Primary Location Addressing Options page.

CSCdx89357

After running the failover configuration wizard on the secondary server, the Cisco Unity services on the secondary sever that run on the Unity_<Cisco Unity server name> account no longer start.

CSCdx89372

When failover is set up, file replication between the primary and secondary servers fails. The behavior occurs when the account used for running the failover configuration wizard on the secondary server is different from the account used for running the wizard on the primary server.

CSCdx90566

Subscribers cannot reply (by using the phone) to messages from other subscribers who are located in a separate directory.

To implement the fix

Although this caveat is resolved in 3.1(5), a hot fix for the Voice Connector is also required. Contact Cisco TAC for more information.

CSCdx91125

Subscribers cannot exit the Change Address menu in the Cisco Unity conversation by pressing * after a non-delivery receipt (NDR) message is received for a message sent to a Cisco Unity Bridge node, and the subscriber has pressed 2 to change addressing for the NDR message.

CSCdx91352

In the Cisco Unity Administrator, run-time errors are displayed when you try to access any subscriber record. The page displays, but all the fields are blank.

CSCdx92346

When running the Cisco Unity Setup program, a message appears saying "Setup was unable to configure default settings on your system. You may continue the setup process and configure the system manually. Do you want to continue?" The error message is not logged to the Tempu.log file. When you click Cancel or Continue, either "User canceled" or "User elected to continue" appears in the log file.

CSCdx93837

The Unity Message Repository (UMR) fails to deliver messages to Exchange. Additionally, 1,000 or more log files are written to the directory in which Cisco Unity diagnostic logs are kept (the default is CommServer\Logs) in less than an hour, consuming hard disk space.

CSCdy01002

Alternate extensions are not written to the Active Directory when using the Alternate Extension tool.

CSCdy02968

VOICE addresses for Internet Subscribers are not saved correctly in Exchange 5.5.

To implement the fix

Although this caveat is resolved in 3.1(5), a hot fix for the is also Voice Connector is also required. Contact Cisco TAC for more information.

CSCdy03223

When failover is set up and both Cisco Unity servers are restarted at exactly the same time, the Failover Monitor on the primary server indicates that the primary server is inactive but continues to take calls. As a result, MWIs may be out of sync, and message notifications may not work properly.

CSCdy03758

When a subscriber who has a full mailbox calls another Cisco Unity subscriber and leaves a message, Cisco Unity fails to deliver the message and does not inform the subscriber with the full mailbox that the message was never delivered.

CSCdy12012

In the Cisco Unity Administrator, when you try to create a subscriber by importing an Exchange user, the Cisco Unity Administrator displays errors and fails to create the subscriber account. The problem occurs when the Cisco Unity server is in a sub-domain in a multi-domain parent/child configuration.

CSCdy13526

In the Cisco Unity Administrator, when the Lock This Key To The Action check box is checked and the action for the key is set to Ignore on the Call Management > Call Handlers > Caller Input Page, Cisco Unity ignores more than just one of the keys that a caller presses. For example, if the 0 key is locked and set to ignore, and the caller dials extension 7001, Cisco Unity incorrectly tries to route the call to extension 71.

CSCdy15617

When a subscriber listens to a message from a "VOICE" Internet subscriber, the Cisco Unity conversation is unable identify the message as being from another subscriber and cannot play the Internet subscriber's recorded name. ("VOICE" Internet subscribers are Internet subscriber accounts on the local server that correspond to subscribers on a remote Cisco Unity server. They have addresses in the format VOICE:<Delivery Location ID>_<Extension>.)

To implement the fix

Although this caveat is resolved in 3.1(5), a hot fix for the Voice Connector is also required. Contact Cisco TAC for more information.

CSCdy15708

When subscribers press 4 during message playback to slow down a message that was recorded on a phone using the G729a codec, Cisco Unity stops message playback prematurely. Related to caveat CSCdx78152.

CSCdy18162

Dialogic ports lock up, and the waveInStart function fails with an error.

CSCdy20353

Cisco Unity may produce a fatal exception when synchronizing its database with the directory if the database contains more than approximately 5,000 subscribers. This occurs when using the database import tool for upgrading from pre-3.0 Cisco Unity to Cisco Unity 3.x or higher. It also occurs when using the Disaster Recovery Tools (DiRT) to restore a back up.

CSCdy26265

When the ADSchemaSetup program fails, it does not generate log files that help determine what caused the failure.

CSCdy29279

When troubleshooting MWI issues, the Exchange Monitor diagnostics (in particular Mapi Notification 13) are used to see if Cisco Unity is getting MAPI notifications for the user mailbox in question. It is very difficult on a busy system to tell which subscriber the Table add, delete, or modify records are for because the diagnostics do not show the user name or alias associated with the event.

CSCdy31156

When upgrading from 3.0, the second part of the Cisco Unity setup program fails, displaying the error message: "Failed reading Registry value: HKEY_LOCAL_MACHINE\Software\Active Voice\Commserver\1.0\PrimaryServer"

CSCdy31263

During message playback via the G.729a codec, pressing the 4 key on the phone keypad to slow down the message takes the user back to the beginning of the message rather than slowing playback.

Pressing 4 a second time takes the user to the end of the message (to the prompt that plays after listening to the message).

CSCdy35994

Cisco Unity is in a parent/child domain environment. Cisco Unity was originally connected to an Exchange 5.5 server. Subsequently, the Exchange 5.5 connector was removed, and the Exchange 2000 connector was installed. Because Exchange 5.5 and Exchange 2000 were in the environment, the Active Directory Connector was also installed. However, users that were created in Exchange 5.5 cannot get replicated into Exchange 2000. This causes DirSynchAD errors to be logged in the Application Event log.


Resolved Caveats—Release 3.1(4)

Table 11 Cisco Unity Release 3.1(4) Resolved Caveats 

Caveat Number
Description

CSCdu60397

Subscriber licenses are incremented when an AMIS, Bridge, or Internet subscriber is added to the system (any subscriber that has no assigned mail store).

CSCdu67278

Unable to import hidden users or distribution lists on systems with Exchange 2000.

The new registry setting HKEY_LOCAL_MACHINE\Active Voice\Directory Connectors\DirSynchGlobalCatalog\1.00\ Import Directory Connector\Show Hidden Objects was added. It is a DWORD value:

1 - Include users that are hidden from address lists in results

0 - Do not include users that are hidden from address lists in results

 

CSCdw47452

When an active secondary server fails, neither the primary nor the secondary server takes calls for approximately 10 minutes.

CSCdw72186

A Cisco Unity administrator whose Windows account is associated with multiple Cisco Unity accounts is unable to access the Status Monitor page. The Cisco Unity Administrator page is opened instead.

CSCdw73149

Sometimes during installations or upgrades, the Cisco Unity Setup program simply "disappears" as it is copying files.

CSCdw79848

Message notifications are done by the default system profile, even though a new system profile is used with a one-way CA in ADC. The problem occurs in Cisco Unity versions 3.1(2) and 3.1(3) using Exchange 2000.

To implement the fix (Exchange 2000 system only)

Run Cisco Unity Configuration Setup with the -sysmbx option, and select the account mailbox to use as the system mailbox. All outside caller messages and message notifications will be from the mailbox. Running the -sysmbx option sets the values of the following registry keys:

HKEY_LOCAL_MACHINE\Software\Active Voice\Doh\1.00\ SystemMailboxAlias

HKEY_LOCAL_MACHINE\Software\Active Voice\Doh\1.00\ SystemMailboxDisplayName

HKEY_LOCAL_MACHINE\Software\Active Voice\Doh\1.00\ SystemMailboxDomain

CSCdw88890

Cisco Unity ports lock up, and Cisco Unity stops answering calls or drops calls when a subscriber uses the speed-control keys in an environment with IP phones and the G.729a codec.

CSCdw89600

In some Cisco Unity installations in which computers and subscribers have the same alias, changes made to those subscriber accounts in Active Directory are not replicated to the SQL database on the Cisco Unity server. Affected subscribers are not addressable using the phone and cannot access the ActiveAssistant.

CSCdw94571

Windows Terminal Services can be used to access the Cisco Unity server with some limitations. For more information, see the "Windows Terminal Services" section.

CSCdx03853

Cisco Unity Internet subscribers hear the fail-safe conversation when leaving a message for other subscribers, and sometimes when performing other tasks over the phone.

CSCdx05971

For a few minutes after creating a new subscriber account, all messages left by callers to the new subscriber are not delivered.

CSCdx07551

When you install Cisco Unity on a member server in a Windows 2000 child domain by using the administrator account of the child domain, the Cisco Unity Server Configuration wizard displays an error after you select the containers where users and groups will be created. The error indicates that the account does not have permission to list contents on user objects.

CSCdx10738

CSCdx10749

Recordings and outside caller messages are deleted on a failover system.

CSCdx12769

File replication for failover stops, and the files that should be replicated are on only one server.

CSCdx12829

MWIs are not synchronized: Cisco Unity indicates that certain MWIs are off while the Avaya Definity phone system indicates the same MWIs are on.

CSCdx13512

Cisco Unity does not recognize extensions of newly added call handlers.

CSCdx15190

A user attempts to access the Cisco Unity Administrator, and the browser displays an error message stating that the account is not associated with a subscriber.

CSCdx15569

A port locks and error messages in the event log start with:

"Component Miu: Thread 0x000009F0 had a Failure on Port 5 in AvWav"

CSCdx16643

An auto-created Cisco Unity remote Bridge subscriber has no extension.

CSCdx18244

Callers hear static in greetings.

CSCdx19454

After Cisco Unity failover is installed, some directory changes are not visible in Cisco Unity.

CSCdx20173

Default objects such as the Example Administrator and Example Subscriber are deleted from the Cisco Unity database and must be restored.

Do the following three procedures in the order listed to restore the default objects.

To run the SQL script that recreates the objects

From the command line or using SQL Query Analyzer, run: C:\commserver\localize\defaultconfiguration\enu\FixDefaultObjects.sql

Note The script makes an SQL backup of the Cisco Unity database before modifying it.

To reassociate the objects

1. From Windows or from the command line, run C:\commserver\configmgr.exe.

2. From the Configuration Manager, run Configure Database Schema.


Caution Do not run Run Database Schema Script, or the entire database will be deleted.

3. From the Configuration Manager, run Run Rules Configuration Script.

4. From the Configuration Manager, run Configure Default Location.

5. From Windows or from the command line, run C:\commserver\configurationsetup\setup.exe /sync.

6. Restart the Cisco Unity server.

To fix database errors and orphaned call handlers

When Cisco Unity appears, run C:\commserver\utilities\dbwalker\dbwalker.exe from Windows or from the command line.

Note You can use the Bulk Edit utility to fix bulk errors.

CSCdx21052

An Avaya intercept tone is recorded in messages when a caller hangs up before Cisco Unity has responded to an incoming call.

CSCdx22342

In messaging environments with both Exchange 5.5 and Exchange 2000, the default public distribution lists are sometimes created in the wrong Exchange site. This problem can happen when there are multiple Cisco Unity servers installed into different Exchange sites.

CSCdx24775

The Event log in a failover system has a large number of arbiter errors saying "[Thread 0x84C] Request for a new call failed, hr=[0x8004005]."

CSCdx27422

When Cisco Unity failover is installed, recordings are deleted from the primary and secondary servers.

CSCdx27796

Cisco CallManager failure can cause a port to lock.

CSCdx27961

When attempting to start the Global Subscriber Manager tool on a Cisco Unity system other than version 3.1(2), a message states that the Cisco Unity version is earlier than 3.1(2), although the version is actually later than 3.1(2).

CSCdx28492

After an upgrade to version 3.1.3, Cisco Unity does not start if there is a routing rule that has a condition that uses more than 64 bytes of space in SQL. The error message "Failed activating the [ROUTING] domain in the Ruler" appears in the Event log, followed by an error message stating that the Arbiter failed to initialize.

CSCdx32493

Cisco Unity fails to send messages after restarting the primary server in a failover system.

CSCdx35910

Two Cisco Unity attributes remain in Active Directory after a user is removed from Cisco Unity.

CSCdx41866

During recordings, AvAudio inserts silence into the audio stream if it does not get a packet in a timely manner.

Refer to Cisco Unity-CM TSP 6.0(2) Release Notes for information on implementation of the fix. The release notes are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/tsp/tsp602rn.htm.

CSCdx48079

Disable All Traces in the Unity Diagnostic Tool disables all traces, even the default traces that should remain enabled at all times if Macro traces have never been configured.

CSCdx49446

Some files are not copied from one server to another in failover systems if the primary and secondary server disconnect while the files are being copied.

CSCdx49719

In failover systems, when one of the servers is shut down and the other server is rebooted, some services intermittently display an inactive state, and some services whose state is displayed as active don't function.

CSCdx50682

Cisco Unity does not start after running the failover configuration wizard on the secondary server.

CSCdx50694

The failover configuration wizard does not complete successfully on the secondary server.

CSCdx51535

Cisco Unity does not start after a reboot due to an Arbiter initialization failure.

CSCdx53023

When upgrading to Cisco Unity version 3.1(4) or later, if AGCtargetDB=0 prior to the upgrade, the following (default) values will be written to the registry:

AGCMinimumThreshold=45

AGCsampleSize=8000

AGCgainThreshold=5

CSCdx54427

Subscribers and subscriber templates on upgraded Cisco Unity version 3.1(3) systems were missing their VMI notification devices.

CSCdx66025

The Event Notification utility in Tools Depot can not be accessed by using Windows Terminal Services.


Resolved Caveats—Release 3.1(3)

Table 12 Cisco Unity Release 3.1(3) Resolved Caveats 

Caveat Number
Description

CSCdu46604

The All Subscribers report fails to run. This problem occurred on a New Zealand English system, when the report was looking for and failed to find the U.S. English TTS engine.

CSCdu59265

Cisco Unity is unable to create Windows NT accounts, and generates the error message, "An unrecognized error has occurred."

CSCdu82438

Cisco Unity initiates calls to deliver AMIS messages that are queued in the UAmis mailbox after the AMIS schedule changes to Inactive.

CSCdv61625

A subscriber extension remains in the subscriber template and cannot be assigned to another subscriber. The extension-in-use error message appears, even though the extension is not in use by a subscriber.

CSCdv65543

The Exchange 2000 Gateway fails to install with the following error: "Automation error A constraint violation occurred."

CSCdv66725

During the Cisco Unity Server Configuration wizard, the error "The Unity System Profile could not be created" occurs.

CSCdv69341

The web-based Status Monitor has a memory leak.

CSCdv81855

The Cisco Unity 3.1 Setup program hangs while copying MSCAL.OCX.

CSCdw07299

When sending a message, a subscriber cannot be selected by name if the name starts with "u umlaut," "o umlaut," or a circle.

CSCdw13964

Cisco Unity crashes without any errors in the Application log. The AvCsMgr process appears to be running, but Cisco Unity is not taking any calls. The tray icon indicates that Cisco Unity is in the "stopped" state.

This is an SQL problem.

To implement the fix

Follow the instructions in Microsoft Knowledge Base article Q315395, available at www.microsoft.com.

CSCdw22615

Cisco Unity stops answering calls but appears to be running. Opening the System Administrator, Status Monitor, and other Cisco Unity tools do not work. The symptoms are much like CSCdv04296 (SQL Server Deadlock), but without events in the Application Event log. Before applying the workaround, confirm that you are not seeing the defect described in CSCdv04296.

This defect can happen on any version of Cisco Unity that uses TRaP (Telephony Record and Playback). The defect is related to a bug in the Windows 9x RPC layer. This defect affects Cisco Unity because Cisco Unity communicates with the Windows 9x clients during TRaP calls. Windows Me is also affected because it is part of the Windows 9x operating system line.

To implement the fix

Download the fix from Cisco.com at http://www.cisco.com/pcgi-bin/specialaccess.cgi. The access code is VIEKBQFL.

The fix is from Microsoft and is discussed in Microsoft KB article Q315575.

The fix must be applied to every Windows 95, Windows 98, and Windows Me workstation that has ViewMail for Outlook, access to Active Assistant, and/or access to the Cisco Unity Administrator. If the fix is not applied to all workstations, the problem will occur on the Cisco Unity server.

This fix should not be applied to Windows 2000 or Windows XP.

Other workaround

If you are unable to apply the fix from Microsoft, you can disable TRaP access for all subscribers who use Windows 9x as their operating system.

If most of the subscribers use Windows 9x, you can disable TRaP system-wide by doing the following procedure:

1. On the Cisco Unity server, run Dcomcnfg.

2. If any warnings appear, click Yes. (More than one may appear.)

3. On the Default Properties page, uncheck the Enable Distributed COM on This Computer check box.

4. Restart the Cisco Unity server. (Continued)

CSCdw22615
(Continued)

Note Consequences of applying the workaround are:

Subscribers will be unable to use TRaP in ViewMail. Playback and record are still available if there are speakers and a microphone installed.

Subscribers will be unable to play or record in the ActiveAssistant.

Remote viewing of the registry and event log are not possible by using Regedit and Event Viewer. Remote access to Cisco Unity is still possible.

CSCdw22942

RealSpeak TTS sends a stream of unintelligible audio during an e-mail that contains either a subject or a new line that begins with the word "Plants" or "Plant" followed by at least two more words.

CSCdw26918

When recording a message by using the TUI, the recording beep tone stops playing while recording the message.

CSCdw41721

A non-deliverable message blocks delivery of new outside caller messages. The problem occurs when one or more subscriber accounts are missing their mail user records, preventing them from receiving or retrieving messages.

Messages to subscribers without mail user records stay in the Cisco Unity MTA directory and prevent other messages from being delivered. The following error message appears in the Event log: "AvUMR_MC Error UMR Thread Error 101."

The problem exists in Cisco Unity versions 3.0(1) through 3.0(3), and versions 3.1(1) through 3.1(3). Unified messaging subscriber-to-subscriber messages between subscribers on the same Exchange server are delivered.

To implement the fix for Cisco Unity version 3.0(4) or 3.1(3) by adding a registry key to automatically move blocking messages to a specified directory

1. Stop the AvUmrSyncSvr service.

2. Browse to the directory CommServer\UnityMTA.

3. Create a new Failed directory.

4. Start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

5. If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file. (Continued)

CSCdw41721

(Continued)

6. Expand the key

HKEY_LOCAL_MACHINE/Software/Active Voice/UnityUMR/1.0/

7. Add a new String Value, naming it MtaFailedPath.

8. Double-click the key you created in Step 7, and enter the following in the Value data field:

<Drive on which Cisco Unity is installed>:\CommServer\UnityMTA\Failed

9. Click OK.

10. Start the AvUmrSyncSvr service.

11. When a message is moved to the Failed directory, an information message appears in the Application event viewer. Use the information message to repair or recreate accounts for the intended recipients of failed messages.

To prevent the problem from occurring again on a Cisco Unity version 3.0(1) through 3.0(3), 3.1(1), or 3.1(2) system

1. Browse to the directory CommServer\UnityMTA.

2. Move all of the messages in the directory to the directory of your choice, then move the messages back to the UnityMTA directory one at a time. This process allows you to see which messages are able to be delivered and which messages are causing the problem.

3. Remove the undeliverable message(s) from the UnityMTA directory.

4. Determine the affected subscriber(s) in Step 2, and repair or recreate the account(s) on Cisco Unity. Possible causes for this problem include no Exchange mailbox, or a failed import during a 2.4(6) upgrade.

CSCdu71673

Subscribers are prompted to change their password each time they log on to Cisco Unity, even if their password was recently changed.

CSCdv67899

On a new Cisco Unity system, the class of service for the default subscriber is set to add ViewMail for all subscribers. Subscribers cannot be added if the customer did not purchase any ViewMail seats.

CSCdv91084

When attempting to import a subscriber Exchange record that contains quotation marks by using AvImport or Cisco Unity Administrator Import via Exchange, the Cisco Unity Administrator Subscriber Profile fields are not populated.

CSCdw12707

When using an Ericsson serial integration with Unity 3.0(3), all incoming serial packets are invalid packets, even though the phone system has been programmed correctly. The IntegrationMonitor.exe shows outgoing serial packets preceded with =0.

CSCdv15935

If a non-delivery receipt is sent by someone other than the public distribution list owner, then Cisco Unity hangs up on the public distribution list owner when the owner checks voice messages by phone.

CSCdv69328

MWIs do not light on subscriber phones when new messages are left. In addition, on the Subscriber > Subscriber > Messages page in the Cisco Unity Administrator, the Indicator Lamp field is set to false instead of On or Off.

CSCdv23404

ViewMail error message "Unknown problems are preventing connection to the server."

CSCdw29348

When a call handler is set up to play prompts in a language other than English on a system with multiple languages installed, all prompts are played in the language specified on the Call Management > Call Handler > Profile page—except the transfer prompt.

CSCdw41728

An AvCsGateway pointer error causes login errors when accessing the Cisco Unity Administrator and the Status Monitor.

CSCdw42558

Example Administrators are not created in the Active Directory.

CSCdw43067

Cisco Unity Server Configuration wizard fails to install because the domain of the logged-on user was not being passed to the privilege checking routines.

CSCdw51156

UMR diagnostics 12 (MTA Walk Through) and 13 (MTA Errors) do not produce output even when an error occurs.

CSCdw53962

A Syscheck test during Cisco Unity Server Configuration wizard fails to revert to the installer account.

CSCdw60112

Sometimes a subscriber experiences a long pause in the phone conversation when forwarding a message.

CSCdv69128

An AMIS location in the Cisco Unity Administrator can have a blank Delivery phone number or contain illegal characters.

CSCdv73752

When the Exchange 5.5 Organization, Site, or Recipients container names contain a comma, a subscriber search in the Cisco Unity Administrator results in the following error message: "A runtime error has occurred. Do you wish to debug? Line 1055 Error: Expected."

CSCdw18757

The non-local subscriber type in the GlobalSubscriber table was incorrectly left as NULL, causing a variety of global searches to fail.

CSCdw25596

New subscribers are created with an SQL SubscriberType of 0 instead of 1.

CSCdw26807

Adding a subscriber by using the Cisco Unity Administrator Import results in a blank Alias text box when the subscriber alias contains an apostrophe.

CSCdw28876

Messages cannot be recorded via TRaP by non-administrators if an administrator installs ViewMail but does not start Outlook.

CSCdw38210

To change the text to speech engine from L&H 3000TTS to RealSpeak on a Cisco Unity 2.4(6.x), 3.0(x) or 3.1(x) system, the TTS registry key needs to be deleted.

CSCdw54104

The Failsafe message plays on Cisco Unity systems with Exchange 5.5 when subscribers attempt to listen to their messages when their mailboxes are full.

CSCdw60729

During Cisco Unity Server Configuration wizard, after entering the server name and LDAP port, the following error message is displayed: "NamedProps error, hr=140064. Setup will not continue beyond this point."

CSCdw62269

When the ExchangeMonitor loses the connection to Exchange, and does not reconnect, the AMIS notifier is unable to initiate calls for AMIS delivery.

CSCdw63453

The error message "SQLServer executable file version is lower than current hot fix. Install SQL Server hot fix before installing Cisco Unity" is received during installation of Unity 3.1(x), even though the hot fix and SQL Service Pack 2 have already been installed on the Cisco Unity server.

CSCdw73676

AMIS and Bridge subscribers cannot be added to a private distribution list via the phone conversation.

CSCdw74529

A Cisco Unity 3.0(x) to 3.1(2) upgrade fails to run SQL scripts.

CSCdw77742

Cisco Unity upgrades to 3.1(2) fail on failover systems.

CSCdw85660

Clicking on the ActiveAssistant link from the Cisco Unity Administrator results in a Cisco Unity Administrator session. It does not transition appropriately to an ActiveAssistant session.

CSCdw86425

On Cisco Unity Server Configuration wizard, portions of message text in Japanese are corrupted.

CSCdw87945

When Cisco Unity goes into a failover state, MWIs fail to work for subscribers who were added to the primary server after a Cisco Unity 3.2(x) upgrade.

CSCdw88890

Cisco Unity ports lock up and Cisco Unity stops answering calls or drops calls when a subscriber uses the speed-control keys in an environment with IP phones and the G.729a codec.

The speed-control feature has been disabled in Cisco Unity versions 3.1(2c) and 3.1(3). Customers who experience port lock-ups due to the speed-control feature should upgrade to version 3.1(3) to disable the feature.

A fix is planned for Cisco Unity version 3.1(4) that will make speed control available again.

CSCdw92062

Enabling automatic gain control when the G.729a codec is used for recording may lock a port after a caller leaves a message, or Cisco Unity may drop the call.

CSCdw94866

When upgrading from Cisco Unity 2.4(6) to 3.0(x) or later, sometimes the DBImport utility causes more than one DTMFId row to be created in the SQL database on the Cisco Unity server.

CSCdx05436

Cannot add subscribers after an upgrade from Cisco Unity version 3.0(4) to version 3.1(3) on systems running Windows 2000.


Resolved Caveats—Release 3.1(2c)

Table 13 Cisco Unity Release 3.1(2c) Resolved Caveats 

Caveat Number
Description

CSCae06736

Enhancement request: Allow the display language for Windows Event log messages generated by Cisco Unity to be set in the Cisco Unity Diagnostic Tool.

CSCdu38728

CSCdw61959

In Cisco Unity Import for Exchange 2000, the Exchange server list should contain a list of subscribers from the selected domain who reside on the selected Exchange server.

Note that caveat CSCdx00823, which has very similar symptoms to CSCdu38728 and CSCdw61959, is still open.

CSCdw11833

A buffer overrun causes MIU errors and a port lockup. (Applies to Cisco CallManager integrations only.)

CSCdw37376

In an organization with multiple Exchange 5.5 sites, the AMIS gateway fails to deliver outbound messages to UAmis mailboxes associated with Cisco Unity that are located on another Exchange site.

CSCdw39160

When Failover from Secondary is implemented, scheduled failback cannot be used. Either the primary server must be active when it is running, or the interleaved ports configuration must be used without enabling Failover from Secondary.

To implement the fix

Cisco Unity-CM TSP version 6.0(1) or later is required. (Applies to Cisco CallManager integrations only.)

CSCdw48240

Traces enabled or changed on the Cisco Unity Administrator Tools page are not saved.

CSCdw59379

CSCdw59570

CSCdw85596

CSCdv87611

Administrators should be able to log on to the Cisco Unity Administrator without requiring Local Admin rights on the Cisco Unity server.

CSCdw61404

During failover or failback, subscriber MWIs are not always illuminated and message notifications are not always sent when new messages arrive.

CSCdw68215

Cisco Unity stops responding after sitting idle for one week or longer.

CSCdw88890

Cisco Unity ports lock up and Cisco Unity stops answering calls or drops calls when a subscriber uses the speed-control keys in an environment with IP phones and the G.729a codec.

CSCdw91072

Calls in to the Cisco Unity system may receive the fail-safe message due to Cisco Unity losing connection to the SQL database.

CSCdw91796

The Cisco Unity Diagnostic Tool crashes when attempting to view a log file if a messaging DLL (*_MC.dll) is missing the string associated with logged output.


Resolved Caveats—Release 3.1(2b)

Table 14 Cisco Unity Release 3.1(2b) Resolved Caveats 

Caveat Number
Description

CSCdv73752

When the Exchange 5.5 Organization, Site, or Recipients container names contain a comma, a subscriber search in the Cisco Unity Administrator results in the following error message: "A runtime error has occurred. Do you wish to debug? Line 1055 Error: Expected."

CSCdw60729

During the Cisco Unity Server Configuration wizard, after entering the server name and LDAP port, the following error message is displayed: "NamedProps error, hr=140064. Setup will not continue beyond this point."

CSCdw70697

The Cisco Unity Uninstall utility fails to run because the Subscriberkiller.exe file cannot be located.

CSCdw70707

When running the Bulk Edit utility, run-time error 713 occurs because the Msstdfmt.dll file was not installed.


Resolved Caveats—Release 3.1(2)

Table 15 Cisco Unity Release 3.1(2) Resolved Caveats 

Caveat Number
Description

CSCdu19891

CSCdu26044

CSCdu55971

CSCdu69854

D240PCIT1 Miu initialization fails due to a timeout on opt d41mt.tsp.

CSCdv15935

When a public distribution list owner listens to a non-delivery notification message over the phone, Cisco Unity hangs up if the non-delivery notification message is the result of a message sent by someone other than the owner of the public distribution list.

CSCdv57185

Dr. Watson error occurs in TapiSrv.exe after shutting down Cisco Unity.

CSCdv57693

While trying to install the Sentinel system driver, Windows installer returns failure code1603.

CSCdv66725

During the Cisco Unity Server Configuration wizard, the error "The Cisco Unity System Profile could not be created" appears.

CSCdv67899

On a new Cisco Unity system, the class of service for the default subscriber is set to add ViewMail for all subscribers. Subscribers cannot be added if the customer did not purchase any ViewMail seats.

CSCdv69250

Transfers to a subscriber whose extension has recently changed causes the old number to be rung instead.

CSCdv81868

The Cisco Unity Setup program fails to run configuration scripts 17, 18, and Unitydbex.sql.

CSCdv91084

Import fails with a run-time error if the Find button is clicked when there are quotes around the Exchange user distinguished name.

CSCdv91192

Cisco Unity accounts that have the appropriate class of service rights to administer Cisco Unity but do not have sufficient local administrator rights on the Cisco Unity server are unable to import or add users by using the Cisco Unity Administrator.

CSCdw04836

Changing the * key for caller input causes the Bulk Edit utility to close with the following error message: "Error #445 - Object does not support this action."

CSCdw04875

Setting a call handler to transfer to a message recipient that does not have an extension causes the Bulk Edit utility to close with the following error message: "Error #13 - Type mismatch."

CSCdw04940

The Notifier checks for an AMIS Mailbox when AMIS is not installed.

CSCdw05373

The Bulk Edit utility exits when an invalid entry is encountered for a subscriber, call handler, or interview field.

CSCdw06277

When an alternate extension ID is called directly and the extension is set to forward to Cisco Unity, the opening greeting plays rather than the greeting of the subscriber who owns the alternate extension ID.

CSCdw11118

Cisco Unity accepts messages for AMIS subscribers who do not have an Exchange mailbox.

CSCdw12707

Ericsson integration special control characters at the end of both incoming and outgoing packet definitions are not parsed by the serial integration server.

CSCdw17521

Opening a Cisco Unity Visual Messaging Interface (VMI) session for a subscriber whose name is in Japanese results in the following error message: "Error Writing Output." In addition, the browser displays no content for the page.

CSCdw18464

The Extension Address utility crashes if a subscriber lacks an extension.

CSCdw19807

After failover, calls take too long to get answered by the backup server.

Cisco Unity-Cm TSP 3.1(2) is also required for resolution of this caveat.

CSCdw23147

The Cisco Unity Administrator does not reflect a new AMIS subscriber after an Exchange 5.5 synchronization.

CSCdw21085

Cisco Unity retries AMIS calls when no D tone is received from the destination voice messaging system.

CSCdw22602

AMIS Runtime error occurs on the Subscriber Profile page.

CSCdw24035

Siemens0009 file should have only one flash for ConfirmReturn.


Documentation Updates

Errors

This section lists errors in the current Cisco Unity documentation and gives corrected information. The correct information will be incorporated in a future documentation release, or as otherwise noted.

Automatic Gain Control Setting: Online Help in Advanced Settings Tool

The online Help for AGC Adjust Volume Target Level for New Recordings in the Advanced Settings tool incorrectly describes Automatic Gain Control (AGC) as disabled by default.

AGC is enabled by default in all new installations of Cisco Unity version 3.1(2c) and later, and in upgrades to version 3.1(2c) and later from version 3.0(x) or 2.4(6.x). AGC is off by default only in upgrades to 3.1(2c) and later from version 3.1(1) or 3.1(2).

Recording Phone Calls with Live Record: Cisco Unity System Administration Guide and Cisco Unity User Guide

The Cisco Unity System Administration Guide and the Cisco Unity User Guide indicate that depending on the phone system that your organization uses, subscribers and operators may be able to record a conversation while talking to a caller by using the live record feature. Although this is true, none of the phone systems supported with Cisco Unity version 3.x offer live record. Thus, the feature is not available for use with any Cisco Unity 3.x system.

Setting Up the Secondary Server for Failover: Cisco CallManager 3.x Integration Guide

The procedure "To set up the secondary server for failover" does not correctly describe how to set up the the Forward Busy and Forward No Answer fields for the voice mail ports. Use the following correct procedure.

To set up the secondary server for failover


Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the Cisco Unity Installation Guide.

Step 2 Set up the Cisco CallManager server to integrate with the secondary server as described earlier in this integration guide.

In the Cisco CallManager Administration, a second voice mail server is required to serve the secondary server. This voice mail server must have a different name from the voice mail server that serves the primary server.

Step 3 In Cisco CallManager Administration, click Feature > Voice Mail > Cisco Voice Mail Port.

Step 4 For the last voice mail port that answers calls on the primary server, set the Forward Busy field to the first voice mail port on the primary server.

If there are voice mail ports on the primary server that do not answer calls (for example, voice mail ports set only to Dialout MWI), leave the Forward Busy field blank.

Step 5 For the last voice mail port that answers calls on the primary server, set the Forward No Answer field to the first voice mail port on the secondary server.

If there are voice mail ports on the primary server that do not answer calls (for example, voice mail ports set only to Dialout MWI), set the Forward No Answer field to the first voice mail port on the primary server.

Step 6 In Cisco CallManager Administration, for the last voice mail port that answers calls on the secondary server, set the Forward Busy and Forward No Answer fields to the first voice mail port on the secondary server.

If there are voice mail ports on the secondary server that do not answer calls (for example, voice mail ports set only to Dialout MWI), leave the Forward Busy field blank and set the Forward No Answer field to the first voice mail port on the secondary server.

Step 7 In the Cisco Unity Administrator of the secondary server, enter the settings on the System > Ports page to match the port settings on the primary server.


Uninstalling Failover on a Cisco Unity 3.1 System: Cisco Unity Failover Guide

The instructions for uninstalling Cisco Unity on the secondary server are incorrect in the "Uninstalling Failover on a Cisco Unity 3.1 System" section in Appendix C. For the correct instructions, see the "Uninstalling Cisco Unity on the Secondary Server" section of these release notes.

Changes

This section lists changes to the current Cisco Unity documentation. The changed information will be incorporated in a future documentation release, or as otherwise noted.

Backup and Restore: Cisco Unity System Administration Guide and Cisco Unity Troubleshooting Guide

The instructions for backing up and restoring Cisco Unity in the Cisco Unity System Administration Guide and in the Cisco Unity Troubleshooting Guide apply only to systems running on Exchange 5.5. For systems running on Exchange 2000, refer to Microsoft Backup and Restore recommendations.

Cisco Unity-CM TSP: Cisco Unity Integration Guides for Various Phone Systems

In all integration guides for Cisco Unity version 3.1(1), all references to the AV-Cisco TSP and to the AV-Cisco service provider should be Cisco Unity-CM TSP and Cisco Unity-CM service provider.

Default Diagnostic Traces: Cisco Unity Troubleshooting Guide

The following default diagnostic traces are set for Cisco Unity version 3.1(4) and later, and should be enabled at all times:

FailoverConfig 0, 1, and 10

MiuGeneral 0- 4

SystemConfig 10-12

MiuCall 15

UnityDiagnostics 10

To enable only the default diagnostic traces


Step 1 On the Cisco Unity server desktop, double-click the Tools Depot icon.

Step 2 In the left pane of the Tools Depot window, under Diagnostic Tools, double-click Cisco Unity Diagnostic Tool.

Step 3 In the Cisco Unity Diagnostic Tasks window, click the Disable All Traces icon.

Step 4 In the Disable All Traces window, check the Disable All Traces check box, then click Finish.

The diagnostic traces will be reset to enable only the default traces.

Step 5 Close the Cisco Unity Diagnostic Tool and the Tools Depot windows.


RJ-11 Connector Pinout: Cisco Unity Installation Guide

In the "Intel Dialogic D/41E PCI" section of Appendix A, "Voice Cards," the RJ-11 connector pinout should be:

Pin 1

Unused

Pin 2

Unused

Pin 3

Tip

Pin 4

Ring

Pin 5

Unused

Pin 6

Unused


Set Volume Utility: Cisco Unity Troubleshooting Guide

The instructions for running the Set Volume utility in the Cisco Unity Troubleshooting Guide version 3.1(3) have been updated for version 3.1(3) and later systems. For instructions on running the utility in version 3.1(3) and later systems, see the "Automatic Gain Control Registry Settings Can Be Updated with the Set Volume Utility" section of these release notes.

Omissions

This section lists new and additional information that is not included in the current Cisco Unity documentation. The new and additional information will be incorporated in a future documentation release, or as otherwise noted.

Configuring Failover on the Primary and Secondary Servers: Cisco Unity Failover Guide

The following caution should appear before the procedure "To configure failover on the secondary server" in the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter:


Caution The Cisco Unity services on the secondary server will not start if they use the Unity_<Cisco Unity server name> account set up on the secondary server. To enable the Cisco Unity services on the secondary server to start, use the same domain account or Unity_<Cisco Unity server name> account that the Cisco Unity services use on the primary server.

Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes: Cisco Unity System Administration Guide and Networking in Cisco Unity

Information on moving Cisco Unity Messaging System, UAmis, and UOmni mailboxes was not included in the "Moving Subscriber Mailboxes" section of the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, or detailed in the Networking in Cisco Unity guide. See the "Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes" section for details.

Replacing the Exchange Server: Cisco Unity Installation Guide

The "Replacing the Exchange Server" section has been added to the instructions in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter in the Cisco Unity Installation Guide. For the instructions on replacing the Exchange server, see the "Replacing the Exchange Server" section of these release notes.

Upgrading a Cisco Unity 3.0 or 3.1 System When Failover Is Configured: Cisco Unity Installation Guide

One procedure has been added to the instructions in the "Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter. For the correct and complete instructions, see the "Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured" section of these release notes.

Upgrading from Exchange 5.5 to Exchange 2000: Cisco Unity Installation Guide

A task has been added to the Task List for Upgrading from Exchange 5.5 to Exchange 2000 in the "Upgrading from Exchange 5.5 to Exchange 2000" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide. For the correct and complete instructions, use the following task list:

1. Disconnect Cisco Unity from Exchange 5.5. See the "Disconnecting Cisco Unity from Exchange 5.5" section on page 3-5.

2. Install the NNTP service on the Cisco Unity server. See the "Installing the NNTP Service (Exchange 2000 Only)" section on page 2-36.

3. Upgrade from Exchange 5.5 to Exchange 2000. Refer to the Microsoft website.


Caution Cisco TAC does not provide support for upgrading Exchange 5.5 to Exchange 2000.

4. If you are not installing Exchange on the Cisco Unity server, install Exchange 2000 Administration Software on the server. See the "Installing Exchange Administration Software Only" section on page 2-43.

5. Update the Active Directory schema. See the "Updating the Active Directory Schema (Exchange 2000 Only)" section on page 2-45.

6. Add Exchange permissions to the installation and service accounts:

If all Cisco Unity subscribers will have their mailboxes on Exchange 2000 servers, see the "Exchange Permissions Required If the Organization Contains Only Exchange 2000 Servers" section on page 2-59.

If Cisco Unity subscribers will have their mailboxes on both Exchange 5.5 and Exchange 2000 servers, see the "Exchange Permissions Required If the Organization Contains Both Exchange 2000 and Exchange 5.5 Servers" section on page 2-63.

7. If Cisco Unity subscribers have their mailboxes on both Exchange 5.5 and Exchange 2000 servers, and if the Active Directory Connector uses a one-way connection agreement between Exchange 5.5 and Windows 2000, configure the Cisco Unity system to work with Exchange 5.5 and Exchange 2000. See the "Configuring a System That Includes Exchange 2000 and Exchange 5.5 Servers (Selected Systems Only)" section on page 2-85.

8. Reconnect Cisco Unity. See the "Cisco Unity Server Configuration Wizard" section on page 2-77. Do the procedures for Exchange 2000.

Upgrading from Exchange 5.5 to Exchange 2000 When Failover Is Configured: Cisco Unity Installation Guide

A task has been added to the Task List for Upgrading from Exchange 5.5 to Exchange 2000 When Failover Is Configured in the "Upgrading from Exchange 5.5 to Exchange 2000 When Failover is Configured" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide. For the correct and complete instructions, use the following task list:

1. Disable automatic failover and failback. See the "Disabling Automatic Failover and Failback" section on page 3-7.

2. Disable SQL replication on the primary server. See the "Disabling SQL Replication on the Primary Server" section on page 3-7.

3. Stop and disable the NodeMgr service on the primary server. See the "Stopping and Disabling the NodeMgr Service on the Primary Server" section on page 3-8.

4. Disable McAfee NetShield services on both the primary and secondary servers. See the "Disabling McAfee NetShield Services" section on page 3-18.

5. Disconnect Cisco Unity from Exchange 5.5 on both servers. See the "Disconnecting Cisco Unity from Exchange 5.5" section on page 3-5.

6. Install the NNTP service on both Cisco Unity servers. See the "Installing the NNTP Service (Exchange 2000 Only)" section on page 2-36.

7. Upgrade from Exchange 5.5 to Exchange 2000. Refer to the Microsoft website.


Caution Cisco TAC does not provide support for upgrading Exchange 5.5 to Exchange 2000.

8. Install Exchange 2000 Administration Software on both Cisco Unity servers, See the "Installing Exchange Administration Software Only" section on page 2-43.

9. Update the Active Directory schema. See the "Updating the Active Directory Schema (Exchange 2000 Only)" section on page 2-45.

10. Uninstall Cisco Unity on the secondary server. See the "Uninstalling Cisco Unity on the Secondary Server" section on page 3-8.

11. Add Exchange permissions to the installation and service accounts:

If all Cisco Unity subscribers will have their mailboxes on Exchange 2000 servers, see the "Exchange Permissions Required If the Organization Contains Only Exchange 2000 Servers" section on page 2-59.

If Cisco Unity subscribers will have their mailboxes on both Exchange 5.5 and Exchange 2000 servers, see the "Exchange Permissions Required If the Organization Contains Both Exchange 2000 and Exchange 5.5 Servers" section on page 2-63.

12. Run the Cisco Unity Server Configuration wizard on the primary server. See the "Cisco Unity Server Configuration Wizard" section on page 2-77.

13. Reinstall Cisco Unity on the secondary server. See the "Cisco Unity Setup Program" section on page 2-74.

14. Run the Cisco Unity Server Configuration wizard on the secondary server. See the "Cisco Unity Server Configuration Wizard" section on page 2-77.

15. If Cisco Unity subscribers have their mailboxes on both Exchange 5.5 and Exchange 2000 servers, and if the Active Directory Connector uses a one-way connection agreement between Exchange 5.5 and Windows 2000, configure the system to work with Exchange 5.5 and Exchange 2000. See the "Configuring a System That Includes Exchange 2000 and Exchange 5.5 Servers (Selected Systems Only)" section on page 2-85.

16. Configure failover on the primary server. See the "Configuring Failover on the Primary Server" section on page 3-23.

17. Configure failover on the secondary server. See the "Configuring Failover on the Secondary Server" section on page 3-24.

18. Re-enable McAfee NetShield services on the primary and secondary servers. See the "Re-enabling McAfee NetShield Services" section on page 3-21.

19. Restart both Cisco Unity servers. For more information, see Appendix B, "Exiting and Starting the Cisco Unity Software and Server."

Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes

The Unity Messaging System, UAmis, and UOmni mailboxes are special Exchange mailboxes with specific functions. From time to time, you may need to move the mailboxes to an Exchange server that is faster or has more disk space available, or you may want to move the mailboxes when you add new servers to your Exchange network.

You use the same procedures to move the Unity Messaging System, UAmis, and UOmni mailboxes that you use to move ordinary subscriber mailboxes in Exchange—but with a few extra steps to prevent problems that can occur after the special mailboxes are moved.

To avoid inadvertently moving the Unity Messaging System, UAmis, or UOmni mailboxes when you move a group of subscriber mailboxes, consider changing their Exchange display names so the mailboxes are more clearly identified to you or your site's Exchange administrator as requiring "special" treatment.

The following sections describe the mailboxes and how to move them correctly.

Unity Messaging System Mailbox

When an outside caller leaves a message for a subscriber, Cisco Unity gives the message to Exchange, which routes the message to the subscriber home server (if not the Cisco Unity server) and stores it in the subscriber mailbox. Such messages are identified as coming from the Unity Messaging System mailbox, which is homed on the Exchange server that Cisco Unity gives the message to, and has the display name Unity Messaging System.

For more information on the Unity Messaging System mailbox and its associated Exchange account, refer to the "Default Accounts" section in the "About Subscriber Accounts" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

To move the Unity Messaging System mailbox


Step 1 Use the same procedures that you use for moving ordinary subscriber mailboxes in either Exchange 5.5 or Exchange 2000. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Step 2 Stop and restart the Cisco Unity Messaging Repository (UMR) service (AvUMRSyncSvr) from the Services window in Administrative Tools. (On the Windows Start menu, click Programs > Administrative Tools > Services.) Otherwise, messages from outside callers getting stuck in the UMR after the move.

Once the UMR service has restarted (it may take a few minutes), Cisco Unity exhibits the following behavior:

Messages from outside callers that are addressed to subscribers who do not have full mailboxes are delivered.

As expected, messages from outside callers that are addressed to subscribers who have full mailboxes are not delivered. However, when Cisco Unity attempts to send a nondelivery receipt (NDR), the NDR gets stuck in the Unity Messaging System mailbox, and is never forwarded to the Unidentified Messages distribution list.

Step 3 To release any stuck NDRs from the Unity Messaging System mailbox, stop and restart Cisco Unity by using the system tray icon.


UAmis Mailbox

Outgoing AMIS messages are placed in the special Exchange mailbox that has the display name UAmis_<Servername>.

For more information on the UAmis mailbox, refer to the "About the UAmis Mailbox" section in the "AMIS Networking" chapter of the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

To move the UAmis mailbox


Step 1 Use the same procedures that you use for moving ordinary subscriber mailboxes in either Exchange 5.5 or Exchange 2000. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Step 2 Stop and restart Cisco Unity by using the system tray icon. Otherwise, messages get stuck in the UAmis mailbox after the move.


UOmni Mailbox

Administrative messages from theCisco Unity Bridge to create, modify, or delete Bridge subscribers are placed in the special Exchange mailbox that has the display name UOmni_<Servername>.

For more information on the UOmni mailbox, refer to the "Creating the UOmni Mailbox" section in the "Bridge Networking" chapter of the Networking in Cisco Unity guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/net/index.htm.

To move the UOmni mailbox


Step 1 Use the same procedures that you use for moving ordinary subscriber mailboxes in Exchange 2000. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/sag/index.htm.

Step 2 Immediately stop and restart the Bridge Connector service (CsBridgeConnector) from the Services window in Administrative Tools. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

The Bridge Connector monitors the UOmni mailbox. Restarting it ensures that the Active Directory contacts that are associated with Bridge subscribers are created correctly and messages do not get stuck in the UOmni mailbox after the move. Once you have restarted the Connector, Bridge subscribers can be added, modified, and deleted without any problems.


Replacing the Exchange Server

This section describes the process of connecting Cisco Unity to a different Exchange server from the one selected when the Cisco Unity server was installed. There are three scenarios for which the process is used:

The Exchange 2000 server on a separate computer is being replaced by another Exchange 2000 server on a separate computer.

The Exchange 5.5 server on a separate computer is being replaced by another Exchange 5.5 server on a separate computer.

The Exchange server and Cisco Unity are installed on the same computer, and the message store is being replaced by another Exchange server on a separate computer.

Use one of the following task lists to replace the Exchange server, depending on the system configuration:

Task List for Replacing the Exchange 2000 Server

Task List for Replacing the Exchange 2000 Server When Failover Is Configured

Task List for Replacing the Exchange 5.5 Server

Task List for Replacing the Exchange 5.5 Server When Failover Is Configured

Task List for Replacing Exchange 2000 Installed on the Cisco Unity Server with Exchange 2000 Installed on a Separate Server

Task List for Replacing Exchange 5.5 Installed on the Cisco Unity Server with Exchange 5.5 Installed on a Separate Server

Task List for Replacing the Exchange 2000 Server

Do the following tasks to replace the existing Exchange 2000 server on a separate computer with another Exchange 2000 server on a separate computer.


Note Because the following tasks require that Cisco Unity be stopped, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 2000 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 2000 server to the network.

3. Move the subscriber mailboxes from the original Exchange 2000 server to the replacement Exchange 2000 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. On the Cisco Unity server, exit Cisco Unity.

5. On the Cisco Unity server, run the Cisco Unity Server Configuration wizard and select the replacement Exchange 2000 server as the message store. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. Disconnect the network cable from the original Exchange 2000 server.

7. On the Cisco Unity server, restart the Cisco Unity server.

Task List for Replacing the Exchange 2000 Server When Failover Is Configured

Do the following tasks to replace the existing Exchange 2000 server on a separate computer with another Exchange 2000 server on a separate computer when the Cisco Unity system is configured for failover.


Note Because the following tasks require that Cisco Unity be stopped on both servers, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 2000 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 2000 server to the network.

3. Move the subscriber mailboxes from the original Exchange 2000 server to the replacement Exchange 2000 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. Confirm that the primary server is active and the secondary server is inactive. Refer to the "Determining Which Server Is Active" section in the "Maintaining Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

5. On the primary server, disable automatic failover. Refer to the "Disabling Automatic Failover and Failback" section in the "Maintaining Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. On the primary server, stop the Cisco Unity service AvCsMgr. (On the Windows Start menu, click Programs > Administrative Tools > Services.)

7. On the primary server, run the Cisco Unity Server Configuration wizard and select the replacement Exchange 2000 server as the message store. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

8. Disconnect the network cable from the original Exchange 2000 server.

9. On the primary server, run the failover configuration wizard. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

10. On the primary server, start Cisco Unity.

11. On the secondary server, run the failover configuration wizard. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Task List for Replacing the Exchange 5.5 Server

Do the following tasks to replace the existing Exchange 5.5 server on a separate computer with another Exchange 5.5 server on a separate computer.


Note Because the following tasks require that Cisco Unity be stopped, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 5.5 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 5.5 server to the network.

3. Move the subscriber mailboxes from the original Exchange 5.5 server to the replacement Exchange 5.5 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. On the Cisco Unity server, exit Cisco Unity.

5. On the Cisco Unity server, disconnect Cisco Unity from Exchange 5.5. Refer to the "Disconnecting Cisco Unity from Exchange 5.5" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. On the Cisco Unity server, disconnect the network cable from the original Exchange 5.5 server.

7. On the Cisco Unity server, run the Cisco Unity Server Configuration wizard and point Cisco Unity to the replacement Exchange 5.5 server. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

8. On the Cisco Unity server, restart the Cisco Unity server.

Task List for Replacing the Exchange 5.5 Server When Failover Is Configured

Do the following tasks to replace the existing Exchange 5.5 server on a separate computer with another Exchange 5.5 server on a separate computer when the Cisco Unity system is configured for failover.


Note Because the following tasks require that Cisco Unity be stopped on both servers, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 5.5 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 5.5 server to the network.

3. Move the subscriber mailboxes from the original Exchange 5.5 server to the replacement Exchange 5.5 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. Confirm that the primary server is active and the secondary server is inactive. Refer to the "Determining Which Server Is Active" section in the "Maintaining Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

5. On the primary server, disable automatic failover. Refer to the "Disabling Automatic Failover and Failback" section in the "Maintaining Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. On the primary server, exit Cisco Unity.

7. On the primary server, disconnect Cisco Unity from Exchange 5.5. Refer to the "Disconnecting Cisco Unity from Exchange 5.5" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

8. On the primary server, start Cisco Unity.

9. Disconnect the network cable from the original Exchange 5.5 server.

10. On the primary server, run the Cisco Unity Server Configuration wizard and point Cisco Unity to the replacement Exchange 5.5 server. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

11. On the primary server, run the failover configuration wizard. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

12. On the secondary server, run the failover configuration wizard. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Task List for Replacing Exchange 2000 Installed on the Cisco Unity Server with Exchange 2000 Installed on a Separate Server

Do the following tasks to replace the existing Exchange 2000 server on the same computer with Cisco Unity with another Exchange 2000 server on a separate computer.


Note Because the following tasks require that Cisco Unity be stopped, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 2000 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 2000 server to the network.

3. Move the subscriber mailboxes from the original Exchange 2000 server to the replacement Exchange 2000 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. On the Cisco Unity server, exit Cisco Unity.

5. On the Cisco Unity server, run the Cisco Unity Server Configuration wizard and select the replacement Exchange 2000 server as the message store. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. On the Cisco Unity server, restart the Cisco Unity server.

Task List for Replacing Exchange 5.5 Installed on the Cisco Unity Server with Exchange 5.5 Installed on a Separate Server

Do the following tasks to replace the existing Exchange 5.5 server on the same computer with Cisco Unity with another Exchange 5.5 server on a separate computer.


Note Because the following tasks require that Cisco Unity be stopped, we recommend that you do these tasks after business hours.


1. Install the replacement Exchange 5.5 server. Refer to the Microsoft website.

2. Connect the replacement Exchange 5.5 server to the network.

3. Move the subscriber mailboxes from the original Exchange 5.5 server to the replacement Exchange 5.5 server. Refer to the "Moving Subscriber Mailboxes" section in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

4. On the Cisco Unity server, exit Cisco Unity.

5. On the Cisco Unity server, disconnect Cisco Unity from Exchange 5.5. Refer to the "Disconnecting Cisco Unity from Exchange 5.5" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

6. On the Cisco Unity server, run the Cisco Unity Server Configuration wizard and select the replacement Exchange 5.5 server as the message store. Refer to the "Cisco Unity Server Configuration Wizard" section in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

7. On the Cisco Unity server, restart the Cisco Unity server.

Uninstalling Cisco Unity on the Secondary Server


Note This section replaces the "Uninstalling Cisco Unity on the Secondary Server" section in the "Uninstalling Failover on a Cisco Unity 3.1 System" section in Appendix C of the Cisco Unity Failover Guide.


The uninstall process removes only enough of Cisco Unity so that it can be reinstalled. It does not completely remove all traces of Cisco Unity, so the next time you restart the Cisco Unity server, a message box may appear explaining that at least one service or driver failed during system startup. In addition, the Windows system and application event logs will contain several errors and warnings related to the uninstallation.


Note To remove all traces of Cisco Unity, you must reinstall the operating system.


Do the following five procedures in the order listed.

To install the Cisco Unity Uninstall utility


Step 1 On the secondary server, insert Cisco Unity Disc 1—version 3.1(3) or later—in the CD-ROM drive.

Step 2 Browse to the directory MigrationTools\UninstallUnity.

Step 3 Double-click Setup.exe, and follow the on-screen prompts to install the utility.


To uninstall the Cisco Unity-CM TSP


Refer to the applicable Cisco CallManager integration guide: Do the procedure "To remove the existing TSP" in the "Installing, Configuring, and Testing the TSP" section of the "Cisco CallManager 3.x Integration" chapter. The integration guides are available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/integuid/index.htm.


To uninstall Cisco Unity on the secondary server


Step 1 Log on to the secondary server by using the account that was used to install Cisco Unity.

Step 2 Exit the Cisco Unity software.

Step 3 On the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 4 In the Command Prompt window, enter cd commserver\utilties\uninstallunity3x, and press Enter.

Step 5 Enter unityuninstall3x.exe /skipdoh, and press Enter.


Caution The Cisco Unity Uninstall utility cannot be stopped after it starts, and the uninstall cannot be reversed.

Step 6 Uncheck the Remove Subscriber Information From Mail Users in Directory check box.


Caution If you do not uncheck the check box, Cisco Unity attributes will be removed from Active Directory or the Exchange 5.5 directory for all subscribers associated with this Cisco Unity server and the related primary server. The primary server will no longer be able to take calls because it will not have any subscribers.

Step 7 Click Uninstall.

Step 8 Follow the on-screen prompts.

Step 9 When the utility has finished, you may need to manually delete the directory in which Cisco Unity was installed (the default directory is CommServer).

If you cannot delete the CommServer directory:

a. In the CommServer directory, delete *.exe files.

b. On the Windows Start menu, click Programs > Startup, right-click AvCsTrayStatus, and click Delete.

c. Restart the Cisco Unity server, and delete the CommServer directory.


To delete objects from Active Directory and Exchange 5.5


Step 1 Delete the users created by Cisco Unity by using Active Directory Users and Computers, or in Exchange 5.5 by using the recipient containers (not all users may exist on your system):

Unity Messaging System - <Secondary server display name> or Unity_<Secondary server display name>

Example Administrator - <Secondary server display name>

Example Subscriber - <Secondary server display name>

UAmis_<Secondary server display name>

Step 2 Delete the distribution lists created by Cisco Unity (not all distribution lists may exist on your system):

All Subscribers - <Secondary server display name>

System Event Messages - <Secondary server display name>

Unaddressed Messages - <Secondary server display name>

Unaddressed Faxes - <Secondary server display name>

Step 3 On the Active Directory Users and Computers View menu, confirm that the Advanced Features option is selected.

Step 4 Expand the Unity OU or Unity container, and expand Location.

Step 5 If the location of the secondary Cisco Unity exists, delete it.


To uninstall the Cisco Unity Uninstall utility


Step 1 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.

Step 2 Remove Cisco Unity Uninstall.


Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured


Note This section replaces the "Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured" section in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide.


Task List for Upgrading Cisco Unity Software, or Adding or Changing Licensed Features When Failover Is Configured

Use the following task list to upgrade the Cisco Unity system correctly.

1. Confirm that the secondary server is inactive. See the "Confirming That the Secondary Server Is Inactive" section of these release notes.

2. Disable automatic failover. See the "Disabling Automatic Failover" section of these release notes.

3. If McAfee NetShield is installed, disable NetShield services on the primary server. See the "Disabling McAfee NetShield Services" section on page 3-18 of the Cisco Unity Installation Guide.

4. Run the Cisco Unity Setup program on the primary server. See the "Rerunning the Cisco Unity Setup Program" section on page 3-18 of the Cisco Unity Installation Guide.

5. Upgrade the Cisco Unity-CM TSP on the primary server. See the "Upgrading the Cisco Unity-CM TSP (Cisco CallManager Integrations Only)" section on page 3-21 of the Cisco Unity Installation Guide.

6. Configure failover on the primary server. See the "Configuring Failover on the Primary Server" section of these release notes.

7. If McAfee NetShield is installed, re-enable NetShield services on the primary server. See the "Re-enabling McAfee NetShield Services" section on page 3-21 of the Cisco Unity Installation Guide.

8. If McAfee NetShield is installed, disable NetShield services on the secondary server. See the "Disabling McAfee NetShield Services" section on page 3-18 of the Cisco Unity Installation Guide.

9. Run the Cisco Unity Setup program on the secondary server. See the "Rerunning the Cisco Unity Setup Program" section on page 3-18 of the Cisco Unity Installation Guide.

10. Upgrade the Cisco Unity-CM TSP on the secondary server. See the "Upgrading the Cisco Unity-CM TSP (Cisco CallManager Integrations Only)" section on page 3-21 of the Cisco Unity Installation Guide.

11. Configure failover on the secondary server. See the "Configuring Failover on the Secondary Server" section of these release notes.

12. If McAfee NetShield is installed, re-enable NetShield services on the secondary server. See the "Re-enabling McAfee NetShield Services" section on page 3-21 of the Cisco Unity Installation Guide.

Confirming That the Secondary Server Is Inactive

To confirm that the secondary server is inactive


Step 1 On the secondary Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 In the Services section, determine the value of Local Status, and follow the applicable instruction:

Running: Inactive

The secondary server is inactive. Skip to the procedure "To disable automatic failover" in the "Disabling Automatic Failover" section of these release notes.

Running: Active

Continue with Step 3 to fail back to the primary server.

Any other value

Skip to the procedure "To disable automatic failover" in the "Disabling Automatic Failover" section of these release notes.


Step 3 Click Failback.

Step 4 Click OK to confirm that you want to fail back to the primary server.


Disabling Automatic Failover

To disable automatic failover


Step 1 On the primary server, on the Windows Start menu, click Programs > Cisco Unity > Failover Monitor.

Step 2 Click Advanced.

Step 3 Check the Disable Automatic Failover and Failback check box.


Configuring Failover on the Primary Server

To configure failover on the primary server


Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is C:\CommServer).

Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 3 Click Next.

Step 4 Click Browse, select the name of the secondary server, and click OK. The IP address for the secondary server is filled in automatically.

Step 5 If the system is running Cisco Unity 3.12, skip to Step 6.

If the system is running Cisco Unity 3.13 and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.


Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.


Step 6 Click Next.

Step 7 If you did not create a Cisco Unity failover account, skip to Step 8.

If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.


Caution You must specify the same account on the both the primary and the secondary servers.

Step 8 Enter the password for the account that owns the failover service.

Step 9 Click Next.

Step 10 Click Configure. The wizard verifies settings and configures failover on the primary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.

Step 11 Click Finish.

Step 12 Exit and restart the Cisco Unity software.


Configuring Failover on the Secondary Server

To configure failover on the secondary server


Step 1 In Windows Explorer, browse to the directory where Cisco Unity is installed (the default directory is C:\CommServer).

Step 2 Double-click FailoverConfig.exe to start the Configure Cisco Unity Failover wizard.

Step 3 Click Next.

Step 4 Click Browse, select the name of the primary server, and click OK. The IP address for the primary server is filled in automatically.

Step 5 If the system is running Cisco Unity 3.12, skip to Step 6.

If the system is running Cisco Unity 3.13 and you want the switch file for the selected phone system to replicate during the wizard, check the Copy Switch Files from Primary Server to Secondary Server check box.


Note The switch file is replicated only during the failover configuration wizard. If you select a different phone system after you run the wizard, the new switch file is not replicated to the secondary server. In addition, changes to phone system settings are not replicated between the primary and secondary servers. If you change phone system settings after you run the failover configuration wizard, you must manually change values on both servers.


Step 6 Click Next.

Step 7 If you created a Cisco Unity failover account, click Browse, and double-click the name of the account.

Otherwise, skip to Step 8.


Caution You must specify the same account on the both the primary and the secondary servers.

Step 8 Enter the password for the account that owns the failover service.

Step 9 Click Next.

Step 10 Click Configure. The wizard verifies settings and configures failover on the secondary server.

If the wizard does not finish the configuration successfully, an error message explains why the wizard failed. Exit the wizard, correct the problem, and click Configure again.

Step 11 Click Finish.

Step 12 Exit and restart the Cisco Unity software.


Troubleshooting

Cisco Unity troubleshooting information can be found:

In the Cisco Unity Troubleshooting Guide, which is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

At the website http://www.cisco.com/warp/public/788/AVVID/vmum.shtml.

Cisco Unity Demonstration System

When you run the Cisco Unity Setup program on a server that does not have a system key attached, you are asked to confirm that you want to install Cisco Unity as a demonstration system. A demonstration system is a fully functioning version of Cisco Unity that has the limits noted in the "Limits on a Cisco Unity Demonstration System" section.

The software for a demonstration system can be ordered online. The orderable demonstration system is the easiest way for you to get an entire set of compact discs, including third-party software (except Windows 2000 Server). It is available at http://www.cisco.com/go/marketplace. The part number is UNITY-10USR-2DEMO. There is a small charge to cover duplication costs.

We strongly recommend that you install a demonstration system by using the software you receive when you purchase either the full version of Cisco Unity or the orderable demonstration system. Both include the versions of third-party products that Cisco Unity requires to function properly. Installations of demonstration systems frequently fail because the installer is using an unsupported version of third-party software.

Because a demonstration system is a fully functioning Cisco Unity system, installing a demonstration system requires the same level of care and attention to detail that is required of installing a system on a customer site. To successfully install a demonstration system, refer to the instructions in the Cisco Unity Installation Guide and in the integration guide for your phone system, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/index.htm.

Cisco TAC does not provide support for Cisco Unity demonstration systems.

Limits on a Cisco Unity Demonstration System

When you run the Cisco Unity Setup program on a server that does not have a system key attached, you are asked to confirm that you want to install Cisco Unity as a demonstration system. Default license settings for a demonstration system are:

2 voice ports

0 fax ports

0 TTS3000 sessions

2 RealSpeak sessions

4 Visual Messaging Interface sessions

10 voice mail users

10 fax mail users

10 text-to-speech users

10 ViewMail for Microsoft Outlook users

10 Cisco Unity ActiveAssistant users

10 Cisco Unity Visual Messaging Interface users

6 languages for the Cisco Unity Administrator

6 languages for the system conversation

Networking (to enable Internet subscribers)

The ability to integrate with any phone system

In addition, the maximum message length on a demonstration system is 15 seconds.

Using a Dual Phone System Integration with a Cisco Unity Demonstration System

To integrate a Cisco Unity demonstration system with both Cisco CallManager and a traditional, circuit-switched phone system, you must update the Windows registry.

To enable a dual phone system integration on a demonstration system


Refer to the "Assigning Dialogic Ports for a Dual Phone System Integration" appendix in the Cisco CallManager 3.0 Integration Guide, the Cisco CallManager 3.1 Integration Guide, or the Cisco CallManager 3.2 Integration Guide, available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/integuid/index.htm.


To return a demonstration system to a single IP phone system integration.


Step 1 Refer to the "Removing Voice Card Software" section in the "Upgrading a Cisco Unity 2.x System to Version 3.1" chapter of the Cisco Unity Installation Guide: Do the "To remove Intel Dialogic software" procedure for your version of Windows.

The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst.

Step 2 In the Cisco Unity Administrator, update the subscriber, call handler, notification device, switch, and any other settings that apply to the integration.


To return a demonstration system to a single traditional phone system integration


Step 1 Start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 3 Expand the key

HKEY_LOCAL_MACHINE\Software\ActiveVoice\MIU\1.0\ Initialization\ServiceProvider <x>

where <x> is a number. There are several subkeys with this name.

Step 4 Locate the subkey in which the Service Provider Name value is D41MT.TSP.

Step 5 In the subkey, click DeviceID Lower Bound.

Step 6 On the Edit menu, click Delete.

Step 7 In the Confirm Value Delete box, click OK.

Step 8 Click DeviceID Upper Bound.

Step 9 On the Edit menu, click Delete.

Step 10 In the Confirm Value Delete box, click OK.

Step 11 Close the Registry Editor.

Step 12 For the settings to take effect, restart the Cisco Unity server.

Step 13 In the Cisco Unity Administrator, update the subscriber, call handler, notification device, switch, and any other settings that apply to the integration.


Converting a Cisco Unity Demonstration System to a Standard System

Do the following procedure after you have ordered and received a standard Cisco Unity system.

To convert a demonstration system to a standard system


Step 1 Plug the system key into the parallel or USB port on the server.

Step 2 Exit the Cisco Unity software, but do not restart the server.

Step 3 Insert Cisco Unity Disc 1 in the CD-ROM drive.

Step 4 Browse to the root directory, and double-click Setup.exe.

Step 5 Follow the on-screen prompts and the instructions in the e-mail that you received from Cisco when you registered Cisco Unity on Cisco.com.

Step 6 Restart the Cisco Unity server.

Step 7 Redo the procedures for your integration by using the applicable Cisco Unity integration guide. Integration guides are available on the Cisco Unity Documentation compact disc and on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.


Cisco Unity Documentation

Table 16 Cisco Unity Documentation Set 

Document
Location

Cisco Unity at a Glance for Optional Conversation 1 card

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Cisco Unity at a Glance for Standard Conversation card

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Cisco Unity Bridge Installation Guide

Available in print, on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge/big/index.htm, and on the Cisco Documentation CD-ROM.

Cisco Unity Bridge Release Notes

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge/rel_note/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity Bridge System Requirements, and Supported Hardware and Software

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge/sysreq/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity-CM TSP Release Notes

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/cmptblty/tspmtrx.htm and on the Cisco Documentation CD-ROM.

Also available on the Cisco Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Cisco Unity Customization Worksheets

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Cisco Unity Failover Guide

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity Installation Guide

Available in print, on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm, and on the Cisco Documentation CD-ROM.

Cisco Unity integration guides for various phone systems

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity Release Notes

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Also available on the Cisco Software Center website at http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.

Cisco Unity System Administration Guide

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity System Requirements, and Supported Hardware and Software

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity Troubleshooting Guide

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Cisco Unity User Guide

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm.

Cisco Unity white papers and application notes

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/index.htm and on the Cisco Documentation CD-ROM.

Networking in Cisco Unity

Available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm and on the Cisco Documentation CD-ROM.

Online Help

Available in:

The Cisco Unity ActiveAssistant

The Cisco Unity Administrator

The Cisco Unity Visual Messaging Interface

Cisco Unity ViewMail for Microsoft Outlook

Regulatory Compliance and Safety Information for Cisco Unity

Available in print, on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/index.htm, and on the Cisco Documentation CD-ROM.

Translated Cisco Unity documentation

Pieces of the Cisco Unity documentation set are available in French and German on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/trans/index.htm.


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:

http://www.cisco.com

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.com users (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 the Fax or Email option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

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

http://www.cisco.com

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:

http://www.cisco.com/tac

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.