500-444 Exam Dumps : Cisco Contact Center Enterprise Implementation and Troubleshooting

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

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.

 = In order to configure SAML SSO for PCCE, you need to create claim rules that specify the claims sent from ADFS to Cisco Identity Service as part of a successful SAML assertion. The claim rules define how to transform the incoming claims from the AD FS identity provider into the outgoing claims that are expected by the Cisco Identity Service relying party. The two claim rules that are required for PCCE are:

• sAMAccountName - Logon names maintained for backward compatibility. This claim rule maps the sAMAccountName attribute from the AD FS identity provider to the uid attribute in the outgoing claim. The uid attribute is used to identify the authenticated user in the claim sent to the applications. The sAMAccountName attribute is the logon name used to support clients and servers from a previous version of Windows1.
• E-Mail Address - For the Outgoing claim type. This claim rule maps the E-Mail-Addresses attribute from the AD FS identity provider to the mail attribute in the outgoing claim. The mail attribute is used to provide the email address of the authenticated user in the claim sent to the applications. The E-Mail-Addresses attribute is the primary email address of the user2.

The other options are not valid claim rules for PCCE. The user_principal option is not a valid attribute name in AD FS. The Unspecified option is not a valid claim type in AD FS. The uid option is not a valid attribute name in AD FS, but it is the outgoing claim type that is mapped from the sAMAccountName attribute.

References :=

• AD FS 2.0 Setup for SAML SSO Configuration Example
• Configure Single Sign-On with CUCM and AD FS 2.0
• Checklist - Creating Claim Rules for a Claims Provider Trust
• Notes on ADFS as SAML IdP for ISE User Portals