About this Document


This document provides installation instructions for ICM11.6(1)_ES9_24_build_21. Please review all sections in this document pertaining to installation before installing the product. Failure to install this engineering special as described may result in inconsistent ICM behavior.

This document contains these sections:

Signup to Receive Email Notification of New Field Notices


The Product Alert Tool offers you the ability to set up one or more profiles that will enable you to receive email notification of new Field Notices, Product Alerts or End of Sale information for the products that you have selected.

The Product Alert Tool is available at http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice

About Cisco ICM (and ICM Engineering Specials)


Explain how this particular patch (service release or engineering special) is used -- does it play nice with other patches?
Be sure to include ALL of the changes for the files you're delivering, i.e. all of the info from the release notes of the previous ES which included these files.

ICM Compatibility and Support Specifications


ICM Version Support

ICM11.6(1)_ES9_24_build_21

ICM Component Support

Supported ICM Components

ICM11.6(1)_ES9_24_build_21 is compatible with and should be installed on these ICM components:

All ICM components

Unsupported ICM Components

Do not install this engineering special on any of the following components:

Non ICM components

ICM Engineering Special Installation Planning


Installing ICM11.6(1)_ES9_24_build_21


Installation of this patch requires that all ICM services are shut down during the entire installation process. It is always recommended to install this ES during a scheduled downtime.

·       Using the ICM Service Control, stop all the ICM services running on the system

·       Launch the Installer provided for ES9 and following the instructions on the screen

·       Using the ICM Service Control, start all ICM services again.


This section is where you should include actual step-by-step installation instructions.

Uninstall Directions for ICM11.6(1)_ES9_24_build_21


To uninstall this patch, go to Control Panel. Select "Add or Remove Programs". Find the installed patch in the list and select "Remove".

Note: Patches have to be removed in the reverse order in which they were installed. For example, if you had installed patches 3, then 5, then 10 for a product, you will need to uninstall patches 10, 5 and 3 in that order to remove all patches for that product.

Specification Based Hardware Support Instruction in this Engineering Special


Select and Initialize the Packaged CCE Deployment

The steps for selecting and initializing your deployment type depend on which deployment type you are using.

Initialize the Packaged CCE Deployment Type

When you sign into Unified CCE Administration for the first time, you are prompted to enter information and credentials for the components in your deployment. Packaged CCE uses this information to configure the components and build the System Inventory.

Procedure

Step 1:

On the Deployment page, select the instance from the Instance drop-down list. You must be a member of the Setup security group for the instance you select. Click Next.Note The system does not support IP address change. Use the hostname if you foresee a change in IP address. This is applicable for all the Hostname/ IP Address fields.

Step 2:

On the VM Host page, enter the IP address, Username, and Password for the VMware hosts for Side A and Side B. Select the hardware layout type as Tested Reference Configuration or Specification Based Hardware. Click Next.The VMware hosts are the two servers on which ESXi is installed. The username and password fields are the host login names and passwords configured in ESXi.

Packaged CCE validates the hosts in your deployment.

                If you select Tested Reference Configuration and click Next, the system checks if the hardware is supported UCS hardware and verifies if the VMs are configured as per the reference design. If the validation is successful, the Credentials page opens.

                If you select Specification Based Hardware and click Next, the system validates the hardware specifications of the VMware host and verifies if the VMs are configured as per the reference design. If the validation is successful, click Next to open the Credentials page. See the Virtualization for Cisco Packaged CCE at http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​voice_ip_comm/​uc_system/​virtualization/​pcce_​virt_​index.html for hardware specifications.

                If the validation fails, click Update Hosts to go back to the VM Hosts page and edit the values. Click Retry to run the validation with existing values.

Note

                           Datastores used by Cisco VMs should not be shared or used by other third-party VMs.

Packaged CCE core components include:

                                       Unified CCE Rogger

Unified CCE AW/HDS/DDS

Unified CCE PG

Unified CVP Server

Unified CVP OAMP Server

UnifiedIntelligence Center Publisher

Finesse

                                    VM annotations are used to identify Packaged CCE core component VMs. Do not change the default annotations of any of the core component VMs. The following terms are reserved for core component annotations: Cisco, Finesse, CUIC, and CVP. Do not use these reserved terms in the annotations of any of the non-core component VMs.

Step 3

On the Credentials page, enter the specified information for each component in your deployment. After entering information for a component, click Next.The system validates the credentials you entered before prompting you for the next component's information.

Component

Information Required

Unified CM

Either:

   The Unified CM Publisher for an on-box Unified Communications Manager deployment.

   The Unified CM Publisher Name and IP address for an external Unified Communications Manager deployment.

Note Only a single Unified CM cluster can be integrated to a single

Packaged CCE deployment. AXL username and password.

Unified CVP

Unified CVP Server (Side A) username and password. Unified CVP Server (Side B) username and password.

Unified CCE AW-HDS-DDS

Unified CCE Diagnostic Framework Service domain, username, and password.

These credentials must be for a domain user who is a member of the Config security group for the instance, and valid on all Unified CCE components in your deployment (the Side A and Side B Unified CCE Roggers, PGs, and AW-HDS-DDSs).

Unified Intelligence Center

Unified Intelligence Center Administration application username and password. Identity Service Administration username and password.

Finesse

Finesse Administration username and password.

 

Step 4

On the Settings page, select the following:

   Select the codec used for Mobile Agent calls from the Mobile Agent Codec drop-down menu. The codec you select must match the codec specified on the voice gateways.

   If you have an external Unified Communications Manager, select the Unified CM Subscribers to which the Side A and Side B Unified CCE PGs connect from the Side A Connection and Side B Connection drop-down menus.

   For the Automatically create service accounts check box, either:

Leave the check box checked if you want automated initialization to create the service accounts in Active Directory. These accounts will be created and added to the Service group.

Uncheck the check box if you want to use an existing Active Directory account. Enter the username and password for an existing Active Directory user in the same domain as the Packaged CCE servers. This account will be added to the Service       group. Click Next.

The deployment is initialized. The Details dialog box displays the status of the automated initialization tasks.

Step 5

After the automated initialization tasks complete, click Done. The System Inventory opens. If one of the automated initialization tasks fails, correct the errors and then click Retry.

If the retry is successful, the automated initialization continues.

For some task failures, all completed tasks must be reverted before the task can be retried. You see a message informing you that the system needs to be reverted to a clean state.

Click OK, and then after the system is in a clean state, click Start Over.

 

Note : For complete documentation pleases refer to the Package CCE Specification Based Hardware_01


Obtaining Documentation


The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance


Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to: http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website: http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows: