Guest

Cisco Unity

Release Notes for Cisco Unity Release 7.0(2)

  • Viewing Options

  • PDF (1.0 MB)
  • Feedback
Release Notes for Cisco Unity Release 7.0(2)

Table Of Contents

Release Notes for Cisco Unity Release 7.0(2)

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

Cisco Personal Communications Assistant

Cisco Unity ViewMail for Microsoft Outlook

Related Documentation

New and Changed Requirements and Support—Release 7.0(2)

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

Antivirus Software Qualified for Use with Cisco Unity

Cisco Security Agent for Cisco Unity Version 3.1(4)

Cisco Unity-CM TSP Version 8.3(1)

Cisco Unity Documentation

Cisco Unity 7.x Documentation Set

Cisco Unity 7.0(2) Versioning Explained

Cisco Unity Voice Connector for Microsoft Exchange Version 14.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 Unity Connection Networking Is Now Supported

Cisco Unity with Exchange: Exchange 2010 Is Now Supported

Increased Limits for Subscribers and Ports for Selected Servers

Languages for Cisco Unity Components

Netscape Web Browser No Longer Supported

Phone System Integrations Qualified for Use with Cisco Unity

Software Qualified for Use on Cisco Unity Subscriber Workstations

Utility Updates in the Cisco Unity Tools Depot

New Functionality—Release 7.0(2)

Alternate Extension "Learning"

Cisco Unity Bulk Import Wizard and Bulk Edit Utility Enhancements

Cisco Unity Conversation Enhancements

Cisco Unity with Domino: Exclude Reply History and Attachments from TUI Replies

Cisco Unity with Exchange: Subscribers Can Delete Introductions on Forwarded Messages

Enhanced Telephone User Interface Addressing by Using Recipient History

Follow-Me Transfer Rules

Live Reply Enhancements

Outside Callers Can Mark Messages Private

Playback Speed Adjustments Are Saved Across Sessions

Setup Options Added

Subscribers Can Configure SMS Notification Devices by Phone

Subscribers Can Hear Message Duration Before Playback

Cisco Unity Failover Enhancements

Cisco Unity with Exchange: VPIM Delivery Location Configuration Options

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

Media Master Can Be Disabled in the Cisco Unity Assistant Web Tool

MWI Constant Message Count

New Port Status Monitor

Subject Lines of Voice Messages Can Be Configured

UTIM

Changed Functionality—Release 7.0(2)

Alternate Device Number Field Validates Against Alt Ext Restriction Table

Apache Tomcat Sample Applications Contain Security Vulnerabilities

Automated Attendant Search Scope Setting Moved to the Cisco Unity Administrator

Cisco Unity Conversation Changes

Conversation Settings Changed or Removed from the Advanced Settings Tool

Defaults for Outside Caller and Identified Subscriber Messaging Conversation Settings

Defaults for Subscriber Conversation Settings

Cisco Unity Server Licensing

Cisco Unity with Domino: Anonymous Logon No Longer Required for TRaP

Cisco Unity with Domino: Interop Gateway Service

Cisco Unity with Domino: Serviceability Improvements

Cisco Unity with Domino: Storage of Notes Password on the Cisco Unity Server

Cisco Unity with Exchange: Resynchronizing Message Counts with Exchange Is Faster

Defaults for Addressing Search Scopes

Default for Allowing Subscribers to Create Alternate Extensions

Encryption Algorithm for Phone Password

Java SDK Upgraded

Remote Serviceability Kit Updates

Support for Up to 200 Voice Messaging Ports

Installation and Upgrade Information

Downloading Software for Cisco Unity 7.0(2)

Upgrading to Cisco Unity 7.0(2)

Installing Cisco Unity 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

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 5.0 Does Not Require Extending Active Directory Schema, But Upgrade from 4.x Does

Upgrade Always Requires Upgrade Purchase, Sometimes Requires Upgrade License

Upgrade from Cisco Unity 4.0(2) or 4.0(1) 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 Exchange: Alternate Extensions Page Generates a DCOM Error After the Password Is Changed on the UnityMsgStoreSvc Account

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

First Subscriber to Call Cisco Unity After Restart Hears Delay Before First Prompt

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

Message Monitor Delay Before Playing Subscriber Greeting Is Reduced

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—Release 7.0(2)

Resolved Caveats—Release 7.0(2)

Documentation Updates

New and Changed Content

New Functionality Items

Changed Functionality Items

Errors

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

Cisco Unity Integration Guides for Cisco Unity 5.x: Creating a New Integration

Failover Configuration and Administration Guide for Cisco Unity Release 5.x: Intervals for Failover and Failback

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

Maintenance Guide for Cisco Unity Release 5.x: Excluding Cisco Unity Directories from Scanning

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with IBM Lotus Domino): Configuring the Interop Gateway

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with Microsoft Exchange): Determining the Domain Name

Networking Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Configuring the Interop Gateway

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Domain Name Requirements

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Obtaining and Installing Cisco Unity License Files

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Extending the Active Directory Schema for Cisco Unity

System Administration Guide for Cisco Unity Release 5.x and Interface Reference Guide for the Cisco Unity Administrator: Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password

System Administration Guide for Cisco Unity Release 5.x: Phone View Features

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Enabling Alternate Greeting Notices

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Specifying How Cisco Unity Behaves When Subscribers Have Their Alternate Greeting Enabled

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange) and Integrated Mailbox Configuration Online Help: Using Integrated Mailbox Configuration to Create Individual Subscriber Accounts

Troubleshooting Guide for Cisco Unity Release 5.x: Cisco Unity Services and Their Functions

Omissions

Multiple Guides: SIP Integrations May Not Add a Pause for a Comma in a Dialstring

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

Networking Guide for Cisco Unity: Cross-Server Logon, Transfers, and Live Reply

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

Security Guide for Cisco Unity: Limitations of Secure Messaging

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

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

System Administration Guide for Cisco Unity: Phone View Features

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 5.x Demonstration System to a Cisco Unity 7.0(2) 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 Release 7.0(2)


Revised April 4, 2012 (Originally published May 23, 2008)

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

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

For this release, only a portion of the Cisco Unity documentation set was updated. Information on new and changed features in 7.x—including any required procedures—can be found in these release notes. See the "Cisco Unity 7.x Documentation Set" section for complete details on documentation for Release 7.x.

Cisco Unity 7.0(2) is orderable June 30. The U.S. English (ENU) version is available for download, but can be used only for demonstration systems until June 30. The multilingual version is available for download beginning June 27 and available for shipping the week of July 7. For download instructions, see the "Downloading Software for Cisco Unity 7.0(2)" section.

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


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

System Requirements

Related Documentation

New and Changed Requirements and Support—Release 7.0(2)

New Functionality—Release 7.0(2)

Changed Functionality—Release 7.0(2)

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

System Requirements

The following documents list the most current Cisco Unity requirements:

System Requirements for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html.

Cisco Unity Bridge 3.1 System Requirements, and Supported Hardware and Software at http://www.cisco.com/en/US/docs/voice_ip_comm/bridge/31/requirements/31cubsysreq.html.

Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

Compatibility Information

The following documents list the most current version combinations qualified for use with Cisco Unity:

Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.html.

SCCP Compatibility Matrix: Cisco Unity, the Cisco Unity-CM TSP, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cutspmtx.html.

SIP Trunk Compatibility Matrix: Cisco Unity, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cusiptrunkmtx.html.

Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/support/7xcusupp.html.

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

Cisco Personal Communications Assistant

Cisco Unity ViewMail for Microsoft Outlook

Cisco Unity

To Determine the Cisco Unity Version in Use by Using the Cisco Unity Administrator


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


To Determine the Cisco Unity Version in Use by Using the AvCsMgr.exe File


Step 1 Browse to the CommServer directory.

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

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

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


Cisco Unity-CM TSP

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


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

Step 2 In the UTIM window, in the left pane, click the Cisco Unified Communications Manager 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

Windows 2000

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

To Determine the Voice Connector Version in Use


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

Step 2 In Windows Explorer or My Computer, browse to <ExchangeServerPath>\VoiceGateway\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.


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

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 Cisco Unity Inbox web tool, 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. Do either procedure on the subscriber workstation.

To Determine the ViewMail Version in Use from Outlook


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


To Determine the ViewMail Version in Use from Add/Remove Programs


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.


Related Documentation

For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to the Documentation Guide for Cisco Unity Release 7.x. The guide is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/roadmap/7xcudg.html.

New and Changed Requirements and Support—Release 7.0(2)

This section contains information about new and changed requirements and support in the Cisco Unity Release 7.0(2) 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 2, 2009

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 7.0(2) server is accessing a Windows Server 2008 global catalog server (GC), each time a subscriber tries to log on to Cisco Unity by using the phone interface to access voice messages, the subscriber may hear the message "Your messages are not available now," and errors may be logged in the Windows application event log on the Cisco Unity server.

For information on determining whether a change to the registry on the Active Directory 2008 GC 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 June 10, 2010

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 7.0 Engineering Special 7 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, expand Products > Voice and Unified Communications > Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity , and click Cisco Unity Version 7.0 > Unity System Software.)

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 7.0(2) 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 a change to the registry on the Active Directory 2008 GC 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."

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

Active Directory schema extensions for Cisco Unity were not changed for Cisco Unity 7.0(2). If you are upgrading from Cisco Unity 5.0 to version 7.0(2), you do not need to extend the Active Directory schema.

However, if you are upgrading from Cisco Unity 4.x to version 7.0, you must extend the schema with Cisco Unity 7.0 schema extensions. For more information, refer to the following documentation:

The section "Active Directory Schema Extensions Required for Cisco Unity with Exchange" in Release Notes for Cisco Unity 5.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/release/notes/501curelnotes.html.

The white paper Cisco Unity Data and Active Directory (Cisco Unity 5.x and Later with Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/white/paper/5xcudatadirectory.html.

Note that schema 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 4.x Cisco Unity server to 7.0(2) 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 7.0(2). 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/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

Antivirus Software Qualified for Use with Cisco Unity

The following antivirus software has been qualified for optional use with Cisco Unity 7.0(2):

CA Anti-Virus for the Enterprise version 8.0 and later (formerly called eTrust Antivirus)

For the most current list of all supported antivirus software, refer to the "Supported Antivirus Software" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/support/7xcusupp.html.

Cisco Security Agent for Cisco Unity Version 3.1(4)

Cisco Security Agent for Cisco Unity 3.1(4) is qualified for use with Cisco Unity 7.0(2), Cisco Unity 7.0(2) voice recognition, and Cisco Unity Bridge. For information on the security agent, refer to Release Notes for Cisco Security Agent for Cisco Unity Release 3.1(4) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/security_agent/release/notes/314cusecagtrelnotes.html.

Cisco Unity-CM TSP Version 8.3(1)

Cisco Unity-CM TSP 8.3(1) is qualified for use with Cisco Unity version 7.0(2). For information on the Cisco Unity-CM TSP, refer to Release Notes for Cisco Unity-CM TSP Release 8.3(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/tsp/release/notes/831tsprelnotes.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 7.x Documentation Set

For this release, only a portion of the Cisco Unity documentation set was updated. Information on new and changed features in 7.x—including any required procedures—can be found in these release notes. For guides that were not updated, use the Release 5.x versions; all 5.x content applies to Release 7.x.

Table 1 below lists documentation that was and was not updated. Refer to the Documentation Guide for Cisco Unity Release 7.x for documentation URLs. A printed version of the guide is shipped with Cisco Unity, and it is also available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/roadmap/7xcudg.html.

Table 1 Documentation for Cisco Unity Release 7.x 

Updated or New for Release 7.x
Not Updated for 7.x—Use Release 5.x Versions

Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations

Components and Software Installed by the Cisco Unity Platform Configuration Discs and the Cisco Unity System Preparation Assistant

Documentation Guide for Cisco Unity Release 7.x (new)

Networking Options Requirements for Cisco Unity

Open-Source Software Included in Cisco Unity Release 7.x (new)

Release Notes for Cisco Security Agent for Cisco Unity Release 3.1(4) (new)

Release Notes for Cisco Unity-CM TSP Release 8.3(1) (new)

Release Notes for Cisco Unity Release 7.0(2) (new)

Release Notes for Cisco Unity ViewMail for Microsoft Outlook Release 7.0(2) (new)

Release Notes for Cisco Unity Voice Connector for Microsoft Exchange Release 14.0(1) (new)

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

Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x (new)

System Requirements for Cisco Unity Release 7.x (new)

Use the Installation Guide That Matches the Cisco Unity 7.x Configuration (new)

Cisco Unity integration guides

Design Guide for Cisco Unity

Failover Configuration and Administration Guide for Cisco Unity

Installation Guide for Cisco Unity

Interface Reference Guide for the Cisco Unity Administrator

Maintenance Guide for Cisco Unity

Networking Guide for Cisco Unity

Reconfiguration and Upgrade Guide for Cisco Unity

Release Notes for Spoken Commands in Cisco Unity

Security Guide for Cisco Unity

System Administration Guide for Cisco Unity

Troubleshooting Guide for Cisco Unity

User Guide for Accessing Cisco Unity Voice Messages in an E-Mail Client

User Guide for the Cisco Unity Assistant Web Tool

User Guide for the Cisco Unity Inbox Web Tool

User Guide for the Cisco Unity Phone Interface

User Guide for Mobile Message Access for BlackBerry

User Guide for the Cisco Unity Plug-in for Sametime Connect


Cisco Unity 7.0(2) Versioning Explained

The field-test version of Cisco Unity version 7.0 was versioned "7.0(1)" to improve source control. To ensure that field-test sites do not have problems upgrading to the release version, the release version has been numbered "7.0(2)."

Cisco Unity Voice Connector for Microsoft Exchange Version 14.0(1)

Voice Connector 14.0(1) is qualified for use with Cisco Unity version 7.x. For information on the Voice Connector, refer to Release Notes for Cisco Unity Voice Connector for Microsoft Exchange Release 14.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/voice_connector/release/notes/vc1401relnote.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/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

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 (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.

Cisco Unity with Exchange: Cisco Unity Connection Networking Is Now Supported

Revised April 4, 2012

You can now use Cisco Unity 7.0(2) in a Digital Network with a Cisco Unity site gateway running Cisco Unity 8.0(3) to link to a Cisco Unity Connection site. Cisco Unity Connection Networking provides directory synchronization, message exchange, and call transfers between servers in both sites. To use Cisco Unity Connection Networking, you must install Cisco Unity Engineering Special (ES) 36 or later on each Cisco Unity 7.0(2) server in the Digital Network. Cisco Unity 7.0(2) is not supported on the site gateway.

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

For additional requirements for Cisco Unity Connection Networking, see the "Cisco Unity Networking Requirements" section of Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

For information and instructions on setting up Cisco Unity Connection Networking, see the Networking Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

Cisco Unity with Exchange: Exchange 2010 Is Now Supported

Added April 15, 2010

You can now use 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 Engineering Special (ES) 35 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 7.0 at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html.

Increased Limits for Subscribers and Ports for Selected Servers

The maximum number of Cisco Unity subscribers has been increased to 15,000 subscribers for selected servers. When the Cisco Unity server has more than 7,500 subscribers, Exchange must be the message store.

The maximum number of ports has been increased to 200. (See also the "Support for Up to 200 Voice Messaging Ports" section.)

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

Languages for Cisco Unity Components

This section lists new languages in which Cisco Unity components are available. For a complete list of languages, refer to the "Available Languages for Cisco Unity Components" section of System Requirements for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html.

System prompts

Catalan-Spain, Welsh-Wales

Netscape Web Browser No Longer Supported

The Netscape Navigator web browser is no longer supported for use with the Cisco Unity Administrator or Cisco Personal Communications Assistant.

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:

Avaya Definity G3 (In-Band integration through TIMG units)

Avaya S8500/S8700 (In-Band integration through TIMG units)

Cisco Unified Communications Manager 3.3 (SCCP integration)

Cisco Unified Communications Manager 7.0 (SCCP and SIP integrations)

Cisco Unified Communications Manager Express 4.2 (SCCP and SIP integrations)

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

QSIG-Enabled Phone System (QSIG/SIP integration through a a Cisco ISR voice gateway)

For the most current list of all supported phone system integrations, refer to the "Supported Phone System Integrations" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/support/7xcusupp.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

Apple Safari version 3.1 and later on Windows Vista, Windows XP, Mac OS X 10.5, and Mac OS X 10.4


Note When subscribers use this browser, the Media Master control bar does not appear in the Cisco Unity Assistant web tool.


Cisco Unity with Exchange

Cisco Unity ViewMail for Microsoft Outlook version 7.0(2)


Note ViewMail 7.0(2) is not supported with Outlook 2000. Subscribers who use Outlook 2000 should continue to use earlier versions of ViewMail.


Apple Safari version 3.1 and later on Windows Vista, Windows XP, Mac OS X 10.5, and Mac OS X 10.4


Note When subscribers use this browser, the Media Master control bar does not appear in the Cisco Unity Assistant web tool, and the Cisco Unity Inbox web tool is not available.


For the most current version combinations of software qualified for use on subscriber workstations, refer to Compatibility Matrix: Cisco Unity and the Software on Subscriber Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cuclientmtx.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.

Information on the following new tools is available in these release notes:

New Port Status Monitor

New Functionality—Release 7.0(2)

This section contains information about new functionality for Cisco Unity Release 7.0(2) 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 7.0(2). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.

Alternate Extension "Learning"

Revised June 26, 2008

When a subscriber calls and logs on to Cisco Unity from a phone number that is not configured as a primary or alternate extension for any subscriber, Cisco Unity can add the number to the subscriber's calling party ID (CPID) history. If the subscriber calls and logs on from the phone a sufficient number of times within a given time frame, on a subsequent logon from the same number the system asks the subscriber if he or she wants to be recognized when calling from the number in the future. If the subscriber chooses to have the number recognized, the number is added as an alternate extension for the subscriber. If the subscriber chooses not to have the number recognized, Cisco Unity will no longer keep a history of calls from that number, and will not ask the subscriber about the number again in the future.

This feature is controlled by class of service and is enabled by default. To enable or disable the feature for a particular class of service, in the Cisco Unity Administrator, go to the applicable Subscribers > Class of Service > Profile page, and check or uncheck the Subscribers Can Add, Modify and Delete Their Own Alternate Extensions check box. (When checked, the feature is enabled.)

Once a subscriber has added an alternate extension either by phone or by using the Cisco Unity Assistant web tool, the subscriber can remove the alternate extension by phone by accessing the Setup Options menu and choosing Personal Settings. The subscriber must be calling from the alternate extension, or the option to remove the number will not be offered. Subscribers can remove only those numbers they have added by phone or by using Cisco Unity Assistant. A subscriber will not be offered the option of removing an alternate extension that was assigned by using the Cisco Unity Administrator or the Bulk Edit utility.

Administrators can configure how many times a subscriber must call and log on from a number and the time frame in which they must do so before the system prompts the subscriber with the option to add the number as an alternate extension. The default is 5 times over 30 days. To configure these values, in the Cisco Unity Administrator, go to the System > Configuration > Settings page, and configure the Alternate Extension Setup Based on CPID fields.

Note also that Cisco Unity checks the CPID against the {Default Alt Ext} restriction table. If the number is not allowed by this restriction table, Cisco Unity will not consider it for alternate extension learning. Administrators can configure this restriction table to constrain learned alternate extensions to a certain length or to restrict certain numbers or patterns, for example to prevent subscribers from being offered a conference room or lobby phone as an alternate extension. By default, this restriction table allows any number that is between 10 and 30 digits long.

This feature is enabled by default, and can cause unexpected behavior if subscribers add alternate extensions for numbers that are used by the system or by multiple subscribers, or in situations where one extension frequently transfers subscribers to Cisco Unity. We strongly recommend that you configure the {Default Alt Ext} table to disallow the extensions of frequently used phones that you do not want inadvertently added as subscriber alternate extensions (for example, receptionist, lobby, or conference room phones).


Caution In the default configuration, this feature conflicts with the cross-server login feature; the first subscriber to perform cross-server logins a sufficient number of times will be prompted to add the caller ID (in this case, the extension of the calling Cisco Unity server) as an alternate extension. If the subscriber does so, all future cross-server login attempts from the calling server will fail because the Cisco Unity server receiving the call processes it as a login attempt from the subscriber alternate extension rather than as a cross-server login. To avoid this issue, on each server that will accept cross-server login attempts, add the extensions that other Cisco Unity servers use to dial out for cross-server login to the {Default Alt Ext} table as call patterns that are not allowed. For information on correcting this issue if you have encountered it, refer to caveat CSCsq81915. (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/go/bugs.)

Cisco Unity Bulk Import Wizard and Bulk Edit Utility Enhancements

The Cisco Unity Bulk Import wizard and Bulk Edit utility that are included with Cisco Unity 7.0(2) have the following enhancements:

Administrators can configure SMS (SMPP) message notification devices when importing new subscribers or modifying existing regular subscribers with the Cisco Unity Bulk Import wizard.

Administrators can use Bulk Edit to configure the notification schedule for all notification devices.

Administrators can use Bulk Edit to configure whether to include voice, e-mail, and fax message counts for the SMS (SMPP), Text Pager 1, Text Pager 2, and Text for Cisco Unity Inbox (referred to as VMI in Bulk Edit) notification devices.

Table 2 lists the optional column headers that can be added to a CSV file for importing or modifying subscribers with the Cisco Unity Bulk Import wizard.

Table 2 Optional CSV File Column Headers for SMS Notification in Cisco Unity Bulk Import 

Optional Column Header
Description

SMS_PHONE_NO

Enter the phone number of the SMS-compatible device. The format and the number that you enter depends on the SMPP Provider. The provider may require that you include international country codes, beginning with a plus sign (+) and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234).

This column corresponds to the To: (Phone Number) field for the SMS (SMPP) device on the on the Subscribers > Subscriber > Message Notification page in the Cisco Unity Administrator.

Enter any combination of digits from 0 through 9, and the following characters, up to a maximum of 128 characters:

+ (plus sign).

, (comma) to insert a one-second pause.

# and * to correspond to the # and * keys on the phone.

Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.

SMS_FROM_PHONE_NO

What you enter in this field depends on the SMPP provider:

If the SMPP provider requires a "source address" for the server sending the message, enter the IP address for the Cisco Unity server.

If the SMPP provider does not require a "source address," enter the number that the subscriber calls to check messages. The format and the number that you enter depends on the SMPP provider. The provider may require that you include international country codes, beginning with a plus sign (+) and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234). Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.

Consider that some SMPP providers replace the number that you enter in the From field with their own phone number. For an alternative method of including a call back number, try entering the number that the subscriber calls to check messages in the SMS_TEXT column.

This column corresponds to the From: (Phone Number) field for the SMS (SMPP) device on the on the Subscribers > Subscriber > Message Notification page in the Cisco Unity Administrator.

Enter any combination of digits from 0 through 9, and the following characters, up to a maximum of 40 characters:

+ (plus sign).

. (period) for IP addresses.

, (comma) to insert a one-second pause.

# and * to correspond to the # and * keys on the phone.

SMS_TEXT

Enter the text that the subscriber will receive in the notification.

This column corresponds to the Text field for the SMS (SMPP) device on the on the Subscribers > Subscriber > Message Notification page in the Cisco Unity Administrator.

Up to 160 characters can be entered in this field. However, depending on the character set that you configure Cisco Unity to use, it is possible that messages that are shorter than 160 characters may also be truncated.

SMS_PROVIDER

Enter the name of the SMPP provider. The name must match the Provider Name of an existing provider configured on the System > SMPP Provider pages.

This column corresponds to the SMPP Provider field for the SMS (SMPP) device on the on the Subscribers > Subscriber > Message Notification page in the Cisco Unity Administrator.

SMS_DISABLE

Disables the SMS (SMPP) device. This column corresponds to the Status field for the SMS (SMPP) device on the on the Subscribers > Subscriber > Message Notification page in the Cisco Unity Administrator.

Enter 1.

After you create the subscriber accounts, you can enable the pager in the Cisco Unity Administrator, or you can tell subscribers to do so in the Cisco Unity Assistant web tool.


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: Exclude Reply History and Attachments from TUI Replies

Cisco Unity with Exchange: Subscribers Can Delete Introductions on Forwarded Messages

Enhanced Telephone User Interface Addressing by Using Recipient History

Follow-Me Transfer Rules

Live Reply Enhancements

Outside Callers Can Mark Messages Private

Playback Speed Adjustments Are Saved Across Sessions

Setup Options Added

Subscribers Can Hear Message Duration Before Playback

For a summary of changes made to the default settings and functionality for the Cisco Unity conversation and the Cisco Unity web tools for this release, see the ""Cisco Unity Conversation Changes" section.

Cisco Unity with Domino: Exclude Reply History and Attachments from TUI Replies

By default, Cisco Unity with Domino includes all reply history and attachments with replies. If a message has been replied to more than once, or forwarded with an introduction, those message parts are included in the reply as well.

To exclude the reply history and attachments when subscribers reply to messages by using the phone, configure the Conversation—Exclude History From Replies setting in the Advanced Settings Tool.

Cisco Unity with Exchange: Subscribers Can Delete Introductions on Forwarded Messages

A subscriber who receives a message that has been forwarded one or more times and that contains one or more recorded introductions can choose to have those prior introductions removed when forwarding the voice message. When subscribers choose to remove prior voice introductions, they can still add their own introductions. The content of the original voice message cannot be removed or altered.

This feature can be enabled in the Custom Keypad Mapping tool by assigning a key to the Forward Without Voice Introductions action on the Message Header, Message Body, Message Footer or After Message Action tabs. By default, no keys are assigned to this action. To use the feature, the subscriber forwarding the message must be assigned to one of the three Custom Keypad Mapping conversations (Custom Key Map, Custom Key Map 2, or Custom Key Map 3) on the applicable Conversation page for the subscriber in the Cisco Unity Administrator. To forward a message without all prior voice introductions, the subscriber would use the key assigned to the Forward Without Voice Introduction action; to forward a message and retain all prior voice introductions, the subscriber would use the key assigned to the Forward Message action.

Note the following considerations when enabling or using this feature:

Cisco Unity uses a specific filenaming scheme for voice-introduction attachments, and this feature will remove only those attachments with names that match this naming scheme. The naming scheme relies on the file attachment having a name of Introduction<number>.wav. The second voice attachment is named Introduction2.wav, the third is named Introduction3.wav, and so on. The first voice attachment is the exception and always has a name of Introduction.wav. Filenames of Introduction1.wav or Introduction0.wav are never used for voice attachments.

In a Unified Messaging environment, it is possible for subscribers to attach any file of their choosing, including a WAV file, to a message. If the filename of such an attachment matches the naming scheme that Cisco Unity uses for recorded introductions, the attachment will be removed if this feature is used to forward a message. The match is not case sensitive.

The Conversation and CDE micro traces available through the Unity Diagnostic Tool will write to the AvCsMgr log the name of each attachment scanned and whether it is being removed or kept.

Enhanced Telephone User Interface Addressing by Using Recipient History

The telephone user interface (TUI) addressing enhancements are designed to improve addressing when using the phone keypad, and to decrease the number of key presses necessary to get to a particular address. The addressing enhancements apply only when subscribers address a message by spelling a name; they do not apply for outside callers or when subscribers address a message by extension or by using voice recognition to say the name.

There are two TUI addressing enhancements: the Most Recently Used (MRU) List and Name Suggest.

The MRU List takes all the matches to the entered criteria, then sorts the ones that the subscriber has most recently used to the top of the list. Every time a subscriber confirms selection of a name, that name is added to the MRU List, up to a maximum of 300 names per subscriber. Addresses are automatically removed from the MRU List if they have not been used recently (by default, after 30 days).

Name Suggest performs a lookup after every entered digit (minimum of two digits) and plays a prompt in either of the following conditions:

There is a single exact match found, in which case the name is announced.

There are between two and six matches found, in which case Cisco Unity plays the number of matches found.

Note that the prompt is not a menu; the subscriber can continue to enter additional input if necessary.

The MRU List is always on and cannot be disabled. By default, Name Suggest is disabled. You can enable Name Suggest by checking the Perform Name Suggest on Spelled Names check box 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 or disable Name Suggest for themselves by phone. (See also the "Setup Options Added" section.)

Note that Name Suggest may affect system performance, depending on the size of the database and the number of callers addressing at any given time. Cisco has observed some delay before recorded names are presented under load test conditions when more than 32 ports have active message-sending traffic. For this reason, we recommend that you monitor the per-subscriber use of the feature and disable it if delays are observed. In must customer situations, delays or other performance degradation are not expected.

Follow-Me Transfer Rules

The Follow-Me feature consists of three new call transfer rules—Follow-Me Mobile, Follow-Me Home, and Follow-Me Here—which provide subscribers additional control over where to route callers that are trying to reach them through the Cisco Unity automated attendant. As with the existing Standard, Closed, and Alternate call transfer rules, the Follow-Me rules control how Cisco Unity handles incoming indirect calls, which are from callers who do not dial subscribers directly. The Follow-Me rules support the same attributes as the existing call transfer rules, but differ in their intended use, how they are enabled and disabled, and, in the case of Follow-Me Here, how the transfer number is determined.

The Follow-Me Mobile and Follow-Me Home rules are intended to transfer to mobile and home phone numbers, respectively. While the rules do not have to be used for those numbers, they are numbers at which subscribers frequently might want to be reached and which are not likely to change often. The first time either the Follow-Me Mobile or Follow-Me Home rule is invoked, the subscriber will be asked to enter a phone number. The number will be validated against the current transfer restriction table for Cisco Unity; if no conflict is found, the subscriber will be asked either to confirm the number entered or to enter a new number. As with the existing contact rules, once a number is specified for either rule, that number will be used each time the rule is enabled. Unlike the existing rules, however, the transfer number can be changed when the rule is enabled by using the phone keypad or a voice command.

When a subscriber logs on to Cisco Unity by phone and activates the Follow-Me Here rule, Cisco Unity obtains the calling party ID (CPID) provided and makes that number the transfer number for the rule. Because CPID is not always provided or can be masked by a phone system, the subscriber must confirm the intended transfer number or enter the desired number each time he or she attempts to activate the Follow-Me Here rule.

Once a Follow-Me rule is activated, it remains active until disabled. Disabling a Follow-Me rule can be done either by explicitly disabling the rule or by enabling a different Follow-Me rule.

When the Spoken Commands feature is enabled on the server, subscribers who have access to voice-recognition features and have the Press-or-Say input style enabled can activate a Follow-Me rule from the Main menu by saying the rule's name (for example, "Follow-Me Mobile"). To disable the active Follow-Me rule, subscribers say, "Disable Follow-Me." It is not necessary to specify the name of the rule to disable, because only one Follow-Me rule can be active at a time. For Help, subscribers say, "Follow-Me Help." (For instructions on enabling the Spoken Commands feature, refer to Release Notes for Spoken Commands in Cisco Unity 5.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/release/notes/501voicecommandsrelnotes.html.)

For subscribers who use one of the three Custom Keypad Mapping conversations, you can assign keys to the Follow-Me rules on the Main Menu tab in the Custom Keypad Mapping tool. You may assign a different key to enable each of the three Follow-Me rules, and a single key to disable the active Follow-Me rule. Assigning a key does not remove the use of voice commands for enabling and disabling Follow-Me rules.

Note the following considerations when allowing subscribers to use the Follow-Me rules:

When entering a transfer number, the subscriber must enter all digits necessary to complete the transfer. (For example, a 9 is often used to first obtain dial tone on the PSTN.)

When entering a transfer number, the subscriber can enter a 1-second pause by pressing #.

If a trunk access code or other code is necessary to complete the transfer and is explicitly entered by a subscriber, Cisco Unity will automatically insert a 1-second pause between the code and the final 7- or 10-digit phone number.

All transfer numbers are checked against the transfer restriction table for the subscriber. If a number violates the restriction table, Cisco Unity notifies the subscriber and asks the subscriber to enter a new number.

Only a single Follow-Me rule can be enabled at a time.

The Follow-Me Here rule uses the CPID as the transfer number only when activated through a spoken command or a assigned key at the Main Menu. If subscribers enable the Follow-Me Here rule through the Setup Options Transfer Settings menu, they must specify the number to transfer to, and confirm that Cisco Unity should transfer to the number rather than to voicemail.

The Follow-Me rules take precedence over the Alternate, Closed and Standard transfer rules. For example, if the Follow-Me Mobile, the Alternate, and the Standard transfer rules are all enabled, then the active transfer rule is the Follow-Me Mobile rule.

You can configure Cisco Unity to notify subscribers if a Follow-Me rule is active when they access their voice mailbox by checking the Follow-Me Rule Notification check box on the applicable Conversation page for a subscriber or subscriber template in the Cisco Unity Administrator.

Live Reply Enhancements

The live reply feature has been enhanced in the following ways:

Subscribers can live reply to messages left by unidentified callers. (When a caller is connected to Cisco Unity, if the caller ID provided by the phone system does not map to the primary or alternate extension of a subscriber, the caller is said to be unidentified, and any message left will be treated as being from an unidentified caller.)

Live reply to messages left by other subscribers uses the active call transfer rule of the subscriber being replied to, even if the call transfer rule is configured to send calls to the personal greeting.

Live reply to messages left by AMIS, Bridge, and VPIM subscribers who are homed on another Cisco Unity server in the dialing domain respects the settings configured on the Network > Dialing Domain options page in the Cisco Unity Administrator.

Live Reply to Unidentified Callers

When reviewing a message left by an unidentified caller, a subscriber whose class of service allows live reply to unidentified callers can call the sender at the caller ID provided by the phone system. To initiate the live reply, Cisco Unity checks the caller ID against the transfer restriction table for the subscriber. If the number is allowed, Cisco Unity returns the call by performing a release transfer to the phone system on the same voicemail port the subscriber is using to check the message; all translation patterns, trunk access codes, prefixes, area codes, or other formatting that must be done to generate a proper dial string from the caller ID must be performed by the phone system in order for live reply to unidentified callers to work properly.


Note Confirm that any phone system programming to support live reply to unidentified callers does not conflict with any other Cisco Unity outdials such as MWI, message notification, and call transfers. On Cisco Unity systems integrated with Cisco Unified Communications Manager, you may need to dedicate ports to MWI in order to avoid MWI delays that can be caused by an overlapping route pattern.


Live reply is controlled by class of service. You can configure live reply by checking or unchecking either or both of the following check boxes on the applicable Messages page for a class of service in the Cisco Unity Administrator:

Subscribers Can Reply to Messages From Other Subscribers by Calling Them.

Subscribers Can Reply to Messages from Unidentified Callers by Calling Them.

The key-press command for live reply to unidentified callers is the same as the key-press command for live reply to subscribers. The keys that subscribers press for live reply depend on the conversation that the subscriber is configured to use. For example:

Standard Conversation—Subscribers press 44 in the After Message Menu.

Optional Conversation 1—Subscribers press 88 in the After Message Menu.

To determine the key-press command in other conversations, run the Custom Keypad Mapping tool and look for the Call the Sender action for the applicable conversation. Note that you can reset one of the three custom key maps to any of the pre-configured conversations (such as the Alternate Keypad Mapping - N) so that you can see which keys are mapped to the Call the Sender action for that conversation.

Currently, live reply is not available when using voice commands.

Live Reply to Subscribers Enhancement

Cisco Unity does not use the caller ID when doing a live reply to a message left from another subscriber. The way the live reply call is handled in this case depends on settings configured on the Cisco Unity server on which the subscriber who is being replied to is homed, as follows:

If the message was left by a subscriber—including messages from Internet, Trusted Internet, AMIS, Bridge, and VPIM subscribers —on the same Cisco Unity server, Cisco Unity uses the active call transfer rule of the subscriber who is being called (that is, the original message sender) when making the live reply call, even when the active call transfer rule is configured to send calls to the personal greeting. (In previous versions of Cisco Unity, when the active call transfer rule was set to send calls to the personal greeting, Cisco Unity rejected the transfer and played the prompt, "You cannot call the subscriber. Try recording a reply instead.")

If the message was left by a subscriber on another Cisco Unity server in the dialing domain, whether or not Cisco Unity does the live reply call depends on the Live Reply setting on the Dialing Domain Options page in the Cisco Unity Administrator. The Dialing Domain Options page also determines the type of call transfer that Cisco Unity uses when doing the live reply call—either a release transfer to the transfer string that is replicated to other Cisco Unity servers in the dialing domain, or a cross-server transfer to the other Cisco Unity server.

If the message is left by a subscriber on another Cisco Unity server in the global directory but outside of the dialing domain, although the key option is available, Cisco Unity will not make the live reply call. In some previous versions, Cisco Unity incorrectly performed live replies to subscribers on Cisco Unity servers not in the dialing domain. In Cisco Unity 7.0(2), live replies are restricted to the Cisco Unity servers in the dialing domain.

Live reply to messages left by AMIS, Bridge, and VPIM subscribers who are homed on another Cisco Unity server in the dialing domain respects the settings configured on the Network > Dialing Domain options page in the Cisco Unity Administrator. In previous versions of Cisco Unity, live reply (and call transfers) to AMIS, Bridge, and VPIM subscribers was always done via release to switch transfer to the xferstring that is replicated to all Cisco Unity servers in the directory. (In Cisco Unity 7.0(2), you can configure the Networking—Cross-server Transfer Behavior for External Subscribers setting in the Advanced Settings Tool to revert back to the previous behavior.)

Outside Callers Can Mark Messages Private

An outside caller who leaves a message for a subscriber or a call handler can mark that message as private. Additionally, when Identified Subscriber Messaging is enabled, subscribers who call other subscribers from their primary or alternate extensions and are forwarded to voicemail can also mark the messages they leave as private. Messages marked private cannot be forwarded by phone, from Cisco Unity ViewMail for Microsoft Outlook or from the Cisco Unity Inbox web tool. Previously, only subscribers who were logged on to Cisco Unity could mark messages as private when sending messages by phone.

You configure the Mark Messages as Private field on the applicable Messages page for a subscriber template, an individual subscriber, or a call handler in the Cisco Unity Administrator, or by using the Bulk Edit utility. The available options are to always mark messages as private, never mark messages as private, or ask callers for their preference.

Subscribers can allow all callers to mark messages as private by checking the Mark the Message as Private check box on the Preferences > Transfer and Screening Options page in the Cisco Unity Assistant web tool. When checked, callers will be given the option to mark the message as private; when unchecked, callers leaving a message will not be given the option to mark the message as private.

Note the following considerations when allowing callers to mark messages as private:

Messages that are marked private are not automatically encrypted. A voice message can be private but not encrypted, or private and encrypted.

You can configure encryption for messages from outside callers on the Configuration > Message Security page in the Cisco Unity Administrator. For Identified Subscriber Messaging calls, the encryption setting that Cisco Unity applies depend on the type of identified caller:

For subscribers, Cisco Unity uses the setting on the Subscribers > Subscriber > Features page.

For VPIM or Bridge contacts, Cisco Unity uses the setting on the Delivery Locations > Delivery Location > Profile page.

For all other contacts, Cisco Unity uses the setting on the Configuration > Message Security page.

When the administrator configures the Mark Messages as Private field for a subscriber to always mark messages private, callers will not be asked and all messages will be marked private. A subscriber can work around this by unchecking the Mark the Message as Private check box in the Cisco Unity Assistant, saving the page, and then checking the check box again, at which time callers will then be asked if they would like to mark the message as private.

Playback Speed Adjustments Are Saved Across Sessions

Subscribers can use key presses to speed up or slow down both message and prompt playback by phone. The new speed setting is saved, so that when they next call in, the same speed settings will be used.

Subscribers can use the message playback speed adjustment key presses at any time during message playback. For example, subscribers who use the Standard Conversation or Optional Conversation 1 can press 4 to decrease prompt or message playback speed and press 6 to increase prompt or message playback speed. Cisco Unity adjusts either the prompt playback speed or the message playback speed depending on the phase of playback at the time the key is pressed: when pressed during the message header or footer, Cisco Unity adjusts the prompt playback speed; during the message body, Cisco Unity adjusts the message playback speed.

Subscribers who are assigned to one of the three Custom Keypad Mapping conversations can also use global key commands for increasing and decreasing prompt playback speed from anywhere in the conversation where a prompt is heard (or for changing message playback speed, if pressed during the message header, body, or footer). By default, 99 is assigned to the Increase Speed and Save action, and 97 is assigned to the Decrease Speed and Save action; you can configure the key maps for these actions on the Globals tab in the Custom Keypad Mapping tool.

In previous versions of Cisco Unity, subscribers could use defined key presses during message playback to speed up or slow down playback for each message individually; the change did not affect the playback speed of other messages. No key presses were available for adjusting prompt playback speed by phone.

Setup Options Added

Many settings have been added to the Setup Options menus so that subscribers can adjust their values by phone.

In the Setup Options Message Settings menu, the following settings have been added:

Message Notification > SMS Phone. Subscribers can use this menu to configure an SMS notification device. In previous versions, this device could be configured only by using the Cisco Unity Assistant web tool, the Cisco Unity Administrator, and Bulk Edit. See also the "Subscribers Can Configure SMS Notification Devices by Phone" section.

Message Send Style. Subscribers can choose between the Standard Send menu or the Streamlined Send menu for sending messages. In previous versions, this setting was available only in the Cisco Unity Assistant web tool, the Cisco Unity Administrator, and Bulk Edit.

Name Suggest. This setting represents new Cisco Unity functionality. See also the "Enhanced Telephone User Interface Addressing by Using Recipient History" section.

Name Playback. Subscribers can use this setting to toggle whether Cisco Unity greets them by their recorded name after they log on. In previous versions, this setting was available only in the Cisco Unity Assistant, the Cisco Unity Administrator and Bulk Edit.

Automatic Messages Playback. Subscribers can use this setting to toggle whether Cisco Unity starts to play new messages automatically after they log on. In previous versions, this setting was available only in the Cisco Unity Assistant, the Cisco Unity Administrator, and Bulk Edit.

In the Setup Options Transfer Settings menu, the following settings have been added: (These settings all represent new functionality. See also the "Follow-Me Transfer Rules" section.)

Follow-Me Mobile Transfer Rule

Follow-Me Here Transfer Rule

Follow-Me Home Transfer Rule

Subscribers Can Configure SMS Notification Devices by Phone

Subscribers can use the Message Notification menu (in Setup Options) to turn an SMS notification device on or off, to set the phone number for the device, or to review the device settings.

The SMS notification device setup conversation is available to a subscriber only when either of the following conditions is met:

The SMS notification device is already assigned to an SMPP provider that is enabled.

There is only one SMPP provider on the system that is enabled and is not owned by the subscriber. In this case, Cisco Unity assigns (or reassigns) the SMS device to this SMPP provider when the subscriber attempts to access the SMS notification device setup conversation.

In Cisco Unity 7.0(2), administrators can also configure this device by using the Cisco Unity Bulk Import wizard. See also the "Cisco Unity Bulk Import Wizard and Bulk Edit Utility Enhancements" section.

Subscribers Can Hear Message Duration Before Playback

Subscribers can hear the duration of a message in minutes and seconds before Cisco Unity plays the message when checking messages by phone. You can enable the automatic playback of message duration by checking the Message Duration check box in the Before Playing Each Message, Play section 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. By default, Cisco Unity will not announce the message duration during the message header.

Subscribers can configure whether or not to automatically play the message duration before playing a message on the Message Playback Preferences page in the Cisco Unity Assistant web tool. Regardless of whether this feature is enabled, subscribers can also hear the message duration by playing the message properties during or after message playback. In addition, subscribers who use visual clients such as Phone View to view messages can see the duration of a message along with the other message properties.

Cisco Unity Failover Enhancements

Cisco Unity failover provides the following serviceability improvements:

The failover configuration wizard prompts to disable all security-related applications between the primary and secondary servers such as virus-scanning applications, firewall applications, and Cisco Security Agent for Cisco Unity.

The failover configuration wizard prompts to run the Permissions wizard on the primary and secondary servers.

The failover configuration wizard prompts to confirm that the Cisco Unity software is installed on the same drive and directories on both primary and secondary servers.

The failover configuration wizard correctly identifies that SQL Server is installed.

The directory services account owns the SQL nightly and SQL weekly backup jobs.

The Failover Monitor provides the date and time of the last failover occurrence.

Cisco Unity with Exchange: VPIM Delivery Location Configuration Options

VPIM delivery locations include the following new delivery location configuration options, which apply when sending messages from Cisco Unity to the delivery location:

Remove Message Subject—If enabled, the Voice Connector does not include the "Subject:" MIME header or value when converting the message to VPIM for sending to this location.

Remove All Text Attachments—If enabled, the Voice Connector removes all text attachments when converting the voice message to VPIM for sending to this location. This includes any previous vCard attachments on the message; however, if the delivery location is configured to include the sender's vCard, this vCard will still be added to the message before sending.

Remove All Fax Attachments—If enabled, the Voice Connector removes all fax attachments when converting the message to VPIM for sending to this location.

Note that this functionality requires Cisco Unity Voice Connector for Microsoft Exchange version 14.0(1). Also note that when any of these settings are enabled, the sender is not notified that part of the message has been removed.

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

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 one of the following trusts:

Two-way forest trust

Create the trust between the corporate forest and the forest that contains the Cisco Unity server.

One-way forest trust

Create the trust with the forest that contains the Cisco Unity server trusting the corporate forest:

a. In the corporate forest, create a one-way incoming forest trust. (The corporate forest allows the Cisco Unity forest to trust it.)

b. In the Cisco Unity forest, create a one-way outgoing trust. (The Cisco Unity forest trusts the corporate forest.)

If you are using Windows Server 2003, you can do both steps simultaneously, without having to separately log on to a server in each forest.


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

Step 3 If you created a two-way trust, skip to Step 4.

If you created a one-way trust in Step 1, at a command line, run the following command to connect the Cisco Unity server with a domain controller in the corporate forest:

net use \\<domain controller in the corporate forest>\ipc$ /USER:<DomainName>\<UserName> *

where <DomainName>\<UserName> refers to a user in the corporate forest. The account does not require any special permissions.

Step 4 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>
-c <domain controller in the corporate forest that you specified in Step 3>


Note If you created a one-way trust, include the -c switch; if you created a two-way trust, omit the -c switch.


For example:

grantunityaccess -u CorporateDomain\dgupta -s dmitrygupta -c CorporateDC


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 5 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 6 If you created a two-way trust, skip to Step 7.

If you created a one-way trust, at a command line, run the following command to disconnect the Cisco Unity server from the domain controller in the corporate forest that you connected to in Step 3.

net use \\<domain controller in the corporate forest>\ipc$ /d

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


Media Master Can Be Disabled in the Cisco Unity Assistant Web Tool

To prevent the Media Master control bar from being displayed in the Cisco Unity Assistant, configure the Unity Assistant—Disable MediaMaster setting in the Advanced Settings tool. This setting does not affect the Media Master control bar in the Cisco Unity Inbox web tool.

MWI Constant Message Count

Message Waiting Indicators (MWIs) are enhanced to provide a real-time count of new and saved messages, and new and saved urgent messages. Along with this enhancement, Cisco Unity continues to provide the traditional indicator (light or stutter dial tone) to indicate that new messages are available.

The enhanced MWI information appears on the LCD screen portion of the user Cisco IP phone in the following format:

Messages-Waiting: <yes or no>
Voice-message: <new>/<saved> <new urgent>/<saved urgent>
 
   

This feature requires:

Cisco Unified Communications Manager 7.1.

Cisco Unity sends MWIs messages through a SIP trunk to Cisco Unified CM.

MWI and message count are enabled for each subscriber.

These settings can be set in the Cisco Unity Administrator on the Subscribers > Subscribers > Messages page for the subscriber, on the Subscribers > Subscriber Template > Messages page for the subscriber template, and in the Bulk Edit tool in Cisco Unity Tools Depot.

Cisco IP phones capable of displaying the MWI message count information.

New Port Status Monitor

The new Port Status Monitor is a tool for monitoring voice messaging ports on Cisco Unity and is available in the Cisco Unity Tools Depot. The tool provides improved performance and functionality over the web-based Status Monitor and the previously existing Port Status Monitor.

For instructions on using the new Port Status Monitor tool, refer to the Help that is available with the tool. To download the tool, go to the Cisco Unity Tools website at http://www.ciscounitytools.com and click the 7.x Tools tab.

Subject Lines of Voice Messages Can Be Configured

Using the Cisco Unity Administrator, administrators can configure the format of voice message subject lines for four types of messages: outside caller messages, subscriber messages, interview handler messages, and live record messages. The subject lines can include Caller ID and Name, Called ID and Name, Sender ID and Name, and the message flags for urgent, private, and secure. Voice message subjects will not be announced when a subscriber listens to a message by phone, but they will be seen when subscribers access their messages by using a GUI client, such as ViewMail for Outlook or the Cisco Unity Inbox web tool.

To customize voice message subjects, in the Cisco Unity Administrator, go to the System > Configuration > Message Subjects page. You can configure both the wording and the information that is included in the subject line of voice messages.

Note the following considerations when defining subject line formats:

Subscribers will not hear a voice message subject when listening to messages by phone.

Cisco Unity does not apply custom subjects to AMIS, Bridge, or VPIM messages, or to messages sent from a desktop client such as ViewMail for Outlook, Lotus Notes, or the Cisco Unity Inbox.

If you have upgraded from an earlier Cisco Unity version, messages received before the upgrade will not have customized subjects. Subjects will be displayed only for new messages that are received after upgrading to Cisco Unity 7.0(2).

The values for Caller ID, Caller Name, Called ID, and Called Name come from the phone system, so they will be available only if the phone system is configured to present that information to Cisco Unity; this is particularly notable for messages from outside callers, because phone systems are often not configured to provide external caller names.

Table 3 lists the replaceable parameters that can be added to customized subject lines.

Table 3 Optional Replaceable Parameters in Customized Subject Lines 

Parameter
Description

%CALLERID%

The caller ID on the phone call, or a system administrator defined default if no caller ID is available. This data comes from the telephony integration.

%CALLERNAME%

The caller name on the phone call, or a system administrator defined default if no caller name is available. This data comes from the telephony integration.

%CALLEDID%

The called ID on the phone call, or a system administrator defined default if no called ID is available. This data comes from the telephony integration.

%CALLEDNAME%

The called name on the phone call, or a system administrator defined default if no called name is available. This data comes from the telephony integration.

%SENDERID%

The extension of the sender, or a system administrator defined default if no extension is available. For messages recorded by call handlers or interview handlers, the DTMF access ID of the handler.

%SENDERNAME%

The name of the sender, or a system administrator defined default if no name is available. For messages recorded by call handlers or interview handlers, the display name of the handler.

%U%

Replaced with the system administrator defined value to describe an urgent message if the message is urgent. Otherwise, omitted.

%P%

Replaced with the system administrator defined value to describe a private message if the message is private. Otherwise, omitted.

%S%

Replaced with the system administrator defined value to describe a secure message if the message is secure. Otherwise, omitted.


UTIM

The Cisco Unity Telephony Integration Manager (UTIM) provides the following enhancements:

UTIM supports the quad-span TIMG (DMG-2000 series), which has 96 ports.

On the Properties page of integrations, an Advanced tab is added for Automatic Gain Control settings (formerly on another tab) and other infrequently used settings that were accessible only through the registry.

The Subscriber-Phone System Associations and Call Handler-Phone System Associations tools show the primary extensions and allow sorting entries by the information in each column.

Changed Functionality—Release 7.0(2)

This section contains information about changed functionality for Cisco Unity Release 7.0(2) 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 7.0(2). Some offerings may not be supported by Cisco TAC. Refer to http://www.ciscounitytools.com/ for information.

Alternate Device Number Field Validates Against Alt Ext Restriction Table

When subscribers whose class of service allows them to add their own alternate extensions enter a phone number in the Alternate Devices section in the Cisco Unity Assistant web tool, Cisco Unity checks the number against the {Default Alt Ext} restriction table. In previous releases, Cisco Unity checked the length of the number against a registry key defining the minimum length of subscriber-defined extensions.

Apache Tomcat Sample Applications Contain Security Vulnerabilities

Apache Tomcat, which is automatically installed on the Cisco Unity server and is required for Cisco Unity to function properly, contains security vulnerabilities in sample applications. To eliminate the security vulnerabilities, do the following procedure to delete the sample directories. For more information, refer to the CVE-IDs "CVE-2007-1355" and "CVE-2007-2449" on the CVE (Common Vulnerabilities and Exposures) website at cve.mitre.org.

To Delete Apache Tomcat Sample Applications


Step 1 In the Services MMC, stop the Tomcat service.

Step 2 Delete the following directories and their contents under the directory where Cisco Unity is installed (Commserver by default):

cscoserv\Tomcat\webapps\examples

cscoserv\Tomcat\webapps\tomcat-docs

Step 3 In the Services MMC, restart the Tomcat service.


Automated Attendant Search Scope Setting Moved to the Cisco Unity Administrator

The Networking—Set Auto Attendant Search Scope setting has been removed from the Advanced Settings Tool. The automated attendant search scope can be configured on the Network > Primary Location > Profile page in the Cisco Unity Administrator. The existing value for the setting is retained upon upgrading. For new installations, the setting defaults to Dialing Domain.

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 Settings Changed or Removed from the Advanced Settings Tool

Defaults for Outside Caller and Identified Subscriber Messaging Conversation Settings

Defaults for Subscriber Conversation Settings

Conversation Settings Changed or Removed from the Advanced Settings Tool

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

Conversation—Reply to Unknown Caller. The option to reply to unknown callers has been removed. See the "Live Reply Enhancements" section for improved functionality allowing subscribers to return calls to unknown callers.

Defaults for Outside Caller and Identified Subscriber Messaging Conversation Settings

The following settings are the defaults for the outside caller and identified subscriber messaging (ISM) conversation for new installations and upgrades:

Ask caller for their preference whether to mark messages as urgent.

Ask caller for their preference whether to mark messages as private.

As a result of these changes, after recording a message, outside callers and subscribers who call other subscribers and are forwarded to Cisco Unity will be prompted to press 1 to mark the message as urgent or 2 to mark the message as private. (In previous releases, if Cisco Unity was configured to ask callers for their preference whether to mark messages as urgent, Cisco Unity prompted these callers to press 1 to send the message with normal priority or 2 to send the message with urgent priority.)

You configure these settings on the applicable Messages page for a subscriber template, an individual subscriber, or a call handler in the Cisco Unity Administrator, or by using the Bulk Edit utility.

Subscribers whose class of service allows them to use the Cisco Unity Assistant web tool can configure these settings on the Transfer and Screening Preferences page.

Defaults for Subscriber Conversation Settings

The following settings are defaults for the subscriber conversation for new installations and upgrades:

Brief prompts.

Do not play the subscriber recorded name after logging on.

Play new messages automatically after logging on.

You can configure these settings 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 whose class of service allows them to use the Cisco Unity Assistant web tool can configure these settings on the Phone Menu Preferences page.

Cisco Unity Server Licensing

When a Cisco Unity license violation occurs, Cisco Unity provides more effective warnings and extends the period before Cisco Unity will stop taking calls. The steps that Cisco Unity takes depends on whether Cisco Unity failover is configured.

Steps When Failover Is Not Configured

When failover is not configured, Cisco Unity takes the following steps when a Cisco Unity license violation occurs and until the license violation is corrected:

1. During the first 30 days after a Cisco Unity license violation, Cisco Unity sends warnings of the license violation:

Each day, the members of the Unaddressed Messages public distribution list receive a voice message that a license violation has occurred.

Each day, a warning is entered in the Event log.

A warning is displayed in the Licensing snap-in.

2. During the period of 31 through 60 days after a Cisco Unity license violation, Cisco Unity sends warnings of the license violation:

On the 31st day after a license violation, all subscribers on the local server receive a broadcast message that the license violation has occurred.

Each day, a warning is entered in the Event log.

A warning is displayed in the Licensing snap-in.

3. After this 60-day period, Cisco Unity takes the these actions:

On the 61st day after a Cisco Unity license violation, Cisco Unity waits 48 hours, then stops taking calls. When the Cisco Unity software is restarted, Cisco Unity will take calls for 48 hours, then stop taking calls again.

Each day, an error is entered in the Event log.

An error is displayed in the Licensing snap-in.

Steps When Cisco Unity Is Configured for Failover

When Cisco Unity is configured for failover, the steps in the "Steps When Failover Is Not Configured" list above apply to the primary Cisco Unity server.

However, the secondary Cisco Unity server, if it is active, takes the following steps when a Cisco Unity license violation occurs or when it has not contacted the primary server:

1. During the first 60 days, Cisco Unity sends warnings of the Cisco Unity license violation:

Each day, the members of the Unaddressed Messages public distribution list receive a voice message that the license violation has occurred.

Each day, a warning is entered in the Event log.

A warning is displayed in the Licensing snap-in.

2. During the period of 61 through 120 days, Cisco Unity sends warnings of the Cisco Unity license violation:

On the 61st day after a license violation, all subscribers on the server receive a broadcast message that the license violation has occurred.

Each day, a warning is entered in the Event log.

A warning is displayed in the Licensing snap-in.

3. After this 120-day period, Cisco Unity takes the these actions:

On the 121st day after a Cisco Unity license violation, Cisco Unity waits 48 hours, then stops taking calls. When the Cisco Unity software is restarted, Cisco Unity will take calls for 48 hours, then stop taking calls again.

Each day, an error is entered in the Event log.

An error is displayed in the Licensing snap-in.

Cisco Unity with Domino: Anonymous Logon No Longer Required for TRaP

Revised July 14, 2008

When Domino is the message store, you can disable anonymous logon for remote access on client workstations and still use the phone record and playback (TRaP) feature in the Lotus Notes client and the Cisco Personal Communications Assistant. (Beginning with Windows XP Service Pack 2, anonymous logon for remote access is disabled by default.)

To disable anonymous logon on client workstations, you must install the DUC for Cisco csClient 1.2.3 Build 19 Hotfix 5 on the workstations. To download the hotfix, do the "To Download the Software Required to Install Cisco Unity 7.0(2)" procedure. Follow the instructions for downloading Cisco Unity disc images, which is where DUC for Cisco csClient 1.2.3 Build 19 Hotfix 5 is available. For information on installing the hotfix, see the readme included with the hotfix.

The security settings that you must change if you do not install DUC for Cisco csClient 1.2.3 Build 19 Hotfix 5 are documented in the tech note "Cisco Unity Domino Error - Play to phone: Unspecified error" in the Cisco Unity with Domino group at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html.

Cisco Unity with Domino: Interop Gateway Service

When Domino is the message store and you are using AMIS, the Cisco Unity Bridge, or VPIM to interoperate with other voice-messaging systems, Cisco Unity requires the Interop Gateway service to log on by using the Cisco Unity directory and message store services account. (This is the services account that you selected in the Cisco Unity Permissions wizard.) In previous versions of Cisco Unity, we recommended that you use the local system account.

See also the following documentation corrections in these release notes:

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with IBM Lotus Domino): Configuring the Interop Gateway

Networking Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Configuring the Interop Gateway

Cisco Unity with Domino: Serviceability Improvements

The IBM Lotus Domino Unified Communications (DUC) for Cisco runtime DLL has been upgraded, which significantly improves serviceability of Cisco Unity with Domino.

Cisco Unity with Domino: Storage of Notes Password on the Cisco Unity Server

Beginning with Cisco Unity 7.0, the way the IBM Lotus Notes password is stored on the Cisco Unity server is different than for previous releases. The result is that any Cisco Unity tools that access the Domino server (for example, the Domino Unity Tool, in the CommServer\Utilities\Domino\DUT directory on the Cisco Unity server) must be run while you are logged on either as the installation account or as the directory and message store services account. These are the accounts that you specified when you ran the Cisco Unity Permissions wizard during installation.

Cisco Unity with Exchange: Resynchronizing Message Counts with Exchange Is Faster

Cisco Unity uses Exchange search folders, when they are available, to update the message count for each subscriber. As a result, updating message counts takes about half as long as in previous versions of Cisco Unity. Message counts, which are stored in memory on the Cisco Unity server, are automatically resynchronized with message counts in Exchange when the Cisco Unity server is restarted; they can also be manually resynchronized to resolve problems with MWIs. Cisco Unity uses message counts to trigger message notifications, including activating or deactivating the MWI for a subscriber, as appropriate.

Note that the time required for the resynchronization to complete depends on the number of subscribers and on the phone-system integration. For example, the resynchronization on a system with 15,000 subscribers that is integrated with Cisco Unified Communications Manager 6.0(1) may take 2.5 hours to complete.

Defaults for Addressing Search Scopes

The default search scope values for subscriber searches and blind addressing on the Networking > Primary Location > Addressing Options page have changed. Both settings now default to Global Directory for new installations. The existing values for the settings are retained upon upgrading. (In previous releases, the default value for subscriber searches was Local Server, and the default value for blind addressing searches was None.)

Default for Allowing Subscribers to Create Alternate Extensions

The default setting to allow subscribers to add, modify, and delete their own alternate extensions on the Subscribers > Class of Service page in the Cisco Unity Administrator has changed for new installations and upgrades. By default, subscribers are allowed to define alternate extensions. (Alternate extensions are referred to as Alternate Devices in the Cisco Unity Assistant web tool.)

Encryption Algorithm for Phone Password

The phone password is stored in the Cisco Unity database using SHA-1 encryption, which is more secure than the MD5 encryption that was used for previous versions of Cisco Unity.

Java SDK Upgraded

The Java SDK was upgraded from JavaSDK_1.4.0_1 to JavaSDK_1.4.2_13. This change does not affect performance or functionality.

Remote Serviceability Kit Updates

To facilitate monitoring by network monitoring systems, the Remote Serviceability Kit includes four Cisco Unity services in the Cisco Unity MIB:

CuDohMgr.exe

CuMessageAgeAging.exe

CuMDBStoreMonitor

AvCsNodeMgr

For information on supported monitoring software, refer to the "Supported Monitoring Software" section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/support/5xcusupp.html.

Support for Up to 200 Voice Messaging Ports

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

Number of Ports
Requirements

1 to 72

All integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP (excluding SIP trunk)

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

Integrations with PIMG or TIMG units

Integrations with voice cards

73 to 96

The following integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP trunk (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 must be enabled in the Advanced Settings tool in Cisco Unity Tools Depot.

97 to 200

The following integration types are supported:

SCCP (Cisco Unified CM and Cisco Unified CM Express)

SIP trunk (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=2800 switches must be added to the Windows Boot.ini file.

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


Installation and Upgrade Information

Downloading Software for Cisco Unity 7.0(2)

Upgrading to Cisco Unity 7.0(2)

Installing Cisco Unity for the First Time

Installation and Upgrade Notes

Downloading Software for Cisco Unity 7.0(2)

Revised April 4, 2012

This section contains a procedure for downloading Cisco Unity 7.0(2) 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 7.0(2) discs, we recommend that you do the procedure to download the following software:

The current 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 7.0(2), if any.

To Download the Software Required to Install Cisco Unity 7.0(2)


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

You always need DVD 1.

You need other DVDs only 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 Download the required files according to the applicable substeps in Table 4 below.


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


Table 4 Download Substeps 

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.

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

c. Click Cisco Unity System Software and 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 image

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

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

b. Click CiscoUnity7.0.2-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.

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

b. Click Microsoft Updates for Cisco Unity/Unity Connection-s.

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


Table 5 lists the contents of the Cisco Unity 7.0(2) 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 5 Contents of Cisco Unity 7.0(2) 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 ENU (English-United States). Required for all installations.

2

Language files for the following languages:

ARA (Arabic-Saudi Arabia)

CAT (Catalan-Spain)

CHS (Chinese-PRC)

CHT (Chinese-Taiwan)

CSY (Czech-Czech Republic)

CYM (Welsh-Wales)

DAN (Danish-Denmark)

3

Language files for the following languages:

DEU (German-Germany)

ENA (English-Australia)

ENC (English-Canada)

ENG (English-United Kingdom)

ENX (English TTY/TDD-United States)

ENZ (English-New Zealand)

ESO (Spanish-Colombia)

4

Language files for the following languages:

ESP (Spanish-Spain)

FRA (French-France)

FRC (French-Canada)

HUN (Hungarian-Hungary)

ITA (Italian-Italy)

5

Language files for the following languages:

JPN (Japanese-Japan)

KOR (Korean-Korea)

NLB (Dutch-Belgium)

NLD (Dutch-Netherlands)

NOR (Norwegian-Bokmål)

6

Language files for the following languages:

PLK (Polish-Poland)

PTB (Portuguese-Brazil)

PTG (Portuguese-Portugal)

RUS (Russian-Russia)

SVE (Swedish-Sweden)

ZHH (Chinese-Hong Kong SAR)

Service Pack 1

The following software required to complete a Cisco Unity installation:

Cisco Unity System Preparation Assistant

Crystal Reports XI

Exchange 2000 Server Service Pack 3 or Exchange Server 2003 Service Pack 2

Exchange 2000 Server post-Service Pack 3 rollup (Microsoft Knowledge Base article 870540)

Internet Explorer 6.0 with Service Pack 1

Microsoft Data Access Components Refresh (Installed by Microsoft SQL Server 2000 Service Pack 4 or Microsoft MSDE 2000 Service Pack 4)

Microsoft .NET Framework 1.1, Microsoft .NET Framework 2.0 and Microsoft .NET Framework 2.0 Service Pack 1

Microsoft Extensible Markup Language (MSXML) 3.0 with Service Pack 1 (Installed by Microsoft SQL Server 2000 Service Pack 4 or Microsoft MSDE 2000 Service Pack 4)

Microsoft Visual C++ 2005 Redistributable DLLs

SQL Server 2000 Service Pack 4 or MSDE 2000 Service Pack 4

Windows 2000 Server patch for "Vulnerability in Windows Kernel Could Result in Remote Code Execution" (Microsoft Security Bulletin MS06-051, Microsoft Knowledge Base article 917422)

Windows 2000 Server Service Pack 4 or Windows Server 2003 Service Pack 2

Windows Installer 3.1


Upgrading to Cisco Unity 7.0(2)

For upgrades from Cisco Unity 5.x to version 7.0(2), see the following documentation:

The "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity.

The "Documentation Updates" section in these release notes applicable to your message store:

"Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" section

"Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" section

See also the "Installation and Upgrade Notes" section in these release notes.

For upgrades from Cisco Unity 4.x to version 7.0(2), see the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity. See also the "Installation and Upgrade Notes" section.


Note The following links go to Release 5.x versions of the guide; all 5.x content applies to version 7.x as well.


Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With IBM Lotus Domino) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/dom/5xcurugdx.html.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/upgrade/guide/ex/5xcurugex.html.


Caution Upgrading from Cisco Unity 3.x directly to Cisco Unity 7.0(2) is not supported. You must upgrade to Cisco Unity 4.x first, then upgrade again from 4.x to 7.x.

Installing Cisco Unity for the First Time

For instructions on installing a new Cisco Unity 7.0(2) system, refer to the Installation Guide for Cisco Unity that matches the configuration you are installing. For descriptions of the various installation guides, refer to Use the Installation Guide That Matches the Cisco Unity 7.x Configuration at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/correct_ig/7xcuigcrct.html.

Installation guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. Use the Release 5.x versions of the guides; all 5.x content applies to Release 7.x.

See also the following section, "Installation and Upgrade Notes."

Installation and Upgrade Notes

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run

Customizing Cisco Unity System Prompts Is Not Supported

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 5.0 Does Not Require Extending Active Directory Schema, But Upgrade from 4.x Does

Upgrade Always Requires Upgrade Purchase, Sometimes Requires Upgrade License

Upgrade from Cisco Unity 4.0(2) or 4.0(1) 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.

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

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 5.0 Does Not Require Extending Active Directory Schema, But Upgrade from 4.x Does

Active Directory schema extensions for Cisco Unity were not changed for Cisco Unity 7.0(2). If you are upgrading from Cisco Unity 5.0 to version 7.0(2), you do not need to extend the Active Directory schema. If you are upgrading from Cisco Unity 4.2 or earlier, you do need to extend the Active Directory schema.

Upgrade Always Requires Upgrade Purchase, Sometimes Requires Upgrade License

Upgrading to Cisco Unity 7.0 requires that you purchase an upgrade regardless of the version from which you are upgrading. However, you are required to register the upgrade and install a new license file only if you are upgrading from Cisco Unity 4.x or earlier to Cisco Unity 7.0. If you are upgrading from Cisco Unity 5.0 to 7.0, you are not required to register the upgrade or to install a Cisco Unity 7.0 license file.

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

When you upgrade from Cisco Unity version 4.0(2) or 4/0(1), 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.


Note The following links go to Release 5.x versions of the guide; all 5.x content applies to version 7.x as well.


System Administration Guide for Cisco Unity Release 5.x (With IBM Lotus Domino) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/administration/guide/dom/5xcusagdx.html.

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/administration/guide/ex/5xcusagex.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.


Note The following links go to Release 5.x versions of the guide; all 5.x content applies to version 7.x as well.


System Administration Guide for Cisco Unity Release 5.x (With IBM Lotus Domino) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/administration/guide/dom/5xcusagdx.html.

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/administration/guide/ex/5xcusagex.html.

Limitations and Restrictions

Cisco Unity with Exchange: Alternate Extensions Page Generates a DCOM Error After the Password Is Changed on the UnityMsgStoreSvc Account

After a change has been made to the password on the account that Cisco Unity Message Store Services log on as (typically UnityMsgStoreSvc, although the actual account name may differ), Cisco Unity may display a DCOM error and fail to display the Alternate Extensions page for subscribers when administrators attempt to browse to this page in the Cisco Unity Administrator.

To resolve this issue, you must update Component Services with the new password. Do the following procedure.

To Update the UnityMsgStoreSvc Account Password in Component Services


Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Administrative Tools > Component Services.

Step 2 In the right pane, expand Component Services > Computers > My Computer > COM+ Applications.

Step 3 Right-click Cisco Unity and click Properties.

Step 4 Click the Identity tab.

Step 5 Enter and confirm the new password.

Step 6 Click OK to save the changes, then close the Component Services window.

Step 7 If the Cisco Unity Administrator is open, close it.

Step 8 Open the Cisco Unity Administrator and browse to a Subscriber > Alternate Extensions page. The Alternate Extension page should display correctly.


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.

First Subscriber to Call Cisco Unity After Restart Hears Delay Before First Prompt

The first subscriber to call Cisco Unity after the software has been restarted may hear several seconds of silence before Cisco Unity plays the first prompt. Subscribers making subsequent calls do not experience the delay. The silence occurs while Cisco Unity loads the conversations that are configured for the system; the length of the delay depends on how many conversations are in use on the system.

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

To configure Message Monitor, you create an application user for the Phone View features in Cisco Unified Communications Manager, and associate subscriber devices with the application 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 the Cisco Unity Administrator.

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

Message Monitor Delay Before Playing Subscriber Greeting Is Reduced

When a call is forwarded to the mailbox of a subscriber who has Message Monitor enabled, the delay before Cisco Unity plays the subscriber greeting has been reduced. However, there is a delay of 3 to 4 seconds before Cisco Unity plays the greeting.

Remote Desktop

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 (a Cisco Unity server, a failover server, a voice-recognition 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/go/bugs.)

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 numbers 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 7.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 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 on subscriber workstations to record and play messages with Cisco Unity ViewMail for Microsoft Outlook is not supported.

Caveats

This section lists any Severity 1, 2, and 3 caveats in this release.

You can find the latest caveat information for Cisco Unity version 7.0(2)—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 Release 7.0(2) only. Refer to the release notes of the applicable version for caveat information for earlier versions of Cisco Unity. Release notes for all versions of Cisco Unity are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.

Open Caveats—Release 7.0(2)

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

Table 6 Cisco Unity Release 7.0(2) Open Caveats 

Caveat Number
Component
Severity
Description

CSCse06229

conversations

3

Routing rule to subscriber system transfer causes Unity to hang up

CSCse46251

conversations

3

CSSS:fails to address to remote subscriber within defined CSSS

CSCse90932

conversations

3

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

CSCsh10926

conversations

3

Phrase server initialization performance needs improvement

CSCsj15242

conversations

3

System Xfer Conv doesn't prompt when invalid # dialed

CSCso28123

conversations

3

Unity repeats option to record message

CSCsi00810

core

3

Incorrect message notification data for some scenarios.

CSCsk14746

core

3

Notifications continue after sub deleted until Notifier restarted

CSCsm55543

core

3

CPCA unable to login, cannot contact server, web Status Montior fails

CSCso07497

core

3

Unity 5.0.1 Syscheck does not warn to disable CSA

CSCso10811

core

3

Unity Message Store Configuration Wizard fails to set homeserver

CSCso38413

core

3

Switch ID Info in Notifier Diagnostics Is Misleading or Missing

CSCso57982

core

3

ADSchemaSetup implies errors when group access is checked

CSCsk26365

dialogic

3

RMM: Num of rings settings does not take effect on phone 6

CSCsm21636

documentation

3

Rolling Upgrade Document Incomplete and Misleading

CSCsb75255

dommessaging

3

DOM: MWIs sometimes do not resynch after Domino server back online

CSCse48630

dommessaging

3

Domino - Subscriber hears this message is no longer available

CSCse54029

dommessaging

3

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

CSCse54039

dommessaging

3

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

CSCsi81757

dommessaging

3

Dom: NDRs are not forwarded to Unaddressed Messages list

CSCsd60682

ducs

3

Dom: Domino email containing 'twisties' results in failsafe on playback

CSCsq05129

exchvoicegateway

3

IVC Exceptions cause entire process to hang

CSCsl85185

exdirconnector

3

UPN Fixup should only look to local domain

CSCsm03671

exdirconnector

3

Show Hidden Objects reg key ignored and then deleted on reboot

CSCsh81214

exmessaging

3

UMR - Doh session cycling not observed

CSCsi44475

exmessaging

3

Exchange 2007: Transport rules aren't applied to Unity voicemails

CSCsd02261

failover

3

AvCsGateway errors during failover config, AvCsMgr fails to start

CSCsq06794

localization

3

The same prompt plays after automatic playback of messages after sign-in

CSCsg27013

messagemonitor

3

MM:When pressing "Ask" diags show "Take_Call"

CSCsk16674

messagemonitor

3

MM works even after removing phone frm CTI phn access user in CCM

CSCsi77374

mobilemessage

3

Unity Mobile Messaging Cannot Handle Spaces

CSCsg09004

pca

3

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

CSCsj15517

pca

3

PCA: TRaP playback fails when Lotus Notes on same computer

CSCsk21510

reports

3

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

CSCsf04733

sa

3

With minimal permissions msExchHideFromAddressLists should be grayed out

CSCsi31263

sa

3

SA:using server IP, seeing ...not authorized... error

CSCsi56059

sa

3

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

CSCsm65412

sa

3

Delete of subscriber should succeed regardless of MWI reset result

CSCsq06780

sa

3

Alternate extension setup based on CPID is not working.

CSCsq81915

sa

3

Alternate Extension "Learning" can break cross box login/transfer

CSCsj83395

setup

3

Setup - May not replace all files in \ Windows\System32 directory

CSCsl29451

setup

3

Ex2007:script fails when run in domain other than Unity domain

CSCso38223

setup

3

Upgrade of SQL Weekly/Nightly Backup Jobs Causes Upgrade To Fail

CSCsh32681

telephony

3

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

CSCsg23521

upgrade

3

ES installer fails to replace/upgrade specific files

CSCsd71523

utilities

3

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

CSCsd98936

utilities

3

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

CSCse12359

utilities

3

PW: Permissions Wizard does not ensure vm interop applied.

CSCse78060

utilities

3

Unity and Locations OUs created under domain root by Report mode

CSCsg27007

utilities

3

UDT: need mAcro trace option for Message Monitor

CSCsi39962

utilities

3

SECURE: GSM does not delete Trusted Internet contacts

CSCsl32654

utilities

3

PDL Builder does not allow non-ENU characters

CSCsl80617

utilities

3

Uninstall fails to handle CsDomInteropGty service

CSCsm35827

utilities

3

Mail sent to SMTP Address by EMS is garbled

CSCsm69361

utilities

3

New Unity Status Monitor utility has mem leak

CSCsg72153

viewmail

3

TRaP causes Event Viewer warnings on client

CSCsi39378

viewmail

3

Forward/Reply w/ voice actions missing in Outlook 2k7.

CSCsk15978

vml

3

VML: Wrapping text in VML menu results in msg info not being displayed

CSCsq37532

vmws

3

VMWS Setup fails if Unity is not running

CSCsq37556

vmws

3

VMWS Setup fails if Unity is not the active server

CSCsq37567

vmws

3

CiscoUnity_Ruler warning in application log after running VMWSSetup

CSCsm33672

voicecsa

3

CSA - Uninstalling enables Windows Firewall breaking Unity Failover7.0

CSCsj08463

vui

3

SC - Send Msg. Special delivery options not available with Standard Send

CSCsj17494

vui

3

SC - Streamline Send - Re-Record SC defined incorrectly

CSCsj17510

vui

3

SC - Streamline Send - Add Name SC defined incorrectly

CSCsj17531

vui

3

SC - Standard Send Menu SC to review message defined incorrectly

CSCsj17539

vui

3

SC - Send Msg. change addressing not available with Standard Send

CSCsj17546

vui

3

SC - Streamline Send - Review Message Recipients, no SC.

CSCsj17552

vui

3

SC - Standard Send - Review Message Recipients, no SC.

CSCsj17561

vui

3

SC - Receipt after message menu no SC to play orginal message

CSCsj17563

vui

3

SC - Forward Message, no SC to record introduction

CSCsj17569

vui

3

SC - Msg Playback / After Msg Menu, SC to repeat msg. defined incorretly

CSCsj17573

vui

3

SC - DCR Welcome back menu has no spoken commands

CSCsj82882

vui

3

VUI - Voice Recognition offered to g729 calls but is not supported.


Resolved Caveats—Release 7.0(2)

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

Table 7 Cisco Unity Release 7.0(2) Resolved Caveats 

Caveat Number
Component
Severity
Description

CSCsk67827

telephony

1

MWI's may fail for PIMG integrations greater than the first integration.

CSCsj03459

conversations

2

Streamlined Conversations are inconsistent

CSCsk51239

conversations

2

Convr-SubSendMsg: STD send msg style (enabled), not being enforced.

CSCsk88930

conversations

2

Duplicate Alias can cause system to become unresponsive

CSCsl80928

conversations

2

Duplicate aliases may cause Unity to become unresponsive

CSCso69772

conversations

2

When sending message, if hang up after continuing, is not delivered

CSCsl56254

core

2

GC total resync should sync typically most important objects first

CSCsj43233

exmessaging

2

Ex2000/2003: MAPI address book providers Global Catalog failover broke

CSCsj63611

exmessaging

2

ExchangeMonitor falsely detects mailbox move during CUBI import

CSCsj29095

ossetup

2

Server 2003 2.2.0.2 PCD Erases drives without confirmation

CSCsj90603

sa

2

Win2K3+DEU MUI: UNITY SA inaccessible - Error msg hr=0x80042506.

CSCsk08785

sa

2

ML:msg to non-ENU PDLs not delivered

CSCef69851

telephony

2

TSP returns CALL_MWI_FAIL for nonexistant DNs with CCM 4.0(X)

CSCsj57251

telephony

2

Errors during Play Speed Adj with g.711 to g.729a conversion

CSCsk30869

telephony

2

SCCP constant re-registration causes network connectivity issues

CSCsk33686

telephony

2

RFC2833 digits from secure SIP phones not working on Unity

CSCsk73751

telephony

2

Unity should be able to record mismatch packetization size

CSCeb66120

tsp

2

Unity may not disconnect call when call preservation occurs

CSCec60226

tsp

2

No audio from Unity when skinny messages are fragmented

CSCed02520

tsp

2

DTMF is passed during a hold scenario with Unity

CSCsj97835

upgrade

2

"Failed to get resource from LicFileWizRes" on upgrade

CSCsk27633

utilities

2

Upgrades fail after DIRT restore with a new server name

CSCsk90629

viewmail

2

VMO prevents Outlook 2007 from starting

CSCsk44048

amis

3

Unity takes long time to Sync with AMIS MailBox

CSCsk44675

amis

3

Multithreading issues with AMIS conversations with Domino

CSCso63748

amis

3

Dom: AMIS recipients get multiple copies of message

CSCsj38740

bridge

3

imported users are showing up in address book when they shouldn't be

CSCsl87943

bridgeconnector

3

Malformed directory message causes CsBridgeConnector to stop working

CSCsd54083

conversations

3

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

CSCsi88008

conversations

3

AvConcCVMENU006.wav causes call to terminate prematurely

CSCsk06734

conversations

3

French Canadian give wroung time between 01 and 09 min

CSCsk14879

conversations

3

Failsafe heard after hitting message locator and then addressing a msg

CSCsk56884

conversations

3

Subscriber sign in should respect system first & inter digit dtmf delays

CSCsl24837

conversations

3

SubSign In from personal greeting logic is incorrect.

CSCsl32479

conversations

3

Secure: voicemail reply to email is not encrypted

CSCsl40212

conversations

3

Secure Msg:Fwded msgs' introduction is not encrypted .

CSCsl90428

conversations

3

ERROR_EVENT not generated if CDE diags not enabled

CSCso53637

conversations

3

TUI-Infinite Loop condition in streamline send with null recording

CSCso74325

conversations

3

TUI-Can not change fax delivery number in send fax conversation

CSCsg76524

core

3

BusinessLogicManagerSvr.dll violates DLLMain rules and causes deadlock

CSCsi61540

core

3

Unity Notification failure with Domino integration

CSCdz19265

database

3

DOM: GrantUnityAccess does not list associations correctly

CSCsd44843

database

3

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

CSCsj70905

database

3

Fresh install may fail if running on a non-clean system

CSCsj80282

database

3

User name with Apostrophe will generate error

CSCsj92828

database

3

Unity 4.x to 5.0.1 upgrade is failing though server not renamed

CSCsk67852

database

3

XferString not being updated correctly

CSCsm97318

database

3

ReportDb_log.ldf or TempLog.ldf fill disk, may cause failsafe

CSCso20141

database

3

Unity Delivery Locations dissapear on Secondary FO on change

CSCsj20642

dialogic

3

PIMG: UTIM does not allow 4-span TIMG for 96 ports

CSCsj29059

dialogic

3

PIMG: Clipping at beginning of prompt playback after DTMF

CSCsk03572

dialogic

3

Unity lets you add PIMG ports if you dont have any available in license

CSCsk70045

documentation

3

Dom: PDL is import only in the SA

CSCsl17919

documentation

3

Alt extension is blank on saweb when changing the UnityMsgstoreSvc cred.

CSCsl39682

documentation

3

Missing note in global subscriber manager delete/move wizard document

CSCsm35904

documentation

3

COM security setting on Permission wizard help is incorrect.

CSCsm62612

documentation

3

Unity System Requirements for Domino mailstore don't list AIX versions

CSCso54487

documentation

3

Cisco Unity TomCat Apache Vulnerability

CSCsi92237

dommessaging

3

Dom: TUI does not announce NDRs

CSCsf06231

exchvoicegateway

3

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

CSCsj29997

exchvoicegateway

3

Secure Msg: vc inbound encrypt fails due to server name case

CSCsk58626

exchvoicegateway

3

VPIM: voice connector fails to process inbound msg with many recipients

CSCsl79289

exmessaging

3

MWI lengthy after Exchange Cluster Failover

CSCsm09325

exmessaging

3

Unnecessary Drafts folder in unexpected language is created in Outlook

CSCsm27607

exmessaging

3

JPN: Message Locator cannot search messages

CSCsi24340

failover

3

Gui failed to display left tabs if the SA is open from the Inactive SERV

CSCsi50517

failover

3

Failover: SQL replication jobs can fail and provide no warning

CSCsg45153

import

3

Bulk Import CSV ZERO_KEY_RULE does not Attempt Transfer to Callhandler

CSCso68194

import

3

CUBI does not set PAGER1 or VMI _TEXT_AFTER_DIAL_DIGITS

CSCsl23322

localization

3

JPN: wrong translation on permission wizard

CSCsq01991

mediamaster

3

Options in Media Master is changed after CPCA logoff and login.

CSCdz87439

miu

3

SIP/CCM dual: if one CCM cluster down, Unity wont start

CSCeb25215

miu

3

The call not go to Unity VMailbox when XferToVM

CSCec03487

miu

3

CiscoUnity_TSP reports incorrect device/port #s in app. log msgs.

CSCse04439

mobilemessage

3

MobileMessage: Windows 2003 Permissions Prevent DCOM Access

CSCsi96323

ossetup

3

Cisco Provided OS does not recognize 4 GB of RAM in MCS Server

CSCsj81705

ossetup

3

New Zealand DST may cause message time stamps to be incorrect

CSCsd39975

pca

3

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

CSCsi73888

pca

3

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

CSCsj81527

pca

3

Unity Inbox: time stamp adjustment not valid for DST change in 2007 NZ

CSCsj81671

pca

3

JVM version installed is not compliant with 2007 DST changes NewZealand

CSCsk79469

pca

3

DST: Venezuela

CSCsm32946

pca

3

DST Australia Unity: Update for Unity

CSCsi98311

pimg

3

PIMG: Notifier should disable port when PIMG unavailable

CSCsj76543

pimg

3

No audio if SIP call not cleared correctly, UDP port re-used

CSCsc86904

sa

3

WS03: Cannot log back in to SA after timeout

CSCsh54775

sa

3

SA: Schedules other than 'Always' don't work

CSCsk06752

sa

3

SA does not update CallHandler Message Recipient

CSCsl32525

sa

3

Ex2007:PDLs w/non-ENU characters fail to create valid SMTP addr

CSCsm17318

sa

3

Unity can't set Continue adding names after each addressee from Web SA

CSCse87434

setup

3

SETUP: Buffer overflow and crash when PATH is too long

CSCsi00319

setup

3

UTIM should check for TFTP.EXE on Windows 2k3 when enable security mode

CSCsk33981

setup

3

Dom: Upgrade changes SubscriberType of default accounts

CSCsj49463

tbd

3

Text pager notification doesn't send intial message at correct time.

CSCef10291

telephony

3

CiscoUM-TSP - API func calls into TSP outside of TAPI do not diag

CSCef36843

telephony

3

Skinny TSP does not recover/reset connection correctly

CSCef79341

telephony

3

AvAudio - Ports locks when media stream stops (i.e. Unity on hold)

CSCsb33436

telephony

3

With g.729 the packet preceding the CN packet is not always transmitted

CSCsd71904

telephony

3

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

CSCsi65508

telephony

3

Unity TSP port failback detection fails

CSCsi85034

telephony

3

Extension remapping fails for calling # with SIP Fwd'd calls

CSCsj13401

telephony

3

Unity Failover results from OpenSSL errors

CSCsj63332

telephony

3

UTIM - Option to add TIMG missing from integration menu

CSCsl23106

telephony

3

blind transfer to RNA fails with latest CCME build

CSCsm11043

telephony

3

SIP/PIMG needs configurable answer delay

CSCsm73465

telephony

3

Secure messages forwarded twice have static via SIP integations

CSCsm79100

telephony

3

MIU: Unity fails to tear down PIMG session properly - intermittently.

CSCso19301

telephony

3

RFC2833 redundant marker bit causes redundant digits

CSCdw49611

tsp

3

Transferring call to VM of an ext. plays the wrong source name.

CSCea19653

tsp

3

TSP: Unity should not record when on hold, empty messages result

CSCea35850

tsp

3

Unity RTP stream has inherent jitter

CSCeb29226

tsp

3

AvcsMgr on Unity 2.4 does not start with TSP 7.0(2)

CSCeb76227

tsp

3

Interdigit timeout-caused MWI errors unclear

CSCeb79047

tsp

3

Unity TSP traces indicate on-hook received instead of sent

CSCec22397

tsp

3

Failover: with secondary active, easy message access doesnt work

CSCec26437

tsp

3

KAs sent 15 seconds regardless of Station Keep Alive Interval

CSCec54161

tsp

3

Unity disconnects call and delivers message when Hold tone is played

CSCec72157

tsp

3

when using DNS names, Unity can never connect to CCM down at startup

CSCec79795

tsp

3

TSP - Do not transfer while Unity is on hold with MOH

CSCso00238

umr

3

UmrSynchSvr process leaks Notes handles in Unity for Domino

CSCsm15661

upgrade

3

Upgrade from 4.x may cause Std & Alt Transfer rules to change

CSCsd52601

utilities

3

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

CSCsd53143

utilities

3

CUBI:does not modify DISPLAY_NAME value

CSCsi68156

utilities

3

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

CSCsj21911

utilities

3

Bulk Edit will not allow subscribers language to be changed

CSCsk60527

utilities

3

AST does not set correct key for Spoken Commands

CSCsm15882

utilities

3

Settings in SubscriberEx table not migrated on moves with GSM

CSCsm44022

utilities

3

DBWalker incorrectly detects restriction table violation

CSCsm53675

utilities

3

DBwalker should check for SchemaMajorVersionSchemaMinorVersion in ser tb

CSCso15730

utilities

3

BulkEdit may crash when modifying subscriber TUI passwords

CSCso34515

utilities

3

DBWalker v4.0.52 gets run time 3704 error with Unity v4.0.5 to v4.2

CSCsl00137

viewmail

3

ViewMail for Outlook: No audio devices of the PC in playback options

CSCsl59482

viewmail

3

VMO reports errors when form is published by not locally installed

CSCsj29032

vml

3

VML: Msg from network blind address displays as unknown caller

CSCsk13091

vml

3

VML: MM: Phone View inoperable for DNs of 10 digits or longer

CSCsj17518

vui

3

SC - Sub Manin Menu, SC to transfer to ext. defined incorrectly


Documentation Updates

New and Changed Content

The cross-references below go to items in the "New Functionality" and "Changed Functionality" sections of these release notes. Individual items contain the applicable information about configuring and using the features, including any required procedures.

New Functionality Items

Alternate Extension "Learning"

Cisco Unity Bulk Import Wizard and Bulk Edit Utility Enhancements

Cisco Unity Conversation Enhancements

Cisco Unity Failover Enhancements

Cisco Unity with Exchange: VPIM Delivery Location Configuration Options

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

Media Master Can Be Disabled in the Cisco Unity Assistant Web Tool

MWI Constant Message Count

New Port Status Monitor

Subject Lines of Voice Messages Can Be Configured

UTIM

Changed Functionality Items

Alternate Device Number Field Validates Against Alt Ext Restriction Table

Apache Tomcat Sample Applications Contain Security Vulnerabilities

Automated Attendant Search Scope Setting Moved to the Cisco Unity Administrator

Cisco Unity Conversation Changes

Cisco Unity Server Licensing

Cisco Unity with Domino: Anonymous Logon No Longer Required for TRaP

Cisco Unity with Domino: Interop Gateway Service

Cisco Unity with Domino: Serviceability Improvements

Cisco Unity with Domino: Storage of Notes Password on the Cisco Unity Server

Defaults for Addressing Search Scopes

Default for Allowing Subscribers to Create Alternate Extensions

Encryption Algorithm for Phone Password

Java SDK Upgraded

Remote Serviceability Kit Updates

Support for Up to 200 Voice Messaging Ports

Errors

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


Note For guides that were not updated for 7.x (see the "Not Updated" column in Table 1), the 5.x documentation applies to Release 7.x.


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

Cisco Unity Integration Guides for Cisco Unity 5.x: Creating a New Integration

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

Maintenance Guide for Cisco Unity Release 5.x: Excluding Cisco Unity Directories from Scanning

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with IBM Lotus Domino): Configuring the Interop Gateway

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with Microsoft Exchange): Determining the Domain Name

Networking Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Configuring the Interop Gateway

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Domain Name Requirements

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Obtaining and Installing Cisco Unity License Files

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Extending the Active Directory Schema for Cisco Unity

System Administration Guide for Cisco Unity Release 5.x and Interface Reference Guide for the Cisco Unity Administrator: Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password

System Administration Guide for Cisco Unity Release 5.x: Phone View Features

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Enabling Alternate Greeting Notices

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Specifying How Cisco Unity Behaves When Subscribers Have Their Alternate Greeting Enabled

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange) and Integrated Mailbox Configuration Online Help: Using Integrated Mailbox Configuration to Create Individual Subscriber Accounts

Troubleshooting Guide for Cisco Unity Release 5.x: Cisco Unity Services and Their Functions

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

Added June 2, 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 System Requirements for Cisco Unity Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/requirements/7xcusysreq.html.

Cisco Unity Integration Guides for Cisco Unity 5.x: Creating a New Integration

For integrations that support more than 72 voice messaging ports, in the "Creating a New Integration" section in the Cisco Unity integration guides, the procedure "To Adjust the Advanced Settings for 72 or More Voice Messaging Ports" is incorrect. Use the following procedure instead.

To Adjust the Advanced Settings for 72 or More Voice Messaging Ports


Step 1 If the Cisco Unity server is not running Windows Server 2003, you do not have to do this procedure.

If the Cisco Unity server is running Windows Server 2003, on the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity Tools Depot.

Step 2 In the Tools Depot window, in the left pane, expand Administration Tools and double-click Advanced Settings Tool.

Step 3 In the Cisco Unity Advanced Settings window, in the left pane, click Messaging - 72 or More Voice Ports - Enable Low-Fragmentation Heap.

Step 4 In the New Value drop-down box, click 1 and click Set.

Step 5 When prompted that the value has been set, click OK.

Step 6 Close the Tools Depot window.

Step 7 Restart the Cisco Unity server.


Failover Configuration and Administration Guide for Cisco Unity Release 5.x: Intervals for Failover and Failback

Added October 27, 2009

In the "About Cisco Unity Failover" chapter of the Failover Configuration and Administration Guide for Cisco Unity Release 5.x, Table 4-4, "Interval for Failover," indicates that the secondary server will begin taking calls:

Immediately after a manual failover.

Immediately after failure of the AvCsMgr service on the primary server.

Immediately after the inactive secondary server answers a call.

However, testing shows that the secondary server answers the first incoming call but does not answer subsequent calls until failover is complete and the secondary server is the active server. The amount of time required for the secondary to start answering all calls varies, but can be over a minute.

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

Added June 26, 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" appendix of the Failover Configuration and Administration Guide for Cisco Unity Release 5.x, some descriptions of disconnection behavior when the Exchange or Domino server is disconnected from the network are partially incorrect.

In the bulleted items that begin "Subscribers homed on the same Cisco Unity server can leave messages for each other...," the phrase "...or logging on to Cisco Unity" is incorrect. When the Exchange or 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.

Maintenance Guide for Cisco Unity Release 5.x: Excluding Cisco Unity Directories from Scanning

In the "Scanning for Viruses" section in the "Routine and Scheduled Maintenance on the Cisco Unity Server" chapter, the subsection "Excluding Cisco Unity Directories from Scanning" says to exclude from virus scanning only the directory in which Cisco Unity is installed (and all subdirectories). To improve Cisco Unity performance and reliability, we recommend that you exclude the directories listed below from virus scanning.

For all configurations

The directory in which Cisco Unity is installed (Commserver by default), and all subdirectories.

The directory that contains the files UnityDB.mdf and UnityDb_log.ldf.

The directory specified in the Temp system variable for the message store services account (when Exchange is the message store) or the directory and message store services account (when Domino is the message store. (To find this directory, log on as the applicable account. Open a command-prompt window, and run the set temp command.)

When Exchange Server 2003 is installed on the Cisco Unity server

Drive M, the virtual share for Exchange, if you have added the registry key that is required to make drive M visible.

The directories that contain Exchange storage group data.

When the Cisco Unity Voice Connector is installed on the Cisco Unity server, the directory where the Cisco Unity Voice Gateway is installed (Voicegateway by default), and all subdirectories.

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with IBM Lotus Domino): Configuring the Interop Gateway

In the "To Configure the Interop Gateway" procedure in the "Configuring the Interop Gateway" section in the "Setting Up Cisco Unity and the Bridge for Networking" chapter, Step 6 is incorrect. You no longer have the option to choose the local system account; instead, choose the services account. Enter the name of the account in the format <DomainName>\<UserName>.

Beginning with Cisco Unity 7.0, when Domino is the message store, we require the Interop Gateway service to log on by using the Cisco Unity services account. (This is the services account that you selected in the Cisco Unity Permissions wizard.)

Networking Guide for Cisco Unity Bridge Release 3.1 (For Cisco Unity Release 5.x with Microsoft Exchange): Determining the Domain Name

Added September 12, 2008

The "Determining the Domain Name" section in the "Setting Up Cisco Unity and the Bridge for Networking" chapter omits some information related to determining the domain name for Bridge Networking when Cisco Unity is already configured to use VPIM Networking.

If VPIM Networking is already configured, choose a domain name for Bridge Networking that is different than the domain in use for VPIM Networking, and is not a subset of the domain name used for VPIM Networking. For example, if the domain configured for VPIM Networking is cisco.com, do not use a name like bridge.cisco.com or bridge-cisco.com for Bridge Networking. However, if you are using vpim.cisco.com for VPIM Networking, you could use the name bridge.cisco.com or bridge-cisco.com for Bridge Networking.

Networking Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Configuring the Interop Gateway

In the "To Configure the Interop Gateway" procedure in the "Configuring the Interop Gateway" sections of the "AMIS Networking" and "VPIM Networking" chapters, Step 6 is incorrect. You no longer have the option to choose the local system account; instead, choose the services account. Enter the name of the account in the format <DomainName>\<UserName>.

Beginning with Cisco Unity 7.0, when Domino is the message store, we require the Interop Gateway service to log by on using the Cisco Unity services account. (This is the services account that you selected in the Cisco Unity Permissions wizard.)

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Domain Name Requirements

Added September 12, 2008

In the "Domain Name Requirements" section of the "VPIM Networking" chapter, the following requirement is omitted:

If Bridge Networking is already configured, choose a domain name that is different than the domain in use for Bridge Networking, and is not a subset of the domain name used for Bridge Networking. For example, if the domain configured for Bridge Networking is cisco.com, do not use a name like vpim.cisco.com or vpim-cisco.com for VPIM Networking. However, if you are using bridge.cisco.com for Bridge Networking, you could use the name vpim.cisco.com or vpim-cisco.com for VPIM Networking.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With IBM Lotus Domino): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Added April 9, 2009

The "Cisco Unity 7.x Documentation Set" section incorrectly implies that all content in the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x can be used as written for upgrades from Cisco Unity 5.x to 7.x.

This section lists the tasks that you can omit as you follow the "Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" to upgrade a 5.x system without Cisco Unity failover or to upgrade a 5.x system with failover configured:

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version Without Failover

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version With Failover Configured

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version Without Failover

When you are upgrading a Cisco Unity 5.x system without failover to Cisco Unity 7.x, omit the following tasks:

1. Obtain the license file(s) for the upgrade to Cisco Unity 5.x.

(Upgrading from Cisco Unity 5.0 to 7.0 requires that you purchase an upgrade, but you are not required to register the upgrade or install a new license file.)

2. Acquire the upgrade to IBM Lotus Domino Unified Communications (DUC) for Cisco version 1.2.3 from IBM Lotus.

4. If the Cisco Unity server is a member server in a Windows NT domain: Remove the Cisco Unity server from the Windows NT domain and make it a domain controller or a member server in a Windows Server 2003 or Windows 2000 Server domain.

12. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4) and Cisco Unity is integrated with Cisco Unified CM Express or with a Cisco Unified CM cluster that includes a Cisco Unified CM Express server: Designate the phone system as Cisco Unified CM Express.

17. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4), and if Cisco Unity uses Intel Dialogic D/120JCT-Euro Rev 2 voice cards to integrate with a circuit-switched phone system: Install additional Dialogic .prm files.

19. Optional: Do the following tasks to upgrade from one supported version of Domino to another.

20. Do the following tasks to upgrade DUC for Cisco software.

21. Optional: Upgrade Notes on the Cisco Unity server.

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version With Failover Configured

When you are upgrading a Cisco Unity 5.x system with failover configured to Cisco Unity 7.x, omit the following tasks:

1. Obtain the license file(s) for the upgrade to Cisco Unity 5.x.

(Upgrading from Cisco Unity 5.0 to 7.0 requires that you purchase an upgrade, but you are not required to register the upgrade or install a new license file.)

2. Acquire the upgrade to IBM Lotus Domino Unified Communications (DUC) for Cisco version 1.2.3 from IBM Lotus.

4. If the Cisco Unity server is a member server in a Windows NT domain: Remove the Cisco Unity server from the Windows NT domain and make it a domain controller or a member server in a Windows Server 2003 or Windows 2000 Server domain.

16. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4), and if Cisco Unity uses Intel Dialogic D/120JCT-Euro Rev 2 voice cards to integrate with a circuit-switched phone system: Install additional Dialogic .prm files.

21. Optional: Do the following tasks to upgrade from one supported version of Domino to another.

22. Do the following tasks to upgrade DUC for Cisco software.

23. Optional: Upgrade Notes on the Cisco Unity server.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version

Added April 9, 2009

The "Cisco Unity 7.x Documentation Set" section incorrectly implies that all content in the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x can be used as written for upgrades from Cisco Unity 5.x to 7.x.

This section lists the tasks that you can omit as you follow the "Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" to upgrade a 5.x system without Cisco Unity failover or to upgrade a 5.x system with failover configured:

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version Without Failover

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version With Failover Configured

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version Without Failover

When you are upgrading a Cisco Unity 5.x system without failover to Cisco Unity 7.x, omit the following tasks:

1. Obtain the license file(s) for the upgrade to Cisco Unity 5.x.

(Upgrading from Cisco Unity 5.0 to 7.0 requires that you purchase an upgrade, but you are not required to register the upgrade or install a new license file.)

3. If the partner Exchange server is running Exchange 5.5: Upgrade Exchange.

4. If SMTP Networking is configured: Migrate to VPIM Networking.

9. Update the Active Directory schema.

10. Optional: Create new Active Directory accounts for Cisco Unity installation and services.

11. If you downloaded the latest version of the Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity DVD.

12. If Cisco Unity is configured to automatically create Bridge or VPIM subscribers in a different AD location than regular subscribers: Rerun the Permissions wizard, and specify the domain and location on the Set Active Directory Containers for New Objects page.

15. If Exchange 2000 System Manager (not the full version of Exchange 2000) is installed on the Cisco Unity server: Upgrade to Exchange 2003 System Manager.

18. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4) and Cisco Unity is integrated with Cisco Unified CM Express or with a Cisco Unified CM cluster that includes a Cisco Unified CM Express server: Designate the phone system as Cisco Unified CM Express.

23. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4), and if Cisco Unity uses Intel Dialogic D/120JCT-Euro Rev 2 voice cards to integrate with a circuit-switched phone system: Install additional Dialogic .prm files.

Task List for Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version With Failover Configured

When you are upgrading a Cisco Unity 5.x system with failover configured to Cisco Unity 7.x, omit the following tasks:

1. Obtain the license file(s) for the upgrade to Cisco Unity 5.x.

(Upgrading from Cisco Unity 5.0 to 7.0 requires that you purchase an upgrade, but you are not required to register the upgrade or install a new license file.)

3. If the partner Exchange server is running Exchange 5.5: Upgrade Exchange.

4. If SMTP Networking is configured: Migrate to VPIM Networking.

9. Update the Active Directory schema.

10. Optional: Create new Active Directory accounts for Cisco Unity installation and services.

11. If you downloaded the latest version of the Permissions wizard from CiscoUnityTools.com, install and run that version. Otherwise, run the version that appears in the Utilities\PermissionsWizard directory on the shipping Cisco Unity DVD.

12. If Cisco Unity is configured to automatically create Bridge or VPIM subscribers in a different AD location than regular subscribers: Rerun the Permissions wizard, and specify the domain and location on the Set Active Directory Containers for New Objects page.

15. If Exchange 2000 System Manager (not the full version of Exchange 2000) is installed on the Cisco Unity server: Upgrade to Exchange 2003 System Manager.

22. If you are upgrading from Cisco Unity 4.0(1) through 4.0(4), and if Cisco Unity uses Intel Dialogic D/120JCT-Euro Rev 2 voice cards to integrate with a circuit-switched phone system: Install additional Dialogic .prm files.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x: Obtaining and Installing Cisco Unity License Files

In the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x, the sections "Obtaining Cisco Unity License Files" and "Upgrading and Configuring Cisco Unity Software" imply that you always need to obtain and install new license files during an upgrade to Cisco Unity 7.0. Note the following:

Upgrading from Cisco Unity 5.0 to 7.0 requires that you purchase an upgrade, but you are not required to register the upgrade or install a new license file.

Upgrading from Cisco Unity 4.x to 7.0 requires that you purchase an upgrade, register the upgrade, and install a Cisco Unity 7.0 license file. The upgrade license activates Cisco Unity 4.x licensed features on a Cisco Unity 7.0 system.

Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Extending the Active Directory Schema for Cisco Unity

In the "Upgrading Cisco Unity 4.x Software to the Shipping 5.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 5.x (With Microsoft Exchange), the "Extending the Active Directory Schema for Cisco Unity" section is incorrect. The section indicates that you must always extend the Active Directory schema when upgrading to a later version of Cisco Unity.

However, Active Directory schema extensions for Cisco Unity were not changed for Cisco Unity 7.0(2). If you are upgrading from Cisco Unity 5.0 to version 7.0(2), you do not need to extend the Active Directory schema.

If you are upgrading from Cisco Unity 4.2 or earlier to version 7.0, you must extend the schema with Cisco Unity 7.0 schema extensions.

System Administration Guide for Cisco Unity Release 5.x and Interface Reference Guide for the Cisco Unity Administrator: Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password

Added September 12, 2008

In the "Allowing Subscribers to Access Cisco Unity by Phone Without Entering a Password" section in 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 and the "Subscriber Phone Password Page" section in the "Subscriber Settings" chapter of the Interface Reference Guide for the Cisco Unity Administrator, the note on security omits the following information:


Note This setting also affects phone-based visual clients, such as Phone View and Message Monitor; if subscribers are using these clients, we recommend that you do not allow them to access Cisco Unity by phone without entering a password.


System Administration Guide for Cisco Unity Release 5.x: Phone View Features

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 Release 5.x, the procedure "To Configure Cisco Unified Communications Manager for Phone View (Cisco Unified CM 5.x and Later)" is incorrect. Use the applicable procedure below instead, depending on the version of Cisco Unified CM:

To Configure Cisco Unified Communications Manager for Phone View (Cisco Unified CM 6.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 an application user account that will have access to all subscriber phones for Phone View:

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

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

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

d. Under Device Information, to the right of the Available Devices field, click Find More Phones.

e. On the Find and List Phones page, select the phones on which you want to enable Phone View and click Add Selected.

f. On the Application User Configuration page, confirm that the phones on which you want to enable Phone View appear in the Controlled Devices field so that the phones are associated with the application user.

For any phones that you selected in Step 3e. and that appear in the Available Devices field, select the applicable phones and click the Down arrow below the field to move the phones to the Controlled Devices field.

g. Under Permissions Information, click Add to User Group.

h. On the Find and List User Groups page, check the Standard CCM Admin Users check box and click Add Selected.

i. On the Application User Configuration page, click Save.

j. Under Application User Information, click Edit Credential.

k. On the Credential Configuration page, confirm that the User Must Change at Next Login check box is unchecked and click Save.

Step 4 Continue with the "To Enable Phone View on the Cisco Unity Server" procedure.


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


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 an application user account that will have access to all subscriber phones for Phone View:

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

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

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

d. Under Device Information, to the right of the Available Devices field, click Find More Phones.

e. On the Find and List Phones page, select the phones on which you want to enable Phone View and click Add Selected.

f. On the Application User Configuration page, confirm that the phones on which you want to enable Phone View appear in the Controlled Devices field so that the phones are associated with the application user.

For any phones that you selected in Step 3e. and that appear in the Available Devices field, select the applicable phones and click the Down arrow below the field to move the phones to the Controlled Devices field.

g. On the Application User Configuration page, click Save.

h. Click User Management > User Group.

i. On the Find and List User Groups, click Standard CCM Admin Users.

j. On the User Group Configuration page, click Add Application Users to Group.

k. On the Find and List Application User page, check the check box for the application user that you created in Step 3g.

l. Click Add Selected.

Step 4 Continue with the "To Enable Phone View on the Cisco Unity Server" procedure.


System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Enabling Alternate Greeting Notices

Added June 26, 2008

In the "Enabling Alternate Greeting Notices" section of the "Managing System-Wide Conversation Settings" chapter of the System Administration Guide for Cisco Unity Release 5.x, the procedure "To Enable Alternate Greeting Notices for a Cisco Unity Server (Voice Messaging Only)" is incorrect. Use the following procedure instead.

To Enable Alternate Greeting Notices for a Cisco Unity Server (Voice Messaging Only)


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

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

Step 3 In the Unity Settings pane, click Conversation—Alternate Greeting Notices (Exchange Only).

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

Step 5 When prompted, click OK.

Step 6 In the Unity Settings pane, click Conversation—Exclude All Receipts From Voice Mail Stack (Exchange Only).

Step 7 If the key is not present or is set to 0, skip toStep 8.

If the key is present and is set to 1, reset the key:

a. In the New Value List, click 0 and click Set.

b. When prompted, click OK.


Note Subscribers can receive alternate greeting notices only if they are able to access receipts. The alternate greeting notice feature does not work if the value of Conversation—Exclude All Receipts From Voice Mail Stack (Exchange Only) is set to 1.


Step 8 Click Exit.

Step 9 Restart the Cisco Unity software.


Note If you do not restart the Cisco Unity software when you enable or disable the feature, notices do not behave as expected.


Step 10 As applicable, repeat the procedure for each Cisco Unity server at your site.


Note For Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated.



System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Specifying How Cisco Unity Behaves When Subscribers Have Their Alternate Greeting Enabled

Added June 26, 2008

The "Specifying How Cisco Unity Behaves When Subscribers Have Their Alternate Greeting Enabled" section in 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 omits some information related to alternate greeting notices.

For more complete information, refer to the "Enabling Alternate Greeting Notices" section of the "Managing System-Wide Conversation Settings" chapter of the System Administration Guide for Cisco Unity instead. Also see the "System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange): Enabling Alternate Greeting Notices" section of these release notes for a corrected procedure.

System Administration Guide for Cisco Unity Release 5.x (With Microsoft Exchange) and Integrated Mailbox Configuration Online Help: Using Integrated Mailbox Configuration to Create Individual Subscriber Accounts

The System Administration Guide for Cisco Unity and Integrated Mailbox Configuration Online Help incorrectly indicate that the Integrated Mailbox Configuration wizard can be used when Cisco Unity is integrated with Cisco Unified Communications Manager version 4.1 or later. The supported versions of Cisco Unified CM for use with the Integrated Mailbox Configuration wizard are 4.1, 4.2, and 4.3 (including all maintenance releases on these branches, for example, 4.1(2) ).

Troubleshooting Guide for Cisco Unity Release 5.x: Cisco Unity Services and Their Functions

In the "Cisco Unity Services and Their Functions" appendix of the Troubleshooting Guide for Cisco Unity Release 5.x, the CuDohMgr service should be added with the following details:

Function: The CuDohMgr service provides access to the DOH for clients such as Cisco Personal Communications Assistant and Cisco Unity Administrator.

Logs on as: UnityMsgStoreSvc

Startup mode: Manual

Dependencies: MSSQLSERVER

Omissions

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


Note For guides that were not updated for 7.x (see the "Not Updated" column in Table 1), the 5.x documentation applies to Release 7.x.


Multiple Guides: SIP Integrations May Not Add a Pause for a Comma in a Dialstring

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

Networking Guide for Cisco Unity: Cross-Server Logon, Transfers, and Live Reply

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

Security Guide for Cisco Unity: Limitations of Secure Messaging

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

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

System Administration Guide for Cisco Unity: Phone View Features

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

Multiple Guides: SIP Integrations May Not Add a Pause for a Comma in a Dialstring

Added October 23, 2009

In multiple sections in several Cisco Unity guides, the following information was omitted:

When Cisco Unity is integrated with the phone system using SIP, the handling of a comma in the dialstring to add a pause is controlled by the SIP phone system or gateway, and in some cases the comma is ignored. This applies anywhere than you can specify dialstrings, for example, call handler transfer settings, alternate contact numbers, MWI settings for individual Cisco Unity subscribers, and message notification. You may be able to work around the problem by configuring the phone system or gateway to add a pause where necessary.

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

Added March 20, 2009

In the "Determining How Many Voice Messaging Ports Will Answer Calls" section in the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" chapter of 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 7.0.

c. Click Cisco Unity System Software.

d. In the All Releases section, expand 7.0, and click 7.0(2).

e. In the right pane, click CiscoUnity_7.0(2)_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_7.0(2)_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_7.0(2)_LotusNotes8.xSupport_ReadMe.txt, to the Commserver directory

Step 5 Delete the self-extracting EXE file.

Although you may safely delete the file CiscoUnity_7.0(2)_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"

Networking Guide for Cisco Unity: Cross-Server Logon, Transfers, and Live Reply

Added March 25, 2011

In the "Cross-Server Logon, Transfers, and Live ReplyCisco Unity" chapter in both the Exchange and Domino versions of the Networking Guide for Cisco Unity Release 5.x, http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html, a task and subtasks are missing from the following task lists:

"Task List: Enabling Cross-Server Logon"

"Task List: Enabling Cross-Server Transfer"

"Task List: Enabling Cross-Server Live Reply"

Do the following task and subtasks just before the test task:

If you configured the Cisco Unified CM service parameter "Display Original Calling Number on Transfer from Cisco Unity": Do the following tasks:

a. In Cisco Unified CM, configure a directory number (for example, on a CTI route point) for each Cisco Unity pilot number, and set the directory number to always forward into the Cisco Unity pilot number. For information on configuring a directory number, see the "Directory Number Configuration" chapter in the "Call Routing Configuration" part of the applicable Cisco Unified Communications Manager Administration Guide at http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

b. Configure a Forwarded Call routing rule on Cisco Unity to trigger on the directory number as the redirecting number, and send the call to the Opening Greeting. Put this routing rule at the top of the stack. For more information, see the "Creating and Modifying Call Routing Rules" section in the "Call Management Overview" chapter in the applicable version of 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.

c. When configuring cross-server dialing between servers, use the corresponding directory number as the pilot number for each remote Cisco Unity server.

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

Revised April 4, 2012

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 > Cisco Unity Version 7.0 > Cisco Unity System Software.

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

d. 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 > Cisco Unity Version 7.0 > Cisco Unity System Software.

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

d. 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 April 4, 2012

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 7.0 Engineering Special 19 (ES 19) or later Engineering Special 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 7.0 ES 19 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.

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

c. Click Cisco Unity System Software.

d. In the All Releases section, expand 7.0, and click 7.0(2).

e. In the right pane, click CiscoUnity_7.0(2)_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_7.0(2)_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_7.0(2)_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_7.0(2)_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.

Security Guide for Cisco Unity: Limitations of Secure Messaging

Added July 1, 2009

In the "Limitations of Secure Messaging" section in the "Securing Subscriber Messages" chapter, add the following limitation.

If your subscribers access secure messages by using clients such as Cisco Unified Personal Communicator, Cisco Unified Mobile Communicator (through Cisco Unified Mobility Advantage), and Cisco Unified Messaging with IBM Lotus Sametime, you must install Cisco Unity Voicemail Web Service (VMWS) on the Cisco Unity server.

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: Disabling Voice Recognition for All Subscribers

Added November 3, 2008

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: Phone View Features

Added February 25, 2009

Note that Phone View features are not supported on Cisco IP phones that have shared lines (multiple Cisco IP phones that share one extension).

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

Added June 2, 2009

If the Microsoft Messaging API (MAPI) installed on a Cisco Unity 7.0(2) server is accessing a Windows Server 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:

<pre>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 a Windows Server 2008 GC, to determine whether the Win2008 GC is having the NSPI problem, and, if so, to change a registry setting on all Windows Server 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 a Windows Server 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 Windows Server 2008 GC, continue with Step 2.

If the value is not the name of a Windows Server 2008 GC, your symptoms have another cause.

Step 2 Determine whether the Windows Server 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 a Windows Server 2003 GC. Set the value to 0x00002710.

d. Restart the Cisco Unity server.

e. Repeat Step b. and Step c. on every Windows Server 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 Windows Server 2008 GC but you have Windows Server 2008 GCs in the forest, you may still want to do step 4c. on every Windows Server 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.


Note The following links go to Release 5.x versions of the guide; all 5.x content applies to version 7.x as well.


Troubleshooting Guide for Cisco Unity Release 5.x (With IBM Lotus Domino) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/troubleshooting/guide/dom/5xcutsgex.html.

Troubleshooting Guide for Cisco Unity Release 5.x (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/troubleshooting/guide/ex/5xcutsgex.html.

For troubleshooting Phone View features, refer to the tech note Cisco Unity 5.0 - Troubleshooting Phone View Issues at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_tech_notes_list.html. Note that although the document title refers to version 5.0, the content applies to version 7.x as well.

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.



Note The software for a demonstration system can be ordered online. The orderable demonstration system is the easiest way to get an entire set of the discs, including third-party software (except Windows). It is available at https://tools.cisco.com/qtc/config/jsp/configureHome.jsp. The part number is UNITY7-DEMO-K9. 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 5.x Demonstration System to a Cisco Unity 7.0(2) 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. Note that the CiscoUnity50.lic license file is still being used for Cisco Unity 7.0.

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 three procedures in this section 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 and 7.0 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 5.x Demonstration System to a Cisco Unity 7.0(2) Demonstration System

To Upgrade a Cisco Unity 5.x Demonstration System to a Cisco Unity 7.0(2) Demonstration System


Step 1 Follow the documented process for upgrading a Cisco Unity 4.x system to a Cisco Unity 5.x system. Cisco Unity 5.x and 7.0 use the same license file, so replacing the existing license file is not necessary.

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 Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html. (All 5.x content applies to version 7.x as well.)


Converting a Cisco Unity Demonstration System to a Standard System

Do the procedure in this section 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 Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html. (All 5.x content applies to version 7.x as well.)


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.

b. For the new ports, set the line groups and hunt groups for the ports. Refer to 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.

b. 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 Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html. (All 5.x content applies to version 7.x as well.)


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. (All 5.x content applies to version 7.x as well.)

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. (All 5.x content applies to version 7.x as well.)



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

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. (All 5.x content applies to version 7.x as well.)


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. (All 5.x content applies to version 7.x as well.)


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.


© 2012 Cisco Systems, Inc. All rights reserved.