500-052 Deploying Cisco Unified Contact Center Express Questions and Answers

To enable a contact center supervisor to access and monitor live data reports for multiple teams, the administrator should assign the supervisor as primary supervisor for one of the teams and as secondary supervisor for other relevant teams. This way, the supervisor can view the live data reports for all the teams that he or she is associated with, either as primary or secondary supervisor. The supervisor can also switch between different teams in the Cisco Finesse desktop or the Cisco Unified Intelligence Center (CUIC) web interface. For more information on how to assign primary and secondary supervisors for teams, see the Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1), Chapter: Unified CCX Application Configuration, Section: Teams.

The following actions will not enable a contact center supervisor to access and monitor live data reports for multiple teams:

• Take no action, because a supervisor cannot monitor more than one team: This is incorrect, because a supervisor can monitor more than one team if he or she is assigned as primary or secondary supervisor for those teams. Taking no action will prevent the supervisor from accessing and monitoring live data reports for any team.
• Assign the supervisor as primary supervisor for all the relevant teams: This is not recommended, because a primary supervisor is responsible for managing and coaching the agents in a team, and having multiple primary supervisors for the same team can cause confusion and conflict. A team should have only one primary supervisor and optionally one or more secondary supervisors. A secondary supervisor can access and monitor live data reports for a team, but cannot perform other supervisory tasks, such as barge-in, intercept, or chat with agents.
• Add the supervisor as a member of all the relevant teams: This is not possible, because a supervisor cannot be a member of a team. A team consists of agents who handle customer contacts, and a supervisor who oversees the performance and activities of the agents. A supervisor can be associated with one or more teams, but cannot be part of a team. References:
• Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1)
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]2, Module 1: Cisco Unified CCX Overview, Lesson 2: Cisco Unified CCX User Roles and Capabilities, Topic: Supervisor Role

 The Agent email feature is available only in the Cisco Unified Contact Center Express Premium package. The Agent email feature is a basic email queuing and response system that allows agents to handle customer emails from the Cisco Agent Desktop. The feature supports email routing, email prioritization, email response templates, email attachments, email history, and email reporting12

The other options are not correct:

• Premium and Enhanced: The Agent email feature is not available in the Enhanced package. The Enhanced package supports only voice and chat interactions12
• Premium, Enhanced, and Standard: The Agent email feature is not available in the Enhanced and Standard packages. The Standard package supports only voice interactions12
• Premium and Standard: The Agent email feature is not available in the Standard package. The Standard package supports only voice interactions12

References: 1: Cisco Unified Contact Center Express Data Sheet - Cisco 1 2: Cisco Unified Contact Center Express Design Guide, Release 10.0(1) - Features [Cisco Unified Contact Center Express] - Cisco 2

 The Cisco Unified CCX license MAC is generated based on the hostname, IP address, and gateway address of the Unified CCX server. These are some of the system parameters that affect the license MAC, which is different from the physical MAC address of the system. Changing any of these parameters can invalidate the current license files. The Cisco Unified CCX version and the physical MAC are not used to generate the license MAC. References := Cisco Unified Contact Center Express Installation and Upgrade Guide, Release 12.5(1), Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 Course Outline

The invalid deployment option for Cisco Unified Contact Center Express is two Cisco Unified Contact Center Express clusters, each with two nodes, connected to the same Cisco Unified Cisco Unified Communications Manager cluster. This option is not supported because Cisco Unified Contact Center Express does not allow multiple clusters to share the same Cisco Unified Communications Manager cluster. Each Cisco Unified Contact Center Express cluster must have its own dedicated Cisco Unified Communications Manager cluster1.

The other options are valid deployment options for Cisco Unified Contact Center Express:

• A two-node Cisco Unified Contact Center Express cluster connected to a Cisco Unified Communications Manager cluster. This option is supported and provides high availability and redundancy for both Cisco Unified Contact Center Express and Cisco Unified Communications Manager. A two-node Cisco Unified Contact Center Express cluster consists of a primaryand a secondary node that can synchronize data and take over the call processing in case of a failure2.
• A one-node Cisco Unified Contact Center Express cluster connected to two Cisco Unified Communications Manager clusters. This option is supported and provides redundancy for Cisco Unified Communications Manager. A one-node Cisco Unified Contact Center Express cluster consists of a single node that handles all the call processing and administration functions. A one-node Cisco Unified Contact Center Express cluster can connect to two Cisco Unified Communications Manager clusters using the Intercluster Lookup Service (ILS) feature3.
• A one-node Cisco Unified Contact Center Express cluster connected to a Cisco Unified Communications Manager Express router. This option is supported and provides a cost-effective and simplified solution for small and medium-sized businesses. A one-node Cisco Unified Contact Center Express cluster can connect to a Cisco Unified Communications Manager Express router using the Skinny Client Control Protocol (SCCP) or the Session Initiation Protocol (SIP)4.

References: 1: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco 2: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco 3: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco 4: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco

Reactive debugging is a facility provided by the Cisco Unified CCX Editor that allows you to debug a Cisco Unified CCX script live with a real voice call. Reactive debugging enables you to step through the script execution and view the variable values and the call flow in real time. You can also set breakpoints and watchpoints to pause the script execution and inspect the variables. Reactive debugging is useful for troubleshooting and testing the script logic and functionality12

References: 1: Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 - Course 644-906 1 2: Cisco Unified Contact Center Express Scripting and Development Series: Volume 2, Editor Step Reference, Release 10.0(1) - Debugging Scripts [Cisco Unified Contact Center Express] - Cisco 

Cisco Finesse supports the use of custom call variable layouts to define how call variables appear on the Finesse agent desktop. The agent desktop determines which layout to use based on the value of a keyword variable that is named user.layout. This variable is passed to the agent desktop via the Set Enterprise Call Info step in the CCX script. The value of the user.layout variable must match the name of the custom call variable layout that is configured in the Finesse Administration page. If no user.layout variable exists, or if the value does not match any custom layout, the default layout will be used12

References: 1: Cisco Finesse Administration Guide, Release 12.5 (1) - Call Variables Layouts [Cisco Finesse] - Cisco 1 2: How to apply new ‘Call Variables Layout’ to desktop layo

 The three operations that can be performed within the Cisco Finesse IP Phone Agent (IPPA) are:

• A. A supervisor can use Finesse IPPA to act as an agent and accept calls. This is true because Finesse IPPA does not support supervisor tasks such as monitor, barge, and intercept, but supervisors can sign in and perform all agent tasks on their IP Phones. To perform supervisor tasks for Finesse IPPA agents, supervisors must sign in to the Finesse desktop and follow the same steps that they use for the Finesse desktop agents1.
• D. An agent using Finesse IPPA can enter Not Ready, Sign-out, and Wrap-up reasons. This is true because Finesse IPPA allows agents to change their state from Ready to Not Ready, sign out from the Finesse service, and apply wrap-up reasons after handling a call. Agents can select the appropriate reason codes from the list of available options on their IP Phones2.
• E. Agents can log in to Finesse IPPA with Cisco Unified CCX deployed using a Standard license. This is true because Finesse IPPA is supported on all Cisco Unified CCX license packages, including Standard, Enhanced, and Premium. Agents can use Finesse IPPA regardless of the license package that is deployed on Cisco Unified CCX3.

The other options are not correct because:

• B. An agent can sign in to Finesse IPPA and initiate call recording. This is false because Finesse IPPA does not support call recording. Agents cannot initiate, stop, or pause call recording from their IP Phones. Call recording is only supported on the Finesse desktop in the browser4.
• C. A supervisor can sign in to Finesse IPPA and initiate call recording. This is false because Finesse IPPA does not support call recording. Supervisors cannot initiate, stop, or pause call recording from their IP Phones. Call recording is only supported on the Finesse desktop in the browser4.

References: 1: Cisco Finesse Agent and Supervisor Desktop User Guide for Cisco Unified Contact Center Express, Release 12.5(1) - IP Phone Agent [Cisco Finesse] - Cisco 2: Cisco Finesse Agent and Supervisor Desktop User Guide for Cisco Unified Contact Center Express, Release12.5(1) - IP Phone Agent [Cisco Finesse] - Cisco 3: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco 4: Cisco Finesse Agent and Supervisor Desktop User Guide for Cisco Unified Contact Center Express, Release 12.5(1) - IP Phone Agent [Cisco Finesse] - Cisco

 The correct answer is B. The default script field when adding an application specifies the script that will be executed if there are any problems running the configured script for the application. For example, if the configured script is missing, corrupted, or containserrors, the default script will be executed instead. The default script field is mandatory and must point to a valid script file1.

The other options are not correct because:

• A. When a caller does not enter a choice in a Menu step, it will execute the default script. This is false because the Menu step has its own Timeout branch that determines what to do when the caller does not enter a choice within the specified timeout period. The default script field has no effect on the Menu step2.
• C. When the caller enters a digit in the Menu step that is not defined, the default script will be executed. This is false because the Menu step has its own Unsuccessful branch that determines what to do when the caller enters a digit that is not defined as a valid option. The default script field has no effect on the Menu step2.
• D. When the caller enters a digit that is not checked in the filter of the Get Digit String step, the default script will be executed. This is false because the Get Digit String step has its own Invalid Entry branch that determines what to do when the caller enters a digit that is not checked in the filter. The default script field has no effect on the Get Digit String step3.

References: 1: Cisco Unified Contact Center Express Administration Guide, Release 12.5(1) - Cisco Applications Configuration [Cisco Unified Contact Center Express] - Cisco 2: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.5(1) - Chapter 2: Media Steps [Cisco Unified Contact Center Express] - Cisco 3: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.5(1) - Chapter 3: Input Steps [Cisco Unified Contact Center Express] - Cisco

 The three tasks that an agent can perform on the Cisco Agent Desktop are:

• Chat with an SME. An agent can chat with a subject matter expert (SME) using the Cisco Agent Desktop integrated chat feature. This feature allows the agent to see the presence status of SMEs and other critical members of the enterprise, and to initiate chat sessions with them without navigating away from the Agent Desktop. The agent can also transfer the chat session to another agent or SME, or escalate the chat session to a voice or video call1.
• Transfer a call to an SME. An agent can transfer a call to an SME using the Cisco Agent Desktop call control buttons. The agent can select the destination SME from a list of availablecontacts or enter the SME’s phone number. The agent can also consult with the SME before transferring the call, or transfer the call directly2.
• Start a Cisco WebEx session with an SME. An agent can start a Cisco WebEx session with an SME using the Cisco Agent Desktop WebEx button. This feature allows the agent to invite the SME to join a web-based collaboration session that supports voice, video, and screen sharing. The agent can also invite the customer to join the WebEx session if needed3.

The other options are not correct because:

• B. Send an email to an SME. An agent cannot send an email to an SME using the Cisco Agent Desktop. The email feature of the Cisco Agent Desktop is only for handling incoming and outgoing emails from customers, not from internal contacts. The agent can use other applications, such as Cisco Unified Personal Communicator or Cisco Jabber, to send emails to SMEs4.
• C. Send enterprise data to an SME. An agent cannot send enterprise data to an SME using the Cisco Agent Desktop. The enterprise data feature of the Cisco Agent Desktop is only for displaying customer-related information, such as account number, name, address, and so on, that are passed from the Cisco Unified Contact Center Express server. The agent cannot modify or forward the enterprise data to SMEs5.

References: 1: Cisco Agent Desktop User Guide for Cisco Unified Contact Center Express, Release 10.0(1) - Chat [Cisco Unified Contact Center Express] - Cisco 2: Cisco Agent Desktop User Guide for Cisco Unified Contact Center Express, Release 10.0(1) - Call Control [Cisco Unified Contact Center Express] - Cisco 3: Cisco Agent Desktop User Guide for Cisco Unified Contact Center Express, Release 10.0(1) - WebEx [Cisco Unified Contact Center Express] - Cisco 4: Cisco Agent Desktop User Guide for Cisco Unified Contact Center Express, Release 10.0(1) - Email [Cisco Unified Contact Center Express] - Cisco 5: Cisco Agent Desktop User Guide for Cisco Unified Contact Center Express, Release 10.0(1) - Enterprise Data [Cisco Unified Contact Center Express] - Cisco

To deploy a Cisco Unified CCX application, the following tasks are required:

• Create a trigger: A trigger is a phone number or a URI that is associated with an application and invokes a script when it is dialed or requested. A trigger defines the type of communication (voice or HTTP), the maximum number of sessions, and the script to be executed. To create a trigger, use the Cisco Unified CCX Administration web interface and navigate to Applications > Trigger Management. For more information on how to create a trigger, see the Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1), Chapter: Unified CCX Application Configuration, Section: Trigger Management.
• Upload script to repository: A script is a set of instructions that defines the call flow and logic of an application. A script is created using the Cisco Unified CCX Editor, which is a graphical tool that allows users to drag and drop steps, variables, and expressions. To upload a script to the repository, use the Cisco Unified CCX Editor and select File > Save Script As. For more information on how to upload a script, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Saving and Uploading Scripts, Section: Saving and Uploading Scripts.
• Specify the maximum number of sessions: The maximum number of sessions defines how many concurrent calls or requests an application can handle. The maximum number of sessions is configured at the trigger level and depends on the license type and the available system resources. To specify the maximum number of sessions, use the Cisco Unified CCX Administration web interface and navigate to Applications > Trigger Management. For more information on how to specify the maximum number of sessions, see the Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1), Chapter: Unified CCX Application Configuration, Section: Trigger Management.

The following tasks are not required to deploy a Cisco Unified CCX application:

• Restart the Cisco Unified CCX Engine: The Cisco Unified CCX Engine is a service that runs on the Unified CCX server and executes the scripts associated with the applications. The Cisco Unified CCX Engine does not need to be restarted after deploying an application, unless there is a change in the system configuration or a problem with the service. To restart the Cisco Unified CCX Engine, use the Cisco Unified CCX Serviceability web interface and navigate to Tools > Control Center - Network Services. For more information on how to restart the Cisco Unified CCX Engine, see the Cisco Unified Contact Center Express Serviceability Administration Guide, Release 12.5 (1), Chapter: Unified CCX Serviceability, Section: Control Center - Network Services.
• Configure default session timeout: The default session timeout defines how long an idle session can remain active before it is terminated by the system. The default session timeout is configured at the system level and applies to all applications. The default session timeout does not need to be configured for each application, unless there is a specific requirement to override the system value. To configure the default session timeout, use the Cisco Unified CCX Administration web interface and navigate to System > System Parameters. For more information on how to configure the default session timeout, see the Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1), Chapter: Unified CCX System Configuration, Section: System Parameters. References:
• Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1)
• Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1)
• Cisco Unified Contact Center Express Serviceability Administration Guide, Release 12.5 (1)
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]5

This statement is false because a subflow cannot access all variables in the calling script, unless they are passed as input parameters or global variables. A subflow has its own local variables that are not visible to the calling script. A subflow can only access the variables that are mapped to its input parameters or declared as global variables1.

The other statements are true because:

• B. When the Call Subflow step executes, you can transfer values of variables from the calling flow to the subflow. This statement is true because you can use the Input Mappingstab of the Call Subflow step to map the variables from the calling flow to the input parameters of the subflow. This allows you to pass data to the subflow and initialize its variables2.
• C. After the Call Subflow step executes, you can transfer values of variables from the subflow to the calling flow. This statement is true because you can use the Output Mappings tab of the Call Subflow step to map the variables from the subflow to the variables of the calling flow. This allows you to return data from the subflow and update the variables of the calling flow3.
• D. The same subflow can be invoked from different scripts. This statement is true because a subflow is an independent script that can be reused in other scripts. You can call the same subflow from different scripts using the Call Subflow step and specify the subflow name and location4.

References: 1: Troubleshoot the Subflow - CRS Script - Cisco 2: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.5(1) - Chapter 1: General Steps [Cisco Unified Contact Center Express] - Cisco 3: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.5(1) - Chapter 1: General Steps [Cisco Unified Contact Center Express] - Cisco 4: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.5(1) - Chapter 1: General Steps [Cisco Unified Contact Center Express] - Cisco

The three components that are installed from the Cisco CRS Installer media are the Cisco CRS Engine, the Cisco Recording, and the MS SQL Server. The Cisco CRS Engine is the core component of the Unified CCX system that provides the call processing, scripting, and application integration functions. The Cisco Recording is the component that enables the recording and playback of agent calls for quality monitoring and training purposes. The MS SQL Server is the component that provides the database services for the Unified CCX system, such as storing configuration data, historical data, and agent data. The other components listed are not installed from the Cisco CRS Installer media. The iPlanet Web Server is not used by the Unified CCX system, as it uses the Apache Tomcat Web Server instead. The Cisco IP Telephony Windows 2000 Server OS is not a component of the Unified CCX system, as it uses the Linux-based Cisco Unified Communications Operating System. The Cisco Unified CallManager is not a component of the Unified CCX system, but a separate product that provides the call control and signalingfunctions for the IP telephony network. References := Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 > Module 2: Implementing Cisco Unified Contact Center Express > Lesson 1: Installing Cisco Unified Contact Center Express > Topic 1.1: Cisco Unified CCX Installation Overview1

The customer must purchase 30 outbound IVR ports and 30 agent seats in addition to the 200 Cisco Unified Center Express Premium agent seats. The outbound IVR ports are required to run the outbound IVR campaign, which can make outbound calls to customers and play prerecorded messages or collect customer inputs. The agent seats are required to handle the outbound calls that are transferred to agents based on the customer’s choice or the campaign configuration. The outbound IVR ports and the agent seats are licensed separately and are not included in the Premium agent seats1, page 2-3, 2, page 4-1. References: Solution Design Guide for Cisco Unified Contact Center Express, Release 12.5 (1) SU1, Cisco Unified Contact Center Express Features Guide, Release 12.5 (1)

 Cisco Unified CCX Premium provides the most advanced features and capabilities for contact center agents and supervisors, including IVR scripting, database integration, keystroke macros, CRM integration, outbound preview dialer, and agent email and chat. Cisco Unified CCX Standard and Enhanced do not support keystroke macros, CRM integration, or agent email and chat. Cisco Unified IP IVR does not support agent desktop functions or outbound preview dialer. Cisco Unified CCX Enterprise is not a valid option, as Cisco Unified CCX only comes in Standard, Enhanced, and Premium versions. References: Cisco Unified Contact Center Express 12.5 Data Sheet, [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]

CSQs are associated to the team definition to designate which CSQ information to display on the supervisor desktop. The supervisor desktop allows the supervisor to monitor and manage the agents and the CSQs that are assigned to the team. The supervisor can view the real-time statistics, historical reports, and chat transcripts of the CSQs that are associated to the team. The supervisor can also change the skill competency level of the agents for the CSQs that are associated to the team1, page 2-3, 2, page 2-5, 3, page 2-6. References: Cisco Unified Contact Center Express Features Guide, Release 12.5 (1), Cisco Finesse Supervisor Desktop User Guide for Cisco Unified Contact Center Express, Release 12.5 (1), Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.0 (1)

In a Cisco Unified Contact Center Express deployment with Cisco Unified Communications Manager Express, the embedded browser feature is disabled on the Cisco Agent Desktop. The embedded browser feature allows the agent to view web pages or applications within the Cisco Agent Desktop window, such as customer information, scripts, or web chat. However, this feature requires the Cisco Unified Communications Manager to provide CTI data to the Cisco Agent Desktop, which is not supported by the Cisco Unified Communications Manager Express. Therefore, the embedded browser feature is not available when using Cisco Unified Communications Manager Express as the call control system. References := Cisco Unified Contact Center Express Installation and Upgrade Guide, Release 12.5(1) SU3, Chapter 2: Preinstallation Tasks for Cisco Unified CCX, Cisco Unified Communications Manager Express, page 2-11.

According to the Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Cisco Unified CCX 8.0 can support a maximum of 400 agents when deployed with Cisco Unified Communications Manager. This is the highest capacity option for Cisco Unified CCX 8.0, which requires a dedicated server for the Cisco Unified CCX Engine and a dedicated server for the Cisco Unified CCX Database. The maximum number of agents depends on the hardware configuration, the deployment model, and the features enabled. For example, if Cisco Unified CCX is deployed in a high availability mode, the maximum number of agents is reduced to 300. If Cisco Unified CCX is deployed with Cisco Unified Presence, the maximum number of agents is reduced to 250. If Cisco Unified CCX is deployed with Cisco Unified Intelligence Center, the maximum number of agents is reduced to 150. The maximum number of agents also varies for different versions of Cisco Unified CCX. For example, Cisco Unified CCX 7.0 can support a maximum of 300 agents, while Cisco Unified CCX 9.0 can support a maximum of 500 agents. References: Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 2: Unified CCX Product Overview, Section 2.1: Unified CCX Product Packages, Page 151 Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.1: Unified CCX Deployment Models, Page 252 Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2: Unified CCX Capacity Planning, Page 293

 CTI route points are virtual devices that can receive multiple, simultaneous calls for application-controlled redirection. They are added or configured for Cisco Unified Contact Center Express (UCCX) in the Cisco Unified CallManager Device Configuration. This allows UCCX to integrate with Cisco Unified Communications Manager (CUCM) and use the CTI route points as triggers for UCCX scripts. The CTI route points must be associated with the UCCX application user in CUCM and have the correct partition and calling search space settings. References: CiscoUnified Contact Center Express Getting Started with Scripts, Release 12.5(1) - Configuring Unified CCX Triggers, Cisco Unified Contact Center Express Design Guide, Release 10.0(1) - Deployment Models, CTI Port and CTI Route Point - Cisco Community

The default eMail address in the eMail Subsystem Configuration page is used as the From address in the Send eMail step if no address is specified. This is useful when you want to send emails from a generic or default address without having to specify it in every Send eMail step. The default eMail address can be configured in the Unified CCX Administration web interface, under Subsystems > eMail > eMail Subsystem Configuration. You can also specify the default eMail address in the script editor, using the Set Default eMail Address step. References := Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 > Module 3: Implementing Cisco Unified Contact Center Express Scripting > Lesson 3: Implementing Basic Scripting Techniques > Topic 3.3: Sending an E-mail Message1

Historical reports can be generated using the Historical Reporting Client (HRC) and the Cisco Unified Intelligence Center (CUIC). The HRC is a standalone application that allows supervisors and administrators to view and print reports on historical data from the Unified CCX server. The CUIC is a web-based reporting application that provides real-time and historical reports for Unified CCX. Both tools allow users to create, schedule, and export reports on various aspects of the Unified CCX system, such as agent performance, call statistics, and system health. References:

• Cisco Unified Contact Center Express Reporting Guide, Release 11.6(2), Chapter: Historical Reports
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]2, Module 3: Cisco Unified CCX Reporting, Lesson 1: Cisco Unified CCX Reporting Overview

The correct answer is C. Only agent phones that are used with the Cisco Finesse agent desktop must be associated to the RmCm application user account. The RmCm application user account is a special user account that is created by Cisco Unified Contact Center Express (UCCX) during the initial setup and is used to control and monitor the agent phones through the Computer Telephony Integration (CTI) interface. The RmCm application user account must have the Standard CTI Enabled and Standard CTI Allow Control of Phones supporting Connected Xfer and conf user roles, and must have the agent phones associated as controlled devices. This allows the UCCX to perform actions such as logging in and out agents, changing agent states, making and receiving calls, transferring and conferencing calls, and sending and receiving enterprise data1.

The other options are not correct because:

• A. All phones must be associated to the RmCm application user account. This is false because not all phones need to be controlled and monitored by UCCX. Only the phones that are used by the agents who log in to the Cisco Finesse agent desktop need to be associated to the RmCm application user account. Other phones, such as supervisor phones, IVR phones, or non-UCCX phones, do not need to be associated to the RmCm application user account2.
• B. None, because that user account is not used for phone association. This is false because the RmCm application user account is used for phone association. The RmCm applicationuser account is the user account that UCCX uses to communicate with the Cisco Unified Communications Manager (CUCM) and control the agent phones. Without phone association, the RmCm application user account cannot perform the CTI functions that are required for the UCCX features1.
• D. Only Cisco Finesse IPPA phones must be associated to the RmCm application user account. This is false because Cisco Finesse IPPA phones are not supported by UCCX. Cisco Finesse IPPA is a feature that allows agents to use the Cisco IP Phone Agent (IPPA) service to log in to the Cisco Finesse server and access the Cisco Finesse agent desktop features. However, this feature is only available for Cisco Unified Contact Center Enterprise (UCCE), not for UCCX. UCCX agents can only use the Cisco Finesse agent desktop web interface or the Cisco Agent Desktop (CAD) application to log in and access the UCCX features3.

References: 1: Cisco Unified Contact Center Express Administration Guide, Release 12.5(1) - Cisco Applications Configuration [Cisco Unified Contact Center Express] - Cisco 2: Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5(1) - Unified CCX Deployment Models [Cisco Unified Contact Center Express] - Cisco 3: Cisco Finesse Installation and Upgrade Guide, Release 12.5(1) - Cisco Finesse IPPA [Cisco Finesse] - Cisco

• Heap dumps are snapshots of the Java heap memory that contain information about the objects and classes in the heap at the moment of the dump. Heap dumps can help you identify memory leaks, excessive memory consumption, and other memory-related issues. You can collect heap dumps using the Cisco Unified Real-Time Monitoring Tool (RTMT), which is a client application that allows you to monitor and troubleshoot Cisco Unified CCX components. To collect heap dumps, you need to enable the HeapDumpEnabled service parameter and configure theHeapDumpSchedule parameter. You can then use the RTMT to view and download the heap dumps from the Cisco Unified CCX server2.
• Collect engine heap performance data via the Cisco Unified Real-Time Monitoring Tool. In addition to heap dumps, you can also collect engine heap performance data using the RTMT. This data includes metrics such as heap usage, heap size, garbage collection time, and garbage collection frequency. You can use the RTMT to monitor these metrics in real time or generate historical reports. You can also set alerts and thresholds for these metrics to receive notifications when they exceed the specified values. Collecting engine heap performance data can help you analyze the memory behavior and performance of the Cisco Unified CCX engine3.

References: 1: Cisco Unified Contact Center Express Serviceability Administration Guide, Release 12.5(1) - Control Center [Cisco Unified Contact Center Express] - Cisco 2: Cisco Unified Contact Center ExpressAdministration and Operations Guide, Release 12.5(1) - Troubleshoot Unified CCX [Cisco Unified Contact Center Express] - Cisco 3: Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5(1) - Monitor Unified CCX [Cisco Unified Contact Center Express] - Cisco

The Cisco Unified Communications Sizing Tool is a web-based tool that helps system engineers to size Cisco Unified Communications solutions, including Cisco Unified CCX. The tool can validate various parameters and requirements for a Cisco Unified CCX deployment configuration, such as the number of agents, supervisors, IVR ports, outbound ports, chat sessions, email sessions, and reporting users. However, the tool cannot validate the following options:

• The number of silent-monitoring and remote-monitoring sessions. Silent monitoring and remote monitoring are features that allow supervisors to listen to the agent’s calls without being heard by the agent or the caller. The tool does not support sizing for these features,as they depend on the network bandwidth and the codec used for the calls. The tool only provides a formula to estimate the bandwidth requirement for silent monitoring and remote monitoring, based on the number of sessions, the codec, and the packet size. The formula is: Bandwidth (kbps) = Number of sessions x Codec bit rate x (1 + Network overhead). For example, if there are 10 silent-monitoring sessions using G.711 codec with a bit rate of 64 kbps and a network overhead of 20%, the bandwidth requirement is: Bandwidth (kbps) = 10 x 64 x (1 + 0.2) = 768 kbps1.
• The number of historical reporting sessions. Historical reporting is a feature that allows users to generate reports on the historical data of the Cisco Unified CCX system, such as agent performance, call statistics, and queue summary. The tool does not support sizing for this feature, as it depends on the number of reporting users, the frequency and complexity of the reports, and the database size. The tool only provides some guidelines and best practices for historical reporting, such as limiting the number of concurrent reporting users to 10, scheduling the reports during off-peak hours, and purging the historical data regularly2.
• The number of ASR and TTS ports. ASR (Automatic Speech Recognition) and TTS (Text-To-Speech) are features that enable voice interaction between the callers and the IVR system, using speech recognition and synthesis technologies. The tool does not support sizing for these features, as they are provided by third-party vendors, such as Nuance or LumenVox. The tool only provides some recommendations and considerations for ASR and TTS integration, such as using MRCPv2 protocol, allocating enough CPU and memory resources, and configuring the network QoS policies3.

References: Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2.2: Silent Monitoring and Remote Monitoring, Page 321 Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2.4: Historical Reporting, Page 342 Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2.5: ASR and TTS Integration, Page 353

To run a 30-port outbound IVR campaign, the customer needs to purchase 30 outbound IVR ports and 15 agent seats in addition to the 200 Cisco Unified CCX Premium agent seats. This is because the outbound IVR ports are not included in the Premium package and need to be purchased separately as an add-on component1. The outbound IVR ports are used to dial out to customers and play prompts or transfer calls to agents. The outbound IVR ports are also consumed by the agents who are logged in to the outbound campaign. The ratio of outbound IVR ports to agents is 2:1, which means that for every two outbound IVR ports, one agent seat is required2. Therefore, to run a 30-port outbound IVR campaign, the customer needs 15 agent seats for the outbound agents. The customer does not need to purchase a gateway or a router, as these are network devices that are not related to the outbound IVR campaign. References := Cisco Unified Contact Center Express 12.5 Data Sheet, page4. Outbound Option Guide for Cisco Unified Contact Center Enterprise and Hosted Release 9.0(1), page 2-3.