About this Document

This document provides installation instructions for Unified CCE 12.5(1) ES88. 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(1) ES88 on these Unified CCE components:

Unsupported Unified CCE Components

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

Unified CCE Engineering Special Installation Planning

Installing Unified CCE 12.5(1) ES88

Installation of this patch requires that all Unified CCE services be shut down during the entire period of installation.

  1. It is always recommended to install this ES during a scheduled downtime.
  2. Using the Unified CCE Service Control, stop all the Unified CCE Services running on the system.
  3. Launch the installer provided and follow the instructions on the screen.
  4. Check the version of tomcat installed by running \tomcat\bin\version.bat . If its 9.0.37 or higher, then do the following steps.

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.5(1) ES88

  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(1) ES88

This section lists caveats specifically resolved by Unified CCE 12.5(1) ES88.

Index of Resolved Caveats

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

Identifier   Severity  Component  Headline
CSCvz74481  2  pg.opc  UCCE 12.5 OPC Exception due to not clearing CID.

Detailed list of Resolved Caveats in This Engineering Special

Caveats are ordered by severity then defect number.

Defect Number: CSCvz74481

Component: pg.opc

Severity: 2

Headline: UCCE 12.5 OPC Exception due to not clearing CID.


Symptom: Fault Exception in OPC causes the service to restart. All Agents are kicked out of Finesse and all calls in IVR Treatment will be dropped.

Conditions: Seen to happen on Version UCCE 12.5 Call stack: Address Frame 00A8A3B0 009BFA00 ConnectionIDObj::GetDeviceIDType+0 00A9C3B2 009BFA48 ProcessReassignCallIDInd+82 00A9AB35 009BFA68 CSTAPrivateEventMessages+E5 00A9A450 009BFA84 CSTAPrivateEvent+40 00B7743E 009BFA9C ProcessCSTAMsg+8E 00B7787C 009BFACC ProcessPIMMsgs+23C 00BF7AF1 009BFB3C invoke_message_handler+A1 00BF712D 009BFB50 MDSStartClient+25D 00AC99BF 009BFBA8 OPCInput::MDSInput+1FF 00AC9C28 009BFBD0 OPCInput::ProcessInput+48 00ACB0E1 009BFC04 OPCInput::StartInput+1D1 00AEB2C3 009BFC3C OPCMain::Execute+673

Workaround: None at this time

Further Problem Description: Looks to be triggering by a Hold event from a device that the last Call ID associated to it didn't get cleared from. //~45 mins ago there was post routed call ID 2130706734 associated with device 1033231. This call object was not cleared 09:36:00:386 pg1a-opc Trace: CSTA_SERVICE_INITIATED(PID=5000): InitiatedConn=(CID=2130706734,Dev=1033231,Type=Static) localConnInfo(1)=CS_INITIATE cause=-1 09:36:00:386 pg1a-opc Trace: AssignNewCallID - ASTID=8695 Periph#=5433231 OldCID=2130706734 NewCID=17176264) AgentObj=59FD750 //From OPCPlayback logs, 10:59:26:559 PG1A-opc Trace: CSTA_HELD(PID=5000): HeldConn=(CID=33984774,Dev=1033231,Type=Static) HoldingDev=(DEV)1033231 localConnInfo(4)=CS_HOLD cause=-1 //While OPC processing Service Initiate event for device 1033231, it crashed 10:16:29:961 pg1a-pim1 Trace: ServiceInitiated: CID=17177515 ConnDevID=1033231/0 ConsOrigCID=33984774 ConsOrigConnDevID=1033231/0 LocalConn=1 Cause=-1UniqueID=0000000000061BAB02489B9F00000000 DevTgDevStr=1033231 10:16:29:961 pg1a-pim1 Trace: CSTA SERVICE INITIATED, TelephonyDriver::ServiceInitiated: SENT TO OPC CallID = 17177515 DeviceID = 1033231 DeviceType = Static LocalState = INITIATE Cause = EC_NONE 10:59:26:559 PG1A-opc Trace: 692218197 1 CSTA_PRIVATE::PROCESS_REASSIGN_CALLID_IND - Connection=(CallID=2130706734 Device=1033231 Type=) NewCallID=17177515 RequestedCallObj=0x0 10:59:26:831 PG1A-opc Trace: CExceptionHandlerEx::GenerateMiniDump -- A Mini Dump File is available at C:\icm\bin\OPC-CCE.EXE_20210922105926559.mdmp 10:59:27:445 PG1A-opc Unhandled Exception: Exception code: C0000005 ACCESS_VIOLATION Fault address: 0092A410 01:00089410 C:\icm\bin\OPC-CCE.EXE Registers: EAX:00000001 EBX:00000028 ECX:00000028 EDX:0860EB94

Caveats resolved in earlier ESs and included as part of Unified CCE 12.5(1) ES88

Identifier   Severity  Component  Headline
CSCvu96298  2  pg.opc  The UTC Fields are not initialized causing HLGR to fail.
CSCvw90640  2  pg.opc  ECC Variables Not Maintaining when Transferred between Avaya 12.5 Peripheral.
CSCvp83424  2  pg.opc  PG OPC crash during state transfer.
CSCvu89253  3  pg.opc  ICM 12.5 Router call key is not maintained for a transfer scenario.
CSCvy08809  3  pg.opc  Skill Group Interval NetTransferOutCalls field not updated for the network Transfer.
CSCvt06136  3  pg.opc  opc-tdm.exe crashed with a mini dump.

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: