Information About Interoperability with Cisco Unified CCX
Unified CME 4.2 to Unified CME 8.5 Release versions support interoperability between Cisco Unified CME and Cisco Customer Response Solutions (CRS) with Cisco Unified Call Center Express (Cisco Unified CCX), including enhanced call processing, device and call monitoring, unattended call transfers to multiple call center agents and basic extension mobility, and IP IVR applications.
Note |
For Unified CME 8.6 and later releases, CRS with Unified CCX is not supported. |
The Cisco Unified CCX application uses the CRS platform to provide a multimedia (voice, data, and web). Cisco IP IVR functionality is available with Cisco Unified CCX and includes prompt-and-collect and call treatment.
-
Support of Cisco Unified CCX Cisco Agent Desktop for use with Cisco Unified CME
-
Configuration query and update between Cisco Unified CCX and Cisco Unified CME
-
SIP-based simple and supplementary call control services including:
-
Call routing between Cisco Unified CME and Cisco Unified CCX using SIP-based route point
-
First-party call control for SIP-based simple and supplementary calls
-
Call monitoring and device monitoring based on SIP presence and dialog event package
-
-
Cisco Unified CCX session management of Cisco Unified CME
-
Cisco Unified CCX device and call monitoring of agent lines and call activities in Cisco Unified CME
Provisioning and configuration information in Cisco Unified CCX is automatically provided to Cisco United CME. If the configuration from Cisco Unified CCX is deleted or must be modified, you can configure the same information in Cisco Unified CME by using Cisco IOS commands.
For first party call control, a route point for Cisco CRS is a peer device to Cisco Unified CME through a SIP trunk. An incoming call to Cisco Unified CME that is targeted to a call center phone is routed to Cisco Unified CCX through the route point. The call is placed in a queue and redirected to the most suitable agent by Cisco Unified CCX.
Supplementary services such as call hold, blind transfer, and semi-attended transfer are initiated by Cisco Unified CCX. Existing SIP-based simple and supplementary service call flow applies except for blind transfers. For blind transfers with Cisco Unified CCX as the transferrer, Cisco Unified CCX will stay in the active state until the transfer target answers. It drops out only after the transferred call is successfully answered. If the transfer target does not answer when ringing times out, the call is pulled back by Cisco Unified CCX and rerouted to another agent. This mechanism also applies when the transfer target is configured with call-forward all or forward no-answer. The forward configuration is ignored during blind transfer.
When a call moves between Cisco Unified CCX and Cisco Unified CME because of redirect, transfer, and conference, the SIP Call-ID continues to change. For call control purposes, Cisco Unified CME issues a unique Global Call ID (Gcid) for every outbound call leg. A Gcid remains the same for all legs of the same call in the system, and is valid for redirect, transfer, and conference events, including 3-party conferencing when a call center phone acts as a conference host.
Before Cisco IOS Release 12.4(11)XW6, if the call monitoring module in Cisco Unified CME 4.2 detected a call associated with a non default session application, such as B-ACD or a TCL script, the module was globally disabled. After the module was disabled, Cisco Unified CCX administration had to manually re-enable the call monitoring module after the session completes.
In Cisco IOS Release 12.4(11)XW6 and later releases, the call monitoring module in Cisco Unified CME does not monitor a call associated with a non default session application, such as B-ACD or a TCL script, including all calls merged into this call by way of consult transfer and conference. The module is not disabled and continues to monitor other calls.
Table 1 contains a list of tasks required to enable operability between Cisco Unified CME and Cisco Unified CCX, presented in the order in which the tasks are to be completed. This section contains information about performing tasks in the first 2 steps in this table and procedures for completing step 3.
For configuration information, see Configure Interoperability with Cisco Unified CCX.
Step |
Task |
Name of Document |
||
---|---|---|---|---|
1 |
Verify that the appropriate Cisco Unified Communications Manager Express (Cisco Unified CME) version is installed on the router. For compatibility information, see Cisco Unified Contact Center Express (Cisco Unified CCX) Software and Hardware Compatibility Guide. |
— |
||
2 |
Configure the Cisco Unified CME router.
|
See "Prerequisites' section in Enable Interoperability with Cisco Unified CCX. |
||
3 |
Configure Cisco Unified CME to enable interoperability with Cisco Unified CCX. |
|||
4 |
Install Cisco Unified Contact Center Express (Cisco Unified CCX) for Cisco Unified CME. |
See Cisco Unified Contact Center Express Administration Guide at Configuration Guides. |
||
5 |
Perform the initial setup of Cisco CRS for Cisco Unified CME.
|
|||
6 |
Configure Cisco Unified CME telephony subsystem to enable interoperability with Cisco Unified CCX. |
“Provisioning Unified CCX for Unified CME” chapter in the appropriate Cisco CRS Administration Guide or Cisco Unified Contact Center Express Administration Guide at Configuration Guides. |
||
7 |
Create users and assign the agent capability in Cisco CRS. |