Upgrade Guide for Cisco Unity Connection Release 10.x
Upgrading Cisco Unity Connection 7.x, 8.0, or 8.5 to the Shipping 10.x Version
Downloads: This chapterpdf (PDF - 483.0KB) The complete bookPDF (PDF - 4.84MB) | Feedback

Table of Contents

Upgrading Cisco Unity Connection 7.x, 8.0, or 8.5 to the Shipping 10.x Version

About Upgrades to Unity Connection 10.x

Status of Unity Connection Features During an Upgrade from Unity Connection7.x, 8.0, and 8.5 to Unity Connection10.x

Features You Must Reconfigure When You Upgrade to Unity Connection10.x

Duration of an Upgrade Unity Connection 7.x, 8.0 and 8.5 to Unity Connection 10.x

Migrating Licenses to Cisco Unity Connection 10.x

Migrating Licenses from Cisco Unity to Unity Connection 10.x

Migrating Licenses from Cisco Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x

Using COBRAS Tool

Using Upgrade Process

Task List for Upgrading Unity Connection7.x, 8.0 or 8.5 Software to the Shipping 10.x Version Without a Unity Connection Cluster

Task List for Upgrading Unity Connection7.x, 8.0, or 8.5 Software to the Shipping 10.x Version in a Unity Connection Cluster

Installing the Cisco Option Package Required to Upgrade from Unity Connection7.x, 8.0 or 8.5 to the Shipping 10.x Version

Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping10.x Version from a Local DVD

Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping10.x Version from a Network Location

Upgrading Cisco Unity Connection 7.x, 8.0, or 8.5 to the Shipping 10.x Version

This chapter contains the following sections:

About Upgrades to Unity Connection 10.x


Note The following considerations about upgrading from Unity Connection 7.x, 8.0, or 8.5 to version 10.x:

  • If you have never upgraded the Unity Connection server before, the upgrade copies the new version to an empty partition.
  • If you have upgraded the Unity Connection server before, the upgrade copies the new version to the inactive partition, which usually contains a version of Unity Connection older than the version that is running on the active partition. (If you previously upgraded to a later version and then reverted to the older version, the inactive partition includes a version of Unity Connection later than the version that is currently running.) The software that was on the inactive partition before you started the upgrade is overwritten.
  • Depending on your current version, you may be required to upgrade twice to reach the desired version. In that case, the current version is no longer available when the upgrade is complete because the partition that contains the current version will be overwritten by the second upgrade.
  • Depending on the data size, switching to the upgraded software may requires some time.

Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0, and 8.5 to Unity Connection 10.x

During an upgrade from Unity Connection 7.x, 8.0, and 8.5 to Unity Connection 10.x, if you do not have a cluster, Unity Connection is completely disabled for the entire duration of the upgrade.

If you are upgrading a cluster, the upgrade starts on the publisher server. Unity Connection functionality on the publisher server is completely disabled for the entire duration of the upgrade. Note the following about the functionality that is available on the subscriber server while the publisher server is being upgraded:

  • If the phone system is routing calls to the subscriber server, outside callers and Unity Connection users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
  • Unity Connection users can use the telephone user interface (touchtone conversation ) to listen to messages that are left before you start the upgrade. However, users cannot listen to messages that are left during the upgrade, and Unity Connection will not always retain the status of messages. For example, if a user plays a voice message during the upgrade, the message may be marked as new again after the upgrade. If a user deletes a message, the message may reappear after the upgrade.
  • Unity Connection users cannot access Unity Connection using graphical user interfaces, for example, ViewMail for Outlook, Web Inbox, or IMAP email applications.
  • If Unity Connection users use the touchtone conversation to change their user preferences or other settings during the upgrade, their changes will probably be lost. (There are brief periods during the upgrade when changes are saved, but identifying those periods is difficult at best.)
  • Administration user interfaces, for example, Connection Administration, Cisco Unity Connection Serviceability, and Cisco Unified Operating System Administration are not available. In addition, custom administration interfaces that were developed by using the Unity Connection administration API are also not available.
  • Intrasite and intersite networking is disabled for the duration of the upgrade. Directory changes made on other nodes in the network are not replicated to the server or cluster that you are upgrading until the upgrade is complete.

When the upgrade of the publisher server is complete, full functionality is restored on the publisher server.

When you start the upgrade on the subscriber server in a cluster:

  • Messages that were left on the subscriber server are copied to the publisher server, and the publisher server begins to deliver the messages to user mailboxes.
  • Unity Connection functionality on the subscriber server is completely disabled for the entire duration of the upgrade.

While the subscriber server is being upgraded, messages that are left on the publisher server are delivered to user mailboxes on the publisher server. When the upgrade of the subscriber server is complete, the messages are replicated to the subscriber server and are delivered to user mailboxes on the subscriber server. If single inbox is configured, messages are synchronized to Exchange after they are delivered to user mailboxes. If a large number of messages were left during the upgrade, there may be a significant delay before message delivery, replication, and synchronization with Exchange.

Features You Must Reconfigure When You Upgrade to Unity Connection 10.x

If you are upgrading from Unity Connection 7.x and 8.0 to Unity Connection 10.x, you must reconfigure the following features that are now among the features in Unity Connection unified messaging:

  • Accessing Exchange email by using text to speech.
  • Accessing Exchange calendars by phone, which allows you to hear a list of upcoming meetings, send a message to the meeting organizer or the meeting participants, and so on.
  • Importing Exchange contacts, which can be used in Unity Connection personal call transfer rules and when users place outgoing calls by using voice commands.
  • You must install all provided licenses on Cisco Unity Connection 7.x, 8.0, or 8.5 before you upgrade.

If you are upgrading from Unity Connection 8.0 or earlier and if Unity Connection is accessing Exchange email, calendars, or contacts, the features stop working until you reconfigure them. The task list tells you when in the upgrade process to reconfigure these features.

Duration of an Upgrade Unity Connection 7.x, 8.0 and 8.5 to Unity Connection 10.x

Under ideal conditions, upgrading a non-clustered Unity Connection server will take four hours or longer. Under less than ideal conditions, for example, if you are upgrading from a network drive over a slow network connection, an upgrade could take several hours longer. Upgrading both servers in a cluster will take roughly twice as long as upgrading a non-clustered server.


Caution Cisco Unity Connection 10.0(1) and later releases can only be installed on virtual machines. Physical servers are not supported to install or upgrade Unity Connection 10.0(1) and later, and an attempt to install or upgrade Unity Connection 10.x on physical servers will fail.


Note By default, when users delete Unity Connection voice messages, the messages are moved to the Unity Connection deleted items folder, which is also exported during the upgrade. (Messages are moved to the deleted items folder regardless of how the users deleted the messages, for example, the telephone user interface, the Cisco Unity Inbox, or an email application when IMAP access to Unity Connection is configured.) If Unity Connection is configured to move deleted messages to the deleted items folder, users must delete messages and also empty their Unity Connection deleted items folder to reduce the number of messages that are exported during the upgrade.


Migrating Licenses to Cisco Unity Connection 10.x

You need to upgrade licenses while migrating from Cisco Unity or from the earlier versions of Cisco Unity Connection to Unity Connection 10.x. For more information, see the following sections:

Migrating Licenses from Cisco Unity to Unity Connection 10.x

Migrating licenses from Cisco Unity to 10.x involves exporting of legacy license information from Cisco Unity and importing the exported data to Unity Connection 10.x. The legacy license information from Cisco Unity is exported to the computer through the export tool of COBRAS. For more information on COBRAS export tool, refer to http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html link . The exported data is further imported in Unity Connection 10.x and is stored in Unity Connection 10.x database.

After the completion of importing of legacy license information, Unity Connection 10.x needs to be configured and synchronized with the ELM server. For more information, refer to the ELM User Guide at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_1_1/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91_chapter_01.html.

Once synchronization is done at ELM server, the legacy license information from Unity Connection 10.x is sent to the ELM server for migration. Now, you can migrate licenses through the ELM server. For more information in migrating licenses through the ELM server, refer to the "Migrate licenses using Upgrade Licenses wizard" section of ELM User Guide.

Migrating Licenses from Cisco Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x

You can use either of the following methods to migrate licenses from Cisco Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x:

  • Using COBRAS tool
  • Using Upgrade Process

Using COBRAS Tool

You can use COBRAS tool to migrate licenses from Cisco Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x.


Caution You must install all provided licenses on Cisco Unity Connection 7.x, 8.0, or 8.5 before you export the data as only installed license data will be migrated.

Steps for migrating licenses from Cisco Unity Connection 7.x, 8.0, or 8.5 to Cisco Unity Connection 10.x


Step 1 Start the COBRAS export tool.

Step 2 Navigate to License Details for Migration to Unity Connection 10.x and later field under Backup Options tab. Select the License Details for migration to Unity Connection 10.x and later check box on Backup Options tab for exporting the legacy license data from Cisco Unity. A pop up appears.

Step 3 Enter the CLI credentials and click OK.

Step 4 Browse to the backup location for exporting the legacy license data under select Backup Destination tab.

Step 5 Click on the Export Data tab to export the legacy license data.


Note Similarly, you can use COBRAS import tool to import the backup to Unity Connection 10.x. When the backup data is imported in Unity Connection 10.x, the legacy license information is stored in Unity Connection 10.x database. For more information on COBRAS tools, refer to http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html link.


After the completion of uploading of legacy license information, Unity Connection 10.x needs to be configured and synchronized with the ELM server. For more information, refer to the ELM User Guide at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_1_1/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91_chapter_01.html.

Once synchronization is done at ELM server, the legacy license information from Unity Connection 10.x is sent to the ELM server for migration. Now, you can migrate licenses through the ELM server. For more information in migrating licenses through the ELM server, refer to the "Migrate licenses using Upgrade Licenses wizard" section of ELM user guide.

Using Upgrade Process

If you are upgrading from Cisco Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x, during the upgrade, the legacy license information of the previous version is uploaded to Unity Connection 10.x database. After the completion of upgrade process, Unity Connection 10.x needs to be configured and synchronized with the ELM server. For more information, refer to the ELM User Guide at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/elmuserguide/9_1_1/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91/CUCM_BK_EDEFFAEB_00_enterprise-license-manager-user-91_chapter_01.html.

Once Unity Connection 10.x is configured with the ELM server, the legacy information is sent to the ELM server. Now, you can migrate licenses through the ELM server. For more information in migrating licenses through the ELM server, refer to the "Migrate licenses using Upgrade Licenses wizard" section of ELM user guide.


Warning If you are upgrading from 7.x, 8.0, or 8.5, you must install the licenses to upgrade to Cisco Unity Connection release 10.x as only the installed license informtation is considered as legacy license data to migrate licenses. After you upgrade to Release 10.x, you can not apply pre 10.x licenses to Cisco Unity Connection 10.x and you can not apply them using the Enterprise License Manager.


Task List for Upgrading Unity Connection 7.x, 8.0 or 8.5 Software to the Shipping 10.x Version Without a Unity Connection Cluster

Revised April 20, 2014


Note In case of a fresh install, you must order physical DVDs because the software that you download from Cisco.com cannot be used for a new install


Do the following tasks to upgrade an existing Unity Connection 7.x, 8.0, or 8.5 server to the shipping 10.x version when no Unity Connection cluster is configured.

1. Cisco Unity Connection 10.0(1) and later releases are installed on only virtual machine. Physical servers are not supported to be installed on Unity Connection 10.0(1) and later releases, and any attempt to install Unity Connection 10.0(1) an later on physical servers will fail. For more information on migrating physical server to virtual machine see, the “Migrating to a Unity Connection 10.x Virtual Machine” chapter at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrug025.html .

2. Review the list of features that are disabled or that have limited functionality during the upgrade. See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0, and 8.5 to Unity Connection 10.x” section.

3. Review the list of features that stop working until you reconfigure them. See the “Features You Must Reconfigure When You Upgrade to Unity Connection 10.x” section.

4. See the applicable version of Release Notes for Cisco Unity Connection for any additional information on upgrading to the shipping version. In particular, note the items in the “Installation and Upgrade Information” section. Release notes are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

5. Install the licenses on the existing Unity Connection server before you upgrade to Unity Connection 10.x server. While upgrade, the legacy license information is uploaded in Unity Connection database. See the “Migrating Licenses to Cisco Unity Connection 10.x” section. For more information on Cisco Unity Connection 10.x Licenses, see the “Managing Licenses in Cisco Unity Connection” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html .

6. Confirm that you have the software required for the upgrade. Note the following:

  • You must download the ciscocm.refresh_upgrade.cop (Cisco Option Package) file from cisco.com.
  • You must download both the ciscocm.refresh_upgrade.cop and ciscocm.version3-keys.cop (Cisco Option Package) files from cisco.com, when upgrading to Unity Connection 10.5(1).

For information on downloading the .cop file from Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

  • If you are replacing the Unity Connection server and the server is currently running Unity Connection 7.0(1) through 7.1(2), you will also need Unity Connection 7.1(3) software. However, not all Unity Connection 7.x versions earlier than 7.1(3) can be directly upgraded to Unity Connection 7.1(3), so you may also need software for an intermediate version that can be upgraded directly to Unity Connection 7.1(3). For information on supported upgrades, see the “Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html .

Unity Connection 7.1(3) software is required for two reasons. First, some older servers are not supported for use with Unity Connection 8.x, and an attempt to install or upgrade to Unity Connection 8.x on these older servers will fail. In addition, Unity Connection software earlier than version 7.1(3) does not include the drivers required by the new servers. This means you cannot install Unity Connection earlier than version 7.1(3) on a new server, move data to the new server by using the Disaster Recovery System, and then upgrade the new server to Unity Connection 10.x.

  • If you are upgrading a virtual server, you can download the software for the upgrade from Cisco.com. For information on downloading the software from Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .
  • If you are not replacing the server, you may still need software for an upgrade to an intermediate version before you can upgrade to Unity Connection 10.x. For information on supported upgrades, see the “Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html .

7. If the Unity Connection server has languages other than English-United States installed and you want to continue using the languages : Download the applicable Unity Connection 10.x language files. See the Downloading Unity Connection 10.x Language Files .


Caution When languages other than English-United States are installed and in use on the Unity Connection server, you must install the Unity Connection 10.x versions of the same languages after the upgrade. Otherwise, the Unity Connection conversation will not function properly for all users.

8. If an intermediate upgrade is required as described in Task 6.: Upgrade Unity Connection as necessary. For information on how to upgrade from Unity Connection 7.x to a later version of Unity Connection 7.x, see the “ Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version ” chapter in the 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 .

Do not install the Unity Connection 10.x license files on the Unity Connection 7.x server.


Caution If the intermediate upgrade includes a major-version upgrade (for example, from 2.x to 7.x), you must complete the upgrade to Unity Connection 10.x before Unity Connection will function again. If you want 2.x license data to be sent to 10.x as legacy license information, you must obtain and install upgrade licenses for the intermediate upgrade.

9. If you are upgrading from Unity Connection 7.x, you are using the current server for Unity Connection 10.x:

a. Back up the server by using the Disaster Recovery System. For more information, see the Disaster Recovery System Administration Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7xcucdrsag.html .

b. Reinstall the version of Unity Connection that was installed when you backed up the server in Task 9.a. 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 .

c. Restore data on the server by using the DRS backup that you made in Task 9.a.

d. Skip to Task 12.

10. If you are upgrading from Unity Connection 7.x and replacing the Unity Connection server: Replace the server. See the “Replacing a Single 7.x Server Without a Unity Connection Cluster” section in the “ Replacing Cisco Unity Connection 7.x Servers ” chapter in the 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 .

11. If you do not have a backup of the existing server: Back up the server by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

12. On the Unity Connection server, install the Cisco Option Package that is required for the upgrade to Unity Connection 10.x. (This is the Cisco Option Package that you downloaded in Task 6.) See the “Installing the Cisco Option Package Required to Upgrade from Unity Connection 7.x, 8.0 or 8.5 to the Shipping 10.x Version” section.

13. Install Unity Connection 10.x languages, if applicable. See the Installing Unity Connection 10.x Language Files

If you are installing Japanese and you want Cisco Unity Connection Administration to be localized, you must also install the Cisco Unified Communications Manager Japanese user 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 and you want the Cisco Personal Communications Assistant to be localized, you must also install the corresponding Cisco Unified Communications Manager user 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 .

14. Upgrade the Unity Connection software. See the applicable section:


Note After the successful completion of upgrade process, if you want to enable the Tenant Partitioning feature then delete all the users (except default users) from Unity Connection. Make sure that you take the backup of your system using COBRAS before deleting all the users.


15. After the successful upgrade to Unity Connection 10.0(1), make sure that you restart your system using the CLI command utils system restart. For more information, see the applicable section in 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

16. If you are upgrading from Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x or later, and if any of the following are true: Configure unified messaging, or review and update unified messaging settings, as applicable.

You were using text to speech to access Exchange email before the upgrade.

You were accessing Exchange calendars by phone before the upgrade.

You were using Exchange contacts for personal call transfer rules or voice commands before the upgrade.

You were accessing MeetingPlace calendars before the upgrade.

You want to synchronize Unity Connection and Exchange mailboxes (single inbox).

For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/unified_messaging/guide/10xcucumgx.html .

Note the following:

External services in Unity Connection 7.x, 8.0, or 8.5 are converted to unified messaging services. The unified messaging services are enabled, but the default settings may not be the ideal settings for your Active Directory and Exchange configuration.

Unity Connection 8.5 no longer uses user passwords that are stored in the Unity Connection database to access Exchange. Instead, Unity Connection accesses Exchange through one or more unified messaging accounts that you create in Active Directory.

17. If you configured single inbox in Task 16. and you want full single-inbox functionality: Do the following tasks:

a. If Outlook on user workstations is currently configured to access Unity Connection voice messages via IMAP, delete the IMAP profile from Outlook.

b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 10.x on user workstations, and configure ViewMail to access Unity Connection voice messages in Exchange.

Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 10.x Version in a Unity Connection Cluster

Revised April 20, 2014


Note In case of a fresh install, you must order physical DVDs because the software that you download from Cisco.com cannot be used for a new install


Do the following tasks to upgrade the publisher and subscriber servers in a Unity Connection 7.x, 8.0, or 8.5 cluster to the shipping Unity Connection 10.x version.

1. Cisco Unity Connection 10.0(1) and later releases are installed on only virtual machine. Physical servers are not supported to be installed on Unity Connection 10.0(1) and later releases, and any attempt to install Unity Connection 10.0(1) an later on physical servers will fail. For more information on migrating physical server to virtual machine see, the “Migrating to a Unity Connection 10.x Virtual Machine” chapter at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/upgrade/guide/10xcucrug025.html .

2. Confirm the status of publisher and subscriber servers as active. To confirm the server status, navigate to Cisco Unity Connection Serviceability> Tools> Cluster Management. In addition, you need to confirm the running state of database replication, run the CLI command show cuc cluster status . For more information, see the applicable section in 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

Note the following:

The status of publisher server should be primary and subscriber server should be secondary.

You should always upgrade the publisher server first, and then the subscriber server.

3. Review the list of features that are disabled or that have limited functionality during the upgrade. See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0, and 8.5 to Unity Connection 10.x” section.

4. Review the list of features that stop working until you reconfigure them. See the “Features You Must Reconfigure When You Upgrade to Unity Connection 10.x” section.

5. See the applicable version of Release Notes for Cisco Unity Connection for any additional information on upgrading to the shipping version. In particular, note the items in the “Installation and Upgrade Information” section. Release notes are available at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

6. Install the licenses on the existing Unity Connection server to upgrade on Unity Connection 10.x server. While upgrade, the legacy license information is uploaded in Unity Connection database. See the “Migrating Licenses to Cisco Unity Connection 10.x” section. For more information on Cisco Unity Connection 10.x Licenses, see the “Managing Licenses in Cisco Unity Connection Surviable Remote Site VoiceMail” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/administration/guide/10xcucsagx.html .

7. Confirm that you have the software required for the upgrade. Note the following:

  • You must download the ciscocm.refresh_upgrade.cop (Cisco Option Package) file from cisco.com.
  • You must download both the ciscocm.refresh_upgrade.cop and ciscocm.version3-keys.cop (Cisco Option Package) files from cisco.com, when upgrading to Unity Connection 10.5(1).

For information on downloading the .cop file from Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .

  • If you are replacing Unity Connection servers and the servers are currently running Unity Connection 7.0(1) through 7.1(2), you will also need Unity Connection 7.1(3) software. However, not all Unity Connection 7.x versions earlier than 7.1(3) can be directly upgraded to Unity Connection 7.1(3), so you may also need software for an intermediate version that can be upgraded directly to Unity Connection 7.1(3). For information on supported upgrades, see the “Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html .

Unity Connection 7.1(3) and Unity Connection 7.1(5) softwares are required for two reasons. First, some older servers are not supported for use with Unity Connection 8.x, and an attempt to install or upgrade to Unity Connection 8.x on these older servers will fail. In addition, Unity Connection software earlier than version 7.1(3) does not include the drivers required by the new servers. This prevents you from installing Unity Connection earlier than version 7.1(3) on a new server, moving data to the new server by using the Disaster Recovery System, and then upgrading the new server to Unity Connection 10.x.

  • If you are upgrading a virtual server, you can download the software for the upgrade from Cisco.com. For information on downloading the software from Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release Notes for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html .
  • If you are not replacing the servers, you may still need software for an upgrade to an intermediate version before you can upgrade to Unity Connection 10.x. For information on supported upgrades, see the “Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified Communications Manager Software Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html .

8. If the Unity Connection server has languages other than English-United States installed and you want to continue using the languages : Download the applicable Unity Connection 10.x language files. See the Downloading Unity Connection 10.x Language Files .


Caution If languages other than English-United States are installed and in use on the Unity Connection server, you must install the Unity Connection 10.x versions of the same languages after the upgrade. Otherwise, the Unity Connection conversation will not function properly for all users.

9. If an intermediate upgrade is required as described in Task 7.: Upgrade Unity Connection as necessary. For information on how to upgrade from Unity Connection 7.x to a later version of Unity Connection 7.x, see the “ Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version ” chapter in the 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 .

Do not install the Unity Connection 8.x license files on the Unity Connection 7.x servers.


Caution If the intermediate upgrade includes a major-version upgrade (for example, from 2.x to 7.x), you must complete the upgrade to Unity Connection 10.x before Unity Connection will function again. When you integrate with the ELM server to obtain license files for the upgrade, Cisco sends you only 10.x license files, which cannot be used on intermediate versions.

10. If you do not have a backup of the existing server: Back up the publisher server by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

11. Install the a.cop file on both Publisher and Subscriber before upgrading to Unity Connection 10.x. (This is the Cisco Option Package that you downloaded in Task 7.). The .cop file patches your current version of Unity Connection, which is required before you can upgrade to Unity Connection 10.x. See the “Installing the Cisco Option Package Required to Upgrade from Unity Connection 7.x, 8.0 or 8.5 to the Shipping 10.x Version” section.

12. Upgrade the Unity Connection software on the publisher server. See the applicable section:


Caution Do not start the upgrade on the subscriber server until the upgrade of the publisher server is complete and Unity Connection functionality on both servers will be disabled until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will fail, and you will have to upgrade the subscriber server again.

If the phone system is routing calls to the subscriber server, outside callers and Unity Connection users can leave voice messages, but the messages are not immediately delivered to user mailboxes.

13. On the subscriber server, confirm that the publisher server has Primary status and that the subscriber server has Secondary status. For instructions, see the Administering a Cisco Unity Connection 10.x Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/cluster_administration/guide/10xcuccagx.html .

14. Confirm that the publisher server is taking calls and delivering voice messages to users.

15. On the subscriber server, install the Cisco Option Package that is required for the upgrade to Unity Connection 10.x. (This is the Cisco Option Package that you downloaded in Task 7.) See the “Installing the Cisco Option Package Required to Upgrade from Unity Connection 7.x, 8.0 or 8.5 to the Shipping 10.x Version” section.

16. Upgrade the Unity Connection software on the subscriber server. See the applicable section:


Note After the successful completion of upgrade process, if you want to enable the Tenant Partitioning feature then delete all the users (except default users) from Unity Connection. Make sure that you take the backup of your system using COBRAS before deleting all the users.


If the phone system is routing calls to the publisher server, outside callers and Unity Connection users can leave voice messages. Messages are immediately delivered to user mailboxes.

17. After the successful upgrade to Unity Connection 10.0(1), make sure that you restart your system using the CLI command utils system restart. For more information, see the applicable section in 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

18. Install Unity Connection 10.x languages, if applicable. See the Installing Unity Connection 10.x Language Files .

Install languages on the publisher server first, then on the subscriber server.

If you are installing Japanese and 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 and 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 .

19. If you are upgrading from Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 10.x, and if any of the following are true: Configure unified messaging, or review and update unified messaging settings, as applicable.

You were using text to speech to access Exchange email before the upgrade.

You were accessing Exchange calendars by phone before the upgrade.

You were using Exchange contacts for personal call transfer rules or voice commands before the upgrade.

You were accessing MeetingPlace calendars before the upgrade.

You want to synchronize Unity Connection and Exchange mailboxes (single inbox).

For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity Connection Release 10.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/10x/unified_messaging/guide/10xcucumgx.html .

Note the following:

External services in Unity Connection 7.x, 8.0, or 8.5 are converted to unified messaging services. The unified messaging services are enabled, but the default settings may not be the ideal settings for your Active Directory and Exchange configuration.

Unity Connection 8.5 no longer uses user passwords that are stored in the Unity Connection database to access Exchange. Instead, Unity Connection accesses Exchange through one or more unified messaging accounts that you create in Active Directory.

20. If you configured single inbox in Task 19. and you want full single-inbox functionality: Do the following tasks:

a. If Outlook on user workstations is currently configured to access Unity Connection voice messages via IMAP, delete the IMAP profile from Outlook.

b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 10.x on user workstations, and configure ViewMail to access Unity Connection voice messages in Exchange.

Installing the Cisco Option Package Required to Upgrade from Unity Connection 7.x, 8.0 or 8.5 to the Shipping 10.x Version


Note Installing the Cisco Option Package will temporarily affect access to Unity Connection administration applications and to the command-line interface.


Do the applicable procedure:

To Install, from a Local DVD, the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0, or 8.5 to the Shipping 10.x Version


Step 1 Insert the DVD that contains the Cisco Option Package (.cop) file into the disc drive on the Cisco Unity Connection server.

Step 2 Sign in to Cisco Unified Operating System Administration.

If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco Unified Operating System Administration by browsing to:

http://<Unity Connection_servername>/cmplatform

Step 3 From the Software Upgrades menu, select Install/Upgrade .

Step 4 On the Software Installation/Upgrade page, in the Source field, select DVD/CD .

Step 5 In the Directory field, enter a forward slash ( / ).

Step 6 Select Next .

Step 7 Choose the software that you want to install, and select Next .

The .cop file is copied to the virtual hard disk on Unity Connection server. When the file is copied, a screen displays the checksum value.

Step 8 Verify the checksum.

Step 9 Select Next to begin the installation.

During the installation, the value of the Status field is Running . When the installation is complete, the value of the Status field changes to Complete .

Note the following:

All command-line interface sessions are terminated automatically.

The Cisco Tomcat Service can take several minutes to restart automatically.

Step 10 Logout from the Cisco Unified Operating System Administration application to reflect the successful installation of the .cop file.

Step 11 Confirm the running state of Cisco Tomcat Service, run the CLI command utils service list . For more information, see the applicable section in 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


 

To Install, from a Network Location, the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0, or 8.5 to the Shipping 10.x Version


Step 1 Copy the Cisco Option Package (.cop) file on an FTP or SFTP server that the Cisco Unity Connection server can access.

Step 2 Sign in to Cisco Unified Operating System Administration.

If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco Unified Operating System Administration by browsing to:

http://<Unity Connection_servername>/cmplatform

Step 3 From the Software Upgrades menu, select Install/Upgrade .

Step 4 On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem .

Step 5 In the Directory field, enter the path to the folder that contains the .cop file.

If the .cop file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning of the folder path. (For example, if the .cop file is in the cop folder, you must enter /cop .)

If the .cop file is located on a Windows server, you must use the applicable syntax for an FTP or SFTP server such as:

    • The path must begin with a forward slash (/) and contain forward slashes throughout instead of backward slashes (\).
    • The path must start from the FTP or SFTP root folder on the server and must not include a Windows absolute path, which starts with a drive letter (for example, C:).

Step 6 In the Server field, enter the server name or IP address.

Step 7 In the User Name field, enter the alias that will be used to sign in to the remote server.

Step 8 In the User Password field, enter the password that will be used to sign in to the remote server.

Step 9 In the Transfer Protocol field, select the applicable transfer protocol.

Step 10 Select Next .

Step 11 Choose the software that you want to install, and select Next .

The .cop file is copied to the virtual hard disk on Unity Connection server. When the file is copied, a screen displays the checksum value.

Step 12 Verify the checksum.

Step 13 Select Next to begin the installation.

During the installation, the value of the Status field is Running . When the installation is complete, the value of the Status field changes to Complete .
Note the following:

All command-line interface sessions are terminated automatically.

The Cisco Tomcat Service can take several minutes to restart automatically.

Step 14 Logout from the Cisco Unified Operating System Administration application to reflect the successful installation of the .cop file.

Step 15 Confirm the running state of Cisco Tomcat Service, run the CLI command utils service list . For more information, see the applicable section in 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


 

Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 10.x Version from a Local DVD

To upgrade Unity Connection from a local DVD, you can do either of the following:

  • Use a DVD shipped from Cisco.
  • Download a signed .iso file from Cisco.com, and burn a disc image of the downloaded software. Burning a disc image extracts the files from the .iso file that you downloaded and writes them to a DVD.

Caution If you are upgrading a cluster, do not start the upgrade on the subscriber server until the upgrade of the publisher server is complete and all Unity Connection functionality on both servers will be disabled until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will fail, and you will have to upgrade the subscriber server again.

To Upgrade Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 10.x Version from a Local DVD


Step 1 Insert the DVD that contains Unity Connection into the disc drive on the Cisco Unity Connection server.

Step 2 Sign in to Cisco Unified Operating System Administration.

If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco Unified Operating System Administration by browsing to:

http://<Unity Connection_servername>/cmplatform

Step 3 From the Software Upgrades menu, select Install/Upgrade .

Step 4 On the Software Installation/Upgrade page, in the Source field, select DVD/CD .

Step 5 In the Directory field, enter a forward slash ( / ).

Step 6 Select Next .

Step 7 Select the upgrade version that you want to install, and select Next . The upgrade file is copied to the virtual hard disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.

Step 8 Verify the checksum.

Step 9 On the next page, monitor the progress of the upgrade.

If you lose your Unity Connection with the remote server or close your browser during this step, you may see the following message when you try to view the Software Installation/Upgrade page again:

Warning: Another session is installing software, click Assume Control to take over the installation.

To continue monitoring the upgrade, select Assume Control .

You can also monitor the upgrade by using the Real-Time Monitoring Tool.

Step 10 Select Next .

During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System Administration is updated with information on the progress of the upgrade, but updates stop after the server automatically restarts for the first time. To determine when the upgrade is complete, view the console for the Unity Connection server: the console screen displays a message indicating that the installation is complete, and the login prompt for the command-line interface appears.

Step 11 To verify the success of the upgrade, run the CLI command show cuc version . The upgrade succeeded if the active partition has the upgraded version and the inactive partition has the old version.

Step 12 After the successful upgrade to Unity Connection 10.0(1), make sure that you restart your system using the CLI command utils system restart. For more information, see the applicable section in 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


 

Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 10.x Version from a Network Location

To upgrade Unity Connection from a network location, you must download a signed .iso file from Cisco.com, and copy the .iso file to an FTP or SFTP server. Unity Connection does not allow you to upgrade by copying either the contents of a DVD shipped from Cisco or the extracted contents of a downloaded .iso file to an FTP or SFTP server. This helps prevent someone from attempting to upgrade by using software that has been tampered with.


Caution If you are upgrading a cluster, do not start the upgrade on the subscriber server unitl the upgrade of the publisher server is complete and all Unity Connection functionality on both servers will be disabled until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will fail, and you will have to upgrade the subscriber server again.

To Upgrade Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 10.x Version from a Network Location


Step 1 Copy the upgrade file to a folder on an FTP or SFTP server that the Cisco Unity Connection server can access.

Step 2 Sign in to Cisco Unified Operating System Administration.

If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco Unified Operating System Administration by browsing to:

http://<Unity Connection_servername>/cmplatform

Step 3 From the Software Upgrades menu, select Install/Upgrade .

Step 4 On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem .

Step 5 In the Directory field, enter the path to the folder that contains the upgrade file.

If the upgrade file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning of the folder path. (For example, if the upgrade file is in the upgrade folder, you must enter /upgrade .)

If the upgrade file is located on a Windows server, you must use the applicable syntax for an FTP or SFTP server such as:

    • The path must begin with a forward slash (/) and contain forward slashes throughout instead of backward slashes (\).
    • The path must start from the FTP or SFTP root folder on the server and must not include a Windows absolute path, which starts with a drive letter (for example, C:).

Step 6 In the Server field, enter the server name or IP address.

Step 7 In the User Name field, enter the alias that will be used to sign in to the remote server.

Step 8 In the User Password field, enter the password that will be used to sign in to the remote server.

Step 9 In the Transfer Protocol field, select the applicable transfer protocol.

Step 10 Select Next .

Step 11 Select the upgrade version that you want to install and select Next . The upgrade file is copied to the virtual hard disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.

Step 12 Verify the checksum.

Step 13 On the next page, monitor the progress of the upgrade.

If you lose your Unity Connection with the remote server or close your browser during this step, you may see the following message when you try to view the Software Installation/Upgrade page again:

Warning: Another session is installing software, click Assume Control to take over the installation.

To continue monitoring the upgrade, select Assume Control .

You can also monitor the upgrade by using the Real-Time Monitoring Tool.

Step 14 Select Next .

During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System Administration is updated with information on the progress of the upgrade, but updates stop after the server automatically restarts for the first time. To determine when the upgrade is complete, view the console for the Unity Connection server: the console screen displays a message indicating that the installation is complete, and the login prompt for the command-line interface appears.

Step 15 To verify the success of the upgrade, run the CLI command show cuc version . The upgrade succeeded if the active partition has the upgraded version and the inactive partition has the old version.

Step 16 After the successful upgrade to Unity Connection 10.0(1), make sure that you restart your system using the CLI command utils system restart. For more information, see the applicable section in 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