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

A supervisor who does not have administrative privilege can perform the following Cisco Unified Contact Center Express Application Administration tasks:

• Remove a skill from a CSQ: A skill is a competency that an agent possesses, such as language, product knowledge, or technical expertise. A Contact Service Queue (CSQ) is a logical grouping of agents based on their skills. A supervisor can remove a skill from a CSQ by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Contact Service Queues. For more information on how to remove a skill from a CSQ, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Contact Service Queues.
• Enable automatic work on a CSQ: Automatic work is a feature that allows agents to automatically enter the work state after they finish a call or chat. This prevents the agents from receiving new contacts until they are ready. A supervisor can enable automatic work on a CSQ by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Contact Service Queues. For more information on how to enable automatic work on a CSQ, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Contact Service Queues.
• Modify the skill competence level of an agent: The skill competence level is a numerical rating that indicates the proficiency of an agent in a certain skill. The skill competence level can range from 1 (lowest) to 10 (highest). A supervisor can modify the skill competence level of an agent by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Resources. For more information on how to modify the skill competence level of an agent, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Resources.

The following tasks cannot be performed by a supervisor who does not have administrative privilege:

• Delete a resource group: A resource group is a collection of agents who share common characteristics, such as location, function, or availability. A resource group can be used to organize agents for reporting and administration purposes. Only an administrator can delete a resource group by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Resource Groups. For more information on how to delete a resource group, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Resource Groups.
• Create a resource: A resource is an entity that can handle customer contacts, such as an agent, a supervisor, or an IVR port. A resource can be associated with one or more resource groups, teams, and skills. Only an administrator can create a resource by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Resources. For more information on how to create a resource, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Resources.
• Delete a skill: A skill is a competency that an agent possesses, such as language, product knowledge, or technical expertise. A skill can be assigned to one or more agents and CSQs. Only an administrator can delete a skill by using the Cisco Unified CCX Administration web interface and navigating to Subsystems > RmCm > Skills. For more information on how to delete a skill, see the Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1), Chapter: Unified CCX Application Configuration, Section: Skills. References:
• Cisco Unified Contact Center Express Administration Guide, Release 10.0 (1)
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]5

 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)

 A POD (Point of Data) is a unit of data that is stored in Context Service. A POD can contain information about a customer, an interaction, or any other entity that is relevant to the contact center. A POD can map to a fieldset, which is a collection of fields that define the structure and schema of the POD. A fieldset can have a name, a description, and a list of fields. Each field can have a name, a type, and a value. A POD can belong to only one fieldset, but a fieldset can have multiple PODs1. The runtime connector is not responsible for account and password management, but for registering the contact center components with Context Service and sending and receiving PODs2. Every customer can be mapped to multiple PODs, depending on the number of interactions they have with the contact center3. References:

• 1: Cisco Unified Contact Center Express Features Guide, Release 12.0(1) - Context Service Data Model, Fields, and Fieldsets [Cisco Unified Contact Center Express] - Cisco(https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_12_0/features/guide/uccx_b_features-guide-1201/uccx_b_features-guide-1201_chapter_010.html)
• 2: Cisco Unified Contact Center Express Features Guide, Release 12.0(1) - Component Configuration and Registration [Cisco Unified Contact Center Express] - Cisco(https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_11_6/features/guide/uccx_b_uccx-features-guide/uccx_b_uccx-features-guide_chapter_01.pdf)
• 3: Cisco Unified Contact Center Express Features Guide, Release 12.0(1) - Omnichannel Customer Journey [Cisco Unified Contact Center Express] - Cisco(https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/crs/express_12_0/features/guide/uccx_b_features-guide-1201/uccx_b_features-guide-1201_chapter_010.html)

The database subsystem is used to communicate with external database servers and execute SQL queries from Unified CCX applications. The database subsystem is available only if the system has a license installed for either the Unified IP IVR or Unified CCX Premium product packages. If the database subsystem is not configured, it will show as out of service on the Control Center page of AppAdmin. This means that the database subsystem is not operational and cannot process any requests from the applications. To configure the database subsystem, you need to add database resources and specify the connection parameters for each database server that you want to access from your applications. You also need to enable the database subsystem from the Control Center page after adding the database resources. References: Cisco Unified Contact Center Express Administration Guide, Release 11.5 (1) - Database Subsystem Configuration

 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

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 peripheral variables in the Set Enterprise Call Info step are related to call variables. Call variables are predefined variables that store information about a call, such as the caller ID, the dialed number, the call duration, the call priority, and so on. Call variables are also known as Call.PeripheralVariable1 to Call.PeripheralVariable10, and they can be set or retrieved by the Set Enterprise Call Info step or the Get Enterprise Call Info step. Call variables can be displayed on the agent desktop or used for reporting purposes1, page 2-3, 2, page 2-4, 3, page 4-1. References: Solution Design Guide for Cisco Unified Contact Center Express, Release 12.5 (1) SU1, Cisco Unified Contact Center Express Editor Step Reference Guide, Release 11.6(2), Cisco Unified Contact Center Express Features Guide, Release 12.5 (1)