500-052 Exam Dumps : Deploying Cisco Unified Contact Center Express

The gadget to initiate or accept a call is common and is not tied to a specific tab on the Cisco Finesse agent desktop. The gadget is located in the call control area, which is a fixed section of the Finesse desktop that appears on every tab. The gadget provides the basic call control buttons, such as Answer, Hold, Retrieve, End, and Make Call. The gadget also displays the caller ID, the call state, and the call timer. The gadget changes depending on the situation and the call type. For example, the gadget shows different buttons for inbound, outbound, and consult calls12

The other options are not correct:

• The My Statistics tab hosts the gadget that shows the agent’s performance statistics, such as the number of calls handled, the average talk time, the average wrap-up time, and the service level12
• The Home tab hosts the gadget that shows the agent’s state, the reason code, and the state timer. The Home tab also allows the agent to change their state, sign out, or go to the Team Performance tab12
• The Manage Customer tab hosts the gadget that shows the customer information, such as the account number, the name, the address, and the call history. The Manage Customer tab also allows the agent to perform advanced call control actions, such as consult, transfer, and conference12

References: 1: Cisco Finesse Agent and Supervisor Desktop User Guide Release 12.0(1) - Cisco Finesse Desktop Interface [Cisco Finesse] - Cisco 1 2: How IT Works: Cisco Finesse Agent Desktop and UCCX | Mindsight 2

To send an HTTP message, you should use the following Cisco Unified CCX steps:

• Send HTTP Response: This step allows the script to send an HTTP response to the client that initiated the HTTP request. The step specifies the HTTP status code, the content type, and the body of the response. The step can also set or delete cookies in the response. For more information on how to use the Send HTTP Response step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Send HTTP Response Step.
• Create URL Document: This step allows the script to create a URL document that contains the URL of a web page or application. The step specifies the URL, the method (GET or POST), and the parameters to be sent with the request. The step can also set or delete cookies in the request. The URL document can be used as an input for other steps, such as Write Document or Place Call. For more information on how to use the Create URL Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Create URL Document Step.

The following steps cannot be used to send an HTTP message:

• Write Document: This step allows the script to write a document to a file or a stream. The step specifies the document, the destination, and the encoding. The document can be any type of document, such as XML, plain text, or URL. The destination can be a local file, a remote file, or a media stream. The step can be used to write a URL document to a file or a stream, but it cannot send an HTTP message by itself. For more information on how to use the Write Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Write Document Step.
• Place Call: This step allows the script to place a call to a destination. The step specifies the calling address, the called address, the media termination, and the timeout. The calling address and the called address can be phone numbers, SIP URIs, or URL documents. The media termination can be a contact, a prompt, or a document. The step can be used to place a call to a URL document, but it cannot send an HTTP message by itself. For more information on how to use the Place Call step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Place Call Step.
• Cache Document: This step allows the script to cache a document in the memory of the Unified CCX server. The step specifies the document and the cache key. The document can be any type of document, such as XML, plain text, or URL. The cache key is a unique identifier for the document in the cache. The step can be used to cache a URL document, but it cannot send an HTTP message by itself. For more information on how to use the Cache Document step, see the Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1), Chapter: Steps, Section: Cache Document Step. References:
• Cisco Unified Contact Center Express Editor Step Reference, Release 12.5 (1)
• [Deploying Cisco Unified Contact Center Express (UCCXD) v6.0]2, Module 2: Cisco Unified CCX Scripting, Lesson 3: Cisco Unified CCX Scripting Steps, Topic: HTTP Contact Steps

 The maximum round-trip time (RTT) between Cisco Unified CCX servers in a WAN deployment is 80 ms. This is the network requirement for deploying Unified CCX high availability over WAN, which provides site redundancy. The RTT is the time it takes for a packet to travel from one node to another and back. If the RTT exceeds 80 ms, the Unified CCX servers may not be able to communicate properly and failover may occur. The RTT can be verified by using an extended ping command on the network device closest to the Unified CCX servers, such as the access switch. The ping command should set the Layer 3 type of service (ToS) bits to ensure that the packet is sent on the same QoS-enabled path as the WAN traffic. References := Solution Design Guide for Cisco Unified Contact Center Express, Release 12.5 (1) SU2, page 10-2. Solution Design Guide for Cisco Unified Contact Center Express, Release 11.5 (1), page 10-2.