About this Document

This document provides installation instructions for Unified CCE 12.5(2) ES33. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.

This document contains these sections:

Sign Up for Email Notification of New Field Notices

In the Product Alert Tool, you can set up profiles to receive email notification of new Field Notices, Product Alerts, or End of Sale information for your selected products.

The Product Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.

About Cisco Unified CCE (and Unified CCE Engineering Specials)

Unified CCE Compatibility and Support Specifications

Unified CCE Version Support

Unified CCE Component Support

This section lists the Unified CCE components on which you can and cannot install this engineering special.

Supported Unified CCE Components

You can install Unified CCE 12.5(2) ES33 on these Unified CCE components:

Unsupported Unified CCE Components

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

Unified CCE Engineering Special Installation Planning

Planning for maintenance window and downtime

The installation or uninstallation of this patch requires a planned maintenance window with some expected downtime of a few seconds / minutes. Yes

Installing Unified CCE 12.5(2) ES33

  1. Download the patch and copy the patch to the local server where patch is going to be installed.
  2. Stop all ICM services and applications running on the server.
  3. Run the patch installer exe and follow the instructions.
  4. Reboot the server on successful completion of the patch install.
  5. Start the ICM services.

Uninstall Directions for Unified CCE 12.5(2) ES33

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

Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.

Resolved Caveats in this Engineering Special

This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:

Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.

Resolved Caveats in Unified CCE 12.5(2) ES33

This section lists caveats specifically resolved by Unified CCE 12.5(2) ES33.

Index of Resolved Caveats

Caveats in this section are ordered by Unified CCE component, severity, and then identifier.
Identifier Severity Component Headline
CSCwh53860 3 tools Diagnostics Framework Portico broken after 12.5.2 ES30

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity then defect number.

Defect Number: CSCwh53860

Component: tools

Severity: 3

Headline: Diagnostics Framework Portico broken after 12.5.2 ES30


Symptom: unable to see status of process\service\product version anything after ES30 session logout

Conditions: when applying 12.5.2 ES30

Workaround:

Further Problem Description: Working logs without ES-30 Analysis We can see that the new request recived to show the lis of processes. And we can see the response at Sep 11 2023 10:04:21.454 +02:00: %ProcessOutgoingResponse-INFO-[8067842] *** COMPLETED PROCESSING REQUEST *** Total time taken to process 'ListProcesses' request: 00:00:00.1249912 Framework"> 1948: 125-AWS-B: Sep 11 2023 10:04:15.470 +02:00: %ProcessOutgoingResponse-INFO-[6137035] *** COMPLETED PROCESSING REQUEST *** Total time taken to process 'ListProcesses' request:00:00:00.1249973 1949: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %.ctor-INFO-[8067842] ***** NEW REQUEST RECEIVED ***** Request URI: https://localhost:7890/icm-dp/rest/DiagnosticPortal/ListProcesses?InstanceName=hcs12&Random=1694419461298 1950: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %checkForCSRFAttack-ERROR-[8067842] originHost : localhost:7890 :: originTargetHost : localhost:7890 1951: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %IsCookieValid-DEBUG-[8067842] Waiting to enter thread safe region 1952: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %IsCookieValid-DEBUG-[8067842] Entered thread safe region 1953: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %IsCookieValid-DEBUG-[8067842] Cookie provided by user is valid 1954: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %IsCookieValid-DEBUG-[8067842] Exited thread safe region 1955: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %IsUserAuthorized-INFO-[8067842] Domain user 'HCSCC\Administrator' pre-authorized via valid cookie. 1956: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %LogIncomingRequest-DEBUG-[8067842] URI query '/icm-dp/rest/DiagnosticPortal/ListProcesses?InstanceName=hcs12&Random=1694419461298' invoked 'ListProcesses' method with parameter(s): instanceName = 'hcs12' 1957: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %SanitizeUri-DEBUG-[8067842] Sanitizing URI parameter: hcs12 1958: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %SanitizeUri-DEBUG-[8067842] URI parameter is clean, no changes made while trying to sanitize = hcs12 1959: 125-AWS-B: Sep 11 2023 10:04:21.329 +02:00: %GetICMLongCompName-DEBUG-[8067842] Input parameter sInst is null or empty or there is only one instance, will not use the instance name 1960: 125-AWS-B: Sep 11 2023 10:04:21.438 +02:00: %ListProcesses-DEBUG-[8067842] command line string for the current instance and component is : "C:\icm\serviceability\diagnostics\bin\DiagFwSvc.exe" 1961: 125-AWS-B: Sep 11 2023 10:04:21.438 +02:00: %ListProcesses-DEBUG-[8067842] The Process Name is : DiagFwSvc.exe 1962: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ListProcesses-DEBUG-[8067842] The Process Description is : Cisco ICM Diagnostic Framework 1963: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ListProcesses-DEBUG-[8067842] The Process Name is : DiagFwSvc.exe 1964: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ListProcesses-DEBUG-[8067842] The Process Description is : Cisco ICM Diagnostic Framework 1965: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ListNonDynamicProcessStatus-DEBUG-[8067842] The non dynamic Process Status is : bin-DiagFwSvc.exe 1966: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ListProcesses-INFO-[8067842] Sending this reply: 1967: 125-AWS-B: Sep 11 2023 10:04:21.454 +02:00: %ProcessOutgoingResponse-INFO-[8067842] *** COMPLETED PROCESSING REQUEST *** Total time taken to process 'ListProcesses' request: 00:00:00.1249912 1968: 125-AWS-B: Sep 11 2023 10:04:25.345 +02:00: %OnStop-INFO-[14] Service Stopped Successfully [Diagnostic Framework: End of logging] Non-Working logs with ES-30 Analysis After the new request for list of processes received, we can see the error with session timer expired and hence logout the session- Sep 11 2023 10:11:37.147 +02:00: %SessionLogout-INFO-[5433727] ***** Session Timeout LOGOUT ***** Request 1797: 125-AWS-B: Sep 11 2023 10:11:37.072 +02:00: %.ctor-INFO-[5433727] ***** NEW REQUEST RECEIVED From UI ***** Request URI: https://localhost:7890/icm-dp/DiagnosticPortal/ListProcesses?InstanceName=hcs12&Random=1694419897057 1798: 125-AWS-B: Sep 11 2023 10:11:37.073 +02:00: %checkForCSRFAttack-ERROR-[5433727] originHost : localhost:7890 :: originTargetHost : localhost:7890 1799: 125-AWS-B: Sep 11 2023 10:11:37.144 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Waiting to enter thread safe region in IsSessionCookieValid 1800: 125-AWS-B: Sep 11 2023 10:11:37.145 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Entered thread safe region 1801: 125-AWS-B: Sep 11 2023 10:11:37.145 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Entry :d18b581ddf3b42aaa752c4d7460459ff Rcvd :Authorization=d18b581ddf3b42aaa752c4d7460459ff 1802: 125-AWS-B: Sep 11 2023 10:11:37.146 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Cookie found checking for expired 1803: 125-AWS-B: Sep 11 2023 10:11:37.146 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Cookie provided for session has expired 1804: 125-AWS-B: Sep 11 2023 10:11:37.147 +02:00: %IsSessionCookieValid-DEBUG-[5433727] Exited thread safe region in IsSessionCookieValid 1805: 125-AWS-B: Sep 11 2023 10:11:37.147 +02:00: %SessionLogout-INFO-[5433727] ***** Session Timeout LOGOUT ***** Request URI: https://localhost:7890/icm-dp/DiagnosticPortal/ListProcesses?InstanceName=hcs12&Random=1694419897057 1806: 125-AWS-B: Sep 11 2023 10:11:37.148 +02:00: %ProcessOutgoingResponse-WARN-[5433727] Reply stream from SessionLogout is null, the underlying assembly did not return a valid response 1807: 125-AWS-B: Sep 11 2023 10:11:37.149 +02:00: %ProcessOutgoingResponse-INFO-[5433727] *** COMPLETED PROCESSING REQUEST *** Total time taken to process 'SessionLogout' request: 00:00:00.0769963

Caveats resolved in earlier ESs and included as part of Unified CCE 12.5(2) ES33

Identifier Severity Component Headline
CSCwc63341 2 tools Diagnostic framework page is blank for domain user (part of admin group) after upgrading to 12.5.2
CSCwd88024 2 tools Diagnostic framework page is blank for domain user (part of config group) after upgrading to 12.5.2
CSCwc98312 6 tools Impact of Chrome deprecating Private Network Access on CCE
CSCwe78531 6 tools Session ID based Authentication and Authorization with Account lockout provision -Diagnostic Portico

Obtaining Documentation

You can access current Cisco documentation on the Support pages at the following sites:

Documentation Feedback

To provide comments about this document, send an email message to the following address:

contactcenterproducts_docfeedback@cisco.com

We appreciate your comments.

Obtaining Technical Assistance

Cisco.com is 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 site.

Cisco.com

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. You can also resolve technical issues with online technical support and download software packages. 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.

Technical Assistance Center

The Cisco TAC site 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 Site

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.

P3 and P4 level problems are defined as follows:

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

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 site: https://mycase.cloudapps.cisco.com/create/start/

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 sites:

P1 and P2 level problems are defined as follows: