Cisco 500-443 Practice Test - Questions Answers, Page 6

A switch leg on CVP refers to an ingress SIP call leg from Ingress gateway to CVP, as this is where CVP receives and controls incoming calls from PSTN or other networks. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 11

When an explicit or implicit Send to VRU node is encountered, a default Label is returned to CVP. This Label, along with a unique correlation ID, is delivered to CVP. What CVP does next is it delivers this string via SIP invite to the Virtual Voice Browser (VVB), which will execute a VXML application on behalf of CVP. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 11

A One of the conditions in which PCS legs get invoked is if Router Re-query is misconfigured and the

Ring-No-Answer timeout expires, the caller is still transferred to the Post Call Survey DN. This can occur if a Queue node is used and Enable target re-query is checked, as this causes CVP to send a new routing request to CCE when no agent answers the call. B Another condition in which PCS legs get invoked is if The Post Call Survey DN is called if the Unified CVP has received at least one CONNECT message from CCE (either from the VRU leg or the Agent's leg). Use the END node in the

CCE routing script if the Post Call Survey is not required for the calls disconnected from the IVR, as this prevents CVP from transferring the call to the Post Call Survey DN when the call is terminated by the caller or the IVR. Reference = [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 25

D One of the steps to enable database access on a CVP VXML Server to implement Database lookup using VXML is to add the JNDI Context configuration, as it defines the data source name and properties for connecting to the database. E Another step to enable database access on a CVP VXML Server to implement Database lookup using VXML is to create an SQL user for JNDI reference, as it provides the username and password for authenticating to the database. Reference = [Cisco Unified Call Studio User Guide Release 12.5(1)], page 48; [Cisco Unified Customer Voice Portal Installation and Upgrade Guide, Release 12.5(1)], page 67

A One of the required parameters to increase the default logout timer in Mobile Agent nailed connection mode in CUCM is to enable the timer entirely, as it activates the Maximum Call Duration Timer setting. D Another required parameter to increase the default logout timer in Mobile Agent nailed connection mode in CUCM is to increase the agent logout setting, as it specifies the maximum duration of a call before the agent is logged out. Reference = [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 28; [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 96

C One of the requirements for MTP configuration in Mobile Agent is that CTI ports use out of band DTMF, and SIP trunks use RFC2833 in-band DTMF, as this allows CVP to receive and process DTMF signals from different sources. D Another requirement for MTP configuration in Mobile Agent is that MTP resource is required to convert mobile agent out of band and CVP in-band signaling, as this enables CVP to communicate with mobile agent phones using different protocols. Reference = [Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND), Release 12.5(1)], page 95; [Cisco Unified Contact Center Enterprise Features Guide, Release 12.5(1)], page 28

B One of the files used to deploy Finesse custom gadgets is CSS, as it defines the style and layout of the gadget. D Another file used to deploy Finesse custom gadgets is JavaScript, as it defines the functionality and logic of the gadget. Reference = [Cisco Finesse Developer Guide Release 12.5(1)], page 9

According to the web search results, Finesse gadgets are OpenSocial gadgets that consist of the following components12:

XML to define metadata

HTML for markup

JavaScript for interactivity

CSS for presentation and style

Therefore, to deploy Finesse custom gadgets, the files that are used are CSS and JavaScript, which are responsible for the appearance and functionality of the gadgets. The other options are not correct, because they are not components of OpenSocial gadgets. Python, JSON, and C++ are different programming languages that are not used to create Finesse custom gadgets.

A One of the ways Finesse gadgets are deployed is that supporting gadgets must be accessible by both the Agent PC and the Finesse Server, as this ensures that the gadget can be loaded and rendered properly on both sides. D Another way Finesse gadgets are deployed is that Finesse Administration changes require a new login or Reset Layout in order to access changes, as this refreshes the Finesse desktop and applies the new gadget configuration. Reference = [Cisco Finesse Developer Guide Release 12.5(1)], page 10; [Cisco Finesse Administration Guide Release 12.5(1)], page 13

A The server on which the Bulk Import Tool is run is Primary Administration, as it hosts the web service that provides access to the tool. Reference = [Cisco Packaged Contact Center Enterprise Administration and Configuration Guide, Release 12.5(1)], page 109