About this Document

This document provides installation instructions for Unified CCE 12.6(1) ES60. 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.

About Cisco Unified CCE (and Unified CCE Engineering Specials)

As a part of this ES registry ,TotalCountsAPIRefreshRate has been introduced under the path Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\ucce\LoggerA\BlendedAgent\CurrentVersion . By default this Decimal registry value would be 0 and it is applicable for LegacyCampaign, For API based campaign this Decimal value could be set to 1 or more than that.

For API based campaigns to refresh real-time counters, set this registry to value: 6 ( updates counter internally at every 6x5 = 30sec). This value can be modified to change counters' refresh rate, but however this will have an impact on SQL. Based on internal testing, value 6 is recommended.

Note: Set the value to 0 for legacy campaigns.

Unified CCE Compatibility and Support Specifications

Note: Install ES38 before intsalling this ES

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.6(1) ES60 on the following Unified CCE component:

Note: Install ES38 before intsalling this ES

Unsupported Unified CCE Components

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

Unified CCE Engineering Special Installation Planning

Installing Unified CCE 12.6(1) ES60

Note: We recommend you to install this engineering special during a scheduled downtime.

To install the Unified CCE 12.6(1) ES60, follow the steps:

  1. Using Unified CCE Service Control, stop all the Unified CCE services running on the system for the whole installation process.
  2. Launch the installer and follow the instructions on the screen.
  3. After the installation of the engineering special, if the Unified CCE services are set to manual, start all the services using Unified CCE Service Control.

If the Unified CCE Services are set to manual, using the Unified CCE Service Control, start all the Unified CCE Services.

Uninstall Directions for Unified CCE 12.6(1) ES60

To uninstall Unified CCE 12.6(1) ES60, follow the steps:

  1. Go to Control Panel.
  2. Select Add or Remove Programs.
  3. Find the installed patch and click 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.

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.6(1) ES60

This section lists caveats specifically resolved by Unified CCE 12.6(1) ES60.

Index of Resolved Caveats

Caveats in this section are ordered by Unified CCE component, severity, and then by identifier.

Identifier  Severity  Component  Headline
CSCwd51837  2  outbound  Campaign Manager crashes without Minidump
CSCwe46199  2  outbound  CampaignManager is crashing with minidump importing contacts to the campaigns created via API
CSCvz92239  3  outbound  Available field have negative number in Outbound Campaign Report
CSCwe62557  3  outbound  TotalVoiceCount field is showing incorrect value after import API overwrite enabled
CSCwd91888  6  outbound  Procmon CLI to display active calls in CampaignManager

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity then defect number.

Defect Number: CSCwd51837

Component: outbound

Severity: 2

Headline: Campaign Manager crashes without Minidump


Symptom: Campaign Manager crashes without generating Minidump

Conditions: None

Workaround: None

Further Problem Description: 13:49:37:439 la-CampaignManager Trace: CCmMain::OnUnhandledException - Unhandled exception. Stopping ReplManager.
13:49:37:439 la-CampaignManager Trace: AsyncReplWriter stopping
13:49:37:439 la-CampaignManager Trace: CCmMain::OnUnhandledException - Unhandled exception. Stopping ReplManager.
13:49:37:439 la-CampaignManager Trace: AsyncReplWriter stopping
13:49:37:939 la-CampaignManager Trace: ReplWriter switching file CM_20221027081930830.tmp -> CM_20221027081937939.repl records 575
13:49:37:939 la-CampaignManager Trace: AsyncReplWriter thread exiting
13:49:37:939 la-CampaignManager Trace: AsyncReplWriter stopped
13:49:37:939 la-CampaignManager Trace: ReplReader stopping
13:49:38:923 la-CampaignManager Trace: ReplReader thread exiting without wait
13:49:38:923 la-CampaignManager Trace: ReplReader stopped
13:49:38:954 la-CampaignManager Trace: CExceptionHandlerEx::GenerateMiniDump -- MiniDumpWriteDump() failed. Last API Error [-2147024865]: A device attached to the system is not functioning.
13:49:38:986 la-CampaignManager Trace: CExceptionHandlerEx::Stack -- SymInitialize failed. Last API Error [8]: Not enough storage is available to process this command.

Defect Number: CSCwe46199

Component: outbound

Severity: 2

Headline: CampaignManager is crashing with minidump importing contacts to the campaigns created via API


Symptom: Campaign Manager Crash

Conditions: UCCE 12.6(1) ES 46, 54 Combination of Legacy Import + API Import for Campaigns

Workaround: None

Further Problem Description: Call stack:
Address Frame
012974F7 0438F5D4 CCmRule::ResetTotalCountStatForAPICase+3C
01297382 0438F60C CCmRule::QueryTotalCount+D2
0129769D 0438F61C CCmRule::SendRealTimeData+15
01272DC0 0438F62C CCmCampaignExt::SendRealTimeData+16
0129037E 0438F638 CmSendRealTimeData+21
01290209 0438FAAC CmMonitor+447
0128D48B 0438FAF8 CCmDispatch::OnMessage+67
012F0740 0438FB30 CThread::MessageLoop+99
012F059F 0438FB38 CThread::CallBack+B
76B6892F 0438FB70 ui64toa_s+1AF
76870419 0438FB80 BaseThreadInitThunk+19
774F72AD 0438FBDC RtlGetAppContainerNamedObjectPath+ED
774F727D 0438FBEC RtlGetAppContainerNamedObjectPath+BD
13:58:35:970 la-CampaignManager Trace: (EMTServer) Accept(): EMT connection accepted from IP: [10.17.47.17] CID: [22], on port: [40032].

Defect Number: CSCvz92239

Component: outbound

Severity: 3

Headline: Available field have negative number in Outbound Campaign Report


Symptom: The "Available" field in the report "Query Rule Within Campaign Real-Time" shows a negative number

Conditions: Outbound Import API with overwrite enabled

Workaround: None

Further Problem Description: None

Defect Number: CSCwe62557

Component: outbound

Severity: 3

Headline: TotalVoiceCount field is showing incorrect value after import API overwrite enabled


Symptom: The "Available" field in the report "Campaign_Query_Rule_Real_Time " shows a negative number with Outbound import API overwrite enabled

Conditions: Outbound Import API with overwrite enabled and accept the call in the finesse and check the TotalVoiceCount Value in Campaign_Query_Rule_Real_Time table

Workaround: It will reset the TotalVoiceCount value if the records are being cleared for DL table

Further Problem Description: It came up due to regression of CSCvz92239 ,it was showing the TVC =0 if no call has been accepted in the finesse which is expected behavior issue came up when call is being answered and checked the value of TVC, however it is being reset to 0 if records are cleared from DL table

Defect Number: CSCwd91888

Component: outbound

Severity: 6

Headline: Procmon CLI to display active calls in CampaignManager


Symptom: Procmon CLI to display active calls calls in CampaignManager

Conditions: None

Workaround: None

Further Problem Description: None

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: