Cisco Cisco E-Mail Manager Unity Integration Option Leaflet
1-19
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
the device (phone) has started ringing, and that notification enables the agent’s answer button on the
desktop application. When the agent clicks the answer button, the ICM instructs Unified CM to make
the device (phone) go off-hook and answer the call.
desktop application. When the agent clicks the answer button, the ICM instructs Unified CM to make
the device (phone) go off-hook and answer the call.
In order for the routing control communication to occur, Unified CM requires the configuration of a CTI
Route Point. A CTI Route Point is associated with a specific JTAPI user ID, and this association enables
Unified CM to know which application provides routing control for that CTI Route Point. Directory
(Dialed) Numbers (DNs) are then associated with the CTI Route Point. A DN is associated to a CTI
Route Point that is associated with the ICM JTAPI user ID, and this enables Unified CM to generate a
route request to the ICM when a new call to that DN arrives.
Route Point. A CTI Route Point is associated with a specific JTAPI user ID, and this association enables
Unified CM to know which application provides routing control for that CTI Route Point. Directory
(Dialed) Numbers (DNs) are then associated with the CTI Route Point. A DN is associated to a CTI
Route Point that is associated with the ICM JTAPI user ID, and this enables Unified CM to generate a
route request to the ICM when a new call to that DN arrives.
In order for the phones to be monitored and controlled, they also must be associated in Unified CM with
a JTAPI user ID. In a Unified CCE environment, the IP phones are associated with the ICM JTAPI user
ID. When an agent logs in from the desktop, the Unified CM PIM requests Unified CM to allow the PIM
to begin monitoring and controlling that phone. Until the login has occurred, Unified CM does not allow
the ICM to monitor or control that phone. If the device has not been associated with the ICM JTAPI user
ID, then the agent login request will fail.
a JTAPI user ID. In a Unified CCE environment, the IP phones are associated with the ICM JTAPI user
ID. When an agent logs in from the desktop, the Unified CM PIM requests Unified CM to allow the PIM
to begin monitoring and controlling that phone. Until the login has occurred, Unified CM does not allow
the ICM to monitor or control that phone. If the device has not been associated with the ICM JTAPI user
ID, then the agent login request will fail.
Because the Unified IP IVR also communicates with Unified CM using the same JTAPI protocol, these
same three types of communication also occur with the Unified IP IVR. Unlike the ICM, the
Unified IP IVR provides both the application itself and the devices to be monitored and controlled.
same three types of communication also occur with the Unified IP IVR. Unlike the ICM, the
Unified IP IVR provides both the application itself and the devices to be monitored and controlled.
The devices that the ICM monitors and controls are the physical phones. The Unified IP IVR does not
have real physical ports like a traditional IVR. Its ports are logical ports (independent software tasks or
threads running on the Unified IP IVR application server) called CTI Ports. For each CTI Port on the
Unified IP IVR, there needs to be a CTI Port device defined in Unified CM.
have real physical ports like a traditional IVR. Its ports are logical ports (independent software tasks or
threads running on the Unified IP IVR application server) called CTI Ports. For each CTI Port on the
Unified IP IVR, there needs to be a CTI Port device defined in Unified CM.
Unlike a traditional PBX or telephony switch, Unified CM does not select the Unified IP IVR port to
which it will send the call. Instead, when a call needs to be made to a DN that is associated with a CTI
Route Point that is associated with a Unified IP IVR JTAPI user, Unified CM asks the Unified IP IVR
(via JTAPI routing control) which CTI Port (device) should handle the call. Assuming the
Unified IP IVR has an available CTI Port, the Unified IP IVR will respond to the Unified CM routing
control request with the Unified CM device identifier of the CTI Port that is going to handle that call.
which it will send the call. Instead, when a call needs to be made to a DN that is associated with a CTI
Route Point that is associated with a Unified IP IVR JTAPI user, Unified CM asks the Unified IP IVR
(via JTAPI routing control) which CTI Port (device) should handle the call. Assuming the
Unified IP IVR has an available CTI Port, the Unified IP IVR will respond to the Unified CM routing
control request with the Unified CM device identifier of the CTI Port that is going to handle that call.
When an available CTI Port is allocated to the call, a Unified IP IVR workflow is started within the
Unified IP IVR. When the Unified IP IVR workflow executes the accept step, a JTAPI message is sent
to Unified CM to answer the call on behalf of that CTI Port (device). When the Unified IP IVR workflow
wants the call transferred or released, it again instructs Unified CM on what to do with that call. These
scenarios are examples of device and call control performed by the Unified IP IVR.
Unified IP IVR. When the Unified IP IVR workflow executes the accept step, a JTAPI message is sent
to Unified CM to answer the call on behalf of that CTI Port (device). When the Unified IP IVR workflow
wants the call transferred or released, it again instructs Unified CM on what to do with that call. These
scenarios are examples of device and call control performed by the Unified IP IVR.
When a caller releases the call while interacting with the Unified IP IVR, the voice gateway detects the
caller release and notifies Unified CM via H.323 or Media Gateway Control Protocol (MGCP), which
then notifies the Unified IP IVR via JTAPI. When DTMF tones are detected by the voice gateway, it
notifies Unified CM via H.245 or MGCP, which then notifies the Unified IP IVR via JTAPI. These
scenarios are examples of device and call monitoring performed by the Unified IP IVR.
caller release and notifies Unified CM via H.323 or Media Gateway Control Protocol (MGCP), which
then notifies the Unified IP IVR via JTAPI. When DTMF tones are detected by the voice gateway, it
notifies Unified CM via H.245 or MGCP, which then notifies the Unified IP IVR via JTAPI. These
scenarios are examples of device and call monitoring performed by the Unified IP IVR.
In order for the CTI Port device control and monitoring to occur, the CTI Port devices on Unified CM
must be associated with the appropriate Unified IP IVR JTAPI user ID. If you have two 150-port
Unified IP IVRs, you would have 300 CTI ports. Half of the CTI ports (150) would be associated with
JTAPI user Unified IP IVR #1, and the other 150 CTI ports would be associated with JTAPI user
Unified IP IVR #2.
must be associated with the appropriate Unified IP IVR JTAPI user ID. If you have two 150-port
Unified IP IVRs, you would have 300 CTI ports. Half of the CTI ports (150) would be associated with
JTAPI user Unified IP IVR #1, and the other 150 CTI ports would be associated with JTAPI user
Unified IP IVR #2.
While Unified CM can be configured to route calls to Unified IP IVRs on its own, routing of calls to the
Unified IP IVRs in a Unified CCE environment should be done by the ICM (even if you have only one
Unified IP IVR and all calls require an initial IVR treatment). Doing so will ensure proper Unified CCE
reporting. For deployments with multiple Unified IP IVRs, this routing practice also allows the ICM to
load-balance calls across the multiple Unified IP IVRs.
Unified IP IVRs in a Unified CCE environment should be done by the ICM (even if you have only one
Unified IP IVR and all calls require an initial IVR treatment). Doing so will ensure proper Unified CCE
reporting. For deployments with multiple Unified IP IVRs, this routing practice also allows the ICM to
load-balance calls across the multiple Unified IP IVRs.