C H A P T E R
1
Architecture Overview
Last revised on: August 18, 2009
Cisco Unified Contact Center Enterprise (Unified CCE) is part of Cisco Unified Communications application suite, which delivers intelligent call routing, network-to-desktop Computer Telephony Integration (CTI), and multi-channel contact management to contact center agents over an IP network. It combines software IP automatic call distribution (ACD) functionality with Cisco Unified
Communications in a unified solution that enables companies to rapidly deploy an advanced, distributed contact center infrastructure.
The Cisco Unified CCE is an integrated suite of products that includes Cisco Unified Intelligent Contact Management (Unified ICM), Cisco Unified Communications Manager (Unified CM, Cisco IP
Interactive Voice Response (Unified IP IVR), Cisco Unified Customer Voice Portal (Unified CVP), Cisco Voice over IP (VoIP) Gateways and Cisco Unified IP phones. Together these products provide Cisco Unified Communications and contact center solutions to achieve intelligent call routing,
multi-channel automatic call distribution (ACD) functionality, interactive voice response (IVR), network call queuing, and consolidated enterprise-wide reporting. Unified CCE can optionally integrate with Cisco Unified ICM to support networking with legacy ACD systems while providing a smooth migration path to a converged communications platform.
The Cisco Unified CCE solution is designed for implementation in both single-site and multi-site contact centers. It utilizes your existing Cisco IP network to lower administrative expenses and extend the boundaries of the contact center enterprise to include branch offices, home agents, and knowledge workers. Figure 1-1 illustrates a typical Unified CCE setup.
Figure 1-1 Typical Unified CCE Deployment
The Cisco Unified CCE solution consists of four primary Cisco software components:
• Unified Communications infrastructure: Cisco Unified Communications Manager (Unified CM)
• Queuing and self-service: Cisco Unified IP Interactive Voice Response (Unified IP IVR) or Unified CVP
• Contact center routing and agent management: Unified CCE is based on the Unified ICM software. It includes Call Router, Logger, Peripheral Gateway, Historical Data Server, Administrative Workstation, and so forth.
• Agent desktop software: Cisco Agent Desktop (CAD), Cisco Toolkit Agent Desktop (CTI OS), or integrations with third-party customer relationship management (CRM) software through Cisco Unified CRM Connector.
In addition to these core components, the following Cisco telephony and infrastructure hardware products may be required for a complete Unified CCE deployment:
• Cisco Unified IP phones
• Cisco voice gateways
• Cisco LAN/WAN infrastructure
The following sections discuss each of the software components in more detail and describe the data communications between each of these components. For more information on a particular product, refer to the specific product documentation available online at
http://www.cisco.com Signaling/CTI IP Voice TDM Voice 143298 V Unified CM Cluster PSTN M M M M M IP IVR/CVP Agent IP Unified CCE
Chapter 1 Architecture Overview
What's New in This Chapter
What's New in This Chapter
Table 1-1 lists the topics that are new in this chapter or that have changed significantly from previous releases of this document.
Cisco Unified Communications Manager
Cisco Unified Communications Manager (Unified CM, formerly Cisco Unified CallManager) is a software application that controls the voice gateways and IP phones, thereby providing the foundation for a Voice over IP (VoIP) solution. Unified CM runs on Cisco Media Convergence Servers (MCS). The software running on a server is referred to as a Unified CM server. Multiple Unified CM servers can be grouped into a cluster to provide for scalability and fault tolerance. Unified CM communicates with the gateways using standard protocols such as H.323, Media Gateway Control Protocol (MGCP), and Session Initiation Protocol (SIP). Unified CM communicates with the IP phones using SIP or Skinny Call Control Protocol (SCCP). For details on Unified CM call processing capabilities and clustering options, 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
A single Unified CM subscriber server is capable of supporting hundreds of agents. In a fault-tolerant design, a Unified CM cluster is capable of supporting thousands of agents. However, the number of agents and the number of busy hour call attempts (BHCA) supported within a cluster varies and must be sized according to guidelines defined in the chapter on Sizing Cisco Unified Communications Manager Servers, page 11-1.
Typically, when designing a Unified CCE solution, you first define the deployment scenario, including arrival point(s) for voice traffic and the location(s) of the contact center agents. After defining the deployment scenario, you can determine the sizing of the individual components within the Unified CCE design for such things as how many Unified CM servers are needed within a Unified CM cluster, how many voice gateways are needed for each site and for the entire enterprise, how many servers and what types of servers are required for the Unified ICM software, how many Unified IP IVR or Unified CVP servers are needed, and so forth.
Table 1-1 New or Changed Information Since the Previous Release of This Document
New or Revised Topic Described in:
Agent interfaces Unified CCE Agent Options, page 1-10
Agent phones Agent Phones, page 1-4
Logical Partitioning and toll bypass Agent Phones in Countries with Toll-Bypass Regulations, page 1-30
Removed reference to Unified IP Queue Manager Various sections
Unified Intelligence Suite Cisco Unified Intelligence Suite, page 1-16
Unified System Contact Center Enterprise Unified System CCE, page 1-21
Video queuing and agent support in Unified CVP Cisco Unified Customer Voice Portal (Unified CVP), page 1-4
Cisco Voice Gateways
When you select voice gateways for a Unified CCE deployment, it is important to select voice gateways that satisfy not only the number of required PSTN trunks but also the busy hour call completion rate on those trunks. Busy hour call completion rates per PSTN trunk are typically higher in a contact center than in a normal office environment. For Cisco Catalyst Communications Media Module (CMM) voice gateways being used in pure contact center deployments, Cisco recommends provisioning a maximum of four T1/E1 interfaces to ensure that the call processing capacity of the voice gateway is satisfactory.
Agent Phones
For a list of supported agent phones, refer to the Cisco Unified Contact Center Enterprise (Unified CCE)
Software Compatibility Guide, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_device_support_tables_list.h tml
The following design considerations apply to the Cisco Unified IP Phone 6900 Series:
• The IP Phone Agent feature is not currently supported.
• Join and Direct Transfer policy for the same line and across lines should be disabled in the Unified CM phone administration page for the agent phones.
• Outbound campaign capability requires Cisco Unified Contact Center Enterprise 7.5(6) or later release.
• Unified CM silent monitoring and recording and Remote Silent Monitoring (RSM) is not supported for Cisco Unified IP Phone 6900 Series agent phones at this time.
Cisco Unified Customer Voice Portal (Unified CVP)
Unified CVP is a software application running on industry standard servers such as Cisco Media Convergence Servers (MCS). It provides prompting, collecting, queuing, and call control services using standard web-based technologies. The Unified CVP architecture is distributed, fault tolerant, and highly scalable. With the Unified CVP system, voice is terminated on Cisco IOS gateways that interact with the Unified CVP application server using VoiceXML (speech) and H.323 or SIP (call control).
The Unified CVP software is tightly integrated with the Cisco Unified ICM software for application control. It interfaces with Unified ICM using the VRU Peripheral Gateway Interface. The Unified ICM scripting environment controls the execution of building-block functions such as play media, play data, menu, and collect information. The Unified ICM script can also invoke external VoiceXML applications to be executed by the Unified CVP VoiceXML Server, an Eclipse and J2EE- based scripting and web server environment. VoiceXML Server is well suited for sophisticated and high-volume IVR
applications, and it can interact with custom or third-party J2EE-based services. These applications can return results and control to the Unified ICM script when complete. Advanced load balancing across all Unified CVP solution components can be achieved by Cisco Content Services Switch (CSS) and Cisco IOS Gatekeepers or Cisco Unified Presence SIP Proxy Servers.
Unified CVP can support multiple grammars for prerecorded announcements in several languages. Unified CVP can optionally provide automatic speech recognition and text-to-speech capability. Unified CVP can also access customer databases and applications via the Cisco Unified ICM software.
Chapter 1 Architecture Overview
Cisco Unified IP Interactive Voice Response (Unified IP IVR)
Unified CVP also provides a queuing platform for the Unified CCE solution. Telephone and video calls can remain queued on Unified CVP until they are routed to a contact center agent (or external system). The system can play back music or videos while the caller is on hold; and when Unified CCE routes the call to an agent, he or she is able to push videos to a caller from the agent desktop application. For more information, refer to the latest version of the Cisco Unified Customer Voice Portal SRND, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps1006/products_implementation_design_gui des_list.html
Cisco Unified IP Interactive Voice Response (Unified IP IVR)
The Unified IP IVR provides prompting, collecting, and queuing capability for the Unified CCE solution. Unified IP IVR does not provide call control like Unified CVP because it is behind Unified CM and under the control of the Unified ICM software via the Service Control Interface (SCI). When an agent becomes available, the Unified ICM software instructs the Unified IP IVR to transfer the call to the selected agent phone. The Unified IP IVR then requests Unified CM to transfer the call to the selected agent phone.
Unified IP IVR is a software application that runs on Cisco MCS Servers. You can deploy multiple Unified IP IVR servers with a single Unified CM cluster under control of Unified CCE.
Unified IP IVR has no physical telephony trunks or interfaces like a traditional IVR. The telephony trunks are terminated at the voice gateway. Unified CM provides the call processing and switching to set up a G.711 or G.729 Real-Time Transport Protocol (RTP) stream from the voice gateway to the Unified IP IVR. The Unified IP IVR communicates with Unified CM via the Java Telephony Application Programming Interface (JTAPI), and the Unified IP IVR communicates with Unified ICM via the Service Control Interface (SCI) with a VRU Peripheral Gateway or System Peripheral Gateway. The chapter on Sizing Call Center Resources, page 9-1 discusses how to determine the number of IVR ports required. For deployments requiring complete fault tolerance, a minimum of two Unified IP IVRs is required. The chapter on Design Considerations for High Availability, page 3-1, provides details on Unified CCE fault tolerance.
Cisco Unified Intelligent Contact Management (Unified ICM)
Software
The Cisco Unified ICM software provides contact center features in conjunction with Unified CM and the IP Queuing platform. Features provided by the Unified ICM software include agent state
management, agent selection, call routing and queue control, IVR control, CTI Desktop screen pops, and contact center reporting. Unified ICM software for Unified Contact Center Enterprise (Unified CCE) runs on Cisco MCS servers or exact equivalents, unless otherwise specified in the chapter on Sizing Unified CCE Components and Servers, page 10-1, and the Hardware and System Software Specification
Guide. It relies on the Microsoft Windows 2003 operating system software and Microsoft SQL Server
2005 database management system. The supported servers can be single, dual, or quad Pentium CPU servers in single or multi-core variations with varying amounts of RAM. This variety of supported servers allows the ICM software to scale and to be sized to meet the needs of the deployment
requirements. The chapter on Sizing Unified CCE Components and Servers, page 10-1, provides details on server sizing.
Basic Unified CCE Call and Message Flow
Figure 1-2 shows the flow of a basic Unified CCE call using Unified IP IVR. In this scenario, all of the agents are assumed to be not ready when the call arrives, so the call is routed by the ICM to the Unified IP IVR. While the call is connected to the Unified IP IVR, call queuing treatment (for example, announcements or music) is provided. When an agent becomes available, the ICM directs the
Unified IP IVR to transfer the call to that agent's phone. At the same time the call is being transferred, the ICM sends the caller data, such as Automatic Number Identification (ANI), Directory Number (DN), and any CTI/call data variables, to the agent desktop software.
Figure 1-2 Basic Unified CCE Call Flow Using Unified IP IVR
The call flow in Figure 1-2 is as follows:
1. Call delivered from PSTN to voice gateway.
2. Voice gateway queries Unified CM for a destination.
3. JTAPI Route Request sent to ICM.
4. ICM runs routing script. No available agent found, so Unified IP IVR label returned from routing script.
5. ICM instructs Unified CM to transfer call to Unified IP IVR.
6. Unified IP IVR notifies ICM that call has arrived.
7. ICM instructs Unified IP IVR to play queue announcements.
8. Agent becomes ready (completed previous call or just went ready).
9. ICM sends call data to selected agent screen and instructs the Unified IP IVR to transfer the call to the agent phone.
10. Unified IP IVR transfers the VoIP voice path to selected agent phone.
ICM
IP phones and agent desktops 143300
Public network
IP voice TDM voice Call control and CTI data V IP 1 2 IP IVRs M M 3 4 7 7 9 7 5 10 10 Agent available Screen pop Call answered 8 9 5 5 10 6 8 9 11 IP IP Unified CM cluster
Chapter 1 Architecture Overview
Cisco Unified Intelligent Contact Management (Unified ICM) Software
11. Call is answered by agent.
Figure 1-3 shows the flow of a basic Unified CCE call using Unified CVP.
Figure 1-3 Basic Unified CCE Call Flow Using Unified CVP
The call flow in Figure 1-3 is as follows:
1. Call is delivered from PSTN to ingress voice gateway.
2. Voice gateway sends SIP or H. 225 request to Unified CVP for the incoming call.
3. Unified CVP sends route request to Unified ICM, requesting instructions.
4. Unified ICM runs routing scripts and instructs Unified CVP for prompting and announcements.
5. Agent becomes ready (completed previous call or just went ready).
6. Unified ICM instructs Unified CVP to send the call to the available agent on Unified CM.
7. Unified ICM sends call data to selected agent screen.
8. Unified CVP transfers the VoIP voice path to the selected agent phone on Unified CM.
9. Call is answered by the agent.
Unified ICM Software Modules
The Cisco Unified ICM software is a collection of modules that can run on multiple servers. The amount of software that can run on one server is primarily based upon busy hour call attempts (BHCA) and the size of the server being used (single, dual, or quad CPU). Other factors that impact the hardware sizing
ICM
IP phones and agent desktops 143301
IP voice TDM voice Call control and CTI data IP 1 CVP 4 6 2 5 7 8 3 1 8 9 IP IP Unified CM cluster Caller PSTN Ingress Gateway V M M
are the number of agents, the number of skills per agent, the number of Unified IP IVR ports, the number of VRU Script nodes in the ICM routing script, Extended Call Context (ECC) usage, and which statistics agents need at their desktops.
The core Unified ICM software modules are:
• Call Router
• Logger
• Agent Peripheral Gateway (PG)
• Unified CM Peripheral Interface Manager (PIM)
• IP IVR or CVP VRU PIM
• CTI Server
• CTI Object Server (CTI OS)
• Administrative Workstation (AW) or Real-Time Distributor
• Historical Data Server (HDS)
• WebView Reporting Server
The Call Router is the module that makes all routing decisions on how to route a call or customer contact. The Logger is the database server that stores contact center configuration and reporting data. The Unified CM PIM is the process that interfaces to a Unified CM cluster via the JTAPI protocol. The VRU PIM is the process that interfaces to the Unified IP IVR or Unified CVP via the Service Control Interface (SCI) protocol. The CTI Server is the process that interfaces to the CTI OS, the CTI Object Server to which Agent Desktops connect.
Each ICM software module can be deployed in a redundant fashion. When a module is deployed in a redundant fashion, we refer to the two sides as side A and side B. For example, Call Router A and Call Router B are redundant instances of the Call Router module (process) running on two different servers. This redundant configuration is also referred to as duplex mode, whereas a non-redundant configuration is said to be running in simplex mode. (Simplex mode is not supported for production environments.) When processes are running in duplex mode, they are not load-balanced. The A and B sides are both executing the same set of messages and, therefore, producing the same result. In this configuration, logically, there appears to be only one Call Router. The Call Routers run in synchronized execution across the two servers, which means both sides of the duplex servers process every call. In the event of a failure, the surviving Call Router will pick up the call mid-stream and continue processing in real-time and without user intervention.
Other components in the ICM, such as the Peripheral Gateways, run in hot-standby mode, meaning that only one of the Peripheral Gateways is actually active and controlling Unified CM or the IVR. When the active side fails, the surviving side automatically takes over processing of the application. During a failure, the surviving side is said to be running in simplex mode and will continue to function this way until the redundant/duplex side is restored to service, then it will automatically return to duplex operation.
Another important component of the architecture is the Historical Data Server (HDS). This is
instantiated by installing a Real-time Distributor with the HDS option to enable this server to maintain a historical reporting database that is synchronized from the Logger to enable the latter to maintain a limited set of records for optimum operation. The HDS follows an n+1 scalability architecture with each HDS, choosing a Logger side (A or B) as its preferred and primary data source. The HDS is a required component for historical reporting by WebView or the Unified Intelligence Suite. WebView can be co-resident with the HDS or deployed in standalone web server mode to achieve higher scalability in terms of reporting users that need access to the application for real-time and historical reporting. Refer to the chapter on Sizing Unified CCE Components and Servers, page 10-1, for more details.
Chapter 1 Architecture Overview
Cisco Unified Intelligent Contact Management (Unified ICM) Software
The Unified ICM software uses the concept of a customer instance to group all of the components under a single Call Router and Logger or Central Controller. The instance relationship ensures that all of the components related to the same system are joined under a single logical Unified CCE IP ACD. This concept is used only to support multiple customer instances in the Unified Contact Center Hosted (Unified CCH) that supports multi-tenant or shared servers that manage multiple customer instances. All Unified CCE systems are deployed as a single instance (using the same instance number in ICM Setup) across all the Unified ICM components.
Combined Routers and Loggers are often called the ICM Central Controller. When the Router and Logger modules run on the same server, the server is referred to as a Rogger. When the Call Router, Logger, and Peripheral Gateway modules run on the same server, the server is referred to as a Progger. In lab environments, the system Administrative Workstation (AW) can also be loaded onto the Progger to create a server known as a Sprawler configuration (also known as All-in-One configuration for Unified System CCE); however, this configuration is approved only for lab use and is not supported in customer production environments.
For each Unified CM cluster in your Unified CCE environment, you need a Unified CM PIM on a separate Peripheral Gateway and physical server. For deployments requiring multiple PIMs for the same Unified CM cluster, you need a separate PG and physical server for each PIM. Starting from
Unified CCE 7.5, deployments with multiple Unified CM PIMs and with CTI OS do not require a separate PG or separate physical server.
For each Unified CM Peripheral Gateway, you need one CTI Server and one CTI OS to communicate with the desktops associated with the phones for that Unified CM cluster. For each Unified IP IVR or CVP Call Server, you need one VRU PIM. The server that runs the Unified CM PIM, the CTI Server, and the CTI OS is referred to as an Agent Peripheral Gateway (APG). VRU PIMs could also be part of the Agent PG in the case of the Generic PG or System PG. Often, the Unified CM PIM, the CTI Server, the CTI OS, and multiple VRU PIMs will run on the same server. Internal to the PG is a process called the PG Agent, which communicates to the Central Controller. Another internal PG process is the Open Peripheral Controller (OPC), which enables the other processes to communicate with each other and is also involved in synchronizing PGs in redundant PG deployments. Figure 1-4 shows the
Figure 1-4 Communications Among Peripheral Gateway Software Processes
In larger, multi-site (multi-cluster) environments, multiple PGs are usually deployed. Each PG requires a local Unified CM node. When multiple Unified CM clusters are deployed, the ICM software makes them all appear to be part of one logical enterprise-wide contact center with one enterprise-wide queue.
Unified CCE Components, Terminology, and Concepts
This section describes the major components and concepts employed in a Unified CCE solution.
Unified CCE Agent Options
Cisco offers the following interfaces for Unified CCE agents (see Figure 1-5):
• Cisco Agent Desktop
Cisco Agent Desktop provides an out-of-the-box, feature-rich desktop solution for Unified CCE. The desktop application can be deployed in various ways:
– Windows application
– Browser-based application
– Cisco Unified IP Phone Agent, where there is no desktop application at all but just an XML application on the IP phone
• Cisco Toolkit
The CTI Toolkit provides a software toolkit for building custom desktops, desktop integrations into third-party applications, or server-to-server integrations to third-party applications.
Unified CM Cluster IP IVR 1 132072 PSTN IP voice TDM Voice CTI/Call control data Unified CCE Agent
desktops
IP IVR 2
IP phones PG 1
PG server
ICM central controller
SCI JTAPI SCI JTAPI V IP IP IP IP M M M JTAPI CTI OS server CCM PIM IVR 1 PIM IVR 2 PIM OPC PG Agent CTI server
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
• CRM Connectors
CRM Connectors provide pre-built integrations into the major CRM applications such as SAP, Siebel, Salesforce, Microsoft CRM, and Peoplesoft.
Figure 1-5 Variety of Agent Interfaces for Unified CCE
Cisco Agent Desktop
Cisco Agent Desktop (CAD) is an out-of-the-box desktop application that enables the agent to perform agent state control (including login, logout, ready, not ready, and wrap up) and call control (including answer, release, hold, retrieve, transfer, conference, make call). CAD requires use of a Cisco Unified IP phone or Cisco IP Communicator (softphone). Other phones can be used as well using the Mobile Agent option (see Cisco Unified Mobile Agent, page 1-21, for more details). Other features, such as an integrated chatting application, call recording, and workflow automation, may also be included. (See
Figure 1-6.)
Figure 1-6 Cisco Agent Desktop
Through integration with Cisco Unified Presence, contact center agents and supervisors using CAD can see subject matter experts (SMEs) who use Cisco Unified Presence Communicator. They can initiate chat sessions with SMEs for consultation on various customer questions or issues and, if needed, can initiate a transfer or a conference to achieve first-caller resolution. The agent or supervisor also has the capability to extend the call data received using Instant Messaging.
CAD also comes in a browser-based edition as a thin client application, which allows more flexibility in deployment and operation with the same rich set of capabilities highlighted above.
CAD also provides IP Phone Agent as an agent interface that does not require a desktop application. It is implemented as an XML application that is rendered on the screen of the IP phone and controlled through the softkeys and buttons on the phone. The XML application performs agent state control, while call control is handled through the normal phone softkeys and buttons. Other enhanced features, including silent monitoring, call recording, screen pop, and call center statistics, are also available through this interface.
Agents using the Cisco Agent Desktop, the browser edition, or IP Phone Agent can be managed by a supervisor using the Cisco Supervisor Desktop, which enables the supervisor to monitor and control agent state, monitor some call center statistics, monitor agents silently, barge in on agents, intercept calls, and initiate agent call recording.
Cisco Toolkit
Cisco Toolkit is a software development kit that provides the capability to build a customized agent desktop, customize the shipped custom desktop samples, or integrate a toolbar into a third-party application. Desktop applications built using CTI Toolkit interact with the CTI Object Server (CTI OS). The APIs available in CTI toolkit include COM/C++, Java, and .NET. A Cisco toolkit desktop can provide the same agent state controls and call controls as CAD. Cisco toolkit desktops require the agent to use a Cisco Unified IP Phone or Cisco IP Communicator (software phone). Other phones can be used as well using the Mobile Agent option (see Cisco Unified Mobile Agent, page 1-21, for more details).
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
Cisco Toolkit also provides the capabilities to develop a custom supervisor desktop. Supervisory functions enable a supervisor to monitor and control agent state, monitor some call center statistics, monitor agents silently, barge in on agents, intercept calls, and initiate agent call recording. Note that supervisors using a supervisor desktop based on CTI Toolkit cannot perform these functions for agents using Cisco Agent Desktop.
The section on CTI Object Server (CTI OS), page 1-13, provides some more details on the components and interfaces in CTI Toolkit.
CRM Connectors
Cisco offers pre-built, certified CRM Connectors for a number of major CRM packages including SAP, Siebel (using CTI OS driver), Salesforce.com, Microsoft Dynamics CRM, and Peoplesoft. These integrated solutions enable call control from the CRM user interface (Answer, Drop, Hold, Un-Hold, Blind or Warm Transfers, and Conferences), outbound and consultative calls from the CRM desktop, and delivery and manipulation of Call Context Data (CTI screen pop).
Agents using a third-party CRM user interface connected through a CRM Connector can be supervised using a CTI Toolkit-based supervisor desktop.
For more information about desktop selection and design considerations, see Unified Contact Center Enterprise Desktop, page 4-1.
CTI Object Server (CTI OS)
The Computer Telephony Integration Object Server (CTI OS) is Cisco's next-generation customer contact integration platform. CTI OS combines a powerful, feature-rich server and an object-oriented software development toolkit to enable rapid development and deployment of complex CTI applications. Together with the Cisco CTI Server Interface, CTI OS Server and CTI OS Client Interface Library (CIL) create a high-performance, scalable, fault-tolerant CTI architecture.
The CTI OS application architecture consists of three tiers:
• The CIL is the first tier, providing an application-level interface for developers. This is part of the CTI Toolkit described above.
• The CTI OS Server is the second tier, providing the bulk of the event and request processing and enabling the object services of the CTI OS system.
• The Cisco CTI Server is the third tier, providing the event source and the back-end handling of telephony requests. CTI OS Server connects to CTI Server for its event and request handling. CTI Server also provides an open published protocol for CTI integration that is sometimes useful for server-to-server integrations. This is part of the CTI Toolkit as well.
Fault-tolerance is provided through a pair of servers that operate together and back up each other. There is no notion of an active and passive server, or of a primary and secondary server. Both servers are always active. Clients may connect to either server. In the event of the failure of any one server, clients can automatically reconnect to the alternate server.
CTI OS connects customer contact servers such as CTI Server with client applications. (See Figure 1-7.) The connection to a contact server is established through a CTI Server Driver library. This library receives state change events on agents, and calls. Those events are sent to the Service Broker, which determines what objects to update. These objects generate update events to the Event Notification Engine, which then notifies all subscribing clients.
Figure 1-7 Generalized View of Information Flow in CTI OS
The type of messages received by the client application depends on the connection mode. Clients may connect in agent or monitor mode. In agent mode, the client receives events specific to that agent (calls delivered or originated on the agent's instrument, agent state changes, and skill group statistics). In monitor mode, the client provides a message filter expression, and the expression selects the types of messages that the client will receive.
Clients may initiate requests such as answering or dropping a call. The request is received by CTI OS through the client connection interface. Requests are brokered by the request service which forwards the request to the correct object, which then forwards it to the CTI Server.
Administrative Workstation
The Administrative Workstation (AW) provides a collection of administrative tools for managing the ICM software configuration. The two primary configuration tools on the AW are the Configuration Manager and the Script Editor. The Configuration Manager tool is used to configure the ICM database to add agents, add skill groups, assign agents to skill groups, add dialed numbers, add call types, assign dialed numbers to call types, assign call types to ICM routing scripts, and so forth. The Script Editor tool is used to build ICM routing scripts. ICM routing scripts specify how to route and queue a contact (that is, the script identifies which agent should handle a particular contact).
For details on the use of these tools, refer to the Cisco Unified Contact Center Administration Guide, available at http://www.cisco.com/en/US/products/sw/custcosw/ps1844/prod_maintenance_guides_list.html 143303 CTI OS Service Broker Call Object Agent Object CTI Server Driver Lib
CTI Server
CTI OS Client Request Service Event Notification
Engine
Client Connection Object Map
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
The AW is the only software module that must run on a separate server from all of the other Unified CCE software modules. An AW can be deployed in the same location as, or remote from, the ICM Central Controller. Each AW is independent of other AWs, and redundancy is provided by deploying multiple AWs.
Some AWs communicate directly with the ICM Central Controller, and they are called Distributor AWs. (See Figure 1-8.) An ICM deployment must have at least one Distributor AW. Additional AWs
(distributors or clients) are also allowed for redundancy (primary and secondary distributors) or for additional access by the AW clients in a site. At any additional site, at least one distributor and multiple client AWs can be deployed; however, client AWs should always be local to their AW distributor.
Figure 1-8 Communication Between ICM Central Controller and Distributor AW
Client AWs communicate with a Distributor AW to view and modify the ICM Central Controller database and to receive real-time reporting data. Distributor AWs off-load the Central Controller (the real-time call processing engine) from the task of constantly distributing real-time contact center data to the client AWs.
AWs can be installed with the following software options:
• Historical Data Server (HDS)
• WebView Server
• Internet Script Editor Server
• Web Administration Tool Server (Unified System CCE deployments only)
The Historical Data Server (HDS) is the database used for longer-term data storage and reporting. WebView Server is the reporting server that can be installed either on an HDS server or on a standalone server. For information on the reporting deployment options, refer to the chapters on Sizing Unified CCE Components and Servers, page 10-1, and Securing Unified CCE, page 8-1.
The WebView Server option provides browser-based reporting. This option enables reporting to be done from any computer with a browser. The Internet Script Editor Server can be installed only on a Distributor AW, and it provides an HTTPS (default protocol) connection for Script Editor clients. The Web Administration Tool Server provides a browser-based configuration tool for Unified System CCE, and it can be installed only on a Distributor AW (called an Administration and WebView Reporting server in Unified System CCE).
The reason for requiring the AW to run on a separate server for production systems is to ensure that complex reporting queries do not interrupt the real-time call processing of the Call Router and Logger processes. For lab or prototype systems, the AW (with the WebView Server option) can be installed on
143304 Central Controller Real-Time Data Config and Historical Data AW Distributor with HDS AWDB and HDS Router Logger WebView
the same server as the Call Router and Logger. If the AW is installed on the same server as the Logger, then HDS is no longer required because a complete copy of the Logger database is already present on the server.
For more details on the design and configuration of the AWs, refer to the ICM product documentation available online at Cisco.com.
Unified CCE Reporting
The Unified CCE Reporting solution provides an interface to access data describing the historical and real-time states of the system. The reporting solution consists of the following components:
• WebView — the reporting user interface
• Reporting Data — contained on a Distributor AW
– Administrative Workstation Database (AWDB) — contains real-time and configuration data
– Historical Data Server (HDS) — contains the historical data
WebView
The reporting user interface is a web-based application referred to as WebView. WebView performs the basic operations of gathering user input, querying the databases and presenting the requested data. Additionally, WebView is a full-featured reporting application server that provides functions such as authentication, storing users' favorite reports, launching scheduled reports, and so forth. WebView can be installed on an AW or, to increase scalability, it can be installed on a standalone server. The WebView architecture is described in the WebView Installation and Administration Guide, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps4145/prod_installation_guides_list.html
WebView comes with a number of categories of report templates. Each category presents different views of the data generated by call center activity. To determine which templates are best suited for your reporting requirements, refer to the WebView Template Reference Guide, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps4145/products_user_guide_list.html
Cisco Unified Intelligence Suite
The Cisco Unified Intelligence Suite is an advanced reporting option that can be substituted for, or used in conjunction with, WebView. This platform is a web-based application offering many Web 2.0 features, greater scalability, better performance, and advanced features such as the ability to integrate data from other Cisco Unified Communications products or third-party data sources.
The Cisco Unified Intelligence Suite consists of two components: Intelligence Server and the Archiver. Both of these components require a separate and dedicated server.
The Intelligence Server is a web-based reporting application that provides real-time and historical reports and dashboards as well as several developer tools for extending the platform and customizing the user experience.
The Archiver is an MSSQL data repository containing a normalized data schema and the infrastructure of tables and processes that will enable customers to Extract, Transform, and Load (ETL) data from any data source.
A unique ETL process is created for each data source and is referred to as a Data Connector. Refer to the Archiver installation and configuration guide for more information on Data Connectors.
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
Reporting Data
The data sources for WebView reports reside on a Distributor AW. For a detailed description of the reporting data flow and the concepts introduced here, refer to the WebView Installation and
Administration Guide, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps4145/prod_installation_guides_list.html Administrative Workstation Database (AWDB)
The AWDB stores real-time and configuration data. Real-time reports combine these two types of data to present a near-current transient snapshot of the system. Real-time reports refresh on a regular interval so that the most current data is always displayed.
Historical Data Server (HDS)
The HDS stores historical data. Historical reports query the AWDB to gather configuration data and join that data with data found in the HDS. Historical reports are typically available in two forms: reports generated on the half hour and reports generated daily. Half-hour reports should be used to report on periods of time less than one day in length.
Unified Contact Center Management Portal
The Unified Contact Center Management Portal provides a simple to use web-based user interface to streamline the day-to-day provisioning and configuration operations performed by a contact center manager, team lead, or administrator. The Management Portal provides the following key benefits:
• Simple to use web user interface for performing basic tasks such as move/add/modify phones, agents, skill groups, teams, and other common contact center administrative functions for an IP contact center
• Unified Configuration; that is, tenant provisioning of both the applicable IP contact center elements and the Unified Communications Manager components through a single task-based web interface
• Partitioned System supporting multiple business units with complete autonomy
• Hierarchical Administration supporting multiple business-level users, where each user is defined with specific roles and responsibilities
• Audit Trail Reports that detail configuration changes and usage by all users of the management portal
Support Tools
Cisco Support Tools is an application that contains a suite of utilities that allow you to manage and troubleshoot servers that run a broad range of Cisco Unified product software components.Through Support Tools, you can troubleshoot configuration and performance problems on these systems from any machine running a supported version of Windows and Internet Explorer on your network that can access the Support Tools Server.
Access to utilities in the Support Tools suite is through a browser-based interface – the Support Tools Dashboard – installed on the Support Tools Server. Levels of security control both access to the Dashboard and the ability to use specific tools once logged in. In low bandwidth conditions (for example, via dial-up access) or when Web browsing is otherwise impractical, many Support Tools utilities can also
JTAPI Communications
In order for JTAPI communications to occur between Unified CM and external applications such as the Unified CCE and Unified IP IVR, a JTAPI user ID and password must be configured within Unified CM. Upon startup of the Unified CM PIM or upon startup of the Unified IP IVR, the JTAPI user ID and password are used to log in to Unified CM. This login process by the application (Unified CM PIM or Unified IP IVR) establishes the JTAPI communications between the Unified CM cluster and the application. A single JTAPI user ID is used for all communications between the entire Unified CM cluster and the ICM. A separate JTAPI user ID is also required for each Unified IP IVR server. In a Unified CCE deployment with one Unified CM cluster and two Unified IP IVRs, three JTAPI user IDs are required: one JTAPI user ID for the ICM application and two JTAPI user IDs for the two
Unified IP IVRs.
The Unified CM software includes a module called the CTI Manager, which is the layer of software that communicates via JTAPI to applications such as the ICM and Unified IP IVR. Every node within a cluster can execute an instance of the CTI Manager process, but the Unified CM PIM on the PG communicates with only one CTI Manager (and thus one node) in the Unified CM cluster. The CTI Manager process communicates CTI messages to/from other nodes within the cluster. For example, suppose a deployment has a voice gateway homed to node 1 in a cluster, and node 2 executes the CTI Manager process that communicates to the ICM. When a new call arrives at this voice gateway and needs to be routed by the ICM, node 1 sends an intra-cluster message to node 2, which will send a route request to the ICM to determine how the call should be routed.
Each Unified IP IVR also communicates with only one CTI Manager (or node) within the cluster. The Unified CM PIM and the two Unified IP IVRs from the previous example could each communicate with different CTI Managers (nodes) or they could all communicate with the same CTI Manager (node). However, each communication uses a different user ID. The user ID is how the CTI Manager keeps track of the different applications.
When the Unified CM PIM is redundant, only one side is active and in communication with the Unified CM cluster. Side A of the Unified CM PIM communicates with the CTI Manager on one Unified CM node, and side B of the Unified CM PIM communicates with the CTI Manager on another Unified CM node. The Unified IP IVR does not have a redundant side, but the Unified IP IVR does have the ability to fail over to another CTI Manager (node) within the cluster if its primary CTI Manager is out of service. For more information on failover, refer to the chapter on Design Considerations for High Availability, page 3-1.
The JTAPI communications between the Unified CM and Unified CCE include three distinct types of messaging:
• Routing control
Routing control messages provide a way for Unified CM to request routing instructions from Unified CCE.
• Device and call monitoring
Device monitoring messages provide a way for Unified CM to notify Unified CCE about state changes of a device (phone) or a call.
• Device and call control
Device control messages provide a way for Unified CM to receive instructions from Unified CCE on how to control a device (phone) or a call.
A typical Unified CCE call includes all three types of JTAPI communication within a few seconds. When a new call arrives, Unified CM requests routing instructions from the ICM. For example, when Unified CM receives the routing response from the ICM, Unified CM attempts delivery of the call to the agent phone by instructing the phone to begin ringing. At that point, Unified CM notifies the ICM that
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.
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.
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.
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. 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.
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. 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.
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.
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.
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.
Multichannel Subsystems
The ICM has the capability to provide a multichannel contact center that includes email and web collaboration. It does this through interactions with Cisco E-Mail Manager (CeM) and Cisco
Collaboration Server (CCS). (See Figure 1-9.). Starting from Cisco Unified CCE 7.2, Cisco Interaction Manager (CIM), which includes E-mail Interaction Manager (EIM) and Web Interaction Manager (WIM), should be deployed with new installations in order to provide multichannel capabilities. For more details, refer to the Unified CCE Software Compatibility Guide, available on
http://www.cisco.com.
With CeM and CCS, ICM has three integration points that are used for its multimedia subsystems:
• Media Routing (MR) interface — The MR interface is through the MR Peripheral Gateway (PG). Cisco E-Mail Manager and Cisco Collaboration Server use this interface to tell the ICM that they have a new task that needs to be serviced, and they would like an agent to be assigned.
• Agent Reporting and Management (ARM) interface — The ARM interface is through the CTI server on the PG to which a given agent is assigned. Cisco E-Mail Manager and Cisco Collaboration Server use the ARM interface to tell the ICM when the agent is working on a task in their subsystem, and to monitor the status of agents in the ICM.
• Configuration Application Programming Interface (ConAPI) — The ConAPI is through the Administrative Workstations (AWs). Cisco E-Mail Manager and Cisco Collaboration Server use this interface to ensure that their configuration and the ICM's configuration are in sync. The ConAPI is used to create skill groups, configure agents, and create ICM services for routing. This API is internal to the Cisco Unified CCE solution and cannot be used for third-party customizations.
Figure 1-9 Multichannel Subsystem
Cisco E-Mail Manager
Cisco E-Mail Manager provides inbound and outbound email services for agents. Cisco E-Mail Manager enables incoming email to be processed with a rules engine, categorized into folders for processing, and queued to agents. When emails are assigned to agents, the agents are able to respond to them, with Cisco E-Mail Manager providing storage of the conversation and tracking of multi-leg responses.
Cisco E-Mail Manager has the ability to escalate overdue emails to be synchronously routed through the ICM router so that they get attention right away. It also has the ability to do some email routing itself.
143305
MR PG Agent PG Central Controller
CeM Media Blender
CCS ConAPI ARM MR Firewall Administrative Workstation
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
Cisco Collaboration Server
The Cisco Collaboration Server provides web-based collaboration and chat capabilities to agents. These capabilities can be used independently or as a supplement to voice calls. Cisco Collaboration Server connects to the ICM through its Media Blender component. This component is required because Cisco Collaboration Server itself must sit outside the corporate firewall to allow for incoming connections from customers.
When doing blended voice and collaboration sessions with IP-based agents, Media Blender talks to the Media Routing PG to route calls. When doing blended voice and collaboration with TDM-based agents, Media Blender talks directly to the TDM switch to queue phantom calls to agents.
Cisco Collaboration Server provides desktop user interfaces for both callers and agents. These components allow the callers and agents to collaborate using a variety of media, including chat, web page sharing, advanced web page sharing (using the Dynamic Content Adapter), application sharing, white boarding. Cisco Collaboration Server also provides an API for developing custom media. Cisco Collaboration Server can use its own internal routing engine or it can use the ICM's routing engine to assign incoming calls to agents. Cisco Collaboration Server provides the ability, through its
multi-session chat desktop, for agents to work with more than one caller at a time.
Cisco Interaction Manager
Cisco Interaction Manager provides an integrated suite of interaction channels that include Cisco Unified E-mail Interaction Manager (Unified EIM) and Cisco Unified Web Interaction Manager (Unified WIM).
There is a design guide specifically for the Cisco Interaction Manager platform, Cisco Unified Web and
E-Mail Interaction Manager Solution Reference Network Design (SRND) Guide For Unified Contact Center Enterprise, Hosted, and ICM, available at
http://www.cisco.com/en/US/products/ps7236/products_implementation_design_guides_list.html
Cisco Unified Outbound Option
Agents can handle both inbound and outbound contacts, which helps in optimizing contact center resources. The Cisco Unified Outbound Option enables the multi-functional contact center to take advantage of Cisco Unified CCE enterprise management. Contact center managers in need of outbound campaign solutions can take advantage of the enterprise view that Cisco Unified CCE maintains over agent resources.
Cisco Unified Mobile Agent
Cisco Unified CCE provides the capability for an agent to use any PSTN phone and a quality high-speed data connection between the agent desktop and the CTI OS server. For design guidance and
considerations for implementing Cisco Unified Mobile Agent, see the chapter on Cisco Unified Mobile Agent, page 6-1.
Unified System CCE
utilizes a single installer to simplify installation and configuration, and it provides web-based administration. Configuration of Unified System CCE is further simplified by removing Services, Translation Routes, Device Targets, Labels, Sub Skill Groups, and Agent IDs. If desired, Agent IDs can be configured in Unified System CCE 7.2(2) and later releases.
Unified System CCE supports new installations and upgrades from previous System CCE releases. It continues to provide fault tolerance through the duplex operation on the Central Controller and Agent/IVR Controller. Unified System CCE can connect to a parent Unified ICM, and the connection is made between the child Unified CCE System PG and the parent Gateway PG.
Unified System CCE consists of the following internal components, illustrated in Figure 1-10 and
Figure 1-11:
• Central Controller — Includes Call Router and Logger (SQL Server must be pre-installed).
• Agent/IVR Controller — Agent Peripheral Gateway (Unified CCE System PG), CTI Server, and CTI Object Server. Optionally, beginning with Unified System CCE 7.5(1), VRU Peripheral Gateway for Unified CVP.
• Administration and WebView Reporting — Distributor Administrative Workstation (AW), WebView, Historical Data Server (HDS), and Internet Script Editor Server (Requires Microsoft Internet Information Service (IIS) and SQL Server pre-installed).
• Unified CM — Unified System CCE connects to single a Unified CM cluster.
• Unified IP IVR or Unified CVP — Queue and prompting platform for Unified System CCE.
• Optional Components:
– Outbound Controller — Dialer and Media Routing Peripheral Gateway for Outbound Option (Outbound Controller can be co-located on the Agent/IVR Controller in Unified
System CCE 7.5(1)).
– Multichannel Controller — Media Routing Peripheral Gateway for Cisco Interaction Manager (CIM).
– Unified CCE gateway to Unified ICM
– Cisco Agent Desktop Services (co-located with the Agent Peripheral Gateway)
– Unified Contact Center Management Portal (Unified CCMP) — Co-located with the
Chapter 1 Architecture Overview
Unified CCE Components, Terminology, and Concepts
Figure 1-10 Unified System CCE with IP IVR
Figure 1-11 Unified System CCE with Unified CVP
143306 Optional IPIVR Admin Browser WebView Browser Agent Desktop Unified CM Cluster Central Controller Agent/IVR Controller Outbound Controller Multichannel Controller CAD Services Admin and Reporting
Optional CCMP
Admin and Reporting
Central Controller Agent/IVR Controller Outbound Controller Multichannel Controller CAD Services CCMP Optional Optional Admin Browser WebView Browser Admin Desktop Unified CM Cluster CVP CVP Controller
For more information on Unified System CCE, see the chapter on Deployment Models, page 2-1.
Unified ICM Routing Clients
A Unified ICM routing client is anything that can generate a route request to the Unified ICM Central Controller. The Unified CM PIM (representing the entire Unified CM cluster) and each
Unified IP IVR/Unified CVP PIM are routing clients. Routing clients generate route requests to the Unified ICM Central Controller. The Unified ICM Central Controller then executes a routing script and returns a routing label to the routing client. A redundant PIM is viewed as a single logical routing client, and only one side of a PIM is active at any point in time. In a Unified CCE deployment with one Unified CM cluster (with any number of nodes) and two Unified IP IVRs, three routing clients are required: the Unified CM PIM and the two Unified IP IVR/Unified CVP PIMs.
The public switched telephone network (PSTN) can also function as a routing client. The Unified ICM supports a software module called a Network Interface Controller (NIC), which enables the Unified ICM to control how the PSTN routes a call. Intelligently routing a call before the call is delivered to any customer premise equipment is referred to as pre-routing. Only certain PSTNs have NICs supported by the Unified ICM. For a detailed list of PSTN NICs and details on Unified ICM pre-routing, refer to the
Pre-installation Planning Guide for Cisco ICM Enterprise & Hosted Editions, available at
http://www.cisco.com/en/US/products/sw/custcosw/ps1001/prod_installation_guides_list.html
Other applications such as the Cisco Media Blender, the Cisco Collaboration Server, the Cisco E-Mail Manager, Web Interaction Manager, or E-mail Interaction Manager can also function as routing clients to allow the Unified ICM to become a multi-channel contact routing engine. Details of currently available multi-channel routing are available on Cisco.com.
Device Targets
Each IP phone must be configured in the Unified ICM Central Controller database as a device target. Only one extension on the phone can be configured as a Unified ICM device target. Additional extensions may be configured on the phone, but those extensions will not be known to the Unified ICM software and, thus, no monitoring or control of those additional extensions is possible. The Unified ICM provides call treatment for Reroute On No Answer (RONA), therefore it is not necessary to configure call forwarding on ring-no-answer in the Unified CM configuration for the phones. Unless call center policy permits warm (agent-to-agent) transfers, the Unified CCE extension also should not be published or dialed by anyone directly, and only the Unified ICM software should route calls to this Unified CCE phone extension.
At agent login, the agent ID and phone extension are associated, and this association is released when the agent logs out. This feature allows the agent to log in to any agent phone. At agent login, the Unified CM PIM requests Unified CM to begin monitoring the agent phone and to provide device and call control for that phone. As mentioned previously, each phone must be mapped to the Unified ICM JTAPI user ID in order for the agent login to be successful.
Labels
Labels are the response to a route request from a routing client. The label is a pointer to the destination where the call is to be routed (basically, the number to be dialed by the routing client). Many labels in a Unified CCE environment correspond to the Unified CCE phone extensions so that Unified CM and Unified IP IVR can route or transfer calls to the phone of an agent who has just been selected for a call.
Chapter 1 Architecture Overview
Unified ICM Routing Clients
Often, the way a call is routed to a destination depends upon where the call originated and where it is being terminated. This is why Unified CCE uses labels. For example, suppose we have an environment with two regionally separated Unified CM clusters, Site 1 and Site 2. A phone user at Site 1 will typically just dial a four-digit extension to reach another phone user at Site 1. In order to reach a phone user at Site 2 from Site 1, users might have to dial a seven-digit number. To reach a phone user at either site from a PSTN phone, users might have to dial a 10- digit number. From this example, we can see how a different label would be needed, depending upon where the call is originating and terminating.
Each combination of device target and routing client must have a label. For example, a device target in a Unified CCE deployment with a two-node Unified CM cluster and two Unified IP IVRs will require three labels. If you have 100 device targets (phones), you would need 300 labels. If there are two regionally separated Unified CM clusters, each with two Unified IP IVRs and 100 device targets per site, then we would need 1200 labels for the six routing clients and 200 device targets (assuming we wanted to be able to route a call from any routing client to any device target). If calls are to be routed to device targets only at the same site as the routing client, then we would need only 600 labels (three routing clients to 100 device targets, and then doubled for Site 2).
Labels are also used to route calls to Unified IP IVR CTI Ports. Details on configuring labels are provided in the Unified CCE Installation Guide, available on Cisco.com. A bulk configuration tool is also available to simplify the configuration of the labels.
Agent Desk Settings
Agent Desk Settings provide a profile that specifies parameters such as whether auto-answer is enabled, how long to wait before rerouting a call for Ring No Answer, what DN to use in the rerouting, and whether reason codes are needed for logging out and going not-ready. Each agent must be associated with an agent desk setting profile in the Unified ICM configuration. A single agent desk setting profile can be shared by many agents. Changes made to an agent’s desk setting profile while the agent is logged in are not activated until the agent logs out and logs in again.
Agents
Agents are configured within the Unified ICM and are associated with one specific Unified CM PIM (that is, one Unified CM cluster). Within the Unified ICM configuration, you also configure the password for the agent to use at login. These passwords are local only to the Unified CCE application and do not interact with the Active Directory or any other encryption or authentication system.
Skill Groups
Skill groups are configured within the Unified ICM so that agents with similar skills can be grouped together. Agents can be associated with one or more skill groups. Skill groups are associated with a specific Unified CM PIM. Skill groups from multiple PIMs can be grouped into Enterprise Skill Groups. Creating and using Enterprise Skill Groups can simplify routing and reporting in some scenarios.
Directory (Dialed) Numbers and Routing Scripts
In order for Unified CM to generate a route request to the Unified ICM, Unified CM must associate the DN with a CTI Route Point that is associated with the Unified ICM JTAPI User. The DN must also be configured in the Unified ICM. Once the Unified ICM receives the route request with the DN, that DN is mapped to a Unified ICM Call type, which is then mapped to a Unified ICM routing script.
Agent Login and State Control
Agents log in to Unified CCE from their Unified CCE agent desktop application. When logging in, the agent is presented with a dialog box that prompts for agent ID or login name, password, and the Unified CCE phone extension to be used for this login session. It is at login time that the agent ID, phone extension (device target), agent desk setting profile, skills, and desktop IP address are all dynamically associated. The association is released upon agent logout.
Unified CCE Routing
The example routing script in Figure 1-12 illustrates how Unified CCE routes calls. In this routing script, the Unified CM PIM (or cluster) is the routing client. Upon receipt of the route request, the Unified ICM maps the DN to a call type and then maps the call type to this routing script. In this routing script, the Unified ICM router first uses a Select node to look for the Longest Available Agent (LAA) in the BoatSales skill group on the CCM_PG_1 peripheral gateway (or cluster). The Unified ICM router determines that agent 111 is the LAA. Agent 111 is currently logged in from device target 1234 (Unified CM phone extension 1234 in this scenario). The Unified ICM router then determines the label to be returned, based upon the device target and routing client combination. The appropriate label is then returned to the routing client (Unified CM cluster) so that the call can be routed properly to that phone (device target).
Chapter 1 Architecture Overview
Unified CCE Routing
Figure 1-12 Routing Script Example
Translation Routing and Queuing
If no agents are available, then the router exits the Select node and transfers the call to a Unified IP IVR to begin queuing treatment. The transfer is completed using the Translation Route to VRU node. The Translation Route to VRU node returns a unique translation route label to the original routing client, the Unified CM cluster. The translation route label will equal a DN configured in Unified CM. In
Unified CM, that DN is mapped to a CTI Route Point that is associated with the JTAPI user for the Unified IP IVR to which the call is being transferred.
Unified CM and Unified IP IVR will execute the JTAPI routing control messaging to select an available CTI Port.
When the call is successfully transferred to the Unified IP IVR, the Unified IP IVR translation routing application first sends a request instruction message to the Unified ICM via the SCI between the Unified IP IVR and the Unified ICM. The Unified ICM identifies the DN as being the same as the translation route label and is then able to re-associate this call with the call that was previously being routed. The Unified ICM then re-enters the routing script that was previously being run for this call. The re-entry point is the successful exit path of the Translation Route to VRU node. (See Figure 1-13.) At this point, the routing client has changed from the Unified CM cluster to IPIVR1.
While the call was being transferred, the routing script was temporarily paused. After the transfer to the Unified IP IVR is successfully completed, the Unified IP IVR becomes the routing client for this routing
Agent ID Dev Target
111 1234 Label 1234 1234 CM Cluster IPIVR 1 IPIVR 2 Dev Target 1234 1234 1234 1234
Route response returned to Unified CM Cluster
76581
Route request (DN, ANI, CED) Unified CM cluster
becomes available, and as in the previous example, the label to be returned to the routing client is identified based upon the combination of device target and routing client. Note that the routing client is now the Unified IP IVR. The label returned (1234) when agent 111 becomes available causes the Unified IP IVR to transfer the call to agent 111 (at extension 1234).
Figure 1-13 Translation Routing and Queuing
For each combination of Unified CM cluster and Unified IP IVR, a translation route and a set of labels is required. For example, if a deployment has one Unified CM cluster and four Unified IP IVRs, then four translation routes and sets of labels are required.
For deployments with multiple Unified IP IVRs, the Unified ICM routing script should select the Unified IP IVR with the greatest number of idle Unified IP IVR ports and then translation-route the call to that specific Unified IP IVR. If no Unified IP IVR ports are available, then the script should execute a Busy node. If a high number of calls are executing Busy nodes, then it is important to resize your Unified IP IVR port capacity.
Reroute On No Answer (RONA)
When a call is routed to an agent but the agent fails to answer the call within a configurable amount of time, the Unified CM PIM for the agent who did not answer will change that agent’s state to not ready (so that the agent does not get more calls) and launch a route request to find another agent. Any call data is preserved and popped onto the next agent's desktop. If no agent is available, the call can be sent back to the Unified IP IVR for queuing treatment again. Again, all call data is preserved. The routing script
Agent ID Dev Target
111 1234 Rtg Client Label 1234 1234 CM Cluster IPIVR 1 IPIVR 2 Dev Target 1234 1234 1234 1234
Route response returned to IPIVR 1
76582
Original route request
New routing client IPIVR 1
Original routing client
Unified CM Cluster
