Packaged Contact Center Enterprise supports Symantec Endpoint Protection 12.1.
Be aware that the firewall component of Symantec Endpoint Protection 12.1, the Network Threat Protection feature, must be disabled. If the feature is enabled, both sides of a duplexed router come up in simplex mode, thus blocking communication between each side of a router. This blocking impacts all deployment types.
The problem occurs if you install Symantec Endpoint Protection 12.1 and leave the default settings. If you start services on side A and B of the router, a Symantec message pops up in the system tray indicating: The client will block traffic from IP address [side A router address] for the next 600 seconds(s). The same message is also written to the security log in client management. The Symantec Network Threat Protection traffic log indicates that a default firewall rule called “Block_all” was dynamically enabled. The result, according to the router logs, is that both sides of the router come up in simplex mode.
To resolve the issue, you must disable the Symantec firewall and restart both sides of the router. To do this, double click the Symantec icon in the system tray and select Change Settings. Then configure settings for Network Threat Protection and uncheck the Enable Firewall checkbox at the top of the Firewall tab.
Unified Customer Voice Portal (Unified CVP) Reporting Server
In Packaged CCE 9.0(1), you can install an optional VM for the Unified Customer Voice Portal (Unified CVP) Reporting Server. This server enables you to use the Courtesy Callback feature and run the CVP reports for Courtesy Callback. It also allows you to do IVR application reporting.
However, before the Unified CVP Reporting Server is set up, the deployment type must be changed and System Validation must be run. Note that while these actions are required in Packaged CCE 9.0(1), the issue will be resolved in release 9.0(2).
Unified Communications Manager (Unified CM) Publisher and Subscribers VMs
In Packaged Contact Center Enterprise 9.0(1), the Unified Communications Manager (Unified CM) publisher and subscribers VMs are not required to be on the Side A or B ESXi hosts for execution. However, they are required for the System Validation that must be run before the deployment type can be changed to PCCE.
In order to run the Unified CM publisher and subscribers on separate hardware, you will need the upcoming maintenance release, Cisco Unified Contact Center Enterprise 9.0(2).
Cisco Release Notes normally include tables listing all defects of the following severity levels:
1 or 2
3 (if found by customer use)
Defects are either Open or Resolved (fixed).
Table 1 Open Defects in This Release
Queue To Agent should not require Ent Route or Ent Skill Group for PCCE
CTIOS Dev Guide should say dumpargs does not work with call vars
trace mask for callvariable logging needs to be documented
Blank CallingDeviceID in any Inbound call to CTISvr drops Dialer calls
Websetup for Logger doesnt define public medium addresss
baDialer minidump when attempting a call back
EnablementMask incorrect when caller hangs up before NR agent answers
Wrong CTIOS enablement mask when Silent Monitor ends after the call
Database Schema Handbook updates to clarify why null values
PG OPC does not generate agent outbound option completed tasks data
Bug Search Tool
If you have an account with Cisco.com, you can use the Bug Search tool to find caveats of any severity for any release.