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

Table of Contents

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

About the Upgrade Process to Unity Connection 8.x

Features You Must Reconfigure During an Upgrade to Unity Connection8.5

Task List for Upgrading Single Unity Connection Server 7.x or 8.x Software to the Shipping 8.x Version

Task List for Upgrading Unity Connection Cluster 7.x or 8.x Software to the Shipping 8.x Version

Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)

Upgrading Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Local DVD

Upgrading Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Network Location

Switching to the Upgraded Version of Unity Connection 8.x Software

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

This chapter contains the following sections:

About the Upgrade Process to Unity Connection 8.x

Added November 16, 2010

Note the following considerations about the Cisco Unity Connection upgrade process:

  • When you upgrade a server, the existing version of Unity Connection continues to run, and the version you are upgrading to is installed on a different partition:

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.

  • At the start of the upgrade, you choose whether to restart to the inactive partition. If you choose to restart, when the upgrade is complete, the server automatically restarts, running the upgraded version of Unity Connection. If you choose not to restart, after the upgrade is complete, you must manually switch to the upgraded version.
  • Installing the software upgrade requires approximately two hours for each server. When upgrading a Unity Connection cluster, an upgrade requires approximately four hours.
  • Switching to the upgraded software requires a few minutes.

Note To migrate from a physical to virtual server or from virtual to virtual server, make sure the server requirements are met for Unity Connection 8.x, as mentioned in: http://docwiki.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance#Upgrading_the_UC_applications.


Features You Must Reconfigure During an Upgrade to Unity Connection 8.5

Added November 16, 2010

Unity Connection 8.5 includes enhancements to the following features, which are now included 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 that can be used in Cisco Unity Connection Personal Call Transfer Rules and when users place outgoing calls by using voice commands.

If Unity Connection is accessing Exchange 2007, after an upgrade from Unity Connection 7.x or 8.0, the features stop working until you reconfigure them. The task list tells you when in the upgrade process to reconfigure these features.

Task List for Upgrading Single Unity Connection Server 7.x or 8.x Software to the Shipping 8.x Version

Revised November 16, 2010

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

1. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 8.5 or later: Review the list of features that stop working until you reconfigure them. See the “Features You Must Reconfigure During an Upgrade to Unity Connection 8.5” section.

2. If you are upgrading from Unity Connection 7.x or 8.0: See the Cisco Unity Connection 8.x Supported Platforms List at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/supported_platforms/8xcucspl.html to determine:

  • Whether the current Unity Connection server is supported for Unity Connection 8.x.
  • If the current Unity Connection server is supported, whether it requires replacement hard disks.
  • If the current Unity Connection server is supported, whether you are adding a feature that requires additional memory.

If the server is no longer supported, replace it before you obtain license files, which are tied to the MAC address of the server.

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

4. If you are upgrading from Unity Connection 7.x: Obtain the license files for the upgrade to Unity Connection 8.x. Do not install them now; you do so later in the upgrade process. See the “Managing Licenses in Cisco Unity Connection 8.x” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx/8xcucsag310.html .


Note Upgrading from Unity Connection 8.0 to 8.5 does not require a new license file.


5. Confirm that you have the software required for the upgrade. If you are upgrading from Unity Connection 7.x, note the following:

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

Note For 7.x versions, Cisco Unified CM and Cisco Unity Connection version numbers are identical.


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

  • If you are replacing the Unity Connection server or replacing hard disks in the server, you must order physical disks because the software that you download from Cisco.com cannot be used for a new install.

If you are not replacing the server or replacing hard disks in the 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 8.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 .

Note For 7.x versions, Cisco Unified CM and Cisco Unity Connection version numbers are identical.


6. If you are upgrading from Unity Connection 7.x to 8.x or from 8.0 to 8.5, 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 8.0 or 8.5 language files. See the “Downloading Unity Connection Language Files” section.


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

7. If an intermediate upgrade is required as described in Task 5.: 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 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 server.


Caution If the current Unity Connection server is not supported for Unity Connection 8.x, you must complete the upgrade Unity Connection 8.x, including possible intermediate upgrades, before Unity Connection will function again. When you obtain license files for the upgrade to version 8.x, Cisco sends you only 8.x license files, which cannot be used on intermediate versions.

8. If you are upgrading from Unity Connection 7.x, you are using the current server for Unity Connection 8.x, and you are replacing hard disks and/or adding memory:

a. Back up the server by using the Disaster Recovery System. You will use this backup to restore data on the replacement hard disks. 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. Replace the hard disks and/or add memory. See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)” section.

c. Reinstall the version of Unity Connection that was installed when you backed up the 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 .

d. Restore data on the server using the DRS backup.

9. 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/c/en/us/td/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx/7xcucrug040.html .

10. If you do not have a backup from replacing hard disks or replacing the 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 .

11. If you are upgrading during nonbusiness hours : Run the CLI command utils iothrottle disable to speed up the upgrade.

In an effort to prevent upgrades from adversely affecting system performance during business hours, the upgrade process is throttled and may take several hours to complete. If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the time required for the upgrade to complete but adversely affects Unity Connection performance. For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .


Caution You cannot disable throttling while an upgrade is running. If you decide to disable throttling after you start an upgrade, you must stop the upgrade, disable throttling, and restart the upgrade from the beginning.

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

13. If you disabled the upgrade throttle in Task 11. : Run the CLI command utils iothrottle enable to re-enable the throttle. For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

14. If you chose to do a later restart at the end of the software upgrade in Task 12.: Switch to the upgraded partition. See the “Switching to the Upgraded Version of Unity Connection 8.x Software” section.

(If you chose to automatically restart at the end of the software upgrade, the switch to the upgraded partition is complete.)

15. If you are upgrading from Unity Connection 7.x: Install the license files that you obtained before.

16. Install Connection 8.0 or 8.5 languages, if applicable. See the “Installing Unity Connection Language Files” section.

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 .

17. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 8.5 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 8.5 and Later at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx.html .

Note the following:

External services in Unity Connection 7.x or 8.0 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.

18. If you configured single inbox in Task 17. 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 8.5 on user workstations, and configure ViewMail to access Unity Connection voice messages in Exchange.

Task List for Upgrading Unity Connection Cluster 7.x or 8.x Software to the Shipping 8.x Version

Revised December 20, 2010

As the upgrade software is installed, the publisher and subscriber servers continue answering calls and replication occurs. After the upgrade is complete, you switch the two servers, one at a time, to the upgraded software.

Note the following details about how Unity Connection functions during the switch:

  • When you switch the publisher server to the upgraded software, the subscriber server answers all calls, but replication does not occur and messages may not be available.
  • When you switch the subscriber server to the upgraded software, the publisher server answers all calls, but replication does not occur and messages may not be available.
  • About 15 minutes after both servers are switched to the upgraded software, both servers answer calls, replication resumes, and messages are available.

Note the following considerations about the upgrade process:

  • Messages that are recorded while switching to the upgraded software are not replicated. This means that, depending on the Connection server that is accessed, a user may briefly not be able to retrieve new messages. After the upgrade process is complete, messages are replicated. When replication is complete, all messages are available regardless of which Unity Connection server is accessed.
  • MWIs and notifications may not be sent. MWIs and notifications synchronize only after the upgrade process is complete.
  • After the upgrade process is complete, the servers require about 15 minutes to renegotiate their server status and to replicate messages.

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

1. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 8.5 or later: Review the list of features that stop working until you reconfigure them. See the “Features You Must Reconfigure During an Upgrade to Unity Connection 8.5” section.

2. If you are upgrading from Unity Connection 7.x or 8.0: Review the applicable Cisco Unity Connection 8.<x> Supported Platforms List to determine:

  • Whether the current Unity Connection server is supported for Unity Connection 8.x.
  • If the current Unity Connection servers are supported, whether they require replacement hard disks.
  • If the current Unity Connection servers are supported, whether you are adding a feature that requires additional memory.

The document is available at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html .

If the servers are no longer supported, replace them before you obtain license files, which are tied to the MAC address of the server.

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

4. If you are upgrading from Unity Connection 7.x: Obtain the license files for the upgrade to Unity Connection 8.x. Do not install them now; you do so later in the upgrade process.


Note Upgrading from Unity Connection 8.0 to 8.5 does not require a new license file.


5. Confirm that you have the software required for the upgrade. If you are upgrading from Unity Connection7.x, note the following:

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

Note For 7.x versions, Cisco Unified CM and Cisco Unity Connection version numbers are identical.


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

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

Note For 7.x versions, Cisco Unified CM and Cisco Unity Connection version numbers are identical.


  • If you are replacing the Unity Connection server or replacing hard disks in the server, you must order physical disks because the software that you download from Cisco.com cannot be used for a new install.

If you are not replacing the server or replacing hard disks in the 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 .

6. If you are upgrading from Unity Connection 7.x to 8.x or from 8.0 to 8.5, 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 8.0 or 8.5 language files. See the “Downloading Unity Connection Language Files” section.


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

7. If one or both of your current servers are no longer supported, and if your current servers are running Unity Connection 7.0(1) through 7.1(2): Upgrade your existing servers to Unity Connection version 7.1(3) even if you are only replacing one of them. You may have to upgrade to an intermediate version first, as explained in Task 5. For information on upgrading from an earlier version of Unity Connection 7.x to version 7.1(3), see the “Task List for Upgrading Unity Connection 7.x Software to the Shipping 7.x Version in a Unity Connection Cluster” section in the “Upgrading Cisco Unity Connection 7.x to the Shipping 7.x Version” chapter of the Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx/7xcucrug009.html .

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


Caution If the current Unity Connection servers are not supported for Unity Connection 8.x, you must complete the upgrade Unity Connection 8.x, including possible intermediate upgrades, before Unity Connection will function again. When you obtain license files for the upgrade to version 8.x, Cisco sends you only 8.x license files, which cannot be used on intermediate versions.

8. If you are upgrading from Unity Connection 7.x, you are using the current servers for Unity Connection 8.x, and you are either replacing one or both servers or replacing hard disks in one or both servers: Replace the servers or replace hard disks in the servers. See the applicable section in the “Replacing Cisco Unity Connection 7.x Servers or Hard Disks” chapter of the Upgrade Guide for Cisco Unity Connection Release 7.x at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx/7xcucrug040.html .


Caution If you are replacing hard disks, do not use the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)” section of this chapter, which does not account for issues related to a cluster.

9. If you are upgrading from Unity Connection 7.x and you are adding memory to the current Unity Connection server: See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)” section.

10. Sign in to Cisco Unity Connection Serviceability and 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 Cluster” chapter of the applicable Cluster Configuration and Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

11. If you do not have a backup from replacing hard disks or replacing the 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 .

12. If you are upgrading during nonbusiness hours : On the publisher server, run the CLI command utils iothrottle disable to speed up the upgrade.

In an effort to prevent upgrades from adversely affecting system performance during business hours, the upgrade process is throttled and may take several hours to complete. If you are upgrading during a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the time required for the upgrade to complete but adversely affects Unity Connection performance. For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .


Caution You cannot disable throttling while an upgrade is running. If you decide to disable throttling after you start an upgrade, you must stop the upgrade, disable throttling, and restart the upgrade from the beginning.

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

The publisher server continues to answer calls.


Caution Do not restart the publisher server and do not switch to the upgraded software during this task. Otherwise, the Unity Connection cluster will not function correctly.

14. If you are upgrading during nonbusiness hours : On the subscriber server, run the CLI command utils iothrottle disable to speed up the upgrade.

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

The subscriber server continues to answer calls.


Caution Do not restart the subscriber server and do not switch to the upgraded software during this task. Otherwise, the Unity Connection cluster will not function correctly.

16. If you disabled the upgrade throttle on the publisher server in Task 12.: Run the CLI command utils iothrottle enable to re-enable the throttle. For more information, see the applicable Command Line Interface Reference Guide for Cisco Unified Communications Solutions at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html .

17. Switch to the upgraded software on the publisher server. See the “Switching to the Upgraded Version of Unity Connection 8.x Software” section.

18. If you disabled the upgrade throttle on the subscriber server in Task 14.: Run the CLI command utils iothrottle enable to re-enable the throttle.

19. Switch to the upgraded software on the subscriber server. See the “Switching to the Upgraded Version of Unity Connection 8.x Software” section.

20. About 15 minutes after you complete Task 19., on the publisher 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 8.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/8x/cluster_administration/guide/8xcuccagx.html .

21. 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 8.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/8x/cluster_administration/guide/8xcuccagx.html .

22. If you are upgrading from Unity Connection 7.x: Install the license files that you obtained in Task 4. See the “Managing Licenses in Cisco Unity Connection 8.x” chapter of the System Administration Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html .

23. Install Connection 8.0 or 8.5 languages, if applicable. See the “Installing Unity Connection Language Files” section.

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 .

24. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 8.5 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 8.5 and Later at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumgx.html .

Note the following:

External services in Unity Connection 7.x or 8.0 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.

25. If you configured single inbox in Task 24. 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 8.5 on user workstations, and configure ViewMail to access Unity Connection voice messages in Exchange.

Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)


Note If you are upgrading a server that does not require a memory upgrade or a hard-disk replacement, skip this section.


Some servers that are running Cisco Unity Connection 7.x and are qualified for use with Unity Connection 8.x require a hard-disk replacement to support Unity Connection 8.x. In addition, some servers require additional memory if you are going to add selected features (for example, intrasite or intersite networking) to the upgraded server.

For information on your Unity Connection server, see the applicable server-specific table in the Cisco Unity Connection 8.<x> Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html .


Warning Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord. Statement 1



Warning Before opening the chassis, disconnect the telephone-network cables to avoid contact with telephone-network voltages. Statement 2



Warning This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260 Clause 1.2.14.3 Service Personnel. Statement 88



Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94



Warning The safety cover is an integral part of the product. Do not operate the unit without the safety cover installed. Operating the unit without the cover in place will invalidate the safety approvals and pose a risk of fire and electrical hazards. Statement 117



Warning Do not work on the system or connect or disconnect cables during periods of lightning activity. Statement 1001



Warning Read the installation instructions before connecting the system to the power source. Statement 1004



Warning To prevent bodily injury when mounting or servicing this unit in a rack, you must take special precautions to ensure that the system remains stable. The following guidelines are provided to ensure your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing the unit in the rack. Statement 1006



Warning There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with the same or equivalent type recommended by the manufacturer. Dispose of used batteries according to the manufacturer’s instructions. Statement 1015



Warning This unit is intended for installation in restricted access areas. A restricted access area can be accessed only through the use of a special tool, lock and key, or other means of security. Statement 1017



Warning To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021



Warning To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023



Warning This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the absence of a suitably installed ground conductor. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024



Warning Blank faceplates and cover panels serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement 1029



Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030



Warning Ultimate disposal of this product should be handled according to all national laws and regulations. Statement 1040


(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html .)

To Install a Memory Upgrade or Replace All Hard Disks to Support Unity Connection 8.x (Selected Servers Only)


Step 1 Remove the cover.

Step 2 If you are not installing a memory upgrade, skip to Step 3.

Install the memory modules in the applicable slots or locations, depending on the server model, as documented in the Cisco Unity Connection 8.<x> Supported Platforms List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html .


Caution If you install new memory modules in the wrong slots, the server and operating system may not recognize that they have been installed, and Cisco Unity Connection performance may suffer.

Step 3 If you are not replacing hard disks, skip to Step 4.

Replace all of the hard disks in the server.


Caution You must remove existing hard disks and install exactly as many hard disks as you remove, or Cisco Unity Connection installation will fail.

a. Make note of the current locations of the hard disks in the server, including which hard disk is in which hard disk slot. If the replacement fails and you want to revert to the current configuration, you must put the existing hard disks back into their current locations.

b. Remove the drive trays from the server.

c. Remove the old hard disks from the drive trays.

d. Insert the new hard disks into the drive trays.

e. Reinstall the drive trays in the locations that you made note of in Step a.

Step 4 Reattach the cover.


 

Upgrading Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Local DVD

Revised September 13, 2013

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.

To Upgrade Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Local DVD


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

Step 2 Sign in to Cisco Unified Operating System Administration.

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 .

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

If you close your web 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 9 Select the applicable restart action, depending on the configuration:

 

No Unity Connection cluster
  • To install the upgrade software and automatically restart to the upgraded partition, select Reboot to Upgraded Partition .
  • To install the upgrade and restart to the upgraded partition at a later time, select Do Not Reboot After Upgrade .
Unity Connection cluster configured

Select Do Not Reboot After Upgrade .

Step 10 Select Next .

Step 11 If you selected the Do Not Reboot After Upgrade option in Step 9, close the window when the installation of the upgrade software is complete. The Upgrade Status window displays the Upgrade log.

If you selected the Reboot to Upgrade Partition option, note the following:

    • Unity Connection services are stopped.
    • Data from the partition where the older version is installed is copied to the partition where the newer version is installed. If changes to the database schema require updates to the format of data, that occurs in this step. Note that messages are stored in a common partition, so they are not copied.
    • The Unity Connection server restarts and switches to the newer version.

Note You can check the status of the installation of the upgrade software by using the CLI command utils system upgrade status. The installation is complete when the inactive partition has the upgraded software and the active partition has the old software.



 

Upgrading Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Network Location

Revised September 13, 2013

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

To Upgrade Unity Connection 7.x or 8.x Software to the Shipping 8.x Version from a Network Location


Step 1 To copy the upgrade file to a folder on an FTP or SFTP server that Unity Connection can access:

a. In Cisco Unified Operating System Administration, expand Software Upgrades menu and select Install/Upgrade .

b. In the Source field, select Remote Filesystem .

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

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

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

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

g. In the Transfer Protocol field, select the applicable transfer protocol and select Next .

Step 2 Select the upgrade version that you want to install and select Next .

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

If you lose your 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 4 Select the applicable restart action, depending on the configuration:

 

No Unity Connection cluster
  • To install the upgrade software and automatically restart to the upgraded partition, select Reboot to Upgraded Partition .
  • To install the upgrade and restart to the upgraded partition at a later time, select Do Not Reboot After Upgrade .
Unity Connection cluster configured

Select Do Not Reboot After Upgrade .

Step 5 Select Next .

Step 6 If you selected the Do Not Reboot After Upgrade option in Step 4, close the window when the installation of the upgrade software is complete. The Upgrade Status window displays the Upgrade log.

If you selected the Reboot to Upgrade Partition option, not the following:

    • Unity Connection services are stopped.
    • Data from the partition where the older version is installed is copied to the partition where the newer version is installed. If changes to the database schema require updates to the format of data, that occurs in this step. Note that messages are stored in a common partition, so they are not copied.
    • The Unity Connection server restarts and switches to the newer version.

Note You can check the status of the installation of the upgrade software by using the CLI command utils system upgrade status. The installation is complete when the inactive partition has the upgraded software and the active partition has the old software.



 

Switching to the Upgraded Version of Unity Connection 8.x Software

If you chose not to automatically switch to the upgraded partition at the end of the upgrade, do the following procedure when you are ready to switch partitions.

To Switch to the Upgraded Version of Unity Connection 8.x Software


Step 1 If you do not have a recent backup, 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 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/drs_administration/guide/8xcucdrsag.html .

Step 2 In Cisco Unified Operating System Administration, expand Settings menu and select Version .

Step 3 The following occurs:

    • Unity Connection services are stopped.
    • Data from the partition where the older version is installed is copied to the partition where the newer version is installed. If changes to the database schema require updates to the format of data, that occurs in this step. Note that messages are stored in a common partition, so they are not copied.
    • The Unity Connection server restarts and switches to the newer version.

Note You can check the status of the installation of the upgrade software using the CLI command utils system upgrade status. The upgrade is complete when the inactive partition has the upgraded software and the active partition has the old software.