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

Answer: D

The PCCE wizard uses the Service Account login for logins to access the appropriate server and enable interfaces, databases, and protocols. The Service Account login is an existing Active Directory user in the same domain as the Packaged CCE servers. This account is added to the Service group during the initialization of the Packaged CCE deployment type. The Service Account login has the required permissions to access the SQL Server, the Organizational Units, and the Security Groups for the Packaged CCE components.

References:

• Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.6 (1) - Initialize the Packaged CCE 2000 Agents Deployment Type1
• Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 12.0 (1) - Configure PCCE Local Authorization2

Microapps are small applications that run on the CVP server and provide interactive voice response (IVR) functionality. They can play prompts, collect digits, perform database lookups, and transfer calls. Microapps are defined and configured using PCCE Web Administration Manager (S.P.O.G) under the Call Settings -> IVR Settings -> Network VRU Scripts menu. Here, you can create, modify, or delete network VRU scripts that reference the microapps and specify the parameters for each microapp. You can also associate the network VRU scripts with call types and dialed numbers to invoke them in the call flow12. References: Troubleshooting Cisco Contact Center Enterprise (CCET) course outline1, Contact Center Enterprise Troubleshooting and Configuration document2.

Answer: B

The sync job that runs every 10 minutes to bring back the OUT_OF_SYNC machine to the IN_SYNC state is the Automated differential sync job. This sync job compares the configuration of the Packaged CCE components on the primary and secondary nodes and applies the changes to the secondary node if there is any difference. The Automated differential sync job is enabled by default and runs every 10 minutes. It can also be triggered manually from the SPOG UI12.

References:

• Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.0 (1) - Synchronize the Configuration1
• Troubleshoot CVP on SPOG that Shows Out of Sync - Cisco3

A SIP proxy server is a component of a SIP network that handles the setup and termination of calls between SIP devices. It also performs functions such as registration, authorization, network access control, and network security. Some of the functions of a SIP proxy server are:

• Centralizes dial plans: A SIP proxy server can centralize the dial plans for a SIP network, meaning that it can translate and route calls based on a unified set of rules and policies. This simplifies the administration and management of the SIP network and ensures consistent call routing across different devices and locations.
• Helps to centralize the administration and call control: A SIP proxy server can also help to centralize the administration and call control of a SIP network, meaning that it can provide a single point of contact and configuration for all the SIP devices and endpoints. This reduces the complexity and overhead of maintaining multiple SIP servers and devices and allows for easier monitoring and troubleshooting of the SIP network.

References:

• 1: What Is a SIP Proxy? How Does a SIP Server Work? - Nextiva
• 2: What is a SIP Proxy Server and How Does It Work? - ULTATEL Blog
• 3: What is SIP proxy? | Webopedia
• 4: Definition of SIP proxy | PCMag
• 5: All About SIP Proxy: What is a SIP Server? | TelNet Worldwide

= UC on UCS Tested Reference Configuration (TRC) is a type of deployment option for Cisco Unified Communications applications on Cisco Unified Computing System (UCS) servers. TRC is defined as Configuration Based, which means that it specifies the exact hardware configuration, including server model, CPU, memory, disk, RAID settings, BIOS settings, and network adapters. TRC also requires VMware vSphere as the virtualization software, and does not support any other hypervisor. VMware vCenter is not required for TRC, but it is recommended for managing multiple ESXi hosts. TRC is different from Specs-based, which is defined as Rule Based, and allows more flexibility in choosing the hardware components, as long as they meet the minimum requirements and follow the rules defined by Cisco. Specs-based also supports other hypervisors besides VMware vSphere, such as Microsoft Hyper-V and KVM. References :=

• Troubleshoot UC on UCS TRC, UC on UCS Specs-based, and 3rd-party Specs-based Deployments1
• Collaboration Virtualization Sizing2
• Unified Computing System Hardware3
• What to select - Cisco BE6000 or UC-on-UCS45

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

The Single Pane of Glass (SPOG) is the web-based administrative interface that should be deployed to provide a unified and simplified view of the Unified CCE system, even though Unified CCE provides Configuration Manager as the legacy User Interface for administrators1. The SPOG is also known as the CCE Web Administration or the Unified CCE Administration console, and it allows administrators to configure and manage various Unified CCE features and settings, such as agents, attributes, precision queues, bucket intervals, media routing domains, license, bulk jobs, deployment type, system information, single sign-on, context service, and contact center AI23.

The other options are incorrect because:

• A: WebSetup is not a web-based administrative interface, but rather a tool that is used to install and configure the web setup components, such as the web setup database, the web setup service, and the web setup client, on the Unified CCE servers. WebSetup is used to perform initial configuration tasks, such as setting the deployment type, the instance name, the security mode, the license server, and the LDAP directory4.
• B: Contact Centre Management Portal (CCMP) is not a web-based administrative interface for Unified CCE, but rather a separate product that provides a web-based interface for managing Cisco Unified Contact Center Express (UCCX) and Cisco Unified IP Interactive Voice Response (IP IVR) systems. CCMP allows administrators to perform tasks such as creating and modifying scripts, applications, triggers, teams, skills, and CSQs, as well as monitoring and reporting on the system performance and agent activity5.
• C: LDAP Plugin is not a web-based administrative interface, but rather a component that enables Unified CCE to integrate with an external LDAP directory, such as Microsoft Active Directory, for user authentication and authorization. LDAP Plugin allows Unified CCE to synchronize user data from the LDAP directory and assign roles and permissions to the users based on their LDAP group membership2.

References:

1: UCCE 10.5 Web Admin Interface - Cisco Community 2: Administration Guide for Cisco Unified Contact Center Enterprise, Release 12.6 (1) - Web Based CCE Administration [Cisco Unified Contact Center Enterprise] - Cisco 4: Web Setup Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.6(1) - Web Setup Overview [Cisco Unified Contact Center Enterprise] - Cisco 5: [Cisco Unified Contact Center Management Portal Data Sheet - Cisco] 3: Web Based CCE Administration - Cisco 6: Web Setup Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.6(1) - Web Setup Overview [Cisco Unified Contact Center Enterprise] - Cisco : Cisco Unified Contact Center Management Portal Data Sheet - Cisco

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1151/Admin/guide/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151_chapter_01001.pdf

Cisco Finesse primary and secondary servers accept both self-signed certificates and certificate authority certificates when HTTPS protocol is used to access the administration console or agent desktop in Cisco Finesse. A self-signed certificate is a certificate that is generated by the server itself and is not verified by a trusted third-party. A certificate authority certificate is a certificate that is issued by a trusted third-party vendor and is used to establish a secure connection between the server and the client. Cisco Finesse supports both types of certificates for HTTPS connections, but recommends using certificate authority certificates for better security and compatibility. Domain validation certificates, digital certificates, and root certificates are not valid options for this question. A domain validation certificate is a type of certificate authority certificate that only verifies the ownership of the domain name, but not the identity of the organization. A digital certificate is a general term that refers to any certificate that uses public key cryptography to authenticate the identity of the sender and the integrity of the data. A root certificate is a certificate that is used to validate other certificates in a chain of trust, but it is not directly used for HTTPS connections. References: Cisco Finesse Administration Guide, Release 12.6 (2) - Getting Started [Cisco Finesse] - Cisco1, Solved: Finesse Certificate Issue - Cisco Community2, Cisco Finesse Administration Guide Release 11.6(1)3, Cisco Finesse Administration Guide, Release 12.0 (1)4, Cisco Finesse Administration Guide, Release 12.6 (1)5

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1151/Admin/guide/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151/CFIN_BK_C0CD262D_00_cisco-finesse-administration-guide-1151_chapter_01001.pdf

Two upgrades for Common Ground are includes migration of windows registry and includes database migration. Common Ground is a type of upgrade that allows you to upgrade your Cisco Unified Contact Center Enterprise (CCE) components from one release to another without changing the hardware or operating system1. Common Ground upgrade is supported for virtualized deployments on VMware ESXi hosts1. Common Ground upgrade involves the following steps1:

• Back up the existing configuration and data using the Disaster Recovery System (DRS).
• Run the User Migration Tool to export the user accounts from the source domain to a file.
• Run the Enhanced Database Migration Tool (EDMT) to migrate the Historical Data Server (HDS), Logger, and Business Analytics (BA) databases from the source servers to the destination servers.
• Run the Regutil Tool to export the Cisco Systems, Inc. registry from the source servers to a file.
• Run the Unified CCE Installer on the destination servers to install the new release of Unified CCE software.
• Import the user accounts from the file using the User Migration Tool.
• Import the Cisco Systems, Inc. registry from the file using the Regutil Tool.
• Restore the configuration and data from the DRS backup.

The Common Ground upgrade includes migration of windows registry because the Regutil Tool is used to export and import the Cisco Systems, Inc. registry from the source servers to the destination servers. The registry contains important information about the Unified CCE configuration, such as the instance name, the peripheral ID, the system ID, and the license key2. The registry migration ensures that the destination servers have the same settings as the source servers after the upgrade2.

The Common Ground upgrade includes database migration because the EDMT is used to migrate the HDS, Logger, and BA databases from the source servers to the destination servers. The databases contain historical and real-time data about the Unified CCE system, such as the call records, the agent statistics, the skill group statistics, and the reporting data3. The database migration ensures that the destination servers have the same data as the source servers after the upgrade3.

The Common Ground upgrade does not update IP address as appropriate because the IP addresses of the source and destination servers are not changed during the upgrade. The IP addresses are configured during the initial installation of the Unified CCE software and are not modified by the upgrade process1.

The Common Ground upgrade does not update Hostname as appropriate because the hostnames of the source and destination servers are not changed during the upgrade. The hostnames are configured during the initial installation of the Unified CCE software and are not modified by the upgrade process

 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

According to the Cisco documentation12, single sign-on (SSO) in PCCE can be implemented in one of these three modes:

• SSO - Enable all agents and supervisors in the deployment for SSO. This mode requires the use of SAML assertions to exchange authentication and authorization details between an identity provider (IdP) and an identity service (IdS)1.
• SAML - Security Assertion Markup Language (SAML) is an XML-based standard that allows the IdP to issue SAML assertions, which are packages of security information transferred from the IdP to the service provider for user authentication1. SAML is the underlying technology that enables SSO in PCCE2.
• Hybrid - Enable agents and supervisors selectively in the deployment for SSO. Hybrid mode allows you to phase in the migration of agents from a non-SSO deployment to an SSO deployment and enable SSO for local PGs. Hybrid mode is useful if you have third-party applications that don’t support SSO, and some agents and supervisors must be SSO-disabled to sign in to those applications1.

Option A is incorrect because Non-SSO is the opposite of SSO, and it means continuing to use existing Active Directory-based and local authentication, without SSO1. Option C is incorrect because ldS is a typo for IdS, which is not a mode but a component of SSO. Option D is incorrect because ldP is a typo for IdP, which is also not a mode but a component of SSO.

References:

• 1: Single Sign-On - Cisco3
• 2: Cisco Packaged Contact Center Enterprise Features Guide Release 11.6 (1) - Single Sign-On [Cisco Packaged Contact Center Enterprise] - Cisco

• SSO - Enable all agents and supervisors in the deployment for SSO.
• Hybrid - Enable agents and supervisors selectively in the deployment for SSO. ...
• Non-SSO - Continue to use existing Active Directory-based and local authentication, without SSO.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/pcce/pcce_12_6_1/maintenance/guide/pcce_b_features-guide-1261/pcce_b_features-guide-1261_chapter_01110.html

 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.