Guest

Cisco Unity

Release Notes for Cisco Unity Release 3.1(6)

 Feedback

Table Of Contents

Release Notes for Cisco Unity Release 3.1(6)

Contents

System Requirements, and Supported Hardware and Software

Compatibility Matrixes

Hewlett-Packard SoftPaq for ProLiant DL380 G2 Server

Security Issues

Microsoft Security Bulletin MS02-045

Security White Paper

Determining the Software Version

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector

G.729a Audio Codec

RealSpeak Engine

Downloading Software for Cisco Unity 3.1(6)

Downloading Full-Disc Files of Cisco Unity 3.1(6) CDs

Downloading Patch Files and Patching Cisco Unity 3.1(5) or 3.1(3) CDs

Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)

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

New and Changed Support—Release 3.1(6)

Cisco Unity Tools Depot

Cisco Unity ViewMail for Microsoft Outlook Version 4.0(2) Qualified for Use on Subscriber Workstations

Fax Servers Qualified for Use with Cisco Unity

Gigabit Ethernet

IIS Hot Fix Described in Microsoft Security Bulletin MS03-007 and Microsoft Knowledge Base Article 815021 Is Required

Phone System Integrations Qualified for Use with Cisco Unity

SQL Server 2000/MSDE 2000 Service Pack 3 Is Required, and Service Pack 3a Is Not Supported Yet

Windows 2000 Advanced Server Is Required on New Platform Overlay 4 and 5 Servers

Windows 2000 Server Service Pack 3 Is Required

New and Changed Functionality—Release 3.1(6)

Changing How Cisco Unity Handles Messages Interrupted by Disconnected Calls

Cisco Unity Conversation Available in Danish

Cisco Unity Permissions Wizard Is Required for New Installations, and an Additional Account Is Required for New Installations with Exchange 2000

Customizing the Subscriber Conversation: Changing the Order for Addressing and Recording

Customizing the Subscriber Conversation: Changing How Subscribers Confirm Message Addressing

Identified Subscriber Messaging Between Cisco Unity Servers

Intel Dialogic D/240 Voice Card

Thread-Safe Audio Codec

Installation and Upgrade Notes

Automatic Gain Control Setting Adjustment

Cisco Unity Phone Conversation System Prompts

Exchange 2003: Do Not Run Forestprep to Begin an Exchange Upgrade

Failover and AMIS: Restriction Table Selection 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 and Mainland Mandarin Text to Speech

Limitations and Restrictions

Dual NICs

Failover and the Cisco Unity Bridge

Search Scope for Inbound Messages from the Cisco Unity Bridge

Search Scope for the Cisco Unity Visual Messaging Interface Address Book

Subscriber Lookups Fail to Find Subscriber Names in Japanese

Text to Speech Does Not Play Name in From Field

Windows Terminal Services

Caveats

Open Caveats—Release 3.1(6)

Resolved Caveats—Release 3.1(6)

Documentation Updates

Errors

Recording Phone Calls with Live Record: Cisco Unity System Administration Guide and Cisco Unity User 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

Subscriber Total Mailbox Size: Cisco Unity System Administration Guide

Switch File Location: 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 Guide

Multiple Languages: Cisco Unity System Administration Guide

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

Unity Messaging System Mailbox

UAmis Mailbox

UOmni Mailbox

Uninstalling Cisco Unity on the Secondary Server

Troubleshooting

Installing a 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

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco TAC Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco Unity Release 3.1(6)


Revised February 6, 2004

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(6).

Cisco Unity software is available on the Cisco Unity 3.1 Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-31.

Contents

These release notes contain the following sections:

System Requirements, and Supported Hardware and Software

Determining the Software Version

Downloading Software for Cisco Unity 3.1(6)

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

New and Changed Support—Release 3.1(6)

New and Changed Functionality—Release 3.1(6)

Installation and Upgrade Notes

Limitations and Restrictions

Caveats

Documentation Updates

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

Uninstalling Cisco Unity on the Secondary Server

Troubleshooting

Installing a Cisco Unity Demonstration System

Cisco Unity Documentation

Obtaining Documentation

Documentation Feedback

Obtaining Technical Assistance

Obtaining Additional Publications and Information

System Requirements, and Supported Hardware and Software

The following documents list the most current Cisco Unity requirements, and are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Cisco Unity 3.1 System Requirements, and Supported Hardware and Software

Cisco Unity Bridge System Requirements, and Supported Hardware and Software

Cisco Unity Networking Options Requirements (With Microsoft Exchange)

Compatibility Matrixes

The following matrixes list the most current version combinations qualified for use with Cisco Unity. The matrixes are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations

Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, and Cisco CallManager

Compatibility Matrix: Required and Recommended Third-Party Service Packs.

Hewlett-Packard SoftPaq for ProLiant DL380 G2 Server

A customer-provided Hewlett-Packard ProLiant DL380 G2 server with a Magma expansion chassis requires a system BIOS version P24 dated June 26, 2002 or later, available from the Hewlett-Packard website.

Security Issues

Microsoft Security Bulletin MS02-045

Cisco Unity servers are vulnerable to the types of attacks described in Microsoft Security Bulletin MS02-045. 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 the patch from the Microsoft website.

Security White Paper

For information about security best practices, refer to White Paper: Security Best Practices for Cisco Unity 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/security.htm.

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 Build Number 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 Version in Use: Cisco Unity 3.1(6) and Later, Voice Connector 10.0 and Later


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 the applicable directory:

Exchange 2000
or Exchange 2003

<ExchangeServerPath>\VoiceGateway\Bin

Exchange 5.5

<ExchangeServerPath>\Connect\Voice\Bin


Step 3 Right-click GwIvc.exe, and click Properties.

Step 4 Click the Version tab in the Properties window.

Step 5 In the Item Name box, click Product Version to view the product version in the Value box.


To Determine the Voice Connector Version in Use: Cisco Unity 3.0-3.1(5)


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 the applicable directory:

Exchange 2000

<ExchangeServerPath>\VoiceGateway\Bin\LocalizedFiles\ENU

Exchange 5.5

<ExchangeServerPath>\Voice\Bin\LocalizedFiles\ENU


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

Step 4 In the Properties window, click the Version tab to view the File Version.


G.729a Audio Codec

When the G.729a audio codec has been installed on the Cisco Unity server or on a subscriber workstation, use the following procedure to determine the codec version.

To Determine the G.729a Audio Codec Version in Use


Step 1 Browse to the Winnt\System32 directory.

Step 2 Right-click Sl_g729a.acm, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The G.729a audio codec version is displayed in the Value window.


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)


Downloading Software for Cisco Unity 3.1(6)

This section contains procedures for downloading full-disc files of Cisco Unity version 3.1(6) CDs and patch files for Cisco Unity 3.1(5) or 3.1(3) CDs, and for downloading full-disc files of third-party Service Packs CDs from the Cisco Unity 3.1 Software Download page.

Do the procedures in either the first or the second section—depending on your upgrade plans—and the third section:

Downloading Full-Disc Files of Cisco Unity 3.1(6) CDs

Downloading Patch Files and Patching Cisco Unity 3.1(5) or 3.1(3) CDs

Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)

Downloading Full-Disc Files of Cisco Unity 3.1(6) CDs

Table 1 lists the contents of the Cisco Unity 3.1(6) CD files. The files contain only Cisco Unity software. They do not contain any third-party software.

Table 1 Cisco Unity 3.1(6) CD Files 

CD
File Name
Contents
1

CiscoUnity3.1.6.CD1.exe

Cisco Unity application files and ENU language files

2

CiscoUnity3.1.6.CD2.exe

ENG, ENA, and ENZ language files

3

CiscoUnity3.1.6.CD3.exe

DEU, NOR, and NLD language files

4

CiscoUnity3.1.6.CD4.exe

FRA, SVE, ITA, and DAN language files

5

CiscoUnity3.1.6.CD5.exe

ESP, ESO, and PTB language files

6

CiscoUnity3.1.6.CD6.exe

JPN, CHS, CHT, and KOR language files

7

CiscoUnity3.1.6.CD7.exe

Voice card driver files


To Download Full-Disc Files of Cisco Unity 3.1(6) CDs


Step 1 Use Table 1 to determine which Cisco Unity 3.1(6) CD files to download. You always need CD 1.

Step 2 Confirm that the computer you are using has up to 680 MB of hard disk space for each of the applicable Cisco Unity 3.1(6) CD files, in addition to the space required to download the file. (The download-file sizes appear on the Cisco Unity 3.1 Software Download page.)

Step 3 On a computer with a high-speed Internet connection, go to the Cisco Unity 3.1 Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-31.

Step 4 In the paragraph at the top of the page, click Download Full CD Images of Unity 3.1.

Step 5 Enter your contact information, and click Submit.

Step 6 On the Software Download: Cisco Unity 3.1 CD Images page, click the name of the file to download.

Step 7 Follow the on-screen prompts to complete the download. Note that each file may take more than 10 minutes to download.

Step 8 Repeat Step 6 and Step 7 for each file that you need.

Step 9 When all downloads are complete, extract the files for each CD 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.

Step 10 If you plan to install Cisco Unity 3.1(6) from new compact discs, create a new Cisco Unity 3.1(6) CD <N> for each CD file.

Step 11 When you are done extracting the files, delete the downloaded .exe files to free disk space.


Downloading Patch Files and Patching Cisco Unity 3.1(5) or 3.1(3) CDs

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(6) from the Cisco Unity 3.1 Software Download page, then update the Cisco Unity 3.1(5) or Cisco Unity 3.1(3) CD files with the Cspatch executable file. You can then make new compact discs to install the upgrade, or install directly from updated disc files on the Cisco Unity server. (Cisco Unity versions 3.1(4) and 3.1(2) were available only from the Cisco Unity 3.1 Software Download page, so there are no 3.1(4) or 3.1(2) patch files available.)

The patch files patch only Cisco Unity CD files, and the CD files contain only Cisco Unity software. They do not contain any third-party software.

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

If you do not have Cisco Unity version 3.1(5) or 3.1(3) CD files, download the full-disc files of Cisco Unity 3.1(6) CDs. See the "Downloading Full-Disc Files of Cisco Unity 3.1(6) CDs" section.


Note Patching CD files is labor intensive and time consuming. Unless your network connection is very slow, you will probably find that downloading full-disc files is faster and easier than downloading and patching your current CD files.


To Download Patch Files and Patch Cisco Unity 3.1(5) or 3.1(3) CDs


Step 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 CD files.

Step 2 On a computer with a high-speed Internet connection, go to the Cisco Unity 3.1 Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-31.

Step 3 Download one of the following files, depending on the version of Cisco Unity CD files that you want to update:

CiscoUnity3.1.6PatchFrom3.1.5.exe

Will update all Cisco Unity 3.1(5) CD files.

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

Will update only Cisco Unity 3.1(5) CD 1 (Cisco Unity application files and ENU language files).

CiscoUnity3.1.6PatchFrom3.1.3.exe

Will update all Cisco Unity 3.1(3) CD files.

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

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


Step 4 In Windows Explorer, double-click CiscoUnity3.1.6PatchFrom<Version>.exe or CiscoUnity3.1.6PatchFrom<Version>-CD1-only.exe.

Step 5 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.6PatchFrom<Version> or CiscoUnity3.1.6PatchFrom<Version>-CD1-only, with subdirectories CD1, CD2, CD3, CD4, CD5, CD6, and CD7, as applicable.

Step 6 Delete the CiscoUnity3.1.6PatchFrom<Version>.exe or CiscoUnity3.1.6PatchFrom<Version>-CD1-only.exe file to free disk space:

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

Step 8 Use Table 2 to determine which CD files you need to patch. You always need CD 1.

Table 2 Cisco Unity 3.1(6) CD Files 

CD
Contents
1

Cisco Unity application files and ENU language files

2

ENG, ENA, and ENZ language files

3

DEU, NOR, and NLD language files

4

FRA, SVE, ITA, and DAN language files

5

ESP, ESO, and PTB language files

6

JPN, CHS, CHT, and KOR language files

7

Voice card driver files


Step 9 On the partition, create a CiscoUnity3.1.5 or CiscoUnity3.1.3 directory, and create subdirectories for the CDs you need to patch (for example, CD1, CD2, and so on).

Step 10 Copy the Cisco Unity 3.1(5) or Cisco Unity 3.1(3) CD files that you need to patch to the corresponding subdirectories.

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

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

Step 13 Follow the on-screen prompts. You will be prompted to browse to the subdirectories that you created in Step 9 for each CD file. The patch may take several minutes. When you see the message "The patch succeeded," continue with Step 14.

Step 14 If the patch process fails or is canceled, the 3.1(5) Cisco Unity CD <N> or 3.1(3) Cisco Unity CD <N> file that you made in Step 10 is restored to its original state. Correct any problems, and begin again with Step 11.

Step 15 If you plan to install the 3.1(6) upgrade from new CDs, create a new Cisco Unity 3.1(6) CD <N> with the updated CD file.

Step 16 Repeat Step 11 through Step 15 for each of the remaining Cisco Unity 3.1(5) or Cisco Unity 3.1(3) CD files. All of the CD files that you want to use for the upgrade must be updated before you start the upgrade.


Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)

Table 3 lists the contents of the Service Packs CD files for Cisco Unity 3.1(6). Each CD file is available in U.S. English and Japanese.

Table 3 Contents of Service Packs CD Files for Cisco Unity 3.1(6) 

CD
Contents
CiscoUnity3.1.6ServicePacks-ENU-CD1of2
(U.S. English)

Exchange 5.5 SP 4

Exchange 2000 SP 2

IIS hot fix described in Microsoft Security Bulletin MS03-007 and Microsoft Knowledge Base article 815021

Windows 2000 SP 3

CiscoUnity3.1.6ServicePacks-ENU-CD2of2
(U.S. English)

Exchange 2000 SP 3

MSDE 2000 SP 3

SQL Server 2000 SP 3

MSDE-SP3-ENU (U.S. English)

MSDE 2000 SP 3

SQL-2000-SP3-ENU (U.S. English)

SQL Server 2000 SP 3

CiscoUnity3.1.6ServicePacks-JPN-CD1of3
(Japanese)

IIS hot fix described in Microsoft Security Bulletin MS03-007 and Microsoft Knowledge Base article 815021

MSDE 2000 SP 3

SQL Server 2000 SP 3

Windows 2000 SP 3

CiscoUnity3.1.6ServicePacks-JPN-CD2of3
(Japanese)

Exchange 2000 SP 2

Exchange 2000 SP 3

CiscoUnity3.1.6ServicePacks-JPN-CD3of3
(Japanese)

Exchange 5.5 SP 4

MSDE-SP3-JPN (Japanese)

MSDE 2000 SP 3

SQL-2000-SP3-JPN (Japanese)

SQL Server 2000 SP 3


To Download Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)


Step 1 Use Table 3 to determine which Service Packs CD files to download.

Step 2 Confirm that the computer you are using has up to 680 MB of hard disk space for each of the applicable Cisco Unity 3.1(6) Service Packs CD files, in addition to the space required to download the file. (The download-file sizes appear on the Cisco Unity 3.1 Software Download page.)

Step 3 On a computer with a high-speed Internet connection, go to the Cisco Unity 3.1 Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-31.

Step 4 On the Cisco Unity 3.1 Software Download page, click the name of the Service Packs CD file to download, in the applicable language. (The three letters that appear before the CD number in the file name refer to the language.)

Step 5 Follow the on-screen prompts to complete the download.

Step 6 Repeat Step 4 and Step 5 for each Service Packs CD file that you need.

Step 7 When all downloads are complete, extract the files for each Service Packs CD 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 following table lists the default locations of the unzipped service pack files for U.S. English (ENU) and Japanese (JPN) versions:

Exchange 5.5 SP 4

CiscoUnity3.1.6ServicePacks-ENU-CD1of2\Exchange_5.5_sp4\Update.exe

CiscoUnity3.1.6ServicePacks-JPN-CD3of3\Exchange_5.5_sp4\Update.exe

Exchange 2000 SP 2

CiscoUnity3.1.6ServicePacks-ENU-CD1of2\Exchange_2000_sp2\Update.exe

CiscoUnity3.1.6ServicePacks-JPN-CD2of3\Exchange_2000_sp2\Update.exe

Exchange 2000 SP 3

CiscoUnity3.1.6ServicePacks-ENU-CD2of2\Exchange_2000_sp3\Update.exe

CiscoUnity3.1.6ServicePacks-JPN-CD2of3\Exchange_2000_sp3\Update.exe

IIS hot fix

CiscoUnity3.1.6ServicePacks-ENU-CD1of2\Q815021_W2K_sp4_x86_EN.exe

CiscoUnity3.1.6ServicePacks-JPN-CD1of3\Q815021_W2K_sp4_x86_EN.exe

MSDE 2000 SP 3

CiscoUnity3.1.6ServicePacks-ENU-CD2of2\MSDE_sp3\MSDE\Setup.exe

CiscoUnity3.1.6ServicePacks-JPN-CD1of3\MSDE_sp3\MSDE\Setup.exe

MSDE SP3\Setup.exe (if you downloaded MSDE-SP3-ENU or MSDE-SP3-JPN)

SQL Server 2000 SP 3

CiscoUnity3.1.6ServicePacks-ENU-CD2of2\SQL_2000_SP3\x86\Setup\Setupsql.exe

CiscoUnity3.1.6ServicePacks-JPN-CD1of3\SQL_2000_SP3\x86\Setup\Setupsql.exe

SQL 2000 SP3\Setupsql.exe (if you downloaded SQL-2000-SP3-ENU or SQL-2000-SP3-JPN)

Windows 2000 SP 3

CiscoUnity3.1.6ServicePacks-ENU-CD1of2\Windows_2000_SP3\ENU_w2ksp3.exe

CiscoUnity3.1.6ServicePacks-JPN-CD1of3\Windows_2000_SP3\ENU_w2ksp3.exe


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



Step 8 When you are done extracting the files, delete the downloaded .exe files, to free disk space.


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

To upgrade to Cisco Unity 3.1(6), refer to the applicable chapter of the Cisco Unity Installation Guide, Release 3.1:

"Upgrading a Cisco Unity 3.0 or 3.1 System."

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


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.

If you have installed Windows 2000 Service Pack 4 on the Cisco Unity server, refer to the tech note Using Windows 2000 Server Service Pack 4 with Cisco Unity 3.1, 4.0(1), and 4.0(2) for information on the registry change that you must make before you can rerun Cisco Unity Setup. The tech note is available at http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Software:Unity&viewall=true, in the "Operating Systems and Core Components" section.

The Cisco Unity Installation Guide, Release 3.1 is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity31/inst/inst31/index.htm.

For upgrades from version 3.0 or 2.4(6), you download the applicable full-disc files of Cisco Unity 3.1(6) CDs from the Cisco Unity 3.1 Software Download page, and install from those files.

You also download the Service Packs CD files from the Cisco Unity 3.1 Software Download page.

The Cisco Unity 3.1(6) CD files 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.


Caution Cisco Unity 3.x does not support Exchange 2003. Before you run Exchange 2003 Forestprep to begin an upgrade to Exchange 2003, you must first upgrade Cisco Unity to version 4.0(3) or later. Otherwise, the changes that Forestprep makes to Active Directory will cause Cisco Unity to stop functioning.

New and Changed Support—Release 3.1(6)

This section contains information about new and changed support in the Cisco Unity Release 3.1(6) time frame only. Refer to the release notes of the applicable version for information about new and changed support with earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Cisco Unity Tools Depot

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

Table 4 Changes to the Tools Depot 

Updated Tools
New Tools

Advanced Settings Tool

Bulk Edit

Cisco Unity Message Store Manager (MSM)

Disaster Recovery Backup and Restore (DiRT)

Gather Unity System Information (GUSI)

Global Subscriber Manager (GSM)

Permissions Wizard

Subscriber Information Dump

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

Cisco Unity Database Link Explorer (CUDLE)

Directory Access Diagnostics

For information on how to use a tool, see the 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.

Cisco Unity ViewMail for Microsoft Outlook Version 4.0(2) Qualified for Use on Subscriber Workstations

Cisco Unity version 3.1(6) supports ViewMail for Microsoft Outlook version 4.0(2) for use on Cisco Unity subscriber workstations. The setup for ViewMail 4.0(2) has been redesigned to use Microsoft Windows Installer, and is presented in a wizard format. The new setup allows system administrators to deploy and support ViewMail from a CD-ROM, shared network drive, or by using software publishing tools, such as Microsoft IntelliMirror and version 1.2 or 2.0 of Systems Management Server.

In addition, the new ViewMail installation no longer requires the installation of Microsoft Collaboration Data Objects on subscriber workstations.

For additional information— including upgrade considerations, related caveats, and installation instructions—refer to Release Notes for Cisco Unity ViewMail for Microsoft Outlook Release 4.0(2), available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Note that Cisco Unity 3.1(6) provides ViewMail version 4.0(2) on Cisco Unity CD 1. Therefore, you do not need to download the ViewMail files from the ViewMail for Microsoft Outlook Software Download page, as indicated in the installation procedure in the ViewMail 4.0(2) release notes.

Fax Servers Qualified for Use with Cisco Unity

Interstar XMediusFax version 3.0 has been qualified for use with Cisco Unity.

For the most current list of all supported fax servers—including fax servers qualified since the release of Cisco Unity version 3.1(6)—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/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Gigabit Ethernet

Use of gigabit Ethernet is recommended on the Cisco Unity server for general connectivity, and in particular for the heartbeat link between Cisco Unity failover nodes, but it is not required.

IIS Hot Fix Described in Microsoft Security Bulletin MS03-007 and Microsoft Knowledge Base Article 815021 Is Required

Cisco Unity 3.1(6) requires that the IIS hot fix described in Microsoft Security Bulletin MS03-007 and Microsoft Knowledge Base article 815021 be installed on the Cisco Unity server. The software is included on Cisco Unity Service Packs CD 1 (U.S English and Japanese). For information on downloading the CD from Cisco.com, see the "Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)" section.

Phone System Integrations Qualified for Use with Cisco Unity

The following phone system integrations have been qualified for use with Cisco Unity version 3.1(6) and later:

Alcatel 4400.

Avaya Definity ProLogix.

Cisco CallManager 3.3.

ECI Coral III.

Fujitsu 9600.

For the most current list of all supported phone system integrations—including integrations qualified since the release of Cisco Unity version 3.1(6)—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/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

SQL Server 2000/MSDE 2000 Service Pack 3 Is Required, and Service Pack 3a Is Not Supported Yet

SQL Server 2000/MSDE 2000 Service Pack 3 is required for Cisco Unity 3.1(6). The software is included on Cisco Unity Service Packs CD 2 for U.S. English and Cisco Unity Service Packs CD 1 for Japanese. For information on downloading the CD from Cisco.com, see the "Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)" section.


Caution Do not install SQL Server 2000/MSDE 2000 Service Pack 3a on the Cisco Unity server. Service Pack 3a is currently being qualified for use with Cisco Unity. The testing done so far suggests that you may need to make some configuration changes to use Service Pack 3a on the Cisco Unity server. Do not install Service Pack 3a until it has been qualified, or Cisco Unity may stop working.

Windows 2000 Advanced Server Is Required on New Platform Overlay 4 and 5 Servers

Windows 2000 Advanced Server (in English, German, French, or Japanese) is required for a new installation of Cisco Unity on a Platform Overlay 4 or 5 server. It is also required for an existing Cisco Unity site that purchases an additional Cisco Unity Platform Overlay 4 or 5 server or is replacing a Cisco Unity server with a new Platform Overlay 4 or 5 server. (Platform overlays are defined in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.)

Note that Windows 2000 Advanced Server is included with Cisco Unity Platform Overlay 4 and 5 servers purchased from Cisco. If the server is not purchased from Cisco, the customer also must purchase Windows 2000 Advanced Server.

You are not required to upgrade existing Cisco Unity servers to Windows 2000 Advanced Server, but you may want to for performance reasons as described in Cisco Unity Virtual Memory Usage Troubleshooting and Workaround, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html. If you choose to upgrade from Windows 2000 Server to Windows 2000 Advanced Server, do the following procedure.

To Upgrade from Windows 2000 Server to Windows 2000 Advanced Server (Optional)


Step 1 Download the latest version of the Cisco Unity Disaster Recovery Tool (DiRT) from http://ciscounitytools.com/.

Step 2 Back up Cisco Unity data using DiRT. For more information, refer to the DiRT online Help and the streaming video training available on http://ciscounitytools.com/.


Caution The restore will fail if you do not follow the instructions in the DiRT online Help. For example, you cannot restore data to a version of Cisco Unity different from the one you backed up.

Step 3 If Exchange is installed on the Cisco Unity server: Back up messages by using Veritas Backup Exec or another Exchange-aware backup utility.

Step 4 Reinstall all software on the Cisco Unity server. Refer to "Part 1: Installing and Configuring the Cisco Unity Server" in the "Overview of Mandatory Tasks for Installing Cisco Unity" chapter of the Cisco Unity Installation Guide, Release 3.1, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guides_books_list.html.

Step 5 If Exchange is installed on the Cisco Unity server: Restore messages by using the backup that you made in Step 3.

Step 6 Restore Cisco Unity data by using DiRT. Refer to the DiRT online Help.

Step 7 Restore settings that are not saved by DiRT (for example, any mappings made with the GrantUnityAccess tool). Refer to the DiRT online Help.


Windows 2000 Server Service Pack 3 Is Required

Windows 2000 Server Service Pack 3 is required for Cisco Unity 3.1(6). The software is included on Cisco Unity Service Packs CD 1 (U.S. English and Japanese). For information on downloading the CD from Cisco.com, see the "Downloading Full-Disc Files of Service Packs CDs for Cisco Unity 3.1(6)" section.

New and Changed Functionality—Release 3.1(6)

This section contains information about new and changed functionality for Cisco Unity Release 3.1(6) only. Refer to the release notes of the applicable version for information about new and changed functionality in earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Changing How Cisco Unity Handles Messages Interrupted by Disconnected Calls

You can change how Cisco Unity handles messages that are interrupted by disconnected calls as subscribers are in the process of sending, replying to, or forwarding messages. Calls can be intentionally or unintentionally disconnected—for example, when a subscriber hangs up or when a cell phone loses its charge or signal.

By default, Cisco Unity sends a message when the call is disconnected in the following circumstances:

When a subscriber is
replying to or sending
a message

As long as the message has at least one recipient and the recording is more than one second (1,000 ms) in length. This means that Cisco Unity sends the message even though the subscriber may not have finished recording or addressing the message.

When a subscriber is
forwarding a message

As long as the message has at least one recipient. This means that Cisco Unity sends the message even though the subscriber may not have recorded an introduction or completely addressed the message.


By using the Advanced Settings Tool to change the registry, you can set Cisco Unity so that it will delete interrupted messages unless subscribers have pressed the # key to send their messages. Thus, if a call is disconnected before a subscriber has a chance to press #, Cisco Unity deletes the message rather than sending it.

How Cisco Unity handles a message interrupted by a disconnected call depends on the registry value you set:

0

Cisco Unity sends the interrupted message even if the subscriber has not pressed the # key.

1

Cisco Unity deletes the interrupted message unless the subscriber has pressed the # key.


The registry change is applied systemwide to all subscribers associated with the Cisco Unity server. You cannot make the change for an individual subscriber or a specific group of subscribers.


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


Do the following procedure to change how Cisco Unity handles messages when calls are disconnected.

To Change How Cisco Unity Handles Messages Interrupted by Disconnected Calls


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

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

Step 3 In the Cisco Unity Settings pane, click Subscriber Send Message Hang-Up Action.

Step 4 In the New Value list, click the applicable value, and click Set.

Step 5 When prompted, click OK.

Step 6 Click Exit.

You do not need to restart the Cisco Unity software for the registry change to take effect.


Cisco Unity Conversation Available in Danish

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

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/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.

Cisco Unity Permissions Wizard Is Required for New Installations, and an Additional Account Is Required for New Installations with Exchange 2000

When you do a new installation of Cisco Unity 3.1(6), you must create accounts for the installation and run the Cisco Unity Permissions wizard to give the accounts the necessary rights before you install Cisco Unity. If you are using Exchange 2000 for the message store, either alone or with Exchange 5.5, you must now create two accounts for Cisco Unity services—one for directory services and the other for message store services. The Permissions wizard will prompt you to specify an account for each type of service and does not allow you to specify the same account twice because the rights required by the two accounts conflict with one another. You cannot complete the Cisco Unity installation if you have not run the Permissions wizard.

For more information, refer to the sections "About the Accounts Required for the Cisco Unity Installation," "Creating the Accounts," and "Setting Rights and Permissions with the Cisco Unity Permissions Wizard" in the "Installing the Cisco Unity System" chapter of the Cisco Unity Installation Guide.

Customizing the Subscriber Conversation: Changing the Order for Addressing and Recording

The Cisco Unity subscriber conversation can be customized to change the order in which Cisco Unity prompts subscribers to address and record when they send or forward messages to other subscribers or distribution lists. By default, when a subscriber sends or forwards a message, Cisco Unity first prompts the subscriber to address the message and then prompts the subscriber to record the message or to record an introduction for a forwarded message.

By using the Advanced Settings Tool to change the registry, you can customize the subscriber conversation so that Cisco Unity prompts subscribers to record a message or introduction before prompting them to address it.

How Cisco Unity prompts subscribers to address and record when they send and forward messages depends on the registry value you set:

0

Cisco Unity records the message and then addresses it.

1

Cisco Unity addresses the message and then records it.


The registry change is applied systemwide to all subscribers associated with the Cisco Unity server. You cannot make the change for an individual subscriber or a specific group of subscribers. Finally, note that you cannot change the order in which Cisco Unity prompts subscribers to address and record when they reply to messages; Cisco Unity always prompts subscribers to record a reply before allowing them to add additional recipients.


Note 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 


Do the following procedure to change the order in which Cisco Unity prompts subscribers to address and record when they send messages.

To Change the Order of Addressing and Recording When Subscribers Send Messages


Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity 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 Subscriber Send Message Flow.

Step 4 In the New Value list, click the applicable value, and click Set.

Step 5 When prompted, click OK.

Step 6 Click Exit.

You do not need to restart the Cisco Unity software for the registry change to take effect.


Customizing the Subscriber Conversation: Changing How Subscribers Confirm Message Addressing

The Cisco Unity subscriber conversation can be customized to alter how Cisco Unity prompts a subscriber to confirm message addressing. By default, when a subscriber addresses a message, Cisco Unity plays the recorded name and extension of the intended recipient (or, when there is no recorded name, Cisco Unity plays the extension instead) and asks the subscriber to confirm that the recipient is correct.

By using the Advanced Settings Tool to change the registry, you can customize how Cisco Unity prompts subscribers to confirm message addressing. Table 5 shows the confirmation prompts that subscribers hear during message addressing, depending on the registry value you set.


Note The Advanced Settings Tool also allows you to customize other aspects of the subscriber conversation. The Cisco Unity prompts listed in Table 5 assume that all other registry settings related to the subscriber conversation are set to their default values. Changes to some registry settings—such as the Directory List Selection Style setting—affect what the subscriber hears when you customize message addressing.


Table 5 Confirmation Prompts During Message Addressing 

Registry
Value
When There Is an Exact Match
When There Is More Than One Matching Name

0

"For <recipient name> at <extension>, press #. To cancel, press *."

"There are <x> matching names; choose by number. For Alex Campbell at extension 2015, press 1. For Li Campbell at extension 2003, press 2. For Terry Campbell at extension 2078, press 3..."

1

"For <recipient name>, press #. To cancel, press *."

"There are <x> matching names; choose by number. For Alex Campbell, press 1. For Li Campbell, press 2. For Terry Campbell, press 3..."

2

"Added."

"There are <x> matching names; choose by number. For Alex Campbell at extension 2015, press 1. For Li Campbell at extension 2003, press 2. For Terry Campbell at extension 2078, press 3..."


The registry change is applied systemwide to all subscribers associated with the Cisco Unity server. You cannot change how Cisco Unity prompts an individual subscriber or a specific group of subscribers to confirm message addressing.


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


Do the following procedure to change how subscribers confirm message addressing.

To Change How Subscribers Confirm Message Addressing


Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity 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 Subscriber Addressing Confirm Match Mode.

Step 4 In the New Value list, click the applicable value, and click Set.

Step 5 When prompted, click OK.

Step 6 Click Exit.

You do not need to restart the Cisco Unity software for the registry change to take effect.


Identified Subscriber Messaging Between Cisco Unity Servers

Identified subscriber messaging is fully functional between Cisco Unity 3.1(6) servers configured for Digital Networking. When identified subscriber messaging is enabled, Cisco Unity automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.

In other words, when a subscriber on one Cisco Unity server calls a subscriber on either the same Cisco Unity server or a different Cisco Unity server and leaves a message, Cisco Unity can identify the message as being from a subscriber. This means that:

Cisco Unity can play the internal greeting when the caller leaves a message.

Cisco Unity can play the recorded name of the calling subscriber when the recipient listens to the message.

Cisco Unity allows the recipient to record a reply.

In installations with networked servers running different versions of Cisco Unity, in order for identified subscriber messaging to work, all Cisco Unity servers must be running version 3.1(6).

Note that identified subscriber messaging between Cisco Unity servers is not enabled by default. To enable identified subscriber messaging between Cisco Unity servers:

The automated attendant search scope must be set to the dialing domain.

Identified subscriber messaging must be enabled on the System > Configuration Settings page in the Cisco Unity Administrator.

For detailed information, see the "Enabling Identified Subscriber Messaging" section in the "Digital Networking" chapter of the Networking in Cisco Unity Guide available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guide_books_list.html.

Intel Dialogic D/240 Voice Card

Fixes for caveats CDCdy68405, CSCdx25405, CSCdx83741, and CSCdw73457 resolve problems with port lock-ups, call collisions, and blind transfers on systems that use Intel Dialogic D/240 voice cards. Removal and reinstallation of the Dialogic software, a required step in the 3.1(6) upgrade process, is also required to implement these fixes.

Thread-Safe Audio Codec

The G.729a audio codec that ships with Cisco Unity has been upgraded to resolve caveat CSCae08069. The workaround described in this caveat is no longer necessary.

Installation and Upgrade Notes

For detailed information on upgrading to Cisco Unity version 3.1, refer to the Cisco Unity Installation Guide, Release 3.1, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guides_books_list.html.

Automatic Gain Control Setting Adjustment

Do the following procedure to ensure that automatic gain control settings are correct. The procedure levels all WAV files on the Cisco Unity server to the same value, and provides instructions to adjust the playback level if needed.

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.


Cisco Unity Phone Conversation System Prompts

System prompts are standard recordings that come with the Cisco Unity system, and they cannot be changed by using the Cisco Unity Administrator, the ActiveAssistant, or the phone conversation. System prompts are played in different combinations in multiple places in the phone conversation. All system prompts are located in the CommSvr\Localize\Prompts directory and subdirectories.

Do not delete system prompts, as this can cause system errors.

Customizing system prompts is not supported. All system prompts are automatically deleted and replaced whenever you upgrade Cisco Unity, including the installation of maintenance releases.

Exchange 2003: Do Not Run Forestprep to Begin an Exchange Upgrade


Caution Cisco Unity 3.x does not support Exchange 2003. Before you run Exchange 2003 Forestprep to begin an upgrade to Exchange 2003, you must first upgrade Cisco Unity to version 4.0(3) or later. Otherwise, the changes that Forestprep makes to Active Directory will cause Cisco Unity to stop functioning.

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

On a system set up for Cisco Unity failover, when you change the restriction table to be used for outgoing AMIS calls, the table selection on the primary server does not replicate to the secondary server. You must manually select the same AMIS restriction table on the secondary server. (Note that the settings on the restriction table itself replicate.) You specify the AMIS restriction table in the Cisco Unity Administrator on the Network > AMIS Options page.

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/en/US/partner/products/sw/voicesw/ps2237/prod_technical_reference_list.html.

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 and Mainland Mandarin Text to Speech

Japanese and Mainland Mandarin text to speech require specific language settings on the Cisco Unity server.

To Use Mainland Mandarin Text to Speech


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

Step 2 On the General tab, in the Your Locale (Location) list, click Chinese (PRC).

Step 3 In the Language Settings for the System box, click Simplified Chinese.

If you have a multilingual system, choose additional languages as applicable.

Step 4 Click Set Default. The Set System Locale dialog box opens.

Step 5 In the Select Appropriate Locale list, click Chinese (PRC).

Step 6 Restart the Cisco Unity server for the changes to take effect.


To Use Japanese Text to Speech


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

Step 2 On the General tab, in the Your Locale (Location) list, click Japanese.

Step 3 In the Language Settings for the System box, click Japanese.

If you have a multilingual system, choose additional languages as applicable.

Step 4 Click Set Default. The Set System Locale dialog box opens.

Step 5 In the Select Appropriate Locale list, click Japanese.

Step 6 Restart the Cisco Unity server for the changes to take effect.


For more information, refer to the "Multiple Languages" chapter of the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_books_list.html.

Limitations and Restrictions

Dual NICs

Cisco Unity is qualified for dual network interface cards (NICs) configured only in adapter 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 Hewlett-Packard). 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 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.

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

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, callers can find subscriber names by using directory assistance, and subscribers can use spelling mode to address messages to other subscribers. 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.)

Text to Speech Does Not Play Name in From Field

By design, when subscribers listen to their e-mail messages by using the Cisco Unity phone conversation, the text-to-speech (TTS) feature does not "read" the name in the From field to subscribers. Thus, if the message is from someone who is not a Cisco Unity subscriber, the Cisco Unity conversation does not indicate who sent the message. However, when a message is from a Cisco Unity subscriber, the Cisco Unity conversation plays the name (if one is recorded) or extension for that subscriber.

The design allows better TTS performance, and has worked as described since Cisco Unity 2.4(6). For more information, refer to caveat CSCdx95644. (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 6 on a Cisco Unity server with version 3.1(4) and later.

Table 6 Windows Terminal Services Limitations with Cisco Unity 

Remote Functionality
Cisco Unity 3.1(4) and Later

Install or upgrade Cisco Unity

Not supported

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

Not supported

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

Not supported


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.

Note that this section contains caveat information for Cisco Unity Release 3.1(6) only. Refer to the release notes of the applicable version for caveat information for earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Open Caveats—Release 3.1(6)

Table 7 Cisco Unity Release 3.1(6) Open Caveats 

Caveat Number
Sev
Description

CSCdx31189

2

Users are unable to open the Cisco Unity Administrator, and an error is displayed that the subscribers account is not associated with a Cisco Unity subscriber account. This can happen when Cisco Unity looses network connection to the DC or GC. The same behavior is observed if Unity looses network connection with a domain controller in an NT domain. This can also happen if the AvCsMgr process stops for some reason.

Workaround

1. Stop Cisco Unity by using the tray icon.

2. Stop the AvCsGateway service from the Services Control Panel, then restart the service.

3. Start Cisco Unity by using the tray icon.

4. Confirm that all Cisco Unity services have restarted, then access the Cisco Unity Administrator.

CSCdy36595

2

Cisco Unity subscribers may hear the failsafe conversation while accessing their voice mailbox. They may also see one or more of these errors in the Application Event log: Source: VBRuntime EventID: 1 Description: The VB Application identified by the event source logged this Application AvSubSetupUtilsENU: Thread ID: 598,4 Logged: modPhraseUtilGeneral: ErrorGettingProperty: Error getting property: MailUserExtension Source: AvPhraseServer_MC EventID: 10002 Description: AvPhrase:Make - error returned from Make for PhraseServer [AvSubMsgCountENU], PhraseID [AnnounceMsgCount], Message [Invalid procedure call or argument], Return code [800A0005h]. Source: AvArbiter_MC EventID: 1020 Description: [Port 26] Failed routing a continued call to application [PHGreeting] with data object type [0]. Using Failsafe instead.

In Cisco Unity version 3.1.5, this may happen due to AvCsMgr virtual memory fragmentation. If the virtual bytes exceed the recommended limits on a Cisco Unity system, the subscriber may see unexpected system behavior and error s in the Application Event log. This happens only on large systems with a high user-to-port ratio and when under heavy call traffic.

Workaround

For systems running Windows 2000 server:

1. Restart theCisco Unity server when the virtual bytes counter reaches 1.65 GB.

For systems running Windows 2000 Advanced server:


Note Do not perform this procedure if you are running Windows 2000 Server. The /3GB switch is designed for use only with Windows 2000 Advanced Server.


1. On the Cisco Unity server, open the Boot.ini file by using Windows Notepad from
<root directory>\boot.ini. The root directory corresponds to the directory where the operating system binaries are installed.

2. Add the /3GB parameter to the startup line. For example,
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT=Microsoft Windows 2000 Advanced Server /fastdetect /3GB

3. Save the Boot.ini file.

4. Install the CiscoUnity3.1(5)_ES20 hot fix, available from Cisco TAC.


Note Cisco Unity versions 3.1(5) ES20 and 3.1(6) contain the ES_20 hot fix. If you have either of these versions of Cisco Unity, skip to Step 5. If you have Cisco Unity version 3.1(5) or earlier and upgrade to version 3.1(6), you may see DDTS defect CSCdw36215 (Setup crashes when using a /3GB switch in the boot file.) If so, follow the workaround identified in the Release Note of the defect to correct the problem.


5. Restart the Cisco Unity server for the changes to take effect.

CSCdy70554

2

A Cisco Unity server may unregister one or more ports via the TSP connection to Cisco CallManager. The port unregister is initiated by Cisco Unity. The following error is displayed repeatedly in the TSP trace just before Unity unregisters the port:

CAvTapiLine:NewCall dwReason 4.

CAvTapiLine:NewCall: Previous call not deallocated.

Any Cisco Unity 3.x version using a version 6 or prior TSP connection to Cisco CallManager can experience the behavior when requests to off-box Exchange servers are delayed. The port disconnect occurs when an outstanding request to an Exchange server by a prior call never returns the requested data. Any call that request service on the same port will subsequently initiate the TSP disconnection from Cisco CallManager.

Workaround

The 7.0(1) and later TSP will disconnect the port until the failing request completes. A TSP upgrade is recommended where the port disconnect causes the next call to the same port to fail. The port will reconnect once the request (usually to a non-responsive Exchange server) has fully failed or completed. Any calls to this port during the disconnect period will forward to the next Cisco Unity port. This workaround will not correct the initial condition of a slow response from the message store.

CSCdz03042

2

The Example Subscriber serves no purpose and is security hole. In addition, the account uses a valuable mailbox license.

Workaround

Delete the Example Subscriber. Refer to the following security advisory for more information: http://www.cisco.com/warp/public/707/toll-fraud-pub.shtml.

CSCea26846

2

With Cisco Unity, when the global catalog (GC) server that MAPI uses is down, or when MAPI is unable to connect with its designated GC server, messages may not be delivered.

Cisco Unity for Exchange uses MAPI to address and send messages. When Cisco Unity starts, it ensures the name of a GC server is present in its MAPI profile. MAPI uses the GC server to resolve the names of message recipients. When the GC server is down, MAPI does not automatically use another GC server for name resolution, so messages cannot be delivered.

Workaround

1. On the Cisco Unity server, log on using the account that the Cisco Unity message store services log on as. If the message store services log on using the LocalSystem account (which is not recommended), then log on to the Cisco Unity server using an account with sufficient rights to modify the Registry.

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 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 the message store services do not log on as LocalSystem, then expand the key
HKEY_CURRENT_USER\Software\Microsoft\Windows NT \CurrentVersion \Windows Messaging Subsystem\Profiles\Unity System Profle

Otherwise (the message store services log on as LocalSystem), expand the key
HKEY_USERS\.Default\Software\Microsoft\Windows NT\CurrentVersion
\Windows Messaging Subsystem\Profiles\Unity System Profle

4. In the tree in the left pane, click dca740c8c042101ab4b908002b2fe182.

5. In the right pane, double-click 001e6602. The Edit String dialog box displays. The Value data field contains the fully-qualified domain name of the GC server that Cisco Unity monitors.

6. If the monitored GC server is permanently down or will be down for a long period of time:

a. Replace the name in the Value data field with the fully-qualified domain name of another GC/DC server.

b. Click OK and then exit Regedit.

c. Restart Cisco Unity for the change to take effect.

7. If the monitored GC server is not down, then there is a either a networking connectivity or DNS problem that needs to be resolved:

a. In a command prompt window, ping the server to check for network connectivity.

b. If the ping works, do nslookup to determine if there are any DNS problems.

CSCea43272

2

A full restore of a Cisco Unity server is not working with Backup Exec 9.0. The server was running SQL Server 2000 and Exchange 2000, and was a domain controller and global catalog server. After the restore, Microsoft Message Queuing (MSMQ) failed to start. Because Cisco Unity directory services (AvDSAD, AvGlobalCatalog, and AvDirChangeWriter) are dependant on MSMQ, they also failed to start.

CSCea59538

2

In the Cisco Unity Administrator, when the Add icon is clicked to add a new subscriber, a popup message indicates that the user could not be added. The Application Event Viewer logs the following message:

Event Type: Warning
Event Source: AvDirSynch_MC
Event Category: Warning
Event ID: 1070
Description:
<Path to the Active Directory user> was created, but the password specified could not be set. The account has been deleted.

This problem was seen in Cisco Unity 3.1(5) with an offbox Exchange 2000 partner server that is also a domain controller (DC).

Workaround

On the system in which the problem was observed, the administrator modified the display name of an existing Active Directory user using another tool. After that, subscribers could be added via the Cisco Unity Administrator. It is unknown at this time if connecting to Active Directory really did provide a workaround. However, if you encounter the problem, try the following:

1. Start Active Directory Users and Computers. (On the Windows Start menu, click Programs > Administrative Tools > Active Directory Users and Computers.)

2. Browse to the container in which Cisco Unity subscribers are or will be created.

3. Make a minor modification to the properties of a user. For example, change the display name of a user.

4. Close Active Directory Users and Computers.

5. In the Cisco Unity Administrator, try adding a subscriber.

CSCea73353

2

Some subscriber s hear the failsafe conversation when they log in by using the TUI. The following error messages are written to the Application Event log: Event Type: Error Event Source: AvConvMsg_MC Event Category: Error Event ID: 10002 Date: 09/04/2003 Time: 11:10:52 User: N/A Computer: XXXXXXX Description: GetMailboxStatus returned [0x80004005] on line 98 of file e:\views\cs_UE3.1.4.39\un_Core2 \ConversationEng\AvStateSvr\AvSGetMailboxStatus.cpp Running conversation SubMenu on Port 3 Subscriber Display Name: XXXXXX Subscriber Alias: XXXXXXXX Running conversation SubMsgCount on Port 3.

Workaround

Restart the Cisco Unity server.

CSCdv14714

3

Cisco Unity does not respond when subscribers press keys during the Message Playback menu Help.

Workaround

Tell subscribers to wait for the Help prompts to finish playing before attempting another action.

CSCdw05408

3

Doh: Cannot set a users password to blank. Symptom: You cannot set a subscribers DTMF password to blank even if the Account Policy settings say that you should be able to. Condition: This occurs in Cisco Unity 3.1(1) and later.

Workaround

There is currently no workaround.

CSCdw57310

3

Unnecessary warning during setup that disk space may be insufficient. Symptom: A warning is displayed during Unity setup part 1 that the disk space may be insufficient Condition: This happens when running Unity setup part 1 and might be displayed even when the free space is enough to install Unity

Workaround

Check whether the free disk space is enough and click on OK to continue with the install

CSCdx17690

3

Should not allow deleting an object that is a destination of links. Symptom: When Cisco Unity administrator tries to delete an object (call handler, subscriber, etc.) that is a destination of links in the System Administration, the delete object screen should not delete the object but it does. This results in creation of links that do not have their destination. Condition: This defect exists in Cisco Unity 3.0(1) or later.

Workaround

There is only a workaround for deleting subscriber objects. The Global Subscriber Manager tool available in Tools Depot has an option to delete subscribers.

CSCdx44295

3

Server rename post-SQL install and pre Unity config problematic. Symptom: Unity may fail to start after the Unity Configuration Setup is ran. Conditions: This can happen if the name of the Unity server is changed after SQL has been installed. Both Unity and MSSQL have a dependency on the name of the server.

Workaround

The workaround is to upgrade to Unity 3.1.5 or higher. To implement the fix, the following the following procedure must be performed in SQL after the servername 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 type in SELECT @@SERVERNAME Make sure that is the new servername

When SQL is installed, the SQL servername defaults to the NetBios name of the machine. If the NetBios name of the server is changed, the SQL servername does not change with the servername. When Unity creates the outside caller object, it uses the Unity_<SQL servername> account to create the account in Exchange/NT. However, when Unity tries to log on to this account, it does not use the Unity_<SQL servername>, it uses Unity_<NetBios servername> and fails. In short, if SQL servername does not equal the NetBios servername, Unity will not start.

CSCdx46888

3

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.

CSCdx89867

3

Sentinel driver doesn't install through WTS causing setup to fail. Symptom:The following error message is displayed while installing Unity 3.1(4) on a clean system through terminal services: While trying to install the Sentinel System Driver, Windows Installer returned a failure code: 3 The Unity setup cannot continue. Conditions: This occurs with Unity version 2.X and 3.X when attempting to install using Window Terminal Services.

Workaround

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. Once completed, re-run Unity setup.

CSCdy37982

3

On upgrades, AvCiscoTSP_MC.dll becomes unregistered.

CSCdy47747

3

Make messages in the Tempu.Log file more understandable. Symptom: Make messages in the Cisco Unity tempu.log file more intuitive. Condition: The tempu.log file is overwritten during every upgrade or running of the Cisco Unity Setup and the Message Store Configuration Wizard. There should be an archived log that's kept for *every* install/upgrade done to a single Cisco Unity system. This way TAC can tell if a Cisco Unity system setup was the result of a 3.1.1-to-3.1.4 version upgrade, a 3.1.1-to-3.1.3-to-3.1.4 version upgrade, or a fresh install. There currently is no mechanism to do this.

Workaround

Manually create renamed copies of tempu.log after each instance of Cisco Unity Setup and Message Store Configuration Wizard.

CSCdy47780

3

Unity provides no debugging for stored procedures and triggers.

There is no workaround. This defect tracks the serviceability of UnityDb with respect to tracing when data in UnityDb becomes corrupt or unexpectedly changes.

CSCdy66087

3

Whenever the last port on each Dialogic D240T1 voice card is configured for outgoing notification the last port locks up on the first outdial. Lock up means the port enters the busy state and never exits. The only way to get the ports to exit the busy state is to reboot Unity. Attempting to reset the port from the SA or Status Monitor results in the SA and Status Monitor hanging. These utilities must then be terminated from the Task manager.

Conditions: Unity 3.1.3 on Windows 2000 and Exchange 5.5. with a PBX integration and D/240T-1 cards.

Workaround

Line coding on the Intecom T1 card should be set to AMI rather than B8ZS. If AMI line coding is used and problem persists, disable the last port or configure it to only answer incoming calls.

CSCdy67781

3

When integrated with a Nortel Meridian via a PBXLink, calls are randomly being sent to the opening greeting instead of subscribers mailboxes. Problems:

1. After a PBXLink sends out a corrupt MWI on/off request, the very next incoming call has its call info stripped by the PBXLink. When the call is handed to Cisco Unity, it is routed to the opening greeting due to lack of call info.

2. After a caller connects with Cisco Unity and hangs up, subsequent calls may not have call info and thus will be routed to opening greeting.

Workaround

Problem 1: Dedicate a PBXLink box for MWIs, so that any PBXLink boxes that are processing incoming calls are not also processing MWIs.

Problem 2: No workaround exists at this time.

CSCdz02986

3

Users cannot configure the Event Notification Utility to send a message for a monitored event that contains an apostrophe. The popup error Error showing event properties is displayed, the changes made to the notification event are not saved, and these errors show up in the application event log:

Event Type: Error
Event Source: AvGaen_MC
EventCategory: Gaen DB Access
Event ID: 110
Date: 10/16/2002
Time: 12:26:54 PM
User: N/A
Computer: 52CCVM00
Description:
COM Exception:[Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in query expression Looks like we've got an undeliverable in the unitymta folder., 2). (0x80040E14) on line 294 of file e:\views\cs_ue3.1.3.43\un_Conv3\Gaen\AvGaenDbSvr\AvAddGaenEventDb.cpp

Event Type: Error
Event Source: AvGaen_MC
Event Category: Gaen Admin UI
Event ID: 101
Date: 10/16/2002
Time: 12:26:54 PM
User: N/A
Computer: 52CCVM00
Description:
IAvAddGaenEventDb:Submit() returned [0x80040E14] on line 1277 of file e:\views\cs_ue3.1.3.43\un_Conv3\Gaen\GaenAdmin\GaenAdminView.cpp.

Event Type: Error
Event Source: AvGaen_MC
Event Category: Gaen Admin UI
Event ID: 104
Date: 10/16/2002
Time: 12:26:54 PM
User: N/A
Computer: 52CCVM00
Description:
Failed UpdateEvent() on line 996 of file e:\views\cs_ue3.1.3.43\un_Conv3\Gaen\GaenAdmin\GaenAdminView.cpp

Workaround

Don't use apostrophes in outbound messages for notification events.

CSCdz03023

3

When configuring a new alert in the Event Notification Utility, AvUMR_MC is not an option in the Source pull-down under the Event tab.

Workaround

AvUMR_MC must be manually entered.

CSCdz04915

3

Upgrade to 3.1(5) error: Fail to register commserver services. Symptom: An upgrade from Unity 3.0(3) to Unity 3.1(5) may fail with the following chain or errors: First error: Setup; Fail to register commserver services. Followed by the same error again: Setup; Fail to register commserver services. Followed by the error: Setup; The installation is not complete. You should run this setup procedure again in its entirety.

Workaround

There is no workaround to avoid the chain of errors. Should the chain of errors occur, the installer should reboot the server and re-run setup. It is unlikely that the chain of errors will occur twice.

CSCdz05433

3

3.1(5) upgrade changes system conversation from optional to normal.Symptom: When upgrading to a new version of Unity and the option conversation is set; the system conversation might be changed from the optional conversation back to the normal (default) conversation.

Workaround

If this occurs, manually change the value of HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\CDE\1.0\SoftKey Config File to <drive>:\CommServer\Support\OptConv1.ini where <drive> = the drive letter that the CommServer directory is in. Example: C:\CommServer\Support\OptConv1.ini

CSCdz05449

3

3.1(5) upgrade, Configuration Setup hangs then disappears. Symptom: When upgrading to 3.1(5), configuration setup might appear hung for around ten minutes and then disappear. Additionally, the Unity tray icon and the AvCsMgr service might appear stuck in starting. Even after a prolonged period of time Unity does not start.

Workaround

After a reboot Unity does startup fine.

CSCdz09011

3

Customer does not receive full information when upgrading key. Symptom: When a customer goes online to our website to upgrade a key. They receive an email that tells them how to upgrade a new system key through the setup program. The email does not tell them how to upgrade an existing key on the unity server. It also does not tell them how upgrade there TTS engine and it will not work right off the bat along with why there ports will not take effect immediately. Conditions: This is a documentation issue. It affects all versions of unity and the customer does not have to do anything except attempt to upgrade there license to run in to it.

Workaround

Right now there is no work around. We have been notifying the customers after a case has been created.

CSCdz13335

3

Syscheck make sure Unity install account belongs to build-int admin.

CSCdz13475

3

Fail to create new user; error Templates CallHandler not found. Symptom: Templates Call handler error appears when trying to created new Cisco Unity subscribers. Condition: Often when customers have difficulty creating Cisco Unity subscribers, the default mail user template is disassociated with the default subscriber call handler. The result is that the customer gets the following error when adding users: Templates CallHandler not found

Workaround

DBWalker 3.0.46 has an option to recreate the default templates. This option may be present in prior versions of DBWalker. To select this option, go to File > Recreate Subscriber Templates. By selecting this option, dbWalker will delete the {Default Subscriber} and {Default Administrator} subscriber templates and their corresponding primary call handlers and recreate them from scratch using the same construction script that the Unity setup uses during installation. This script does not create, remove or edit any other types of objects other than the two default subscriber templates and their primary call handlers.

CSCdz30363

3

Unity does not prevent deletion of call handler message recipients. Problem: When deleting a subscriber or distribution list, Unity makes no checks to verify that the deleted object is the message recipient for a call handler or interview handler. If it is, then CSCdx46851 is experienced.

Workaround

Once the object is deleted, the administrator should check the call handlers and interview handlers to verify that all message recipients are valid subscribers or distribution lists. Also, if deleting a subscriber object, the Global Subscriber Manager tool available in Tools Depot has an option to delete subscribers.

CSCdz32892

3

Unity setup does not reinstall/reregister missing services. Symptom: After an upgrade to 3.1.5, some functions of Unity may not operate properly. For example, text-to-speech doesn't work, messages from PSTN callers are never delivered, event notifications aren't working. Problem: The service responsible for that non-functioning feature is no longer registered. Unity attempts to reregister the service, but is unsuccessful and gives no reasons why. If text-to-speech isn't working, check to see if the AvTTSSvr service exists in the Services Administrative Tool. If messages from PSTN callers aren't being delivered, check for the presence of the AvUMRSyncSvr. If event notifications aren't working, look to see if AvGaenSvr is registered. The following app event log is a tell-tale sign this is what is happening: Event Type: Error Event Source: AvCsServices_MC Event Category: Error Event ID: 1093 Date: 11/15/2002 Time: 12:35:31 PM User: N/A Computer: EVOICE-UNITY4 Description: Gateway: Failed to open service [AvUMRSyncSvr] [hr = 0x00000424]. This will be displayed for each service that isn't registered.

Workaround

Manually reregistering the services restores functionality. Open a DOS prompt, move into the CommServer directory, and issue the following command (where <servicename> is the name of the service that has become unregistered). C:\CommServer> <servicename>.exe -service The command should return without any output. Check the Services Administrative Tool to verify the service is now registered and running.

CSCdz42117

3

Incoming integration will fail and MWIs will not activate/de-activate after following the Nortel Meridian1/PBXLink Integration Guide. The guide is missing some key programming. The PBXLink will show warnings like Failed to press display key and/or Failed to press MIK/MCK key. Incoming integration will not work even though the PBXLinks display shows correct information from the PBX. Additionally MWIs may fail to activate/deactivate even though Unity IntegrationMonitor.exe shows Unity sending SMDI MWI requests to the PBXLink.

Workaround

Add the following keys for the digital line that is set to take calls on the PBXLink:

12 DISP
13 MIK
14 MCK

These keys can be added in a similar fashion to the other keys listed in Digital Line Options table of the integration guide.

CSCdz50043

3

Faxing and email fails with Omtool 3.2.6 with Genifax E2K fax connector at one customer site.

There is currently no workaround.

CSCdz50684

3

Exchange 5.5 to 2000 Migration steps need to be documented. Symptom: Exchange 5.5 to Exchange 2000 migration fails. Condition: Failed Cisco Unity migrations from Exchange 5.5 to Exchange 2000 fail due to the lack of a documented process and expectations.

Workaround

The best known way at this time to migrate from Exchange 5.5 to Exchange 2000 if the Exchange 5.5 server remains in the environment with users on it is to use DiRT.

CSCdz51904

3

Conversation should not go to failsafe if ForwardToFax fails. Symptom: The customer tries to fax an email and immediately goes to failsafe. In the conversation, IAvDohMessage:ForwardToFax is failing in CAvSTwoCallFaxExit:GetForwardingMessage. This bubbles up to a failsafe Conditions: Unity 3.1(x) or beyond. Unity with FAX. Forwarding of FAX failing for some reason.

Workaround

None. This is a symptom of something wrong with the message store. Fixing that is important. Fixing this defect is not going to change the basic reason why the forward is failing.

CSCdz60254

3

The Event Notification Utility repeatedly notifies of errors until it is stopped and restarted.

Workaround

There is no workaround. A replacement for the ENU tool will be made available in the 4.0(3) timeframe.

CSCdz75004

3

Insufficient registry permissions prevents user creation. Problem: If the account that the AvDSGlobalCatalog service is running under does not have Full Control over the following registry key and its subkeys, new users cannot be added to the system. HKLM\SOFTWARE\Active Voice\Directory Connectors\DirSynchGlobalCatalog Symptoms: In Unity 3.1, before the new subscriber creation window comes up, the following error pop-ups appear: Illegal configuration: Server list cannot be empty in active directory configuration. Runtime Error has occurred. Do you wish to debug? Line 2030 Error: Servers GetServerByName (..) is null or not an object.

Workaround

Open Regedt32, highlight the registry key above, click Security > Permissions, and restore Full Control to the account that the AvDSGlobalCatalog service is running under.

CSCdz84934

3

Calls to subscribers from the operator forward to the opening greeting instead of the subscriber voice mail. This occurs when Cisco Unity is integrated with Nortel PBX via a PBXLink SMDI integration. Although this problem was discovered and worked around in Unity 3.1(4), it would apply to any version of Cisco Unity integrating with a Nortel phone system. Its also important in this scenario that the operator extension is 0.

Workaround

The solution to the problem is a change to the PBX Link Box using the following menu option: Configuration \ SMDI Option \ CPID Mask The CPID mask should be set to 10 zeros. Refresh it by typing 10 consecutive zeros and saving the change. This should re-initialize the placeholder and get rid of the blank spaces. This solution may require you to refresh the cpid mask twice. So if it does not work the first time, follow the above steps and do it a second time.

CSCdz87175

3

Exceeded mailbox limit conversation error should be reworded for cust use. Symptom: The following event log error is in the application log: AvConvMsg_MC Error 10002 IAvDohMessage:Submit returned [0x800404d9] on line 307 of file e:\views\cs_UE3.1.4.39\un_Core2 \ConversationEng\AvStateSvr\AvSMsgSend.cpp Running conversation PHGreeting on Port 2 Running conversation MessageEditing on Port 2 Conditions: This happens when Unity tries to submit a message to a mailbox that has exceeded its Exchange mailbox limit.

Workaround

There is no workaround for the Unity behavior. If Exchange is configured to log events when mailbox quotas are reached, then check the application log for those MSExchange events and deal with those mailboxes appropriately.

CSCdz88347

3

Full DB import gives ODBC SQL Server Driver error code -2147217833. Problem Description: When running the Full Database Import tool to import a backed up database into a 3.X server, the following error(s) may be encountered in the DBImport.LOG file: (error) Creation of Handler failed. Reason=[Microsoft][ODBC SQL Server Driver][SQL Server]tr_GlobalSubscriberUpdateDtmfNameUponNameUpdate, Code=-2147217833 sp_ImportCallHandler @Alias = Nch_ACME, @DisplayName = Nch_ACME, @AfterMessageAction = 2, @AfterMessageConversation = NPHTransfer, @EditMsg = -1, @IsPrimary = -1, @DtmfId = N4075551212, @MaxMsgLen = 300, @OneKeyDelay = 1500, @ScheduleObjectName = NAll Hours - All Days, @SendUrgentMsg = 2, @CreateContactRules = 1, @CreateMenuEntries = 1, @CreateMessagingRules = 1, @Undeletable = 0 Skipping Handler. **Starting record** Alias:ch_ACME Name:ch_ACME DTMF ID:5555551212 later on you will also get an error such as the following that is a direct result of the first problem: (error) Could not find Primary Call Handler object reference by ID:./03:cn=ch_ACME,cn=CallHandlers,cn=Handlers,cn=Unity,ou=VM_AC,o=MyOrg Removing mail user as a subscriber and skipping record. Alias=ACME Display Name=ACME Private Lists for this subscriber=0 When taking the first query above and plugging it into the SQL query analyzer we get more information: Server: Msg 248, Level 16, State 1, Procedure sp_ImportCallHandler, Line 67 The conversion of the nvarchar value 5555551212 overflowed an in the column. Maximum integer value exceeded. The statement has been terminated. What has happened is that the sp_ImportCallhandler sproc is casting DTMFaccessID into ints, which cannot be greater than 2147483647. Therefore any imported user with a DtmfAccessId greater than that number will fail the import. Condition: This occurs with the FullDbImport utility version 2.0.0.25 and lower.

Workaround

In the SA, delete the affected user and import them via the SA (not via the Import Tool). Greetings and spoken names should still be in the \commserver\streamfiles directory to reassociate with the user. If a large number of users will be affected by this, then a corrected SQL stored procedure should be obtained.

CSCdz88852

3

Outlook fails to publish the ViewMail form after the following sequence of events:

a. ViewMail is installed while antivirus software is enabled on the subscriber workstation, which causes the ViewMail installation to fail.

b. ViewMail is uninstalled by following the procedure in the tech tip Cisco Unity VMO Error: "The Custom Form Could Not Be Opened." (The tip is available on Cisco.com at http://www.cisco.com/warp/customer/788/AVVID/vmo_error_custom_form.html.)

c. Antivirus software is disabled on the subscriber workstation, and ViewMail is reinstalled.

Workaround

1. On the subscriber workstation, open Outlook.

2. On the Help menu, click About Microsoft Outlook. In the About Microsoft Outlook, dialog box, click Disabled Items. In the Disabled Items dialog box, select ViewMail and click Enable. Close the dialog box(es).

3. On the Tools menu, click Options. Click the Other tab, and click Advanced Options. In the Advanced Options dialog box, click Add-In Manager. Check the ViewMail Extensions check box, and click OK. Close the dialog box(es).

4. On the Tools menu, click Macro > Security. In the Security dialog box, click Medium and click OK. (Medium is the level recommended in the Security Notes for Microsoft Office Solution Developers article available on the Microsoft MSDN Library website.)

CSCdz88921

3

ExMon - Partial MAPI Notification outage breaks MWI. MWIs and Message Notification fail for a particular subscriber, and no MAPI table add or modified notifications are generated (Microtrace Exchange Monitor13) when a new message is left for the subscriber. Sometimes, delete notications are not generated for the subscriber, either. Conditions:Any Unity version; seen so far in Exchange 2000, but the possibility in Exchange 5.5 is unknown.

Workaround

Re-register the problem subscriber for MAPI notification with the following

procedure:

1. From Tools Depot, open Bulk Logout.

2. Find the problem subscriber by extension number, and press Log Out Subscriber. Then press Resynch Subscriber. This procedure can be done for many subscribers at once by adding each one to the list, then performing Log Out and Resynch for all of them. In Unity 3.1(5) and higher, all users can be re-registered at once by stoppingand starting the AvMsgStoreMonitor service.

Note: A problem subscriber can not be re-registered for MAPI notification by a simple MWI refresh from the SA.

CSCdz89148

3

TUI transfer to phone number does not work. Symptom: Automatic calls transfer don't work for the new phone number entered. Conditions: A user logs in to Cisco Unity using phone. The user goes to the user settings and select option 2 to enter the phone number, which should be called, Unity saves the phone number. And it plays the prompt - your calls will be transferred to this new phone number. When you check in the SA for that subscriber, the phone number is saved but not enabled.

Workaround

This is expected behavior. The change on the phone will not automatically enable the transfer option. It is available so that folks can change it when the feature is already enabled.

CSCdz89153

3

Unistall does not remove Unity.mdf file. Symptom: Unity setup fails and Unity database unityDb is not created. Conditions: If Cisco Unity was uninstalled. The doesn't clean up the database file Unity.mdf and Unity.ldf. When we run the setup again, then the SQL script fails to create the database, as the file with same name already exists. The error is logged in the SQL output file. There is no indication in the tempu.log. We get errors later, when we try to create Unity objects, as the database is missing.

Workaround

Delete the database file Unity.mdf and Unity.ldf from the SqlServer data directory. Run Cisco Unity Setup again.

CSCdz89697

3

LogMgr should tolerate/report problems with reg diag grid. Cisco Unity won't start. There is event log error 1025 from AvCsServices_MS about Component ResourceManager initialize failed. This can be caused by corruption in the registry diagnostic grid under HKLM | SOFTWARE | Active Voice | AvLogMgr | 1.0 | Diagnostic Grid. The primary known cause is from using the SA to change diagnostics. (See defect CSCdw48240.)

Workaround

Repair the registry diagnostic grid by either upgrading to the same version, manually adding the keys back to the registry based on a known good system, or using the .rgs files to refresh the diagnostic grid.

CSCea01229

3

Conv base logs 2 event logs for circular reference in handlers. We get AvConvMsg_MC error in the Event log. If a call handler is pointing to itself, then we log 2 event log errors (10020 and 10016) from AvConvMsg_MC. The second event log error message is for failsafe.

Workaround

1. RunDbwalker utility to find out the problem, and follow the link.

2. Find out the call handler from the event log. Make sure that in its after-greeting action, it is not pointing to itself.

CSCea19147

3

3.1(5)ES13 & 3.1(5)ES28 cause Miu Diags to be formatted wrong. Cisco Unity diagnostic logs may falsely state that the system is in inactive mode and not configured to answer calls. This condition may occur after 3.1(5)ES13 is applied.

Workaround

No workaround at this time, this issue is cosmetic and does not impact system performance, however it may be confusing when troubleshooting.

CSCea21699

3

Refresh of Application Event Viewer takes greater than 15 seconds. Symptom: A refresh of the application event viewer will take greater than 15 seconds. Conditions: This has been observed on a Unity 3.1.5 system, Voice Mail only and Exchange offbox.

Workaround

None Additional information: This is a Windows problem and is not specific to Unity.

CSCea22181

3

Import Subscriber screen shows wrong MailServer and MailStore Info. Symptom: When we import a exchange user through SA. SA doesn't show the correct user Mail Server and MailStore information. Conditions: This can occur where there are multiple exchange servers and Mail stores.

Workaround

This is because SA doesn't get those properties from the user object from AD. That's why it shows the first found Mail Server and Mail Store. This field is grayed out. This is just for information display. SA doesn't make any changes to that. This just a cosmetic defect. The imported subscriber should have correct MailServer and Mail Store information.

CSCea26526

3

If you unload a language from the TUI or GUI Language settings in the Cisco Unity Administrator, callers hear the failsafe conversation if either of these conditions exist:

The unloaded language was set as the default Cisco Unity language, and the operating system regional language was set to a language that is not supported on Cisco Unity.

Or

The unloaded language was explicitly set as the language to use, rather than the inherited language setting.

Workaround

Do not unload a TUI or GUI language that is set as the default Cisco Unity language, or one that is explicitly set as the language to use for a subscriber, call handler, or other Cisco Unity object.

CSCea35850

3

Unity RTP stream has inherent jitter. The playback of Cisco Unity system prompts and voice message sounds robotic to outside callers. The playback of Cisco Unity system prompts and voice message sounds robotic to outside callers but there is no such problem for inside callers from IP phone. Also, there is no problem on voice quality between IP phones and outside callers. The problem is between Cisco Unity and the voice gateway but not all voice gateways have this problem.

Workaround

The gateway loads with fix for this DDTS are D004030145S1 (6608) and A002030139S1 (6624). These loads are available as part of the following Cisco CallManager Engineering Specials. For 3.1 - Available for 3.1 releases. For 3.2 - 3.2(2c)SpD This can be done on IOS MGCP gateways with this command mgcp playout adaptive 60 40 200 and on H323 IOS gateways with the playout-delay commands.

CSCea36275

3

More descriptive failure message for COS licenses > available. A more descriptive failure message is required where COS licenses used exceed those available: Could not create the object because no more licenses were available is not descriptive enough. An alternative has been suggested: Could not create the object because no more VMO licenses were available. COS assigned to <object template> includes VMO licensing.

CSCea39776

3

Documentation should tell users to use First Time Enrollment first. First Time Enrollment can be frustrating if you are trying to follow along in the users guide. New subscribers should simply call in to Unity for the first time and walk through the First Time Enrollment tutorial, and only refer to the user guides or quick reference guides once they have completed First Time Enrollment.

CSCea40009

3

CAvPhrasServerMgr:CreatePhraseServerSU - error in event viewer. Every voice message left for a subscriber generates an error in the event log stating ENG, British English isn't found. Event Type: Error Event Source: AvPhraseServer_MC Event Category: Error Event ID: 10025 Date: 2/24/2003 Time: 10:24:42 PM User: N/A Computer: UNITY Description: CAvPhraseServerMgr:CreatePhraseServerSU - The language defined as ENG is not loaded.

Workaround

Add the following registry setting: HKLM\Software\Active Voice\CDE\1.0\RetryDefaultLanguage = 1 <DWORD Value>

CSCea44038

3

SQL replication fails from secondary to primary in Unity failover. This DDTS tracks a Microsoft SQL defect (Microsoft Bug #364345). The SQL defect will affect Unity with failover in the following scenario: Microsoft security patch MS02-061 (SQL Slammer security patch) is applied to SQL Server 2000, where there is replication between a primary (publisher) server and secondary (subscriber) server. The effect of the defect is to break replication from the secondary to the primary server. Specifically, the queue reader will show errors.

CSCea46593

3

MSM doesn't update Admin quotas.

CSCea53153

3

When subscribers address a message (add names) using Message Options Menu via Telephone User Interface (TUI), pressing # at the address searcher prompt removes the addresses from the list. This defect exists in Cisco Unity 3.x and 4.x.

Workaround

Press * instead of #. Pressing * will not remove the names added in the Message Options Menu.

CSCea54995

3

When a subscriber sends a message via Telephone User Interface (TUI), the message can be sent in a future time if specified. However, cancelling the future delivery option and sending the message still sends the message in the specified future time, which should have been cancelled. This defect exists in Cisco Unity 3.x and 4.x.

Workaround

Cancel the message and try sending a new message without setting the future

delivery. Defect will be resolved in Unity 4.0(3).

CSCea63941

3

Cannot address messages to Ex55 subscriber that doesn't have a SMTP add. Symptom: Unity 3.1.5 installation integrated with an existing exchange 5.5 server. If Unity imports an existing Exchange 5.5 user which doesn't contain a SMTP address, Unity subscribers will not be able to send a message to these subscribers. When attempting to send a message to a subscriber with a missing SMTP address, Unity gives the following error. sorry, this recipients mailbox does not exist. Conditions: Unity 3.x with an Exchange 5.5 integration

Workaround

Open the SQL subscriber table and replace the <null> with a space for the subscribers without an SMTP address. To change all subscribers at once, run the following SQL command: UPDATE Subscriber SET SmtpAddress = WHERE SmtpAddress IS NULL Further Problem Description: Unity does not need to check for the presence of the smtpAddress if the Unity system is E55 connected.

CSCea65603

3

Nortel Meridian 1/PBXLink Integration Document has error. A portion of the document: Nortel Meridian 1/PBXLink Integration Guide contains incorrect statements about how analog lines on the meridian should be configured for integration with Cisco Unity. The portion in error can be found on page 22 of the document. The document in whole can be found here: http://www.cisco.com/application/pdf/en/us/guest/products/ps4774/c1069/ccmigration_09186a00800889bc.pdf

Page 22 contains this table:
Table 1-5 Analog Voice Messaging Line Options
Option Setting
CDEN SD (if QPC60)
DD (if QPC452)
4D (if QPC594)
CUST <customer data block>
DN <the extension number for the port being set>
HUNT <the next line after the port being set>
CLS HTA FBD DTN SFA FND MWD LDTA

The last line of this table contains the incorrect entry. The last line should read like this:

CLS HTA FBD DTN XFA FND MWD LDTA

So that SFA (secondary forward allowed) is replaced with XFA(transfer allowed). If SFA is used, transferred calls will fail with a busy signal.

Workaround

Change SFA to XFA on the analog line that is interfacing to Cisco Unity.

CSCea67183

3

When a subscriber replies to a message via Telephone User Interface (TUI), if the call is disconnected before the subscriber confirms to send the reply message, the reply message is still sent. The problem happens even though the Subscriber Send Message Hang-Up action setting is configured so that Cisco Unity discards the message when the call gets disconnected before the subscriber confirms to send it.

The problem happens only if the call is disconnected while Cisco Unity is playing the invalid selection prompt: "Sorry. That is not a valid selection. Please try again."

Workaround

There is currently no workaround.

CSCea69184

3

MCS7847 Hewlett-Packard install image does not install IIS help files. Symptom: The following messages are seen in the System Event Viewer: Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 30 Date: 4/7/2003 Time: 10:16:03 AM User: N/A Computer: UNITY-FL1 Description: The server was unable to read the file C:\WINNT\help\iisHelp\common\401-1.htm. The file does not exist. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp. Conditions: This has been observed when using the Cisco Unity Platform Configuration Discs Rev 12.

Workaround

The files can be copied from another server or installed from the W2K CD.

CSCea69272

3

When trying to access Unity's VMI on a machine that has Sun's Java RunTime Environment (JRE) or Java Development SDK (which includes the JRE) installed, users will not be able to log in. The error displayed after entering credentials is:

Error: A RunTime Error has occurred. Do you wish to Debug?
Line: 27
Error: Object doesn't support this property or method.

After pressing Yes/No in the dialog box, the browser is left blank except for the Cisco Unity Banner.

Workaround

The following workarounds are available:

1. This problem does not exist in Unity version 4.0(1) and higher. Upgrade to 4.0(x).

2. For VMI to work properly when a JRE is installed, the Java Plug-in must be disabled. To do this, open the Java Plug-in options from Control Panel. Go to the Browser tab and uncheck Internet Explorer. Click Apply and then restart the browser. This should disable the Java Plug-in and make VMI work again.

3. User can uninstall the JRE version from that PC.Using Control Panel add/remove program options may not properly uninstall the JRE. You should rerun the JRE install program. The install program will see that the program is already installed and will give the option to uninstall. Select 'Yes' to uninstall.

CSCea69856

3

SA erroneously prompts for reboot when setting nightly mwi resynch. When setting the ability to have MWI resynched nightly the following pop-up message is displayed when the switch configuration is saved:
Changes will take effect only if you restart Unity Do you still want to save?

This happens when saving the changes to Resynch All Message Waiting Indicators is done in the SA This is an issue in Cisco Unity 3.x, but not in Cisco Unity 4.x

Workaround

The message indicating the reboot is not correct. The change takes affect without a reboot.

CSCea70229

3

Statusmonitor.exe crashes. Symptom: The following entry is seen in the Application event log: Event Type: Information Event Source: DrWatson Event Category: None Event ID: 4097 Date: 4/2/2003 Time: 9:59:39 AM User: N/A Computer: VM-FLORIDA1 Description: The application, StatusMonitor.exe, generated an application error The error occurred on 04/02/2003 @ 08:59:39.483 The exception generated was c0000005 at address 00402385 (<nosymbols>) Condition: This has been observed in Unity version 3.1.5.

Workaround

None

CSCea71798

3

MSD fails when there is a comma in the org name. When using the Migrate Subscriber Data tool (MSD 1.1.63), the exmerge process will fail to access the correct directory object name if a name contains a comma (,) in it. For example:
/O=Cisco Systems, Inc.

will be interpreted as:
/ Inc. /O=Cisco Systems

This only affects Exchange sites that use a comma (,) in any of the name fields (organization or site).
/O=Cisco Systems, Inc. - would be affected
/O=Cisco Systems Inc. - would not be affected

Workaround

None

CSCea71906

3

DAD needs to output a log file during user creation test. Directory Access Diagnostics (DAD) does not generate a log file during a User Creation Tests and make it difficult to troubleshoot where the failure occurred. If running DAD the user creation process fails, it is hard to determine where the failure occurred. For example, if DAD was unable to create a Test user but SAWeb could, it is hard to compare the two process without a detailed log file.

Workaround

None

CSCea71951

3

Optional Conversation: 33 does not fast forward to end of message. Problem: When using the Optional Conversation with Unity, hitting 3 3 while listening to TTS read email does not fast forward to the end of the message. This functionality works when listening to voice mail.

Workaround

Press the # sign instead to fast forward to the end of email.

CSCea72616

3

Attempts to access VMI are unsuccessful. Attempts receive the following error:

Internet Explorer [warning]
Problems with this Web page might prevent it from being displayed properly or functioning properly. In the future, you can display this message by double-clicking the warning icon displayed in the status bar. [OK]
Line: 648
Char: 4
Error: 'pageFlipper' is undefined
Code: 0
URL: http://<servername>/web/vmi/LocalizationFiles/ENU/inbox.stm

Clicking on OK minimizes the error window, but the browser shows a blank page. VMI does not load.

Another message that can pop up when attempting to access VMI are the following:

Install on Demand (Other)
To display this page correctly, you need to download and install the following components:
Java virtual machine
[Download] [Cancel]

If you chose Download, the system may hang and the Install on Demand wizard advises that Virtual machine did not install properly.

The errors occur with Unity 3.1.x when the client has EOM provided version of Internet Explorer 6.0 SP1. Client computer opens IE and attempts to enter the default VMI URL: http://<servername>/web/vmi.

Further Problem Description:

EOM versions of Internet Explorer 6.0 SP1 no longer have Microsoft Virtual Machine installed. VMI requires Java/Microsoft Virtual Machine be installed. This only affects 'new' installations of IE 6.0 SP1 or later. This is typical with new (EOM) client workstations with the OS and IE already installed.

Upgrading IE from older versions of IE will not uninstall Java/Microsoft VM. These clients are not affected.

Workaround

1) This problem does not exist in Unity server 4.0(1) or higher. Upgrade to 4.0(x).

2) Install IE 6.0 SP1 from Unity Installation CD pack. This version contains IE version that will install the Java/Microsoft Virtual Machine.

3) Download Java virtual machine using Microsoft's 'Install on Demand' utility.

CSCea72723

3

Forwarding information not cleared after leaving a voice message. Symptom: After leaving a message for a Subscriber, the caller is not able to get to the Opening Greeting. Instead, after certain DTMF sequences, the call is transferred back to the subscriber. Condition: When the following sequence is used the call will be transferred back to the Subscriber instead of going to the Opening Greeting. - Call into a Subscriber - Leave a message and hit # - Hit # again to send the message - Hit * to go to Sign-in - Log into the mailbox that the message was left for - Hit * during the message count greeting Call is transferred back to the subscriber This sequence will send the call to the Opening Greeting as expected. - Call into a Subscriber - Hit * during the greeting to go to Sign-in - Log into that mailbox - Hit * during the message count greeting Call is sent to the Opening Greeting

Workaround

None

CSCea73252

3

Unavailable port stalls MWI on other clusters. Observed with Unity 4.0.2 / TSP 7.0.2 (will be present in earlier versions). When integrating multiple Cisco CallManager clusters to one Cisco Unity system, if one of the Cisco CallManager clusters becomes unreachable (WAN failure, Cisco Callmanager outage, etc.), MWI notifications may be affected on the Cisco CallManager clusters that are still registered normally with Cisco Unity. In the Application Event Log many of the following warnings will be present:
Event Type: Warning
Event Source: CiscoUnity_Miu
Event Category: Warning
Event ID: 526
Date: 4/10/2003
Time: 3:18:21 PM
User: N/A
Computer: ClusterB-CCM1
Description:
Cisco Unity had a problem while attempting to toggle an MWI. This can happen occasionally as part of normal operation, and the MWI request will be retried. If the MWI status remains unchanged for extended periods of time, or if there are many of these warnings from Cisco Unity in a short period of time, there may be an MWI misconfiguration or other problem. See the MWI section in the troubleshooting guide, and contact TAC for assistance if needed.

Workaround

If the Cisco CallManager site is going to be down for a while, it may make sense to remove or to at least disable MWI on the Cisco Unity ports going to that cluster. If this step is performed, errors (Cisco Unity_Notifier, Event ID: 1041, no suitable port) will appear in the Applications log, but Cisco Unity will immediately try Cluster A. Once Cluster B is available again, the ports would need to be reconfigured for MWI notification again.

CSCea77084

3

JPN: Outlook folder names in Eng for subscribers created in Unity. Symptom: In Cisco Unity for Exchange 3.1(5) and 4.0(2), Microsoft Outlook folder names are shown in English if the subscriber is created in Cisco Unity System Administration (SA). When creating a user in Active Directory and importing the user in SA, the folder names are shown in Japanese. This defect exists in Cisco Unity 3.1(5) and 4.0(2) JPN.

Workaround

No workaround.

CSCea79126

3

Message length does not correspond to COS. Symptoms: Default Subscriber COS greeting length was changed from 90 seconds to 250 seconds. Customer built a subscriber and used the Default subscriber COS. Then, the customer recorded a 200 second recording and saved it. When the customer played it back and it only kept/played 90 seconds worth Conditions: Many of the settings for subscribers in the SA, follows the class of service of the administrator that was logged onto the SA to make changes in subscribers COS. If the COS of the Administrator that was logged onto the SA to make a change in the COS of a bunch of subscribers, had a specific value for the greeting length, the effective greeting length in the COS for the subscribers that this Administrator modified can only be lower or equal to that specific value that this Administrator has in his/her COS. Greeting length value in COS for Administrator making changes to subscribers COS > or = Greeting length value in modified subscriber COS.

Workaround

Increase the COS greeting length for the Administrator up to the value that you want your subscriber COS, then change the subscriber COS, and finally, change the Administrator COS as you wish.

CSCea81348

3

Location should not be announced if msg sender from same Dial Domain. Description: When a Unity Subscriber retrieves a voice message sent from a Subscriber on another Unity node within the same dialing domain, the sending Subscribers recorded name and Location is announced. Expected functionality is for only the Subscribers recorded name to be announced. Condition: This is reproducible with Cisco Unity version 3.1(5) with Digital Networking active on multiple Unity servers in the same dialing domain.

Workaround

Two system prompts may be edited to remove the conversation phrases heard after the subscribers name is announced. NOTE: Modifying system prompts on a Unity system will not create a permanent change to the conversation. If the Unity system is upgraded, customized system prompts WILL BE OVERWRITTEN. The change below will affect any subscriber that may be associated to a Location (i.e., AMIS, Internet Subscribers, etc.). This change is intended for Unity systems where only the Digital Networking feature is used. The conversation prompts heard before this change are: Message <x> sent from <Subscriber> at <Location> The conversation prompts heard after this change are: Message <x> sent from <Subscriber> The at prompt is found in the.\commserver\Localize\Prompts\ENU\AvSubMsgPlay directory. Make a copy of the file AvSubMsgPlayENU020.wav and name it AvSubMsgPlayENU020.bak. Copy in a file of the same name AvSubMsgPlayENU020.wav that contains only silence. The Digital Networking Location names should also be modified by recording a blank name for the location.

CSCea84262

3

SA empty domain list when selecting Exchange user to import. The following problem has been seen when using the SA in Unity 3.1.3 SR1 ES 5.

Go through the steps in the SA to import an Exchange user. When you hit the Select button, the resulting page has a blank Domain drop-down box.

Workaround

Restart the IIS Admin service, and start the SA again. This has been shown to clear up this problem.

CSCea84577

3

SAWeb will not load with Inoculan Anti-virus. Symptom: When running Inoculate Anti-virus software in Unity, SAWeb will not launch properly. A web browser will show up but with a blank page and messages to hit refresh within the web page. Hitting it multiple times will get to the correct page Conditions: Found in Unity 3.1.5 Deleting cache and restarting IIS do not solve the issue. This is also related to Microsoft Knowledge base 302424.

Workaround

Disable the Inoculan Anti-virus by launching it from the menu. Go to Scanner and Services option and stop the 3 services. Further Problem Description: Our documentation listed Inoculan as one of the supported third party software

CSCeb04758

3

TUI should prevent user from setting blank contact rule extension. Symptom: A contact rule unexpectedly behaves like its disabled. Conditions: Log in to the TUI, press 4 for settings, press 1 for greetings and transfer settings, press 2 for transfer settings, press 2 to change the extension, hear enter the extension then press #, enter no extension, press #. The contact rule extension is now blank; it is in SQL, not NULL. The contact rule will behave like its disabled.

Workaround

Follow the TUI flow above; then enter a valid extension and press #. Further Problem Description: This is mostly a UI issue. There is currently no way to change the contact rule extension via the TUI. It can only be changed through the graphical tools such as the SA, PCA, etc.

CSCeb04769

3

Need supported languages in Unity Release Notes to be more clear. Symptom: Unity Release Notes for 3.1.5 mentions support for Brazilian Portuguese (PTG). The release notes for 4.x do not mention support for PTG. Customer are lead to believe that this isn't supported.

Workaround

We need to add a matrix to the Unity release notes.


Resolved Caveats—Release 3.1(6)

Table 8 Cisco Unity Release 3.1(6) Resolved Caveats 

Caveat Number
Severity
Description

CSCdu37182

2

MALEx_MC: Error while trying to logon to MAPI mailbox

CSCdu74580

3

Number of passwords to remember does not work

CSCdv06740

3

Setup fails, doesn't report problem that IIS cant be stopped

CSCdv24303

2

Symantec pcAnywhere & Multi-way Server Kernel Stoppage

CSCdv67065

4

In Cisco Unity Administrator, on the Subscribers > Messages page, the subscriber Total mailbox size (Kb) always has Unavailable as its value.

Workaround

The Total mailbox size field was removed from the Cisco Unity Administrator.

To view the total mailbox size for a subscriber, use the Message Store Manager utility, available in Tools Depot.

CSCdv77509

2

JPN: Upgrade failed with corrupted msg while copying file

CSCdw04464

2

Cant import a user from Exchange with in first or last name

CSCdw41728

2

AvCsGateway pointer error causes login errors when accessing SA/SM

CSCdw45334

3

ML: Timeout waiting for AvCsMgr to start

CSCdw59188

3

Unity SA does not use the fqdn of the machine when selecting users

CSCdx03853

2

imported Internet Subscribers receive failsafe AVP_MAIL_SERVER fails

CSCdx10818

3

Optional conv: Failsafe when pressing ## after playback of saved msg

CSCdx14296

3

When viewing the Properties for the Exchange 2000 Voice Connector in the Exchange 2000 System Administrator, the following message is displayed: The Connector could not be found on this machine and is using the registry for storing it's configuration data. Reading configuration data from a remote registry is not supported by this Voice snap-in.

This behavior may occur on Exchange 2000 servers on which the Unity Exchange2000 Voice Connector has been installed where the Microsoft Windows Script Host version is earlier than version 5.6. Use the following procedure to confirm the version number.

To determine the installed version of Microsoft Windows Script Host file

1. Browse to \Winnt\System32 on the Exchange server.

2. Right-click wshom.ocx file.

3. Click the Version tab.

4. Click Product Version. The file version is displayed in the Value box.

Workaround

Install the latest version of Microsoft Windows Script Host from the Microsoft Product Support web site.

CSCdx15372

3

Changing port assignment on ports page should prompt to reboot

CSCdx29139

2

MWIs don't work in failover when mailboxes are moved

CSCdx43466

2

Synchronization of MWIs stops without logging errors. This can happen if unexpected UDP packets are being sent to the Cisco Unity server. The MAPI notification mechanism that is listening for UDP packets can stop if it gets unexpected data.

Workaround

1. Restart the Unity server.

2. Install one of the following:

For Exchange 2000 systems, see Microsoft KB article XCCC: MAPI Thread That Is Monitoring the New Mail Notification Quits (Q329024).

For Exchange 5.5 systems, see KB article XCCC: MAPI Thread That Is Monitoring the New Mail Notification Quits When It Receives a UDP Packet (Q329415).

CSCdx45571

3

FO: Incoming call during failback causes failover

CSCdx45850

3

File replication stops if directory structure is modified

CSCdx52339

2

After Cisco Unity unexpectedly stops, starting Cisco Unity again by using the tray icon results in a blue-screen error.

Workaround

Restart the Cisco Unity server.

CSCdx62296

2

Codec:72port IP nominal load crashes while using transcoding

CSCdx76064

3

Transfers do not work from Cisco Unity after the Quiet50.prm file was added.

Workaround

Use the revised text below for Step 10, "Resetting the Intel Dialogic Quiet Parameter", in Appendix A of the Cisco Unity Installation Guide.

10. In the Value box, enter the values that you recorded in Step 9 of the procedure, "To determine the current setting for the Intel Dialogic quiet parameter," page A-16, in the format quiet<XX>.prm (where XX = the -dBm level of the desired quiet parameter file. The default setting is 50.) If spandti.prm or any other values existed in the box, re-enter each value followed by a space, then enter quiet<XX>.prm as the last value in the box.

CSCdx77631

2

SA Subs page times out in large system during wildcard Find

CSCdx82421

3

Failover event logging is not clear

CSCdx83741

2

Caller hanging up while Unity blind transferring call locks up Port

CSCdy01456

3

SA shows locked account as unlocked

CSCdy11225

3

Undescriptive error during upgrade: Value is not a valid enumeration

CSCdy14076

3

SA reports that E2K server without a mailstore is an invalid config

CSCdy28293

3

Syncher doesn't sync mailstores when running a full directory sync

CSCdy29087

3

One language disappears from the SA web admin page

CSCdy32442

3

AvDSAD - Unchecked ADSI API call causes access violation

CSCdy41298

3

Not possible to change After message action

CSCdy47698

3

No way to enforce installation of Ex2k SP2 during upgrade

CSCdy49079

3

AvRepMgr event 20004 is not useful to customer

CSCdy49126

2

AvTTSSvr with RealSpeak leaks about 2 MB per session/hour under load

CSCdy50682

2

After CCM failover, MWI notification may fail from Unity

CSCdy50887

3

TTS: Skipping ahead at the end of an email can lock a port

CSCdy52075

3

HKLM\Software\Active Voice\AvWm\1.0\Diag Level should default to 0.

CSCdy56599

3

Perfmon counters not available through WTS

CSCdy58840

2

Corrupt routing rules prevent unity from starting on arbiter init

CSCdy68149

3

SA: additional screens that break with quote in username

CSCdy68405

3

D240 message notification may cause port lockup

CSCdy69100

3

AMIS-Delay after processing packets s/b before processing

CSCdy69646

2

ISM does not get disabled

CSCdy75591

3

UnityConfig - UnityConfig on E2K displays incorrect mailstore names

CSCdy75857

2

Default config fails if there is a space in the SQL scripts path

CSCdy84566

3

RealSpeak TTS messages not read if user set to English(Australian)

CSCdy84583

2

SQL replication is not working after an upgrade

CSCdy85300

2

Restriction tables allow long-distance calls

CSCdy85651

3

Extension remapping doesn't handle wildcards properly

CSCdy86430

2

AMIS-message delivery from UAmis mailbox sometimes never attempted

CSCdy86917

3

Event Notification Utility(ENU) gives false alarms continuously

CSCdz03031

3

EAdmin display name should not say DO NOT DELETE

CSCdz03192

3

Cannot import adofre15.reg error during Unity installation

CSCdz07585

2

unity does not start on secondary when DNS name is used

CSCdz08719

2

Failsafe in optional conversations when hitting 1 or 3 after message

CSCdz13517

2

2nd part of setup will not run if AD container for subscr. deleted

CSCdz15442

1

ACM thread safety is disabled in Unity 3.1.5

CSCdz17817

3

Display error message when adding/importing user relevant to DSAD

CSCdz19695

3

Record Termination Warning is not set properly by Adv Settings Tool

CSCdz20116

2

Number pattern order makes default restriction table ineffective

CSCdz24111

3

Unity should better handle WAVs with bad RIFF header section lengths

CSCdz24696

3

Opt Conv - Pressing 5 during msg play does not play summary

CSCdz27593

3

MWI requests are not getting pushed onto the Notifier Queue

CSCdz30359

3

Need event log warning if message is discarded due to Record Min. Len

CSCdz31029

3

Unity fails to start after uninstalling Dialogic software. The following error appears in the System Event log: The AvCsMgr service depends on the following nonexistent service: Dialogic.

Workaround

1. Start Regedt32.


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. Go to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\AvCsMgr.

4. Edit the multi-string value DependOnService.

5. Remove Dialogic from the data list.

6. Restart the Cisco Unity server.

CSCdz34890

3

Reply not always offered by conversation when using blind addressing

CSCdz38060

3

Using Alternate Conversation, short cut to deleting messages fails.

CSCdz39077

2

Cannot import Distribution Lists from Ex5.5 into Unity

CSCdz46426

3

Code is not diagnosing 3rd party call failure HRESULTS

CSCdz48747

2

Port hung with AvTTS_MC 1016 WavOutPlay WavOutClose app log error

CSCdz53581

3

Error Exchange Server version is not version 6.0.

CSCdz54589

3

Unity fails to start if Rule Index in SQL table is out of order

CSCdz55952

3

Unable to import DL into Cisco Unity when org name contains & symbol

CSCdz58781

2

ENU not triggering on eventlogs

CSCdz62822

1

Bridge-any vcard received with END in FN string halts processing

CSCdz69110

3

Misconfigured DNS causes exception in MSCW (configuration setup)

CSCdz72630

3

LearnTones isn't correctly saving cadence tones

CSCdz75891

3

Optional Conv: Confirm delete does not delete the message

CSCdz87445

3

Disaster Recovery Tool (DiRT): Alias field in SQL Server 2000 Servers table not updated so upgrade fails

CSCea04029

2

Conversation fails to find language when building phrase

CSCea04111

3

FixDefaultObject.sql script does not update existing MUTemplates

CSCea05124

2

LogMgr & other services fail to initialize if root path has a space

CSCea07024

3

SA: Failed extension change still updates contactrule table in error

CSCea07029

3

SA: xferstring is not updated when dtfmaccessid is changed in the SA

CSCea08124

2

Miu timing errors with SerialAutoAnswer/WaitIfBufferedPacketPresent

CSCea10916

2

Script error in SubsAddPropBody.asp when importing Exchange user

CSCea12285

3

Subscriber deletes leave orphaned alternate extensions on remote sys

CSCea17551

2

Disaster Recovery Tool (DiRT): Upgrades to newer builds fail if the server has been restored

CSCea18998

3

Message Notification to work phone can cause failover to occur.

CSCea21395

3

G729 prompts for self-enrollment were not rebranded

CSCea21398

3

Stop recording option under Configuration in SA ambiguous

CSCea23843

3

Conv goes to failsafe, if it gets a NDR with recipient not set properly.

CSCea24153

3

LDAP syncronization warnings too generic for failed components

CSCea36241

3

Default database shouldn't include VMO & VMI in default COS objects

CSCea36770

3

Open enrollment does not prompt for # key at recorded name

CSCea36804

2

SA: User import search w/ Ex5.5 doesn't show contacts

CSCea37488

3

Analog MWI integration not working w/Avaya Gx PBXLink

CSCea38735

2

DirChangeWriter doesn't create alternate DTMF IDs

CSCea43499

3

Duplicate entries in Global Subscriber table in move scenario

CSCea46565

1

Running the Storage Usage report can crash Unity

CSCea52818

2

SA:Cannot add Subscribers via SA--Servers.GetServerByName exception

CSCea58120

3

LnH TTS locks Unity port during TTS playback

CSCea65997

2

JPN: VBScript error when opening Call Handlers Messages screen

CSCea69906

2

Unity hangs on startup if space in install path

CSCea91085

2

Setup:Part2, Selecting diff. acct. produces NTDOM for domain name


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.

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.

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

Do not use the instructions for backing up and restoring Cisco Unity in the Cisco Unity System Administration Guide and in the Cisco Unity Troubleshooting Guide. Instead, use White Paper: Backing Up and Restoring a Cisco Unity System, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_technical_reference_list.html.

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.


Subscriber Total Mailbox Size: Cisco Unity System Administration Guide

In Cisco Unity Administrator, on the Subscribers > Messages page, the Total mailbox size field was removed. To view the total mailbox size for a subscriber, use the Message Store Manager utility, available in Tools Depot.

Switch File Location: Cisco Unity Troubleshooting Guide

Before making edits to a switch file it is often recommended to create a backup copy of that file. A problem occurs when the backup copy is created with the following conditions:

The backup file is in the IntLib folder.

An .ini file extension is used.

None of the four identity fields (SwitchManufacturer, SwitchModel, SwitchSoftwareVersion, IntegrationType) were modified

When the conditions exist, selecting a switch via the Cisco Unity Administrator will not allow a choice between the edited copy and the backup copy of the switch file.

This problem can be avoided by doing one of the following:

Place backup files in a separate folder.

Use an alternate file extension on backup files, such as *.bak or *.org.

Modify one or more of the identity fields in the edited file to indicate that it has been customized.

In addition to using one of the above steps to prevent this problem, confirm that Cisco Unity loads the expected switch file whenever changes are made to the file. The loaded switch file can be verified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\MIU\1.0\Initialization\SwitchX\Switch Configuration File.

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 Guide

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 guide. See the "Moving Cisco Unity Messaging System, UAmis, and UOmni Exchange Mailboxes" section of these release notes.

Multiple Languages: Cisco Unity System Administration Guide

One of the languages installed on the Cisco Unity server must match the Windows operating system language (U.S. English, French, German, or Japanese.) Other languages may be installed as needed.

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

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.


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/en/US/products/sw/voicesw/ps2237/products_maintenance_guide_book09186a0080098ac9.html.

At the website http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Software:Unity

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


Note 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/en/US/partner/products/sw/voicesw/ps2237/prod_technical_documentation.htm.


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/order/apollo/configureHome.html. The part number is UNITY-10USR-2DEMO.

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.

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, the Cisco CallManager 3.2 Integration Guide, or the Cisco CallManager 3.3 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 Circuit-Switched 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 Refer to applicable task list in the "Upgrading a Cisco Unity 3.0 or 3.1 System" chapter of the Cisco Unity Installation Guide, Release 3.1. The guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_guides_books_list.html.


Cisco Unity Documentation

For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to About Cisco Unity Documentation. The document is shipped with Cisco Unity and is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/about/aboutdoc.htm.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

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

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

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

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

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

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

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

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

Cisco TAC Website

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

http://www.cisco.com/tac

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

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

Opening a TAC Case

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

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

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

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

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

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

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

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

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

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

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

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

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

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

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

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

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

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

http://www.ciscopress.com

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

http://www.cisco.com/packet

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

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

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

http://www.cisco.com/ipj

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

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