Release Notes for Cisco Unity Release 8.0(3) Republished February 18, 2010 (Originally published February 2, 2010)

These release notes contain information on downloading and installing software, new and changed requirements and support, new and changed functionality, limitations and restrictions, and caveats for Cisco Unity Release 8.0(3).

Contents •

System Requirements, page 1

•

Related Documentation, page 5

•

New and Changed Requirements and Support—Release 8.0(3), page 6

•

New Functionality—Release 8.0(3), page 11

•

Changed Functionality—Release 8.0(3), page 13

•

Installation and Upgrade Information, page 15

•

Limitations and Restrictions, page 24

•

Caveats, page 27

•

Documentation Updates, page 28

•

Troubleshooting Information, page 29

•

Installing a Cisco Unity Demonstration System, page 29

•

Obtaining Documentation and Submitting a Service Request, page 31

•

Cisco Product Security Overview, page 31

System Requirements The following documents list the most current Cisco Unity requirements: •

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

Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

System Requirements

•

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

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 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/support/8xcusupp.html.

Determining the Software Version This section contains procedures for determining the version in use for the following software: •

Cisco Unity, page 2

•

Cisco Unity-CM TSP, page 3

•

Interoperability Gateway for Microsoft Exchange, page 3

•

Cisco Unity Voice Connector for Microsoft Exchange, page 4

•

Active Directory Schema Extensions for Cisco Unity, page 4

•

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.

Release Notes for Cisco Unity Release 8.0(3)

2

OL-21706-01

System Requirements

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 an SCCP integration, if available.

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 Windows\System32 directory.

Step 2

Right-click AvSkinny.tsp, and click Properties.

Step 3

In the Properties window, click the Version tab.

Step 4

In the Item Name list, click Product Version. The Cisco Unity-CM TSP version is displayed in the Value window.

Interoperability Gateway for Microsoft Exchange To Determine the Interoperability Gateway for Microsoft Exchange Version in Use by Using the CuIgeSvc.exe File Step 1

On the Windows Start menu on the server on which the Interoperability Gateway for Microsoft Exchange is installed, click Search > For Files or Folders.

Step 2

Search for the file named CuIgeSvc.exe.

Step 3

In the results pane, right-click CuIgeSvc.exe, and click Properties.

Step 4

In the Properties window, click the Version tab.

Step 5

In the Item Name list, click Product Version. The Interoperability Gateway version is displayed in the Value window.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

3

System Requirements

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

•

Cisco Unity Bridge

•

Cisco Unity VPIM

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

Release Notes for Cisco Unity Release 8.0(3)

4

OL-21706-01

Related Documentation

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, see the Documentation Guide for Cisco Unity Release 8.x. The guide is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/documentation/guide/8xcudg.html.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

5

New and Changed Requirements and Support—Release 8.0(3)

New and Changed Requirements and Support—Release 8.0(3) This section contains information about new and changed requirements and support in the 8.0(3) release time frame only. (For information on new and changed requirements and support in earlier versions of Cisco Unity, see the applicable release notes at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.)

Active Directory Schema Extensions Required for Cisco Unity Active Directory schema extensions for Cisco Unity were not changed for Cisco Unity 8.0(3). If you are upgrading from Cisco Unity 5.0 to version 8.0(3), you do not need to extend the Active Directory schema. However, if you are upgrading from Cisco Unity 4.x to version 8.0, you must extend the schema with schema extensions for Cisco Unity 5.0 or later. For more information, see 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 8.0(3) 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 8.0(3). For a list of Cisco Unity version combinations that are supported for networked Cisco Unity servers, see 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.

Cisco Security Agent for Cisco Unity Version 3.1(7) Cisco Security Agent for Cisco Unity 3.1(7) is qualified for use with Cisco Unity 8.0(3) and Cisco Unity Bridge. For information on the security agent, see Release Notes for Cisco Security Agent for Cisco Unity Release 3.1(7) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/security_agent/release/notes/317cusecagtreln otes.html.

Cisco Unity-CM TSP Version 8.4(3) Cisco Unity-CM TSP 8.4(3) is qualified for use with Cisco Unity version 8.0(3). For information on the Cisco Unity-CM TSP, see Release Notes for Cisco Unity-CM TSP Release 8.4(3) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/tsp/release/notes/843tsprn.html. Note that Cisco Unity-CM TSP 8.4(3) supports Cisco Unity versions 5.0(1) and later. Earlier versions of Cisco Unity are not supported.

Release Notes for Cisco Unity Release 8.0(3)

6

OL-21706-01

New and Changed Requirements and Support—Release 8.0(3)

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

Cisco Unity 8.0(3) Versioning Explained Field-test versions of Cisco Unity version 8.0 were versioned “8.0(1)” and “8.0(2)” to improve source control. To ensure that field-test sites do not have problems upgrading to the release version, it has been numbered “8.0(3).”

Cisco Unity Voice Connector for Microsoft Exchange Version 15.0(1) Voice Connector 15.0(1) is qualified for use with Cisco Unity version 8.0(3). 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, see Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

Cisco Unity Voice-Recognition Server Now Runs on Linux Beginning with Cisco Unity 8.0, you can no longer use the Windows-based voice-recognition application that is compatible with earlier versions of Cisco Unity. Instead, you must install a new Linux-based voice-recognition application. For information on servers supported as voice-recognition servers for Cisco Unity 8.0, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

IBM Lotus Domino Is Not Supported for Use with Cisco Unity 8.x Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x. Consequently, IBM Lotus Domino Unified Communications (DUC) for Cisco is not supported with version 8.x, and installing IBM Lotus Notes on a Cisco Unity version 8.x server is not supported. IBM Lotus Domino continues to be supported with earlier versions of Cisco Unity. In addition, Cisco Unity Connection supports IBM Lotus Notes access to Connection voice messages by using ViewMail for Notes. See the following documentation: •

For compatibility information, see Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucclientmtx. html.

•

For information on ViewMail for Lotus Notes, see Release Notes for Cisco Unity Connection ViewMail for IBM Lotus Notes Release 8.0(1) at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/vmn/release/notes/801cucvmnrn.ht ml.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

7

New and Changed Requirements and Support—Release 8.0(3)

•

For information on configuring Lotus Notes to access Connection voice messages by using IMAP, see the “Creating and Configuring an Account in IBM Lotus Notes” section in the “Configuring an Email Account to Access Cisco Unity Connection Voice Messages” chapter of the User Workstation Setup Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/user_setup/guide/8xcucuwsx.ht ml.

Languages for Cisco Unity Components There are no new languages in this release. For a complete list of languages, see the “Available Languages for Cisco Unity Components” section of System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/requirements/8xcusysreq.html.

Limits on Cisco Unity Subscribers in a Digital Network or Cisco Voicemail Organization for Platform Overlay 1 and 2 Servers For performance reasons, the number of Cisco Unity subscribers in a Digital Network or Cisco Voicemail Organization is limited when the network includes one or more Platform Overlay 1 or 2 servers that are running Cisco Unity 8.0: •

Platform Overlay 1 servers that are running Cisco Unity 8.0 cannot be used in a Cisco Unity Digital Network or Cisco Voicemail Organization that includes more than 10,000 Cisco Unity subscribers.

•

Platform Overlay 2 servers that are running Cisco Unity 8.0 cannot be used in a Cisco Unity Digital Network or Cisco Voicemail Organization that includes more than 20,000 Cisco Unity subscribers.

If the Digital Network or Cisco Voicemail Organization includes both Platform Overlay 1 and 2 servers, any one of which is running Cisco Unity 8.0, the lower limit applies.

Microsoft Exchange 2000 Server Is No Longer Supported on the Partner Exchange Server Cisco Unity no longer supports using an Exchange server that is running Exchange 2000 Server as the partner Exchange server. When Cisco Unity is installed in a Unified Messaging configuration, you can continue to home subscriber mailboxes in Exchange 2000 Server. Note the following considerations: •

If the Cisco Unity server is using a separate Exchange 2000 Server as the partner Exchange server, you must change the partner Exchange server to one running Exchange Server 2003 or Exchange Server 2007 before you can upgrade to Cisco Unity 8.0.

•

If Exchange 2000 Server is installed on the Cisco Unity server, you must reinstall all software to upgrade to Windows Server 2003 and Exchange Server 2003 before you can upgrade to Cisco Unity 8.0.

•

If you have UCSS support and if Cisco Unity is installed in a Voice Messaging configuration, you can order Exchange Server 2003 from Cisco free of charge. The Client Access Licenses (CALs) that are included with Exchange Server 2003 can also be used with Exchange Server 2007, but you must provide your own copy of Exchange 2007 and an Exchange 2007 server license. The Cisco-provided CALs cannot be used on systems that are used for email messages.

Release Notes for Cisco Unity Release 8.0(3)

8

OL-21706-01

New and Changed Requirements and Support—Release 8.0(3)

If you do not have UCSS support, you can buy Exchange Server 2003 from Cisco.

Microsoft Service Packs Required with Cisco Unity For the most current list of all required and recommended Microsoft service packs, see the “Software Requirements—Cisco Unity Server” section of System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/requirements/8xcusysreq.html.

Microsoft Windows 2000 Server Is No Longer Supported on the Cisco Unity Server If you want to upgrade a Cisco Unity Server that is currently running Windows 2000 Server, you must reinstall all software to upgrade to Windows Server 2003. If you have UCSS support, you can order part number Unity-OS-LIC-UPG, and Cisco will ship you a Windows Server 2003 disc. If you do not have UCSS support, you must purchase Windows Server 2003 from another vendor.

Phone System Integrations Qualified for Use with Cisco Unity Cisco Unified Communications Manager 8.0 has been qualified for use with Cisco Unity 8.0. For the most current list of all supported phone system integrations, see the “Supported Phone System Integrations” section of Supported Hardware and Software, and Support Policies for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/support/8xcusupp.html.

Phone System Integrations Through Voice Cards Are Not Supported Cisco Unity does not support phone system integrations through voice cards because voice cards and voice card software will not function correctly with the operating system on the Cisco Unity server. Note, that IP integrations (Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, and SIP) and PIMG/TIMG integrations continue to be supported.

Software Qualified for Use on Cisco Unity Subscriber Workstations The following software has been qualified for use on Cisco Unity subscriber workstations: •

Windows 7 Professional (32- and 64-bit)

•

Windows 7 Enterprise (32- and 64-bit)

•

Windows 7 Ultimate (32- and 64-bit)

•

Internet Explorer 8

For the most current versions of software supported for use on subscriber workstations, see 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.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

9

New and Changed Requirements and Support—Release 8.0(3)

Software That Is No Longer Supported for Use on Cisco Unity Subscriber Workstations Beginning with Cisco Unity version 8.0(3), the following software is not supported for use on Cisco Unity subscriber workstations: •

IBM Lotus Domino Unified Communications (DUC) for Cisco

•

Lotus iNotes/Domino Web Access

•

Windows 2000

For the most current versions of software supported for use on subscriber workstations, see 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.

Upgrading Directly from Cisco Unity 4.1(1) and Earlier Is Not Supported If you are upgrading a Cisco Unity server that is currently running version 4.1(1) or earlier, you must upgrade to version 4.2(1) or later before you can upgrade to version 8.0. For information on upgrading an older server to Cisco Unity 4.2(1) or later, see the “Upgrading Cisco Unity 4.x Software to the Shipping Version” in the Cisco Unity Reconfiguration and Upgrade Guide (With Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/42/upgrade/guide/ex/ex.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.

Release Notes for Cisco Unity Release 8.0(3)

10

OL-21706-01

New Functionality—Release 8.0(3)

VPIM Networking and Trusted Internet Subscribers Supported in Pure Exchange 2007 Environments The Interoperability Gateway for Exchange is a Cisco Unity networking component that enables VPIM messaging between Cisco Unity servers and other voice messaging systems. The gateway also supports Cisco Unity Connection Networking and the use of trusted Internet subscriber accounts. The Interoperability Gateway can be installed on an Exchange 2007 server with the Hub Transport role or on Exchange 2003 server to provide VPIM and trusted Internet subscriber functionality in all Exchange environments that are supported by Cisco Unity 8.0(3), including pure Exchange 2007 or any mixture of Exchange 2007, Exchange 2003, and Exchange 2000. However, if the deployment also includes AMIS or Bridge networking, you must use the Cisco Unity Voice Connector for Microsoft Exchange for those protocols, either along with or instead of the Interoperability Gateway. (The Voice Connector also supports VPIM networking and trusted Internet subscribers, but installing the Voice Connector on an Exchange 2007 server is not supported.) Although in some Exchange environments you have the option of using either the Voice Connector or Interoperability Gateway for VPIM Networking, if you also use Cisco Unity Connection Networking, which requires the Interoperability Gateway, you must use the Interoperability Gateway for VPIM as well. Support for installing the Interoperability Gateway on Microsoft Exchange 2010 servers is planned. For up-to-date support and requirements information for the Interoperability Gateway, see the Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs.html.

New Functionality—Release 8.0(3) This section contains information about new functionality in the 8.0(3) release time frame only. (For information on new functionality in earlier versions of Cisco Unity, see the applicable release notes 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 8.0(3). Some offerings may not be supported by Cisco TAC. See http://www.ciscounitytools.com/ for information.

Active Directory Synchronization Improvements The process for synchronizing data in the SQL Server database on the Cisco Unity server with data in Active Directory has been enhanced to improve performance in environments with large directories, primarily when Cisco Unity is synchronizing with a Windows Server 2003 or later domain controller or global catalog server.

Cisco Unity Connection Networking You can link a Cisco Unity server, failover pair, or Digital Network with a Cisco Unity Connection site of up to ten servers to provide directory synchronization, message exchange, and call transfers between servers in both sites. The linked sites are referred to as a Cisco Voicemail Organization.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

11

New Functionality—Release 8.0(3)

To create an intersite link, you choose a single location on each site to act as a gateway to the other site. The gateways exchange directory synchronization information via HTTP or HTTPS. Message exchange occurs via SMTP. On the Cisco Unity site, the Interoperability Gateway for Microsoft Exchange functions as the messaging gateway. On the Connection site, the SMTP server on the Connection site gateway serves as the messaging gateway. Cross-server sign in, transfers, and live reply can be enabled across the entire Cisco Voicemail Organization. The Cisco Unity site gateway must be running Cisco Unity version 8.x. Other Cisco Unity servers in the site may be running Cisco Unity with Microsoft Exchange version 5.x or 7.x provided that the applicable engineering special is installed to add Connection Networking support. The engineering specials will be available after the Cisco Unity version 8.0(3) release. For information about the availability of the engineering specials and for additional requirements, see the 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. For information on using Cisco Unity Connection Networking to migrate from Cisco Unity to Connection, see the “Migrating from Cisco Unity to Cisco Unity Connection 8.x by Gradually Moving Data” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/upgrade/guide/8xcucrugx.html.

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

Subscribers Can Copy Themselves When Sending Messages, page 12

•

Voice-Recognition Enhancements, page 12

For a summary of changes made to the default settings and functionality for the Cisco Unity conversation for this release, see the “Cisco Unity Conversation Changes” section on page 13.

Subscribers Can Copy Themselves When Sending Messages Subscribers have the option to send themselves copies of messages that they send. After addressing and recording a message, subscribers can choose the “copy yourself” special delivery option. If a subscriber is already a recipient, Cisco Unity will offer the option to “remove yourself.” In earlier versions, subscribers could add themselves to the recipient list by spelling their name or entering their extension. This feature gives them a faster way to send themselves copies of messages.

Voice-Recognition Enhancements The following enhancements have been made to voice recognition: •

Voice commands have been extended to all subscriber menus.

•

“Hang up” has been added as a new global voice command.

•

Subscribers can say their passwords when logging on to Cisco Unity by phone.

•

Subscribers can say dates and times when taking actions that require them, such as entering an end date and time for the alternate greeting.

Release Notes for Cisco Unity Release 8.0(3)

12

OL-21706-01

Changed Functionality—Release 8.0(3)

•

A Threshold to Trigger Speech Verification value has been added to control the voice-recognition confidence score below which subscribers are asked to confirm voice-command actions for deleting messages; addressing a reply to all recipients; sending a message, reply, or forward; or calling the sender of a message (live reply).

In addition, voice-recognition accuracy and performance have been improved over earlier releases.

Changed Functionality—Release 8.0(3) This section contains information about changed functionality in the 8.0(3) release time frame only. (For information on changed functionality in earlier versions of Cisco Unity, see the applicable release notes 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 8.0(3). Some offerings may not be supported by Cisco TAC. See http://www.ciscounitytools.com/ for information.

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

Conversation Settings Changed or Removed from the Advanced Settings Tool, page 13

•

First-Time Enrollment, Password Reset, and Private List Management Conversation Changes, page 13

Conversation Settings Changed or Removed from the Advanced Settings Tool The Conversation—Spoken Commands setting is no longer available in the Advanced Settings Tool. The setting has been replaced by enhanced voice-recognition functionality. See the “Voice-Recognition Enhancements” section on page 12.

First-Time Enrollment, Password Reset, and Private List Management Conversation Changes Some of the prompts that subscribers hear when listening to the first-time enrollment, password reset, and private list management conversations have been reworded to be more concise.

Playback Speed Adjustments Are Not Saved Across Phone Sessions Subscribers can use defined keys during message playback to speed up or slow down playback for each message individually; the change does not affect the playback speed of other messages and subscribers’ default speed setting is not changed. No keys are available for adjusting prompt playback speed by phone. In Cisco Unity 7.x, when subscribers use keys to speed up or slow down either message or prompt playback by phone, the new speed setting is saved so that when they next call in, the new speed settings are used.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

13

Changed Functionality—Release 8.0(3)

To revert to the Cisco Unity 7.x behavior, use the Advanced Settings Tool setting called Conversation—Do Not Save Speed Changes Made By Phone. For details, see Advanced Settings Tool Help.

Cisco Unity New Installs Use SQL Server 2005 or SQL Server 2005 Express as the Data Store When you purchase a new Cisco Unity server, Cisco ships a Cisco Unity Data Store 2005 disc that contains SQL Server 2005 and SQL Server 2005 Express. When you purchase an upgrade for an existing Cisco Unity server, Cisco ships an updated Cisco Unity Data Store 2000 disc that contains SQL Server 2000 and MSDE 2000. If the upgrade requires that you reinstall software (because, for example, the Cisco Unity server is still running Windows 2000 Server, which is no longer supported), you must use the new Cisco Unity Data Store 2000 disc because it has a different directory layout than the Data Store 2000 discs shipped with earlier versions of Cisco Unity. If you are upgrading from an earlier version of Cisco Unity, you have the option to pay for an upgrade from SQL Server 2000 or MSDE 2000 to SQL Server 2005 or SQL Server 2005 Express. Unlike Windows and Exchange upgrades, the upgrade to SQL Server 2005 or SQL Server 2005 Express is not available for free with UCSS support.

Cisco Unity Failover Supports a Single Gigabit Connection When Cisco Unity is configured for failover and the Cisco Unity servers are in separate buildings or sites, Cisco Unity supports a single path of connectivity between the Cisco Unity servers. This path must be gigabit speed or higher with no steady-state congestion.

Cisco Unity Installation Has Been Updated The Cisco Unity installation application has been updated to merge the functionality of the Cisco Unity System Preparation Assistant and the Cisco Unity Installation and Configuration Assistant into a single application called the Cisco Unity System Setup Assistant. You can also start the Permissions wizard from the main page of the Cisco Unity System Setup Assistant. Many of the operations formerly performed by the Cisco Unity System Preparation Assistant have been automated, so you no longer have to sit at the computer and click OK repeatedly while third-party prerequisites are being installed.

Media Master Uses HTTP/HTTPS Protocol to Communicate with Cisco UnityServer In the Cisco Unity Administrator, Cisco PCA web tools, and ViewMail for Outlook, the Media Master component can use either HTTP/HTTPS or DCOM as the communication protocol to send recordings and audio streams to and from Cisco Unity. By default, the Media Master uses HTTP/HTTPS as the communication protocol. HTTP/HTTPS is preferred because it is more reliable when connecting through a firewall and it uses TCP ports that are already opened for administration access.

Release Notes for Cisco Unity Release 8.0(3)

14

OL-21706-01

Installation and Upgrade Information

In the Cisco Unity Administrator and Cisco PCA web tools, whether the Media Master uses either HTTP or HTTPS as the default protocol is determined by the URL used to access the Cisco Unity Administrator and Cisco PCA web tools and whether SSL is configured for the Cisco Unity server. If your browser already has the Cisco Unity 8.0 version of the Media Master Active-X control installed, but you are browsing to a server running Cisco Unity version 7.x or earlier, which does not support HTTP/HTTPS as a communication protocol, the Media Master will automatically switch to using DCOM as the communication protocol. Cisco Unity ViewMail for Microsoft Outlook version 8.0 and later uses HTTPS as the communication protocol. If the Cisco Unity server is not running version 8.0 or later or the server is not configured to use SSL, then the Media Master in ViewMail will automatically switch to using DCOM as the communication protocol. If your Cisco Unity server is not configured to use SSL and you wish to use HTTP as the as the communication protocol, see the ViewMail for Outlook 8.0 Release Notes for information on how to configure the Media Master to use HTTP instead of HTTPS. In earlier versions of Cisco Unity and Cisco Unity ViewMail for Microsoft Outlook, the Media Master always used DCOM as the communication protocol between the client (browser or ViewMail) and the Cisco Unity server.

MWI Constant Message Count for SCCP Integrations Cisco Unified Communications Manager SCCP integrations support the message-count feature, which displays a real-time count of new and saved messages, and new and saved urgent messages on the Cisco IP phone screen. (The format of the display depends on which phone you are using.) The integration continues to provide the message indicator to indicate that new messages are available. For the Cisco Unified CM SCCP integration, this feature requires: •

Cisco Unified Communications Manager with Skinny Client Control Protocol (SCCP) version 18 or later.

•

A Skinny Client Control Protocol (SCCP) integration with Cisco Unity.

•

MWI and message count 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 message-count information.

Installation and Upgrade Information •

Downloading Software for Cisco Unity 8.0(3), page 15

•

Upgrading to Cisco Unity 8.0(3), page 18

•

Installing Cisco Unity for the First Time, page 18

•

Installation and Upgrade Notes, page 19

Downloading Software for Cisco Unity 8.0(3) Revised February 9, 2010

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

15

Installation and Upgrade Information

This section contains a procedure for downloading Cisco Unity 8.0(3) disc images, the Cisco Unity Prerequisites disc image, and the Cisco Unity Server Updates wizard. Even if you have Cisco Unity 8.0(3) discs, we recommend that you do the procedure to download the current Cisco Unity Server Updates wizard, which contains the latest Microsoft updates recommended for use with Cisco Unity. The wizard is updated monthly. To Download the Software Required to Install Cisco Unity 8.0(3) Step 1

See Table 2 on page 18 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 1 below.

Note

Table 1

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

Download Substeps

Cisco Unity disc images, including languages, if applicable

Cisco Unity Prerequisites disc image

a.

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

b.

In the tree control on the Downloads page, expand Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity, and click Cisco Unity version 8.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.

a.

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

a.

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

b.

Click CiscoUnity8.0.1-Prereqs--DVD1.exe, and follow the on-screen prompts to complete the download. Make note of the MD5 value.

Release Notes for Cisco Unity Release 8.0(3)

16

OL-21706-01

Installation and Upgrade Information

Table 1

Download Substeps (continued)

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

Step 4

a.

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

a.

In the tree control on the Downloads page, expand Unified Communications Applications > Voice Mail and Unified Messaging > Cisco Unity, and click Cisco Unity version 8.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.

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

Step 6

Step 7

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.

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.

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

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

17

Installation and Upgrade Information

Table 2 lists the contents of the Cisco Unity 8.0(3) DVD images that are available on Cisco.com. (The physical discs that Cisco ships when you order a Cisco Unity server 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 2

Contents of Cisco Unity 8.0(3) DVD Images

DVD

Contents

1

The following software: •

Cisco Unity application files

•

Cisco Personal Communications Assistant

•

Cisco Unity ViewMail for Microsoft Outlook

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

The following software required to complete a Cisco Unity installation: •

Cisco Unity Report Engine

•

Cisco Unity System Setup Assistant, which also performs system checks, and guides you through the installation of the applicable Cisco Unity Data Store and the corresponding Data Store service pack

•

Microsoft Internet Explorer, Version 6, Service Pack 1

•

Microsoft Messaging API and Collaboration Data Objects version 1.2.1

•

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

•

Microsoft Visual C++ 2005 Redistributable DLLs

•

Microsoft Windows Installer version 3.1

•

Microsoft Windows Server 2003 Service Pack 2

•

Selected Microsoft World Wide Web Service subcomponents of Microsoft IIS

•

Selected Microsoft Message Queuing (MSMQ) components

Upgrading to Cisco Unity 8.0(3) For instructions on upgrading to Cisco Unity version 8.0(3), see the “Upgrading Cisco Unity Software to the Shipping 8.x Version” chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/upgrade/guide/8xcurugx.html. See also the “Installation and Upgrade Notes” section on page 19.

Caution

Upgrading directly from Cisco Unity 4.1(1) and earlier to Cisco Unity 8.0(3) is not supported. You must upgrade to Cisco Unity 4.2 first, then upgrade again from 4.2 to 8.0. (See also the “Upgrading Directly from Cisco Unity 4.1(1) and Earlier Is Not Supported” section on page 10.)

Installing Cisco Unity for the First Time For instructions on installing a new Cisco Unity 8.0(3) server, see the Installation Guide for Cisco Unity that matches the configuration you are installing. For descriptions of the various installation guides, see Use the Installation Guide That Matches the Cisco Unity 8.x Configuration at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/correct_ig/8xcuigcrct.html.

Release Notes for Cisco Unity Release 8.0(3)

18

OL-21706-01

Installation and Upgrade Information

Installation guides are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. See also the following section, “Installation and Upgrade Notes.”

Installation and Upgrade Notes •

Cisco Unity Malfunctions After Exchange 2000 EDSLock Script Is Run, page 19

•

Customizing Cisco Unity System Prompts Is Not Supported, page 20

•

Missing Exchange Service Packs Can Affect Cisco Unity Functionality, page 20

•

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

•

Permissions Wizard Causes a Spike in Processing on All Domain Controllers in the Domain, page 21

•

Public Distribution Lists and Networking Subscribers Created by Cisco Unity Are Not Listed in the Directory, page 21

•

Upgrade Effect on Diagnostic Traces, page 24

•

Upgrade from 5.0 or 7.0 Does Not Require Extending Active Directory Schema, But Upgrade from 4.x Does, page 24

•

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

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, see 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, see Permissions wizard Help.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

19

Installation and Upgrade Information

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.

Missing Exchange Service Packs Can Affect Cisco Unity Functionality If the minimum required Exchange service pack is not installed, Cisco Unity functionality may not function properly—for example, message indicators. Exchange service packs that are required both when Exchange is installed on the Cisco Unity server and when Exchange is installed on another server are listed in System Requirements for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/requirements/8xcusysreq.html. Also see the “Minimum Exchange Service Packs Required—Message Store” section.

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 following procedure to 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 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.

Release Notes for Cisco Unity Release 8.0(3)

20

OL-21706-01

Installation and Upgrade Information

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.

Permissions Wizard Causes a Spike in Processing on All Domain Controllers in the Domain 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.

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.

Public Distribution Lists and Networking Subscribers Created by Cisco Unity Are Not Listed in the Directory When Cisco Unity is installed in an Active Directory forest that contains only Microsoft Exchange 2007 servers, public distribution lists and contact objects created by the Cisco Unity server do not have a value written to the showInAddressBook attribute. As a result, those objects are not available in an address book accessed through a mail client, such as Microsoft Outlook. The contact objects affected include VPIM, Trusted Internet, and Connection Networking subscribers. (Note that this affects both objects that you create by using the Cisco Unity Administrator, such as public distribution lists or manually-created VPIM subscribers, and objects that are created automatically by Cisco Unity, such as Connection Networking subscribers or automatically-created VPIM subscribers. If you always create objects in Active Directory or Exchange first and then import them into Cisco Unity, and you do not use Connection Networking or automatically-created VPIM subscribers, this issue does not affect you.) When Cisco Unity is installed in an environment with Exchange versions prior to Exchange 2007, the Exchange Recipient Update Service (RUS) writes values to the showInAddressBook attribute. Exchange 2007 does not use RUS. Instead, the showInAddressBook attribute is populated automatically at the time an object is created through a PowerShell cmdlet. Because Cisco Unity does not use PowerShell when creating public distribution lists or contacts, the showInAddressBook attribute is not populated for these objects unless you take additional steps to do so. In order to populate the attribute, you can update the address lists in which the public distribution lists and contact objects should be listed manually by using either the Exchange 2007 Management Console or the Exchange Management Shell. Or, you can create a PowerShell script to update the address lists, and schedule the script to run periodically. Either manual approach may be acceptable if you anticipate

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

21

Installation and Upgrade Information

creating few distribution lists or contacts through Cisco Unity. However, if you anticipate these types of objects being created periodically and prefer passing control to a scheduled script, we recommend setting up and scheduling the PowerShell script. Do one of the following procedures: •

To Update Address Lists Manually by Using the Exchange 2007 Management Console, page 22

•

To Update Address Lists Manually by Using the Exchange Management Shell, page 22

•

To Create and Schedule a PowerShell Script to Automatically Update Address Lists, page 22

To Update Address Lists Manually by Using the Exchange 2007 Management Console Step 1

Open the Exchange 2007 Management Console on any Exchange server in the organization.

Step 2

In the tree in the left-hand pane, click Microsoft Exchange > Organization Configuration > Mailbox.

Step 3

In the center pane, click the Address Lists tab. Right-click each of the applicable address lists and click Apply, then follow the instructions on the screen to re-apply (update) the address list. •

For distribution lists, the standard default address list is named All Groups.

•

For contacts, the standard default address list is named All Contacts.

•

If you wish to have distribution lists and contacts also appear in the default Global Address List, also select Default Global Address List.

To Update Address Lists Manually by Using the Exchange Management Shell Step 1

Open the Exchange Management Shell on any Exchange server in the organization.

Step 2

At the prompt, enter the following command, including the single quotes: update-addresslist -identity ''

Replace with the name as it would be displayed on the Address Lists tab in the Exchange Management Console.

Step 3

•

For distribution lists, the standard default address list is named All Groups.

•

For contacts, the standard default address list is named All Contacts.

•

To have distribution lists and contacts appear in the default Global Address List, enter update-GlobalAddressList -identity 'Default Global Address List'.

Repeat Step 2 for each applicable address list, including the Default Global Address List or any additional global address lists you use.

To Create and Schedule a PowerShell Script to Automatically Update Address Lists Step 1

Sign on to a server that has Windows PowerShell installed.

Note

We recommend creating and scheduling the PowerShell script on an Exchange 2007 server.

Release Notes for Cisco Unity Release 8.0(3)

22

OL-21706-01

Installation and Upgrade Information

Step 2

Use a text editor to create a text file with a descriptive name and an extension of ps1 (for example, Cisco Unity Address List Update.ps1).

Step 3

In the text file, enter Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin.

Step 4

Add an update-addresslist cmdlet for each address list to be updated, or update-GlobalAddressList line to update a Global Address List. In the following example script, the standard default address list for distribution lists (All Groups) will be updated, along with the standard default address list for contacts (All Contacts), and the default Global Address List. Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin update-addresslist -identity 'All Groups' update-addresslist -identity 'All Contacts' update-GlobalAddressList -identity 'Default Global Address List'

Tip

You can add additional address lists if your deployment contains address lists that display distribution lists and contacts, or remove any address lists that are not applicable. The only required line is the first line, which allows Exchange 2007 PowerShell cmdlets to be executed.

Step 5

Save the text file.

Step 6

Test the script: a.

On the Windows Start menu, click Run.

b.

Run cmd.

c.

Browse to the directory containing your PowerShell script.

d.

Enter

Powershell.exe -Noninteractive -command “& .\.ps1” and press Enter.

Note

Replace .ps1 with the name of the file that you created in Step 2. The double quotes must surround the ampersand (&) and script file name. Also, note the period and slash (.\) before the file name.

If the script does not execute successfully, error messages will be displayed. Step 7

Schedule the script to run automatically. a.

In the directory in which you saved the script file in Step 2, use a text editor to create a batch file with a descriptive name and an extension of bat (for example, Cisco Unity Address List Update.bat).

b.

In the text file, enter the same text that you entered in Step 6 d.

c.

On the Windows Start menu, browse to All Programs > Accessories > System Tools > Scheduled Tasks.

d.

Double-click Add Scheduled Task.

e.

Follow the screens in the Scheduled Task Wizard to schedule the task. When presented the menu to select the program to run, click Browse, browse to the directory containing the batch file and select it.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

23

Limitations and Restrictions

The frequency at which to execute the batch file is up to you. The more frequently it runs, the sooner distribution lists and contacts that have been created since the last task execution will appear in address books.

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

Upgrade from 5.0 or 7.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 8.0(3). If you are upgrading from Cisco Unity 5.0 or 7.0 to version 8.0(3), 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.

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, see the “Managing Languages” chapter of the System Administration Guide for Cisco Unity Release 8.x (with Microsoft Exchange) at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.html.

Limitations and Restrictions 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.

Release Notes for Cisco Unity Release 8.0(3)

24

OL-21706-01

Limitations and Restrictions

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

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

25

Limitations and Restrictions

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.

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 Email By design, when subscribers listen to their email 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, see 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.)

Voice-Recognition Session Limit Cisco Unity supports up to 24 concurrent voice-recognition sessions, regardless of the platform overlay in use.

Release Notes for Cisco Unity Release 8.0(3)

26

OL-21706-01

Caveats

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 Using Windows Terminal Services (WTS) to access a Cisco Unity 8.x server is supported for all Cisco Unity installation, upgrade, and administration functions with the following exceptions: •

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.

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 You can find the latest caveat information for Cisco Unity version 8.0(3) by using Bug Toolkit, an online tool available for customers to query defects according to their own needs. Bug Toolkit is available at www.cisco.com/go/bugs. Fill in your query parameters by using the custom settings in the Advanced Settings option.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

27

Documentation Updates

Note

To access Bug Toolkit, you must be logged on to Cisco.com as a registered user. 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 8.0(3) This section list any Severity 1, 2, and 3 open caveats when Cisco Unity version 8.0(3) was released. Select a link in the Caveat Number column to view the latest information on the caveat in Bug Toolkit. (Caveats are listed in order by severity, then by component, then by caveat number.) Table 3

Cisco Unity Release 8.0(3) Open Caveats

Caveat Number

Component

Severity

Description

CSCtc91569

conversations

2

Subscriber addressing not working as designed

CSCtb32879

exmessaging

2

Subscribers on newly added failover server unable to retrieve messages.

CSCte67714

documentation

3

numeric value for Notification.SignIn key may cause sign-in failure.

CSCte33508

exchvoicegateway

3

voice connector hangs on shutdown

CSCte56457

failover

3

Upgrade re-run after initial fail/cancel on secondary can not succeed

CSCte46634

ige

3

IGE-Connection VPIM Dir Push inbound messages not handled by IGE

CSCte46428

setup

3

UCI: New intersite link fails to retrieve site statistics from Unity

CSCte65989

setup

3

Setup disappears shortly after install begins

CSCte44045

telephony

3

Release Transfers over SIP can cause hang-up

CSCte67142

utilities

3

Port Status Monitor doesn’t display last redirecting ID

CSCte73540

viewmail

3

VMO fails to upgrade on Windows Vista and Windows 7

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

Installation Guide for Cisco Unity Release 8.x, All Versions: Configuring a Dual NIC in the Cisco Unity 8.x Server Added February 18, 2010

Release Notes for Cisco Unity Release 8.0(3)

28

OL-21706-01

Troubleshooting Information

In the “Customizing the Cisco Unity 8.x Platform” chapter, the “Configuring a Dual NIC in the Cisco Unity 8.x Server” section mentions Broadcom Control Suite 2. Broadcom Advanced Control Suite 3 and later is also supported for configuring a dual NIC.

Troubleshooting Information Cisco Unity troubleshooting information can be found in the Troubleshooting Guide for Cisco Unity Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/troubleshooting/guide/8xcutsgx.html. For troubleshooting Phone View features, see 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 8.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 on page 30. A demonstration system uses one of two different license files:

Note

•

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

•

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

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, see the instructions in the Installation Guide for Cisco Unity and in the integration guide for your phone system. Cisco TAC does not provide support for Cisco Unity demonstration systems. The Installation Guide for Cisco Unity is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. The software for a demonstration system can be ordered 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.

Note

You must be a registered user to access this web page. If you are not a registered user, go to http://tools.cisco.com/RPF/register/register.do to register and obtain a Cisco.com user ID. We strongly recommend that you install a demonstration system by using the software you receive when you purchase either the full version of Cisco Unity or the orderable demonstration system. Both include the versions of third-party products that Cisco Unity requires to function properly. Installations of demonstration systems frequently fail because the installer is using an unsupported version of third-party software.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

29

Installing a Cisco Unity Demonstration System

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

Release Notes for Cisco Unity Release 8.0(3)

30

OL-21706-01

Obtaining Documentation and Submitting a Service Request

•

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

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.

Cisco Product Security Overview This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately Further information regarding U.S. export regulations may be found at http://www.access.gpo.gov/bis/ear/ear_data.html.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2010 Cisco Systems, Inc. All rights reserved.

Release Notes for Cisco Unity Release 8.0(3) OL-21706-01

31

Cisco Product Security Overview

Release Notes for Cisco Unity Release 8.0(3)

32

OL-21706-01