Cisco Cisco Customer Response Solution Downloads Designanleitung
3-5
Cisco Unified Contact Center Express Solution Reference Network Design, Release 4.1
Chapter 3 Cisco Unified Contact Center Express Deployment Models
Single-Server Non-HA Deployment Model (2)
Co-resident installations do not support the following:
•
Expansion servers
•
Unified ICME integration using Unified Contact Center Gateway PG
•
High Availability
•
Failover to a secondary CTI Manager
If the Cisco Unified CallManager server is part of a multi-node Cisco Unified CallManager cluster, the
CTI Manager which Unified CCX communicates with must be running on the same Cisco Unified
CallManager node where Unified CCX is installed. All CTI Ports and Route Points must register with
this Cisco Unified CallManager node as primary and no secondary is supported.
CTI Manager which Unified CCX communicates with must be running on the same Cisco Unified
CallManager node where Unified CCX is installed. All CTI Ports and Route Points must register with
this Cisco Unified CallManager node as primary and no secondary is supported.
Install the maximum allowed memory on the Cisco Unified CallManager server. The Cisco Unified
CallManager server platforms have particular memory requirements, which are documented in Product
Bulletin 2864, Physical Memory Recommendations for Cisco Unified CallManager, Version 4.0 and
Later, available at:
CallManager server platforms have particular memory requirements, which are documented in Product
Bulletin 2864, Physical Memory Recommendations for Cisco Unified CallManager, Version 4.0 and
Later, available at:
Single-Server Non-HA Deployment Model (2)
This deployment model is for small deployments that do not meet the requirements of the Cisco Unified
CallManager Co-Resident deployment model and will only require one single processor server or two
dual processor servers simultaneous reporting sessions. The 7845 will allow two reporting client
sessions during operating hours. All others servers only support one reporting client during operating
hours. This deployment model places a single instance of all 4 software components on the same server.
This deployment model may use either MSDE (default) or SQL Server as the database. The MSDE
database limits the number of simultaneously connected historical reporting clients to five and the max
database size is 2 GB.
CallManager Co-Resident deployment model and will only require one single processor server or two
dual processor servers simultaneous reporting sessions. The 7845 will allow two reporting client
sessions during operating hours. All others servers only support one reporting client during operating
hours. This deployment model places a single instance of all 4 software components on the same server.
This deployment model may use either MSDE (default) or SQL Server as the database. The MSDE
database limits the number of simultaneously connected historical reporting clients to five and the max
database size is 2 GB.
This deployment model can support silent monitoring and recording for agents at any WAN connected
site using desktop monitoring (CAD with a 7940 or higher phone). This deployment model can also
support SPAN port monitoring for agents on the same VLAN segment as the Unified CCX server.
site using desktop monitoring (CAD with a 7940 or higher phone). This deployment model can also
support SPAN port monitoring for agents on the same VLAN segment as the Unified CCX server.
This deployment model will allow the CRS Engine to fail over to a backup CTI Manager in the event
that the primary CTI Manager fails. CTI Ports and CTI Route Points should be grouped into device pools
that have the same primary and secondary server list as that used for JTAPI communications with the
CTI Managers.
that the primary CTI Manager fails. CTI Ports and CTI Route Points should be grouped into device pools
that have the same primary and secondary server list as that used for JTAPI communications with the
CTI Managers.
Up to four additional Monitoring Servers for SPAN port monitoring of agents at remote sites can be
added to this model if needed.
added to this model if needed.
Multi-Server Non-HA Deployment Model (3)
This deployment model is for scenarios requiring more than two simultaneous historical reporting clients
during operating hours or more IVR applications, agents, supervisors, monitoring, and recording than
could be supported on a single-server deployment or for any deployment requiring ASR or TTS. When
any software component is split off onto a separate server from the server with the CRS Engine, we call
that server an expansion server.
during operating hours or more IVR applications, agents, supervisors, monitoring, and recording than
could be supported on a single-server deployment or for any deployment requiring ASR or TTS. When
any software component is split off onto a separate server from the server with the CRS Engine, we call
that server an expansion server.
This deployment model may use either MSDE (default) or SQL Server as the database. The MSDE
database limits the number of simultaneously connected historical reporting clients to five and the
maximum database size is 2 GB.
database limits the number of simultaneously connected historical reporting clients to five and the
maximum database size is 2 GB.