Cisco Unity

Document ID: 41201

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Downgrading from Cisco Unity Version 4.0 to Version 3.1(5)
      Task List for Downgrading from Cisco Unity Version 4.0 to Version 3.1(5) Without Failover
      Task List for Downgrading from Cisco Unity Version 4.0 to Version 3.1(5) with Failover
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document outlines the process for downgrading a Cisco Unity system with Microsoft Exchange from version 4.0 to version 3.1(5), for systems with and without failover. Use the applicable task list to downgrade the Cisco Unity system correctly.

Note: The Cisco Unity server will be out of service while the Cisco Unity software is downgraded.

Prerequisites

Requirements

To downgrade successfully, you must have done all of the following:

• Installed a Cisco Unity 3.1(5) system with Microsoft Exchange 5.5 or Microsoft Exchange 2000

• Backed up the Cisco Unity 3.1(5) system by using the Cisco Unity Disaster Recovery Tool (Note that for systems with failover, the back up must have been done on the secondary Cisco Unity server)

• Upgraded the Cisco Unity system from version 3.1(5) to version 4.0

Components Used

The information in this document is based on Cisco Unity 4.0 downgraded to Cisco Unity 3.1(5).

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Downgrading from Cisco Unity Version 4.0 to Version 3.1(5)

Task List for Downgrading from Cisco Unity Version 4.0 to Version 3.1(5) Without Failover

Follow the instructions provided below:

1. Obtain an activation code for the Cisco Unity 3.1(5) system key. Call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team, or send an e-mail to licensing@cisco.com .

2. Uninstall Cisco Unity 4.0 software by running the utility to uninstall Cisco Unity versions 3.x and 4.0. The latest version of the utility is available at Cisco Unity Tools . Refer to the online help for the utility. Do the following as you uninstall the software:

   • If the system has voice cards, uninstall the Intel Dialogic software.

   • Remove the Cisco Unity-specific accounts, such as the Example Subscriber.

   • When the uninstall program has completed, restart the server.

3. Attach the 3.1(5) system key to the Cisco Unity server.

4. Install Cisco Unity 3.1(5) software by using the same account that was previously used to install or upgrade to Cisco Unity 3.1(5). Refer to the “Installing Cisco Unity Software” section of the Cisco Unity 3.1(5) installation guide.

5. Use the Cisco Unity Disaster Recovery Restore tool to restore data that was backed up from the Cisco Unity 3.1(5) system before the upgrade to Cisco Unity 4.0. The latest version of the Disaster Recovery Restore tool is available at Cisco Unity Tools . Refer to the online help for the tool.

   Note: Do not add subscribers to the Cisco Unity system before restoring the data.

6. While Cisco Unity is running, run the Cisco Unity Directory Walker utility and fix any errors that occur. The latest version of the Directory Walker utility is available at Cisco Unity Tools . Refer to the online help for the utility.

7. Test the system to verify that Cisco Unity answers calls properly and that users can access messages by using the phone.

8. To work around caveat CSCea13833, reconfigure IIS settings to work properly with Cisco Unity 3.1(5). Follow the steps below.

   1. On the Windows Start menu, click Programs > Administrative Tools > Internet Services Manager.

   2. Double-click <System-name> to expand it.

   3. Double-click Default Web Siteto expand it.

   4. Right-click ActiveAssistant, and click Properties.

   5. In the Properties dialog box, click the Virtual Directory tab.

   6. Click A Directory Located on this Computer.

   7. Repeat steps d through f for the VisualMessagingInterface directory and for the AA and VMI directories under the Web directory.

   8. Close Internet Services Manager.

Task List for Downgrading from Cisco Unity Version 4.0 to Version 3.1(5) with Failover

Follow the instructions provided below:

1. Obtain an activation code for the Cisco Unity 3.1(5) system keys for the primary and secondary Cisco Unity servers. Call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team, or send e-mail to licensing@cisco.com .

2. Do the following five subtasks to remove the Unity 4.0(1) failover configuration:

   1. Make the secondary server active.

   2. On both the primary and secondary servers, disable failover and stop file replication.

   3. On the primary server, disable SQL replication.

   4. On both the primary and secondary servers, delete references to the Node Manager service.

   5. On both the primary and secondary servers, disable sharing in the directories used by failover.

3. On the secondary Cisco Unity server, uninstall Cisco Unity 4.0 software by running the utility to uninstall Cisco Unity versions 3.x and 4.0. The latest version of the utility is available at Cisco Unity Tools . Refer to the online help for the utility. Do the following as you uninstall the software:

   • If the system has voice cards, uninstall the Intel Dialogic software.

   • DO NOT remove the Cisco Unity-specific accounts, such as the Example Subscriber. (These accounts are shared with the primary server and if you remove them before uninstalling the Cisco Unity software on the primary server, the uninstall will fail.)

   • When the uninstall program has completed, restart the server.

4. On the primary Cisco Unity server, uninstall Cisco Unity 4.0 software by running the utility to uninstall Cisco Unity versions 3.x and 4.0. Refer to the online help for the utility. Do the following as you uninstall the software:

   • If the system has voice cards, uninstall the Intel Dialogic software.

   • Remove the Cisco Unity-specific accounts, such as the Example Subscriber.

   • When the uninstall program has completed, restart the server.

5. Attach the 3.1(5) system keys to both the primary and secondary Cisco Unity servers.

6. On the primary and secondary Cisco Unity servers, install Cisco Unity 3.1(5) software by using the same account that was previously used to install or upgrade to Cisco Unity 3.1(5). Follow the instructions in the Cisco Unity 3.1 Installation Guide but DO NOT run the Configure Cisco Unity Failover wizard on either the primary or the secondary server. This task list alerts you when to run the Configure Cisco Unity Failover wizard on each server later in the downgrade process. Refer to the “Installing Cisco Unity Software” section of the Cisco Unity 3.1(5) installation guide.

7. On the primary Cisco Unity server, use the Cisco Unity Disaster Recovery Restore tool to restore data that was backed up from the secondary server of the Cisco Unity 3.1(5) system before the upgrade to Cisco Unity 4.0. The Disaster Recovery Restore tool is available at Cisco Unity Tools . Refer to the online help for the tool.

   Note: Do not add subscribers to the Cisco Unity system before restoring the data.

8. On the primary Cisco Unity server, run the Cisco Unity Telephony Integration Manager (UTIM) to reconfigure the integration. (The secondary server’s integration data is restored onto the primary server in task 7.)

9. On the primary Cisco Unity server, run the Configure Cisco Unity Failover wizard.

10. On the secondary Cisco Unity server, run the Configure Cisco Unity Failover wizard.

11. While Cisco Unity is running, on both the primary and secondary Cisco Unity servers, run the Cisco Unity Directory Walker utility and fix any errors that occur. The latest version of the Directory Walker utility is available at Cisco Unity Tools . Refer to the online help for the utility.

12. Test the system to verify that Cisco Unity answers calls properly and that users can access messages by using the phone. Additionally, test failover and failback functionality.

13. To work around caveat CSCea13833, on the primary and secondary Cisco Unity servers, reconfigure IIS settings to work properly with Cisco Unity 3.1(5):

    1. On the Windows Start menu, click Programs > Administrative Tools > Internet Services Manager.

    2. Double-click <System-name> to expand it.

    3. Double-click Default Web Site to expand it.

    4. Right-click ActiveAssistant, and click Properties.

    5. In the Properties dialog box, click the Virtual Directory tab.

    6. Click A Directory Located on this Computer.

    7. Repeat steps d through f for the VisualMessagingInterface directory and for the AA and VMI directories under the Web directory.

    8. Close Internet Services Manager.

NetPro Discussion Forums - Featured Conversations

Related Information

• Release Notes for Cisco Unity
• Cisco Unity Failover Configuration and Administration Guide (with Microsoft Exchange)
• Cisco Unity Installation Guide (With Microsoft Exchange)
• Cisco Unity System Requirements, and Supported Hardware and Software
• Voice Technology Support
• Voice and IP Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support - Cisco Systems