About this Document
This document provides
installation instructions for Unified CCE 12.0(1) ES7. 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 12.0
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.0(1) ES7 on these Unified CCE components:
Unsupported Unified CCE Components
Do not install this
engineering special on the components other than the following components:
Unified CCE Engineering Special
Installation Planning
Installing Unified CCE
12.0(1) ES7
After installation of
Patch, please follow steps to install new stored procedures.
Installation of this
patch requires that all Unified CCE services be shut down during the
entire period of installation. It is always recommended to install this ET
during a scheduled downtime.
If the Unified CCE
Services are set to manual, using the Unified CCE Service Control, start all
the Unified CCE Services.
Please follow below
procedure to install new stored procedures post patch installation.
Installing New Stored Procedures:
StoredProcedures are
attached as part of ReplicationSQL_BatchFiles.rar file
in ES Patch.
Attachment(ReplicationSQL_BatchFiles) mainly contains
stored procedures(SP) to build DialingList table
from contact table and change sm_used field
in contact table. Details of attached files:
buildDL: stored procedure to build DL from contact table.
sm_used: stored procedure to update sm_used field in contact table.
DropBuildDL: Drop
installed BuildDL procedure
Dropsm_used: Drop installed sm_used procedure.
Syntax to run Batch
Files
(Run from command prompt
at ReplicationSQL_BatchFiles location):
------------------------------------------------------------------
BatchFile <Instance_Name> <Side>
Ex:BatchFile ucce A
Side can be A or B(it has to be with CAPSLOCK ON), it should reflect to BA
database name in system. Above example ba database
name was ucce_baA. This would install new stored
procedure under ‘programmability’ of ba database.
Follow below procedure
to install new StoredProcedures:
--------------------------------------------------------------------
1) Install ES Patch on both sides of loggers.
2) Go to unzipped folder of
ReplicationSQL_BatchFiles from command prompt.
3) Run below command on A
side
InstallReplicationsql <instance_name>
A
4) Run below command on B side
InstallReplicationsql <instance_name>
B
5) Make sure stored procedures are added under ‘programmability’ of ba database from SQL Server management studio.
6) Manually set stored procedure 'Replicate' property to 'Execution
of Stored Procedure'. by default it would to set to
'Stored Procedure definition only'
Uninstall Directions for Unified CCE 12.0(1) ES7
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.
Follow below procedure
to uninstall new StoredProcedures:
----------------------------------------------------------------------
1) Disable Replication on both sides of logger.
2) Go to unzipped folder of ReplicationSQL_BatchFiles from command
prompt.
3) Run below command on A side
DropReplicationsql <instance_name>
A
4) Run below command on B side
DropReplicationsql <instance_name>
B
5) Make sure stored procedures are deleted under ‘programmability’
of ba database from SQL Server management
studio.
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.0(1) ES7
This section lists
caveats specifically resolved by Unified CCE 12.0(1) ES7.
Index of Resolved Caveats
Caveats in this section
are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCvn65050 |
3 |
outbound |
Improve SQL replication
performance for overwrite imports, and doc limitations |
Detailed list of Resolved Caveats in This Engineering Special
Caveats are ordered by
severity then defect number.
Defect Number: CSCvn65050
Component: outbound
Severity: 3
Headline: Improve SQL replication performance for
overwrite imports, and doc limitations
Symptom: Replication of
contact dialing list status can be delayed by minutes or hours depending on
environment and use case which, on failover, can result in the same customers
being called twice, even if they were already successfully contacted
once.
Conditions: Outbound Option with High Availability enabled. *
Overwrite Imports (instead of append) * Large imports while campaigns are in
progress * Continuous high call rates approaching 120 CPS * WAN delays
exceeding 20 ms in the public network
between Side A and Side B
Workaround: Temporary Fix upon Campaign Manager failure with
replication delay: Import new updated dialing lists to the newly active
Campaign manager side, which will allow to prevent dialing the same customer
twice. One-time fix during maintenance window: * Stop both the sides of logger.
Disable the HA option via websetup in both
the sides. * Take a SQL backup of BA DB (whichever side has latest data).
Restore it to other side. * Enable Outbound HA via websetup on
both the sides. * Start both loggers. High demand customers may be better off
running in a warm standby model with a backup campaign manager running on Side
B logger, with SQL replication disabled. This approach will require you to
import new dialing lists to the newly active side upon failover, but will allow
you to prevent dialing the same customers twice.
Further Problem Description: Microsoft SQL Replication is a best
effort technology which does not guarantee fast replication. A combination of
factors including import type, import size while campaigns are in progress,
dialing consistently high call rates, and WAN delays can lead to large number
of pending replication commands.
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/
CContacting 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: