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

 According to the Cisco Unified Contact Center Express Design Guide, Release 8.0(1), the two resource selection criteria that are available for a chat Contact Service Queue are longest available and most skilled. These are the criteria that determine how the chat contacts are routed to the available agents in the chat Contact Service Queue. The longest available criterion selects the agent who has been in the ready state for the longest time, regardless of the skill level. The most skilled criterion selects the agent who has the highest skill competency level for the chat Contact Service Queue, regardless of the ready time. These criteria can help to balance the workload and performance of the chat agents, and to match the chat contacts with the most appropriate agents. The other options are not valid resource selection criteria for a chat Contact Service Queue. Least skilled, most handled contacts, and random are not supported for chat routing, as they are not relevant or optimal for chat interactions. References: Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2.3: Agent Web Chat, Page 33

When Cisco Unified CCX is deployed with Cisco Unified Communications Manager Express (CME), the user management is done through the Application Administration web interface of Cisco Unified CCX. The user data, such as user ID, password, PIN, and roles, are stored in the Cisco Unified CCX database. The user synchronization between Cisco Unified CME and Cisco Unified CCX is done manually by using the Data Synchronization option in the Tools menu of the Application Administration web interface. The user data is not stored in the Cisco Unified CME database, nor is it managed by Cisco Unified CME. References:

• Deploying Cisco Unified Contact Center Express (UCCXD) v6.0
• Cisco Unified Contact Center Express Installation and Upgrade Guide, Release 11.6(1) - Chapter 2: Preinstallation Tasks for Cisco Unified CCX

The CallSubflow step and the Trigger Application step are two Cisco Unified CCX steps that can invoke another Cisco Unified CCX application script. The CallSubflow step allows a script to call another script as a subflow, which can return values to the calling script. The Trigger Application step allows a script to trigger another application by using one of its associated triggers, which can be either a Unified CM Telephony trigger or an HTTP trigger. Both steps can be used to modularize the script logic and reuse existing scripts. References: Cisco Unified Contact Center Express Editor Step Reference Guide, Release 12.0(1) - Call Subflow Step 1 and Trigger Application Step 2

 The importing of contacts into a Cisco Unified Contact Center Express campaign has the following characteristics:

• Phone1 is the only mandatory field. The Phone1 field contains the primary phone number of the contact. The other fields are optional and can be used to store additional information about the contact, such as first name, last name, account number, etc1, page 4-16.
• Up to three custom fields can be added. The custom fields can be used to store any additional data that is not available in the predefined fields. The custom fields can be named and mapped to the corresponding columns in the CSV file1, page 4-17.
• Imports can be automatically executed on a weekly basis. The import schedule can be configured to run the import process at a specified time and frequency. The import frequency can be daily, weekly, or monthly1, page 4-18.

The following statements are incorrect:

• List filtering for “Do Not Call” is unsupported. The list filtering feature allows the administrator to filter out contacts that match certain criteria, such as phone numbers that are on the “Do Not Call” list, duplicate records, or invalid numbers. The list filtering can be enabled or disabled for each campaign1, page 4-19.
• When records have matching phone numbers, only one record is created. The duplicate handling feature allows the administrator to specify how to handle contacts that have the same phone number as an existing contact in the database. The administrator can choose to overwrite the existing contact, skip the new contact, or create a new contact with a different ID1, page 4-20. References: Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.0 (1)

The maximum number of concurrent agent web chat sessions that are supported on the highest class server is 50. This means that each agent can handle up to 50 simultaneous web chat contacts on a server that meets the highest specifications for Cisco Unified Contact Center Express (UCCX). The highest class server for UCCX is the Cisco Unified Computing System (UCS) C240 M5, which supports up to 400 agents and 400 IVR ports1.

The other options are not correct because:

• A. 75 is not the maximum number of concurrent agent web chat sessions that are supported on the highest class server. 75 is the maximum number of concurrent agent web chat sessions that are supported on the second highest class server, which is the Cisco UCS C220 M5. This server supports up to 300 agents and 300 IVR ports1.
• B. 25 is not the maximum number of concurrent agent web chat sessions that are supported on the highest class server. 25 is the maximum number of concurrent agent web chat sessions that are supported on the third highest class server, which is the Cisco UCS C220 M4. This server supports up to 200 agents and 200 IVR ports1.
• D. 120 is not the maximum number of concurrent agent web chat sessions that are supported on the highest class server. 120 is the maximum number of concurrent agent web chat sessions that are supported on the entire UCCX system, regardless of the server class. This means that the total number of web chat contacts across all agents cannot exceed 1202.

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 Features Guide, Release 12.5(1) - Web Chat [Cisco Unified Contact Center Express] - Cisco

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

 Cisco Unified Contact Center Express does not support an embedded Internet browser within the Cisco Agent Desktop. The Cisco Agent Desktop is a legacy desktop application that provides call control and agent state management for Unified CCX agents. The Cisco Agent Desktop does not have an embedded Internet browser, but it can launch an external browser to display web pages or applications. However, the Cisco Agent Desktop is deprecated and replaced by the Cisco Finesse desktop, which is a web-based agent and supervisor desktop that supports an embedded Internet browser. The CiscoFinesse desktop is available for all Unified CCX platform sets, including Standard, Enhanced, and Premium. For more information on the differences between the Cisco Agent Desktop and the Cisco Finesse desktop, see the Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5 (1), Chapter: Cisco Unified CCX Desktop Options, Section: Cisco Agent Desktop and Cisco Finesse Desktop Comparison. References:

• Cisco Unified Contact Center Express Solution Reference Network Design, Release 12.5 (1)
• Cisco 500-052 Free Practice Exam & Test Training - ITExams.com

According to the Cisco Unified Contact Center Express 12.5 Data Sheet1, the maximum number of concurrent chat agents supported by Cisco Unified CCX is 70, regardless of the number of licensed seats. This means that if 70 agents log in as chat agents via an independent browser, they will consume 70 chat agent seats out of the 120 agent seats licensed for the Cisco Unified CCX deployment. The remaining 50 agent seats can be used for voice agents who log in via Cisco Agent Desktop. Therefore, the answer is A. 50. References := Cisco Unified Contact Center Express 12.5 Data Sheet, page 4.

 The application username is not an input that is required when you install Cisco Unified CCX. The application username is the username that you use to log in to the Cisco Unified CCX Administration web interface after the installation is complete. You can configure the application username during the initial system setup, which is a separate step from the installation. The other inputs, such as the platform administrator username, the IP address, the default language, and the time zone, are required during the installation process. You need to enter these inputs to configure the basic system parameters and network settings for the Unified CCX server. References := Cisco Unified Contact Center Express Install and Upgrade Guide, Release 12.5(1) SU2, Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 Course Outline

To send an HTTP message, you should use the following Cisco Unified CCX steps:

• Send HTTP Response: This step allows the script to send an HTTP response to the client that initiated the HTTP request. The step specifies the HTTP status code, the content type, and the body of the response. The step can also set or delete cookies in the response. For more information on how to use the Send HTTP Response step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Send HTTP Response Step.
• Create URL Document: This step allows the script to create a URL document that contains the URL of a web page or application. The step specifies the URL, the method (GET or POST), and the parameters to be sent with the request. The step can also set or delete cookies in the request. The URL document can be used as an input for other steps, such as Write Document or Place Call. For more information on how to use the Create URL Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Create URL Document Step.

The following steps cannot be used to send an HTTP message:

• Write Document: This step allows the script to write a document to a file or a stream. The step specifies the document, the destination, and the encoding. The document can be any type of document, such as XML, plain text, or URL. The destination can be a local file, a remote file, or a media stream. The step can be used to write a URL document to a file or a stream, but it cannot send an HTTP message by itself. For more information on how to use the Write Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Write Document Step.
• Place Call: This step allows the script to place a call to a destination. The step specifies the calling address, the called address, the media termination, and the timeout. The calling address and the called address can be phone numbers, SIP URIs, or URL documents. The media termination can be a contact, a prompt, or a document. The step can be used to place a call to a URL document, but it cannot send an HTTP message by itself. For more information on how to use the Place Call step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Place Call Step.
• Cache Document: This step allows the script to cache a document in the memory of the Unified CCX server. The step specifies the document and the cache key. The document can be any type of document, such as XML, plain text, or URL. The cache key is a unique identifier for the document in the cache. The step can be used to cache a URL document, but it cannot send an HTTP message by itself. For more information on how to use the Cache Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Cache Document Step. References:
• Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1)
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]2, Module 2: Cisco Unified CCX Scripting, Lesson 3: Cisco Unified CCX Scripting Steps, Topic: HTTP Contact Steps

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)

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

The gadget to initiate or accept a call is common and is not tied to a specific tab on the Cisco Finesse agent desktop. The gadget is located in the call control area, which is a fixed section of the Finesse desktop that appears on every tab. The gadget provides the basic call control buttons, such as Answer, Hold, Retrieve, End, and Make Call. The gadget also displays the caller ID, the call state, and the call timer. The gadget changes depending on the situation and the call type. For example, the gadget shows different buttons for inbound, outbound, and consult calls12

The other options are not correct:

• The My Statistics tab hosts the gadget that shows the agent’s performance statistics, such as the number of calls handled, the average talk time, the average wrap-up time, and the service level12
• The Home tab hosts the gadget that shows the agent’s state, the reason code, and the state timer. The Home tab also allows the agent to change their state, sign out, or go to the Team Performance tab12
• The Manage Customer tab hosts the gadget that shows the customer information, such as the account number, the name, the address, and the call history. The Manage Customer tab also allows the agent to perform advanced call control actions, such as consult, transfer, and conference12

References: 1: Cisco Finesse Agent and Supervisor Desktop User Guide Release 12.0(1) - Cisco Finesse Desktop Interface [Cisco Finesse] - Cisco 1 2: How IT Works: Cisco Finesse Agent Desktop and UCCX | Mindsight 2

 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 trace configuration interface is used to configure debug parameters for log files in Cisco Unified Contact Center Express (UCCX). This interface allows the administrator to set the trace level, trace output, and trace file size for different UCCX components and services. The trace configuration interface can be accessed from the UCCX Serviceability web page by selectingTrace > Configuration from the menu. The trace configuration interface also provides the option to view the current trace settings and download the trace files for troubleshooting purposes. References: Cisco Unified Contact Center Express Administration and Operations Guide, Release 12.5 (1) SU3 - Cisco Unified CCX Serviceability, Use CLI to Collect Unified Contact Center Express Logs - Cisco

The option that enables you to monitor previous agent seat license usage is port and agent seat utilization historical report in Cisco Unified Intelligence Center. This report provides information about the number of agent seats and IVR ports that are in use for a specified time period. You can use this report to track the peak and average utilization of agent seats and IVR ports, and compare them with the licensed capacity. You can also filter the report by node, license package, and date range.

The other options are not correct because:

• traffic analysis historical report provides information about the call traffic and service level for each CSQ and application. It does not show the agent seat license usage.
• port-monitoring tool in Cisco Unified Communications Manager Real-Time Monitoring Tool allows you to monitor the status and statistics of the voice gateway ports that are registered with Cisco Unified Communications Manager. It does not show the agent seat license usage.
• overall Cisco Unified CCX stats in Cisco Unified Communications Manager Real-Time Monitoring Tool shows the overall status and performance of the Cisco Unified CCX system, such as the number of active calls, agents, sessions, triggers, and chat contacts. It does not show the previous agent seat license usage.

References: : [Cisco Unified Intelligence Center Report Customization Guide, Release 12.5(1) - Unified CCX Historical Reports [Cisco Unified Contact Center Express] - Cisco] : [Cisco Unified Contact Center Express Historical Reports User Guide, Release 12.5(1) - Chapter 4: Unified CCX Historical Reports [Cisco Unified Contact Center Express] - Cisco] : [Cisco Unified Serviceability Administration Guide, Release 12.5(1)SU3 - Real-Time Monitoring Tool [Cisco Unified Communications Manager (CallManager)] - Cisco] : [Cisco Unified Contact Center ExpressAdministration 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

The Cisco Unified CCX Installer media is used to install the following components on the Unified CCX server:

• Cisco Unified CCX Engine: This is the core component that provides the call control, routing, and scripting functionality for Unified CCX. It also includes the Cisco Unified CCX Administration web interface, the Cisco Unified CCX Serviceability web interface, the Cisco Unified CCX Editor, and the Cisco Unified CCX Historical Reports client.
• Recording Component: This is an optional component that enables the recording and playback of agent calls. It also includes the Cisco Unified CCX Supervisor Desktop and the Cisco Unified CCX Agent Desktop applications.
• Informix DB: This is the database component that stores the configuration and historical data for Unified CCX. It also includes the Cisco Unified CCX Database Schema and the Cisco Unified CCX Database Monitor Service.

The following components are not installed from the Cisco Unified CCX Installer media:

• iPlanet Web Server: This is a web server that is not used by Unified CCX. Unified CCX uses the Apache Tomcat web server, which is installed as part of the Cisco Unified Communications Operating System.
• Cisco Unified Operations Manager: This is a network management application that monitors the health and performance of Cisco Unified Communications systems. It is not part of Unified CCX and requires a separate installation and license.
• Cisco Unified Communications Manager: This is the call processing component that provides the IP telephony services for Unified CCX. It is not part of Unified CCX and requires a separate installation and license.

References:

• Cisco Unified Contact Center Express Install and Upgrade Guide, Release 12.5(1), Chapter 1: Unified CCX Installation
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0], Module 1: Cisco Unified Contact Center Express Overview

According to the Cisco Unified Contact Center Express Design Guide, Release 8.0(1), the maximum number of agent web chat sessions that is supported on the highest class server is 50. This means that a single agent can handle up to 50 concurrent web chat sessions on a server that meets the highest hardware specifications for Cisco Unified CCX 8.0. The highest class server for Cisco Unified CCX 8.0 is the MCS 7845, which has the following hardware configuration:

• Processor: Two quad-core Intel Xeon E5440 2.83-GHz processors
• Memory: 12 GB RAM
• Hard disk: Four 146-GB SAS hard disks

The maximum number of agent web chat sessions 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 agent web chat sessions is reduced to 25. If Cisco Unified CCX is deployed with Cisco Unified Presence, the maximum number of agent web chat sessions is reduced to 20. If Cisco Unified CCX is deployed with Cisco Unified Intelligence Center, the maximum number of agent web chat sessions is reduced to 10. The maximum number of agent web chat sessions also varies for different versions of Cisco Unified CCX. For example, Cisco Unified CCX 7.0 can support a maximum of 25 agent web chat sessions, while Cisco Unified CCX 9.0 can support a maximum of 60 agent web chat sessions. References: Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.2.3: Agent Web Chat, Page 331 Cisco Unified Contact Center Express Design Guide, Release 8.0(1), Chapter 3: Unified CCX Architecture and Capacity Planning, Section 3.3: Unified CCX Hardware Configuration, Page 372

he gateway is the option that can perform Call Progress Analysis (CPA) in outbound IVR. CPA is a DSP algorithm that analyzes the RTP voice stream to look for special information tones (SIT), fax or modem tones, human speech, and answering machine tones. CPA also passes the voice information to Cisco IOS or CUBE. CPA is initiated on receiving a new SIP INVITE with x-cisco-cpa content. The gateway detects non-live contact with its CPA capabilities and sends the status of the non-live contact to the dialer. The dialer then decides whether to redirect the call to UCCX or terminate the call based on the CPA event. References: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Call Progress Analysis, IVR-Based Outbound Dialer Troubleshooting

The Cisco Unified CCX Installer automatically installs the IVR System Prompts and the Unified Communications Operating System on the Cisco Unified CCX server. The IVR System Prompts are the default voice prompts that are used by the Unified CCX applications, such as the Script Editor and the Cisco Unified CCX Editor. The Unified Communications Operating System is the platform software that provides the basic functionality and security for the Unified CCX server, such as the CLI, the web interface, the database, and the license management. The Cisco Supervisor Desktop, the Cisco Unified Communications Manager, and the Workforce Management are not installed by the Cisco Unified CCX Installer. The Cisco Supervisor Desktop is a separate application that can be installed on a client PC to monitor and manage the Unified CCX agents. The Cisco Unified Communications Manager is a separate server that provides call control and signaling for the Unified CCX system. The Workforce Management is an optional component that can be purchased and installed separately to provide scheduling and forecasting capabilities for the Unified CCX agents. References := Cisco Unified Contact Center Express Install and Upgrade Guide, Release 12.5(1), Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 Course Outline

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.

The security password is used as the secret key during the second node installation of Cisco Unified Contact Center Express (UCCX). This password is entered during the first node installation and must be the same for all nodes in the cluster. The security password is used to encrypt sensitive data in the database and to authenticate communication between nodes. If the security password is not the same for all nodes, the installation will fail and the cluster will not function properly. References: Cisco Unified Contact Center Express Install and Upgrade Guide, Release 12.5 (1) - Unified CCX Installation, Free Cisco Deploying Unified Contact Center Express (UCCXD) v6.0 Certification Sample Questions and Answers

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)