Cisco Cisco Unified Contact Center Enterprise 8.5(2) Leaflet
2-12
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 2 Deployment Models
IPT: Single Site
This system can be installed using the traditional Unified CCE model (not Unified System CCE), which
would allow for several different options. For example, two Unified CCE System PGs could be installed
along with a single Unified CVP.
would allow for several different options. For example, two Unified CCE System PGs could be installed
along with a single Unified CVP.
Unified System CCE or traditional Unified CCE must be deployed in a redundant fashion. Simplex
deployments are supported only for lab or non-production deployments. For information on Unified
CCE redundancy, see to the chapter on
deployments are supported only for lab or non-production deployments. For information on Unified
CCE redundancy, see to the chapter on
.
The number of Unified CM nodes and the hardware model used is not specified along with the number
of Unified IP IVRs. For information on determining the number and type of servers required, refer to the
chapter on
of Unified IP IVRs. For information on determining the number and type of servers required, refer to the
chapter on
Also not specified in this model is the specific data switching infrastructure required for the LAN, the
type of voice gateways, or the number of voice gateways and trunks. Cisco campus design guides and
Cisco Unified Communications design guides are available to assist in the design of these components.
The chapter on
type of voice gateways, or the number of voice gateways and trunks. Cisco campus design guides and
Cisco Unified Communications design guides are available to assist in the design of these components.
The chapter on
, discusses how to determine the number of
gateway ports.
Another variation in this model is to have the voice gateways connected to the line side of a PBX instead
of the PSTN. Connection to multiple PSTNs and a PBX all from the same single-site deployment is also
possible. For example, a deployment can have trunks from a local PSTN, a toll-free PSTN, and a
traditional PBX/ACD. For more information, see
of the PSTN. Connection to multiple PSTNs and a PBX all from the same single-site deployment is also
possible. For example, a deployment can have trunks from a local PSTN, a toll-free PSTN, and a
traditional PBX/ACD. For more information, see
, and
.
This deployment model also does not specify the type of signaling (ISDN, MF, R1, and so on) to be used
between the PSTN and voice gateway or the specific signaling (H.323 or MGCP) to be used between the
voice gateway and Unified CM.
between the PSTN and voice gateway or the specific signaling (H.323 or MGCP) to be used between the
voice gateway and Unified CM.
The amount of digital signal processor (DSP) resources required for placing calls on hold, consultative
transfers, and conferencing is also not specified in this model. For information on sizing of these
resources, refer to the latest version of the Cisco Unified Communications Solution Reference Network
Design (SRND) guide, available at
transfers, and conferencing is also not specified in this model. For information on sizing of these
resources, refer to the latest version of the Cisco Unified Communications Solution Reference Network
Design (SRND) guide, available at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides
_list.html
_list.html
The main advantage of the single-site deployment model is that there is no WAN connectivity required.
Given that there is no WAN in this deployment model, there is generally no need to use G.729 or any
other compressed Real-Time Transport Protocol (RTP) stream, so transcoding would not be required.
Given that there is no WAN in this deployment model, there is generally no need to use G.729 or any
other compressed Real-Time Transport Protocol (RTP) stream, so transcoding would not be required.
Unified CCE: Unified CCE System PG
In this deployment model, the agent PG that is deployed is a Unified CCE System PG. Only a single
peripheral is needed to handle both the Unified CM and any Unified IP IVRs that may exist. This
peripheral unifies the appearances of the multiple PIMs and also handles load balancing calls between
multiple Unified IP IVRs. Alternatively, this model may be configured to use Unified CVP. When
Unified CVP is used, its connectivity to Cisco Unified Presence handles load balancing by distributing
the incoming calls among Unified CVP Call Servers. In this deployment, the VRU PIMs (up to 10)
communicating with the Unified CVP Call Server(s) reside on their own PG and not under the
Unified CCE System PG.
peripheral is needed to handle both the Unified CM and any Unified IP IVRs that may exist. This
peripheral unifies the appearances of the multiple PIMs and also handles load balancing calls between
multiple Unified IP IVRs. Alternatively, this model may be configured to use Unified CVP. When
Unified CVP is used, its connectivity to Cisco Unified Presence handles load balancing by distributing
the incoming calls among Unified CVP Call Servers. In this deployment, the VRU PIMs (up to 10)
communicating with the Unified CVP Call Server(s) reside on their own PG and not under the
Unified CCE System PG.
shows a single-site deployment utilizing Unified CVP instead of
IP-IVR in a Unified System CCE system. In this model, no longer do all calls reside under a single
peripheral; Unified CVP is its own peripheral(s).
peripheral; Unified CVP is its own peripheral(s).