500-052 Exam Dumps : Deploying Cisco Unified Contact Center Express

 Control Center on Cisco Unified Contact Center Express Serviceability Comprehensive and Detailed Explanation: The Control Center on Cisco Unified Contact Center Express Serviceability is a web-based interface that allows you to start, stop, and restart Cisco Unified CCX services. You can also view the status of each service and the server on which it is running. The Control Center is accessible from the Navigation drop-down list on the Cisco Unified CCX Serviceability page. You can select either Network Services or Feature Services to manage the corresponding services. References: Cisco Unified Contact Center Express Operations Guide, Release 11.5 (1) - Cisco Unified CCX Serviceability1, Serviceability Tools1

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 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