500-444 Exam Dumps - Cisco CCEIT Questions and Answers

UC on UCS Spec Based is a deployment option for Cisco Unified Communications (UC) applications on Cisco Unified Computing System (UCS) servers that allows customers to choose their own hardware configuration based on a set of rules and guidelines1. The two descriptions that apply to UC on UCS Spec Based are:

• A: may be available as a packaged offer such as the Cisco Business Edition 7000 Platform. This is true because Cisco Business Edition 7000 (BE7000) is a packaged solution that includes a UCS server and preloaded UC applications that can be configured according to the customer’s needs. The UCS server can be either a Tested Reference Configuration (TRC) or a Specs-based configuration, depending on the customer’s preference and requirements2.
• C: defined as Rule Based. This is true because UC on UCS Specs-based deployments follow a set of rules and guidelines that define the minimum and maximum hardware specifications, such as CPU, memory, disk, network, and power supply, that are required to support the UC applications. The rules and guidelines also specify the supported virtualization software versions, co-residency policies, and performance expectations1.

The other options are incorrect because:

• B: VMware vCenter is required. This is false because VMware vCenter is not mandatory for UC on UCS Specs-based deployments, although it is recommended for managing multiple UCS servers and VMs. VMware vCenter is only required for certain UC applications, such as Cisco Unified Contact Center Enterprise (CCE) and Cisco Unified Intelligence Center (CUIC), or for certain features, such as VMware High Availability (HA) and VMware Distributed Resource Scheduler (DRS)13.
• D: defined as Configuration Based. This is false because UC on UCS Specs-based deployments are not defined by a fixed hardware configuration, but rather by a range of hardware specifications that can be customized by the customer. Configuration Based is a term that applies to UC on UCS TRC deployments, which are predefined and validated hardware configurations that are supported by Cisco1.
• E: VMware vSphere is optional. This is false because VMware vSphere is the only supported virtualization software for UC on UCS Specs-based deployments. VMware vSphere includes the VMware ESXi hypervisor and the VMware vCenter Server, which provide the virtualization platform and management tools for the UC applications. VMware vSphere is not optional, but rather mandatory for UC on UCS Specs-based deployments1.

References:

1: Cisco Collaboration Virtualization - Unified Communications in a Virtualized Environment 2: Cisco Business Edition 7000 Version 12.5 Ordering Guide 3: Cisco Collaboration Virtualization - VMware Requirements

A voice gateway (VGW) is a device that connects a traditional telephony network, such as a TDM trunk, to a voice over IP (VoIP) network, such as a Cisco Unified Communications Manager (CUCM) cluster. A VGW performs signaling and media conversion between the two networks, and can also provide supplementary services, such as call routing, digit manipulation, transcoding, conferencing, and fax relay. A VGW can be a standalone device, such as a Cisco Integrated Services Router (ISR), or a software module, such as a Cisco Unified Border Element (CUBE). A CUBE is a special type of VGW that can also provide security, demarcation, and interworking functions for VoIP calls. A CUBE can be deployed between two VoIP networks, such as CUCM and a service provider SIP trunk, or between a TDM trunk and a VoIP network, in which case it acts as both a CUBE and a VGW. A CUCM is not a VGW, but a call control platform that manages VoIP endpoints, such as IP phones, and interacts with VGWs for call routing and signaling. A CUSP is a Cisco Unified SIP Proxy, which is a device that provides SIP routing and load balancing for VoIP networks. A CUSP is not a VGW, but a SIP proxy server that can work with CUCM and CUBE to optimize SIP call flows. References:

• Troubleshooting Cisco Contact Center Enterprise (CCET), Module 1: Voice Gateway Overview1
• Cisco Contact Center Enterprise Implementation and Troubleshooting (CCEIT), Module 2: Voice Gateway Configuration2
• Cisco Unified Border Element Configuration Guide3
• Cisco Unified SIP Proxy Configuration Guide4

 The URL for the VOS O/S admin page is https:// :8443/osadmin. VOS O/S admin is a web-based tool that allows you to perform various administrative tasks on the Unified CCE servers, such as managing users, certificates, services, network settings, backups, and upgrades. VOS O/S admin requires the fully qualified domain name (FQDN) of the server and the port number 8443 to access the login page. The other options are not valid URLs for the VOS O/S admin page12. References: Cisco Unified Contact Center Enterprise Installation and Upgrade Guide, Release 12.5(1)1, Cisco Unified Contact Center Enterprise Administration Guide, Release 12.5(1)2.

External voice DNs are sourced from CUCM in a CCE Dial Plan. External voice DNs are the DNs that are not associated with any CCE device, such as agent phones, VRU peripherals, or gateways. They are used to route calls to destinations outside the CCE network, such as PSTN numbers, voicemail, or other PBXs. CUCM is responsible for provisioning and managing these DNs and assigning them to the appropriate devices or trunks. CVP can also use external voice DNs to send calls to CUCM for further routing or treatment.

References:

• Troubleshooting Cisco Contact Center Enterprise (CCET) course, Module 3: Troubleshooting Call Flow Issues, Lesson 3.1: Troubleshooting CCE Call Flows, Topic: CCE Dial Plan1
• Configuration Guide for Cisco Unified Customer Voice Portal, Release 12.6 (1) - System Configuration [Cisco Unified Customer Voice Portal] - Cisco, Chapter: Dialed Number Pattern Configuration2

Cisco VOS is a Linux-based operating system that runs on Cisco Unified Communications servers. It provides a common platform for various Cisco applications, such as Finesse, CUIC, CVP, and ECE. Finesse is a web-based agent and supervisor desktop solution that integrates with Cisco Unified Contact Center Enterprise (CCE) and Customer Voice Portal (CVP). CUIC is a web-based reporting and analytics solution that provides real-time and historical data for Cisco Unified CCE and CVP. CVP is a software-based solution that provides call control, voice self-service, and outbound dialing capabilities. ECE is an email and chat solution that integrates with Cisco Unified CCE and Finesse.

References:

• Cisco VOS System Administration - Certificate Management1
• Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 12.6 (2) - Prepare Customer Site Servers2
• Troubleshooting Cisco Contact Center Enterprise (CCET) Course Outline

A certificate authority (CA) is a trusted entity that issues digital certificates for websites and other entities. CAs validate a website domain and, depending on the type of certificate, the ownership of the website, and then issue TLS/SSL certificates that are trusted by web browsers like Chrome, Safari and Firefox. Thus, CAs help keep the internet a safer place by verifying websites and other entities to enable more trust in online communications and transactions. Some of the roles of a CA in a trusted third-party CA certificate are:

• To provide validation of certificate requests: A CA verifies the identity and authenticity of the certificate requester before issuing a certificate. The CA may use different methods of validation, such as domain validation, organization validation, or extended validation, depending on the type and level of assurance of the certificate. The CA may also check the revocation status of the certificate or the certificate chain to ensure that the certificate is not expired or revoked.
• To issue a CA signed Identity certificates: A CA signs the certificate with its own private key, which attests to the validity and integrity of the certificate. The CA also provides the certificate with a serial number, a validity period, and other attributes. The CA signed certificate can be used by the certificate holder to prove its identity and establish secure connections with other parties.

References:

• What is a CA? Certificate Authorities Explained
• The Role of Certificate Authorities
• The 5 most frequently Asked Questions about Certificate Authority (CA)

 To use microapps in Cisco Unified CVP Comprehensive mode, the following core components are required12:

• CUCM: CTI Route Point and SIP Trunk. The CTI Route Point is used to trigger the ICM routing script when a call arrives at CUCM. The SIP Trunk is used to send the call to CVP for further treatment by the ICM script1.
• ICM: CVP Type 2 VRU and Network VRU labels. The CVP Type 2 VRU is a configuration option in ICM that allows the ICM script to send instructions to CVP using microapps. The Network VRU labels are used to route the call from CUCM to CVP via the SIP Trunk1.
• VXML Gateway: The VXML Gateway is used to execute the microapps that are sent by the ICM script. The VXML Gateway communicates with CVP using HTTP and plays the media files that are stored on the CVP Media Server1.

Option A is incorrect because it uses CTI Route Port instead of CTI Route Point, and it includes CUBE, which is not required for microapps. Option C is incorrect because it uses CTI Route Port instead of CTI Route Point, and it uses CVP Type 10 VRU, which is not supported for microapps. Option D is incorrect because it uses CVP Type 10 VRU, which is not supported for microapps1.

References:

• 1: Troubleshooting Cisco Contact Center Enterprise (CCET) course, Module 3: CVP Microapps3
• 2: Cisco Contact Center Enterprise Implementation and Troubleshooting (CCEIT) exam description1

 A push sync is triggered when an administrator performs any create, update, or delete operation on a specific configuration item. A push sync sends the configuration changes to all the nodes in the PCCE deployment. A push sync is also triggered when an administrator adds or removes a node from the deployment.

References:

• Troubleshooting Cisco Contact Center Enterprise (CCET), page 2-9
• Implementing Cisco Contact Center Enterprise (CCEI), page 2-10

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/pcce/pcce_12_5_1/release/guide/pcce_b_1251_pcce-release-notes/pcce_b_1251_pcce-release-notes_chapter_010.pdf

 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.