Cisco 500-052 Exam With Confidence Using Practice Dumps

 The number of premium seats required for a Cisco Unified Contact Center Express system is based on the maximum number of logged in agents plus the number of IVR and email ports needed. In this case, the maximum number of logged in agents is 150, the number of IVR ports needed for outbound calls is 30, and the number of email ports needed for email agents is 20. Therefore, the total number of premium seats required is 150 + 30 + 20 = 180 seats. References: Deploying Cisco Unified Contact Center Express (UCCXD) v6.0 - Module 1: Design a Cisco Unified Contact Center Express System Deployment - Lesson 1: Cisco Unified Contact Center Express Product Overview - Topic: Cisco Unified CCX Product Packages1

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

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