500-444 Sample Questions Answers

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

Remote sites are added using the Websetup tool, which is a web-based interface that allows administrators to configure and manage the Packaged Contact Center Enterprise (PCCE) deployment12. Websetup provides a wizard-like process that guides the user through the steps of adding a remote site, such as entering the site name, the PG hostnames or IP addresses, the PG client types, the Unified CM publisher and subscribers, the Finesse server, and the CVP servers1. Websetup also performs automated configuration tasks for the Unified CCE PG, the Unified CCE Rogger, and the CVP Reporting Server1.

Option A is incorrect because PG Setup is a tool that is used to configure the peripheral gateways (PGs) in the main site, not the remote sites3. Option B is incorrect because Initialization Wizard is a tool that is used to initialize the PCCE deployment, not to add remote sites4. Option C is incorrect because SPOG interface is a term that refers to the Single Pane of Glass interface, which is a web-based interface that provides a unified view of the PCCE system status, not a tool to add remote sites5.

References:

• 1: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Manage Remote Sites [Cisco Packaged Contact Center Enterprise] - Cisco
• 2: Troubleshooting Cisco Contact Center Enterprise (CCET) course, Module 1: PCCE Overview
• 3: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Configure Peripheral Gateways [Cisco Packaged Contact Center Enterprise] - Cisco
• 4: Cisco Packaged Contact Center Enterprise Administration and Configuration Guide Release 11.6 (1) - Initialize the Deployment [Cisco Packaged Contact Center Enterprise] - Cisco

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

An enterprise-focused Session Border Controller (SBC) providing voice and video connectivity from the enterprise IP network to service provider SIP trunks is Cisco Unified Border Element (CUBE). CUBE is a Cisco IOS software application that acts as a network border element between two or more VoIP networks, providing interconnectivity, security, and transcoding1. CUBE can be deployed on Cisco Integrated Services Routers (ISRs), Cisco Aggregation Services Routers (ASRs), or Cisco Cloud Services Routers (CSRs) in the enterprise network edge1. CUBE enables enterprises to use SIP trunking services from service providers, as well as interconnect their on-premises or cloud-based unified communications systems with other SIP networks1. CUBE also supports various features such as call admission control, media flow-through or flow-around, quality of service, and media recording1.

CUCM, CVP, and DNIS are not valid options for this question. CUCM stands for Cisco Unified Communications Manager, which is a call processing system that provides call control, device management, and user administration for Cisco IP telephony and video solutions2. CVP stands for Cisco Unified Customer Voice Portal, which is an interactive voice response system that provides self-service and call routing applications for contact centers3. DNIS stands for Dialed Number Identification Service, which is a feature that identifies the number dialed by the caller and passes it to the destination device. None of these products or features act as an enterprise-focused SBC providing voice and video connectivity from the enterprise IP network to service provider SIP trunks.

References: Cisco Unified Border Element Configuration Guide1, Cisco Unified Communications Manager Overview2, Cisco Unified Customer Voice Portal Overview3, Dialed Number Identification Service

Dial-peers are the configuration objects that define the dial plan on a Cisco Voice Gateway/CUBE. Dial-peers are used to match the incoming and outgoing calls based on the destination patterns, and to apply the dial-peer attributes, such as codec, digit manipulation, voice-class, and call routing. Dial-peers can be of different types, such as POTS (Plain Old Telephone Service), VoIP (Voice over IP), or VXML (Voice XML). ATR, voice-class, and Voip voice are not the objects that define the dial plan, but they are some of the attributes that can be applied to the dial-peers.

References: Configuring Voice Gateways, Dial Plan, Configuring a Dial Plan

The CLI command that manages the Java Keystore Certificate in Windows CCE servers is keytool. Keytool is a utility that is included in the Java Runtime Environment (JRE) and allows you to create, import, export, list, and delete certificates, keys, and keystores. A keystore is a repository of security certificates that can be used for SSL/TLS communication. The Java Keystore Certificate is the default keystore that is used by the Java applications running on the Windows CCE servers, such as the Web Setup tool, the Diagnostic Framework Portico, and the Unified Intelligence Center12. To use keytool, you need to open a command prompt window and navigate to the JRE bin directory, which is typically located at C:\Program Files\Java\jre\bin. Then, you can use the keytool command with various options and parameters to perform the desired operations on the Java Keystore Certificate34. References: Security Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.5 (1) and 12.5 (2)1, Implement CA Signed Certificates in a CCE 12.6 Solution2, SSL Certificate Installation - Java Based Web Servers - DigiCert3, Keytool - Oracle Help Center4.

 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.

 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

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

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

SSLUtil is a Cisco-provided utility that helps to configure web servers for use with TLS. It is located in the \icm\bin folder. It can be invoked in standalone mode or automatically as part of setup. It is used to manage IIS certificates on the CCE servers for web applications such as Unified CCE Administration, WebSetup, and ISE. References:

• Security Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.6(1) - Certificate Management for Secured Connections
• Security Guide for Cisco Unified ICM/Contact Center Enterprise, Release 12.5 (1) and 12.5 (2) - Certificate Management for Secured Connections

SAML (Security Assertion Markup Language) is a service that is used to provide authorization between the Identity Provider (IdP) and the application. SAML is an XML-based open standard for transferring identity data between two parties: an IdP and a service provider (SP). The IdP performs authentication and passes the user’s identity and authorization level to the SP. The SP then grants or denies access to the application based on the user’s credentials and permissions. SAML enables single sign-on (SSO) and federated identity management across different domains and platforms.

OAuthv2 is not a service, but a protocol for authorization that allows a user to grant a third-party application access to their resources without sharing their credentials. OAuthv2 relies on tokens that are issued by an authorization server and used by the client application to access the protected resources. OAuthv2 does not provide authentication or identity information, but it can work with other services, such as OpenID Connect, to achieve that.

Active Directory Federation Services (ADFS) is a Microsoft service that provides SSO and identity federation capabilities for Windows-based environments. ADFS uses SAML as the default protocol to communicate with other IdPs and SPs. ADFS can also support other protocols, such as WS-Federation and OAuthv2.

Identity Service (IdS) is a generic term for a service that manages and verifies user identities. An IdS can use different protocols and standards, such as SAML, OAuthv2, OpenID Connect, or LDAP, to provide authentication and authorization services. An IdS can be an IdP, an SP, or both, depending on the context and the role it plays in the identity federation process.

References: What is SAML and how does SAML Authentication Work, Identity Providers and Service Providers, What is an identity provider (IdP)?