Installation Guide for Cisco Unity Unified Messaging with Microsoft Exchange 5.5 (With Failover Configured), Release 4.0(5) and Later
Overview of Mandatory Tasks for Installing Cisco Unity

Table Of Contents

Overview of Mandatory Tasks for Installing Cisco Unity

Part 1: Installing and Configuring the Cisco Unity Server

Part 2: Installing the Secondary Server for Cisco Unity Failover

Part 3: Populating the Cisco Unity System with Subscriber and Call Management Data

Part 4: Configuring Failover and Setting Up Networking Options (If Applicable)

Part 5: Customizing the Cisco Unity Conversation

Part 6: Backing Up Cisco Unity

Part 7: Training


Overview of Mandatory Tasks for Installing Cisco Unity



Note If you are upgrading Cisco Unity, refer instead to the Cisco Unity Reconfiguration and Upgrade Guide for upgrade instructions.


Use the following high-level task list to install the Cisco Unity system correctly. The tasks reference detailed instructions in the Cisco Unity installation guide, and in other Cisco Unity documentation as noted. Follow the documentation for a successful installation.

The task list leads you through the complete installation of the Cisco Unity system—from installing and configuring the Cisco Unity server; to populating the Cisco Unity system with subscriber and call management data; to setting up optional features, such as failover and networking; to backing up Cisco Unity.


Note Cisco assumes that the Exchange environment is already set up and working before the Cisco Unity system is installed.


The list is divided into seven parts. Some of the tasks apply only to specific situations, and are noted as such. If a task does not apply to your situation, skip it.

We recommend that you check off tasks as you complete them.

Part 1: Installing and Configuring the Cisco Unity Server

The tasks in Part 1 reference chapters in the Cisco Unity installation guide, unless otherwise noted.


Note Begin the installation on the computer that will be the primary Cisco Unity server. The task list alerts you when to install the secondary Cisco Unity server. Both servers must have the same enabled features and configurations.


1. Confirm that you are using the correct version of the Cisco Unity installation guide for your configuration. This version of the guide is for Cisco Unity 4.0(5) and later Unified Messaging with Exchange 5.5, configured for failover. You use this guide only when all subscriber mailboxes will be homed in Exchange 5.5. For a list of configurations and applicable installation guides, refer to the document Use the Installation Guide That Matches the Cisco Unity 4.0(5) or Later Configuration at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/inst/inst405/405list.htm.

2. Verify the following requirements:

a. System requirements for the Cisco Unity 4.0 system, including requirements for the failover feature. Refer to Cisco Unity 4.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/41/requirements/40_41cusysreq.html.

b. Requirements for integrating the phone system(s), including requirements for the failover feature. Refer to the "Requirements" section of the applicable Cisco Unity integration guide(s) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

c. If the system is using Cisco Unity Bridge Networking: Requirements for the Bridge. Refer to Cisco Unity Bridge 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/sysreq/30bsysrq.htm.

d. If the system is using any Cisco Unity networking option (including the Bridge): Requirements for the networking option. Refer to Cisco Unity Networking Options Requirements at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/netrq.htm.

3. Gather the documentation and tools for the installation, download the latest Microsoft updates and other software, and determine the drive locations for application, log, and database files that you will need later in the installation. See Chapter 2, "Preparing for the Installation."

4. Set up or program the phone system(s) and extensions to enable the integration(s) with Cisco Unity. Refer to the "Programming the <Name> Phone System" section of the applicable Cisco Unity integration guide(s) at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

5. Set up the Cisco Unity server, install voice cards and attach peripheral devices, if applicable, and make connections from the phone system. See Chapter 3, "Setting Up the Hardware."

6. Configure the RAID arrays, if applicable, install Windows 2000 Server, and create the logical drives, if applicable. See Chapter 4, "Installing the Operating System."

7. Obtain Cisco Unity license files, and use the Cisco Unity System Preparation Assistant to configure the operating system and install required software components. Then set up the server in the Windows networking environment. See Chapter 5, "Customizing the Cisco Unity Platform."

8. Install and configure the applicable Exchange software. See Chapter 6, "Setting Up Exchange."

9. Create the accounts required for the Cisco Unity installation, and set rights and permissions. See Chapter 7, "Creating Accounts for the Installation and Setting Rights and Permissions."

10. Decide whether to set up Cisco Unity to use SSL and install the Microsoft Certificate Services component, if applicable, then use the Cisco Unity Installation and Configuration Assistant to install and configure Cisco Unity software, and to set up the Cisco Personal Communications Assistant to use SSL, if applicable. You also set up the Cisco Unity Administrator and the Status Monitor to use SSL, if applicable, then secure the Example Administrator account against toll fraud, and move SQL Server database files and transaction logs, if applicable. See Chapter 8, "Installing and Configuring Cisco Unity Software."

11. Install any optional software. See Chapter 9, "Installing Optional Software."


Caution Do not install Microsoft Outlook on the Cisco Unity server, or Cisco Unity may not notify subscribers of new messages.

12. Create an emergency repair disk that can be used to repair and restart Windows, if it is damaged. Refer to Windows Help.

13. Determine the authentication method that you want to use for the Cisco Unity Administrator web application, and configure IIS, as applicable. See Chapter 10, "Setting Up Authentication for the Cisco Unity Administrator."

Part 2: Installing the Secondary Server for Cisco Unity Failover

The tasks in Part 2 reference chapters in the Cisco Unity installation guide, unless otherwise noted.

14. With a Cisco CallManager integration only: On the phone system, add the voice messaging ports that will be used by the secondary server. Refer to the "Programming the Cisco CallManager Phone System" section of the applicable Cisco CallManager integration guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

15. On the secondary server, repeat the following Part 1 tasks, depending on the phone system integration being used:

For Cisco CallManager, repeat Task 6. through Task 8.

For a circuit-switched phone system, repeat Task 5. through Task 8.

16. For the same accounts that you created in Task 9., add the Cisco Unity administration account to the local Administrators group, and run the Cisco Unity Permissions wizard to set rights and permissions. See Chapter 7, "Creating Accounts for the Installation and Setting Rights and Permissions."

17. Use the Cisco Unity Installation and Configuration Assistant to install and configure Cisco Unity software, and to set up the Cisco PCA to use SSL, if applicable. You also set up the Cisco Unity Administrator and the Status Monitor to use SSL, if applicable, and move SQL Server database files and transaction logs, if applicable. See Chapter 8, "Installing and Configuring Cisco Unity Software."

18. Install any optional software. See Chapter 9, "Installing Optional Software."

19. Create an emergency repair disk that can be used to repair and restart Windows, if it is damaged. Refer to Windows Help.

20. Configure IIS so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, if you decided to use that method. See Chapter 10, "Setting Up Authentication for the Cisco Unity Administrator."

21. Store all of the software that was shipped with Cisco Unity together in a location that is safe and can be readily accessed. You may need the discs later to upgrade or to otherwise modify the Cisco Unity system, or Cisco TAC may require you to access them during a service call.

Part 3: Populating the Cisco Unity System with Subscriber and Call Management Data

You do most of the tasks in Part 3 by using the Cisco Unity Administrator. (For information on logging on to the Cisco Unity Administrator and on using it, refer to the "Accessing the Cisco Unity Administrator" chapter of the Cisco Unity System Administration Guide.)

The tasks reference chapters in the Cisco Unity System Administration Guide, Release 4.0(5) that contain detailed information; the guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/sag/sag405/ex/index.htm.


Note Do these tasks on the primary Cisco Unity server. Subscriber and call management data will be replicated to the secondary Cisco Unity server after you configure failover later in the installation.


22. Define system schedules:

a. Identify standard business hours.

b. Identify closed and weekend hours.

c. Create custom schedules, if necessary.

d. Identify holidays.

Refer to the "Schedule Settings" and "Holiday Settings" sections in the "System Settings" chapter.

23. Set up phone, GUI, and TTS languages (including TTY, if applicable). Refer to the "Languages" chapter.

24. Set up third-party fax, if applicable. Refer to the "Integrating a Fax Server with Cisco Unity" chapter.

25. Create a call management plan. Refer to the "Call Management" chapter.

26. Prepare to create regular subscriber accounts. Refer to the "Before Creating Regular Subscriber Accounts" section in the "Creating Subscriber Accounts" chapter.

a. Confirm that you have the necessary permissions for creating subscriber accounts and that Cisco Unity is configured properly to work with the message store.

b. Confirm that you have the applicable licenses.

c. Determine password and account lockout policy for Cisco Unity phone access.

d. Determine logon, password, and account lockout policy for Cisco Unity web access.

e. Set up enhanced phone security, if applicable.

f. Review, change, and create classes of service.

g. Create restriction tables, and assign them to the appropriate class(es) of service.

h. Create public distribution lists.

i. Review, create, and modify subscriber templates. Secure phone passwords, and, as applicable, secure Windows domain account passwords.

j. As needed, change the locale ID of the MAPI profile for the Cisco Unity server.

27. Set up the Cisco Unity Hospitality and property management system integration, if applicable. Refer to the "Hospitality and Property Management System Integration" chapter.

28. Test the system configuration:

a. Add a single subscriber (refer to the "Creating Subscriber Accounts" chapter).

b. Use the phone to log on to Cisco Unity as the test subscriber, record a voice name, and set a phone password. Hang up.

c. Call Cisco Unity and log on as the test subscriber again to confirm that the password, greeting, and conversation style specified for the subscriber are working properly. Confirm that the subscriber inherited the correct class of service by testing any applicable features by phone.

d. Log on to the Cisco Personal Communications Assistant (PCA) as the test subscriber. If you gave the test subscriber the required class of service rights, test to see if you can browse from the Cisco PCA Welcome page to the Cisco Unity Assistant. If you gave the test subscriber the required class of service rights, test to see if you can browse to the Cisco Unity Inbox.

e. Make corrections to the system configuration as necessary.

29. Create subscriber accounts. Refer to the "Creating Subscriber Accounts" chapter.

30. If you used the Cisco Unity Administrator to create more than 100 subscribers: Run the Exchange 5.5 Optimizer. Refer to the "Adding Large Numbers of Subscribers to Cisco Unity with Exchange 5.5" section in the "Creating Subscriber Accounts" chapter.

31. Hide users in the Exchange address book, if applicable. Refer to the "Preventing Subscribers from Appearing in Outlook Address Books" section in the "Creating Subscriber Accounts" chapter.

32. Modify individual subscriber accounts as needed. Refer to the "After Creating Subscriber Accounts" section in the "Creating Subscriber Accounts" chapter.

33. Add individual subscribers to public distribution lists, as needed. (For example, assign subscribers to screen those messages left in Cisco Unity that are not associated with a specific recipient, such as those left to the Unaddressed Messages distribution list or for the Opening Greeting call handler.) Refer to the "Message Handling" section in the "Default Accounts and Message Handling" chapter.

34. Implement, then test the call management plan you created in Task 25.:

a. Create call handlers. Refer to the "Call Handler Settings" chapter.

b. Specify directory handler settings. Refer to the "Directory Handler Settings" chapter.

c. Create interview handlers. Refer to the "Interview Handler Settings" chapter.

d. Set up call routing. Refer to the "Call Routing" chapter.

35. Review the substitute objects on the System > Configuration > Settings page of the Cisco Unity Administrator. The objects are Substitute Recipient, Substitute Owner, Substitute After Message Call Handler, and Substitute Exit Call Handler. Cisco Unity uses the objects to substitute references to any subscriber that is deleted by using the Cisco Unity Administrator without first reassigning such references (for example, ownership of a call handler or distribution list). For new installations, the Example Administrator is configured as the Substitute Recipient and Substitute Owner, and the Goodbye call handler is configured as the Substitute After Message Call Handler and Substitute Exit Call Handler. For upgrades, any changes made to the defaults will not be overwritten. However, we recommend that you review these settings now and update them if you wish to use different substitute objects. Refer to Cisco Unity Administrator Help for a description of each object and where it applies.

36. As appropriate, set up subscribers to use their phones to access Cisco Unity, specify their recording and playback device, install Cisco Unity ViewMail for Microsoft Outlook, and set up text-message notificaitons. Refer to the "Setting Up Cisco Unity Applications on Subscriber Workstations" chapter.

Part 4: Configuring Failover and Setting Up Networking Options (If Applicable)

37. Configure Cisco Unity failover. Refer to the "Configuring Cisco Unity Failover" chapter of the Cisco Unity Failover Configuration and Administration Guide, Release 4.x at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/fail/fail401/ex/index.htm.

38. If the system is using Digital Networking: Set up Digital Networking. Refer to the "Digital Networking"chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm. (Note that the settings for Digital Networking are replicated to the secondary server.)

39. If the system is using Internet Subscribers: Set up Internet subscribers. Refer to the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm.

40. If the system is using SMTP Networking: Set up SMTP Networking. Refer to the "SMTP Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm. (Note that the settings for SMTP Networking are replicated to the secondary server.)

41. If the system is using AMIS Networking: Set up AMIS Networking. Refer to the "AMIS Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm. (Note that the settings for AMIS Networking are replicated to the secondary server.)

42. If the system is using VPIM Networking: Set up VPIM Networking. Refer to the "VPIM Networking" chapter of the Networking in Cisco Unity Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/net/net405/ex/index.htm. (Note that the settings for VPIM Networking are replicated to the secondary server.)

43. If the system is using Bridge Networking: Install the Cisco Unity Bridge server. Refer to the "Overview of Mandatory Tasks for Installing the Cisco Unity Bridge" chapter of the Cisco Unity Bridge Installation Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/big/big30/index.htm.

44. If the system is using Bridge Networking: Set up Cisco Unity and the Bridge for networking. Refer to the "Setting Up Cisco Unity and the Bridge for Networking" chapter of the Cisco Unity Bridge Networking Guide, Release 3.0 at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm. (Note that the settings for the Bridge are replicated to the secondary server.)

Part 5: Customizing the Cisco Unity Conversation

45. When callers access Cisco Unity by phone, they hear a set of prerecorded instructions and options known as the Cisco Unity conversation—or the TUI (telephone user interface).You can customize the conversations that subscribers and unidentified callers hear in several ways.

For example, you may want to change how Cisco Unity handles messages that are interrupted by disconnected calls, specify that Cisco Unity prompts subscribers to record first and then address when they send messages, offer "Easy" Sign-In and system transfers, or specify that Cisco Unity plays additional caller information when subscribers play messages. You may also want to set up the Cisco Unity Greetings Administrator or the Cisco Unity Broadcast Message Administrator for system administrators to use.

Refer to the "Cisco Unity Conversation" chapter of the Cisco Unity System Administration Guide for details on these and many other conversation customizations.

Part 6: Backing Up Cisco Unity

46. Back up Cisco Unity. Refer to the "About Backing Up a Cisco Unity System" chapter of the Cisco Unity Maintenance Guide, Release 4.0(5) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/maint/maint405/ex/index.htm.

Part 7: Training

47. Train subscribers, operators, and support desk personnel to use Cisco Unity. Refer to the "Preparing Subscribers, Operators, and Support Desk Personnel to Work with Cisco Unity" chapter of the Cisco Unity System Administration Guide.