Guest

Cisco Unity

Release Notes for Cisco Unity Release 4.0(2)

 Feedback

Table Of Contents

Release Notes for Cisco Unity Release 4.0(2)

Contents

System Requirements, and Supported Hardware and Software

Compatibility Matrixes

Hewlett-Packard Service Pack for ProLiant DL380 G2 Server

Determining the Software Version

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector for Microsoft Exchange

G.729a Audio Codec

RealSpeak Engine

Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging

Downloading Software for Cisco Unity 4.0(2)

Downloading CD Images of Cisco Unity 4.0(2)

Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

Task List for Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

Upgrading and Configuring the Cisco Unity Software

Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

New and Changed Support—Release 4.0(2)

Cisco Unity Tools Depot

IBM Lotus Notes 5.0.11 Supported on a Cisco Unity with Domino Server

Phone System Integrations Qualified for Use with Cisco Unity

Software Qualified for Use on Cisco Unity Subscriber Workstations

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

Third-Party Fax Integrations Supported with Cisco Unity with IBM Lotus Domino

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

Windows Automatic Update Supported

New and Changed Functionality—Release 4.0(2)

Cisco Personal Communications Assistant Help

Cisco Unity Bulk Import Wizard

Cisco Unity Greetings Administrator

Cisco Unity Installation and Configuration Assistant

Cisco Unity with Exchange: Active Directory Contacts Deleted When Associated External Subscribers Are Deleted

Cisco Unity with Exchange: Disabling the Automatic Directory Synchronization of Bridge Subscribers

Customizing the Subscriber Conversation: Changing How Subscribers Confirm Message Addressing

Support for Copies of Configuration Files for Circuit-Switched Phone Systems

Installation and Upgrade Notes

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

Cisco Unity Phone Conversation System Prompts

Cisco Unity with Exchange: ViewMail for Microsoft Outlook No Longer Controlled by Class of Service

Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter

Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported

Using Japanese and Mainland Mandarin Text to Speech

Limitations and Restrictions

Cisco Unity Bulk Import Wizard

Digital Networking

Call Transfer Settings Unavailable

Message Sender Is Unknown and Message Recipient Cannot Reply

Dual NICs

Replacing Disks in a RAID

Cisco Unity with Exchange: 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 4.0(2)

Resolved Caveats—Release 4.0(2)

Documentation Updates

Errors

Obtaining License Files for Additional Features: Cisco Unity Installation Guide

Changes

Creating an Integration for a Circuit-Switched Phone System: Cisco Unity Integration Guides

Omissions

Determining the Cause of Failover or Failback: Cisco Unity Failover Configuration and Administration Guide

Viewing License Pooling Information: Cisco Unity System Administration Guide

Troubleshooting

Installing a Cisco Unity Demonstration System

Limits on a Cisco Unity Demonstration System

Default License File

Time-Limited License File

Enabling a Cisco Unity Demonstration System with the Default License File

Enabling a Cisco Unity Demonstration System with the Time-Limited License File

Converting a Cisco Unity Demonstration System to a Standard System

Cisco Unity Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Release Notes for Cisco Unity Release 4.0(2)


Revised June 26, 2003

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 4.0(2).

The latest software upgrades for Cisco Unity 4.0 are available on the Cisco Unity 4.0 Software Download page at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-40.


Note Confirm that you have the latest software version available and that you are using the corresponding version of the Cisco Unity Installation Guide. The guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


Contents

These release notes contain the following sections:

System Requirements, and Supported Hardware and Software

Determining the Software Version

Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

Downloading Software for Cisco Unity 4.0(2)

Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

New and Changed Support—Release 4.0(2)

New and Changed Functionality—Release 4.0(2)

Installation and Upgrade Notes

Limitations and Restrictions

Caveats

Documentation Updates

Troubleshooting

Installing a Cisco Unity Demonstration System

Cisco Unity Documentation

Obtaining Documentation

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 4.0 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 Service Pack for ProLiant DL380 G2 Server

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

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 for Microsoft Exchange

G.729a Audio Codec

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.


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


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.


Cisco Unity-CM TSP

To determine the Cisco Unity-CM TSP version in use by using the Cisco Unity Telephony Integration Manager


Step 1 Double-click the Cisco Unity Tools Depot icon on the desktop.

Step 2 Under Switch Integration Tools, double-click Telephony Integration Manager.

Step 3 In the Cisco Unity Telephony Integration Manager, go to the Cisco CallManager > Properties page. The Cisco Unity-CM TSP version is displayed in the TSP Version field.


To determine the Cisco Unity-CM TSP version in use by using the AvSkinny.tsp file


Step 1 Browse to the WinNT\System32 directory.

Step 2 Right-click AvSkinny.tsp, 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-CM TSP version is displayed in the Value window.


Cisco Unity Voice Connector for Microsoft Exchange

This section contains two procedures. Do the procedure for your version of Cisco Unity.

To determine the Voice Connector version in use: Cisco Unity 4.0 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 appropriate folder:

Exchange 2000:<ExchangeServerPath>\VoiceGateway\bin

Exchange 5.5:<ExchangeServerPath>\connect\voice\bin

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

Step 4 Click the Version tab in the Properties window.

Step 5 Click Product Version in the Item Name box to view the product version in the Value box.


To determine the Voice Connector version in use: Cisco Unity 3.0 through 3.1


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 appropriate folder:

Exchange 2000:
<ExchangeServerPath>\VoiceGateway\bin\LocalizedFiles\ENU.

Exchange 5.5:<ExchangeServerPath>\voice\bin\LocalizedFiles\ENU.

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

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


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 Enu_g2p.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The File version corresponds to the following RealSpeak versions:

3.6.0.0 = RealSpeak ENU language engine version 3.0(1)

2.11.0.0 = RealSpeak ENU language engine version 2.1(1)

2.1.0.0 = RealSpeak ENU language engine version 2.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 Lhstts.dll, and click Properties.

Step 3 Click the Version tab.

Step 4 In the Items list, click Product Version. The File version corresponds to the following RealSpeak versions:

2.13.0.0 = RealSpeak base engine version 3.0(1)

2.12.0.0 = RealSpeak base engine version 3.0(0)

2.11.0.0 = RealSpeak base engine version 2.1(1)

2.1.0.0 = RealSpeak base engine version 2.0(1)


Important Information to Note from Earlier Cisco Unity 4.0(x) Release Notes

This section contains information worth noting from the Cisco Unity 4.0(1) release notes. 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.

Exchange Is No Longer Supported on the Cisco Unity Server for Unified Messaging

When Cisco Unity with Exchange is configured as Unified Messaging, Exchange cannot be installed on the Cisco Unity server for Cisco Unity 4.0(x). You must either move Exchange users to other Exchange servers or, if there are no other Exchange servers, you must install Exchange on another server and move Exchange users to the new server.

(When Cisco Unity is configured as Voice Messaging, Exchange 5.5 is supported on a Cisco Unity 4.0 server only if you are upgrading from a previous version of Cisco Unity. Exchange 2000 is supported on the Cisco Unity server both for upgrades and for new installations in the Voice Messaging configuration.)

Downloading Software for Cisco Unity 4.0(2)

This section contains procedures for downloading full CD images of Cisco Unity version 4.0(2) software and of third-party service packs from the Cisco Software Center website:

Downloading CD Images of Cisco Unity 4.0(2), below

Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Downloading CD Images of Cisco Unity 4.0(2)

Table 1 lists the contents of the Cisco Unity 4.0(2) CD images. The images contain only Cisco Unity software. They do not contain any third-party software.

Table 1 Contents of Cisco Unity 4.0(2) CD Images 

CD
Contents
1

Cisco Unity application files, ENU language files

2

CPCA and voice card driver files

3

ENG, ENZ, and ENA language files

4

FRA and DEU language files

5

NLD and NOR language files

6

ITA and SVE language files

7

ESP and ESO language files

8

DAN and PTB language files

9

JPN and KOR language files

10

CHS and CHT language files


To download full images of Cisco Unity CDs


Step 1 Use Table 1 to determine which Cisco Unity 4.0(2) CD images 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 full Cisco Unity 4.0(2) images, in addition to the space required to download the image. (The download file sizes appear on the Cisco Software Center website.)

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

Step 4 Click Unity 4.0 under "Cisco Unity Software."

Step 5 On the Cisco Unity 4.0 Software Download page, click the name of the file to download.

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

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

Step 8 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 9 If you plan to install Cisco Unity 4.0(2) from new compact discs, create a new 4.0(2) Cisco Unity Disc <N> for each image.

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


Downloading CD Images of Service Packs for Cisco Unity 4.(02)

Table 2 lists the contents of the service pack CD images for Cisco Unity 4.0(2). Each CD image is available in multiple languages, noted by the three-letter language acronym in the file name (for example, the ENU in the name CiscoUnity4.0-ServicePacks-ENU-CD1.exe refers to U.S. English).

Table 2 Contents of Service Pack CD Images for Cisco Unity 4.0(2) 

CD
Contents
1

Cisco Unity System Preparation Assistant, SQL Server 2000 SP 3, MSDE SP 3, Windows 2000 SP 3, MSXML3 SP 1, Internet Explorer 6.0 SP 1

2

Exchange 2000 SP 2, Exchange 2000 SP 3

3

Exchange 5.5 SP 4


To download full images of service pack CDs


Step 1 Use Table 2 to determine which service pack CD images to download. You always need CD 1.

Whether you download CD 2 and CD 3 depends on the message store being used. (Note that for an upgrade to Cisco Unity 4.0(2) from version 4.0(1), you do not need to download the CD 2 and CD 3 images.)

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 4.0(2) service pack images, in addition to the space required to download the image. (The download file sizes appear on the Cisco Software Center website.)

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

Step 4 Click Unity 4.0 under "Cisco Unity Software."

Step 5 On the Cisco Unity 4.0 Software Download page, click the name of the service pack file to download, in the applicable language. (The three letters that appear before the CD number in the file name refer to the language.)


Note For all languages, service pack CD 2 and CD 3 did not change between Cisco Unity versions 4.0(1) and 4.0(2). The CD 2 and CD 3 files on the Download page are still listed as being for version 4.0(1) and have an earlier date than the CD 1 files.


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

Step 7 Repeat Step 5 and Step 6 for each service pack file that you need.

Step 8 When all downloads are complete, extract the files for each service pack 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 (<XXX> is the language):

Cisco Unity System Preparation Assistant

CiscoUnity4.0-ServicePacks-<XXX>-CD1\Cuspa.exe

Exchange 5.5
Service Pack 4

CiscoUnity4.0-ServicePacks-<XXX>-CD3\Exchange_5.5_SP4\Update.exe

Exchange 2000
Service Pack 2

CiscoUnity4.0-ServicePacks-<XXX>-CD2\Exchange_2000_SP2\setup\i386\Update.exe

Exchange 2000
Service Pack 3

CiscoUnity4.0-ServicePacks-<XXX>-CD2\Exchange_2000_SP3\setup\i386\Update.exe

Internet Explorer 6
Service Pack 1

CiscoUnity4.0-ServicePacks-<XXX>-CD1\IE6SP1\ie6setup.exe

MSDE
Service Pack 3

CiscoUnity4.0-ServicePacks-<XXX>-CD1\MSDE_SP3\MSDE\Setup.exe

MSXML3
Service Pack 1

CiscoUnity4.0-ServicePacks-<XXX>-CD1\MSXML3_SP1\Msxml3sp1.exe

SQL Server 2000
Service Pack 3

CiscoUnity4.0-ServicePacks-<XXX>-CD1\SQL2000_SP3\x86\Setup\Setupsql.exe

Windows 2000
Service Pack 3

CiscoUnity4.0-ServicePacks-<XXX>-CD1\Win2K_SP3\I386\Update\Update.exe

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


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


Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)

For an upgrade from version 4.0(1), you download the applicable Cisco Unity 4.0(2) CD images from the Cisco Software Center website, and install from those images.

Use the following task list to upgrade Cisco Unity correctly. Some tasks in the list reference detailed instructions in the Cisco Unity Installation Guide, which is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

If you are upgrading a system configured for failover, start the upgrade on the primary Cisco Unity server. The task list alerts you when to begin upgrading the secondary server. Some failover tasks reference detailed instructions in the Cisco Unity Failover Configuration and Administration Guide, which is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.


Note The failover feature cannot be used for continuing Cisco Unity service on one server while upgrading the Cisco Unity software on the other server. Both the primary and secondary servers must be out of service while the Cisco Unity software is upgraded. The secondary server cannot handle voice messaging while the primary server is being upgraded.


Task List for Upgrading to Cisco Unity 4.0(2) from Version 4.0(1)


Note The Cisco Unity server will be out of service while the Cisco Unity software is upgraded.


1. Back up the Cisco Unity system.

2. Download the applicable Cisco Unity 4.0(2) software CD images and the Cisco Unity Service Packs CD 1 image from the Software Center website. See the "Downloading Software for Cisco Unity 4.0(2)" section. (Note that you do not need to download the Cisco Unity Service Packs CD 2 and CD 3 images for the upgrade.)

3. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server: Disable virus-scanning services and set the IDS Host Sensor Agent to run in On-Warning mode. Refer to the "Setting Security-Monitoring Software Before Running the Installation Programs" section of the "Customizing the Cisco Unity Platform" chapter of the Cisco Unity Installation Guide.

4. Run the Cisco Unity System Preparation Assistant to install SQL Server 2000 Service Pack 3 or MSDE 2000 Service Pack 3. Refer to the "Running the Cisco Unity System Preparation Assistant" section of the "Customizing the Cisco Unity Platform" chapter of the Cisco Unity Installation Guide.

5. Run the Cisco Unity Installation and Configuration Assistant to upgrade and configure the Cisco Unity software. See the "Upgrading and Configuring the Cisco Unity Software" section.

6. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server: Re-enable virus-scanning services and reset the IDS Host Sensor Agent to run in On-Protecting mode. Refer to the "Resetting Security-Monitoring Software After the Installation Programs Have Been Run" section of the "Installing and Configuring Cisco Unity Software" chapter of the Cisco Unity Installation Guide.

7. If the system is configured for failover: Upgrade the secondary server and configure both servers for failover:

a. Run the Configure Cisco Unity Failover wizard on the primary Cisco Unity server. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Configuration and Administration Guide

b. Repeat Task 3. through Task 6. on the secondary Cisco Unity server.

c. Run the Configure Cisco Unity Failover wizard on the secondary Cisco Unity server. Refer to the "Configuring Failover on the Primary and Secondary Servers" section in the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Configuration and Administration Guide.

8. If you are modifying hardware or software, or adding features: Refer to the "Modifying the Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide.

9. If the system is using the AMIS, Bridge, SMTP, or VPIM networking options: Upgrade the Cisco Unity Voice Connector for Microsoft Exchange, if applicable. Refer to the applicable version of release notes for the Voice Connector, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Upgrading and Configuring the Cisco Unity Software


Caution When you run the Cisco Unity Installation and Configuration Assistant, Cisco Unity is uninstalled and then reinstalled. Fields will contain values from the current installation. Do not change any values unless you are instructed to do so in the following procedure, or the system may not be updated correctly.

To upgrade and configure the Cisco Unity software


Step 1 Log on to Windows by using the Cisco Unity installation account.

Step 2 From the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the root directory and double-click Setup.exe.

Step 3 If prompted, double-click the language of your choice to continue the upgrade.

Step 4 On the Cisco Unity Installation and Configuration Assistant Welcome screen, click Continue.

Step 5 In the main window of the assistant, click Run the Cisco Unity Setup Program.

Step 6 If prompted, double-click the language of your choice to continue the upgrade.

Step 7 If a message to stop services appears, click OK.

Step 8 Click Next or Continue without changing values until the Select Features dialog box appears.

Step 9 In the Select Features dialog box:

a. Check the Upgrade Cisco Unity check box.

b. Uncheck the Install Voice Card Software check box.

Do not change any other values.

Step 10 Click Next or Continue without changing values until you are prompted to restart the Cisco Unity server.

Step 11 Check the Yes, I Want to Restart My Computer Now check box, and click Finish.

The Cisco Unity Installation and Configuration Assistant displays check marks next to "Install Cisco Unity" and "Install the Cisco Unity License Files," and the Configure the Cisco Unity Services screen appears in the main window.

Step 12 In the main window of the assistant, click Run the Cisco Unity Services Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

Step 13 On the Welcome screen, click Next.

Step 14 Select the message store type, and click Next.

Step 15 Follow the on-screen prompts to complete the configuration.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Services," and the Configure the Cisco Unity Message Store screen appears in the main window.

Step 16 In the main window of the assistant, click Run the Cisco Unity Message Store Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

Step 17 Confirm that the message store server is running. If the message store server is not running, configuring the message store will fail.

Step 18 On the Welcome screen, click Next.

Step 19 Follow the on-screen prompts.

Step 20 When the message store configuration is complete, click Finish.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Message Store."

Step 21 When the Summary screen appears, click Close.


Upgrading to Cisco Unity 4.0(2) from Version 3.x or 2.x

For upgrades from Cisco Unity version 3.x or 2.x, refer to the applicable chapter of the Cisco Unity Installation Guide:

Chapter 13, "Upgrading Cisco Unity Version 3.x to Version 4.0"

Chapter 14, "Upgrading a Cisco Unity 2.x System to Version 4.0"

The Cisco Unity Installation Guide is available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

New and Changed Support—Release 4.0(2)

This section contains information about new and changed support in the Cisco Unity Release 4.0(2) 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 3 Changes to the Tools Depot 

Updated Tools
New Tools

Bulk Logout

Cisco Unity Data Link Explorer

DbWalker

Message Store Manager

Permissions Wizard

Public Distribution List Builder

Schedule Cisco Unity Restart

Subscriber Information Dump

Third Party Fax Administration

Uninstall Cisco Unity

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

Port Status Monitor

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


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

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

IBM Lotus Notes 5.0.11 Supported on a Cisco Unity with Domino Server

Cisco Unity versions 4.0(2) and later support IBM Lotus Notes 5.0.11 as a messaging client on a Cisco Unity with IBM Lotus Domino server.

Phone System Integrations Qualified for Use with Cisco Unity

The following phone system integrations have been qualified for use with Cisco Unity:

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 4.0(2)—refer to the "Supported Phone System Integrations" section in Cisco Unity 4.0 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.

Software Qualified for Use on Cisco Unity Subscriber Workstations

Cisco Unity version 4.0(2) with IBM Lotus Domino supports IBM Lotus Notes version 5.0.10 for use as a messaging client on Cisco Unity subscriber workstations.

For the most current version combinations of software qualified for use on subscriber workstations—including software qualified since the release of Cisco Unity version 4.0(2)—refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations, available 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

Because of the recent W32.Slammer worm, Cisco is requiring Service Pack 3 for SQL Server 2000 and MSDE 2000 with Cisco Unity versions 3.0(1) and later. Procedures in these release notes and in the Cisco Unity Installation Guide, Release 4.0(2), for upgrading to and installing Cisco Unity 4.0(2) have been updated to reflect the change.


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.

Third-Party Fax Integrations Supported with Cisco Unity with IBM Lotus Domino

Cisco Unity with Domino supports third-party fax integrations.

For a complete list of qualified third-party fax products, refer to the "Supported Fax Server Software" section of the Cisco Unity 4.0 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.

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. However, if you are using Cisco Unity with Microsoft Exchange, you may want to upgrade 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.


Caution The following procedure does not work when Domino is the message store, because the Disaster Recovery Tool does not support Domino.

To upgrade from Windows 2000 Server to Windows 2000 Advanced Server (optional, Exchange only)


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 by 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 "Mandatory Tasks for Installing Cisco Unity" chapter of the Cisco Unity Installation Guide, Release 4.0(2), available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_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 Automatic Update Supported

Windows Automatic Update (WAU) is supported on a Cisco Unity 4.0(x) and later server, and on a Cisco Unity Bridge 2.1(x) and later server when the option Notify Me Before Downloading Any Updates and Notify Me Again Before Installing Them on My Computer is selected. (Note that if Cisco Unity Platform Configuration Disc revision 12 or later is used to configure the platform for the Cisco Unity or Cisco Unity Bridge server, then WAU is disabled.)


Caution Configure WAU only to check for updates, not to install updates. Most Microsoft updates can be installed on the Cisco Unity or Cisco Unity Bridge server as soon as they become available. However, Microsoft service packs must be qualified for use with Cisco Unity and the Cisco Unity Bridge, and WAU does not let you distinguish between service packs and other updates.

For Microsoft service pack and update support policy information, refer to Compatibility Matrix: Required and Recommended Third-Party Service Packs, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

New and Changed Functionality—Release 4.0(2)

This section contains information about new and changed functionality for Cisco Unity Release 4.0(2) 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.

Cisco Personal Communications Assistant Help

Online Help for the Cisco Personal Communications Assistant (PCA) is available on the Cisco Unity software discs. You do not need to download it separately from the Cisco Software Center website, nor do you need to install it. It is installed automatically when Cisco Unity is installed.

Cisco Unity Bulk Import Wizard

The Cisco Unity Bulk Import wizard allows you to modify existing subscriber accounts on Cisco Unity with Domino and Cisco Unity with Exchange systems.

In addition, on a Cisco Unity with Exchange system, DELIVERY_LOCATION_ID is now a valid, optional column header in CSV files used to create AMIS, Bridge, or VPIM subscriber accounts with multiple delivery locations.

For additional Cisco Unity Bulk Import wizard information, see the "Limitations and Restrictions" section.

Cisco Unity Greetings Administrator

When a public distribution list owns a call handler, the Cisco Unity Greetings Administrator allows each member of the public distribution list to manage call handler greetings by using the Cisco Unity phone conversation.

For example, the public distribution list members can call Cisco Unity from any site to:

Rerecord a call handler greeting.

Enable or disable the alternate greeting for a call handler.

Determine which greeting is currently active for a call handler.

In previous versions of Cisco Unity, the Cisco Unity Greetings Administrator was not available for use when a public distribution list owned a call handler. Only individual subscribers who owned call handlers could use the Cisco Unity Greetings Administrator. (Note that the call handler owner is not necessarily the message recipient.)

Cisco Unity Installation and Configuration Assistant

The Cisco Unity Installation and Configuration Assistant is now used for installing or upgrading a system with failover, and for adding licensed features to a system with or without failover. In Cisco Unity 4.0(1), the assistant was used only to install a new Cisco Unity system without failover.

Cisco Unity with Exchange: Active Directory Contacts Deleted When Associated External Subscribers Are Deleted

When AMIS, Bridge, or VPIM subscribers (referred to collectively as external subscribers) are deleted in the Cisco Unity Administrator—either by deleting the subscriber accounts individually or by deleting the associated delivery location—the underlying Active Directory contacts (or in the case of AMIS subscribers, the underlying Exchange 5.5 custom recipients) are automatically deleted. When you delete an Internet subscriber in the Cisco Unity Administrator, a dialog box is displayed that allows you to optionally delete the associated contact (or custom recipient).

Note that for regular Cisco Unity subscribers, the option to delete the associated accounts in Active Directory or Windows and Exchange is not provided. Because of the security risk of accidentally deleting messages for a user and denying a user access to the Windows domain, the associated accounts and Exchange mailboxes have to be deleted by using standard Microsoft tools after deleting the subscribers in the Cisco Unity Administrator.

Cisco Unity with Exchange: Disabling the Automatic Directory Synchronization of Bridge Subscribers

On a Cisco Unity server configured for networking with the Cisco Unity Bridge, the CsBridgeConnector service can be customized to disable the automatic creation, modification, and deletion of Bridge subscribers. For more information, see the "Disabling the Automatic Creation, Modification, and Deletion of Bridge Subscribers (Cisco Unity 4.0(2) and Later)" section in the "Bridge Networking" chapter of the Cisco Unity Bridge Networking Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

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 (when there is no recorded name, Cisco Unity plays the extension instead) and asks the subscriber to confirm that the recipient is correct.

A new registry setting allows you to alter the subscriber conversation during message addressing. Table 4 lists the confirmation prompts that subscribers hear with the available values for the registry setting.

Table 4 Confirmation Prompts That Subscribers Hear During Message Addressing 

Registry Value
With Exact Match
With More Than One Matching Name

0
(the default setting)

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

"There are 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 matching names, choose by number. For Alex Campbell, press 1. For Li Campbell, press 2. For Terry Campbell, press 3..."

2

"Added."

"There are 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..."


You use the Advanced Settings Tool to change the registry setting. For details, refer to the "Cisco Unity Conversation" chapter in the Cisco Unity System Administration Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guides_list.html.

Support for Copies of Configuration Files for Circuit-Switched Phone Systems

When you are creating an integration with a circuit-switched phone system and have made a copy of the .ini configuration file for your phone system in the CommServer\IntLib directory, the Telephony Integration Setup wizard and the Cisco Unity Telephony Integration Manager (UTIM) offer you the choice of the applicable configuration files.

This feature is useful when you modify the contents of the configuration file but want to keep a copy of the original file available for reference.

Installation and Upgrade Notes

For detailed information on installing a new Cisco Unity 4.0(x) system or on upgrading to Cisco Unity version 4.0(x), refer to the Cisco Unity Installation Guide, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

The Microsoft Knowledge Base Article 313807, XADM: Enhancing the Security of Exchange 2000 for the Exchange Domain Servers Group, describes how to obtain and use the Microsoft Exchange 2000 script called EDSLock, which restricts access granted to the Exchange Domain Servers groups in a forest. Running the EDSLock script in a forest that includes a Cisco Unity server will cause Cisco Unity to malfunction.

When you install Cisco Unity after you run the EDSLock script, Cisco Unity works properly because the Cisco Unity Permissions wizard sets the permissions on the message store services account that are necessary to counteract the effects of the EDSLock script on Cisco Unity.

You will need to rerun the Permissions wizard to update the permissions on the message store services account whenever you:

Run the EDSLock script after you install Cisco Unity.

Add an Exchange 2000 server to the forest and home mailboxes for Cisco Unity subscribers on that server.

Add a mailstore to an Exchange 2000 server and home mailboxes for Cisco Unity subscribers in that mailstore.

For more information, refer to the tech tip Cisco Unity Malfunctions After Running Exchange 2000 EDSLock Script, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a00801463f3.shtml. For detailed information on the permissions set by the Cisco Unity Permissions wizard, refer to the Permissions wizard Help.

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 Cisco Unity Assistant, 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 CommServer\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 maintenance upgrades.

Cisco Unity with Exchange: ViewMail for Microsoft Outlook No Longer Controlled by Class of Service

When upgrading a Cisco Unity 3.(x) system to Cisco Unity version 4.(x), subscribers are no longer required to have special class of service privileges to use ViewMail for Microsoft Outlook. Any subscriber who has ViewMail installed can use it.

Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter

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

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

Upgrades from Cisco Unity Versions Earlier than 2.3(4.104) Are Not Supported

The Cisco Unity Database Export and Database Import utilities, which let you export subscriber and other information from a 2.x system and import it into a 4.0(x) system, do not work on a Cisco Unity system earlier than version 2.3(4.104). You must install Cisco Unity 4.0(x) as a new system, and all Cisco Unity data from the old system is lost.

Using Japanese and Mainland Mandarin Text to Speech

Japanese and Mainland Mandarin text to speech require specific language settings on the Cisco Unity server. For details, 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_guides_list.html.

Limitations and Restrictions

Cisco Unity Bulk Import Wizard

When you run the Cisco Unity Bulk Import wizard, disable virus-scanning services on the Cisco Unity server and set the IDS Host Sensor Agent on the Cisco Unity server to run in On-Warning mode, if applicable. Otherwise, the Cisco Unity Bulk Import wizard may run slowly.

In addition, on Cisco Unity with Exchange systems, the Select Subscriber Data Import Option page of the Cisco Unity Bulk Import wizard does not explain what happens when the Use Existing Mailboxes and Windows Accounts option is used during the creation of AMIS, Bridge, or VPIM subscriber accounts by importing user data from a comma-separated value (CSV) file.

The Select Subscriber Data Import Option page should provide the following information:
"If you click Use Existing Mailboxes and Windows Accounts, consider that when you import existing Active Directory contacts or Exchange 5.5 custom recipients, the imported objects can no longer be used for outbound message addressing to remote e-mail addresses. They can be used for addressing voice messages to remote voice messaging systems however."

Digital Networking

The following limitations exist when more than one Cisco Unity server is integrated with a networked phone system. (On a networked phone system, subscribers can dial an extension rather than a full phone number when they call someone who is at another location on the phone network.)

Call Transfer Settings Unavailable

When calls are transferred from the automated attendant or directory assistance to subscribers not associated with the local server, the transfers are automatically handled by the phone system (release to switch)—rather than by Cisco Unity (supervised transfer)—even if these subscribers are set up for supervised transfers. In this case, the call screening, call holding, and announce features will not be available on these calls. If the discrepancy in behavior is a concern to subscribers, you may want to consider limiting directory handler searches to the local server by adjusting the setting on the Directory Handler Search Options page in the Cisco Unity Administrator.

Message Sender Is Unknown and Message Recipient Cannot Reply

When a subscriber places a phone call to another subscriber who is associated with a different Cisco Unity server, and the call is forwarded to voice mail, Cisco Unity cannot identify who left the message. That is, identified subscriber messaging does not work, and, instead, the message is handled as though it came from an unidentified caller. In this case, subscribers will notice the following limitations:

When the call is forwarded to voice mail, the internal greeting is not played to the subscriber leaving the message.

When the recipient listens to messages over the phone, the subscriber conversation cannot "announce" who the message is from (by playing the recorded voice name of the sending subscriber).

After listening to the message, the subscriber conversation does not allow the recipient to press the reply key and record a reply to the sender.

This is by design and there is no workaround.

Note, however, that the sending subscriber can be identified (which means the internal greeting will play, the subscriber conversation can announce who left the message, and the recipient can reply) in the following cases:

When a subscriber calls Cisco Unity, logs on as a subscriber, and sends a message, regardless of which Cisco Unity server the recipient is homed on.

When a subscriber places a phone call to another subscriber who is on the same Cisco Unity server, and the call is forwarded to voice mail. For identified subscriber messaging to work in this case, do not check the Subscribers Are Identified as Message Senders Only If They Log On check box on the Configuration > Settings page of the Cisco Unity Administrator. However, if the discrepancy in behavior is a concern to subscribers, you may want to consider disabling identified subscriber messaging systemwide.

Dual NICs

Cisco Unity is qualified for dual network interface cards (NIC) configured only in adaptive fault-tolerant mode (AFT is the abbreviation used by Dell and IBM), which is also known as network fault-tolerant mode (NFT is the abbreviation used by 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.

Replacing Disks in a RAID

For any server in a Cisco Unity system (the Cisco Unity server, a failover server, a Cisco Unity Bridge server, a message store server, or a dedicated DC/GC), Cisco Unity supports only replacing a defective disk in a RAID with a blank disk to repair the RAID. Replacing disks in a RAID for any other reason is not supported.


Caution Do not replace a disk in a RAID with a disk that contains data, even if the replacement disk was originally a disk in the same RAID in the same server.

Cisco Unity with Exchange: 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.

Alternatively, when the Play All Names feature is enabled for a directory handler and Cisco Unity plays all names listed in the directory, callers can find subscribers by using directory assistance. Subscribers still cannot easily address messages to a subscriber with a Japanese name in spelling mode, however.

Cisco Unity plays the names of subscribers for caller selection—rather than requiring the caller to search by spelled name—when the Play All Names check box is checked on the directory handler Profile page in the Cisco Unity Administrator. Cisco Unity automatically plays the names of all subscribers in the directory when either of the following conditions is true:

One to five subscriber names are listed in the directory.

There are more than five—but fewer than 51—subscriber names listed in the directory and the caller chooses to play all names listed in the directory.

Note that when there are more than 51 names in the directory, Cisco Unity requires that the caller search for a subscriber by spelled name.

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/pcgi-bin/Support/Bugtool/launch_bugtool.pl.)

Windows Terminal Services

Table 5 lists the limitations on using Windows Terminal Services on a Cisco Unity server with version 4.0(1) and later.

Table 5 Windows Terminal Services Limitations with Cisco Unity 

Remote Functionality
Cisco Unity 4.0(1) and Later

Install or upgrade Cisco Unity

Not supported

Add or delete a subscriber by using the Cisco Unity Administrator

Supported

Use the Cisco Unity Diagnostic Tool

Supported

Use the Port Status Monitor in Tools Depot

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

Test the Cisco Unity-CM TSP

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/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

Note that this section contains caveat information for Cisco Unity Release 4.0(2) 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 4.0(2)

Table 6 Cisco Unity Release 4.0(2) Open Caveats 

Caveat Number
Severity
Description

CSCdy36595

2

Unity crashes due to AvCsMgr virtual memory leak.

Symptom: Cisco Unity subscribers may hear 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: 5984,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.

Condition: In Cisco Unity version 3.1.5/4.0.1, this may happen if the process AvCsMgr leaks virtual bytes. If the virtual bytes exceeds the recommended limits on an Unity system, the subscriber may possibly see unexpected system behavior and error events in the application event log. This happens only on high end systems with a high user/port number and under heavy call traffic.

Workaround: Restart the Unity server

CSCdy86513

2

Starting and Stopping Cisco Unity services causes Notes to hang.

Symptom: Cisco Unity for Domino fails to start. Or, Cisco Unity for Domino starts but is not operational.

Conditions: When Cisco Unity for Domino is stopped, interaction with the Lotus Notes subsystem may terminate incorrectly. Subsequently, starting Cisco Unity will fail to establish a working connection to Domino.

Workaround: Restart the Cisco Unity server.

CSCdz02639

2

The Cisco Unity Administrator does not display any links in the navigation panel on the left-hand side when someone accesses the Cisco Unity Administrator on a remote computer.

Condition: This can happen if the Cisco Unity Administrator of a remote machine is accessed from the local Cisco Unity server

Workaround

Right click the mouse in the left hand section in SA of the remote Unity server and click on "Refresh." The links should be displayed now

CSCdz12267

2

When using Text Pager Notification with Cisco Unity for Domino, when a new message arrives for a subscriber, Cisco Unity will continue to send notification messages even after the original message is retrieved.

Conditions:

Cisco Unity for Domino only. The Text Pager Notification feature is enabled and configured to a valid SMTP address.

Workaround:

None. To stop the notification messages from being sent, disable the feature from the Cisco Unity Administrator.

CSCdz13175

2

In failover systems that have an integration with a circuit-switched phone system, the primary server may fail over to the secondary server for no valid reason, and a warning is logged in the Event log on the secondary server that a call was received on the secondary server and hence it is failing over.

Condition:

This can happen randomly without a valid reason when the NewCallDelay setting in the registry on the secondary server is set to 1200ms.

Workaround:

Disable the new call delay timer and revert back to the old behavior of increasing the answer delay on the secondary server:

1. Set Miu\1.0\Initialization\New Call Delay on Inactive Backup Server = 0 in the registry.

2. In the switch file on the secondary server, set IncomingCallRings=3.

3. Restart the secondary server for the changes to take effect.

CSCdz22524

2

After a user forwards an email or fax message via the TUI, the user is told they have reached the end of their message stack even though they have more messages, and the failsafe conversation is heard. Also, the forwarded message is never delivered.

Conditions:

Cisco Unity for Domino only. This was only seen when the forward-via-TUI was attempted with an email or fax message that had already been forwarded.

Workaround:

None

CSCdz26046

2

In a multi-Cisco Unity server environment, the All Subscribers public distribution list has the same extension on all the Cisco Unity servers (99991). When subscribers try to address a message to the All Subscribers list, Cisco Unity finds one than one match and prompts subscribers to confirm addressing by playing, "For All Subscribers, press 1. For All Subscribers, press 2. For All Subscribers, press 3..."

In addition, the following error is logged in the event log:

Event Type: Error
Event Source: CiscoUnity_ConvAddrSearch
Event Category: Error
Event ID: 111
Date: 11/8/2002
Time: 9:31:34 AM
User: N/A
Computer: MEDIAUNITY1
Description: Extension Conflict for Multiple Subscriber while searching for subscribers through the TUI. Technical details - [99991] on line 9712 in file:\views\cs_ue4.0.0.280\un_Conv3\AvConvUtilities\AvConvAddrSearchSvr\AvSAddrSearcher.cpp. For more information, click: http://www.CiscoUnitySupport.com/find.php

Workaround:

Modify the extensions for the All Subscribers list on each of the Cisco Unity servers in the network so each distribution list is assigned a unique extension.

CSCdz26707

2

When the Cisco Unity Setup Program is cancelled, and then rerun, the program runs in upgrade mode, and the UnityDb database is not created.

There is no workaround.

CSCdz39077

2

Cannot import Public Distribution Lists from Exchange 5.5 into Unity.

If you go to Public Distribution List in Unity and press Add, then choose Import, Find and Select Public Distribution List to Import. Choose Find by Alias, and the field to enter the Alias has an asterisk for wildcard searches. No matter what is entered, we see, "A Runtime error has occurred. Do you wish to Debug? Line: 1062. Error: Expected ';' "and the Import fails.

Workaround

Because the org of the Exchange environment had quotes in it ("Cisco Systems Inc."), this will make the LDAP property distinguished Name also contain the quotes. Note that the distinguished Name is not the same name of the DL; the distinguished Name includes the name of the object, site, org, etc.... The point is that you don't need a special char like "in the name of the DL. Having it in the distinguished Name can cause this problem.

CSCea09277

2

Cisco Unity stops taking calls while under load due to ports issue.

Symptom: When calling into Cisco Unity, Cisco Unity will not answer (keeps ringing). The Status Monitor port status page shows the ports are stuck in Subscriber Sign-in.

Conditions: This occurs only on Cisco Unity 4.0(2) for Domino when in an overload condition on large systems (72 ports.)

Workaround

Restart Unity services via the Tray Icon.

CSCea26526

2

If you unload a loaded language from the TUI Language settings in the Cisco Unity Administrator, this can lead to failsafe if the language loaded was set as the default and the OS regional language is set to something other than a language supported by Unity, or if - the language unloaded was set explicitly as the language to use instead of inherited.

There is no workaround.

CSCea26846

2

Not all messages are delivered when Unity is not able to connect with the GC.

CSCea29871

2

Tools Depot fails to open if the message store is not configured. Tools Depot returns the following error because the message store is unknown, "Mailstore type returned as. This doesn't match a defined type. Exiting." The problem occurs in Cisco Unity version 4.0(1) or higher.

Workaround

Run Setup.exe, located in the \Configuration\Setup folder, to configure the mailstore. Tools Depot should open. If the mailstore can not be configured, for example when setting up failover, go directly to the executable you want to run and double-click it. Most of the tools that are installed with Cisco Unity can be found in the \Commserver\Utilities directory. For the Licensing Install Wizard, go to \Commserver\Utilities\Licensefilewizard\Licfilewiz.exe, and for the Service Configuration Wizard, go to \Commserver\Utilities\Serviceconfigwizard\Svcwiz.exe.

CSCae08096

3

Unity plays failsafe and AvPhraseServer_MC errors in application log. Symptom: When a caller calls voicemail, the failsafe greeting is played. An AvPhraseServer_MC error is logged in the Application event log. Conditions: The failsafe prompt that is heard when Unity is called says the system is not available to process your call, please try again later. This behavior has been seen in Cisco Unity 2.4.6 and 3.0(x).

Workaround

At a command prompt go to the \Commserver\components directory. Register the AvPhraseServerSvr.dll by typing `regsvr32 AvPhraseServerSvr.dll'. Info to gather for further investigation into a fix: per the Comments enclosure comment from 9/19/02, in order to fix this problem, we need to know the value of the following registry key from a site that is experiencing the problem: HKEY_CLASSES_ROOT\TypeLib\{560C47E1-B2C2-11D1-B681-00C04FB64EDD}\1.0\0\win32.

CSCae08168

3

Sometimes adding a new Restriction Table on the Restriction Table of the Unity System Administrator results in a run time error message. This error prevents the table information from appearing properly on the page. This usually only occurs the first time the administrator accesses the page.

Workaround:

Refreshing the browser page (clicking the refresh button or by pressing 'F5') will correct the information in the table.

CSCdv00319

3

Modify private list dialog needs NEXT button for large lists. Symptom: The dialog box for changing members of a subscriber's private list is able to present a selection of names based on match criteria. If a wildcard character such as * is used, and there is a large number of matching names, not all names will be available in the list box. In most SA screens where this can happen, a NEXT button is provided to get the next set of matching names. It appears that this convention is not used in this particular area of the SA. There will be no Next / Prove buttons for navigating the matches.

Conditions: Using Unity 2.4.6.102 & a database with several hundred subscribers, go to any subscriber's Private List page, click the button for change members, and use * for a wildcard search in the dialog box that appears. IMPORTANT: You must sort by DISPLAY NAME, this bug doesn't seem to happen with the other searches.

Workaround:

You can work around this problem by sorting the list with something other than display name.

CSCdw00609

3

Syscheck Setup Part II needs to verify acct is a domain acct.

Symptom: Syscheck displays the following errors during setup part II: "Domain - The specified domain either does not exist or could not be contacted. Exchange 2000 - Unable to get basic ldap information." Condition: This occurs in Cisco Unity 3.0(X) and higher when you run setup part II with a local account instead of a domain account.

Workaround:

Log on by using a domain account with the appropriate rights before you run the Cisco Unity Server Configuration wizard."

CSCdw24271

3

Reports Notification: No email is sent to the Administrator.

CSCdw36215

3

Setup crashes when using a /3GB switch in the boot file

Symptom: Unity Setup stalls with the following error "Insufficient memory available to run Setup. Close all other applications to make more memory available and try to run Setup again. Error 111". Closing all other applications and re-running setup produces the same error Condition: This happens if there is a /3GB switch in the boot.ini file on the Unity server

Workaround:

Remove the /3GB switch in order for the install to run correctly and then put it back after the configuration setup is completed.

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

CSCdw92582

3

UNITY:Setup Part 2 error regarding local admin group too vague

Configuration setup may fail with the error message `The selected user is not a member of the local administrator's group' incorrectly. Symptom: This is because setup runs several tests while checking for local administrator group membership. If any one of those tests fail they will all return the umbrella error "selected user is not a member of the local administrator's group". An account may actually be a member of the local administrator group but does not have a specific user right such as "Access this computer from the network".

There is no workaround.

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.

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. If you delete subscribers from this tool, a wizard will appear asking where to repoint any links that are pointing to the soon to be deleted subscriber. This workaround only applies to Unity 4.0(x) and higher.

CSCdx46888

3

Subscribers can be deleted without the system checking to see if there are any call handlers or other objects that rely on that subscriber for anything. This can be a problem if a call handler relies on that subscriber as the message recipient. Whenever we hit that call handler, we'll get a failsafe message. The owner field on the call handler will also be blank if it was owned by that subscriber. There should be a mechanism that first checks all object dependencies when an administrator attempts to delete a subscriber.

There is no workaround.

CSCdx62431

3

VMO plug-in causes errors when using Outlook XP. Symptom: When starting Outlook XP with VMO loaded, intermittently you will get the following error. Outlook experienced a serious error the last time the add-in `c:\program files\viewmail\tfxext32.dll' was opened. Would you like to disable this add-in? To reenable this add-in, click About Microsoft Outlook on the Help menu, and then click Disabled Items.

There is no Workaround

CSCdx66059

3

The Event Notification Utility administrator shows errors that are not logged to a persistent file. The Event Notification Utility produces error message boxes to the user but does not log those errors in many cases. It is essential that these errors are logged in a persistent medium so that TAC/sustaining engineers will be able to see what errors were encountered when the customer ran the tool.

There is no workaround.

CSCdx70947

3

SysCheck does not catch SQL permissions issue.

Symptom: Setup Part I fails with the error that UnityDB could not be created. Condition: This occurs in Cisco Unity 3.1(3) and higher when the BUILTIN\Administrators group does not have adequate SQL rights. This may also occur in earlier 3.X versions of Cisco Unity.

Workaround:

In SQL, verify that the BUILTIN\Administrators group has the Database Creators role checked:

1. Run the SQL Enterprise Manager

2. Expand the tree in the left pane until you reach Security > Logins

3. Right click BUILTIN\Administrators and select Properties 4. Go to the Server Roles tab

5. Check ""Database Creators"" if it is not checked.

6. Click OK

CSCdy21304

3

After reboot Unity fails to start with event ID 10005 in system log. Symptom: After a reboot Unity fails to start. The system log contains the following error: Event ID: 10005 Source: DCOM Category: None Type: Error Description: DCOM got error "The service did not start due to a logon failure." attempting to start the service XXZ with arguments "-Service" in order to run the server: {XXX} Condition: This will only occur if the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services are logging on with a domain account and the account is not granted the "Log on as a batch job" right explicitly.

Workaround

1. Grant the account the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services are logging on with the "Log on as a batch job" privilege to the appropriate GPO.

2. From Services, reapply the password used for the account logging on to the AvCsGateway, AvCsMgr, AvUMRSyncSvr, and AvGaenSvr services.

3. From command run
ssecedit /refreshpolicy user_policy /enforce.

4. Start Unity by right clicking the tray icon.

CSCdy28293

3

Syncher doesn't sync mailstores when running a full directory sync. Symptom: Cisco Unity does not recognize new mailbox limits after the appropriate replication has occurred. Condition: This problem may occur when Cisco Unity has been configured previously to connect to an Exchange 5.5 server and the USN value for the mail store on the previous Exchange 5.5 server is higher than the USN values of the mail store on the currently connected Exchange 5.5 server. When this condition occurs, the values in the MailStore table in the UnityDB database will not be updated.

Workaround

1. Stop the AvDSEx55 service by using Windows Services Control Panel.

2. Start Regedit.

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

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

5. Double-click LastUSN.

6. Enter 0 in the Value Data box.

7. Close Regedit.

8. Click Start > Programs > Microsoft SQL Server > Enterprise Manager.

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

10. Click Tables.

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

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

13. Close Microsoft SQL Enterprise Manager.

14. Start the AvDSEx55 service.

CSCdy36517

3

Conversation sees large delays when Exchange index refreshes. Symptom: When subscribers use the phone to check their messages, large delays are experienced in the Cisco Unity conversation. These delays get longer as the user's mailbox gets larger. Condition: Usually these delays are only noticeable when the subscriber has a very large mailbox (in excess of a few thousand messages). But the delays vary depending on the configuration, hardware, and network conditions.

Workaround:

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

CSCdy37982

3

On upgrades, AvCiscoTSP_MC.dll becomes unregistered. Symptom: On upgrades, AvCiscoTSP_MC.dll gets unregistered from the \WINNT\SYSTEM32 directory, this causes all messages for the TSP in the event log to contain no information. They Event log messages for the TSP look similar to this one after an upgrade: Event Type: Information Event Source: AvCiscoTsp_MC Event Category: None Event ID: 101 Date: 8/15/2002 Time: 6:51:46 PM User: N/A Computer: Computer Description: The description for Event ID (101) in Source (AvCiscoTsp_MC) cannot be found.The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 5, 10.93.250.31. Condition: Upgrade from 3.x to 3.x or 3.x to 4.0(1).

Workaround:

Reinstalling the TSP, or re-registering AvCiscoTSP_MC.dll with the regmc utility resolves the problem.

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. Symptom: There are no symptoms.

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

CSCdy49079

3

AvRepMgr event 20004 is not useful to customer. Symptom: Error message logged for AvRepMgr error is not useful to customer. Condition: The following event log error has no useful text for customers. It does not follow ECSBU event log guidelines. event log error event ID 20004 Source: AvRepMgr_MC Description: REPMGR RUNMODULE ERROR REPORTID 7 MODULE CRUNCH01 HRESULT 0x80004005. Workaround: None

CSCdy60149

3

Subscriber Message Activity report not working. Symptom: When we run subscriber message activity report, it only displays subscriber Message waiting light on/off activity. All other related subscriber message activities like deleting, listening, delivery is not reported. Condition: When the subscriber message activity report is viewed by accessing the queued report, they show only activity related to MWI on/off. After accessing the SUBMSG table in the reportDb, we verified, that all the rows were empty.

Workaround

Access the diagnostic tool and Create a new diag_AvCsMgr file for Unity service to start logging information. This works for some time and will eventually require to create a new diag file for it to continue working.

CSCdy66087

3

Last port on Dialogic D240T1 card locks up on outgoing notification. Symptom: Whenever the last port on each 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: The affected system has 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 box, calls are randomly being sent to the opening greeting instead of subscriber mailboxes. Problem: 1) After a PBXLink box sends out a corrupt MWI on/off request, the very next incoming call has its call info stripped by the PBXLink box. When the call is handed to Cisco Unity, the call 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:

For problem 1, dedicate a PBXLink box for MWIs, so that any PBXLink boxes that are processing incoming calls are not also processing MWIs. For problem 2, there is no workaround.

CSCdy81363

3

Installing Dialogic software install Dialogic TSP twice

Symptom: On a Unity system, the Dialogic software and tsp were manually removed and Unity setup was reran, selecting only "Install Voice Card Software". After setup completed, two instances of the Dialogic TSP appeared in Phone and Modem options of the Windows Control Panel Settings. Conditions: The reinstall was done on a failover system and the symptoms were seen on both of the servers.

Workaround:

One instance of the Dialogic TSP can be removed, but contact TAC before doing so.

CSCdy84566

3

In an Australian language installation of Unity 3.1 with RealSpeak TTS, the subscribers that have their "Subscriber language" in the Conversation options set to English(Australian) do not read back the subject and body of messages.

Workaround

Set the Subscriber -> Conversation -> Subscriber's Language to "English (United States)".

Alternatively, for a server wide solution, ensure that the Default Text-To-Speech Language, in the Unity SA's System -> Configuration -> Phone Languages, is set to "English (United States)".

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:

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

CSCdz05449

3

3.1(5) upgrade, Configuration Setup hang 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:

Reboot Unity

CSCdz13335

3

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

Symptom: Cisco Unity install program hangs with the taskbar indicating the install is almost finished if the option to install Dialogic DNA software is selected. The status of Unity install program in the TaskMgr indicates it is either not responding or still running and it will remain in this state indefinitely. If the Unity install program is stopped manually Cisco Unity will have been installed successfully but none of the Dialogic DNA software will have been.

Condition: Dialogic install seems to require the account under which the Dialogic DNA software is being installed be in the built-in administrators group. This may only be a problem with Active Directory because it uses an old 16-bit version of Installshield which was developed before Active Directory was released. In Unity 4.0.x, if CUICA is used properly, then running the Permissions wizard will assign the correct permissions to the Unity installer account, which is the same account that should be used to install the Dialogic software. As Cisco Unity install program suppresses all pop-up dialogue windows generated by the Dialogic install program and because the install programs has not run far enough to enable error logging there is no way to there are problems. Running Syscheck will not work because it does check to see if the account under which Cisco Unity is being installed is in the built-in Administrator's group. One way to verify this is to manually run the Dialogic Install program while logged on under the same account under which Cisco Unity was installed. The Dialogic install program will generate a pop-up dialogue window stating you must log on as the Local Administrator in order to proceed.

Workaround: No workaround is necessary if you are installing Unity 4.0.x, since CUICA will guide you through proper installer account permissions. Do not attempt to install the Dialogic DNA software manually after having installed Cisco Unity as this is not supported and leads to other problems when it comes to configuring the Dialogic Voice cards. Recommend making the built-in administrators group a member of the Domain Admins account. One way of doing this is: 1. Start up Active Directory and Users 2. Go to the OU Container in which the Domain Admins account is in 3. Double click the Domain Admins account 4. Click on the Members tab 5. Click on Add and add the built-in Administrator group account 6. Ensure the domain account under which Cisco Unity is being installed belongs to the Domain Admins account.

CSCdz13475

3

Templates Callhandler 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."

There is no workaround.

CSCdz16187

3

CUCA should have logging. Symptom: The Cisco Unity Installation and Configuration Assistant has no logging. Condition: CUICA needs logging to aid in troubleshooting the problematic installations.

Workaround

Some of the wizards contained in CUICA do write to log files, such as the Permissions Wizard, Cisco Unity Setup and the Message Store Configuration Wizard. These, however, don't inform us of the CUICA's activities.

CSCdz16926

3

HTTP email played through TUI reads HTML tags to you.

Symptom: When Unity reads an email message using Text-to-Speech (TTS) over the telephone user interface (TUI), HTTP formatting tags are read as if they are text.

Conditions: Product is Unity for Domino (4.x). This does not occur for Unity for Exchange. The e-mail message originated from the Lotus iNotes client, which is the web-enabled version of the Lotus user client.

There is no workaround.

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. If you delete subscribers from this tool, a wizard will appear asking where to repoint any links that are pointing to the soon to be deleted subscriber. This only applies to Unity 4.0(x) and higher.

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 is the name of the service that has become unregistered). C:\CommServer> .exe -service The command should return without any output. Check the Services Administrative Tool to verify the service is now registered and running.

CSCdz50043

3

Faxing email fails with Omtool 3.2.6 with Genifax E2K fax connector.

CSCdz51904

3

Conversation should not go to failsafe if ForwardToFax fails.

CSCdz53581

3

Getting error "Exchange Server version is not Version 6.0 (Build 5762.4: Service Pack 2)" With Unity running Configuration Setup. Customer bringing up new E2K server off-box to work with Unity 3.1(5). When attempting to run Configuraton Setup,gets the following error in Tempu.log: ""Exchange Server version is not Version 6.0 (Build 5762.4: Service Pack 2)".

Some additional information: 1) Unity server was upgraded from 2.4.6 s/w. 2) After upgrade, E5.5 was removed from Unity server. This was due to all subscriber mailboxes had been on an off-box server, so when upgraded to 3.1(5), exchange no longer needed on box. 3) Was able to attach to off-box E5.5 server with no problems if the need had arose. 4) Neither the Unity server or E2k server were Domain Controllers."

CSCdz73330

3

AMIS: Incoming AMIS calls fail when not routed to a call handler.

Symptom: Incoming AMIS transmissions to Cisco Unity fail.

Condition: When Cisco Unity call routing rules are configured to force all direct calls to go to a conversation (such as the Sign In conversation) and not to a call handler (such as the Opening Greeting call handler), incoming AMIS transmissions fail. This is because the Cisco Unity AMIS session is designed to initiate with a fourth column tone handshake during a call handler. When an incoming AMIS call is not routed to a call handler, then Cisco Unity does not recognize the "C" tone from the originating system and does not respond appropriately, so the transmission is terminated.

Workaround: For AMIS Networking to be properly configured, you need to ensure that all incoming AMIS calls are routed to a call handler. When Cisco Unity is initially installed, the call routing table routes calls to the Opening Greeting call handler, so it is properly configured for AMIS Networking. If the call routing table has been modified after installation, you need to make sure that a rule is in place in your call routing table to route any incoming AMIS calls to a call handler.

CSCdz75004

3

Insufficient registry permissions prevents user creation. 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

In Unity 3.0, the new subscriber creation window comes up with blank values for the Exchange server and mailstore.

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

In Unity 4.0, when the new subscriber creation window comes up, instead of showing the various fields to fill in, this error is displayed, "Error fetching MailStore list (for server SERVERNAME). hr=0x80005000. Check that the AVDSGlobalCatalog is registered and running. Please see your system administrator for more details."

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.

CSCdz84779

3

In the Cisco Unity System Administrator, the 'Standard' transfer rule on the 'Call Transfer' page for the operator's call handler cannot be changed enabled or disabled. The HTML radio buttons are greyed out. Also, the status is always shows as 'enabled,' whether it is true or not.

Workaround:

The 'Standard' transfer rule is enabled by default. To disable the rule, use DohPropTest to edit the following property:

CallHandlers->operatorch->AVP_CONTACT_RULES->Standard->AVP_TIME_EXPIRES

When the rule is enabled, this property will not be set (it will have a value of 'empty'). If this value is set to a date and time, the rule will be disabled. An example of the date/time format can be copied from another rule (for example, 'Alternate') which is already disabled.

Note: DohPropTest is a low-level property editor, and requires technical assistance. Contact Cisco technical support before attempting to use it.

CSCdz84934

3

Calls to subscribers from the operator forward to the opening greeting instead of the subscriber voice mail.

Conditions:

Cisco Unity integrated with a Nortel PBX via a PBXLink SMDI integration. Although this problem was discovered and worked around in Cisco Unity 3.1.4, it would apply to any version of Cisco Unity integrating with a Nortel. It is also important in this scenario that the operator extension is 0.

Workaround:

The solution to the problem is a change to the PBXLink 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 reinitialize 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.

CSCdz86853

3

Cisco Unity Bulk Import (CUBI) wizard: License check should not apply to subs without mailbox.

Symptom: Cisco Unity Bulk Import Wizard reports Out of licenses. Only allowed to select subscribers for import. when importing VPIM, AMIS, Bridge or Internet subscribers. VPIM, AMIS, Bridge and Internet subscribers should not require a license.

This occurs with Cisco Unity 4.0(1) and 4.0(2) when using the Cisco Unity Bulk Import Wizard to import VPIM, AMIS, Bridge or Internet subscribers from.csv file where the number of records to import exceeds the number of available licenses on the Unity server. For Cisco Unity 4.0(1) this applies to both user and VMI licenses. For Cisco Unity 4.0(2) it only applies to VMI licenses.

Workaround

Cisco Unity subscriber licenses are not required for VPIM, AMIS, Bridge or Internet subscribers and will not be enforced once created. When the error appears at the selection screen indicating there are not enough licenses, reduce the selection to the number of records equal to or less than the number of available licenses and complete the import. The number of available licenses will not be decreased when completed. Run subsequent iterations of the import wizard to import the remaining records, each time selecting the number of records to import equal to or less than the number of available Cisco Unity subscriber licenses on the server.

CSCdz87175

3

Exceeded mbx limit conv 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 Message Editing 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.

CSCdz88921

3

Partial MAPI Notification outage breaks MWI.

Symptom: MWIs and Message Notification fail for a particular subscriber, and no MAPI table add or modified notifications are generated (Microtrace Exchange Monitor 13) when a new message is left for the subscriber. Sometimes, delete notifications 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

a. From Tools Depot, open the Bulk Logout utility.

b. Find the problem subscriber by extension number, and click Log Out Subscriber.

c. Then click 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 Cisco Unity version 3.1(5) and later, all users can be re-registered at once by stopping and starting the AvMsgStoreMonitor service. Note: A problem subscriber can not be re-registered for MAPI notification by a simple MWI refresh from the Cisco Unity Administrator.

CSCdz89153

3

Uninstall does not remove Unity.mdf file.

CSCea01229

3

When a call handler points back to itself, then Cisco Unity logs two event log errors (10020 and 10016) from AvConvMsg_MC. The second event log error message is for failsafe. The customer thinks something went wrong with Cisco Unity and system is causing a problem. This is expected behavior.

There is no workaround.

CSCea03097

3

Short name change on Domino server, is not reflected on Unity.

Symptom: If you change or add a short name on Domino server, Unity is supposed to pick up first shortname and use it for the subscriber. Right now, it is not working. Changes are not being reflected in Unity.

Workaround: None

CSCea03547

3

SA pages opened via links from tools are not logging off properly. During the course of using Cisco Unity tools and opening SA pages through links offered by these tools the Cisco Unity System Administrator returns the following error when an attempt is made to open it, "Access denied. You cannot access the Unity System Administrator. There are too many active sessions. Please try again later. Please see you system administrator for more details.

Workaround

The simplest workaround is to not use the links provided by the tools. If that is not acceptable either wait for the sessions to time-out (approx. 20 minutes) or restart the Cisco Unity server to clear the sessions.

CSCea06697

3

Realspeak License Does not Install Correctly. Symptom: About 50 systems licenses were sent out.

Workaround:

License group has sent out new licenses. If you run across one of these customer have them call the license group. Note: License tool has been repaired so this should be resolved.

CSCea06790

3

The section for Adding or Changing Unity Licensed Features should include the links to the section on how to actually add that feature.

CSCea14540

3

Call transfer is set to send callers to the subscriber greeting with the Cisco Unity Bulk Import wizard. When importing users from exchange from the SA page in Unity, in the SA settings for the subscribers the call transfer settings automatically revert to Yes, Ring Subscriber Extension, not Send To Subscriber's Greeting. Therefore when a non subscriber rings Unity he will hear the opening greeting (e.g. welcome to unity, from a touchtone telephone, you may dial an extension at any time). Dialing the extension will then ring the phone, you won't be forwarded into the greeting. So far so good.

When importing users from the Cisco Unity Bulk Import (CUBI) wizard (start/programs/Unity/Bulk Import Tool), intermittently the call transfer settings for the new subscriber are set to send to subscriber's greeting as opposed to Yes, ring subscriber extension changing the Call Transfer settings from send to subscriber's greeting to Yes, ring subscriber extension does not take effect (so after transferring the call the call will be transferred into the mail box of the subscriber instead of ringing the extension)

Workaround

Set the Call Transfer settings to Yes, ring subscriber at this number and then changing it back to yes, ring subscriber's extension.

CSCea14907

3

The Cisco Unity SA does not correctly show the search scope of a directory handler when it is set to search in a COS.

Workaround

Set the COS again if you are not sure if it is set to the correct value.

CSCea18998

3

Message Notification to work phone can cause failover to occur.

Symptom: In a failover environment, the secondary server becomes active for no apparent reason. Conditions: In a legacy failover environment, if a subscriber sets up message delivery to their work phone, and their work phone is set to forward no answer to VM. When a Unity port calls a work phone to notify the user of new messages, and the user does not answer, the call is forwarded to VM. The receiving VM port does not answer the call because Unity identifies the caller as another VM port (by default Unity does not answer calls from other VM ports to prevent one Unity port leaving a message for another). After three rings the failover server receives the incoming call and if configured to become active when it receives a call, failover occurs, needless to say the secondary does not answer this call either, but the secondary server is now the active server.

Workaround:

Disable Message Notification or do not configure failover to occur when the secondary server receives a call.

CSCea21398

3

Stop recording option under Configuration in SA ambiguous. Problem: Under Configuration > Recordings in SAWeb, the option for Stop Recording after how many seconds? is ambiguous. Does this mean Unity will stop recording a message after two seconds (the default for this setting)?

Workaround

None. This setting actually means that Unity will stop recording after X seconds *of silence*.

CSCea23105

3

Trying to add a user through the Cisco Unity Administrator and the following error is

encountered, "Error: illegal configuration: Server list cannot be empty in Active Directoryconfiguration. See Unity Troubleshooting Guide. The error message is not displayed in the Unity Troubleshooting Guide.

There is no workaround.

CSCea24153

3

LDAP synchronization warnings too generic for failed components

CSCea26260

3

Save Recording button on Media Master Control returns error. Symptom: When saving a recording that was taken using the Media Master Control in the Audio Text Manager the following error is given and the recording is not saved: "Error in cmdSubscriberRecord:Permission denied." Condition: Audio Text Manager with Cisco Unity 4.0(2).

Workaround

Use the SA to record the greeting of the object. A link to the SA is offered for each object in the Audio Text Manager under its Profile tab.

CSCea26848

3

NDRs presented as new voicemail over the TUI.

CSCea27535

3

Symptom: Cisco Unity hangs when CUSPA is stopping Cisco Unity services for the Service Pack 3 for SQL Server 2000 or MSDE 2000 install.

Condition: Cisco Unity 4.x is already installed and running when CUSPA attempts to stop Cisco Unity for the Service Pack 3 install.

Workaround

From a command prompt, go to the \Commserver directory and run kill -f av*. The Unity services should finish stopping and CUSPA will continue the installation of Service Pack 3.

CSCea35476

3

Call handlers created with invalid owner and recipient. When creating a call handler in 4.0(1) or the upcoming 4.0(2) release, both the owner and recipient values are always invalid. This results in the customer getting sent to failsafe when they access the handler over the phone.

Condition: The owner is not required in Unity unless you want to change the greeting for that handler from over the phone. The recipient, however, is always required to be a valid subscriber or distribution list. In 4.x this gets set to the installer account many times because it defaults to the user who authenticated in the SA.

Workaround

Always select the recipient on the call handler creation page before it's actually created.


Resolved Caveats—Release 4.0(2)

Table 7 contains only those Sev 1, Sev 2, and customer-found Sev 3 caveats resolved in the 4.0(2) release.

Table 7 Cisco Unity Release 4.0(2) Resolved Caveats 

Caveat Number
Severity
Description

CSCdz50889
CSCdz50952

3

Cisco Unity does not play voice messages - it jumps directly to the message footer after the message header. Also, the message waiting indicator (MWI) on the subscriber phone flashes on, then turns off spontaneously.

The subscriber workstation had the third-party product Command Anti-Virus for Windows installed. This product uses a MAPI scanner that sets the MAPI property AVP_MESSAGE_TYPE to 0 for voice messages. Setting this value prevents Cisco Unity from recognizing voice messages.

Workaround

Uninstall Command AntiVirus for Windows. Cisco does not support this product on subscriber workstations.

Refer to the "Unsupported Third-Party Software" section of the Cisco Unity 4.0 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.

CSCdv77509

2

JPN: Upgrade failed with corrupted msg while copying file

CSCdx12981

2

SA/AA: Schedule tables always displayed in 24-hour time format

CSCdx24379

3

Notification/private list is greyed out when COS has system access

CSCdx44689

3

FO: Ports remain registered after failover when 1 port locked

CSCdx61880

3

Loads Crashing - acmStreamClose failed with error(5)

CSCdx77631

2

SA Subs page times out in large system during wildcard Find

CSCdx95644

3

Unity Text-To-Speech feature does not "read" the From field when subscribers play their emails over the phone. Although the feature is designed this way to enhance TTS performance, this is regarded as a problem by customers because Cisco Unity does not identify the sender when it is someone who is not a Cisco Unity subscriber. When the message is from a subscriber, Cisco Unity either plays the name--if one is recorded, or the extension for that subscriber.

There is no workaround. The feature works as designed.

CSCdy01456

3

SA shows locked account as unlocked

CSCdy16295

3

FCW error messages should explain the problem clearly

CSCdy47698

3

No way to enforce installation of Ex2k SP2 during upgrade

CSCdz03192

3

Cannot import adofre15.reg error during Unity installation

CSCdz17817

3

Display error message when adding/importing user relevant to DSAD

CSCdz18621

2

MSCW: Exch permissions not checked for Dir svcs acct during upgrade

CSCdz23177

2

A reply voice message is not delivered if the original message is created in Lotus Notes client and the reply message is sent via phone.This defect exists in Cisco Unity 4.x. This defect will occur if the voice message is left using Notes client 5.0.10.

Workaround

a. Uninstall Lotus DUCs csClient via the Control Panel.

b. Uninstall the G.729 codec. Do not restart the workstation.

c. Uninstall the Lotus Notes client completely.

d. Install the Lotus Notes 5.0.11 client and configure it for the user.

e. Install Lotus DUCs csClient and the G729 codec, and restart the workstation when prompted.

CSCdz24111

3

Unity should better handle WAVs with bad RIFF header section lengths

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

CSCdz32613

2

UnityDb failed to upgrade schema from 3.1(3) to 4.0(0.267)

CSCdz33350

2

CUBI: Peer domains are not available for selection

CSCdz34690

2

"Notifications going out serially, performance slowed"

CSCdz34786

2

TTS RealSpeak fails to load if more than 9 languages are installed

CSCdz34890

3

Reply not always offered by conversation when using blind addressing

CSCdz37893

2

CiscoPCA access denied if user name or alias has non-ENU characters.

CSCdz38060

3

"Using Alternate Conversation, short cut to deleting messages fails"

CSCdz39131

3

"When trying to create Dist List with /, we get Unknown Error"

CSCdz48740

3

No reliable way to prevent RPC Hang at customer sites

CSCdz48747

2

Port hung with AvTTS_MC 1016 WavOutPlay WavOutClose app log error

CSCdz50076

2

DOM: Domino cluster support fails if clustermate name longer

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

CSCdz63531

2

CPCA:Recorded voice stream from Inbox fails due to server busy state

CSCdz64644

3

Disabled transfer rules are used when schedule not active

CSCdz64982

3

Greeting source set to blank plays the system greeting

CSCdz69110

3

Misconfigured DNS causes exception in MSCW (configuration setup)

CSCdz70810

3

Copy of switch file should be ignored.

CSCdz74361

3

AMIS: Extensive incoming macro trace should set more micro traces

CSCdz75891

3

Optional Conv: Confirm delete does not delete the message

CSCdz80608

2

SA: User added to Ex server get added to a different Ex server

CSCdz84755

3

Cisco Unity system connected to Domino server recognizes a forwarded fax message as e-mail. Cisco Unity conversation doesn't play a voice attachment for the message and doesn't present an option to send the message to a fax machine.

Workaround

If you are forwarding a fax message to another Unity subscriber via phone, don't record a voice introduction. If you are forwarding a fax message via Notes Client, don't add any attachments or text to the body of the message.If you have received a forwarded fax message and Cisco Unity recognizes it as e-mail, use Notes Client to check the message.

CSCdz85359

2

SA: Cannot choose Ex5.5 server to home user on

CSCdz85986

3

Conversation errors in Event viewer when in UMR mode

CSCdz89697

3

LogMgr should tolerate/report problems with reg diag grid

CSCea04029

2

Conversation fails to find language when building phrase

CSCea05124

2

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

CSCea06790

3

The upgrading or modifying a Cisco Unity 4.0 system section

CSCea06800

3

Step 4 in the task list

CSCea07024

3

SA: Failed extension change still updates contact rule table in error

CSCea08124

2

Miu timing errors with SerialAutoAnswer/WaitIfBufferedPacketPresent

CSCea12285

3

Subscriber deletes leave orphaned alternate extensions on remote sys

CSCea16589

2

CiscoPCA is not installed using Unity 4.0(1) release DVD

CSCea19380

2

JPN: SA subscriber page cannot open with error (SaConstInc.asp)

CSCea21953

3

Unity 4.0 support of Exchange 5.5 ambiguous.

CSCea24768

3

SAG online help is incorrect for directory handler match list options.


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.

Obtaining License Files for Additional Features: Cisco Unity Installation Guide

The "Obtaining Cisco Unity License Files" section in the "Modifying the Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide, Release 4.0(x) incorrectly instructs you to use the product authorization key (PAK) listed in the Cisco Unity Software Keys booklet that is shipped with the software discs.

Instead, when you provide registration information on Cisco.com, you use the PAK from the claim certificate that Cisco sent when the additional features were purchased.

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.

Creating an Integration for a Circuit-Switched Phone System: Cisco Unity Integration Guides

In the procedure "To Create an Integration" in the "Creating a New Integration with the Phone System" section of the Cisco Unity integration guides for circuit-switched phone systems, the Configuration File field should appear in the table listing the settings for the Select Phone System Manufacturer page of the Cisco Unity Telephony Integration Setup wizard.

Table 8 includes the revisions to the table.

Table 8 Settings for the Select Phone System Manufacturer Page 

Field
Setting

Manufacturer

<The name of the manufacturer of the phone system>

Model

<The model of the phone system>

Software Version

<The software version installed on the phone system>

Configuration File

<If you have made copies of the .ini configuration file, the name of the configuration file you want to use>


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.

Determining the Cause of Failover or Failback: Cisco Unity Failover Configuration and Administration Guide

The table in the section "Determining the Cause of Failover and Failback" of the Cisco Unity Failover Configuration and Administration Guide should include the following information in the last row (the primary server has event ID 1048, and the secondary server has event ID 1050, 1047, and CiscoUnity_Miu 542) for the causes of failover or failback:

A caller dialed the extension of a voice messaging port in the secondary server and the Force Failover If Call Arrives on Inactive Secondary check box is checked in the Failover Monitor, causing failover to occur.

(Circuit-switched phone systems) For phone systems that use a linear hunt group (the hunt group starts searching always with the same voice messaging port), an unintended failover may occur when the Force Failover If Call Arrives on Inactive Secondary check box is checked in the Failover Monitor. With this configuration, if a call to Cisco Unity is terminated either before being answered or within a few seconds after being answered by the primary server, the phone system may route a second call immediately to the same port causing the secondary server to count rings from both calls as a single call thus triggering failover.

This cause can be eliminated by setting up a "guard timer" (a timer that enforces a minimum interval between consecutive calls sent to a given port) on the phone system. This timer may not be available on all phone systems.

Viewing License Pooling Information: Cisco Unity System Administration Guide

The following procedure for viewing Cisco Unity license pooling information was not included in the "Maintaining Cisco Unity" chapter of the Cisco Unity System Administration Guide.

To view the license pooling information


Step 1 On a Cisco Unity server where pooling is enabled, double-click the Cisco Unity Tools Depot icon on the desktop.

Step 2 Under Administration Tools, double-click License Info Viewer.

Step 3 Under Cisco Unity Licensing, double-click License Pool.

Step 4 In the right pane, double-click the pooled feature to view the Cisco Unity servers that are contributing and using licenses for the feature.


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/prod_troubleshooting_guides_list.html.

At the Cisco TAC website http://www.cisco.com/en/US/support/index.html.

Installing a Cisco Unity 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. A demonstration system uses one of two different license files:

Default license file (available on the Cisco Unity server).

Time-limited license file (must be ordered from Cisco).


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. Cisco TAC does not provide support for Cisco Unity demonstration systems.


The software for a demonstration system can be ordered online. The orderable demonstration system is the easiest way to get an entire set of the discs, including third-party software (except Windows 2000 Server). It is available at http://www.cisco.com/go/marketplace.

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.

To enable the demonstration system, see the applicable section, depending on which license file you are using:

"Enabling a Cisco Unity Demonstration System with the Default License File" section.

"Enabling a Cisco Unity Demonstration System with the Time-Limited License File" section.

See also the "Converting a Cisco Unity Demonstration System to a Standard System" section, if applicable.

Limits on a Cisco Unity Demonstration System

Depending on the type of license file you use—Default License File or Time-Limited License File—the Cisco Unity demonstration system will have the limits listed below.

Default License File

6 languages

2 RealSpeak text-to-speech (TTS) sessions

10 mailboxes for one of the following subscriber types:

Unified Messaging (UM) subscribers

Voice Messaging (VM) subscribers

10 Cisco Unity Inbox subscribers

2 voice ports

30-second limit for messages

The ability to integrate with any supported phone system

Time-Limited License File

The time-limited license enables either Unified Messaging (UM) or Voice Messaging (VM) with the following limitations:

UM feature package

50 UM subscribers with 16 sessions

2 RealSpeak text-to-speech (TTS) sessions

2 languages

AMIS

4 voice messaging ports

VM feature package

50 VM subscribers with 16 sessions

2 RealSpeak text-to-speech (TTS) sessions

2 languages

25 Cisco Unity Inbox users

4 voice messaging ports

The time-limited license includes the following additional limitations:

Time limit (after which Cisco Unity stops handling calls)

60 days

90 days

Only one license file on the Cisco Unity server is permitted

Non-renewable

Locked to the specific MAC address of the network interface card (NIC) on the Cisco Unity server

The ability to integrate with any supported phone system

Enabling a Cisco Unity Demonstration System with the Default License File

The default license file (CiscoUnity40.lic) is automatically copied to the Cisco Unity server during installation.

To enable a demonstration system with the default license file


Step 1 Install Cisco Unity as described in the Cisco Unity Installation Guide—up to the point where the Install the Cisco Unity License Files screen appears in the main window of the Cisco Unity Installation and Configuration Assistant.

Step 2 Click Run the Cisco Unity Install License File Wizard.

Step 3 On the Welcome screen of the wizard, click Next.

Step 4 Click Add.

Step 5 Browse to the CommServer\Licenses directory, and double-click CiscoUnity40.lic.

Step 6 Click Next.

Step 7 In the Licenses list, confirm that the license information is correct.

Step 8 Click Next.

Step 9 Click Finish.

Step 10 Continue following the instructions in the Cisco Unity Installation Guide to complete the installation.


Enabling a Cisco Unity Demonstration System with the Time-Limited License File

Do the following three procedures to obtain a time-limited license file and enable a Cisco Unity demonstration system.

To get the MAC address of the Cisco Unity computer


Step 1 On the computer where Cisco Unity will be installed, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Step 2 In the Command Prompt window, enter ipconfig /all, and press Enter.

Step 3 Write down the value for Physical Address, excluding the hyphens (for example, if the physical address is 00-A1-B2-C3-D4-E5, record 00A1B2C3D4E5), or save it to a file that you can access during online registration.

If the server contains more than one NIC, one value will appear for each NIC. Use the value for the primary NIC.

Step 4 Close the command prompt window.


To register and obtain the license files


Step 1 Browse to the applicable software registration site (URLs are case sensitive):


Step 2 In the Voice Products section, under Cisco Unity Software, click 4.0 New Install & Add-On Feature Licenses.

Step 3 Enter the requested information, and click Submit.

Step 4 You will receive an e-mail with the Cisco Unity license file.


To install license files


Step 1 Install Cisco Unity as described in the Cisco Unity Installation Guide—up to the point where the Install the Cisco Unity License Files screen appears in the main window of the Cisco Unity Installation and Configuration Assistant.

Step 2 Click Run the Cisco Unity Install License File Wizard.

Step 3 On the Welcome screen of the wizard, click Next.

Step 4 Click Add.

Step 5 Insert the Cisco Unity license file disk, if applicable.

(When Cisco Unity was registered on Cisco.com, Cisco replied with an e-mail containing an attached file with licenses for Cisco Unity features. The instructions in the e-mail directed that the attached file be saved.)

Step 6 Browse to drive A or to the location where the license files have been stored.

Step 7 Double-click the file to add it to the License Files list.

If prompted, click Yes to copy the license file to the local system.

Step 8 Click Next.

Step 9 In the Licenses list, confirm that the license information is correct.

Step 10 Click Next.

Step 11 Click Finish.

Step 12 Continue following the instructions in the Cisco Unity Installation Guide to complete the installation.


Converting a Cisco Unity Demonstration System to a Standard System

Do the following procedure after you have ordered and received the license file for a standard Cisco Unity system.

To convert a demonstration system to a standard system


Step 1 Log on to Windows by using the Cisco Unity installation account.

Step 2 Exit the Cisco Unity software.

Step 3 Double-click the Cisco Unity Tools Depot icon on the desktop.

Step 4 Under Administration Tools, double-click License File Install Wizard.

Step 5 On the Welcome screen of the wizard, click Next.

Step 6 Click the name of the demonstration license file (CiscoUnity40.lic or the time-limited license file), and click Delete to remove the demonstration license file from the list. (The file will not be deleted from your local system.)

Step 7 Click Add.

Step 8 Insert the Cisco Unity license file disk, if applicable.

(When Cisco Unity was registered on Cisco.com, Cisco replied with an e-mail containing an attached file with licenses for Cisco Unity features. The instructions in the e-mail directed that the attached file be saved.)

Step 9 Browse to drive A or to the location where the license files have been stored.

Step 10 Double-click the license file to add it to the License Files list.

If prompted, click Yes to copy the license file to the local system.

Step 11 If you are adding more than one license file, click Add, and repeat Step 9 and Step 10 for each license file.

Step 12 Click Next.

Step 13 In the Licenses list, confirm that the license information is correct.

Step 14 Click Next.

Step 15 Click Finish.

Step 16 Restart the Cisco Unity server.

Step 17 If you are not adding voice ports, skip to step 19.

Otherwise, provide additional ports for the Cisco Unity system. The way you provide additional ports depends on the type of phone system integration you have:

Cisco CallManager
integration

a. In the Cisco CallManager Administrator, add the ports to the voice mail server that the Cisco Unity server uses. Refer to the Cisco CallManager Administration Guide.

b. For the new ports, set the Forward Busy and Forward No Answer fields so incoming calls are forwarded only to ports that will answer calls. Refer to the procedure "To set up voice mail ports so incoming calls are forwarded only to answer ports" in the applicable Cisco CallManager integration guide. If Cisco Unity is configured for failover, refer to the procedure "To set up the secondary server for failover" in the applicable Cisco CallManager integration guide.

Circuit-switched phone
system integration

a. Program the phone system to enable the new ports and to send incoming calls only to ports that will answer calls. Refer to the documentation for the phone system.

b. On the Cisco Unity server, install the voice cards. See the "Adding, Exchanging, or Removing Voice Cards" section in the "Modifying the Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide.


Step 18 Configure Cisco Unity to use the additional ports:

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

b. Under Switch Integration Tools, double-click Telephone Integration Manager.

c. In the left pane, click <Integration name>.

d. In the right pane, click <Phone system name>.

e. Click the Ports tab.

f. Click Add Port.

g. Enter the settings for the voice messaging ports. See the procedure "To enter the voice messaging port settings for the integration" in the applicable Cisco Unity integration guide.

h. When prompted, restart the Cisco Unity server.

Step 19 If you are not adding languages or the RealSpeak text-to-speech engine, you are finished converting the demonstration system to a standard system.

If you are adding languages or the RealSpeak text-to-speech engine, install the feature files and enable the feature(s):

a. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server, disable virus-scanning services and set the IDS Host Sensor Agent to run in On-Warning mode. Refer to the "Setting Security-Monitoring Software Before Running the Installation Programs" section of the "Customizing the Cisco Unity Platform" chapter of the Cisco Unity Installation Guide.

b. On the Cisco Unity DVD or CD 1, or from the location to which you saved the downloaded Cisco Unity CD 1 image files, browse to the root directory and double-click Setup.exe.

c. If prompted, double-click the language of your choice to continue the installation.

d. On the Summary screen, click Add or Change Cisco Unity Features.

e. Follow the on-screen prompts until the Select Features dialog box appears.

f. In the Select Features dialog box, check the Upgrade Cisco Unity check box.

g. Check the Enable TTS check box, if applicable.

h. Uncheck the Install Voice Card Software check box.

i. Click Next.

j. Choose the prompt set to install, and click Next.

k. In the Cisco Unity Languages dialog box, choose the language(s) to install, and click Next.

Note that if you are using text to speech (TTS) and are using Australian English or New Zealand English as the phone language, also install U.S. English or UK English for the TTS language.

l. Set the default languages for the phone, GUI, and TTS, and click Next.

m. Follow the on-screen prompts until you are prompted to restart the Cisco Unity server.

n. Check the Yes, I Want to Restart My Computer Now check box, and click Finish.

The Cisco Unity Installation and Configuration Assistant displays check marks next to "Install Cisco Unity" and "Install the Cisco Unity License Files," and the Configure the Cisco Unity Services screen appears in the main window.

o. In the main window of the assistant, click Run the Cisco Unity Services Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

p. On the Welcome screen, click Next.

q. Select the message store type, and click Next.

r. Follow the on-screen prompts to complete the configuration.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Services," and the Configure the Cisco Unity Message Store screen appears in the main window.

s. In the main window of the assistant, click Run the Cisco Unity Message Store Configuration Wizard. (Note that you should be logged on to Windows with the Cisco Unity installation account.)

t. Confirm that the message store server is running. If the message store server is not running, configuring the message store will fail.

u. On the Welcome screen, click Next.

v. Follow the on-screen prompts.

w. When message store configuration is complete, click Finish.

The Cisco Unity Installation and Configuration Assistant displays a check mark next to "Configure the Cisco Unity Message Store."

x. When the Summary screen appears, click Close.

y. If virus-scanning software or the Cisco IDS Host Sensor Agent is installed on the Cisco Unity server, re-enable virus-scanning services and reset the IDS Host Sensor Agent to run in On-Protecting mode. Refer to the "Resetting Security-Monitoring Software After the Installation Programs Have Been Run" section of the "Installing and Configuring Cisco Unity Software" chapter of the Cisco Unity Installation Guide.

z. Make the feature available for use:

Languages

Refer to the "Multiple Languages" chapter of the Cisco Unity System Administration Guide on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guides_list.html.

TTS

Put subscribers in a class of service (COS) that includes TTS. Refer to the "Class of Service Settings" chapter of the Cisco Unity System Administration Guide on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guides_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 on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Obtaining Documentation

Cisco provides several ways to obtain documentation, 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

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

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

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 Networking Products MarketPlace:

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, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments 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

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

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

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

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

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

Priority level 1 (P1)—An existing 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.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

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

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

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

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

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

Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

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

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://www.cisco.com/en/US/products/products_catalog_links_launch.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. 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/go/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/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

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

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html