Upgrade Guide for Cisco Unity Connection Release 8.x
Migrating from Cisco Unity Connection 1.x to Version 8.x
Downloads: This chapterpdf (PDF - 124.0KB) The complete bookPDF (PDF - 3.95MB) | Feedback

Migrating from Cisco Unity Connection 1.x to Version 8.x

Table Of Contents

Migrating from Cisco Unity Connection 1.x to Version 8.x

Task List for Migrating from Connection 1.x to Version 8.x

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

Preparing to Create User Accounts by Using Multiple Connection 8.x Templates


Migrating from Cisco Unity Connection 1.x to Version 8.x


This chapter contains the following sections:

Task List for Migrating from Connection 1.x to Version 8.x

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

Preparing to Create User Accounts by Using Multiple Connection 8.x Templates

Task List for Migrating from Connection 1.x to Version 8.x

Use the following high-level task list to migrate to Connection 8.x correctly. The tasks reference detailed instructions in this guide and in other Connection documentation as noted. Follow the documentation for a successful migration.

1. If you are reusing the current Connection server rather than installing a new server, review the applicable Cisco Unity Connection 8.<x> Supported Platforms List to determine whether the server requires replacement hard disks or additional RAM. The document is available at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.

2. If the Connection server is running version 1.1: Upgrade to version 1.2. For more information, see the "Upgrading Cisco Unity Connection or Voice-Recognition Software to the Shipping Version" chapter of the Cisco Unity Connection Reconfiguration and Upgrade Guide, Release 1.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/1x/installation/guide/inst.html.

3. Obtain the license file(s) for the upgrade to Cisco Unity Connection 8.x. Do not install them now; you do so later in the migration 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/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx.html.

4. Review the "Requirements for Migrating from Cisco Unity Connection 1.x to Version 8.x" section of System Requirements for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html.

5. See the applicable version of Release Notes for Cisco Unity Connection for 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. Download the following tools:

Connection 1.x Disaster Recovery tools, available at http://www.ciscounitytools.com/Applications/CxN/DIRT/DIRT.html.

COBRAS, available at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.

7. Install the tools that you downloaded in Task 6.

8. Back up the server by using the Connection 1.x Disaster Recovery tools. This backup will not be used to restore data on the Connection 8.x system; we recommend it only so that you can revert to Connection 1.2 if necessary.


Note The Connection 1.x Disaster Recovery tools are different from the Disaster Recovery System available with Connection 2.x and later.


9. Use COBRAS to export Connection data and messages. For more information, see COBRAS Help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.

10. If additional memory or replacement hard disks are required: Add memory or replace hard disks. See the "Installing a Memory Upgrade or Replacing All Hard Disks to Support Connection 8.x (Selected Servers Only)" section of this guide.

11. Install and begin configuring Connection 8.x. See Part 1 through Part 3 in the "Task List for Installing a Cisco Unity Connection 8.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 8.x System" chapter of the Installation Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.html.

12. Populate the system with user and call management data. See the following documentation:

COBRAS Help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.

"Part 4: Populating the System with User and Call Management Data" in the "Task List for Installing a Cisco Unity Connection 8.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 8.x System" chapter of the Installation Guide for Cisco Unity Connection at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.html. Skip tasks for data that will be imported.

13. Finish configuring Connection 8.x. See Part 5 through Part 9 in the "Task List for Installing a Cisco Unity Connection 8.x System (Without a Connection Cluster)" in the "Overview of Mandatory Tasks for Installing a Cisco Unity Connection 8.x System" chapter of the Installation Guide for Cisco Unity Connection Release 8.x.

Installing a Memory Upgrade or Replacing All Hard Disks to Support 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 qualified for use with Cisco Unity Connection require:

A memory upgrade to run Connection 8.x in any configuration.

A memory upgrade to support a specified number of Connection users when both voice recognition and intrasite or intersite networking are configured.

A hard-disk replacement to support a Connection cluster.

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


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

Replace the hard disks:

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.


Preparing to Create User Accounts by Using Multiple Connection 8.x Templates

The utility that exports user data from Connection 1.x creates one CSV file with data for all users, and the utility that imports this data into Connection 8.x creates all of the new user accounts by using the same template. If you want to create user accounts by using two or more templates, you may want to split the CSV file into one file per template. (Depending on how you want to split users among templates, it might be faster to create all user accounts with the same template and then update user settings individually.)

To Prepare Multiple CSV Files for Creating User Accounts by Using Multiple Connection 8.x Templates


Step 1 In the location to which you exported Connection 1.x data, create a subfolder for each template that you want to use. Give each subfolder the same name as the corresponding template.

Step 2 Copy the CSV file to each subfolder. Use the same filename as the original CSV file, or the import will fail.

Step 3 Copy all of the recorded-name WAV files from the location to which you exported Connection 1.x data to each subfolder that you created in Step 1. Filenames are in the format <user_alias>_VOICE_NAME.wav.

When you import user data from a CSV file, the corresponding recorded-name WAV files are also imported. The import utility looks for these files only in the folder that contains the CSV file from which you are importing.

Step 4 Open the CSV file in each subfolder, and delete the rows for the users who you do not want to import by using the corresponding template.

For example, if you were editing the CSV file in a SalesStaffTemplate folder, you would delete all of the rows for all of the users who you do not want to create by using the SalesStaffTemplate.