Cisco Cisco Customer Response Solution Downloads Designanleitung
3-4
Cisco Unified Contact Center Express Solution Reference Network Design, Release 4.1
Chapter 3 Cisco Unified Contact Center Express Deployment Models
Cisco Unified CallManager Co-Resident Deployment Model (1)
Note
If the network connectivity is lost between the two CRS engines, both CRS engines become
active (island mode). When the network connectivity is restored, both CRS servers become
inactive for a few seconds in order to negotiate the CRS engine mastership, and all the calls in
queues and receiving call treatment would be lost.
active (island mode). When the network connectivity is restored, both CRS servers become
inactive for a few seconds in order to negotiate the CRS engine mastership, and all the calls in
queues and receiving call treatment would be lost.
•
The Unified CM servers running CTI Managers with which Unified CCX will communicate must
be located in the same campus LAN as the CRS Engine servers. The available bandwidth for these
LAN links should always be considerably higher than the load, and there should be no steady-state
congestion, and the maximum round-trip delay between the servers should be less than 2 ms. Other
Unified CM nodes within the same Unified CM cluster can be located across the WAN in a Unified
CM cluster split over the WAN. In such deployments, the WAN requirements that are described in
Cisco Unified Communications SRND must be satisfied.
be located in the same campus LAN as the CRS Engine servers. The available bandwidth for these
LAN links should always be considerably higher than the load, and there should be no steady-state
congestion, and the maximum round-trip delay between the servers should be less than 2 ms. Other
Unified CM nodes within the same Unified CM cluster can be located across the WAN in a Unified
CM cluster split over the WAN. In such deployments, the WAN requirements that are described in
Cisco Unified Communications SRND must be satisfied.
•
When deploying HA, the CRS Engine and Database components must both be redundant.
•
If recording is going to be used for a HA deployment, then the Recording component must be
redundant.
redundant.
•
All agents for a Unified CCX deployment must be using phones which register to the same Cisco
Unified CallManager cluster. Calls can be received from devices and callers on another Cisco
Unified CallManager cluster (using inter-cluster trunks).
Unified CallManager cluster. Calls can be received from devices and callers on another Cisco
Unified CallManager cluster (using inter-cluster trunks).
All Unified CCX deployments must be configured using the Unified CCX 4.1 Configuration & Ordering
Tool in order to be supported.
Tool in order to be supported.
With regard to a couple of key server characteristics, only the 7835 and 7845 models provide redundant
power supplies, redundant fans, and redundant hot-swappable disk drives. For any HA deployment, use
either the 7835 or the 7845 server model.
power supplies, redundant fans, and redundant hot-swappable disk drives. For any HA deployment, use
either the 7835 or the 7845 server model.
Cisco Unified CallManager Co-Resident Deployment Model
(1)
(1)
Unified CCX software can be installed co-resident with Cisco Unified CallManager software. For
co-resident installations, there is a limit of 10 simultaneous agents logged in, 1 supervisor logged in, 1
silent monitoring or recording session, 1 after hours historical reporting client session, and either 10
basic IVR ports or 5 advanced IVR ports. The Unified CCX call volume must not exceed 300 BHCC.
co-resident installations, there is a limit of 10 simultaneous agents logged in, 1 supervisor logged in, 1
silent monitoring or recording session, 1 after hours historical reporting client session, and either 10
basic IVR ports or 5 advanced IVR ports. The Unified CCX call volume must not exceed 300 BHCC.
In addition to the 10 IP Phones for agents, the number of non-agent IP Phones supported on the Cisco
Unified CallManager server varies by server model. The supported BHCC call volume of non call center
traffic on the Cisco Unified CallManager server also varies by server model. The following table lists
the supported limits for non call center phone and call volume per server model.
Unified CallManager server varies by server model. The supported BHCC call volume of non call center
traffic on the Cisco Unified CallManager server also varies by server model. The following table lists
the supported limits for non call center phone and call volume per server model.
Server Model
Max Unified CM IP Phones
Max Unified CM BHCC Call
Volume
Volume
7815
150
900
7825
500
3,000
7835
1,000
6,000
7845
3,000
18,000