Guest

Cisco Unity

Release Notes for Cisco Unity Releases 5.0(1) and 5.0(1a)

  • Viewing Options

  • PDF (971.6 KB)
  • Feedback
Release Notes for Cisco Unity Releases 5.0(1) and 5.0(1a)

Table Of Contents

Release Notes for Cisco Unity Releases 5.0(1) and 5.0(1a)

Contents

System Requirements

Compatibility Information

Determining the Software Version

Cisco Unity

Cisco Unity-CM TSP

Cisco Unity Voice Connector for Microsoft Exchange

Active Directory Schema Extensions for Cisco Unity with Exchange

G.729a Audio Codec

Cisco Personal Communications Assistant

Cisco Unity ViewMail for Microsoft Outlook

Related Documentation

New and Changed Requirements and Support—Release 5.0(1)

Active Directory 2008 Global Catalog Servers May Require Registry Changes

Active Directory 2008 R2 Is Supported

Active Directory Schema Extensions Required for Cisco Unity with Exchange

Available Languages for Cisco Unity Components

Cisco Unity Release 5.0(1a)

Cisco Unity with Domino: Lotus Domino 6.0 and Notes 6.0 Are Not Supported for New Installations of Cisco Unity 5.0(1)

Cisco Unity with Exchange: Changing the Partner Exchange Server from Exchange 2007 to Exchange 2003 or 2000 Is Not Supported

Cisco Unity with Exchange: Cisco Unified Personal Communicator

Cisco Unity with Exchange: Exchange Server 2010

Cisco Unity with Exchange: Exchange Server 2007

Cisco Unity-CM TSP Version 8.2(1)

Cisco Unity Documentation

Cisco Unity User Guide

Cisco Unity Integration Guides

Interface Reference Guide for the Cisco Unity Administrator

Cisco Unity Voice Connector for Microsoft Exchange 2003/2000 Version 12.0(1)

Failover When Cisco Unity Servers Are Separated by a Firewall

IMAP and Cisco Unity Inbox Limits Increased for Selected Servers

Microsoft Service Packs Required with Cisco Unity

Mobile Message Access for BlackBerry Available for Use with Cisco Unity Unified Messaging with Domino

Mobile Message Access for BlackBerry Version 1.0(1) Is No Longer Supported

Phone System Integrations Qualified for Use with Cisco Unity

Software Qualified for Use on Cisco Unity Subscriber Workstations

Software That Is No Longer Supported for Use on Cisco Unity Subscriber Workstations

Standby Redundancy

Utility Updates in the Cisco Unity Tools Depot

New Functionality—Release 5.0(1)

Cisco Unity Conversation Enhancements

Cisco Unity with Domino: Full Mailbox Warnings

Cisco Unity with Domino: Full Mailbox Check When an Outside Caller Attempts to Leave a Message

Configuring the Behavior for Replying to All Recipients of a Message

Conversation Settings Added to the Cisco Unity Assistant

Conversation Timeout Setting Added to Cisco Unity Administrator

Custom Keypad Mapping Conversations Can Be Reset to Cisco Internal Mappings

Customizing the Subscriber Setup Options Menu

Dropped Call Recovery

Offering More Options at the Main Menu

Offering the Option to Revert to Default Message Playback Speed

Press-or-Say Phone Input Style

Specifying Per Subscriber the Addressing Order When Sending or Forwarding Messages

Specifying Per Subscriber the Amount of Time to Skip Back or Ahead When Rewinding or Fast-Forwarding Messages

Specifying Per Subscriber the Conversation Styles Offered in the Cisco Unity Assistant

Specifying Per Subscriber Whether Messages Are Sent Upon Hang-Up

Spoken Commands

Cisco Unity Feature Scripts

Cisco Unity with Exchange: Message Store Configuration Wizard Prompts You to Enable Circular Logging

Cisco Unity with Exchange: Trusted Internet Subscribers and Trusted Internet Locations

Cisco Unity with Exchange: Using Logon Credentials from Active Directory Accounts in a Different Forest

Custom Key Map Wallet Card Wizard Enhancements

Distribution of Microsoft Updates Recommended for Use with Cisco Unity

Monitoring Messages Remotely

Phone View Features

Simulating Abbreviated Extensions

Subscriber Partitioning for Message Addressing by Phone

Tracking Unified Messaging Subscribers

Voice Recognition

Changed Functionality—Release 5.0(1)

Cisco Unity Conversation Changes

Conversation Behavior for Replying to All Recipients of a Message

Conversation Settings Removed from Advanced Settings Tool

Custom Key Map Conversations Preserved During an Upgrade

Cisco Unity Assistant: Send Message Style Setting Moved to the Phone Menu Preferences Page

Menu Repeats

Specifying the Transfer Settings for Alternate Contact Numbers

Switching Search Mode by Pressing ## or 00

Cisco Unity with Exchange: Create Cisco Unity Subscribers with Disabled Active Directory Accounts

Cisco Unity with Exchange: Private Secure Messaging

Diagnostic Improvements

Message Notifications and Message Waiting Indicators

Multiple Transfer Rules

On-Box Message Store with Failover for Cisco Unity Voice Messaging Configuration

Phone System Integrations Limited Only by Licensed Ports

QoS Setting Is Configurable

Route Forwarded Calls by the First or Last Redirecting Number

SMTP Networking Not Supported (Cisco Unity With Microsoft Exchange Only)

Support for Up to 144 Voice Messaging Ports

Tempu Logs Provide a History of Each Installation and Upgrade

Installation and Upgrade Information

Downloading Software for Cisco Unity 5.0(1)

Upgrading to Cisco Unity 5.0(1)

Installing Cisco Unity 5.0(1) for the First Time

Installation and Upgrade Notes

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

Customizing Cisco Unity System Prompts Is Not Supported

Example Subscriber Account Is Not Created During Cisco Unity Installation

Navigation Pane May Be Blank When Viewing the Cisco Unity Administrator in Japanese

Permissions Wizard Causes a Spike in Processing on All Domain Controllers in the Domain (Cisco Unity with Exchange Only)

Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter

Upgrade from Cisco Unity 4.x Requires an Upgrade License

Upgrade from Cisco Unity 4.0(2) or Earlier to Version 5.0(1) Requires Reactivation of Optional Conversation 1

Using Chinese-PRC, Chinese-Taiwan, Chinese-Hong Kong SAR, Japanese, and Korean Text to Speech

Limitations and Restrictions

Cisco Unity with Domino: Phone Recording and Playback Does Not Work in IBM Lotus Notes with DUC for Cisco 1.2.4 or 1.2.5

Cisco Unity with Exchange: Subscriber Lookups Fail to Find Subscriber Names in Japanese

Delay When Subscribers Press 00 to Switch Search Modes in Cisco Unity Conversation

Message Monitor Cannot Be Enabled or Disabled for Individual Subscribers in Cisco Unity Administrator

Remote Desktop

Replacing Disks in a RAID

Text to Speech Does Not Read Name in the From Field in E-Mail

Web Pages That Contain the Media Master Control Bar Do Not Load Properly When Google Desktop Search Is Installed

Windows Application Event Log May Not Display Third-Party Product Name in Start-Up Log Entry

Windows Terminal Services

Caveats

Open Caveats—Releases 5.0(1) and 5.0(1a)

Resolved Caveats—Releases 5.0(1) and 5.0(1a)

Documentation Updates

Errors

Cisco Unity Installation Guides for Cisco Unity 5.x: Making the Cisco Unity Server a Domain Controller in a Failover Configuration

Failover Configuration and Administration Guide for Cisco Unity Release 5.x: Behavior of Cisco Unity Failover During Outages of Network Components

System Administration Guide for Cisco Unity: Phone View Features

Omissions

Cisco Unity Integration Guides: Planning How the Voice Messaging Ports Will Be Used by Cisco Unity

Installation Guide for Cisco Unity Release 5.x with IBM Lotus Domino: Installing and Configuring Cisco Unity Software

Installation Guide for Cisco Unity Release 5.x in a Voice Messaging Configuration with Microsoft Exchange: Overview of Mandatory Tasks for Installing Cisco Unity

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Adding Features to the Cisco Unity 5.x System

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Changing the Codec Format of System Prompts

Reconfiguration and Upgrade Guide for Cisco Unity (With IBM Lotus Domino): Upgrading the Domino Environment

Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Server from an Exchange 2000 or 2003 Server to an Exchange 2007 Server for Cisco Unity 5.x

Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Exchange Server from an Exchange 2000 Server to an Exchange 2003 Server for Cisco Unity 5.x

SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express

System Administration Guide for Cisco Unity: Phone View Features

System Administration Guide for Cisco Unity: Disabling Voice Recognition for All Subscribers

System Administration Guide for Cisco Unity: SMTP Message Notifications

Troubleshooting Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Subscriber and Administrator Access

Troubleshooting Information

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

Upgrading a Cisco Unity 4.x Demonstration System to a Cisco Unity 5.0(1) Demonstration System

Converting a Cisco Unity Demonstration System to a Standard System

Installing and Configuring Voice-Recognition Software on a Cisco Unity Server for Demonstration Purposes Only

Removing Voice-Recognition Software from the Cisco Unity Server

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Unity Releases 5.0(1) and 5.0(1a)


Revised April 4, 2012 (Originally published May 31, 2007)

These release notes contain information on downloading software, new and changed support, new and changed functionality, limitations and restrictions, and open and resolved caveats for Cisco Unity Releases 5.0(1) and 5.0(1a).

***********************************************************************************************************************

Release 5.0(1a) contains a fix for one defect that affected upgrades from Cisco Unity 4.x to version 5.0(1). (See the "Cisco Unity Release 5.0(1a)" section.) Nothing else is different.

Note the following information:

Release 5.0(1a) contains no engineering specials (ESes). With the exception of the one defect fix, it is the same as the 5.0(1) base.

Follow the Cisco Unity documentation regarding any 5.0(1) ESes. You use the same ESes with 5.0(1a).

Anything documented as compatible with Cisco Unity 5.0(1)—for example, Cisco Unity versions and tools, and other Cisco products—are equally compatible with 5.0(1a).

You need to use the renumbered Cisco Unity 5.0(1a) DVD 1 or the downloaded disc image only if you are upgrading from a version earlier than 5.0(1). (If you are installing a new 5.0 system, you can use either the 5.0(1) or 5.0(1a) media.)

***********************************************************************************************************************


Note Items in release notes may be added, or revised to correct or clarify information after the initial publication date (the date the software was released). When an item has been changed, the phrase "Added <date>" or "Revised <date>" is included in the text of the item.


Contents

These release notes contain the following sections:

System Requirements

Related Documentation

New and Changed Requirements and Support—Release 5.0(1)

New Functionality—Release 5.0(1)

Changed Functionality—Release 5.0(1)

Installation and Upgrade Information

Limitations and Restrictions

Caveats

Documentation Updates

Troubleshooting Information

Installing a Cisco Unity Demonstration System

Installing and Configuring Voice-Recognition Software on a Cisco Unity Server for Demonstration Purposes Only

Obtaining Documentation and Submitting a Service Request

System Requirements

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

System Requirements for Cisco Unity Release 5.0

System Requirements, and Supported Hardware and Software for Cisco Unity Bridge 3.1

Networking Options Requirements for Cisco Unity

Compatibility Information

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

Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations

SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express

SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express

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

Active Directory Schema Extensions for Cisco Unity with Exchange

G.729a Audio Codec

Cisco Personal Communications Assistant

Cisco Unity ViewMail for Microsoft Outlook

Cisco Unity

To Determine the Cisco Unity Version in Use by Using the Gather Unity System Info Utility (Cisco Unity 5.0(1a) Only)


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

Step 2 In the left pane, under Reporting Tools, double-click Gather Unity System Info.

When version 5.0(1a) is installed, the following line will appear in the Unity Install Information section:

Unity version = 5.0(1.0) (A Version)


To Determine the Cisco Unity Version in Use by Using the UpgradeDatabase_003_021.sql File (Cisco Unity 5.0(1a) Only)


Step 1 Browse to the Localize\DefaultConfiguration\<three-letter language abbreviation> directory.

(For example, on a system on which U.S. English is installed, browse to the Localize\DefaultConfiguration\ENU directory.)

Step 2 The installed version can be determined by the date of the UpgradeDatabase_003_021.sql file:

December 4, 2008

The version of Cisco Unity installed is 5.0(1a).

June 4, 2007

The version of Cisco Unity installed is 5.0(1).



To Determine the Cisco Unity Version in Use by Using the Cisco Unity Administrator (5.0(1) Only)


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.


Cisco Unity-CM TSP

To Determine the Cisco Unity-CM TSP Version in Use by Using the Cisco Unity Telephony Integration Manager


Step 1 On the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.

Step 2 In the left pane, click the Cisco Unified CM integration.

Step 3 In the right pane, click Properties. On the Integration tab, 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 applicable directory, depending on the Windows version:

Windows 2003

Windows\System32 directory

Other versions

WinNT\System32


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

Exchange 2000
or Exchange 2003

<ExchangeServerPath>\VoiceGateway\Bin

Exchange 5.5

<ExchangeServerPath>\Connect\Voice\Bin


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

Step 4 Click the Version tab in the Properties window.

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


To Determine the Voice Connector Version in Use: Cisco Unity 3.0 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 applicable directory:

Exchange 2000

<ExchangeServerPath>\VoiceGateway\Bin\LocalizedFiles\ENU

Exchange 5.5

<ExchangeServerPath>\Voice\Bin\LocalizedFiles\ENU


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

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


Active Directory Schema Extensions for Cisco Unity with Exchange

To View the Version of the Schema Extensions


Step 1 On the desktop of the server on which ADSchemaSetup was run, open the folder Ldif logs.

This folder contains subfolders that are named based on the date on which ADSchemaSetup was run.

Step 2 Open the folder named with the most recent date.

This folder contains a separate folder for Avdirmonex2k.ldf (Cisco Unity schema extensions), Omnigateway.ldf (Cisco Unity Bridge extensions), and Vpimgateway.ldf (VPIM extensions).

Step 3 Open the folder for the appropriate type of schema extensions, and open the file Ldif.log in Notepad.

Step 4 Scroll to the end of the file, and click the last line. There is more than one instance of cisco-Ecsbu-UM-Schema-Version in the file, and you need to locate the last instance that contains a version description.

Step 5 Click Edit > Find, enter cisco-Ecsbu-UM-Schema-Version, and click Up for the direction of the search.

Step 6 Click Find Next one or more times until you find an instance that is followed a few lines down by a line containing the word "Description" and one of the following, as applicable:

Cisco Unity <version>

Cisco Unity Bridge <version>

Cisco Unity VPIM <version>

Note that the version displayed is the Cisco Unity version when the LDIF file was last modified, which may be older than your Cisco Unity version.

The following example shows two parts of an ldif.log file for the Avdirmonex2k.ldf extensions for a server that was installed using a version 4.2(1), and then upgraded to 5.0(1):

51: CN=cisco-Ecsbu-UM-Schema-Version,CN=Schema,CN=Configuration,DC=Media,
	DC=cisco-uty-123456,DC=cisco,DC=com
Entry DN: CN=cisco-Ecsbu-UM-Schema-Version,CN=Schema,CN=Configuration,DC=Media,
	DC=cisco-uty-123456,DC=cisco,DC=com
change: modify
Attribute 0) Description:Unity 4.2
 
   
Attribute or value exists, entry skipped.
 
   
...
 
   
106: CN=cisco-Ecsbu-UM-Schema-Version,CN=Schema,CN=Configuration,DC=Media,
	DC=cisco-uty-123456,DC=cisco,DC=com
Entry DN: CN=cisco-Ecsbu-UM-Schema-Version,CN=Schema,CN=Configuration,DC=Media, 
	DC=cisco-uty-123456,DC=cisco,DC=com
change: modify
Attribute 0) Description:Cisco Unity 5.0
 
   
Entry modified successfully.

G.729a Audio Codec

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

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


Step 1 Browse to the applicable directory, depending on the Windows version:

Windows 2003

Windows\System32 directory

Other versions

WinNT\System32


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.


Cisco Personal Communications Assistant

To Determine the Cisco Personal Communications Assistant (PCA) Version in Use


Step 1 On the subscriber workstation, log on to the Cisco PCA.

Step 2 Browse to the Cisco Unity Assistant or the Cisco Unity Inbox, as applicable.

Step 3 On any page, click Help.

Step 4 Click the About Cisco Unity topic link on the menu.

The Cisco Unity version is displayed. The Cisco PCA version is the same as the Cisco Unity version.


Cisco Unity ViewMail for Microsoft Outlook

There are two ways to determine the version of ViewMail in use on a subscriber workstation. Do either procedure, as applicable.

To Determine the ViewMail Version in Use from Add/Remove Programs (ViewMail version 4.05 and Later Only)


Step 1 On the Windows Start menu on the subscriber workstation, click Settings > Control Panel > Add/Remove Programs.

Step 2 In the Currently Installed Programs list, find ViewMail for Outlook.


To Determine the ViewMail Version in Use from Outlook


In the Outlook Inbox on the subscriber workstation, on the Help menu, click About ViewMail.


Related Documentation

For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to the Documentation Guide for Cisco Unity. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.html.

New and Changed Requirements and Support—Release 5.0(1)

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

Active Directory 2008 Global Catalog Servers May Require Registry Changes

Added June 9, 2010

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 5.0 server is accessing an Active Directory 2008 (including R2) global catalog server (GC), a change to the registry on the GC may be required. For information on determining whether the change is required and, if so, how to make the change, see the "Troubleshooting Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Subscriber and Administrator Access" section under "Documentation Updates."

Active Directory 2008 R2 Is Supported

Revised April 4, 2012

The Cisco Unity server can be a member server in an Active Directory 2008 R2 domain in either Unified Messaging or Voice Messaging configurations. All domain and forest functional levels are supported, including the levels formerly known as mixed mode and native mode. Note the following:

You must install Cisco Unity 5.0 Engineering Special 85 or later on the Cisco Unity server.

Engineering specials are available at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240. (From the Downloads page, expandProducts > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 5.0 > Unity System Software.)

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 5.0 server is accessing an Active Directory 2008 (including R2) global catalog server (GC), a change to the registry on the GC may be required. For information on determining whether the change is required and, if so, how to make the change, see the "Troubleshooting Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Subscriber and Administrator Access" section.

Before you make the Cisco Unity server a member server in an Active Directory 2008 R2 domain, you must install a Microsoft patch on all Active Directory 2008 R2 domain controllers in the forest. The patch, which is available from Microsoft, is associated with Microsoft Knowledge Base article 977180, "Error message when an application or a service tries to query for any deleted objects by using a well-known GUID in a Windows Server 2008 R2-based domain if paged search is used: `0x8007202c Critical extension is unavailable.'"

If you use the new Active Directory 2008 R2 recycle bin feature to restore the Active Directory account for a Cisco Unity subscriber, additional steps are required to reassociate the account and the subscriber. Use the Remove Subscriber Properties tool from CiscoUnityTools.com to remove all Cisco Unity properties from the Active Directory account, reimport the Active Directory account into Cisco Unity, and restart the Cisco Unity server. Messages for the subscriber are retained, but Cisco Unity properties for the user must be reset.

Active Directory Schema Extensions Required for Cisco Unity with Exchange

Several Cisco Unity-specific attributes, an Aux class, and a Structural class were added to Avdirmonex2k.ldf, and the schema was extended in ways that will reduce the need for further schema extensions in the future. For more information, see the white paper Cisco Unity Data and the Directory (All Versions with Microsoft Exchange) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

For Omnigateway.ldf (Bridge Connector) and Vpimgateway.ldf (VPIM Connector), only the version number was changed. However, if the Active Directory schema was extended for Bridge Networking and/or VPIM Networking in the past and you do not extend the schema with the corresponding Cisco Unity 5.0(1) changes, the Cisco Unity Permissions wizard will not let you proceed.

The 5.0(1) extensions must be applied to the Active Directory schema when installing or upgrading to Cisco Unity 5.0(1):

When installing a new Cisco Unity 5.0(1) server, the new schema extensions are applied as part of the schema update you perform during the installation process, as described in the Installation Guide for Cisco Unity.

When upgrading a Cisco Unity server to version 5.0(1), the schema updates must be applied at a specific point during the upgrade process. Follow the instructions in the Reconfiguration and Upgrade Guide for Cisco Unity that apply to your upgrade situation.

Note that the changes are backward compatible with earlier versions of Cisco Unity. If you have multiple servers connected through Digital Networking, you can apply the required schema updates in order to upgrade one Cisco Unity server to 5.0(1) even if other servers continue to run earlier versions of Cisco Unity. You can also apply the schema extensions well in advance of upgrading the first server to Cisco Unity 5.0(1). For a list of Cisco Unity version combinations that are supported for networked Cisco Unity servers, refer to the "Digital Networking Requirements for Cisco Unity with Exchange" section of Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Available Languages for Cisco Unity Components

This section lists the languages in which Cisco Unity components are available. Languages added with this release are marked with an asterisk(*).

Cisco Personal Communications Assistant

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish-Denmark, Dutch-Belgium, English-United States, French-France, German-Germany, Hungarian-Hungary, Italian-Italy, Japanese-Japan, Korean-Korea, Polish-Poland, Portuguese-Brazil, Russian-Russia, Spanish-Colombia, Spanish-Spain

Cisco Personal Communications Assistant (PCA) Help

English-United States

Cisco Unity Administrator

English-United States, French-France, German-Germany, Japanese-Japan

Cisco Unity Administrator Help

English-United States, Japanese-Japan

Cisco Unity Phone View

Added August 31, 2007

Chinese-Hong Kong SAR*, Chinese-PRC*, Chinese-Taiwan*, Danish-Denmark*, Dutch-Netherlands*, English-United States*, French-France*, German-Germany*, Hungarian-Hungary*, Italian-Italy*, Japanese-Japan*, Korean-Korea*, Polish-Poland*, Portuguese-Portugal*, Russian-Russia*, Spanish-Spain*

IBM Lotus Domino Unified Communications (DUC) for Cisco—csClient

Chinese-Simplified, Chinese-Taiwan, English, English-International, French, German, Italian, Japanese, Korean, Portuguese, Spanish

(For information on whether support for other languages has been added, refer to the IBM Lotus Domino website.)

IBM Lotus Domino Unified Communications (DUC) for Cisco—csAdmin and csServer

English, English-International, French, German, Japanese

(For information on whether support for other languages has been added, refer to the IBM Lotus Domino website.)

System prompts

Arabic-Saudi Arabia, Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Czech-Czech Republic, Danish-Denmark, Dutch-Belgium, Dutch-Netherlands, English-Australia, English-Canada, English-New Zealand, English-United Kingdom, English-United States, English TTY/TDD-United States, French-Canada, French-France, German-Germany, Hungarian-Hungary, Italian-Italy, Japanese-Japan, Korean-Korea, Norwegian-Bokmål, Polish-Poland, Portuguese-Brazil, Portuguese-Portugal, Russian-Russia, Spanish-Colombia, Spanish-Spain, Swedish-Sweden

Text-to-speech engine

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish-Denmark, Dutch-Netherlands, English-United Kingdom, English-United States, French-Canada, French-France, German-Germany, Italian-Italy, Japanese-Japan, Korean-Korea, Norwegian-Bokmål, Portuguese-Brazil, Portuguese-Portugal, Spanish-Spain, Swedish-Sweden

ViewMail for Outlook

Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish-Denmark, Dutch-Netherlands, English-United States, French-France, German-Germany, Hungarian-Hungary, Italian-Italy, Japanese-Japan, Korean-Korea, Polish-Poland, Portuguese-Brazil, Russian-Russia, Spanish-Colombia, Spanish-Spain

ViewMail for Outlook Help

English-United States

Voice-recognition engine

English-United States

Product documentation for administrators/installers

English-United States, Japanese-Japan

Product documentation for end users

English-United States, Japanese-Japan

Cisco Unity Release 5.0(1a)

Added February 3, 2009

Release 5.0(1a) contains an update to a single SQL upgrade script to fix CSCsm15661.

Cisco Unity DVD 1 has been rereleased to include the update and has been renumbered 5.0(1a); in addition, the DVD 1 image is available on the Cisco Unity 5.0 Software Download page on Cisco.com (see the "Downloading Software for Cisco Unity 5.0(1)" section).

The defect affected upgrades from Cisco Unity 4.x to version 5.0(1); the settings for standard and closed transfer rules for call handlers were being overwritten with the settings for the alternate transfer rule.

Cisco Unity with Domino: Lotus Domino 6.0 and Notes 6.0 Are Not Supported for New Installations of Cisco Unity 5.0(1)

On the IBM website, the document "End of Service (EOS) of Lotus Notes and Domino 6.0.x" indicates that Lotus Notes 6.0.x and Lotus Domino 6.0.x are end of service effective April 30, 2007. As a result, for new Cisco Unity 5.0(1) systems, you cannot install Lotus Notes 6.0.x on the Cisco Unity 5.0(1) server, and you cannot home Cisco Unity 5.0(1) subscriber mailboxes on a Lotus Domino 6.0.x server. However, if you are upgrading from Cisco Unity 4.x to Cisco Unity 5.0(1), you do not need to upgrade Notes or Domino.

Cisco Unity with Exchange: Changing the Partner Exchange Server from Exchange 2007 to Exchange 2003 or 2000 Is Not Supported

Added August 27, 2009

Changing the partner Exchange server from an Exchange 2007 server to an Exchange 2000 or 2003 server has not been tested and is not supported.

For information on changing the partner Exchange server:

From an Exchange 2000 or 2003 server to an Exchange 2007 server, see the "Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Server from an Exchange 2000 or 2003 Server to an Exchange 2007 Server for Cisco Unity 5.x" section.

From an Exchange 2000 server to an Exchange 2003 server, see the "Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Exchange Server from an Exchange 2000 Server to an Exchange 2003 Server for Cisco Unity 5.x" section.

From one Exchange 2000 server to another, one Exchange 2003 server to another, or one Exchange 2007 server to another, see the applicable section in the "Changing the Partner Exchange Server" chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.

Cisco Unity with Exchange: Cisco Unified Personal Communicator

Subscribers can use Cisco Unified Personal Communicator version 1.2 or later to view, play, and delete Cisco Unity voice messages. Cisco Unified Personal Communicator must be configured to use the IMAP messaging protocol to connect to Cisco Unity. Refer to the Installation Guide for Cisco Unified Personal Communicator at http://www.cisco.com/en/US/products/ps6844/prod_installation_guides_list.html.

Cisco Unity with Exchange: Exchange Server 2010

Added June 2, 2010

Cisco Unity now supports Exchange 2010 as the message store and/or as the partner Exchange server in a Unified Messaging configuration. To use Exchange 2010 with Cisco Unity, you must install Cisco Unity 5.0 Engineering Special (ES) 85 or later. For information on downloading the ES and procedures for configuring Cisco Unity to use Exchange 2010, see Using Microsoft Exchange 2010 with Cisco Unity Versions 7.0 and 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

Cisco Unity with Exchange: Exchange Server 2007

Cisco Unity now supports Exchange 2007 as the message store. Note the following limitations:

Exchange 2007 is supported as the message store only when Cisco Unity is configured as Unified Messaging.

Throughout the Cisco Unity documentation, procedures that are done on Exchange servers are different for Exchange 2007. The corresponding Exchange 2007 procedure is provided in the applicable locations.

During installation, if you choose an Exchange 2007 server as the partner Exchange server, you must configure offline address books for Outlook 2003 and earlier regardless of which version(s) of Outlook you are using, or Cisco Unity will not function properly. The Installation Guide for Cisco Unity explains the process in greater detail.

During installation, if you choose an Exchange 2007 server as the partner Exchange server, you must stop during the Message Store Configuration wizard, run scripts on the Exchange 2007 server to create default Active Directory accounts and Exchange mailboxes, and return to the Cisco Unity server to complete the Message Store Configuration wizard. The Installation Guide for Cisco Unity explains the process in greater detail.

The Cisco Unity Voice Connector for Microsoft Exchange, which is required for communicating with another voice-messaging system using AMIS, the Cisco Unity Bridge, or VPIM, can only be installed on an Exchange 2000 or an Exchange 2003 server. A Voice Connector is not currently available for Exchange 2007. If the customer has already configured a pure Exchange 2007 environment, an Exchange 2000 or Exchange 2003 server cannot be added to the environment and, therefore, Cisco Unity functionality that requires the Voice Connector is not available.

You cannot use Cisco Unity tools to create mailboxes in Exchange 2007:

You cannot use Cisco Unity Administrator or Cisco Unity Bulk Import to create Exchange 2007 mailboxes. If you want to create Cisco Unity subscribers whose mailboxes are homed in Exchange 2007, you must create the corresponding Active Directory accounts and Exchange mailboxes first, then create the subscribers by importing their Active Directory data. See the System Administration Guide for Cisco Unity for information on how to create subscribers by importing data from Active Directory.

If you are migrating or recovering a system using the Cisco Unity Disaster Recovery tools (DiRT) and if mailboxes are homed on Exchange 2007, the mailboxes must exist before the restore. DiRT cannot create mailboxes in Exchange 2007.

You cannot use BellHop to provide hospitality/PMS functionality when Exchange 2007 is the message store because BellHop automatically creates mailboxes in Exchange.

Cisco Unity Mobile Message Access for BlackBerry is not supported for Exchange 2007.

Exchange 2007 transport rules are not applied to Cisco Unity voice messages.

Integrated messaging via IMAP with Exchange 2007 is supported when Cisco Unity voice messages are stored in Exchange 2000 or Exchange 2003.

With Exchange 2000 or Exchange 2003, you can store e-mail messages in one Exchange message store, store Cisco Unity voice messages in another message store, and view both types of messages in a Microsoft Outlook Inbox. In this configuration, known as integrated messaging, you:

Configure Outlook to use MAPI to communicate with the message store that contains e-mail (MAPI is required because the e-mail message store commonly also contains calendars and contacts).

Configure Outlook to use IMAP to communicate with the message store that contains Cisco Unity voice messages. (Outlook only supports one MAPI connection at a time.)

Enable Exchange rich-text format on Exchange servers, which converts IMAP to TNEF-encoded IMAP. (If you do not enable rich-text format, voice messages appear in the Outlook Inbox as e-mail messages, so ViewMail for Outlook is not available.)

Exchange 2007 does not support TNEF-encoded IMAP, but you can still use an integrated messaging configuration with Exchange 2007 if you store e-mail in Exchange 2007 and store Cisco Unity voice messages in Exchange 2000 or Exchange 2003.

Cisco Unity-CM TSP Version 8.2(1)

Cisco Unity-CM TSP 8.2(1) is qualified for use with Cisco Unity version 5.0(1). For information on the Cisco Unity-CM TSP, refer to Release Notes for Cisco Unity-CM TSP Release 8.2(1) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

(The Cisco Unity-CM TSP is used only for SCCP integrations with Cisco Unified CM and Cisco Unified CM Express.)

Cisco Unity Documentation

The section lists new product documentation available with this release.

Cisco Unity User Guide

The Cisco Unity User Guide has been divided into four guides so that administrators can easily choose content relevant to subscribers based on the features and functionality enabled for them:

User Guide for the Cisco Unity Phone Interface

User Guide for the Cisco Unity Assistant Web Tool

User Guide for the Cisco Unity Inbox Web Tool

User Guide for Accessing Cisco Unity Voice Messages in an E-Mail Client (covers ViewMail for Outlook, DUC for Cisco, and IMAP client access to voice messages)

Note that the default key presses have been removed from procedures in the User Guide for the Cisco Unity Phone Interface. Instead, steps tell subscribers to choose menu options based on the prompts they hear (for example: Step 2 From the Main menu, choose the options Setup Options > Personal Settings > Change Password.). With this change, procedures are relevant for all subscribers, regardless of whether they are enabled for a custom conversation (created with the Custom Key Map utility), the default Cisco Unity conversation, or one of the optional premapped Cisco Unity conversations.

Administrators can use the Wallet Card wizard to produce cards that show the key presses for customized conversations and for Cisco Unity premapped conversations. For information on using the wizard, refer to the "Subscriber Orientation" chapter of the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

All of the user guides—as well as the User Guide for Mobile Message Access for BlackBerry—are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.

Cisco Unity Integration Guides

Certain Cisco Unity integration guides have been compiled into single books and are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html:

Cisco Unified CM SCCP Integration Guide for Cisco Unity Release 5.0

Cisco Unified CM SIP Integration Guide for Cisco Unity Release 5.0

PIMG Integration Guide for Cisco Unity Release 5.0

Interface Reference Guide for the Cisco Unity Administrator

This guide to the Cisco Unity Administrator is arranged according to the graphical user interface (GUI) pages in the web application, with chapters for each main area of the interface and sections for each page. Full definitions—including default values and minimum and maximum values, where applicable—are provided for all fields in the interface. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Cisco Unity Voice Connector for Microsoft Exchange 2003/2000 Version 12.0(1)

Voice Connector for Exchange 2000 12.0(1) is qualified for use with Cisco Unity version 5.0(1). For information on the Voice Connector, refer to Release Notes for Cisco Unity Voice Connector for Microsoft Exchange 2000 Release 12.0(1) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

We recommend that you use the latest version of the Voice Connector that is supported for your version of Cisco Unity. If you call Cisco TAC with a problem related to networking, the Cisco TAC engineer may require that you upgrade to a newer supported version of the Voice Connector, if one is available.

For the most current compatibility information, refer to Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Failover When Cisco Unity Servers Are Separated by a Firewall

Revised April 16, 2008

If Exchange is the message store, Cisco Unity failover supports connections when the primary and secondary servers are separated by a firewall. However, the primary server cannot be separated by a firewall from:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

In addition, the partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server that the partner server communicates with.

Cisco Unity failover was designed with the expectation that the primary server would generally be the active server. When Exchange is the message store and the secondary server is separated from any of the listed servers by a firewall, the secondary server must be used as the active server only for brief periods. The problem with the primary server must be resolved promptly, and the primary server must be made the active server again at the earliest opportunity.

If IBM Lotus Domino is the message store, the Cisco Unity servers cannot be separated by a firewall from:

One another.

The Domino message store servers.

The domain controller on which the Cisco Unity installation and services accounts were created.

If the system includes a Cisco Unity voice recognition server, the primary and secondary Cisco Unity servers must be on the same side of the firewall as the Cisco Unity voice recognition server.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, refer to the "IP Communications Required by Cisco Unity" chapter in the Security Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

IMAP and Cisco Unity Inbox Limits Increased for Selected Servers

The maximum number of Cisco Unity subscribers who are using an IMAP e-mail client and/or using the Cisco Unity Inbox to access voice messages has been increased to 4000 subscribers for selected servers when the Exchange message store is installed on a separate server. The limits will be increased for additional servers as we have time to test after Cisco Unity 5.0 has been released.

For the limits for specific servers, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

Microsoft Service Packs Required with Cisco Unity

For the most current list of all required and recommended Microsoft service packs, refer to the "Software Requirements—Cisco Unity Server" section of Cisco Unity 5.0 System Requirements at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Mobile Message Access for BlackBerry Available for Use with Cisco Unity Unified Messaging with Domino

Cisco Unity Mobile Message Access for BlackBerry version 1.1(1) has been qualified for use with Cisco Unity version 5.0(1) in a Unified Messaging configuration with Domino as the message store and BlackBerry Enterprise Server version 4.1(1).

Refer to Release Notes for Cisco Unity Mobile Message Access for BlackBerry Release 1.1(1) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Before you offer Mobile Message Access for BlackBerry to subscribers in your organization, review the following information:

"Setting Up Mobile Message Access for BlackBerry (Unified Messaging Configurations Only)" in the "Setting Up Subscriber Workstations" chapter of the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

The User Guide for Mobile Message Access for BlackBerry at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.

Mobile Message Access for BlackBerry Version 1.0(1) Is No Longer Supported

Beginning with version 5.0(1), Mobile Message Access for BlackBerry Version 1.0(1) is not supported for use with Cisco Unity. You must upgrade to Mobile Message Access for BlackBerry Version 1.1(1).

Phone System Integrations Qualified for Use with Cisco Unity

The following phone system integrations have been qualified for use with Cisco Unity since the last release:

Cisco Unified CM 4.3 (SCCP integrations only)

Cisco Unified CM 5.1 (SCCP and SIP trunk integrations)

Cisco Unified CM 6.0 (SCCP and SIP trunk integrations)

Cisco Unified CM Express 4.1 (SCCP and SIP trunk integrations)

Mitel SX-2000 (digital integration through PIMG units)

NEC NEAX 2400 (serial MCI integration through TIMG units)

Nortel SL-100 (serial SMDI integration through PIMG units)

Phone systems capable of a serial (SMDI, MCI, or MD-110) Integration through PIMG units

For the most current list of all supported phone system integrations—including integrations qualified since the release of Cisco Unity version 5.0(1)—refer to the "Supported Phone System Integrations" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Software Qualified for Use on Cisco Unity Subscriber Workstations

The following software has been qualified for use on Cisco Unity subscriber workstations:

Cisco Unity with Domino

Firefox version 2.x.x and later on the following operating systems:

Linux

Windows

Internet Explorer version 7.0.x and later on Windows XP and Windows Vista. When you run Internet Explorer 7 on Vista, you must disable protected mode for trusted sites and add the URL of the Cisco Personal Communications Assistant to the list of trusted sites.

The following versions of Microsoft Windows Vista are qualified for use on subscriber workstations:

Windows Vista Enterprise (x86)

Windows Vista Business (x86)

Windows Vista Business N (x86)

Cisco Unity with Exchange

Cisco Unity ViewMail for Microsoft Outlook version 5.0(1)

Firefox version 2.x.x and later on the following operating systems:

Linux

Windows

Internet Explorer version 7.0.x and later on Windows XP and Windows Vista. When you run Internet Explorer 7 on Vista, you must disable protected mode for trusted sites and add the URL of the Cisco Personal Communications Assistant to the list of trusted sites.

The following versions of Microsoft Windows Vista are qualified for use on subscriber workstations:

Windows Vista Enterprise (x86)

Windows Vista Business (x86)

Windows Vista Business N (x86)

For the most current version combinations of software qualified for use on subscriber workstations—including software qualified since the release of Cisco Unity version 5.0(1)—refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

Software That Is No Longer Supported for Use on Cisco Unity Subscriber Workstations

Beginning with Cisco Unity version 5.0(1), the following software is not supported for use on Cisco Unity subscriber workstations:

Cisco Unity with Domino

Internet Explorer version 5.5

Cisco Unity with Exchange

Internet Explorer version 5.5

For the most current version combinations of software qualified for use on subscriber workstations—including software qualified since the release of Cisco Unity version 5.0(1)—refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.html.

Standby Redundancy

Revised April 16, 2008

The standby redundancy feature uses failover functionality to provide duplicate Cisco Unity servers for disaster recovery. The primary server is located at the primary facility, and the secondary server is located at the disaster-recover facility. Instructions for configuring this feature are in the applicable Failover Configuration and Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

Standby redundancy functions in the following manner:

Data is replicated to the secondary server, with the exceptions noted in the "About Cisco Unity Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity.

Automatic failover is disabled.

In the event of a loss of the primary server, the secondary server is manually activated.

When Microsoft Exchange is the message store, the primary server cannot be separated by a firewall from:

The partner Exchange server.

The domain controller that Cisco Unity monitors for directory updates.

The global catalog server that Cisco Unity monitors for directory updates.

The global catalog server with which the Cisco Unity MAPI client communicates.

In addition, the partner Exchange server cannot be separated by a firewall from the domain controllers and the global catalog server that the partner server communicates with.

Standby redundancy was designed with the expectation that the primary server would generally be the active server. When Exchange is the message store and the secondary server is separated from any of the listed servers by a firewall, the secondary server must be used as the active server only for brief periods. The problem with the primary server must be resolved promptly, and the primary server must be made the active server again at the earliest opportunity.

When IBM Lotus Domino is the message store, the Cisco Unity servers cannot be separated by a firewall from:

One another.

Domino message store servers.

The domain controller on which the Cisco Unity installation and services accounts were created.

For details on the TCP/UDP ports that must be opened in a firewall to allow communication between Cisco Unity and other servers, refer to the "IP Communications Required by Cisco Unity" chapter in the Security Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Utility Updates in the Cisco Unity Tools Depot

Updates to utilities in the Cisco Unity Tools Depot are frequently posted between Cisco Unity releases. The updates commonly do not apply to a specific release, so we do not list the tools that have been updated since the last version of Cisco Unity. However, you can sign up to be notified when the utilities posted on the Cisco Unity Tools website are updated. Go to http://ciscounitytools.com, and click Sign Up Here.

Most of the utilities in the Tools Depot are also available on the Cisco Unity Tools website (http://ciscounitytools.com). If the Cisco Unity server is connected to the Internet and you run a Tools Depot utility that is available on the Cisco Unity Tools website, the utility automatically checks to see whether an updated version is available. If the Cisco Unity server is not connected to the Internet, we recommend that you check the Cisco Unity Tools website to determine whether a later version of the utility is available.

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

The Cisco Unity Tools Depot is a collection of utilities that perform a variety of administration, audio management, diagnostic, reporting, and phone system integration functions. To display the Tools Depot, double-click the Cisco Unity Tools Depot icon on the Cisco Unity server desktop or click Programs > Unity > Cisco Unity Tools Depot on the Windows Start menu. The left pane of the Tools Depot lists all of the available utilities by category. To display Help for a utility, click the name in the left pane. To run the utility, double-click the name.

New Functionality—Release 5.0(1)

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

Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity 5.0(1). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.

Cisco Unity Conversation Enhancements

The Cisco Unity conversation—also known as the TUI (telephone user interface)—has been enhanced in several ways. The enhancements are described in the following sections:

Cisco Unity with Domino: Full Mailbox Warnings

Cisco Unity with Domino: Full Mailbox Check When an Outside Caller Attempts to Leave a Message

Configuring the Behavior for Replying to All Recipients of a Message

Conversation Settings Added to the Cisco Unity Assistant

Conversation Timeout Setting Added to Cisco Unity Administrator

Custom Keypad Mapping Conversations Can Be Reset to Cisco Internal Mappings

Customizing the Subscriber Setup Options Menu

Dropped Call Recovery

Offering More Options at the Main Menu

Offering the Option to Revert to Default Message Playback Speed

Press-or-Say Phone Input Style

Specifying Per Subscriber the Addressing Order When Sending or Forwarding Messages

Specifying Per Subscriber the Amount of Time to Skip Back or Ahead When Rewinding or Fast-Forwarding Messages

Specifying Per Subscriber the Conversation Styles Offered in the Cisco Unity Assistant

Specifying Per Subscriber Whether Messages Are Sent Upon Hang-Up

Spoken Commands

For a summary of changes made to the default settings and functionality for the Cisco Unity conversation and the Cisco PCA applications for Cisco Unity 5.0(1), see the "Changed Functionality—Release 5.0(1)" section.

Cisco Unity with Domino: Full Mailbox Warnings

When subscribers who have a full mailbox log on to Cisco Unity by phone, Cisco Unity alerts them that their mailbox is full, asks them to delete some messages, and will not allow them to send any new messages while their mailbox is full. A subscriber with a full mailbox hears the following prompt: "Your inbox is full, you cannot send or receive new messages. Delete some messages now."

In previous versions, Cisco Unity alerted subscribers of their full mailbox after they attempted to send messages.

Cisco Unity with Domino: Full Mailbox Check When an Outside Caller Attempts to Leave a Message

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

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

To enable the feature, configure the following settings in the Advanced Settings Tool:

Conversation - Full Mailbox Check Feature

Conversation - Full Mailbox Check Prompt

Note that enabling full-mailbox checks for outside callers does not affect how Cisco Unity handles messages from other Cisco Unity subscribers to a full mailbox; subscribers who send messages to a full mailbox will receive a non-delivery receipt (NDR). Also, Cisco Unity behaves as if the full-mailbox check feature is disabled when:

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

An outside caller leaves a message for an interview handler.

Configuring the Behavior for Replying to All Recipients of a Message

By default, when a subscriber replies to all recipients of a message, Cisco Unity does not indicate to the subscriber how large the recipient list is. You can configure Cisco Unity to warn subscribers when the recipient list is greater than a number that you specify. When the original message includes at least one Public Distribution list or if the number of recipients is equal to or greater than the value you specify, subscribers will hear "This reply-to-all contains many recipients. To continue recording, press 1. To review the original recipient list, 2. To cancel, *." You use the Advanced Settings Tool to enable this feature. The setting is called Conversation—Reply-to-All Warning.

For information on other changes to the behavior when replying to all recipients of a message, see the "Conversation Behavior for Replying to All Recipients of a Message" section.

Conversation Settings Added to the Cisco Unity Assistant

Many conversation settings have been added to the Cisco Unity Assistant so that subscribers can adjust their values.

On Phone Menu Preferences page, the following settings have been added:

Conversation Style. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit. See also the "Specifying Per Subscriber the Conversation Styles Offered in the Cisco Unity Assistant" section.

Use Press-or-Say Phone Input Style (Includes Voice Addressing). This setting represents new Cisco Unity functionality. See also the "Press-or-Say Phone Input Style" section.

Address Message, Then Record It. This setting represents new Cisco Unity functionality. See also the "Specifying Per Subscriber the Addressing Order When Sending or Forwarding Messages" section.

Confirm Addressee by Name. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Continue Adding Names After Each Addressee. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Send Message When Subscriber Hangs Up or Call Is Disconnected. This setting represents new Cisco Unity functionality. See also the "Specifying Per Subscriber Whether Messages Are Sent Upon Hang-Up" section.

New Messages Automatically. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

On Greeting page, the following setting has been added:

Do Not Play the "Record your message at the tone" Prompt). In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

On the Advanced Settings page, the following settings have been added:

After Playing a Menu, Wait <x> Milliseconds For Me To Press the First Key. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Wait <x> Milliseconds For Additional Key Presses When Entering Names, Extensions, and Passwords. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Wait <x> Milliseconds For Additional Key Presses When Entering Phone Menu Commands. In previous versions, this field was available only in Bulk Edit.

Repeat Menu <x> Times When I Do Not Respond. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

When I Fast-Forward Messages, Skip Ahead <x> Seconds. This setting represents new Cisco Unity functionality. See also the "Specifying Per Subscriber the Amount of Time to Skip Back or Ahead When Rewinding or Fast-Forwarding Messages" section.

When I Rewind Messages, Skip Back <x> Seconds. This setting represents new Cisco Unity functionality. "Specifying Per Subscriber the Amount of Time to Skip Back or Ahead When Rewinding or Fast-Forwarding Messages" section.

Ask Me To Confirm Deletions of New and Saved Messages. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Mark a Message As Saved Upon Hang-up or Disconnection. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Include Receipts in Message Locator Searches. In previous versions, this field was available only in the Cisco Unity Administrator and Bulk Edit.

Enable DCR for Calls Dropped During Message Playback. This setting represents new Cisco Unity functionality. See also the "Dropped Call Recovery" section.

Enable DCR for Calls Dropped While Addressing or Recording Messages. This setting represents new Cisco Unity functionality. See also the "Dropped Call Recovery" section.

Conversation Timeout Setting Added to Cisco Unity Administrator

By default, when outside callers or subscribers respond to a phone menu by pressing a key that represents the first digit of more than one possible key combination, Cisco Unity waits 1,500 milliseconds (one and a half seconds) for additional key presses before acting. For example, in the After Message menu for the standard conversation, subscribers can press 4 to reply to a message, 42 to reply to all, or 44 to call the subscriber. Thus, when subscribers press 4 after listening to a message, Cisco Unity waits one and a half seconds before responding to give subscribers a chance to press an additional key. For those who prefer that Cisco Unity respond more quickly or more slowly in waiting for additional key presses, you can adjust the response timeouts.

You can adjust the response timeout setting for all subscribers and outside callers by using the Wait <x> Milliseconds For Additional Key Presses When Entering Phone Menu Commands field on the System > Configuration > Settings page in the Cisco Unity Administrator. You can also adjust this setting for individual subscribers or groups of subscribers using the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator or in the Bulk Edit utility. Subscribers can also adjust this setting themselves on the Advanced Settings page in the Cisco Unity Assistant.

In earlier versions, you adjusted a setting in the Advanced Settings Tool to specify the response timeout setting for all subscribers and outside callers associated with a Cisco Unity server or you could adjust this setting for individual subscribers only in the Bulk Edit utility and the default value was 1,000 milliseconds. If you are upgrading to Cisco Unity version 5.0(1), see the "Conversation Settings Removed from Advanced Settings Tool" section. If you are upgrading to Cisco Unity version 5.0(1), the existing value of the setting is retained.

Note that the Wait <x> Milliseconds For Additional Key Presses When Entering Names, Extensions, and Passwords setting is a similar timeout setting which has been reworded to clarify the difference between the two timeout settings.

Custom Keypad Mapping Conversations Can Be Reset to Cisco Internal Mappings

The Custom Key Map utility allows you to reset a Custom Keypad Mapping conversation to the keys that Cisco uses in our internal deployment.

The new functionality can be used with Cisco Unity version 4.2(1) and later.

The Custom Key Map utility allows you to edit the key mappings associated with several Custom Keypad Mapping conversations, which can be assigned to subscribers on the Conversation page in the Cisco Unity Administrator or by subscribers themselves on the Phone Menu Preferences page in the Cisco Unity Assistant. The Custom Key Map utility can be found in the Cisco Unity Tools Depot.

Customizing the Subscriber Setup Options Menu

Using the Custom Key Map utility, you can specify whether the following options are offered to subscribers as part of the Setup Options menu:

Greetings

Message Settings

Message Notification

Fax Delivery

Menu Style

Private Lists

Personal Settings

Transfer Settings

When the Greetings, Personal Settings, and Transfer Settings menus are specified, all options in those menus are also included. Only the options in the Message Settings menu can be specified individually.

The Custom Key Map tool allows you to edit the key mappings associated with several Custom Keypad Mapping conversations, which can be assigned to subscribers on the Conversation page in the Cisco Unity Administrator or by subscribers themselves on the Phone Menu Preferences page in the Cisco Unity Assistant. The Custom Key Map tool can be found in the Cisco Unity Tools Depot.

Dropped Call Recovery

If subscribers inadvertently disconnect while listening to or sending messages, Dropped Call Recovery allows them to call back into Cisco Unity within a specified period of time and resume the activity without losing their place.

When enabled for dropped calls during message playback, the setting applies when the call terminates while a subscriber is listening to new or saved messages. It does not apply if a subscriber is listening to deleted messages, receipts, or if a subscriber is listening to messages by using the dynamic Message Locator option. By default, the recovery time period for calls dropped during message playback is five minutes. If the subscriber calls back during the specified period of time, the subscriber will be able to continue listening to the message. Note that if the Mark a Message as Saved Upon Hang-up or Disconnection option is also enabled for a subscriber and the subscriber was disconnected while listening to a new message, the message will remain marked as new until the recovery time period has expired.

When enabled for calls dropped while addressing or recording messages, the setting applies when the call terminates while a subscriber is sending a new message, replying to, or forwarding a message. If the message has at least one addressee or a recording and there is a disconnect, it will be held for the specified period of time before sending. By default, the recovery time period for calls dropped while addressing or recording messages is three minutes. If the subscriber calls back into the mailbox during that time, the subscriber will be offered the option to review the message, cancel it, or send it as is. If the subscriber does not call back during that time and the message has at least one addressee and a recording, the message will only be sent if the subscriber has the Send Message When Subscriber Hangs Up or Call Is Disconnected option enabled. If the Send Message When Subscriber Hangs Up or Call Is Disconnected option is disabled, the message will be discarded.

You can enable and specify the time frames for Dropped Call Recovery on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. Subscribers can also enable and adjust the Dropped Call Recovery settings themselves on the Advanced Settings page in the Cisco Unity Assistant.

For more information, refer to the "Dropped Call Recovery" section in the "Managing Conversation Settings That Are Controlled by Subscriber or Subscriber Template Settings" chapter of the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

In earlier versions, you could adjust unsupported settings in the Advanced Settings Tool to turn on a beta "first look" version of the Dropped Call Recovery feature for all subscribers associated with a Cisco Unity server. The Dropped Call Recovery settings in Advanced Settings Tool have been removed. If you are upgrading to Cisco Unity version 5.0(1), the values of the settings are not retained.

Offering More Options at the Main Menu

Using the Custom Key Map tool, you can specify whether the following options are added to the Main menu:

Subscriber System Transfer

Greetings Administrator

Broadcast Message Administrator

The Custom Key Map tool allows you to edit the key mappings associated with several Custom Keypad Mapping conversations, which can be assigned to subscribers on the Conversation page in the Cisco Unity Administrator or by subscribers themselves on the Phone Menu Preferences page in the Cisco Unity Assistant. The Custom Key Map tool can be found in the Cisco Unity Tools Depot.

Offering the Option to Revert to Default Message Playback Speed

Using the Custom Key Map tool, you can map a key that when pressed during message playback will revert the message playback speed to the subscriber's default playback speed. The key would be used by subscribers who have changed the playback speed and want to go back to their default speed while listening to a message.

The Custom Key Map tool allows you to edit the key mappings associated with several Custom Keypad Mapping conversations, which can be assigned to subscribers on the Conversation page in the Cisco Unity Administrator or by subscribers themselves on the Phone Menu Preferences page in the Cisco Unity Assistant. The Custom Key Map tool can be found in the Cisco Unity Tools Depot.

Press-or-Say Phone Input Style

The Press-or-Say phone input style gives subscribers the options of pressing the key or saying the number that corresponds to a menu option.

In addition, when addressing messages or adding names to private lists, subscribers can say the names of recipients instead of spelling them by using the phone keypad. To improve the accuracy of name recognition, you can enter alternate spellings for the names of individual subscribers. Alternate spellings are entered on the Alternate Name page for individual subscribers in the Cisco Unity Administrator. For more information, see the "Managing Voice-Recognition Features" chapter in the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

You enable the Press-or-Say input style on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. If voice-recognition features are enabled for subscribers, then subscribers can enable or disable the Press-or-Say input style over the phone or using the Cisco Unity Assistant.

For information on configuring the Press-or-Say phone input style, see the "Managing Voice-Recognition Features" chapter in the System Administration Guide for Cisco Unity. For information on using this input style, see the "Using the Press-or-Say Phone Input Style" chapter in the User Guide for the Cisco Unity Phone Interface at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.html.

The Press-or-Say feature requires an additional server running voice-recognition software. See the "Voice Recognition" section, under "New Functionality—Release 5.0(1)."

Specifying Per Subscriber the Addressing Order When Sending or Forwarding Messages

By default, when subscribers send or forward messages to other subscribers or distribution lists, Cisco Unity prompts subscribers to address the message first and then record it. You can customize the subscriber conversation so that Cisco Unity prompts subscribers to record a message or introduction before prompting them to address it.

You specify the addressing order on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. Subscribers can also adjust the message addressing order themselves on the Phone Menu Preferences page in the Cisco Unity Assistant.

In earlier versions, you adjusted a setting in the Advanced Settings Tool to specify the message addressing order for all subscribers associated with a Cisco Unity server. If you are upgrading to Cisco Unity version 5.0(1), see the "Conversation Settings Removed from Advanced Settings Tool" section.

Specifying Per Subscriber the Amount of Time to Skip Back or Ahead When Rewinding or Fast-Forwarding Messages

By default, when subscribers are listening to messages, when they rewind or fast-forward the message, Cisco Unity skips back or ahead in the message by five seconds.

You can specify the amount of time Cisco Unity skips back or ahead in the message on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. Subscribers can also adjust the amount of time Cisco Unity skips back or ahead in the message themselves on the Advanced Settings page in the Cisco Unity Assistant.

Specifying Per Subscriber the Conversation Styles Offered in the Cisco Unity Assistant

You can specify the conversation styles that are offered to subscribers in the Cisco Unity Assistant. For example, you may want subscribers to choose among only the standard, Optional 1, and Alternate Keypad Mapping N conversations.

You select the conversation styles on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. If you do not select any conversation style to be offered in the Cisco Unity Assistant, subscribers will see only the conversation style that you have assigned to them in the Cisco Unity Administrator.

In earlier versions, conversation style was not exposed in the Cisco Unity Assistant.

Specifying Per Subscriber Whether Messages Are Sent Upon Hang-Up

You can change how Cisco Unity behaves when calls are disconnected while subscribers are in the process of sending, replying to, or forwarding a message. Calls can be intentionally or unintentionally disconnected when a subscriber hangs up or a cell phone loses its charge or signal. By default, Cisco Unity sends the message if the call is disconnected in the following circumstances:

When a subscriber is replying to or sending a message - As long as the message has at least one recipient and the recording is longer than the value entered in the Discard Any Recording Less Than <x> Seconds field on the System > Configuration > Recordings page in the Cisco Unity Administrator. This means that Cisco Unity sends the message even though the subscriber may not have finished recording or addressing the message.

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

You specify whether messages are sent upon hang-up on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. Subscribers can also adjust the setting themselves on the Phone Menu Preferences page in the Cisco Unity Assistant. This setting does not apply to messages left by outside callers.

By adjusting the default value of the setting, you can alter Cisco Unity behavior so that Cisco Unity will not send messages unless subscribers have pressed # to confirm that they are ready to send their message. Thus, if the call is disconnected before a subscriber has a chance to do so, Cisco Unity deletes the message rather than sending it.

Note that if the subscriber has dropped call recovery enabled for calls dropped while addressing or recording messages, messages that are sent upon hang-up will not be sent until the time period for dropped call recovery has expired.

In earlier versions, you adjusted a setting in the Advanced Settings Tool to specify the message addressing order for all subscribers associated with a Cisco Unity server. If you are upgrading to Cisco Unity version 5.0(1), see the "Conversation Settings Removed from Advanced Settings Tool" section.

Spoken Commands

The Spoken Commands feature enables subscribers using the Press-or-Say input style to say the name of a menu option, as an alternative to pressing the touchtone key or saying the key number that corresponds to the menu option. For example, instead of saying "Three" or pressing the three touchtone key to delete a message, subscribers can now also say "Delete." Subscribers who do not have the Press-or-Say input style enabled may only press touchtone keys to respond to menu options.

The standard and custom conversation versions support spoken commands. Spoken commands are available only for options from the Main menu and when listening to or sending voice messages. To access other parts of the conversation, such as Greetings and Personal Settings under the Setup menu, subscribers must still press or say the name of the applicable touchtone key.

For information on how to enable and use spoken commands, as well as a full list of available spoken commands, see the Release Notes for Spoken Commands in Cisco Unity 5.0(1) document at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Cisco Unity Feature Scripts

Cisco Unity includes a set of sample communication scripts that describe Cisco Unity 5.0 (1) and Cisco Unity 4.2(1) features.

The scripts are text files located in the \\commserver\feature_script\ directory. You can use the scripts as they are written, or customize them to suit the needs of your organization, to record voice messages that promote Cisco Unity to subscribers and explain how these features can improve their productivity.

For more information on using and customizing the feature scripts, refer to the "Sample Communication Scripts" section in the "Subscriber Orientation" chapter of the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Cisco Unity with Exchange: Message Store Configuration Wizard Prompts You to Enable Circular Logging

Each new voice message is saved in an Exchange transaction log and then is copied from the log to the Exchange message store when system resources are available. If the message store is corrupted or destroyed, you can use the last backup of the message store plus the transaction logs to restore the message store (assuming the transaction logs are stored in a different location than the message store and therefore were not destroyed along with the message store).

After you back up the message store by using Exchange-aware backup software, the backup software clears the transaction logs. At this point, the backup reflects the current state of the message store, so the transaction logs are no longer required to restore the message store.

You can configure logging in one of two ways: either the existing logs are regularly overwritten, or the existing logs are never overwritten. Overwriting the existing logs is known as circular logging.

By default, Exchange circular logging is disabled, which means that transaction logs grow until you back up the Exchange database with Exchange-aware backup software, or until the hard disk fills up and the server on which Exchange is installed stops functioning.

For customers who install Cisco Unity in a Voice Messaging configuration, we have added a page to the Message Store Configuration Wizard that allows you to change the circular-logging setting for any message store in the forest for which circular logging is turned off. The new page only appears if the Cisco Unity licenses do not include any Unified Messaging subscribers and if circular logging is disabled for any of the message stores in the forest.

Cisco Unity with Exchange: Trusted Internet Subscribers and Trusted Internet Locations

Trusted Internet Subscribers are a new type of subscriber. Trusted Internet Locations are a new type of delivery location. They are both used in conjunction with Secure Messaging.

Trusted Internet Subscribers are Internet Subscribers that are trusted with decrypted secure messages. Trusted Internet subscribers must be associated with a Trusted Internet Location. Based on the security settings of the Trusted Internet location, secure messages to Trusted Internet subscribers are decrypted by the Cisco Unity Voice Connector for Microsoft Exchange before they are sent by the Exchange server. (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)

For more information on changes to the Secure Messaging feature see the "Cisco Unity with Exchange: Private Secure Messaging" section.

Cisco Unity with Exchange: Using Logon Credentials from Active Directory Accounts in a Different Forest

Added October 20, 2008

Some customers install the Cisco Unity server in a forest other than the corporate forest. However, they still want subscribers to be able to log on to the Cisco Unity Assistant and/or the Cisco Unity Inbox by using user credentials in the corporate forest. If your Cisco Unity servers are in this configuration, you can use the GrantUnityAccess utility to associate Cisco Unity subscribers with the Active Directory accounts in the corporate forest. Do the following procedure.

To Associate Cisco Unity Subscribers with Active Directory Accounts in a Different Forest


Step 1 Using Active Directory Domains and Trusts, create a two-way forest trust between the corporate forest and the forest that contains the Cisco Unity server.

Step 2 Log on to the Cisco Unity server using the Cisco Unity administration account that was configured during installation.

Step 3 At a command line or in a batch file, run the following command once for each Cisco Unity subscriber account that you want to associate with an Active Directory account in the corporate forest:

grantunityaccess
-u <domain controller in the corporate forest>\<Active Directory account alias>
-s <alias of Cisco Unity subscriber>

For example:

grantunityaccess -u CorporateDomain\dgupta -s dmitrygupta


Note If the directory in which Cisco Unity was installed (Commserver by default) is not included in the Path system variable, either add the Commserver directory to the path or change to the Commserver directory before you run GrantUnityAccess.


Step 4 Confirm that a user who is logged on to the corporate forest can access the Cisco Unity Assistant and/or the Cisco Unity Inbox by using credentials from the corporate forest.

Step 5 If there is more than one Cisco Unity server, repeat Step 2 through Step 4 on each Cisco Unity server for which you want to configure the same functionality.


Custom Key Map Wallet Card Wizard Enhancements

The wizard allows you to specify the key press mappings to include on the card for the Main, During Message, After Message, and Send menus. In addition, the generated wallet card includes Entering Recipients and Selecting Recipients menus instead of During Message shortcuts.

Distribution of Microsoft Updates Recommended for Use with Cisco Unity

Beginning with the release of Cisco Unity 5.0, we will no longer post English, French, German, and Japanese versions of the Microsoft updates that are recommended for use with Cisco Unity. Instead, Microsoft updates, in English only, will be included in a new Cisco Unity Server Updates wizard, available at http://www.cisco.com/cgi-bin/tablebuild.pl/unity_msft_updates. The Cisco Unity Server Updates wizard will be updated once a month, after Microsoft releases new updates for the affected software.

To use the Cisco Unity Server Updates wizard to install Microsoft updates for Windows, SQL Server 2000 or MSDE 2000, Internet Explorer, and Exchange, you must install the English-language version of Windows. If you install Windows in French, German, or Japanese, the Server Updates wizard will not run; you must download Microsoft updates from the Microsoft website.

The currently shipping Cisco Unity Platform Configuration discs (PCDs) install Windows in English and allow you to choose the language in which the Windows user interface appears (English, French, German, or Japanese). Therefore, if you use a PCD to install Windows, you can use the Cisco Unity Server Updates wizard to install the Microsoft updates recommended for use with Cisco Unity.

Monitoring Messages Remotely

The Remote Message Monitor feature allows subscribers to be notified on a remote phone such as a mobile phone when their primary extension is called, and provides them with two options for managing the call:

To listen to the message as the caller records it.

To connect to the caller who is recording the message.

For information on enabling Remote Message Monitor, refer to the "Remote Message Monitor" section in the "Managing Phone View Features and Remote Message Monitor" chapter in the System Administration Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Note that the feature is available only for Cisco Unified CM phone system integrations.

Phone View Features

Phone View features allow subscribers to see Cisco Unity information on the LCD screens of their Cisco Unified IP Phones.

Visual Message Locator—Supported for use with Cisco Unity with Exchange Only

When Visual Message Locator is enabled, subscribers can use their phone displays to select a message to play back when they search for the following types of messages:

All new voice messages

All voice messages

Messages from a particular user

Messages from all outside callers

Messages from a particular outside caller

Message Monitoring—Supported for use with Cisco Unity with Domino and Cisco Unity with Exchange

When Message Monitor is enabled, subscribers can monitor callers who are in the process of recording messages, and do the following:

Listen to the message as the caller records it.

Connect to the caller who is recording the message.

While on another call, listen to a message as the caller records it.

While monitoring a call, give the caller the option of continuing to record the message or connecting to the subscriber.

Multilingual Support—With Cisco Unity with Domino and Cisco Unity with Exchange

Added August 31, 2007

Cisco Unity supports the following languages for Phone View features: Chinese-Hong Kong SAR, Chinese-PRC, Chinese-Taiwan, Danish-Denmark, Dutch-Netherlands, English-United States, French-France, German-Germany, Hungarian-Hungary, Italian-Italy, Japanese-Japan, Korean-Korea, Polish-Poland, Portuguese-Portugal, Russian-Russia, Spanish-Spain.

Language support is limited for subscribers using Cisco Unified CallManager version 4.x on the 7940 or the 7960 Cisco IP phones. For these configurations, English may be provided instead of the expected language.


Note If subscriber caller names do not display correctly in Message Monitor, you may need to install supplemental language support via the Windows Regional and Languages Administration tool. The files for most languages are installed on your computer automatically by Microsoft Windows, but you may need to do this step if the names are stored on the Cisco Unity server using characters from any of the following languages:

Complex script and right-to-left languages including Arabic, Armenian, Georgian, Hebrew, the Indic languages, Thai, and Vietnamese.

East Asian languages including Chinese, Japanese, and Korean.

See your Microsoft Windows documentation for using the Windows Regional and Languages Administration tool to install additional languages.

More information about Phone View

For information on configuring and enabling Phone View, refer to the "Phone View Features" section in the "Managing Phone View Features and Remote Message Monitor" chapter of the System Administration Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

For Phone View requirements, refer to the "Requirements for Cisco Unity Phone View" section of System Requirements for Cisco Unity Release 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

For Cisco Unified IP Phone models supported with Phone View features, refer to the "Supported Phone Models for Use with Cisco Unity Phone View" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Simulating Abbreviated Extensions

You can simulate abbreviated extensions by using prepended and postpended digits for call handlers and subscriber mailboxes. When such digits are defined, they will be prepended and postpended to any extension that a caller dials while listening to the greeting for the call handler or subscriber mailbox.

Cisco Unity first attempts to route the call to the prepended/postpended extension. If the prepended/postpended extension is not valid, Cisco Unity attempts to route the call to the dialed extension. In the following example, the call handler named Sales is configured with the prepended digits 123 and the postpended digits 456. When a caller dials 1000 while listening to the greeting for the Sales call handler Cisco Unity attempts to route the call to extension 1231000456; if the prepended/postpended extension is not valid, Cisco Unity attempts to route the call to extension 1000.

You can set up multiple call handlers for which callers are able to enter the same digits (for example 1000) to reach a support person, but the calls can be routed to a support person appropriate to the particular call handler (for example, a Technical Support call handler or a Sales call handler) because of the presence of the prepended and postpended digits.

You use the Advanced Settings Tool to enable this feature. The setting is called Administration—Expose Prepend and Postpend Digits for Call Handlers and Subscribers. You configure prepended and postpended digits on the applicable Caller Input page for a subscriber template, an individual subscriber, or a call handler in the Cisco Unity Administrator or in the Bulk Edit utility.

Subscriber Partitioning for Message Addressing by Phone

Cisco Unity allows you to associate subscribers with directory handlers to control who they can address messages to and who they can add to distribution lists by phone. This can be useful for setting up a multi-tenant system where there is a need to prevent subscribers in one group from sending messages to subscribers in another group.

To partition accounts, you define message addressing search scopes by associating subscribers with directory handlers.

When you associate subscribers with directory handlers, you can have Cisco Unity restrict their search scopes to the search option selected for the directory handler—which can be a dialing domain, the local Cisco Unity server, a location, a class of service, or a public distribution list.

For information on partitioning subscriber accounts, refer to the "Partitioning Subscriber Accounts for Message Addressing by Phone" section in the "Setting Up Features That Are Controlled by Subscriber or Subscriber Template Settings" chapter in the System Administration Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Tracking Unified Messaging Subscribers

The License Features page in Cisco Unity Administrator and the Unity Licensing console display the number of Unified Messaging subscribers as designated by the new Cisco Unity Subscriber Type class of service setting. Tracking the number of Unified Messaging subscribers can be useful for a system that includes both Unified Messaging and Voice Messaging subscribers.

Voice Recognition

Voice-recognition features allow subscribers to interact with Cisco Unity by speaking rather than by using the phone keypad. The features are licensed by number of concurrent sessions, and require installation and configuration of voice-recognition software on a separate and dedicated server.

A System >Voice Recognition page has been added to the Cisco Unity Administrator for configuring voice-recognition settings.

You enable access to the voice-recognition features on the applicable Conversation page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. When subscribers have voice-recognition access, they can enable and disable the Press-or-Say input style by phone or by using the Cisco Unity Assistant. (See also the "Press-or-Say Phone Input Style" section, and the "Spoken Commands" section under "Cisco Unity Conversation Enhancements.")

For information on configuring voice-recognition features, see the "Managing Voice-Recognition Features" chapter in the System Administration Guide for Cisco Unity. For information on using the Press-or-Say input style, see "Using the Press-or-Say Phone Input Style" in the User Guide for the Cisco Unity Phone Interface.

For information on installing and configuring a separate voice-recognition server, refer to Appendix A, "Installing and Configuring a Voice-Recognition Server" in the Installation Guide for Cisco Unity.

Changed Functionality—Release 5.0(1)

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

Note that the Cisco Unity Tools website may offer scripts and applications that were not included in Cisco Unity 5.0(1). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.

Cisco Unity Conversation Changes

In addition to the new functionality described in the "Cisco Unity Conversation Enhancements" section, some default settings and functionality have changed in the Cisco Unity conversation. The changes are described in the following sections:

Conversation Behavior for Replying to All Recipients of a Message

Conversation Settings Removed from Advanced Settings Tool

Custom Key Map Conversations Preserved During an Upgrade

Cisco Unity Assistant: Send Message Style Setting Moved to the Phone Menu Preferences Page

Menu Repeats

Specifying the Transfer Settings for Alternate Contact Numbers

Switching Search Mode by Pressing ## or 00

Conversation Behavior for Replying to All Recipients of a Message

The following changes have been made to how Cisco Unity handles replying to all recipients of a message that was sent to multiple subscribers and/or distribution lists:

If the original message was sent to just one person and that person attempts to reply-all, Cisco Unity warns them that the message has only one recipient and then plays the after-message menu again. Subscribers will hear "Reply-to-all is not available because the message has only one recipient."

If the number of recipients on the original message is larger than 50, Cisco Unity does not allow recipients to reply-all. Subscribers will hear "this message has too many recipients."

If the original message includes at least one Public Distribution list and the subscriber attempting to reply-all belongs to a COS that does not allow sending messages to Public Distribution lists, the subscriber will hear "This message has at least one distribution list as a recipient. You are not allowed to send messages to distribution lists."

If a subscriber attempts to reply-all to a message that was from a remote subscriber or included some remote recipients, they will hear the prompt "Some recipients of the original message may not receive this reply."

By default, when a subscriber replies to all recipients of a message, Cisco Unity does not indicate to the subscriber how large the recipient list is. For information on how you can configure Cisco Unity to warn subscribers when their replies are to a large group, see the "Configuring the Behavior for Replying to All Recipients of a Message" section.

Conversation Settings Removed from Advanced Settings Tool

The following settings are no longer available in the Advanced Settings Tool:

Conversation—Subscriber Send Message Flow (Addressing Order). The existing value for the setting is retained upon upgrading. The setting can be enabled and disabled for individual subscribers by using the Cisco Unity Administrator, Cisco Unity Assistant, or Bulk Edit. Also see the "Specifying Per Subscriber the Addressing Order When Sending or Forwarding Messages" section.

Conversation—Interdigit Delay for Command Entry System Default. The existing value for the setting is retained upon upgrading. The setting can be configured for outside callers and all subscribers on the System > Configuration > Settings page in the Cisco Unity Administrator. Also see the "Conversation Timeout Setting Added to Cisco Unity Administrator" section.

Conversation—Set "Double Key Press" Time For Changing Addressing Mode. This setting was used to adjust the time that Cisco Unity waits for the second # key when subscribers switch between addressing by name and ID. Cisco Unity now uses the Wait <x> Milliseconds for Additional Key Presses When Entering Phone Menu Commands timeout setting to determine how long to wait for the second # key when subscribers switch between addressing by name and ID.

Conversation - Subscriber Send Message Hang-Up Action. The existing value for the setting is retained upon upgrading. The setting can be enabled and disabled for individual subscribers by using the Cisco Unity Administrator, Cisco Unity Assistant, or Bulk Edit.Also see the "Specifying Per Subscriber Whether Messages Are Sent Upon Hang-Up" section.

Custom Key Map Conversations Preserved During an Upgrade

If you used the Custom Key Map utility to create a custom conversation in Cisco Unity version 4.0(5) or later, the custom keypad mapping is preserved during an upgrade. You no longer need to restore the custom keypad mapping.

Cisco Unity Assistant: Send Message Style Setting Moved to the Phone Menu Preferences Page

Using the Cisco Unity Assistant, subscribers can select whether they hear the standard or streamlined Send Message menu style. The setting has been moved from the Advanced Settings page to the Phone Menu Preferences page. The existing value of the Send Message Style setting is retained upon upgrading.

Menu Repeats

You can specify how many times Cisco Unity repeats a menu if the subscriber has not responded to a menu. You can configure the setting on the Conversation pages for subscribers and templates, and on the System > Configuration page of the Cisco Unity Administrator. The default value for new installations is 3 repeats. Therefore if a subscriber does not respond to a menu, they would hear the menu 4 times.

In previous versions the default value was 1 repeat, so that a subscriber would hear a menu twice when they did not respond. The existing value for menu repeats is retained upon upgrading.

Specifying the Transfer Settings for Alternate Contact Numbers

When using the Alternate Contact Number feature, you can configure Cisco Unity to use subscribers' active transfer rule settings, including call holding and call screening options. Cisco Unity will still use the number for the transfer that is specified in the Alternate Contact Number field, but the transfer settings (release, supervised, call holding, etc.) comes from the active transfer rule. By default, Cisco Unity uses a release transfer when transferring callers to an alternate contact number.

You use the Advanced Settings Tool to enable this setting, which is called Conversation—ACN Follows Current Transfer Rule.

Switching Search Mode by Pressing ## or 00

When subscribers address messages, edit private lists, or find messages by phone, they search for a subscriber by spelling the name or by entering the extension. Subscribers can switch search mode by pressing ## or 00.

Due to limitations when pressing 00 to switch search mode, the prompt that tells users they can switch search mode no longer mentions 00 as an option. It mentions only the ## option. Users who are used to pressing 00 can still do so; Cisco Unity responds to either option.

For more information on the limitations of using the 00 option, see the "Delay When Subscribers Press 00 to Switch Search Modes in Cisco Unity Conversation" section.

Additionally, the system-wide setting that was used to adjust the time that Cisco Unity waits for the second # key when subscribers switch between addressing by name and ID has been removed. Cisco Unity now uses the Wait <x> Milliseconds for Additional Key Presses When Entering Phone Menu Commands timeout setting to determine how long to wait for the second # key when subscribers switch between addressing by name and ID. For more information see the "Conversation Settings Removed from Advanced Settings Tool" section and the "Conversation Timeout Setting Added to Cisco Unity Administrator" section

Cisco Unity with Exchange: Create Cisco Unity Subscribers with Disabled Active Directory Accounts

This change applies only if all of the following are true:

You are creating subscriber mailboxes in Exchange 2000 and or Exchange 2003.

Cisco Unity is configured for Voice Messaging.

You use Cisco Unity Administrator or Cisco Unity Bulk Import to automatically create accounts in Active Directory.

You do not allow Cisco Unity subscribers to access voice messages by using the Cisco Unity Inbox or an e-mail client, change their personal settings using the Cisco Personal Communications Assistant, or access the Cisco Unity Administrator.

When you create Cisco Unity subscribers using the Cisco Unity Administrator or by importing a CSV file using Cisco Unity Bulk Import, Cisco Unity automatically creates an Active Directory (AD) account for each subscriber. The password on these AD accounts is the same for every subscriber who was created using the same Cisco Unity template. A subscriber who knows another subscriber's alias and the AD password in the template could access the other subscriber's messages using the Cisco Unity Inbox or an e-mail client, impersonate the user through the Cisco Unity Inbox, or change the other subscriber's settings using the Cisco Personal Communications Assistant.

You can now automatically disable the AD accounts created by Cisco Unity:

During installation if you choose the Message Store Configuration Wizard option to disable the Active Directory accounts created for subscribers.

After installation if you change a value in the Advanced Settings Tool before you create subscribers. For more information, refer to the Advanced Settings Tool help for the "Administration - Disable AD accounts created by Unity" setting.


Caution If you want subscribers to have access to the Cisco Unity Inbox, the Cisco Personal Communications Assistant, or the Cisco Unity Administrator, do not disable AD accounts; the accounts are required for authentication. If accounts cannot be disabled, we recommend that you refer to the "Securing Accounts" chapter in the Security Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Cisco Unity with Exchange: Private Secure Messaging

The Private Secure Messaging feature is now referred to as Secure Messaging. The following enhancements have been made to the Secure Messaging feature:

Encryption is no longer tied to the private flag and all types of messages can now be encrypted. (In previous versions, only private messages could be encrypted.)

Administrators can configure on a per subscriber basis that messages sent by the subscriber either (1) always be encrypted, (2) be encrypted only when flagged as private or (3) never be encrypted.

Messages from unidentified callers can be encrypted.

Subscribers can listen to encrypted messages using ViewMail for Outlook version 5.0(1) and Cisco Unity Inbox using TRAP or PC speakers. (In previous versions, subscribers could listen to encrypted messages only through the telephone interface.)

Delivery location settings have been enhanced for sending & receiving encrypted messages to and from remote sites that are networked using the VPIM, Bridge, or AMIS protocols.

A new type of subscriber, Trusted Internet Subscribers, and a new type of delivery location, Trusted Internet Locations, have been created so that secure massages can be sent to internet subscribers. For more information see the "Cisco Unity with Exchange: Trusted Internet Subscribers and Trusted Internet Locations" section.

Encryption certificates are installed and maintained automatically. (In previous versions, certificates were installed and maintained manually.)

The encryption algorithms have been changed so that message decryption occurs faster and uses less CPU overhead.

Message aging can be enabled for encrypted messages. After a specified period of time, the certificate used to encrypt a message will expire and Cisco Unity will no longer be able to decrypt the message. Message aging applies to all encrypted messages regardless of whether the message recipient has listened to the message.

You configure message aging and message security for unidentified callers on the System > Configuration > Message Security Settings page.

You specify which types of subscriber messages are encrypted, if any, on the applicable Features page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility.

If you are upgrading from a previous version and were using Private Secure Messaging, the per-subscriber setting is retained on upgrade. Subscribers that had Private Secure Messaging enabled will have their message security set to "Encrypt only private messages." In previous versions, there was a system-wide setting in the Advanced Settings Tool that would enable Private Secure Messaging for all subscribers. That setting is not retained on upgrade. You can use Bulk Edit to enable Secure Messaging for all subscribers. If you are upgrading from a previous version and were using Private Secure Messaging, existing certificates are migrated as part of the upgrade and are available for decrypting any existing private secure messages.

If your subscribers use Cisco Unity ViewMail for Microsoft Outlook and you are using Secure Messaging, you must customize the ViewMail installation program to configure subscriber workstations for secure messaging and use ViewMail for Outlook version 5.0 or later. Earlier versions of ViewMail will not encrypt messages and subscribers could unknowingly be sending unsecured messages.

If you are using networking features in Cisco Unity, you must use Cisco Unity Voice Connector for Microsoft Exchange version 12.0(1) or later.

For more information refer to the Security Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Diagnostic Improvements

The diagnostic trace formatting has been improved and new micro traces have been added to the Cisco Unity Diagnostic Tool (UDT).

Message Notifications and Message Waiting Indicators

The change described in this section affects visual message waiting indicators (MWIs) and message notifications when a subscriber listens to a new message that is the only new message or that is the last new message of a group of messages.

The MWI remains on until the subscriber chooses an action that marks the message as read. In previous versions, the MWI turned off when Cisco Unity began playing the message and turned back on if the subscriber chose an action that marked the message as new.

When the subscriber chooses an action that marks the message as new, Cisco Unity does not initiate a repeat message notification (to a text pager, phone, etc.) for the message. In previous versions, Cisco Unity initiated another notification when the subscriber chose an action that marked the message as new.

For a new message, the following actions during or after message playback mark a message as read:

Save

Delete

Skip message, mark as saved

Hang-up (The message is marked as read only if the Mark a Message as Saved Upon Hang-up or Disconnection setting is enabled for the subscriber; otherwise, it is marked as new.)

For a new message, the following actions during or after playback leave the message marked as new:

Reply (and reply to all)

Forward

Skip message, save as new

Skip message, save as is

Play message properties

Toggle urgent flag

Play previous message

Play next message

Play first message

Play last message

Find a message by number

Send quick message

Call the subscriber (live reply)

Hang-up (The message is marked as new only if the Mark a Message as Saved Upon Hang-up or Disconnection setting is disabled for the subscriber; if the setting is enabled, the message is marked as read.)

If you prefer the behavior in earlier versions, you can use the Advanced Settings Tool to adjust a setting that controls this behavior. The setting is called Conversation—Delay Mark As Read.

Multiple Transfer Rules

Each subscriber has three transfer rules that you can customize: one for standard hours and one for closed hours of the active schedule, and an alternate transfer rule that, when enabled, overrides the standard and closed transfer rules. This gives subscribers the option to have their calls routed to a different extension when the office is closed, or they might configure an alternate transfer rule that routes their calls directly to voice mail while they are out of the office.

You configure the transfer rules on the applicable Call Transfer page for a subscriber template or an individual subscriber in the Cisco Unity Administrator, or by using the Bulk Edit utility. Subscribers can also configure transfer rules themselves using the telephone interface or on the Transfer and Screening Options page in the Cisco Unity Assistant.

By default, the alternate transfer rule is enabled for subscribers. In earlier versions, subscribers only had one transfer rule. If you are upgrading to Cisco Unity version 5.0(1), the existing values of subscriber transfer rules are retained as their alternate transfer rule.

On-Box Message Store with Failover for Cisco Unity Voice Messaging Configuration

The Cisco Unity voice messaging configuration supports installing message store (Exchange Server 2003 only) on the secondary server as a "two-box" solution for Cisco Unity failover.

Phone System Integrations Limited Only by Licensed Ports

Cisco Unity supports multiple simultaneous phone system integrations that are limited only by the number of licensed voice messaging ports. There are, however, the following exceptions:

Only one integration with a circuit-switched phone system through voice cards is supported on the Cisco Unity server.

A QSIG/DPNSS phone system integration must be the only phone system integration on the Cisco Unity server. QSIG/DPNSS phone systems integrations cannot be combined with any other phone system integrations.

For example, Cisco Unity can be integrated with the following phone systems at one time (a total of 22 phone system integrations):

Seven circuit-switched phone systems through PIMG/TIMG units

Seven Cisco Unified CM phone systems through Skinny Call Control Protocol (SCCP)

One circuit-switched phone system through voice cards

Seven Cisco Unified CM phone systems through SIP trunk

QoS Setting Is Configurable

The Quality of Service (QoS) settings for call signaling (SIP and SCCP) and for the media stream (RTP audio) can be configured in UTIM on the Tool menu.

Note that the QoS settings apply only to SIP, SCCP, and PIMG integrations.

The default settings have been changed to the following:

Call signaling—CS3

Media stream (RTP audio)—EF

Route Forwarded Calls by the First or Last Redirecting Number

Cisco Unity supports the option of routing calls based on either the first or last redirecting number when a call is forwarded to Cisco Unity.

Note the following:

This option requires Cisco Unity-CM TSP 8.1(2) or later.

This option is not supported by integrations through PIMG units.

This option can be changed through the Advanced Settings Tool (AST), which is available in Tools Depot.

SMTP Networking Not Supported (Cisco Unity With Microsoft Exchange Only)

Beginning with Cisco Unity 5.0(1), SMTP Networking is no longer supported.

If you are upgrading from an earlier version of Cisco Unity on a system configured for SMTP Networking, we recommend that you migrate from SMTP Networking to VPIM Networking before the upgrade.

Both SMTP Networking and VPIM Networking use SMTP as the mechanism for exchanging messages, but the message format differs. SMTP Networking uses a proprietary message format, while the message format in VPIM Networking adheres to the VPIM industry standard. In addition, VPIM Networking provides functionality that is not available in SMTP Networking.

Note that VPIM Networking is a licensed feature. It requires that you have an Exchange 2000 or Exchange 2003 server on which to install the Cisco Unity Voice Connector for Microsoft Exchange. For limitations related to Exchange 2007, see the "Cisco Unity with Exchange: Exchange Server 2007" section.

In addition to VPIM Networking, customers will still be able to set up Internet subscriber accounts for messaging with individuals who do not use Cisco Unity, but who have computers connected to the Internet.

For information about reconfiguring the system to use VPIM Networking instead of SMTP Networking, refer to the "Migrating from SMTP Networking to VPIM Networking" chapter in the Networking Guide for Cisco Unity.

The guide is available at http://cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

Support for Up to 144 Voice Messaging Ports

Depending on the system platform and system configuration, Cisco Unity can support up to a total of 144 voice messaging ports. Note the following requirements for the number of ports.

Number of Ports
Requirements

1 to 71

All integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP (including Cisco Unified CM and Cisco Unified CM Express)

Integrations with PIMG or TIMG units

Integrations with voice cards

72 to 96

The following integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP (including Cisco Unified CM and Cisco Unified CM Express)

Integrations with PIMG or TIMG units

If Windows 2003 is installed on the Cisco Unity server, the "Messaging - 72 or More Voice Ports - Enable Low-Fragmentation Heap" setting in the Advanced Settings Tool, which is in Cisco Unity Tools Depot, must be enabled.

If Exchange is the message store, the "Messaging - 72 or more voice ports - Number of MAPI Sessions per Exchange Server" setting in the Advanced Settings Tool, which is in Cisco Unity Tools Depot, must have the applicable setting.

97 to 144

The following integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP (including Cisco Unified CM and Cisco Unified CM Express)

Integrations with PIMG or TIMG units

Windows 2003 must be installed on the Cisco Unity server.

The 3GB and userva switches must be added to the Boot.ini file.

The "Messaging - 72 or More Voice Ports - Enable Low-Fragmentation Heap" setting in the Advanced Settings Tool, which is in Cisco Unity Tools Depot, must be enabled.

If Exchange is the message store, the "Messaging - 72 or more voice ports - Number of MAPI Sessions per Exchange Server" setting in the Advanced Settings Tool, which is in Cisco Unity Tools Depot, must have the applicable setting.


Tempu Logs Provide a History of Each Installation and Upgrade

The Tempu logs provide a history of installations and upgrades on the Cisco Unity server by the following changes:

The logs are saved in the CommServer\Logs directory.

The logs have file names in the format Tempu_<date>_<time>.log.

When a new Tempu log is created, the old logs are not deleted and the new log is not appended to an existing log. A new Tempu log is saved as a new and separate file. All Tempu logs will remain in the CommServer\Logs directory for future reference.

One Tempu log is created during Cisco Unity Setup and a second Tempu log is created when the Service Configure Wizard runs.

Installation and Upgrade Information

Downloading Software for Cisco Unity 5.0(1)

Upgrading to Cisco Unity 5.0(1)

Installing Cisco Unity 5.0(1) for the First Time

Installation and Upgrade Notes

Downloading Software for Cisco Unity 5.0(1)

Revised April 4, 2012

This section contains a procedure for downloading Cisco Unity 5.0(1) disc images, Cisco Unity Service Pack disc images, the Cisco Unity Server Updates wizard, and the latest Microsoft service packs recommended for use with Cisco Unity.

Even if you have Cisco Unity 5.0(1) discs, we recommend that you do the procedure to download:

The latest Cisco Unity Server Updates wizard, which contains the latest Microsoft updates recommended for use with Cisco Unity. The wizard is updated monthly.

Microsoft service packs qualified for use with Cisco Unity after the release of Cisco Unity 5.0(1), if any.

To Download the Software Required to Install Cisco Unity 5.0(1)


Step 1 See Table 1 to determine which Cisco Unity disc images you need:

You always need DVD 1.

You only need other DVDs if you want Cisco Unity to play the conversation in languages other than English-United States.

Step 2 Log on to a computer with a high-speed Internet connection, and confirm that the computer has sufficient hard disk space for all downloads. For the downloaded files and the extracted disc images or software, you will need approximately two times the download file size, which could total 10 GB or more, depending on which software you need. (The download file sizes appear on the download pages.)

Step 3 Go to each of the following download pages, and do the procedure to download all of the required files.


Note To access the software download page, you must be logged on to Cisco.com as a registered user.


Cisco Unity disc images, including languages, if applicable

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.


Note To access the software download page, you must be logged on to Cisco.com as a registered user.


b. In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity version 5.0.

c. Click Cisco Unity System Software, and click 5.0(1)a.

d. Follow the on-screen prompts to download the disc images that you need. Make note of the MD5 value for each disc image.

Cisco Unity Service Pack disc images

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity version 5.0.

c. Click Cisco Unity Service Packs, and click 5.0(1).

d. Click CiscoUnity5.0.(1)-ServicePacks-<language>-DVD1.exe, and follow the on-screen prompts to complete the download. Make note of the MD5 value.

Cisco Unity Server Updates wizard (contains Microsoft updates and Cisco Security Agent for Cisco Unity)

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity version 5.0.

c. Click Microsoft Updates for Cisco Unity/Unity Connection.

d. Click the latest version number, and follow the on-screen prompts to complete the download. Make note of the MD5 value.


Step 4 For each downloaded file, use a checksum generator to confirm that the MD5 checksum matches the checksum that is listed on Cisco.com. If the values do not match, the downloaded file is damaged.


Caution Do not attempt to use a damaged file to install software or the results will be unpredictable. If the MD5 values do not match, download the file again until the value for the downloaded file matches the value listed on Cisco.com.

Free checksum tools are available on the Internet, for example, the Microsoft File Checksum Integrity Verifier utility. This utility is described in Microsoft Knowledge Base article 841290, Availability and Description of the File Checksum Integrity Verifier Utility. The KB article also includes a link for downloading the utility.

Step 5 Extract the contents of each self-extracting executable file:

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

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

Step 6 Burn a DVD for each file that you downloaded and extracted. Label the discs with the contents and the current date, noting the following considerations:

Use the Joliet file system, which accommodates file names up to 64 characters long.

If the disc-burning application that you are using includes an option to verify the contents of the burned disc, choose that option. This causes the application to compare the contents of the burned disc with the source files.

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


Revised table August 31, 2007

Table 1 lists the contents of the Cisco Unity 5.0(1) DVD images that are available on Cisco.com. (The physical discs that Cisco ships when you order a Cisco Unity system include only three DVDs instead of five, so most languages are on different discs. Language abbreviations are printed on the discs.) The images contain only Cisco Unity software. They do not contain any third-party software.

Table 1 Contents of Cisco Unity 5.0(1) DVD Images 

DVD
Contents
1

The following software:

Cisco Unity application files

Cisco Personal Communications Assistant

Cisco Unity ViewMail for Microsoft Outlook

Voice-card driver files (required only when you are using voice cards to integrate Cisco Unity with a circuit-switched phone system)

Language files for the following languages:

ARA (Arabic-Saudi Arabia)

ENU (English-United States). Required for all installations.

2

CHS (Chinese-PRC)

CHT (Chinese-Taiwan)

CSY (Czech-Czech Republic)

DAN (Danish-Denmark)

DEU (German-Germany)

ENA (English-Australia)

ENC (English-Canada)

ENG (English-United Kingdom)

3

Language files for the following languages:

ENX (English TTY/TDD-United States)

ENZ (English-New Zealand)

ESO (Spanish-Colombia)

ESP (Spanish-Spain)

FRA (French-France)

FRC (French-Canada)

4

HUN (Hungarian-Hungary)

ITA (Italian-Italy)

JPN (Japanese-Japan)

KOR (Korean-Korea)

NLB (Dutch-Belgium)

NLD (Dutch-Netherlands)

5

Language files for the following languages:

NOR (Norwegian-Bokmål)

PLK (Polish-Poland)

PTB (Portuguese-Brazil)

PTG (Portuguese-Portugal)

RUS (Russian-Russia)

SVE (Swedish-Sweden)

ZHH (Chinese-Hong Kong SAR)


The Cisco Unity 5.0(1) Service Pack DVD 1 image includes the following software required to complete a Cisco Unity installation:

Cisco Unity System Preparation Assistant

Crystal Reports XI

Exchange 2000 SP 3

Exchange 2000 post-SP 3 rollup (KB 870540)

Exchange 2003 SP 2

Internet Explorer 6.0 SP 1

Microsoft .NET Framework

MSDE 2000 SP 4

MSXML3 SP 1

SQL Server 2000 SP 4

Windows 2000 SP 4

Windows Server 2003 SP 1

Windows Server 2003 SP 2

Upgrading to Cisco Unity 5.0(1)

For upgrades from earlier versions of Cisco Unity, refer to the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity.

Domino and Exchange versions of the guide are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


Caution Upgrading from Cisco Unity 3.x directly to Cisco Unity 5.0(1) is not supported. You must upgrade to Cisco Unity 4.x first, then upgrade again from 4.x to 5.x.

Installing Cisco Unity 5.0(1) for the First Time

For instructions on installing a new Cisco Unity 5.0(1) system, refer to the Installation Guide for Cisco Unity that matches the configuration you are installing. Installation guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. (For descriptions of the various installation guides, refer to Use the Installation Guide That Matches the Cisco Unity 5.x Configuration, also at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.)

Installation and Upgrade Notes

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

Customizing Cisco Unity System Prompts Is Not Supported

Example Subscriber Account Is Not Created During Cisco Unity Installation

Navigation Pane May Be Blank When Viewing the Cisco Unity Administrator in Japanese

Permissions Wizard Causes a Spike in Processing on All Domain Controllers in the Domain (Cisco Unity with Exchange Only)

Upgrade Effect on Diagnostic Traces and the Intel Dialogic Quiet Parameter

Upgrade from Cisco Unity 4.x Requires an Upgrade License

Upgrade from Cisco Unity 4.0(2) or Earlier to Version 5.0(1) Requires Reactivation of Optional Conversation 1

Using Chinese-PRC, Chinese-Taiwan, Chinese-Hong Kong SAR, Japanese, and Korean Text to Speech

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

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 when 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 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html. For information on the permissions set by the Cisco Unity Permissions wizard, refer to Permissions wizard Help.

Customizing Cisco Unity System Prompts Is Not Supported

System prompts are standard recordings that come with the Cisco Unity software, and they cannot be changed by phone or by using the Cisco Unity Administrator or the Cisco Unity Assistant. System prompts are played in different combinations in multiple places in the Cisco Unity conversation (phone interface). 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.

Example Subscriber Account Is Not Created During Cisco Unity Installation

In earlier versions of Cisco Unity, the Example Subscriber account was created during installation to provide an example configuration for subscriber accounts. Beginning with Cisco Unity version 4.0(3), the Example Subscriber account is not created, although it is not deleted when you upgrade from an earlier version of Cisco Unity.

Navigation Pane May Be Blank When Viewing the Cisco Unity Administrator in Japanese

Added December 13, 2007

When Cisco Unity is installed on an English version of Windows, the left-hand navigation pane on the Subscribers page may be blank when viewing the Cisco Unity Administrator in Japanese. The problem does not occur when Cisco Unity is installed on a Japanese version of Windows.

To fix the navigation pane on an English version of Windows, do the applicable procedure for the version of Windows installed on the Cisco Unity server:

To Fix the Navigation Pane on Windows Server 2003

To Fix the Navigation Pane on Windows 2000 Server

In the following procedure, you change the region and language options. If you installed Windows Server 2003 by using an English-language retail disc rather than the Cisco Unity Platform Configuration discs shipped with the Cisco Unity server, you need the Windows installation disc.

To Fix the Navigation Pane on Windows Server 2003


Step 1 Log on to the Cisco Unity server.

Step 2 On the Windows Start menu, click Settings > Control Panel > Regional and Language Options.

Step 3 Click the Regional Options tab.

Step 4 In the Standards and Formats box, in the Select an Item to Match Its Preferences list, click Japanese.

Step 5 In the Location list, click Japan.

Step 6 Click the Languages tab.

Step 7 If you installed Windows by using the Platform Configuration discs, skip to Step 8.

If you installed Windows by using an English-language retail disc, check the Install Files for East Asian Languages check box and skip to Step 9.

Step 8 Optional: If you installed Windows by using the Platform Configuration discs and want to change the Windows User Interface language on the Cisco Unity server to Japanese, in the Language Used in Menus and Dialogs list, click Japanese. (The list appears only when Windows was installed by using the Platform Configuration discs.)

Step 9 Click the Advanced tab.

Step 10 In the Language for Non-Unicode Programs box, click Japanese.

Step 11 Click OK to close the Regional and Language Options dialog box.

Step 12 If you installed Windows by using the Platform Configuration discs, skip to Step 13.

If you installed Windows by using an English-language retail disc, insert the Windows installation disc when prompted, then click OK to install additional language files.

Step 13 Restart the Cisco Unity server.


In the following procedure, you change the Windows system locale. You need the Windows installation disc.

To Fix the Navigation Pane on Windows 2000 Server


Step 1 Log on to the Cisco Unity server.

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

Step 3 On the General tab, in the Language Settings for the System list, click the Japanese check box.

Step 4 Click Set Default. The Select System Locale window opens.

Step 5 In the Appropriate Locale list, click Japanese, then click OK.

Step 6 Click OK to close the Regional Options dialog box.

Step 7 Insert the Windows installation disc when prompted, then click OK to install additional language files.

Step 8 Restart the Cisco Unity server.


Permissions Wizard Causes a Spike in Processing on All Domain Controllers in the Domain (Cisco Unity with Exchange Only)

When Exchange is the message store, always run the Cisco Unity Permissions wizard during off-peak hours except when you are installing a new Cisco Unity server in a Voice Messaging configuration and you are not creating subscriber accounts in the corporate directory. The Permissions wizard sets permissions at a granular level that requires more changes to the Active Directory database. (When Domino is the message store, the Permissions wizard sets very few permissions, so the effect on Active Directory is negligible.)


Caution When the Permissions wizard completes, the Lsass.exe process updates the Active Directory database with the new permissions. While Lsass.exe is processing the updates, it uses 100 percent of available processor time on the root domain controller in the domain and on one of the global catalog servers in the site where the Permissions wizard was run. (Other domain controllers in the domain and other global catalog servers in the forest are also affected, but the impact is less significant.) The updates take a few minutes to several hours, depending on the size of the database. Do not continue with the Cisco Unity installation or upgrade until Lsass.exe has finished processing the changes, or Cisco Unity Setup may fail.

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.

Upgrade from Cisco Unity 4.x Requires an Upgrade License

Upgrading to Cisco Unity 5.x requires that you purchase an upgrade license. The upgrade license activates Cisco Unity 4.x licensed features on a Cisco Unity 5.x system.

Upgrade from Cisco Unity 4.0(2) or Earlier to Version 5.0(1) Requires Reactivation of Optional Conversation 1

When you upgrade from Cisco Unity version 4.0(2) or earlier, the standard conversation is automatically activated for all subscribers. Therefore, you will need to reactivate Optional Conversation 1 after an upgrade (including maintenance-release upgrades) for those subscribers using it.

To do so, use either the Conversation settings on the template and subscriber pages in the Cisco Unity Administrator or the Bulk Edit utility to select Optional Conversation 1 for individual subscribers or for a particular group of subscribers. (In versions earlier than Cisco Unity 4.0(3), you could specify only a single conversation for all subscribers associated with a Cisco Unity server by using the Advanced Settings Tool to change the registry.)

For information on specifying conversation settings in the Cisco Unity Administrator, refer to the "Managing Conversation Settings That Are Controlled by Subscriber or Subscriber Template Settings" chapter of the System Administration Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

For information on specifying conversation settings in the Bulk Edit utility, refer to Bulk Edit Help.

Using Chinese-PRC, Chinese-Taiwan, Chinese-Hong Kong SAR, Japanese, and Korean Text to Speech

Chinese-PRC, Chinese-Taiwan, Chinese-Hong Kong SAR, Japanese, and Korean Text to Speech require specific language settings on the Cisco Unity server. For details, refer to the "Managing Languages" chapter of the System Administration Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Limitations and Restrictions

Cisco Unity with Domino: Phone Recording and Playback Does Not Work in IBM Lotus Notes with DUC for Cisco 1.2.4 or 1.2.5

Added February 24, 2009

When the IBM Lotus Domino Unified Communications (DUC) for Cisco csClient component version 1.2.4 or 1.2.5 is installed on a client computer with IBM Lotus Notes or iNotes/Domino Web Access, the phone recording and playback feature (known as TRaP) does not work when anonymous logon for remote access is turned off, which is the default setting in some operating systems. When using TRaP, the phone rings but when the user answers the phone, the status on the Notes message form becomes idle, and playback or recording fails.

To work around this issue, confirm that Cisco Unity Engineering Special 48 or later is installed on the Cisco Unity server and do the following procedure on the Cisco Unity server.

To Add the ProxyTrapIStream Registry Key on the Cisco Unity Server


Step 1 On the Cisco Unity server, start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (See the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, export the registry settings to a file.

Step 3 Expand the key

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Commserver Setup\1.0\Properties\.

Step 4 Add a new DWORD Value, naming it ProxyTrapIStream.

Step 5 Double-click the ProxyTrapIStream key you created in Step 4.

Step 6 In the Value Data field, enter 1, and click OK.

Step 7 Close Regedit.


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.

Delay When Subscribers Press 00 to Switch Search Modes in Cisco Unity Conversation

When subscribers press 00 to switch search mode, they will experience a delay before Cisco Unity responds accordingly. To avoid the delay, subscribers can press ## instead of 00. Alternatively, you can reduce the amount of time that Cisco Unity waits for key presses so that subscribers do not experience the delay.

Reducing the amount of time that Cisco Unity waits for more key presses can eliminate the delay when subscribers press 00 to switch search modes, but the change may adversely affect how subscribers interact with the Cisco Unity conversation as they address messages, update passwords, change call transfer or message notification numbers, and do other tasks. We recommend that you reduce the value specified for the Wait <x> Milliseconds For Additional Key Presses When Entering Names, Extensions, and Passwords field (also known as the Interdigit Timeout setting) only for individual subscribers who are likely to use 00, rather than for all subscribers associated with a Cisco Unity server.

The Wait <x> Milliseconds For Additional Key Presses When Entering Names, Extensions, and Passwords field is on the Conversation pages for individual subscribers in the Cisco Unity Administrator. Subscribers can also configure this setting themselves on the Advanced Setting page in the Cisco Unity Assistant. By default, Cisco Unity waits 3,000 milliseconds for additional key presses before it acts.

Message Monitor Cannot Be Enabled or Disabled for Individual Subscribers in Cisco Unity Administrator

To configure Message Monitor, you create a CTI application user for the Phone View features in Cisco Unified CM, and associate subscriber devices with the CTI user. Then, you configure Message Monitor in Cisco Unity for the phone system integration.

When the feature is configured, subscribers can enable or disable it themselves, however, you cannot enable or disable it for them in Cisco Unity Administrator.

To remove the feature for a subscriber, you can disassociate the subscriber device with the CTI user in Cisco Unified CM, but note that doing so removes all Phone View features for the subscriber.

Remote Desktop

Added January 17, 2008

When you configure Remote Desktop on the client computer, do not choose the option to bring sound to the client computer, or all incoming calls will be immediately disconnected. Instead, on the Local Resources tab, in the Remote Computer Sound list, click Leave at Remote Computer.

When you use Remote Desktop to log on to the Cisco Unity server remotely, do not use the /console option, or all incoming calls will be immediately disconnected.

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.

Text to Speech Does Not Read Name in the From Field in E-Mail

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. 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. When a message is from a Cisco Unity subscriber, the conversation plays the name (if one is recorded) or extension for that subscriber.

The design allows better TTS performance, and has worked as described since Cisco Unity 2.4(6). For more information, refer to caveat CSCdx95644. (If you have an account with Cisco.com, you can use Bug Toolkit to find caveats of any severity for any release. Bug Toolkit is available at the website http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.)

Web Pages That Contain the Media Master Control Bar Do Not Load Properly When Google Desktop Search Is Installed

When Google Desktop Search is installed on a subscriber workstation that uses Windows XP, the pages of the Cisco Personal Communications Assistant (PCA) and the Cisco Unity Administrator do not load properly in the browser.

Windows Application Event Log May Not Display Third-Party Product Name in Start-Up Log Entry

When Cisco Unity starts, an Event log entry is created with the version number of installed third-party software. Cisco Unity provides the product name to supplement the version number in the Event log entry. If support for a new version of a product (for example, a service pack) begins between releases of Cisco Unity, however, the Event log entry will not include the product name of the software. Because the information about the new version of the third-party software does not exist in its database, Cisco Unity cannot add the product name to the Event log entry.

Windows Terminal Services

Revised September 12, 2008

Using Windows Terminal Services (WTS) to access a Cisco Unity 5.x server is supported for all Cisco Unity installation, upgrade, and administration functions with the following exceptions:

Installing or upgrading Cisco Unity when Dialogic voice cards are used to integrate Cisco Unity with the phone system.

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

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

Running any application that causes the NIC to reset, for example, installing Cisco Security Agent for Cisco Unity.

Before you use WTS to access the Cisco Unity server remotely, note the following:

When you use WTS in console mode (available through the /console command line parameter), you must first install the Microsoft update and make the Windows registry change associated with Microsoft knowledge base article 928046, "A custom wave driver is unloaded when a remote client computer connects to a Windows Server 2003-based computer that is running a TAPI program." (Running Cisco Unity Server Updates wizard version 2.0(8) or later automatically installs the required update and updates the registry. See Software Installed by the Cisco Unity Server Updates Wizard at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.)

When you use WTS to install or upgrade Cisco Unity, you must disable and re-enable Cisco Security Agent for Cisco Unity as documented in the Release Notes for Cisco Security Agent for Cisco Unity, or the installation or upgrade will fail. The release notes are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

When you use WTS to install or upgrade Cisco Unity, or to make a large number of changes (for example, with tools such as Global Subscriber Manager or Bulk Edit), note that when a WTS session ends, it is permanently deleted from the server. Any applications running in the WTS session are forced to shut down, which can result in a loss of data and can leave the server in an unknown state. On the Cisco Unity server, verify that the Windows Terminal Service time out and reconnection settings are configured to prevent a session timeout and to prevent a session from automatically ending if the network connection is broken. (You can also change these settings in group policy.) In the Help for the Terminal Services Configuration MMC, under "Configure Time-out and Reconnection Settings," see the topic "Change settings for when a session limit is reached or a connection is broken."

Using Windows Terminal Services to access subscriber workstations for the recording and playback of messages by using Cisco Unity ViewMail for Microsoft Outlook is not supported.

Caveats

You can find the latest caveat information for Cisco Unity versions 5.0(1) and 5.0(1a)—in addition to caveats of any severity for any release—by using Bug Toolkit, an online tool available for customers to query defects according to their own needs. Bug Toolkit is available at http://www.cisco.com/go/bugs.


Note To access Bug Toolkit, you must be logged on to Cisco.com as a registered user.


This section contains caveat information for Cisco Unity Releases 5.0(1) and 5.0(1a) 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 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Open Caveats—Releases 5.0(1) and 5.0(1a)

Click a link in the Caveat Number column to view the latest information on the caveat in Bug Toolkit. (Caveats are listed in order by severity, then by component, then by caveat number.)

Table 2 Cisco Unity Releases 5.0(1) and 5.0(1a) Open Caveats 

Caveat Number
Severity
Component
Description

CSCsj03459

2

conversations

Streamlined Conversations are inconsistent in 4.2.1 es67

CSCsi82278

2

telephony

Unity: some ports stop answering a call (RNA)

CSCse80890

3

Activeassistant

CiscoPCA - Unable to contact server error message

CSCsb66422

3

conversations

Msg Locator times out on first search but additional searches work fine

CSCsc38298

3

conversations

Alt-X<MsgHeader-Body-Footer>SIP: [4] or [7] jumps fwd to next state.

CSCsd54083

3

conversations

Caller sent to opn. greeting instead of subs greeting when ACN disabled.

CSCsd75588

3

conversations

DOM: Message number not being played for invalid NDRs

CSCse46251

3

conversations

CSSS:fails to address to remote subscriber within defined CSSS

CSCse48735

3

conversations

Outside Caller maximum message length applied for IdentifiedSub Msgs

CSCse90932

3

conversations

Press-orSay[*] at After Record Resend goes to NDR Resend Menu

CSCsh10926

3

conversations

Phrase server initialization performance needs improvement

CSCsi77530

3

conversations

Subscriber can send messages with no recording

CSCsi83163

3

conversations

Using reply-all in TUI, cannot remove users from list

CSCsa79234

3

core

TTS service init unsuccessful upon completion of FailoverConfig

CSCsg49673

3

core

MAL attempts mailbox sync for subs without mailboxes

CSCsg76524

3

core

BusinessLogicManagerSvr.dll violates DLLMain rules and causes deadlock

CSCsi00810

3

core

Incorrect message notification data for some scenarios

CSCsi22389

3

core

Slow memory leak in AvCsMgr Virtual Bytes

CSCsi61540

3

core

Unity notification failure with Domino integration

CSCsd44843

3

database

JPN: Imported subscriber's display name is not displayed correctly

CSCsg38021

3

database

Adding ports does not increment values in NotificationMWI table

CSCsg48849

3

database

SQL Rep agents checkup fails to run, logs error every 10 minutes

CSCsd29764

3

documentation

Stranded GlobalSubs when converting two standalone systems to Failover

CSCsa84016

3

dommessaging

DBridge-NDR Inbound directory msg if no matching bridge locs exist

CSCse54029

3

dommessaging

DBridge-IGD removes wave parts from outbound fax messages to bridge

CSCse54039

3

dommessaging

DBridge-any NDR message going back to Bridge is double-base64-encoded

CSCsi81757

3

dommessaging

Dom: NDRs are not forwarded to Unaddressed Messages list

CSCsi49688

3

ducs

DOM:DUC DWA7 Fails after imported into Unity

CSCsf06231

3

exchvoicegateway

Voice Connector (IVC): send NDR if recipient does not have OMNI Address

CSCsd16072

3

exmessaging

AvCsMgr and/or AvUMRSnycSvc crash when GC goes offline

CSCse07449

3

exmessaging

DSAD directory write failure events should list the property and value

CSCsf06284

3

exmessaging

Unity 4.0(5) Message Store Configuration Wizard giving generic error

CSCsh61456

3

exmessaging

Delay during Blackberry notification from Unity

CSCsh81214

3

exmessaging

UMR - Doh session cycling not observed

CSCsi19114

3

exmessaging

Exchange Out of Office message shows up in Voice Stack

CSCsi62337

3

exmessaging

RPC exception in EMSMDB32 causes message delivery failure

CSCsa86402

3

failover

Failover: MWI can get out of synch

CSCsd02261

3

failover

AvCsGateway errors during failover config, AvCsMgr fails to start

CSCsg42621

3

failover

Failover: SQL Replication does not startup correctly upon reboot

CSCsi50517

3

failover

Failover: SQL replication jobs can fail and provide no warning

CSCsg45153

3

import

Bulk Import CSV ZERO_KEY_RULE does not Attempt Transfer to Callhandler

CSCsd50689

3

localization

JPN: TUI: wrong translation on broadcast message

CSCsd91284

3

localization

JPN: TUI translation of Alternate Contact Number differs from GUI

CSCsk16660

3

localization

ML: PW (DEU) - Text overlapping an icon on Choose Message Store pg.

CSCsd63459

3

messagemonitor

MessageMonitor - Delay in conversation between greeting and record beep.

CSCsg27013

3

messagemonitor

MM:When pressing Ask diags show Take_Call

CSCsg42469

3

ossetup

new domain user gets blank desktop after login

CSCsd39975

3

pca

PCA cannot read or write to database when JDBC connections are refused

CSCse66503

3

pca

PCA:CSSS restrictions not honored when assigning memb to Priv Lists

CSCse66880

3

pca

PCA:Unity Inbox does not honor CSSS settings

CSCsg09004

3

pca

+ not accepted as a valid data in text input box for phone num in UA

CSCsi73888

3

pca

PCA Unity4.2.1- UK language reverse day with month in Alternate Greeting

CSCsk21510

3

reports

ML:PDL report doesn't include members in the output

CSCsb28092

3

sa

SA - Interview Handler: Recorded questions cannot be saved

CSCsc86904

3

sa

WS03: Cannot log back in to SA after timeout

CSCsd40043

3

sa

SA able to be opened by install account by default

CSCsd51924

3

sa

PGR does not get copied when creating a new COS based on a existing COS

CSCsd93420

3

sa

DirHdlr:if location set as search scope removed, unitydb not cleaned up

CSCse95430

3

sa

unity sa web page is blank after clicking on any link

CSCsf04733

3

sa

With minimal permissions msExchHideFromAddressLists should be grayed out

CSCsh82690

3

sa

Alternate Contact Number does not apply for a Call Handler

CSCsi43384

3

sa

Garbled characters on Unity System Administration when remote accessing

CSCsi56059

3

sa

SA: Increasing session timeout can cause access denied error w/ Win2k3

CSCsd05236

3

setup

DOM: MSCW does not verify service account creation properly

CSCsd05883

3

setup

Authentication method on web virtual directories reset during upgrades

CSCse87434

3

setup

SETUP: Buffer overflow and crash when PATH is too long

CSCsf01695

3

setup

Fresh Install will fail if unitydb.mdf file exists in the SQL Data Dir

CSCsi00319

3

setup

CUSPA should check for TFTP.EXE on Windows 2003 installations

CSCsi21639

3

setup

CUSPA for all languages except ENU can not be installed MSDE/SQL SP4

CSCsi54038

3

setup

UTIM Failed Loading the MIURegistry Component Error 0x800705

CSCsi99059

3

setup

Latest TSP and ES disappear after installing new languages on the unity

CSCsj12345

3

setup

CUSPA does not force networking protocols flag to be enabled for MSDE sp

CSCsi51247

3

tbd

BSOD on 7845-H2 with CSA and Windows 2003 SP2

CSCsc44476

3

telephony

Standard<EmailMsgBody>: Delay upon selection - [1], [3], [7], [9] or [#]

CSCsc44495

3

telephony

Standard<TTS>: Speed UP/DOWN keys are inconsistent.

CSCsc96838

3

telephony

MI: MWI Status not transferred to new phone when sub moved to new switch

CSCsd71904

3

telephony

SIP/PIMG - Disconnect tone trim compensation needs to be configurable

CSCsf99966

3

telephony

Unity TSP should not attempt to transfer a call on hold

CSCsg91152

3

telephony

Unity fails to clear port properly on SMDI integration

CSCsh32681

3

telephony

CME SIP: Call xferred from Unity to invalid number should be fwded to VM

CSCsi77476

3

telephony

Unity Ports Stop Answering Incoming Calls After Connect Timeout

CSCsg23521

3

upgrade

ES installer fails to replace/upgrade specific files

CSCsb78351

3

utilities

RSK: Unity Directory Service not reflected correctly using SNMP Query

CSCsd48043

3

utilities

PW: if import only selected, cannot recreate unity_<servername> account

CSCsd52601

3

utilities

CUBI:try to modify without Admin AD permissions returns no errors

CSCsd53143

3

utilities

CUBI:does not modify DISPLAY_NAME value

CSCsd71523

3

utilities

CUBI: popup error when changing DTMF ID even though change accepted

CSCsd98936

3

utilities

DOM: DUT scan in inaccurate when the partner server is down

CSCse12359

3

utilities

PW: Permissions Wizard does not ensure vm interop applied.

CSCse78060

3

utilities

Unity and Locations OUs created under domain root by Report mode

CSCsg27007

3

utilities

UDT: need mAcro trace option for Message Monitor

CSCsg27489

3

utilities

MSD: Error handler's need to protect against infinite loops

CSCsg38096

3

utilities

IpFax Service not working with Exchange 2003 SP 2

CSCsi39962

3

utilities

SECURE: GSM does not delete Trusted Internet contacts

CSCsi68156

3

utilities

GrantUnityAccess.exe fails with one-way trust between two forest roots

CSCsi72132

3

utilities

Port Status Monitor real-time status crashes for 144 ports

CSCsg36594

3

voicecsa

CSA 4.5.1 [2.0.3] for Unity stops automatic service startup

CSCsk12509

4

sa

ML: JPN - Status Monitor: Reports display in ENU not the dflt GUI (JPN).

CSCsj06285

6

tbd

Need decrease in non-TUI MAPI cache allocations, or potential for crash.


Resolved Caveats—Releases 5.0(1) and 5.0(1a)

Revised February 3, 2009

Click a link in the Caveat Number column to view the latest information on the caveat in Bug Toolkit. (Caveats are listed in order by severity, then by component, then by caveat number.)

Table 3 Cisco Unity Releases 5.0(1) and 5.0(1a) Resolved Caveats 

Caveat Number
Severity
Component
Description

CSCse99215

1

conversations

Msg with large no of recipients/DL may result in dead air & pegs AvCsMgr

CSCsb11049

1

telephony

AvAudio.sys causes a blue screen due to incorrect version information

CSCsh39245

2

conversations

Release transfer to non-local subscriber extension does not convert xfer

CSCsh54425

2

conversations

ISM enabled for remote subscribers may cause messages to be discarded

CSCsb07455

2

dommessaging

DOM: MTA messages may not get delivered when server back online

CSCsb43902

2

exmessaging

AvWM wrongly detects exchange server as being down

CSCsb11449

2

failover

Unity gets into a failover/failback loop when Domino is disconnected

CSCse30348

2

failover

Duplicate DTMFAccessID's are added to SQL DB with same ParentObjectID

CSCsb16302

2

import

JPN: CUBI for Domino reports error when Domino user has JPN alt name

CSCee77821

2

sa

JPN: JPN char in AD Display Name do not show up SA after SA Import

CSCsb05513

2

sa

JPN: Can not import subscriber with double byte name from directory

CSCsf26335

2

sa

CPCA/Cisco Unity SA may causes Inetinfo.exe service to hang

CSCeb63426

2

telephony

Unity sending comfort noise packets can cause gateway jitter

CSCse76319

2

telephony

Unity sends 3rd Transfer if Connected received after 2nd Transfer

CSCsg97844

2

telephony

Unity 4.2(1) server crashed - bugcheck analysis shows avaudio.sys

CSCsg40430

2

utilities

UDT - Gather Logs Wizards does not consider AM or PM

CSCsh15645

2

utilities

GSM Moved accounts missing Exchange info in SQL

CSCsb51339

3

bridgeconnector

Directory updates between Unity and the Bridge fail. Diags need more inf

CSCea53708

3

conversations

Incomplete address searcher prompts played in message options menu

CSCsa70526

3

conversations

Deleting a vm very fast and hitting EndCall key does not delete the vm

CSCsa82816

3

conversations

MessageLocator- Intermittent- Incorrect results returned from search.

CSCsa86792

3

conversations

Login at Greeting to send message broken if Record first

CSCsa91074

3

conversations

TUI marks replies and fwd'ed msgs urgent when org msg was marked urgent

CSCsa96626

3

conversations

Reply-To-All should not be possible when there is only one recipient

CSCsa96843

3

conversations

Failsafe pressing 3 while attempting to re-record a message

CSCsb05741

3

conversations

New Feature for Requiring Recorded Name for Subscriber Enrollment fails

CSCsb11310

3

conversations

Message Locator diags for InitialSearchTotal do not show value returned

CSCsb14168

3

conversations

Double keypress wait time activated after second keypress received

CSCsb28324

3

conversations

Length of Minimum Password Announce Does Not Match What is Set on System

CSCsb35525

3

conversations

Unity applies incorrect prompt speed during subscriber conversation

CSCsc71818

3

conversations

Incorrect greeting played after call holding and RNA

CSCsd26083

3

conversations

Address searcher ## interdigit timing not consistent with other states

CSCse43241

3

conversations

Unity Future Delivery of message feature not working for some dates

CSCse51330

3

conversations

SIGNIN: Wrong subscriber prompted to change password

CSCsf08292

3

conversations

TUI interface incorrectly reports closed greeting is active

CSCsf10951

3

conversations

Addressing prompt heard after selection to leave msg for sub

CSCsf14583

3

conversations

Cross server login fails when delays in setting up calls with CCMs

CSCsf14610

3

conversations

Reply-To-All to a large number of recipients can cause delays

CSCsf30006

3

conversations

DCR: Orphan message does not get sent if mailstore goes down

CSCsf31161

3

conversations

TUI - wrong prompt after reply-all key press 42 and after deleting the

CSCsg18773

3

conversations

Reply-All in Diverse Networks: provide logic/prompts for two cases

CSCsg28060

3

conversations

Cannot address message to DL when search returns more than one match

CSCsg30490

3

conversations

Remove or 00 from switch address modes prompt

CSCsg52066

3

conversations

Subscriber not able to toggle between Standard and Alternate greeting

CSCsg90913

3

conversations

Inconsistent subject line on subscriber to subscriber message

CSCsh52771

3

conversations

Networking - Advanced Setting to toggle ISM for remote subs. not honored

CSCsh55135

3

conversations

Message Notification only accepts first 20 digits when setup over TUI

CSCsh56194

3

conversations

Cross-server transfers not accepted to VPIM Bridge AMIS subs

CSCsh65175

3

conversations

SECURE: First message encryption attempt always fails on clean install

CSCsi01116

3

conversations

sub restricted from sending to PDLs can still reply-all to PDLs

CSCsi76164

3

conversations

DOM: Msg sent to a sub even if deleted from reply to all recipient list

CSCsi82851

3

conversations

Crossbox: transfer fails with Handoff Response = ##

CSCsi86913

3

conversations

Crossbox: No configurable timeout for digits received during transfer

CSCec51860

3

core

Unity gives no warning when CommServer dir is write protected

CSCee49288

3

core

Failover: FCW fails during secondary with WS03 fresh install

CSCee58965

3

core

Integration performance ctrs unavailable after add/del of ports

CSCee58989

3

core

ResourceMgr performance needs improving

CSCef63802

3

core

MWI resynchronization event messages do not audit the requestor

CSCef87812

3

core

AppEvents: Consolidate Info Events on Unity Startup and Shutdown

CSCsb55868

3

core

Blackberry - Need to restart WWW Pub Svc for UDT diags to take effect.

CSCsc91977

3

core

Unity does not log an event if call presented to MIU but not answered

CSCse38429

3

core

Need more diagnostics to troubleshoot Reply via TUI

CSCsg49334

3

core

License Pooling does not work between Unity 4x and 5x versions.

CSCsh59924

3

core

Need Macro trace for troubleshooting Ring no answer problems in Unity

CSCsi56850

3

core

Crash in AvCsMgr while loading Event Log

CSCsa72233

3

csbmsgconnector

Dirt - Cant access Broadcast Msg mailbox, record removed from sub table

CSCsb31813

3

database

WS: When adding subscriber through CUALS, Unity System becomes unstable

CSCsd13958

3

database

Upgrade fails at replacing SqlWeeklyBackupJob if server name changed.

CSCsd93323

3

database

DirHdlr: if PDL set as search scope is removed, unitydb not cleaned up

CSCse78105

3

database

DCR message timeout settings should be in minutes, not milliseconds

CSCsg80256

3

database

ML: SA Conversation Style dropdown box unpopulated

CSCsh02771

3

database

10 entries in CS_Default* restriction table will break table.

CSCsh94992

3

dialogic

Domino NDN causes Unity crash

CSCsb73349

3

documentation

AST does not consider Failover possibility for the UnityMTA directory

CSCsb53397

3

domdirconnector

DOM: Special Chars in shortname for interop subs don't save in NAB

CSCsb53723

3

domdirconnector

DOM: CUBI CSV Create/mod subscriber w/ existing doc fails w/ spec chars

CSCsf10680

3

domdirconnector

DOM: deleted Domino users are not removed from GlobalSubscriber table

CSCsa76348

3

dommessaging

DVPIM: Message sent with no valid attachment not returned by IGD

CSCsa83724

3

dommessaging

DOM: Upgrade from early Unity version with multiple address books fails

CSCsb03504

3

dommessaging

DOM: MSCW does not run syscheck when verifying address book information

CSCsb04480

3

dommessaging

DOM-Unity does not handle 0x0A0A error response from clstr svr when down

CSCsb17276

3

dommessaging

Unity does not recognize Danish Character set

CSCsd06331

3

dommessaging

DOM<StreamReply-All>: Press [92] - List of names includes reply-sender.

CSCse34506

3

dommessaging

Dom: Interop Gateway fails reading audio format of file from Bridge

CSCsf09185

3

dommessaging

DominoMonitor Incorrectly logs warning of subscriber not being monitored

CSCsi92237

3

dommessaging

Dom: TUI does not announce NDRs

CSCsd48585

3

exchvoicegateway

Bridge directory bulk synchronization fails to add all contacts

CSCsd56197

3

exchvoicegateway

IVC: smtp pickup path calculation needs to be more precise

CSCsb16145

3

exdirconnector

ML: new PDL with non-ascii name cannot be sent message

CSCsb21514

3

exdirconnector

Unity scope DL sync for AD unnecessarily invoked

CSCee20569

3

exmessaging

Recipient name not in To: field after added in Resend msg in Outlook

CSCsa74121

3

exmessaging

No diags for troubleshooting mailbox limits with Exchange

CSCse82142

3

exmessaging

CiscoUnity_AvCs report an exception AvExchangeMonitorSvr.dll

CSCse87553

3

exmessaging

MAPI GC reconnect always logs down GC as GC used at startup

CSCef23621

3

failover

Failover wizard does not check for share permissions

CSCsf01602

3

failover

On failover some ports on primary stay registered with CCM integration

CSCsi64012

3

failover

FCW fails to verify SQL is installed with WS03 3SP2

CSCsa85454

3

import

CUBI: Import of AD users may fail depending on containers

CSCse87865

3

import

Change greeting to CUBI subscriber will change all others to default

CSCsi74833

3

import

CUBI Does not use some settings in chosen subscriber template

CSCee77223

3

licensing

JPN: Lic Wiz reports error when clicking Next on first dialog

CSCsb16148

3

localization

ML: Unable to add sub with special chars using SA on FRC system

CSCse78004

3

pca

Distribution List tab in Cisco PCA is slow or hangs

CSCse80370

3

pca

Cisco PCA appears to automatically log user out or gives error messages

CSCsg03144

3

pca

Notify Me Of Voice Messages cannot be saved as None in CPCA

CSCsh61866

3

pca

Unity Inbox: time stamp adjustment incorrect for Eastern and Atlantic

CSCeb82281

3

reports

Reports are failing

CSCsa81987

3

reports

Unity Reporting produces unexpected behavior for cancelled reports

CSCeb48662

3

sa

Subscriber account lockout status is inaccurate for locked subscriber

CSCsa92048

3

sa

Internal Server Error when trying to unlock user from Saweb

CSCsa96920

3

sa

Unable to remove extra digits in message notification device

CSCsa99379

3

sa

Add subscriber button shows domain name rather than DC name when DC down

CSCsb16930

3

sa

Import check for valid data lists variable name instead of property name

CSCsb17396

3

sa

Can not change failed option for message notification to none

CSCsb47717

3

sa

SA: w/SSL, server chooser page error: The page must be viewed over...

CSCsd45689

3

sa

SA:Show subscriber in e-mail server... not gray when admin AD not cked

CSCsd83395

3

sa

JPN: cannot delete schedule with non-ASCII name

CSCsd98785

3

sa

Unity Dialing Domain not saving on SA pages

CSCse97837

3

sa

Dial Strings in the Restriction Tables page may not display

CSCsg80267

3

sa

System/Config/Phone Languages TTS dropdown allows nonTTS langs

CSCsh00106

3

sa

SA: Changes to some SA pages are not logged

CSCsh35528

3

sa

Unity greeting expired when standard greeting wave file is pasted

CSCsh52803

3

sa

SA - Subs. Standard Greeting shows disabled if recorded and saved via SA

CSCuk53403

3

sa

FRA: unity SA/Integration is not localised

CSCsb02180

3

setup

Unity setup allows root drive install

CSCsb62248

3

setup

SysCheck: after clicking Finish, popup error: The instruction at 0x...

CSCsb81662

3

setup

MSCW does not check for mailstore rights during partner server selection

CSCsd43608

3

setup

Incorrect Unity version in Windows registry fails re-install

CSCsd70432

3

setup

Unity Should Track Changes To Configured INI File

CSCsd99610

3

setup

MSCW exits without error when trying to connect to Exchange partner

CSCse00462

3

setup

MSCW:logged on as a non-Exch Admin, popup error indicates invalid pswd

CSCsg07331

3

setup

Service Configuration Wizard exits after selecting dir service account

CSCsg98033

3

setup

Setup: New Install on W2K3 with IE 7 fails

CSCsh60306

3

setup

Win2k3 SP2 with Unity 4.2.1 fails in setup looking for sp1

CSCsa65954

3

telephony

Greeting is intermittently played as no audio or hum - one way audio

CSCsb05840

3

telephony

AvAudio.sys incorrectly reports out-of-sequence packets

CSCsb06144

3

telephony

Abandoned offered calls cause some ports to go RNA

CSCsb35503

3

telephony

Unity falsely reports silence timeout and stops recording

CSCsd92207

3

telephony

TSP sees double digit when both RFC2833 and SCCP digits are used

CSCse32895

3

telephony

PIMG: Eventvwr err's on Unity shutdown when Serial Integrations enabled

CSCsg07329

3

telephony

Listening to all greetings through PIMG/SIP integration fails

CSCsh35344

3

telephony

failed xfer initiate may cause delay in clearing port

CSCsh61717

3

telephony

ext remapping fails with dup entry error even if ports are distinct

CSCsh97318

3

telephony

No disconnect if caller puts Unity on hold during supervised transfer

CSCsi16038

3

telephony

Heap Corruption in UnitySipStack.dll

CSCsi85064

3

telephony

Crossbox: Transfer response timeout should be configurable

CSCsi89941

3

telephony

Cross-box transfer - Transmitted digits delayed by TAPI

CSCsb57898

3

upgrade

Upgrading from 4.0.4 to 4.0.5 may AddUnityRealm to generate exception

CSCsc89407

3

utilities

Permissions Wizard computer object rights assignment not flexible enough

CSCse17109

3

utilities

WaveGain settings at new Registry Location, Tools need Updating

CSCse78071

3

utilities

Permissions Wizard allows single account for directory and msg services

CSCse78095

3

utilities

PWRM missing AMIS/VPIM/Bridge menu and the related mandatory tests

CSCsg06666

3

utilities

Port Usage analyzer cannot deal with different regional settings

CSCsg60890

3

utilities

VMO MediaMaster Unable to Connect to Voice Server with W2K3 SP1 on Unity

CSCsf03101

3

viewmail

VMO: Upgrading to 4.21,4.22, 5.0 does not retain some registry settings

CSCsg69620

3

vpimconnector

SetG726RiffHeader registry key doesn't function


Documentation Updates

Errors

This section lists errors in the current documentation for Cisco Unity and gives corrected information. The correct information will be incorporated in a future documentation release, or as otherwise noted.

Cisco Unity Installation Guides for Cisco Unity 5.x: Making the Cisco Unity Server a Domain Controller in a Failover Configuration

Added May 22, 2009

In the following Cisco Unity installation guides, a few passing mentions imply that you can make the Cisco Unity servers in a failover configuration into domain controllers:

Installation Guide for Cisco Unity Release 5.x in a Unified Messaging Configuration with Microsoft Exchange (With Failover Configured)

Installation Guide for Cisco Unity Release 5.x with IBM Lotus Domino (With Failover Configured)

In a failover configuration, making the Cisco Unity server a domain controller is supported only when Cisco Unity is configured for Voice Messaging and when the message store is installed on the secondary Cisco Unity server. For more information on this configuration, see the "Failover Requirements When the Message Store Is Installed on the Secondary Cisco Unity Server" section of the System Requirements for Cisco Unity Release 5.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/requirements/50cusysreq.html.

Failover Configuration and Administration Guide for Cisco Unity Release 5.x: Behavior of Cisco Unity Failover During Outages of Network Components

Added June 18, 2008

In the "Outage Scenarios for Networks of Windows and Exchange" and the "Outage Scenarios for Networks of Windows and IBM Lotus Domino" sections in the "Behavior of Cisco Unity Failover During Outages of Network Components" chapter, the disconnection behavior when the Exchange or IBM Lotus Domino server is disconnected from the network is partially incorrect.

When the Exchange or IBM Lotus Domino server is disconnected from the network, subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension. Subscribers cannot log on to Cisco Unity.

Incorrect

Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the primary server.

Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension or logging on to Cisco Unity. The new messages are stored in the UnityMTA folder on the secondary server.

Correct

Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension. The new messages are stored in the UnityMTA folder on the primary server.

Subscribers homed on the same Cisco Unity server can leave messages for each other by dialing an extension. The new messages are stored in the UnityMTA folder on the secondary server.


System Administration Guide for Cisco Unity: Phone View Features

Added August 31, 2007

The "To Configure Cisco Unified Communications Manager for Phone View (Cisco Unified CM 5.x and Later)" procedure in the "Phone View Features" section in the "Managing Phone View Features and Remote Message Monitor" chapter of the System Administration Guide for Cisco Unity is incorrect. Use the following procedure instead:

To Configure Cisco Unified Communications Manager for Phone View (Cisco Unified CM 5.x and Later)


Step 1 In Cisco Unified Communications Manager Administration, click User Management > Application User.

Step 2 On the Find and List Application Users page, click Add New.

Step 3 On the Application User Configuration page, do the following sub-steps to create a CTI user account that will have access to all subscriber phones for Phone View:

a. In the User ID field, enter a unique name for the CTI user. For example, enter "PhoneViewUser."

b. In the password field, enter a password for the user.

c. In the Confirm Password field, re-enter the password that you entered in Step 3b.

Step 4 In the credential policy for the Phone View CTI user, ensure that the User Must Change at Next Login check box is unchecked and the Does Not Expire check box is checked. Otherwise, Phone View will not work.

Step 5 Associate the subscriber phone devices for which you want to enable Phone View with the new CTI user.

Step 6 Click Save.

Step 7 Continue with the "To Enable Phone View on the Cisco Unity Server" procedure on page 12-2.


Omissions

This section lists new and additional information that is not included in the current documentation for Cisco Unity. The new and additional information will be incorporated in a future documentation release, or as otherwise noted.

Cisco Unity Integration Guides: Planning How the Voice Messaging Ports Will Be Used by Cisco Unity

Added March 20, 2009

The "Determining How Many Voice Messaging Ports Will Answer Calls" section of the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" chapter in most Cisco Unity integration guides, the following recommendation was omitted:

We strongly recommend and consider it a best practice to configure most voice messaging ports to only answer calls and the remaining ports to only dial out or perform MWI functions. This configuration eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes that port off-hook to dial out.

This recommendation does not apply to the following Cisco Unity integration guides:

Cisco Unified Communications Manager SIP Trunk Integration Guide 

Cisco Unified Communications Manager Express SIP Trunk Integration Guide 

QSIG-Enabled Phone System with Cisco ISR Voice Gateway Integration Guide 

QSIG/DPNSS Phone System with Cisco EGW 2200 Integration Guide 

Session Initiation Protocol (SIP) Integration Guide 

Installation Guide for Cisco Unity Release 5.x with IBM Lotus Domino: Installing and Configuring Cisco Unity Software

Revised April 4, 2012

In the "Installing and Configuring Cisco Unity Software" section in the "Installing and Configuring Cisco Unity Software" chapter of the Installation Guide for Cisco Unity Release 5.x with IBM Lotus Domino, the following information for the "Patching the Cisco Unity Server for Notes 8.x Support" subsection was omitted.

Do one or both of the procedures in this section immediately after you complete the subsection "Starting the Cisco Unity Installation and Configuration Assistant and Installing Cisco Unity Software," as applicable. (At the end of the "Starting the Cisco Unity Installation and Configuration Assistant and Installing Cisco Unity Software" subsection, you restart the Cisco Unity server from within the Cisco Unity Installation and Configuration Assistant.)

The first procedure—"To Patch Cisco Unity for IBM Lotus Notes 8.x Support"—is necessary only if you installed IBM Lotus Notes version 8.x on the Cisco Unity server in the "Setting Up Domino and Installing Lotus Notes" chapter.

The second procedure—"To Add the Domino 8.5.x MailFileTmplt Registry Key on the Cisco Unity Server"—is necessary only if you installed Domino version 8.5.x on the Domino server on which the Cisco Unity Domino Person mail file resides in the "Setting Up Domino and Installing Lotus Notes" chapter.

When you have completed one or both procedures, continue with the instructions in the "Installing License Files" subsection in the Installation Guide.

If Cisco Unity failover is configured, do the applicable procedures on both the primary and secondary servers.

To Patch Cisco Unity for IBM Lotus Notes 8.x Support


Step 1 Log on to the Cisco Unity server by using the Cisco Unity installation account. The Cisco Unity Installation and Configuration Assistant opens. Although you will not use it in this procedure, you can leave it running, or close it now and reopen it later in the installation by using the desktop shortcut.

Step 2 Download the patch from Cisco.com:

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 5.0.

c. Click Cisco Unity System Software.

d. In the All Releases section, expand Cisco Unity v.5, and click 5.0(1).

e. In the right pane, click CiscoUnity_5.0(1)_LotusNotes8.xSupport.exe.

f. Follow the on-screen prompts to complete the download.

Step 3 Disable and stop the Multi-user Cleanup Service:

a. On the Windows Start menu, click Programs > Administrative Tools > Services.

b. Right-click the Multi-user Cleanup Service and click Properties.

c. On the General tab, in the Startup Type list, click Disabled.

d. Click Stop to stop the service immediately.

e. Click OK to close Properties, and close the Services MMC.

Step 4 Install the patch that you downloaded in Step 2:

a. Copy the self-extracting executable file CiscoUnity_5.0(1)_LotusNotes8.xSupport.exe to the root of the CommServer directory on the Cisco Unity server.

b. Double-click the self-extracting executable file to extract the contents to the root of the CommServer directory. The following files will be extracted:

Setup.exe, to the Commserver\ConfigurationSetup directory

TestNotesInstall.xml, to the Commserver\Syscheck\DEU\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\ENU\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\FRA\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\JPN\Domino directory

CiscoUnity_5.0(1)_LotusNotes8.xSupport_ReadMe.txt, to the Commserver directory

Step 5 Delete the self-extracting EXE file.

Although you may safely delete the file CiscoUnity_5.0(1)_LotusNotes8.xSupport_ReadMe.txt from the Commserver directory, you may want to leave the file there as a reminder that this patch has been installed, because information about this patch is not reported in the Gather Cisco Unity System Information utility.

Step 6 If you installed Domino version 8.5.x on a Domino server in the "Setting Up Domino and Installing Lotus Notes" chapter, continue with the "To Add the Domino 8.5.x MailFileTmplt Registry Key on the Cisco Unity Server" procedure. Otherwise, return to the Cisco Unity Installation and Configuration Assistant and continue with the Cisco Unity installation.


To Add the Domino 8.5.x MailFileTmplt Registry Key on the Cisco Unity Server


Step 1 On the Cisco Unity server, start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (See the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, export the registry settings to a file.

Step 3 Expand the key

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors.

Step 4 Within Directory Connectors, add a new Key named DirSynchDomino.

Step 5 Within DirSynchDomino, add a new Key named 1.00.

Step 6 Within DirSynchDomino\1.00, add a new String Value named MailFileTmplt.

Step 7 Double-click the MailFileTmplt key you created in Step 6.

Step 8 In the Value Data field, enter mail85.ntf, and click OK.

Step 9 Close Regedit.

Step 10 If you closed the Cisco Unity Installation and Configuration Assistant in Step 1 of the "To Patch Cisco Unity for IBM Lotus Notes 8.x Support" procedure, restart it now.


Installation Guide for Cisco Unity Release 5.x in a Voice Messaging Configuration with Microsoft Exchange: Overview of Mandatory Tasks for Installing Cisco Unity

Added November 12, 2009

In both failover and non-failover versions of the Installation Guide for Cisco Unity Release 5.x in a Voice Messaging Configuration with Microsoft Exchange, the following task was omitted from the end of the "Populating the Cisco Unity System with Subscriber and Call Management Data" section in the "Overview of Mandatory Tasks for Installing Cisco Unity" chapter.

As applicable, forward voice messages for selected Cisco Unity subscribers to an SMTP email address. This is useful for subscribers who want to listen to their voice messages by using mobile devices that have been configured for mobile mail. For more information, see the applicable article on the Microsoft website:

Exchange 2007: Knowledge Base article 851509, "How to Configure Mail Forwarding in Exchange Server 2007"

Exchange 2003: Knowledge Base article 281926, "How to configure a mailbox to forward mail to a mail-enabled contact"

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Adding Features to the Cisco Unity 5.x System

Added January 16, 2009

In the "Adding Features to the Cisco Unity 5.x System" chapter, a task was omitted from both task lists in each of the following sections:

"Adding, Exchanging, or Removing Voice Cards"

"Adding Languages"

"Adding Text to Speech"

Do the following task immediately after you complete the task "Run the Cisco Unity Installation and Configuration Assistant," if applicable:

If any Cisco Unity engineering specials were installed on the system before you added the feature: Install the latest engineering special available for your version of Cisco Unity:

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 5.0.

c. Click Cisco Unity System Software.

d. Browse to the applicable engineering special, and download both the software and the accompanying readme file.

e. Follow the instructions in the readme file to install the engineering special.

When you run the Cisco Unity Installation and Configuration Assistant, it reinstalls all Cisco Unity software, overwriting any engineering specials that you had installed.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Changing the Codec Format of System Prompts

Revised April 4, 2012

In the "To Run the Cisco Unity Installation and Configuration Assistant to Change the Codec Format of System Prompts" procedure in the "Changing the Codec Format of System Prompts" section in the "Changing the Cisco Unity Codecs" chapter, a step was omitted.

Do the following step immediately after you complete Step 20, if applicable:

Step 21     If any Cisco Unity engineering specials were installed on the system before you added the feature: Install the latest engineering special available for your version of Cisco Unity:

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 5.0.

c. Click Cisco Unity System Software.

d. Browse to the applicable engineering special, and download both the software and the accompanying readme file.

e. Follow the instructions in the readme file to install the engineering special.

When you run the Cisco Unity Installation and Configuration Assistant, it reinstalls all Cisco Unity software, overwriting any engineering specials that you had installed.

Reconfiguration and Upgrade Guide for Cisco Unity (With IBM Lotus Domino): Upgrading the Domino Environment

Revised February 24, 2009

Use the task list in this section to upgrade the IBM Lotus Domino environment. The task list covers upgrading Domino, IBM Lotus Notes, and IBM Lotus Domino Unified Communications (DUC) for Cisco. If you are not upgrading a particular software application, skip the related tasks.

1. Exit the Cisco Unity software.

If Cisco Unity failover is configured, exit the software on the secondary server first, then on the primary server to prevent failover.

2. If you are upgrading Notes from a pre-8.x version to version 8.0.x or 8.5.x on the Cisco Unity server and the Cisco Unity server does not have the 5.0 Engineering Special 68 (ES 68) or later installed: Prepare the Cisco Unity server with a patch that includes Notes 8.x support, upgrade Notes, and disable the Multi-User Cleanup Service. See the "To Patch Cisco Unity for Notes 8.x Support and to Upgrade Notes on the Cisco Unity Server from a Pre-8.x Version to Version 8.0.x or 8.5.x" procedure.


Note To determine if the Cisco Unity server has an Engineering Special installed, run the Gather Cisco Unity System Information utility from Tools Depot.


If Cisco Unity failover is configured, do the procedure on both the primary and secondary servers.

3. If you are upgrading Notes to version 6.5.x or 7.0.x on the Cisco Unity server, or you are upgrading Notes to version 8.0.x or 8.5.x and the Cisco Unity server already has 5.0 ES 68 or later (or the equivalent patch that includes Notes 8.x support) installed: Run the new version of the Notes installation program on the Cisco Unity server and follow the on-screen prompts to upgrade Notes. After the installation, launch Notes to complete the setup, then close Notes.

If Cisco Unity failover is configured, upgrade Notes on both the primary and secondary servers.

4. If you are upgrading Domino or DUC for Cisco: Uninstall the existing DUC for Cisco server component—csServer—on every Domino server on which it is installed.

5. If you are upgrading DUC for Cisco: Uninstall the existing DUC for Cisco administration component—csAdmin—on the Domino server on which it is installed. (You install csAdmin only once for the domain, usually on the server you would typically use to administer the Domino Directory.)

6. If you are upgrading Domino: Upgrade the Domino server to a new version of Domino. Refer to IBM documentation for details on upgrading the software.

7. If you are upgrading Domino or DUC for Cisco: Install the applicable version of the DUC for Cisco server component (csServer) on every Domino server on which Cisco Unity subscribers have or will have mail files.

8. If you are upgrading DUC for Cisco: Install the applicable version of the DUC for Cisco administration component (csAdmin).

9. If you are upgrading Domino or DUC for Cisco: Update the mail file design for each user.

10. If you are upgrading Domino to version 8.5.x: If the Domino server on which the Cisco Unity Domino Person mail file resides does not contain a template file called mail8.ntf, or if you do not know whether the Domino server contains the mail8.ntf template file, add the MailFileTmplt registry key on the Cisco Unity server. See the "To Add the Domino 8.5.x MailFileTmplt Registry Key on the Cisco Unity Server" procedure.

11. Restart the Cisco Unity software.

If Cisco Unity failover is configured, restart the software on the primary server first, then on the secondary server so that the primary server is active on startup.

12. If you upgraded DUC for Cisco on the Domino server: Update clients:

a. Uninstall the existing DUC for Cisco client component on every client computer.

b. Install the new DUC for Cisco client component on every client computer.

c. Uninstall DUC for Cisco from Domino Web Access clients. The DUC for Cisco components for Domino Web Access are pushed out to a client computer the first time the user launches Domino Web Access to listen to a voice message.

13. If you updated clients to DUC for Cisco version 1.2.4 or 1.2.5 from version 1.2.3 or earlier: In order for phone record and playback to work properly in the Lotus Notes or iNotes/Domino Web Access client, confirm that Cisco Unity Engineering Special 48 or later is installed on the Cisco Unity server and add the ProxyTrapIStream registry key. See the "Cisco Unity with Domino: Phone Recording and Playback Does Not Work in IBM Lotus Notes with DUC for Cisco 1.2.4 or 1.2.5" section.

For procedures and information on installing and uninstalling the DUC for Cisco components, and for information on updating the mail file design, refer to the applicable version of the IBM Lotus Domino DUC for Cisco Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

To Patch Cisco Unity for Notes 8.x Support and to Upgrade Notes on the Cisco Unity Server from a Pre-8.x Version to Version 8.0.x or 8.5.x


Step 1 Download the patch from Cisco.com:

a. Go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.

b. In the tree control on the Downloads page, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 5.0.

c. Click Cisco Unity System Software.

d. In the All Releases section, expand Cisco Unity v.5, and click 5.0(1).

e. In the right pane, click CiscoUnity_5.0(1)_LotusNotes8.xSupport.exe.

f. Follow the on-screen prompts to complete the download.

Step 2 Install the patch on the Cisco Unity server:

a. Copy the self-extracting executable file CiscoUnity_5.0(1)_LotusNotes8.xSupport.exe to the root of the CommServer directory on the Cisco Unity server.

b. Double-click the self-extracting executable file to extract the contents to the root of the CommServer directory. The following files will be extracted:

Setup.exe, to the Commserver\ConfigurationSetup directory

TestNotesInstall.xml, to the Commserver\Syscheck\DEU\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\ENU\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\FRA\Domino directory

TestNotesInstall.xml, to the Commserver\Syscheck\JPN\Domino directory

CiscoUnity_5.0(1)_LotusNotes8.xSupport_ReadMe.txt, to the Commserver directory

Step 3 Upgrade Notes:

a. Run the Notes 8.x setup to upgrade Notes.

b. Start the Notes 8.x client to finish the Notes upgrade.

c. Close the Notes client.

Step 4 Disable and stop the Multi-user Cleanup Service:

a. On the Windows Start menu, click Programs > Administrative Tools > Services.

b. Right-click the Multi-user Cleanup Service and click Properties.

c. On the General tab, in the Startup Type list, click Disabled.

d. Click Stop to stop the service immediately.

e. Click OK to close Properties, and close the Services MMC.

Step 5 Delete the self-extracting EXE file.

Although you may safely delete the file CiscoUnity_5.0(1)_LotusNotes8.xSupport_ReadMe.txt in the Commserver directory, you may want to leave the file there as a reminder that this patch has been installed, because information about this patch is not reported in the Gather Cisco Unity System Information utility.

Step 6 If Cisco Unity failover is configured, repeat Step 1 through Step 5 on the secondary server.


To Add the Domino 8.5.x MailFileTmplt Registry Key on the Cisco Unity Server


Step 1 On the Cisco Unity server, start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (See the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, export the registry settings to a file.

Step 3 Expand the key

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\Directory Connectors\DirSynchDomino\1.00\.

Step 4 Add a new String Value, naming it MailFileTmplt.

Step 5 Double-click the MailFileTmplt key you created in Step 4.

Step 6 In the Value Data field, enter mail85.ntf, and click OK.

Step 7 Close Regedit.


Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Server from an Exchange 2000 or 2003 Server to an Exchange 2007 Server for Cisco Unity 5.x

Added August 27, 2009

In the "Changing the Partner Exchange Server" chapter, this section was omitted.

To change the partner Exchange server from an Exchange 2000 or Exchange 2003 server to an Exchange 2007 server, see the applicable section in the "Upgrading Exchange on the Cisco Unity 5.x System" chapter:

Upgrading Exchange 2000 or 2003 to Exchange 2007 for Cisco Unity 5.x Without Failover

Upgrading Exchange 2000 or 2003 to Exchange 2007 for Cisco Unity 5.x with Failover Configured

Do all of the steps in all of the procedures except for the first step in the procedure "To Upgrade from Exchange 2000 or 2003 to Exchange 2007." This is the step in which you follow the Microsoft documentation to install an Exchange 2007 server that has the Mailbox server role.

Reconfiguration and Upgrade Guide for Cisco Unity (With Microsoft Exchange): Changing the Partner Exchange Server from an Exchange 2000 Server to an Exchange 2003 Server for Cisco Unity 5.x

Added August 27, 2009

In the "Changing the Partner Exchange Server" chapter, this section was omitted.

To change the partner Exchange server from an Exchange 2000 server to an Exchange 2003 server, see the applicable section in the "Upgrading Exchange on the Cisco Unity 5.x System" chapter:

Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 5.x Without Failover

Upgrading Exchange 2000 to Exchange 2003 for Cisco Unity 5.x with Failover Configured

Do all of the steps in all of the procedures except for the first step in the procedure "To Upgrade from Exchange 2000 to Exchange 2003." This is the step in which you follow the Microsoft documentation either to install Exchange 2003 on at least one server or to upgrade an existing server to Exchange 2003.

SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express

Added April 29, 2011

In the SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express Guide, in the "Supported Version Combinations for Cisco Unity and Cisco Unified Communications Manager" section, the following note has been added:

The Live Record feature is not supported with Cisco Unity when integrated with Cisco Unified Communications Manager through a SIP trunk integration.

System Administration Guide for Cisco Unity: Phone View Features

Added February 24, 2009

In the "Phone View Features" section in the "Managing Phone View Features and Remote Message Monitor" chapter of the System Administration Guide for Cisco Unity, the following information was omitted:

Note that Phone View features are not supported on Cisco IP phones that have shared lines (multiple Cisco IP phones that share one extension).

System Administration Guide for Cisco Unity: Disabling Voice Recognition for All Subscribers

Added November 3, 2008

In the "Managing Voice-Recognition Features" chapter of the System Administration Guide for Cisco Unity, the following information for the "Disabling Voice Recognition Features" section was omitted.

If you want to disable voice recognition for all subscribers, do the following procedure.

To Disable Voice Recognition for All Subscribers


Step 1 On the Cisco Unity server, log on to Windows by using an account that is a member of the local Administrators group.

Step 2 In the Cisco Unity Administrator, go to the System > Voice Recognition > Settings page.

Step 3 On the Voice Recognition Settings page, change the value of the IP Address field to 0.0.0.0.

Step 4 Click Save.

Step 5 Close the Cisco Unity Administrator.


System Administration Guide for Cisco Unity: SMTP Message Notifications

Added July 31, 2009

In the "Setting Up Text Message Notifications" section in the "Setting Up Message Notifications" chapter of the System Administration Guide for Cisco Unity, the following information was omitted from the "SMTP Message Notifications" section.

You can install Cisco Unity in the Voice Messaging configuration with the Cisco Unity server in an SMTP domain other than the SMTP domain for email. By default, Cisco Unity email notifications are properly routed to the SMTP domain for email. Note, however, that if the corporate email server is configured to not accept emails from the SMTP domain in which the Cisco Unity server was installed, users will not receive email notifications in their email inbox. Do the following procedure to allow email notifications from Cisco Unity 5.x and later to be properly routed to inboxes in the SMTP domain for email.


Note This procedure is not supported when you are using AMIS, Bridge, or VPIM networking.


To Configure Active Directory to Allow Cisco Unity 5.x and Later to Send E-mail Notifications to a Different SMTP Domain (Exchange 2003 and Exchange 2000 Only)


Step 1 In Active Directory Users and Computers, display the Properties dialog box for the Unity_<servername> account.

Step 2 On the E-mail Addresses tab, add an SMTP address in the same SMTP domain as the corporate email, for example, Unity_<servername>@<company_name>.com.

Step 3 Set the new SMTP address as the primary email address for this account.

Step 4 Uncheck the Automatically Update E-mail Addresses Based on Recipient Policy check box.

Step 5 Close the Properties dialog box.


Troubleshooting Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Subscriber and Administrator Access

Added June 9, 2010

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 5.0 server is accessing an Active Directory 2008 global catalog server (GC), subscribers using the phone interface to access voice messages may hear the message "Your messages are not available now." (Subscribers may also hear this message for other reasons, including permissions problems for the message store services account.)

In addition, the following errors may be logged in the Windows application event log on the Cisco Unity server each time a subscriber tries to log on to Cisco Unity by phone:

Event Type: Error
Event Source: CiscoUnity_MALEx
Event Category: Error 
Event ID: 30003
Description: An attempt to access the Primary Exchange Mailbox Store by AvCsMgr via MAPI 
has failed.  The MAPI subsystem return the following error: The information store could 
not be opened.. 
 
   
Event Type: Error
Event Source: CiscoUnity_MALEx
Event Category: Error 
Event ID: 30012
Description: An occurred which prevents successful Exchange access by AvCsMgr via MAPI. 
This is typically an indication of configuration issues with Unity, Exchange, or the MAPI 
subsystem. Verify that the Unity services accounts are granted the correct permissions and 
that there are no issues with installation.  The SysCheck utility may assist in diagnosing 
the problem. 
 
   
Event Type: Error
Event Source: CiscoUnity_ConvSub
Event Category: Network 
Event ID: 1000
Description: An unexpected error has occured while a subscriber is on the phone with 
Unity. This can potentially result in the subscriber hearing the failsafe conversation. 
Technical details are - IAvDohMailUser::get_Inbox returned [0x8004052e] on line 1312 of 
file <path>\un_Conv1\Scripted\ConvSub\MsgCount.cpp. 
 
   
Event Type: Error
Event Source: CiscoUnity_ConvSub
Event Category: Network 
Event ID: 1394
Description: The description for Event ID ( 1394 ) in Source ( CiscoUnity_ConvSub ) cannot 
be found. The local computer may not have the necessary registry information or message 
DLL files to display messages from a remote computer. You may be able to use the 
/AUXSOURCE= flag to retrieve this description; see Help and Support for details. The 
following information is part of the event: msg.GetMessageCount(spMailUser.get(), spNP, 
pSM) returned: 0x8004052E, 534, <path>\un_Conv1\Scripted\ConvSub\MsgCount.cpp, .

Do the following procedure to determine whether MAPI is using an Active Directory 2008 GC, to determine whether the GC is having the NSPI problem, and, if so, to change a registry setting on all Active Directory 2008 GCs to resolve the problem.


Note During the procedure, you will need to refer to Microsoft Knowledge Base article 949469, "NSPI connections from Microsoft Outlook to a Windows Server 2008-based domain controller may fail with an error code: `MAPI_E_LOGON_FAILED.'"


To Determine Whether Cisco Unity Is Affected by the NSPI Problem and to Change a Registry Setting on the GC


Step 1 Determine whether MAPI on the Cisco Unity server is accessing an Active Directory 2008 GC:

a. Log onto the Cisco Unity server by using the Active Directory account that Cisco Unity message store services log on as.

b. Start RegEdit.

c. Expand the following key:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Unity System Profile

d. Click the key that begins with dca.

e. In the right pane, if the value is the name of a Active Directory 2008 GC, continue with Step 2.

If the value is not the name of a Active Directory 2008 GC, your symptoms have another cause.

Step 2 Determine whether the Active Directory 2008 GC is having the NSPI problem and, if so, to fix it:

a. Log onto the GC that you identified in Step 1.

b. Enable event logging as described in the "More Information" section of Microsoft Knowledge Base article 949469.

c. If the event log confirms that you are encountering the problem documented in Microsoft KB article 949469, do the procedure "How to modify the registry to allow for additional NSPI connections," which causes the GC to function similarly to an Active Directory 2003 GC. Set the value to 0x00002710.

d. Restart the Cisco Unity server.

e. Repeat Step b. and Step c. on every Active Directory 2008 GC that MAPI on the Cisco Unity server may use. This will ensure that if the GC that MAPI is currently using fails, the next GC that MAPI uses will already be configured to allow Cisco Unity to function properly.

Cisco Unity is not currently communicating with the other GCs, so restarting the Cisco Unity server after you do this step is not necessary.


Note If the registry key does not list a Active Directory 2008 GC but you have Active Directory 2008 GCs in the forest, you may still want to do Step 2c. on every Active Directory 2008 GC that MAPI on the Cisco Unity server may use.



Troubleshooting Information

Cisco Unity troubleshooting information can be found in the Troubleshooting Guide for Cisco Unity, Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.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 Installation Guide for Cisco Unity and in the integration guide for your phone system. Cisco TAC does not provide support for Cisco Unity demonstration systems. The Installation Guide for Cisco Unity is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


The software for a demonstration system can be ordered on line. 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 https://tools.cisco.com/qtc/config/jsp/configureHome.jsp. The part number is UNITY4-DEMO-10USR.


Note You must be a registered user to access this web page. If you are not a registered user, go to http://tools.cisco.com/RPF/register/register.do to register and obtain a Cisco.com user ID.


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

"Upgrading a Cisco Unity 4.x Demonstration System to a Cisco Unity 5.0(1) Demonstration System" 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

10 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

2 voice-recognition sessions

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

16 voice ports

2 voice-recognition sessions

VM feature package

50 VM subscribers with 16 sessions

2 RealSpeak text-to-speech (TTS) sessions

2 languages

25 Cisco Unity Inbox users

16 voice ports

2 voice-recognition sessions

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 (CiscoUnity50.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 Installation Guide for Cisco Unity—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 CiscoUnity50.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 Installation Guide for Cisco Unity 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 http://www.cisco.com/go/license (the URL is case sensitive).


Note You must be a registered user to access this web page. If you are not a registered user, go to http://tools.cisco.com/RPF/register/register.do to register and obtain a Cisco.com user ID.


Step 2 In the Voice Products section, under Cisco Unity Software, click 5.0 Demo License. (You can use the license on all Cisco Unity 5.x versions.)

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 Installation Guide for Cisco Unity—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 Installation Guide for Cisco Unity to complete the installation.


Upgrading a Cisco Unity 4.x Demonstration System to a Cisco Unity 5.0(1) Demonstration System

To Upgrade a Cisco Unity 4.x Demonstration System to a Cisco Unity 5.0(1) Demonstration System


Step 1 Follow the documented process for upgrading a Cisco Unity 4.x system to a Cisco Unity 5.x system until you reach the Cisco Unity Installation and Configuration Assistant.

For more information, see the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Step 2 During the License File wizard, remove the Cisco Unity 4.x default license file or time-limited license file.

Step 3 Install the Cisco Unity 5.x default license file or time-limited license file.

Step 4 Continue with the documented process for upgrading to Cisco Unity 5.x.


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.


Note To add failover to the system after you have converted the demonstration system to a standard system, refer to the section on adding failover in the "Adding Features to the Cisco Unity 5.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity.


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 (CiscoUnity50.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 Unified CM
integration through SCCP

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

If Cisco Unity is configured for failover, add the ports to the voice mail server that the primary Cisco Unity server uses, then add the same number of ports to the voice mail server that the secondary Cisco Unity server uses.

b. For the new ports, set the line groups and hunt groups for the ports. Refer to the applicable Cisco Unified CM 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 Unified CM integration guide.

Cisco Unified CM Express integration through SCCP

a. On the Cisco Unified CM Express router, configure the additional ports. Refer to the applicable Cisco Unified CM Express documentation.

SIP integration (Cisco Unified CM, Cisco Unified CM Express, or Cisco SIP Proxy Server)

No steps are necessary to provide additional ports on the phone system.

PIMG integration

a. On the phone system, configure the additional ports. Refer to the phone system documentation.

a. Set up the additional PIMG units. Refer to the "Setting Up the PIMG Units" section of the applicable Cisco Unity integration guide.

Voice Card 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. Refer to the "Adding, Exchanging, or Removing Voice Cards" section in the "Adding Features to the Cisco Unity 5.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity.


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. Refer to 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 antivirus software or the Cisco Security Agent for Cisco Unity is installed on the Cisco Unity server, disable antivirus services and the Cisco Security Agent service. Refer to the "Disabling Antivirus and Cisco Security Agent Services" section in the "Customizing the Cisco Unity Platform" chapter of the Installation Guide for Cisco Unity.

b. On Cisco Unity DVD 1, or from the location to which you saved the downloaded Cisco Unity DVD 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 antivirus software or Cisco Security Agent for Cisco Unity is installed on the Cisco Unity server, re-enable antivirus services and the Cisco Security Agent service. Refer to the "Re-enabling Virus-Scanning and Cisco Security Agent Services" section of the "Installing and Configuring Cisco Unity Software" chapter of the Installation Guide for Cisco Unity.

z. Make the feature available for use:

Languages

Refer to the "Managing Languages" chapter of the System Administration Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

TTS

Put subscribers in a class of service (COS) that includes TTS. Refer to the "Managing Classes of Service" chapter of the System Administration Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.



Installing and Configuring Voice-Recognition Software on a Cisco Unity Server for Demonstration Purposes Only

Added December 13, 2007

This section assumes that the Cisco Unity license includes voice-recognition sessions and that you are installing and configuring voice-recognition software on the Cisco Unity server for demonstration purposes only. When the voice-recognition demonstration is no longer necessary, you must remove the voice-recognition software from the Cisco Unity server.


Caution You cannot upgrade Cisco Unity software while voice-recognition software is installed on the Cisco Unity server for demonstration purposes. To add new features that require running Cisco Unity Setup or to upgrade Cisco Unity software to a later version, you must first remove the voice-recognition software. See the "Removing Voice-Recognition Software from the Cisco Unity Server" section.


Caution Do not install Cisco Unity voice-recognition software on a Cisco Unity server running Windows 2000 Server. Windows Server 2003 is required.

To Install and Configure Voice-Recognition Software on a Cisco Unity Server for Demonstration Purposes Only


Step 1 If antivirus software or Cisco Security Agent for Cisco Unity is installed on the server, disable antivirus and Cisco Security Agent for Cisco Unity services.

Step 2 Install the voice-recognition software on the Cisco Unity server:

a. Log on to the Cisco Unity server by using an account that is a member of the local administrators group.

b. Insert Cisco Unity DVD 1 in the DVD drive.

c. From a command prompt, switch to the UnityVoiceRecognitionSetup directory on the DVD, then enter setup.exe /force.


Note During Setup, the installation wizard detects whether Cisco Unity is installed on the server. If it is, the wizard installs only the CuVrt service, which allows Cisco Unity to communicate with a separate voice-recognition server. By using the /force command line argument, this check is skipped and the voice-recognition software is installed on the Cisco Unity server in addition to the CuVrt service.


d. Click Yes at the warning.

e. Follow the on-screen prompts until you are prompted to choose the location for voice-recognition files.

f. Choose a location other than the system drive (C drive) to install the voice-recognition software.


Note The voice-recognition software takes up about 500 MB of hard disk space. On MCS-7825 and MCS-7835 servers, we recommend that you install on the D drive, as the C drive typically has a limited amount of space available. Note also that when Microsoft Exchange is the message store, the message database is on the D drive, and the voice-recognition software takes away voice message storage space (about 1,000 minutes for messages stored in G.711 format).


g. Click Next.

h. Accept the default location for the Cisco Unity voice-recognition service.

i. Follow the on-screen prompts to complete the installation.

Step 3 If antivirus software is installed on the server, exclude selected directories from virus scanning:

a. On the Cisco Unity server, log on to Windows by using an account that is a member of the local Administrators group.

b. Start the administration interface for the antivirus software. Refer to the antivirus software Help for instructions on excluding directories from scanning.

c. Exclude the following two directories from virus scanning:

Nuance

NuanceLogs


Caution Do not configure antivirus software to block WAV attachments, or voice messages will be stripped of their recordings. In addition, do not configure antivirus software to scan WAV files, .log files, or .tmp files. Finally, do not configure antivirus software to block TCP or UDP port traffic, or voice-recognition software may not function properly.

Step 4 If antivirus software or Cisco Security Agent for Cisco Unity is installed on the server, re-enable antivirus and Cisco Security Agent for Cisco Unity services.

Step 5 Configure the voice-recognition software:

a. On the Cisco Unity server, log on to Windows by using an account that is a member of the local Administrators group.


Caution We recommend that you do this procedure after hours. The manual update in Step g is a processor- and memory-intensive process that will affect Cisco Unity performance.

b. In the Cisco Unity Administrator, go to the Configuration > Voice Recognition > Settings page.

c. On the Voice Recognition Settings page, in the IP Address field, enter the IP address of the Cisco Unity server.

d. Do not change the value of the Socket Port field.

e. Change the value of Limit Searches to The, as appropriate. For a detailed explanation of the available options, see Cisco Unity Administrator Help.

f. Click Save.

g. Click Start Manual Update.

Cisco Unity will take up to 15 minutes to transfer licensing information and other data. Until this process is complete, voice recognition will not function.

h. Close the Cisco Unity Administrator.

Step 6 Configure Cisco Unity templates and subscriber accounts for voice recognition:

Refer to the "Managing Voice-Recognition Features" chapter of the System Administration Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.


Note Changes to settings in a template do not affect existing subscriber accounts that were based on that template. Refer to the "Modifying Subscriber Accounts" section in the "Managing Subscriber Accounts" chapter of the System Administration Guide for Cisco Unity for information on modifying subscriber accounts after they have been created.



Removing Voice-Recognition Software from the Cisco Unity Server

When the voice-recognition demonstration is no longer necessary, you must remove the voice-recognition software from the Cisco Unity server.

To Remove Voice-Recognition Software from the Cisco Unity Server


Step 1 Log on to the Cisco Unity server by using an account that is a member of the local administrators group.

Step 2 From the Windows Start menu, click Control Panel > Add or Remove Programs and remove Cisco Unity Voice-Recognition Software.

Step 3 Click Yes when prompted to completely remove the selected application and all of its features.

Step 4 Follow the on-screen prompts to complete the removal of the voice-recognition software.

Step 5 If you are permanently removing voice recognition from the environment, use the Cisco Unity Bulk Edit Utility to disable the following two settings for all subscribers under Conversation > Options:

Use Voice for Navigating the Subscriber Conversation

Allow Access to Voice-Recognition Feature

Step 6 If you are adding a separate voice-recognition server—the supported configuration—to your existing Cisco Unity system, refer to the "Adding Voice Recognition" section in the "Adding Features to the Cisco Unity 5.x System" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.


Note Changes to settings in a template do not affect existing subscriber accounts that were based on that template. Refer to the "Modifying Subscriber Accounts" section in the "Managing Subscriber Accounts" chapter of the System Administration Guide for Cisco Unity for information on modifying subscriber accounts after they have been created.



Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.