Free Cisco 500-444 Practice Exam with Questions & Answers

Certificate Authority (CA) signed certificates are less administration in environments with many servers, such as CCE, because they are issued by a trusted third-party entity that validates the identity of the certificate owner and provides a chain of trust. CA signed certificates are more secure and reliable than self-signed certificates, which are generated by the same entity whose identity they certify and are not verified by anyone else. Self-signed certificates require manual installation and configuration on each server and client that needs to communicate with them, which can be tedious and error-prone. 3rd party signed certificates are similar to CA signed certificates, but they are issued by a commercial entity that may charge a fee for their services. Security Authority (SA) is not a valid term for a certificate issuer. References: 1, 2, 3

 Device Management Protocol (DMP) is a protocol used between ICM Central Controller and IVR/CUCM PGs. It is used to send commands, such as to bring up a voice channel, to the PGs. OCTI, SIP, and ccagent are not protocols used between ICM Central Controller and IVR/CUCM PGs.

References: 500-444-demo, page 4.

 If Cisco Unified ICM sends back a label of 91919191, the caller will hear ringing. This is because 91919191 is a special label that is used by Cisco Unified Customer Voice Portal (CVP) to play a ringtone to the caller while the call is being transferred to an agent or another destination1. The ringtone is a WAV file that is stored on the media server and is configured on the CVP Operations Console and the VXML gateway1. The label 91919191 is matched by a dial-peer on the VXML gateway that invokes a ringtone service and sends the ringback.wav file to the ingress voice gateway2. The caller will hear the ringtone until the call is connected or disconnected1.

References: Configuration Guide for Cisco Unified Customer Voice Portal, Release 11.6(1) - Unified ICM Configuration [Cisco Unified Customer Voice Portal] - Cisco1, Distributed Voice and VXML Gateway Design with CVP SIP - Cisco Community2

There are two types of upgrades available for CCE: Common Ground and Standard. A Common Ground upgrade is a type of upgrade that allows you to upgrade from one major release to another major release without having to rebuild your configuration. A Common Ground upgrade preserves your existing configuration and data, and applies the new features and enhancements of the new release. A Common Ground upgrade is supported for certain releases and deployment models, and requires a specific upgrade path. A Standard upgrade is a type of upgrade that allows you to upgrade from one minor release to another minor release within the same major release. A Standard upgrade also preserves your existing configuration and data, and applies the bug fixes and minor enhancements of the new release. A Standard upgrade is supported for all releases and deployment models, and does not require a specific upgrade path12. References:

• Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.6 (1) - Upgrade Overview2
• Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5 (1) and 12.5 (2) - Upgrade Overview3

The Active and Configured CUIC Users for the 2K deployment model are 200 and 800 respectively. This means that the CUIC server can support up to 200 concurrent users and up to 800 configured users. A concurrent user is a user who is logged in to CUIC and actively using the application. A configured user is a user who has an account in CUIC, regardless of whether they are logged in or not. The 2K deployment model is one of the UCCE deployment types that defines the maximum number of agents, supervisors, and reporting users that can be supported by the system. The 2K deployment model can support up to 2000 agents, 200 supervisors, and 200 CUIC concurrent users12. References:

• Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5 (1) and 12.5 (2) - CLI Commands during Installation and Upgrade 2
• Cisco 500-444 Quiz 1 Topic 8 Questions 1-5 1

The service that must be restarted after modifying the Java Keystore on the CVP servers is the Cisco CVP WebServicesManager. The Cisco CVP WebServicesManager is a service that provides web services for the CVP components, such as the Operations Console, the Reporting Server, and the Call Server. The Java Keystore is a file that stores the certificates and keys for secure communication between the CVP components and other systems. If the Java Keystore is modified, the Cisco CVP WebServicesManager service must be restarted to apply the changes and ensure the proper functioning of the web services12.

References:

• Configure Secure Java Management Extensions (JMX) Communication on CVP3
• User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 11.5 (1) - Rest_Client Integration2

When an agent transfers a call to another ICM Skill Group, the call should be transferred to a CTI route point that is associated with a routing client and a dialed number in the ICM configuration. This way, the ICM can route the call to the appropriate agent based on the skill group and the call context. The ICM can also maintain the end-to-end reporting context for the call, such as the original call type, the transfer reason, the transfer time, and the transfer destination. If the call is transferred to an agent IP phone, a route pattern, or a translation pattern, the ICM will lose the visibility and control of the call, and the reporting context will be broken.

References: Troubleshooting Cisco Contact Center Enterprise (CCET) course, Module 3: Troubleshooting Call Flows, Lesson 3: Troubleshooting Transfers12

The 2K deployment model for Cisco Contact Center Enterprise (CCE) is a prepackaged solution that offers a simplified and scalable architecture for medium-sized contact centers. The 2K deployment model supports up to 2,000 active agents and up to 8,000 configured agents. An active agent is an agent who is logged in and ready to take calls. A configured agent is an agent who has a profile in the system, regardless of their login status. The 2K deployment model also supports up to 4,000 IVR ports, up to 120,000 BHCA, and up to 12,000 concurrent calls1.

References:

1: Cisco Packaged Contact Center Enterprise Solution Reference Network Design (SRND), page 2-3

 The readiness for the CCE deployment can be verified in the CCE Web Admin -> Infrastructure - Inventory page. This page shows the list of machines that are part of the CCE deployment, including their roles, IP addresses, hostnames, and status. The status indicates whether the machine is online, offline, or in maintenance mode. The inventory page also allows adding, editing, or deleting machines from the system inventory. To access the inventory page, follow these steps:

• From your desktop, double-click the Unified CCE Tools icon, and then select Administration Tools.
• Double-click the CCE Web Administration link.
• In the Unified CCE Administration, navigate to Overview > Infrastructure Settings, click Inventory.

References :=

• Web Based CCE Administration12
• Cisco Packaged Contact Center Enterprise Administration and Configuration Guide3
• CCE Web Administration, add AW to System Inventory4

 Cisco Unified Border Element (CUBE) is a session border controller that provides session control, security, interworking, and demarcation for voice and video calls between the enterprise IP network and service provider SIP trunks1. When CUBE is used with CCE and CVP, it provides the following three features:

• Silent Monitor inbound voice calls: CUBE supports the silent monitoring feature for inbound voice calls from the PSTN to the CCE agents. This feature allows supervisors to listen to the agent-customer conversations without being noticed by either party. CUBE uses the built-in-bridge (BIB) capability of the agent phone to fork the media stream and send it to the monitoring server2.
• Secure communication using flow around mode: CUBE supports secure communication using Transport Layer Security (TLS) and Secure Real-Time Transport Protocol (SRTP) for SIP signaling and media streams. CUBE can operate in flow around mode, where it terminates the TLS/SRTP sessions from the service provider and the enterprise, but does not perform any media processing or transcoding. This mode reduces the CPU load on CUBE and preserves the end-to-end media encryption3.
• Normalize SIP messages using SIP profiles: CUBE supports SIP normalization using SIP profiles, which are collections of parameters that modify the SIP messages that pass through CUBE. SIP profiles can be used to resolve interoperability issues between different SIP implementations, such as service providers, CVP, and CCE. SIP profiles can also be used to enhance the functionality of CUBE, such as adding or removing headers, modifying timers, and enabling features4.

References: Cisco Unified Border Element data sheet1, Cisco Unified Border Element Configuration Guide234.