Cisco Cisco Unified Contact Center Enterprise 9.0(2) Release Notes
13
Release Notes for Cisco IPCC/ICM Enterprise & Hosted Editions Release 7.0(0) Installer Update C November 24, 2008
New and Changed Information
The Release 7.0(0) support of Active Directory has wide-ranging implications, including pre-installation
preparation, a requirement for native mode AD, and Organizational Unit (OU) allocation. The Staging
Guide for Cisco ICM/IPCC Enterprise & Hosted Editions should be read with care.
preparation, a requirement for native mode AD, and Organizational Unit (OU) allocation. The Staging
Guide for Cisco ICM/IPCC Enterprise & Hosted Editions should be read with care.
In particular, it should be noted that there is no support for Windows NT Domain Controllers.
It is recommended that member servers use the AD Domain Controllers as their DNS servers.
Note that Release 7.0(0) requires the domain to be (at least) at Windows 2000 native mode—mixed node
is NOT supported.
is NOT supported.
Add an Instance in ICM Setup; New Capabilities of ICMSetup in \icm\bin
Adding, editing, and deleting an ICM instance is now a standard part of ICM Setup.
In addition, many of the actions that could only be performed from the ICM Setup on the CD can now
be performed from the Setup (called ICMSetup.exe) in the local \icm\bin directory.
be performed from the Setup (called ICMSetup.exe) in the local \icm\bin directory.
For more information, refer to the ICM Installation Guide for Cisco ICM Enterprise Edition.
Security
Release 7.0(0) introduces a number of security features and improvements to protect the ICM/IPCC
platform and data against mainstream attacks and other risks to a voice application such as ICM and
IPCC. These features include:
platform and data against mainstream attacks and other risks to a voice application such as ICM and
IPCC. These features include:
•
Automated Windows Server 2003 hardening provided by the Cisco ICM Security Template bundled
with the ICM/IPCC and System IPCC software installers.
with the ICM/IPCC and System IPCC software installers.
•
Default configuration of Secure Sockets Layer (SSL) on WebView, Internet Script Editor, Agent
Re-skilling, System IPCC Web Administration, and Support Tools Server Administration.
Re-skilling, System IPCC Web Administration, and Support Tools Server Administration.
•
Support for Windows Authentication (versus Mixed Mode) on SQL Server 2000 and 'sa' password
protection.
protection.
•
Support for Cisco Security Agent (CSA) version 4.5, leveraging its extended features in the
standalone agent available for ICM and IPCC servers.
standalone agent available for ICM and IPCC servers.
•
Support for Windows Server 2003 SP1 and Windows XP SP2 Windows Firewall functionality. The
Windows Firewall is automatically configured by the CiscoICMfwConfig utility on Windows
Server 2003 SP1 and by the application installers on XP SP2.
Windows Firewall is automatically configured by the CiscoICMfwConfig utility on Windows
Server 2003 SP1 and by the application installers on XP SP2.
•
An expanded list of qualified Anti-Virus products now supported with the ICM and IPCC
applications. The supported applications are McAfee VirusScan 8.0i, Trend Micro ServerProtect
5.58, and Symantec AntiVirus 9.0.
applications. The supported applications are McAfee VirusScan 8.0i, Trend Micro ServerProtect
5.58, and Symantec AntiVirus 9.0.
•
Cisco ICM and IPCC applications also support the deployment of Host Based IPSec on Windows
Server 2003 to secure data in transit such as call variables, Extended Call Context variables,
configuration data and all communication along specified paths.
Server 2003 to secure data in transit such as call variables, Extended Call Context variables,
configuration data and all communication along specified paths.
•
Implementation of TLS in CAD and CTI OS (C++/COM Toolkit only) to secure communication
from the agent desktop to the CTI OS Server to protect agent authentication credentials and all CTI
data. The CTI OS TLS implementation supports mutual authentication and integration with a Public
Key Infrastructure (PKI).
from the agent desktop to the CTI OS Server to protect agent authentication credentials and all CTI
data. The CTI OS TLS implementation supports mutual authentication and integration with a Public
Key Infrastructure (PKI).
•
Revamped Security Best Practices Guide for Cisco ICM/IPCC Enterprise & Hosted Editions as well
as a complementary Security chapter in the IPCC Solution Reference Network Design (SRND)
document.
as a complementary Security chapter in the IPCC Solution Reference Network Design (SRND)
document.