/mcpDeployment Type Reason ErrorType All Attempt to put the held call (a direct call) on hold again. Generic Error Unified CCX Non-conference-controller attempts to conference in another party. Invalid State Asynchronous Errors for Nonvoice Dialogs If an error occurs after the initial validation of a nonvoice dialog is complete, the API send an error notification over XMPP to the Dialogs/Media notification. The error message has the format described in "Media and Dialogs/Media Asynchronous Error Notification.". The requestId is included in the response XML. The ErrorMedia parameter in the ApiError information indicates the Media Routing Domain to which the error applies. For transfers, Finesse communicates asynchronously with Customer Collaboration Platform to initiate task resubmission requests. The following types of errors can occur, and are returned asynchronously: • Customer Collaboration Platform can respond to the Finesse transfer request with an HTTP error response (for example 4XX or 5XX ). • The Finesse request to Customer Collaboration Platform may time-out due to network issues. If the request to Customer Collaboration Platform fails, the API send an error notification over XMPP to the Dialogs/Media notification, and Finesse retains the dialog. Dialog—Update Call Variable Data This API allows a user to set or change call variables (including named variables or ECC variables) of a dialog. If the user is an agent, the user must be a participant to invoke this action. A corresponding notification is published if there is an update to any of the values of the call variables or named variables. With Unified CCE, Cisco Finesse does not support the use of extended ASCII characters required for additional alphabets in the ECC variables and call variables 1-10. You must use only ASCII characters in the 0-127 range. For example, if you set call variable 2 to contain the character à (ASCII 133), it does not appear correctly on the agent desktop. Note With Unified CCX, Cisco Finesse only supports Latin1 characters for ECC variables. Other Unicode characters are not supported. For example, if a user tries to use this API to update an ECC variable that contains Chinese characters, Finesse may not return the correct value in the subsequent dialog update it sends to the client. https://<FQDN>/finesse/api/Dialog/<dialogId> URI: https://finesse1.xyz.com/finesse/api/Dialog/54321 Example URI: Agents can use this API. Agents can only act on a participant of a dialog when they are that participant. Security Constraints: PUT HTTP Method: Application/XML Content Type: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 87 Cisco Finesse Desktop APIs Dialog—Update Call Variable Data