Cisco Cisco IPCC Web Option Release Note
Cisco Unified ICM/Unified CC Enterprise & Hosted Editions, Release 7.2(x)
Rev. 1.30
Hardware and System Software Specification
4BSoftware Upgrade Considerations
©2010 Cisco Systems, Inc.
46
Dialogic Card Requirements
Dialogic telephony cards are an integral part of Outbound Option. These cards reserve agents and place customer calls
as well as detect voice, signal tones, and answering machines. Dialogic offers many different types of cards with
varying numbers of ports, bus types, and connection methods. .Refer to the Dialogic documentation for information
about compatibility between Dialogic hardware/software and Microsoft Windows operating systems.
as well as detect voice, signal tones, and answering machines. Dialogic offers many different types of cards with
varying numbers of ports, bus types, and connection methods. .Refer to the Dialogic documentation for information
about compatibility between Dialogic hardware/software and Microsoft Windows operating systems.
Operating System Requirement
The Outbound Option server is supported on the Microsoft Windows Server 2003 operating system. See page 10 for
the
the
ACD Requirements
Outbound Option currently supports integration to the following ACDs, which must be configured on Unified ICM
software:
software:
• Avaya DEFINITY (refer to the Cisco Unified ICM Software ACD Supplement for DEFINITY)
5.8.12 CTI OS Server
For new installations beginning with release 7.0(0), Cisco specifies that the CTI OS server co-reside within the PG
according to the Agent PG Configuration. When upgrading CTI OS from release 6.0 or earlier, where CTI OS was
installed on standalone server(s), the upgrade may be applied to the standalone server. It is strongly encouraged
however, that the CTI OS server be migrated to co-reside on the PG as soon as possible to reduce bandwidth
requirements on the network. Standalone CTI OS server(s) are supported during the upgrade and migration period.
according to the Agent PG Configuration. When upgrading CTI OS from release 6.0 or earlier, where CTI OS was
installed on standalone server(s), the upgrade may be applied to the standalone server. It is strongly encouraged
however, that the CTI OS server be migrated to co-reside on the PG as soon as possible to reduce bandwidth
requirements on the network. Standalone CTI OS server(s) are supported during the upgrade and migration period.
Also, beginning with release 7.0(1), the number of configured CTI OS peer servers is limited to one (1). Refer to
Unified ICM/Unified CC Hardware and Software Requirements for sizing guidelines.
Unified ICM/Unified CC Hardware and Software Requirements for sizing guidelines.
Standalone CTI OS servers are not supported for Unified CC Hosted deployments.
See
5.8.13 Silent Monitor Service for CTI OS
The silent monitor service is a single executable that can be deployed in two different ways:
1.
Standalone server which is called Silent Monitor Server
2.
Co-resident with any CTI OS Client Toolkit application which is called Silent Monitor Service for Unified
CC Toolkit