Cisco Cisco Customer Response Solution Downloads デザインガイド

ページ / 93
 
3-9
Cisco Unified Contact Center Express Solution Reference Network Design, Release 4.1
Chapter 3      Cisco Unified Contact Center Express Deployment Models
Other Design Considerations
CRS Logs
The CRS Database (comprised of 4 data stores)
BARS (Backup and Recovery System) data
Recording Files.
Systems planners and designers should attempt to estimate the impact of each in order to determine 
hard disk requirements.   The Cisco Customer Response Solutions Installation Guide provides more 
information about disk size requirements for very large installations.
The Cisco Unified CallManager sizing tool assumes devices are evenly distributed across all servers 
within a Cisco Unified CallManager Cluster.  Because it is recommended that ALL CTI Ports and 
CTI Route Points be configured as part of a device pool that homes primarily to the same Cisco 
Unified CallManager Server as the primary CTI Manager being used, it may be required to run the 
Cisco Unified CallManager sizing tool on a per location or per server basis.
The Cisco Unified CallManager QSIG path replacement feature is not supported for Unified CCX 
calls. For additional information about Unsupported Features in Cisco Unified CallManager, see the 
4.1x release notes for Cisco Customer Response Solutions available on line at
Cisco Unified CallManager Forced Authorization Codes and Client Matter Codes are not allowed 
to be used on the same Cisco Unified CallManager cluster where Unified CCX is installed.  This is 
for any Cisco Unified CallManager phones and users— not just Unified CCX agents.  The resolution 
to this is to deploy two separate Cisco Unified CallManager clusters. For details on why this is not 
supported, see the Cisco CRS Release Notes available on line at:
The Unified CCX Gateway PG can be added to any of these models except for Model 1, the 
CallManager co-resident model.  The PG process must run on the server(s) with the CRS Engine 
component(s).
Sometimes new releases of Cisco Unified CallManager will not support Unified CCX immediately 
at Cisco Unified CallManager first customer ship (FCS) time.  Some organizations may be early 
adopters of new Cisco Unified CallManager releases and may be slowed from migrating to new 
Cisco Unified CallManager releases and using new Cisco Unified CallManager features if Unified 
CCX is installed with that same Cisco Unified CallManager cluster.  Therefore, in some scenarios, 
it may make sense to have a separate Cisco Unified CallManager cluster for Unified CCX.
Configurations with a remote IVR with Cisco Unified CallManager are generally not supported 
except on a case-by-case basis using the bid assurance process.