Cisco Cisco Unified Contact Center Enterprise 9.0(2) Release Note

Page of 75
 
Cisco Unified ICM/Unified CC Enterprise & Hosted Editions, Releases 7.0(0) SR1 – SR4 and 7.1(x)  Rev. 1.14 
 
 
Hardware and System Software Specification 
 
6BICM/IPCC Hardware and Software Requirements 
©2008 Cisco Systems, Inc. 
 
44
 
7.6.16 CTI Driver for Siebel 
For supported Siebel versions, see the CTI Compatibility matrix: 
The CTI Driver for Siebel is Installed on the Siebel Communications Manager Server and must operate stand alone from all other 
ICM/IPCC systems. Agent capacity and performance for Siebel Call Centers can vary dramatically based on the deployment 
topology and configuration of the Siebel components and the complexity of the Siebel applications and scripts in use. For more 
details on performance tuning Siebel deployments, consult Siebel Technical Support or a Siebel Certified Configuration Engineer.  
Table 7.54: CTI Driver for Siebel Servers 
Capacity 
*
 
(agents) 
Server 
Call 
Rate  
(calls 
per sec.) 
Hardware 
Other requirements and remarks 
7.0(1) & 7.1(x) 
500 
Siebel Communications 
Manager / Call Center 
Object Manager (SCM + 
OM) 
 
MCS-40-003-Class  The Siebel deployment model tested had the 
SCM and OM collocated on the same server 
host . 
Siebel Communications 
Manager Server (SCM) 
7.1(2), 7.1(3), 
7.1(4), 7.1(5) 
700 
Siebel Call Center Object 
Manager (OM) 
 
3.75 
MCS-40-003-Class  The Siebel deployment model tested had each 
server component (SCM and OM) installed 
stand-alone on its own server host. 
* The capacity was determined on an Siebel environment that met the following configuration conditions:  
1) Siebel component groups enabled during the capacity determination:  
•  System Management  
•  Siebel Call Canter  
•  Workflow management   
•  Communication Management  
The following components in the group were disabled  
Communications Configuration Manager  
Communications Inbound Processor  
Communications Inbound Receiver  
Communications Outbound Manager  
Smart Answer Manager  
2) No Siebel Scripting involved. 
3) No activity records being created.  
4) No Siebel Workflows activated.