Guest

Cisco Unity Connection

Release Notes for Cisco Unity Connection Releases 7.1(5), 7.1(5a), and 7.1(5b)

  • Viewing Options

  • PDF (344.3 KB)
  • Feedback
Release Notes for Cisco Unity Connection Releases 7.1(5), 7.1(5a), and 7.1(5b)

Table Of Contents

Release Notes for Cisco Unity Connection Releases 7.1(5), 7.1(5a), and 7.1(5b)

Contents

System Requirements

For Cisco Unity Connection

For Cisco Unity Connection in Cisco Unified CMBE

Compatibility Information

Determining the Software Version

Cisco Unity Connection

Cisco Personal Communications Assistant

Related Documentation

For Cisco Unity Connection

For Cisco Unified Communications Manager Business Edition

New and Changed Requirements and Support—Release 7.1(5)

Additional Languages for Cisco Unity Connection Components

Calendar Integration with Exchange 2007 Server Is No Longer Supported

Cisco Unity Connection 7.1(5) Engineering Specials Earlier Than ES 18 Are Not Supported with 7.1(5a) or 7.1(5b)

Cisco Unity Connection 7.1(5b)

Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions

Cisco Unity Connection Cluster Patch Required for Upgrades from 7.1(5) to 7.1(5a) or 7.1(5b)

Phone System Integrations

For Cisco Unity Connection

For Cisco Unity Connection in Cisco Unified CMBE

Selected Servers Require Replacement Hard Disks or Additional Memory for Some Configurations

Software Qualified for Use with Cisco Unity Connection on User Workstations

Upgrades from Connection 7.1(5) to 8.0(x) Are Not Supported

Utility Updates on the Cisco Unity Tools Website

New Functionality—Release 7.1(5)

Bulk Password Edit Tool Available for Assigning Unique Passwords and PINs to Multiple User Accounts at Once

Changed Functionality—Release 7.1(5)

Installation and Upgrade Information

Information for Cisco Unified Communications Manager Business Edition Customers

Installing Cisco Unity Connection for the First Time

Supported Cisco Unity Connection Upgrades

Upgrading to Cisco Unity Connection 7.1

Downloading Software for an Upgrade to Cisco Unity Connection 7.1

Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1

Installation and Upgrade Notes

Cisco Unity License Files Can Be Used for Migrations from Cisco Unity to Cisco Unity Connection and to Connection in Cisco Unified CMBE

Installing and Using Cisco Unity Connection Languages in Addition to U.S. English

License Tag Required to Enable the U.S. English Conversation and Personal Call Transfer Rules

Important Notes

Connection IMAP Server Service Should Not Be Stopped or Disabled for an Extended Period of Time

Limitations and Restrictions

Connection Cannot Be Installed or Operated in IPv6 or Dual-Stack (IPv4 and IPv6) Networks

In Connection Cluster, Changed License Data on One Server Does Not Replicate to Other Server

Media Master Cannot Open WAV Files Saved on a Workstation in G.729a Format

Replacing Disks in a RAID

ViewMail Limitations Regarding Secure Messages

Caveats

Open Caveats—Connection Release 7.1(5), and Connection in Cisco Unified CMBE Release 7.1(5)

Related Caveats—Cisco Unified Communications Manager 7.1(5) Components That Are Used by Connection 7.1(5)

Documentation Updates

Errors

Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Traps and Informs

System Administration Guide for Cisco Unity Connection: Creating a Calendar Integration with Exchange 2007

Omissions

Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Services

Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Management Information Base (MIB)

Cisco Unified Serviceability Administration Guide Release 7.1(2): Configuring CISCO-UNITY-MIP Trap Parameters

Interface Reference Guide for Cisco Unity Connection Administration Release 7.x: Messaging Configuration (Cisco Unity Connection 7.1)

Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Replacing a 7.x Publisher Server in a Connection Cluster

Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Task List for Migrating from Cisco Unity 4.x or Later to Connection 7.x

System Administration Guide for Cisco Unity Connection Release 7.x: Using Advanced Settings to Enable System Distribution List Access Lists

Troubleshooting Information

Obtaining Documentation and Submitting a Service Request

Cisco Product Security Overview


Release Notes for Cisco Unity Connection Releases 7.1(5), 7.1(5a), and 7.1(5b)


Revised April 2, 2012 (Originally published April 19, 2010)

These release notes contain information on downloading software, new and changed support, new and changed functionality, limitations and restrictions, open and resolved caveats, and documentation updates for Cisco Unity Connection Releases 7.1(5), 7.1(5a), and 7.1(5b), and for Connection in Cisco Unified Communications Manager Business Edition (CMBE) Releases 7.1(5), 7.1(5a), and 7.1(5b).

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

Cisco Unity Connection 7.1(5a) and 7.1(5b) contain fixes and changes to the operating system and/or Cisco Unified Communications Manager 7.1(5) application components, including components shared by Connection and Cisco Unified CM.

In addition, with the 7.1(5a) release, there are now restricted and unrestricted versions of Cisco Unity Connection software available. Providing two versions addressed import requirements for some countries related to encryption of user data.

Note the following information:

For more information, see the "Cisco Unity Connection 7.1(5b)" section and the "Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions" section.

Throughout this document, references to 7.1(5) also apply to 7.1(5a) and 7.1(5b).

Anything documented as compatible with Connection 7.1(5)—for example, versions and tools, and other Cisco products—are equally compatible with 7.1(5a) and 7.1(5b).

Do not install 7.1(5) engineering specials prior to ES 18 with 7.1(5a) or 7.1(5b). See the "Cisco Unity Connection 7.1(5) Engineering Specials Earlier Than ES 18 Are Not Supported with 7.1(5a) or 7.1(5b)" section.

If you are upgrading a Connection 7.1(5) cluster, see the "Cisco Unity Connection Cluster Patch Required for Upgrades from 7.1(5) to 7.1(5a) or 7.1(5b)" section.

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


Note Cisco Unity Connection is a Linux-based solution. It is available in two configurations—Cisco Unity Connection, and Cisco Unified Communications Manager Business Edition, in which Connection is preloaded on the same platform with Cisco Unified Communications Manager. These release notes contain information for both configurations.



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


Contents

System Requirements

Related Documentation

New and Changed Requirements and Support—Release 7.1(5)

New Functionality—Release 7.1(5)

Changed Functionality—Release 7.1(5)

Installation and Upgrade Information

Important Notes

Limitations and Restrictions

Caveats

Documentation Updates

Troubleshooting Information

Obtaining Documentation and Submitting a Service Request

Cisco Product Security Overview

System Requirements

For Cisco Unity Connection

System Requirements for Cisco Unity Connection Release 7.x contains the most current Connection requirements. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucsysreqs.html.

For Cisco Unity Connection in Cisco Unified CMBE

System Requirements for Cisco Unity Connection in Cisco Unified CMBE Release 7.x contains the most current Connection requirements. The document is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucmbesysreqs.html.

Compatibility Information

The following documents list the most current version combinations qualified for use with Cisco Unity Connection, and with Connection in Cisco Unified CMBE (where applicable):

Compatibility Matrix: Cisco Unity Connection and the Software on User Workstations

SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express

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

The documents are available on Cisco.com at http://www.cisco.com/en/US/products/ps6509/products_device_support_tables_list.html.

Determining the Software Version

This section contains procedures for determining the version in use for the following software:

Cisco Unity Connection

Cisco Personal Communications Assistant

Cisco Unity Connection

To Determine the Cisco Unity Connection Version by Using Cisco Unity Connection Administration


Step 1 In Cisco Unity Connection Administration, in the upper-right corner below the Navigation list, click About.

The Connection version is displayed below "Cisco Unity Connection Administration."


To Determine the Cisco Unity Connection Version by Using the Command-Line Interface


Step 1 Start a command-line interface (CLI) session. For more information, see the Cisco Unified Communications Operating System Administration Help.

Step 2 Run the show cuc version command.


Cisco Personal Communications Assistant

To Determine the Cisco Personal Communications Assistant (PCA) Version


Step 1 Log on to the Cisco PCA.

Step 2 On the Cisco PCA Home page, click About in the upper right corner. (The link is available on every web tool page.)

Step 3 The Cisco Unity Connection version is displayed. The Cisco PCA version is the same as the Connection version.


Related Documentation

For Cisco Unity Connection

For descriptions and URLs of Cisco Unity Connection documentation on Cisco.com, see the Documentation Guide for Cisco Unity Connection Release 7.x. The document is shipped with Connection and is available at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/roadmap/7xcucdg.html.

For Cisco Unified Communications Manager Business Edition

For descriptions and URLs of Cisco Unified Communications Manager Business Edition documentation on Cisco.com, see the Cisco Unified Communications Manager Business Edition Documentation Guide. The document is shipped with Cisco Unified CMBE and is available at http://www.cisco.com/en/US/products/ps7273/products_documentation_roadmaps_list.html.


Note The documentation links on Cisco.com for some Cisco Unity Connection in Cisco Unified CMBE 7.x versions go to documents that are labeled for Cisco Unity Connection Release 7.x. Despite the version label, all content in the following guides applies to both Connection configurations: Administration Guide for Cisco Unity Connection Serviceability, Interface Reference Guide, System Administration Guide, Troubleshooting Guide, User Moves, Adds, and Changes Guide, and the User Workstation Setup Guide.


New and Changed Requirements and Support—Release 7.1(5)

This section contains information about new and changed requirements and support in the 7.1(5) release time frame only.

(For information on new and changed requirements and support in earlier versions of Cisco Unity Connection, see the applicable release notes at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html. Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.)

Additional Languages for Cisco Unity Connection Components

There are no new languages for this release.

For a list of available languages, see the "Available Languages for Cisco Unity Connection Components" section of the applicable System Requirements:

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

System Requirements for Cisco Unity Connection in Cisco Unified CMBE Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/requirements/7xcucmbesysreqs.html.

For more information, see the "Installing and Using Cisco Unity Connection Languages in Addition to U.S. English" section.

(For a list of numeric and alphabetic language codes, see the "Numeric and Alphabetic Codes for Supported Languages in Cisco Unity Connection" section of the 7.x System Requirements.)

Calendar Integration with Exchange 2007 Server Is No Longer Supported

Added July 9, 2010

A calendar integration with Exchange 2007 Server is no longer supported in Cisco Unity Connection 7.1(5x).

The "Creating a Calendar Integration with Exchange 2007" section in the "Creating Calendar Integrations" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x (at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html) incorrectly indicates that calendar integrations with Exchange 2007 Server are supported.

Note however that contact and text to speech integrations are still supported with Exchange 2007 Server.

Cisco Unity Connection 7.1(5) Engineering Specials Earlier Than ES 18 Are Not Supported with 7.1(5a) or 7.1(5b)

Revised July 20, 2010

If you are installing Connection 7.1(5a) or 7.1(5b), do not install 7.1(5) engineering specials prior to ES 18. Earlier 7.1(5) ESes are not supported with 7.1(5a) or 7.1(5b).

ES 18 will be released in late July.

Cisco Unity Connection 7.1(5b)

Added July 20, 2010

Connection 7.1(5b) contains fixes and changes to the operating system and/or Cisco Unified Communications Manager 7.1(5) application components, including components shared by Connection and Cisco Unified CM.

The shipping DVDs and the DVD 1 images available on the Cisco Unity Connection 7.1 Software Download page on Cisco.com have been updated with release 7.1(5b).

For related information, see the following sections in these release notes:

"Supported Cisco Unity Connection Upgrades" section

"Related Caveats—Cisco Unified Communications Manager 7.1(5) Components That Are Used by Connection 7.1(5)" section

Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions

Added July 7, 2010

With this release and going forward, providing two versions of the Connection software—restricted and unrestricted—addresses import requirements for some countries related to encryption of user data and affects the following functionality:

Functionality
Restricted
Version of Connection
Unrestricted
Version of Connection

SSL for IMAP connections used to access voice messages

Enabled

Disabled

Secure SCCP, SIPS, and SRTP for call signaling and media

Enabled

Disabled

File replication in a Connection cluster

Uses 128-bit encryption

Uses 40-bit encryption

Communications among networked Connection servers or clusters

Uses SMIME

Uses unencrypted
MIME


In the unrestricted version, if the disabled settings listed above are changed manually, Connection ignores the changes.

For the restricted version, "Restricted Installation" is included in the DVD label. For the unrestricted version, "Unrestricted Installation" is included in the DVD label and "UNRST" is included in the download filename.

Connection versions 7.1(5) and earlier were equivalent to what is now referred to as the restricted version.


Caution With restricted and unrestricted versions of Connection software available, download software or order a DVD carefully. Upgrading a restricted version to an unrestricted version is supported, but future upgrades are then limited to unrestricted versions. Upgrading an unrestricted version to a restricted version is not supported.

Note that other fixes and changes made in 7.1(5a) to the operating system, Connection, and/or Cisco Unified Communications Manager 7.1(5) application components—including components shared by Connection and Cisco Unified CM—are included in both the restricted and unrestricted versions.

For related information, see the following sections in these release notes:

"Cisco Unity Connection 7.1(5) Engineering Specials Earlier Than ES 18 Are Not Supported with 7.1(5a) or 7.1(5b)" section

"Supported Cisco Unity Connection Upgrades" section

"Related Caveats—Cisco Unified Communications Manager 7.1(5) Components That Are Used by Connection 7.1(5)" section.

Cisco Unity Connection Cluster Patch Required for Upgrades from 7.1(5) to 7.1(5a) or 7.1(5b)

Added September 22, 2010

If you are upgrading to 7.1(5a) or 7.1(5b) on the servers in a Cisco Unity Connection cluster and the servers are running Cisco Unified Communications Operating System version 7.1.5.10000-12, you must install the patch file ciscocm.cuc_cluster_715.cop.sgn before you upgrade Connection. The patch is available on Cisco.com, along with the upgrade files (see the "Downloading Software for an Upgrade to Cisco Unity Connection 7.1" section). For information about the patch, see the accompanying readme on the download page.

Phone System Integrations

For Cisco Unity Connection

For supported versions of Cisco Unified CM and Cisco Unified CM Express, see the applicable document, depending on the integration type:

SCCP Compatibility Matrix: Cisco Unity Connection, Cisco Unified Communications Manager, and Cisco Unified Communications Manager Express at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html.

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

For information on other supported phone system integrations, see the applicable Cisco Unity Connection integration guides at http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.html.

For Cisco Unity Connection in Cisco Unified CMBE

Cisco Unified Communications Manager 7.1 has been qualified for use with Cisco Unified CMBE. It is installed on the same platform with Cisco Unity Connection.

Selected Servers Require Replacement Hard Disks or Additional Memory for Some Configurations

If you are upgrading from Cisco Unity Connection 2.x or 1.x to Connection 7.1 and you want to reuse the current server, for some servers and some configurations you must replace hard disks or add memory. For example:

Some servers require replacement hard disks if you are configuring a Connection cluster.

Some servers require additional memory if voice recognition and Digital Networking are configured when the sum of contacts, users, distribution lists, locations, personal contacts, and personal distribution lists exceeds 2,000. (These are the first six items on the Tools > Grammar Statistics page in Cisco Unity Connection Administration.)

If you are upgrading an existing Connection server to version 7.1, see the Cisco Unity Connection Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html to determine whether your server requires replacement hard disks or additional memory.

For information on replacing the hard disks or adding the memory, see the applicable chapter in the Reconfiguration and Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.

Software Qualified for Use with Cisco Unity Connection on User Workstations

No additional software has been qualified for use with Cisco Unity Connection on user workstations with this release.

For the most current version combinations of software qualified for use on user workstations, 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.

Upgrades from Connection 7.1(5) to 8.0(x) Are Not Supported

Added May 7, 2010

Upgrading from Cisco Unity Connection version 7.1(5) to version 8.0(x) is not supported. To upgrade from Connection 7.1(5), you will need to wait for Connection 8.5 to be released, in late 2010.

Utility Updates on the Cisco Unity Tools Website

Updates to utilities on the Cisco Unity Tools website are frequently posted between Cisco Unity Connection 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 Connection. However, you can sign up to be notified when the utilities posted on the Cisco Unity Tools website are updated. Go to http://www.ciscounitytools.com, and click Sign Up Here.

For information on new utilities since the last Cisco Unity Connection release, see the following section:

Bulk Password Edit Tool Available for Assigning Unique Passwords and PINs to Multiple User Accounts at Once

New Functionality—Release 7.1(5)

This section contains information about new functionality in the 7.1(5) release time frame only.

(For information on new functionality in earlier versions of Cisco Unity Connection, see the applicable release notes at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html. Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.)

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

Bulk Password Edit Tool Available for Assigning Unique Passwords and PINs to Multiple User Accounts at Once

The Bulk Password Edit tool is used to assign unique passwords and PINs to Cisco Unity Connection end user accounts (users with mailboxes). When you create large numbers of user accounts, the passwords and PINs are determined by settings on the user template used to create the accounts. To avoid having identical passwords and/or PINs for all of the accounts, you use the Bulk Password Edit tool along with a CSV file that contains unique strings for the passwords and PINs to apply the passwords/PINs in bulk. This avoids the security risk of having multiple accounts with identical passwords/PINs until the users change them, or having to change them one at a time in Cisco Unity Connection Administration. (Passwords are for accessing the Cisco Personal Communications Assistant. PINs are for accessing the Cisco Unity Connection conversation by phone.)

The Bulk Password Edit tool is a Windows-based tool. Download the tool and view Help at http://www.ciscounitytools.com/Applications/CxN/BulkPasswordEdit/BulkPasswordEdit.html.


Note The Bulk Password Edit tool is not supported for use with Cisco Unified Communications Manager Business Edition.


Changed Functionality—Release 7.1(5)

There is no changed functionality in this release.

(For information on changed functionality in earlier versions of Cisco Unity Connection, see the applicable release notes at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html. Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.)

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

Installation and Upgrade Information

Information for Cisco Unified Communications Manager Business Edition Customers

Installing Cisco Unity Connection for the First Time

Supported Cisco Unity Connection Upgrades

Upgrading to Cisco Unity Connection 7.1

Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1

Installation and Upgrade Notes

Information for Cisco Unified Communications Manager Business Edition Customers

For instructions on installing a new Cisco Unified CMBE system, see Overview of Mandatory Tasks for Setting Up a Cisco Unified Communications Manager Business Edition 7.x System at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/cucmbe_task_list/7xcucmbetask.html and the Installing Cisco Unified Communications Manager Business Edition Release 7.1(2) guide at http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/install/7_1_2/cmins712.html.

For instructions on upgrading a Cisco Unified CMBE system, see the "Software Upgrades" chapter of the applicable version of the Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/ps7273/prod_maintenance_guides_list.html.

Note that when upgrade files are available for download on Cisco.com, the files can be used to upgrade Connection, Cisco Unified Communications Manager, or Cisco Unified CMBE. The files can be downloaded from the Connection or Cisco Unified CM downloads page. For download instructions from the Connection downloads page, see the "Downloading Software for an Upgrade to Cisco Unity Connection 7.1" section.


Caution If you are upgrading from Cisco Unified CMBE version 6.x or 7.0 and any languages other than U.S. English (ENU) are currently installed and in use on the 6.x or 7.0 server, you must install the Connection 7.1 versions of the same languages after the Cisco Unified CMBE upgrade. Otherwise, the Connection conversation will not function properly for users who are configured to use non-ENU languages. For information on downloading and installing languages, see the "Downloading Connection 7.x Language Files" and "Installing Connection 7.x Language Files" sections in the "Adding or Removing Cisco Unity Connection 7.x Languages" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.

There is no supported migration path from Connection 1.x to Cisco Unified Communications Manager Business Edition (CMBE). If you want to migrate from Connection 1.x to Cisco Unified CMBE, you must reinstall all software, and recreate all system and user data.

Installing Cisco Unity Connection for the First Time

You must use the Cisco Unity Connection DVD to install a new server.

For instructions on installing a new Connection server, see the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

Supported Cisco Unity Connection Upgrades

Revised July 20, 2010

Caution With restricted and unrestricted versions of Connection software now available, download software or order a DVD carefully. Upgrading a restricted version to an unrestricted version is supported, but future upgrades are then limited to unrestricted versions. Upgrading an unrestricted version to a restricted version is not supported. (See also the "Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions" section.)

You can upgrade directly to Connection 7.1(5b) from many but not all versions of Connection 2.x and later. For information on whether you can upgrade directly to Connection 7.1, see the "Supported Cisco Unified Communications Manager Upgrades" section of the Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.

You refer to the full version number of the Cisco Unified Communications Operating System that is currently installed on the active partition to determine upgrade support. The version can be viewed by running the CLI command show version active.

Full version numbers include the build number (for example, 7.1.5.10000-10); the software versions listed on the download pages on Cisco.com are abbreviated version numbers (for example, 7.1(5) ). In the tables of the "Supported Cisco Unified Communications Manager Upgrades" section of the compatibility matrix, full version numbers are listed in the System Version row.


Note Abbreviated version numbers for Connection and the Cisco Unified Communications Operating System are identical except that Connection 2.x versions correspond with 6.x versions of the operating system.


Do not refer to version numbers in any of the administration user interfaces because those versions apply to the interfaces themselves, not to the version of the product software installed on the active partition.

If you cannot upgrade directly from your current version to Connection 7.1(5b):

1. Find an intermediate version that is supported both for an upgrade from your current version and for an upgrade to 7.1(5b).

2. Upgrade to the intermediate version. See the applicable Reconfiguration and Upgrade Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_installation_guides_list.html.

3. Upgrade to Connection 7.1(5b). See the following section, "Upgrading to Cisco Unity Connection 7.1."

Upgrading to Cisco Unity Connection 7.1

Revised July 7, 2010

Caution With restricted and unrestricted versions of Connection software now available, download software or order a DVD carefully. Upgrading a restricted version to an unrestricted version is supported, but future upgrades are then limited to unrestricted versions. Upgrading an unrestricted version to a restricted version is not supported. (See also the "Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions" section.)

For instructions on downloading software that can be used to upgrade to Connection 7.1 from a supported version, see "Downloading Software for an Upgrade to Cisco Unity Connection 7.1" section.

For instructions on upgrading:

A Connection 7.x server to version 7.1, see the "Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.

A Connection 2.x server to version 7.1, see the "Upgrading Cisco Unity Connection 2.1(2) or Later to the Shipping 7.x Version" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.


Note If you are upgrading to version 7.1(5x) with the intention of upgrading later to version 8.x, you will need to wait for 8.5 to be released, in late 2010. Upgrading from version 7.1(5x) to version 8.0(x) is not supported.


Downloading Software for an Upgrade to Cisco Unity Connection 7.1

Revised April 02, 2012

The upgrade application posted on Cisco.com can be used only to upgrade to Cisco Unity Connection 7.1 from a supported 7.x or 2.x version. It cannot be used to install a new Connection 7.1 server, or to migrate from Connection 1.x to 7.1.

Because of the size of the upgrade application, the file has been divided into two parts. Do the following procedure to download the two parts and to recombine them into a single file.

To Download Software for an Upgrade to Cisco Unity Connection 7.1


Step 1 Log on to a computer with a high-speed Internet connection, and go to the Voice and Unified Communications Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.


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


Step 2 If you are installing the Connection 7.1(5) cluster patch: Download the file:

a. In the tree control on the Downloads page, expand Products>Voice and Unified Communications>IP Telephony>Unified Messaging>Cisco Unity Connection, and select Cisco Unity Connection Version 7.1.

b. On the Select a Software Type page, select Unified Communications Manager / CallManager / Cisco Unity Connection Utilities.

c. On the Select a Release page, select COP-Files, and the download buttons appear on the right side of the page.

d. Select the ciscocm.cuc_cluster_715.cop.sgn download, then follow the on-screen prompts to complete the download. Make note of the MD5 value.

Step 3 In the tree control on the Downloads page, expand Products>Voice and Unified Communications>IP Telephony>Unified Messaging>Cisco Unity Connection, and select Cisco Unity Connection Version 7.1.

Step 4 On the Select a Software Type page, select Unified Communications Manager / Cisco Unity Connection Updates.

Step 5 On the Select a Release page, select 7.1(5b) under Latest Releases or All Releases, and the download buttons appear on the right side of the page.


Caution With restricted and unrestricted versions of Connection software now available, download software carefully. Upgrading a restricted version to an unrestricted version is supported, but future upgrades are then limited to unrestricted versions. Upgrading an unrestricted version to a restricted version is not supported. (See also the "Cisco Unity Connection 7.1(5a)—Restricted and Unrestricted Versions" section.)

Step 6 Confirm that the computer you are using has sufficient hard-disk space for the downloaded files. (The download file sizes are included in the download descriptions.)

Step 7 Select the applicable link for the first part, then follow the on-screen prompts to complete the download, making note of the MD5 value:

Restricted version

UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part1of2

Unrestricted version

UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso_part1of2


Step 8 Select the applicable link for the second part, then follow the on-screen prompts to complete the download, making note of the MD5 value:

Restricted version

UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part2of2

Unrestricted version

UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso_part2of2


Step 9 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. The 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 10 Depending on the operating system, execute a command to reunite the two parts of the file:

On a Unix/Linux system, copy and paste the applicable command from this document into the CLI to combine the two files:

Restricted version
cat UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part1of2 
UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part2of2 > UCSInstall_UCOS_7.1.5.30000-1.sgn.iso
Unrestricted version
cat UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso_part1of2 
UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso_part2of2 > 
UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso

On a Windows system, copy and paste the applicable command from this document into the command prompt (cmd.exe) to combine the two files:

Restricted version
COPY /B 
UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part1of2+UCSInstall_UCOS_7.1.5.30000-1.sgn.iso_part
2of2 UCSInstall_UCOS_7.1.5.30000-1.sgn.iso
Unrestricted version
COPY /B 
UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso_part1of2+UCSInstall_UCOS_UNRST_7.1.5.30000-1.
sgn.iso_part2of2 UCSInstall_UCOS_UNRST_7.1.5.30000-1.sgn.iso

Step 11 Use a checksum generator to confirm that the MD5 checksum of the reunited file matches the applicable checksum:

Restricted version

272eee358eeb4d50dc1986cb54bb21fa

Unrestricted version

70bc09f55af32689211cd9c541d602fe


If the values do not match, the reunited file is damaged.


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

Step 12 If you are installing from a DVD, burn the DVD, noting the following considerations:

Choose the option to burn a disc image, not the option to copy files. Burning a disc image will extract the thousands of files from the .iso file that you created in Step 10 and write them to a DVD, which is necessary for the files to be accessible for the installation.

Use the Joliet file system, which accommodates filenames 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 13 Confirm that the DVD contains a large number of directories and files, not just the .iso file that you created in Step 10.

Step 14 Delete unnecessary files from the hard disk to free disk space, including the two .iso files that you downloaded and the combined .iso file that you created in Step 10.


Migrating from Cisco Unity or from Cisco Unity Connection 1.x to Cisco Unity Connection 7.1

For information on migrating from Cisco Unity 4.0(5) or later to Connection 7.1 or from Connection 1.x to Connection 7.1, see the applicable "Migrating from ..." chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.


Note There is no supported migration path from Connection 1.x to Cisco Unified Communications Manager Business Edition (CMBE). If you want to migrate from Connection 1.x to Cisco Unified CMBE, you must reinstall all software, and recreate all system and user data.


Installation and Upgrade Notes

Cisco Unity License Files Can Be Used for Migrations from Cisco Unity to Cisco Unity Connection and to Connection in Cisco Unified CMBE

Installing and Using Cisco Unity Connection Languages in Addition to U.S. English

License Tag Required to Enable the U.S. English Conversation and Personal Call Transfer Rules

Cisco Unity License Files Can Be Used for Migrations from Cisco Unity to Cisco Unity Connection and to Connection in Cisco Unified CMBE

Cisco Unity Connection and Connection in Cisco Unified CMBE can use Cisco Unity license files to enable Cisco Unity Connection features when migrating from Cisco Unity 4.x or later to Cisco Unity Connection 7.x or to Cisco Unified CMBE 7.x.

Note that the Cisco Unity license files must have the MAC address of the server on which Cisco Unity Connection is installed:

If Connection is installed on the same server on which Cisco Unity was installed, you can install the Cisco Unity license files.

If Connection is installed on a different server from the one on which Cisco Unity was installed, you must have the Cisco Unity license files reissued with the MAC address of the new server.

(See also the "Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Task List for Migrating from Cisco Unity 4.x or Later to Connection 7.x" section section under "Omissions.")

Installing and Using Cisco Unity Connection Languages in Addition to U.S. English

For instructions on installing additional Connection languages on the following server types, see the referenced documentation:

A new Connection server, see the "Installing Additional Languages on the Cisco Unity Connection 7.x System" chapter of the Installation Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.html.

An existing Connection server, see the "Adding Languages to the Cisco Unity Connection 7.x Server" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.

An existing Cisco Unified CMBE server, see the "Downloading Connection 7.x Language Files" and "Installing Language Files on the Connection 7.x Server" sections in the "Adding Languages to a Cisco Unity Connection 7.x Server" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.

If you are installing Japanese because you want Cisco Unity Connection Administration to be localized, you must also install the Cisco Unified Communications Manager Japanese locale. See the "Locale Installation" section in the "Software Upgrades" chapter of the applicable Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

If you are installing other languages because you want the Cisco Personal Communications Assistant to be localized, you must also install the corresponding Cisco Unified Communications Manager locales. See the "Locale Installation" section in the "Software Upgrades" chapter of the applicable Cisco Unified Communications Operating System Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

If you are using Connection languages other than U.S. English, note the following considerations:

Connection 7.1(5) was not localized, but you can use the languages that were released with Connection 7.1(2) with Connection 7.1(5).

If you are upgrading from Connection 7.1(2), you do not need to reinstall languages. During the upgrade, the languages currently installed on the Connection 7.1(2) partition are automatically copied to the 7.1(5) partition.

If you are upgrading from an earlier version of Connection, you need to download and install Connection 7.1(2) languages.

Any changes and additions to web applications and to conversation prompts in Connection 7.1(5) are not available in the version 7.1(2) languages.

License Tag Required to Enable the U.S. English Conversation and Personal Call Transfer Rules

If you want to use English-United States for the Cisco Unity Connection conversation or you want users to be able to create personal call transfer rules, the Connection license must include the license tag LicRegionIsUnrestricted. If one of your Connection licenses does not include the LicRegionIsUnrestricted tag and you want to use the U.S. English Usage and Personal Call Routing Rules Allowed (LicRegionIsUnrestricted) feature, you must install a license that includes the tag. After you install the license, you must restart Connection. (Licenses without this tag are intended only for use outside the United States.)

If you choose not to install a license that enables the U.S. English Usage and Personal Call Routing Rules Allowed (LicRegionIsUnrestricted) feature, you must install one or more Connection languages.

Connection demonstration licenses enable the U.S. English Usage and Personal Call Routing Rules Allowed (LicRegionIsUnrestricted) feature, so you can use English-United States on demonstration systems.

To Determine Whether the U.S. English Conversation and Personal Call Transfer Rules Are Enabled


Step 1 In Cisco Unity Connection Administration, under System Settings, click Licenses.

Step 2 On the Licenses page, under the License Count table, locate the U.S. English Usage and Personal Call Routing Rules Allowed (LicRegionIsUnrestricted) feature.

Step 3 If the value of this feature is "Yes," the U.S. English conversation and personal call transfer rules are enabled.

If the value of this feature is "No," the U.S. English conversation and personal call transfer rules are not enabled.

Step 4 If the U.S. English Usage and Personal Call Routing Rules Allowed (LicRegionIsUnrestricted) feature is not enabled, obtain a license that contains the LicRegionIsUnrestricted tag before you install Connection.


Important Notes

Connection IMAP Server Service Should Not Be Stopped or Disabled for an Extended Period of Time

Added October 18, 2010

The Connection IMAP Server service processes events that are placed in the IMAP queue table in the Connection database when voice messages are created, updated, or deleted, even if you do not have active IMAP users. If the service is disabled or stopped, the table continues to grow, and can eventually fill available disk space and cause database instability. Do not stop the service for more than a day at a time or disable the service indefinitely. If you have previously stopped or disabled the service, try restarting the service. If the service does not start, contact Cisco TAC to apply the workaround for caveat CSCti68395.

Limitations and Restrictions

Connection Cannot Be Installed or Operated in IPv6 or Dual-Stack (IPv4 and IPv6) Networks

Revised November 9, 2010

Connection 7.1 does not support IPv6, and cannot be installed or operated in a pure IPv6 network. To install or operate in a dual-stack (IPv4 and IPv6) network, a workaround for CSCtj93659 is required. See the caveat information for CSCtj93659 for more details.

In Connection Cluster, Changed License Data on One Server Does Not Replicate to Other Server

When a new or changed license file is installed on one server of a Cisco Unity Connection cluster, the changed license data is not automatically replicated to the other server.

To replicate the changed license data, you must restart both Connection servers by using the CLI command utils system restart.

Media Master Cannot Open WAV Files Saved on a Workstation in G.729a Format

The Media Master cannot open WAV files prerecorded in the G.729a audio format and saved to a workstation.

This limitation has the following workarounds:

Convert the WAV file to another audio format (for example, convert it to the G.711 audio format).

Use a WAV file that is recorded in a supported audio format other than G.729a.

Make the recording by using a phone or a computer microphone.

Note that when Cisco Unity Connection is configured to record in the G.729a audio format, the Media Master functions correctly for recording and playing by using a phone or a computer microphone.

Replacing Disks in a RAID

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

The Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x does not include any information on replacing disks in a RAID array. However, because Connection and Cisco Unified Communications Manager mostly use the same servers, you can use the procedures in the "Performing Failed RAID Disk Replacement" section of the "Cisco Unified Communications Manager System Issues" chapter of the Troubleshooting Guide for Cisco Unified Communications Manager, Release 7.1(2) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/trouble/7_1_2/tbsystem.html.

ViewMail Limitations Regarding Secure Messages

Secure messages cannot be forwarded by using Cisco Unity Connection ViewMail for Microsoft Outlook or ViewMail for IBM Lotus Notes.

ViewMail for Outlook and ViewMail for Notes support only playing secure messages.

Messages that are composed or replied to by using ViewMail for Outlook or ViewMail for Notes are not sent as secure, even when users are assigned to a class of service for which the Require Secure Messaging field is set to Always or to Ask.

Caveats

You can find the latest caveat information for Cisco Unity Connection version 7.1(5) and for Connection in Cisco Unified Communications Manager Business Edition version 7.1(5) 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.


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


This section contains the following caveat information:

Open Caveats—Connection Release 7.1(5), and Connection in Cisco Unified CMBE Release 7.1(5)

Related Caveats—Cisco Unified Communications Manager 7.1(5) Components That Are Used by Connection 7.1(5)

Release notes for all versions of Cisco Unity Connection are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.

Release notes for all versions of Cisco Unified Communications Manager Business Edition are available at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html.

Open Caveats—Connection Release 7.1(5), and Connection in Cisco Unified CMBE Release 7.1(5)

This section list any Severity 1, 2, and 3 open caveats when Cisco Unity Connection version 8.0(2) 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 1 Connection Release 7.1(5) and Connection in Cisco Unified CMBE 7.1(5) Open Caveats 

Caveat Number
Component
Severity
Description

CSCtf11682

database

2

Connection database DbHelper may not connect to primary without warning

CSCtf73231

database

2

UC 7.x - Digital Networking Certificates Get Wiped During Replication

CSCtd79132

admin

3

UC 7.x - UC Administrator "Login Failed" or "Pool Exhausted"

CSCtg20383

config

3

Can't prepend an asterisk to the dialed extensions in Call Handlers

CSCtf73028

conversations

3

UC: "Validate Server Certificate" fails on self signed certificates

CSCtf52047

documentation

3

Outbound routing rule needs to be corrected in PIMG- CUC documentation

CSCsy32272

messaging

3

Connectivity loss to Primary may result in temporary call failures

CSCtg09959

messaging

3

CuMTA not delivering new messages due to leaking file handles

CSCtd95261

pca

3

PCA+IE7: try to add members, no users are displayed


Related Caveats—Cisco Unified Communications Manager 7.1(5) Components That Are Used by Connection 7.1(5)

Revised July 20, 2010

Table 2 describes the Cisco Unified Communications Manager components that are used by Cisco Unity Connection.

Caveat information for the Cisco Unified CM components is available in the following documents:

Release Notes for Cisco Unified Communications Manager Release 7.1(5b) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_1_5/cucm-rel_notes-715b.html.

Release Notes for Cisco Unified Communications Manager Release 7.1(5a) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_1_5/cucm-rel_notes-715a.html.

Release Notes for Cisco Unified Communications Manager Release 7.1(5) at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_1_5/cucm-rel_notes-715.html.

Table 2 Cisco Unified CM 7.1(5) Components That Are Used by Connection 7.1(5) 

Cisco Unified CM Component
Description

backup-restore

Backup and restore utilities

ccm-serviceability

Cisco Unified Serviceability web interface

cdp

Cisco Discovery Protocol Drivers

cli

Command-line interface (CLI)

cmui

Certain elements in the Connection web interfaces (such as search tables and splash screens)

cpi-afg

Cisco Unified Communications Answer File Generator

cpi-appinstall

Installation and upgrades

cpi-cert-mgmt

Certificate management

cpi-diagnose

Automated diagnostics system

cpi-os

Cisco Unified Communications Operating System

cpi-platform-api

Abstraction layer between the Cisco Unified Communications Operating System and the applications hosted on the platform

cpi-security

Security for connections to the server

cpi-service-mgr

Service Manager (ServM)

cpi-vendor

External vendor issues

cuc-tomcat

Apache Tomcat and third-party software

database

Installation and access to the configuration database (IDS)

database-ids

IDS database patches

ims

Identity Management System (IMS)

rtmt

Real-Time Monitoring Tool (RTMT)


Documentation Updates

Errors

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

Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Traps and Informs

In the "SNMP Traps and Informs" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the first note (after the first paragraph) should read as follows:


Note Cisco Unified Communications Manager, Cisco Unified Communications Manager Business Edition, and Cisco Unity Connection support SNMP traps.


System Administration Guide for Cisco Unity Connection: Creating a Calendar Integration with Exchange 2007

Added July 9, 2010

The "Creating a Calendar Integration with Exchange 2007" section in the "Creating Calendar Integrations" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x (at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html) incorrectly indicates that you can do a calendar integration with Exchange 2007 Server. Calendar integrations with Exchange 2007 Server are no longer supported in Cisco Unity Connection 7.1(5) and 7.1(5a).

Note however that contact and text to speech integrations are still supported with Exchange 2007 Server.

Omissions

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

Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Services

In the "SNMP Services" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following row was omitted from Table 15-2, "SNMP Services."

Table 3 SNMP Services 

MIB
Service
Window

CISCO-UNITY-MIB

Connection SNMP Agent

Cisco Unity Connection Serviceability > Tools > Service Management. Choose a server; then, choose Base Services category.


Cisco Unified Serviceability Administration Guide Release 7.1(2): SNMP Management Information Base (MIB)

In the "SNMP Management Information Base (MIB)" section in the "Understanding Simple Network Management Protocol" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following section was omitted.

CISCO-UNITY-MIB

The CISCO-UNITY-MIB uses the Connection SNMP Agent to get information about Cisco Unity Connection.

To view the CISCO-UNITY-MIB definitions, go to the following link and click SNMP V2 MIBs:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


Note Cisco Unity Connection supports this MIB. Cisco Unified Communications Manager does not support this MIB.


The Connection SNMP Agent supports the following objects.

Table 4 Cisco-unity-MIB Objects 

Object
Description

ciscoUnityTable

This table contains general information about the Cisco Unity Connection servers such as host name and version number.

ciscoUnityPortTable

This table contains general information about the Cisco Unity Connection voice messaging ports.

General Unity Usage Info objects

This group contains information about capacity and utilization of the Cisco Unity Connection voice messaging ports.


Cisco Unified Serviceability Administration Guide Release 7.1(2): Configuring CISCO-UNITY-MIP Trap Parameters

In the "Configuring SNMP Trap/Inform Parameters" chapter of the Cisco Unified Serviceability Administration Guide Release 7.1(2), the following text should be included as the "Configuring CISCO-UNITY-MIB Trap Parameters" section.

Connection only: The Connection SNMP Agent does not enable trap notifications, though traps can be triggered by Cisco Unity Connection alarms. You can view Cisco Unity Connection alarm definitions in Cisco Unity Connection Serviceability, on the Alarm > Definitions screen.

You can configure trap parameters by using the CISCO-SYSLOG-MIB. See the "Configuring CISCO-SYSLOG-MIB Trap Parameters" section.

Interface Reference Guide for Cisco Unity Connection Administration Release 7.x: Messaging Configuration (Cisco Unity Connection 7.1)

In the "Messaging Configuration (Cisco Unity Connection 7.1)" section in the "Advanced Settings" chapter of the Interface Reference Guide for Cisco Unity Connection Administration Release 7.x, the following rows were omitted from Table 11-5, "Messaging Configuration Page."

Table 5 Messaging Configuration Page 

Field
Description

Use Access Lists to Control Who Can Send to System Distribution Lists

Check this check box so that Cisco Unity Connection uses a group of users defined in an access list to limit the users who can send messages to a system distribution list. For each system distribution list that receives messages, you create a second distribution list with an alias comprised of the alias of the original list plus a suffix that is defined in the System Distribution List Alias Suffix for Access Lists field. For example, to set up an access list for a system distribution list that has the alias allvoicemailusers, if the value in the System Distribution List Alias Suffix for Access Lists field is -accesslist, you would create a second system distribution list with the alias allvoicemailusers-accesslist, and add as members of the access list any users who need to be able to send messages to allvoicemailusers. Note that users who are members of the access list must also have their search scope set to a search space that includes the partition of the system distribution list in order to address messages to the list.

Uncheck this check box so that Connection does not restrict access to system distribution lists. When this check box is not checked, Connection allows any users whose search space includes the partition of a distribution list to send messages to the list.

Default setting: Check box not checked.

Allow Delivery of Messages to System Distribution Lists That Have No Access List

Check this check box so that Cisco Unity Connection allows messages to be delivered to system distribution lists that do not have an access list created for them.

Uncheck this check box to have Connection reject all messages sent to system distribution lists that do not have an access list created for them, and send a nondelivery receipt (NDR) to the message sender.

This setting has no effect when the Use Access Lists to Control Who Can Send to System Distribution Lists check box is not checked.

Default setting: Check box not checked.

System Distribution List Alias Suffix for Access Lists

Enter a text suffix that Cisco Unity Connection uses to match an access list to the system distribution list that it controls. For example, to set up an access list for a system distribution list that has the alias allvoicemailusers, if the value in the System Distribution List Alias Suffix for Access Lists field is -accesslist, you would create a second system distribution list with the alias allvoicemailusers-accesslist, and add as members of the access list any users who need to be able to send messages to allvoicemailusers.

This setting has no effect when the Use Access Lists to Control Who Can Send to System Distribution Lists check box is not checked.

Default setting: -accesslist.


Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Replacing a 7.x Publisher Server in a Connection Cluster

In the "Replacing Cisco Unity Connection 7.x Servers" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x, the caution text below should be included in the following locations:

In the "Replacing a 7.x Publisher Server in a Connection Cluster" section in the caution in the "To Install the Replacement Publisher Server" procedure.

In the "Replacing the 7.x Publisher and Subscriber Servers in a Connection Cluster" section, in the "When Both Original Servers Are Available and Functioning" subsection, in the caution in the "To Install the Replacement Publisher Server" procedure.


Caution The replacement publisher server must have the same security password as the publisher server that you removed, which also matches the security password for the subscriber server. Otherwise, the Connection cluster will not be able to function. If you do not know the security password, you can change it on the subscriber server before you install the publisher server by using the set password user CLI command. For more information, see the applicable version of the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.

Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x: Task List for Migrating from Cisco Unity 4.x or Later to Connection 7.x

In the "Task List for Migrating from Cisco Unity 4.x or Later to Connection 7.x" section in the "Migrating from Cisco Unity 4.x or Later to Cisco Unity Connection 7.x" chapter of the Reconfiguration and Upgrade Guide for Cisco Unity Connection Release 7.x, Task 2 omitted some information and should be replaced with the following two tasks:

2. Copy or obtain reissued Cisco Unity license files, depending on the type of server you are installing:

Reusing current Cisco Unity server
rather than installing a new server

Copy the Cisco Unity license files to a network location. Do not install the license files now; you do so later in the migration process.

Installing a new server

a. Obtain reissued Cisco Unity license files with the MAC address of the new Cisco Unity Connection server. See the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

b. Save the reissued license files to a network location. Do not install the license files now; you do so later in the migration process.


3. Obtain a Cisco Unity Connection 7.x migration license file with the applicable MAC address, then save the file to a network location. Do not install the license file now; you do so later in the migration process.

See the "Managing Licenses" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/administration/guide/7xcucsagx.html.

System Administration Guide for Cisco Unity Connection Release 7.x: Using Advanced Settings to Enable System Distribution List Access Lists

The following content should be included as the "Using Advanced Settings to Create System Distribution List Access Lists" section in the "Managing System Distribution Lists" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x.

You can use search spaces and partitions to control who can send messages to system distribution lists—for example, you create a new partition called "Distribution Lists Partition," configure the lists that you want to control to use this partition, and assign a search space that includes this partition to users who have permission to send to the lists. However, if you have a large number of lists that each have a specific subset of users who are authorized to send messages to them, the search space approach may not scale well, and you may reach the limit on the number of partitions and search spaces that you can create on the server. As an alternative approach, you can configure advanced settings that allow you to set up individual access lists for each system distribution list that you want to control.

When you enable the access list feature, for each system distribution list that receives messages, you create a second system distribution list with an alias that is created from the alias of the original list plus a suffix that identifies the list as an access list. For example, to set up an access list for a system distribution list that has the alias allvoicemailusers, if the suffix is -accesslist, you create a second system distribution list with the alias allvoicemailusers-accesslist, and add as members of the access list any users who need to be able to send messages to allvoicemailusers. Note that users who are members of the access list must also have their search scope set to a search space that includes the partition of the system distribution list in order to address messages to the list.

Use the following task list to set up system distribution list access lists:

1. Configure the advanced settings that enable and control the access lists. Do the "To Enable and Configure System Distribution List Access Lists" procedure. If you are using Digital Networking to connect multiple Connection servers, do this task on all of the servers.


Caution In a digital network, the values for the advanced settings that enable and control access lists must be configured identically on each location in the network in order for access lists to function properly.

2. For each system distribution list that you want to control with an access list, create a new system distribution list with an alias that is created from the alias of the original list plus a suffix that is defined in the System Distribution List Alias Suffix for Access Lists field. See the "Creating System Distribution Lists" section in the "Managing System Distribution Lists" chapter of the System Administration Guide for Cisco Unity Connection Release 7.x.


Tip The Connection Distribution List Builder tool can be used to bulk add users to a new or existing system distribution list based on a number of search criteria or by importing from a comma-separated value (CSV) file. Download the latest version, and view training videos and Help at http://www.ciscounitytools.com/APP_PDLBuilder_Linux.htm.


To Enable and Configure System Distribution List Access Lists


Step 1 In Cisco Unity Connection Administration, expand System Settings, expand Advanced, then click Messaging.

Step 2 To enable system distribution list access lists, check the Use Access Lists to Control Who Can Send to System Distribution Lists check box. (This check box is unchecked by default.)

Step 3 To have Cisco Unity Connection continue to allow messages to be sent to system distribution lists that do not have access lists created for them, check the Allow Delivery of Messages to System Distribution Lists That Have No Access List check box. Uncheck this check box to have Connection reject all messages sent to system distribution lists that do not have an access list, and send a non-delivery receipt (NDR) to the message sender.

Step 4 To specify the suffix that is used to distinguish access lists, enter a suffix in the System Distribution List Alias Suffix for Access Lists field. The default suffix is -accesslist.

Step 5 Click Save.


Troubleshooting Information

Cisco Unity Connection troubleshooting information can be found in the Troubleshooting Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/troubleshooting/guide/7xcuctsgx.html.

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.