/mcpAgents can use this API. Agents can only act on their own Dialog object. Security Constraints: PUT HTTP Method: Application/XML Content Type: XML Input/Output Format: <Dialog> <requestedAction>UPDATE_SCHEDULED_CALLBACK</requestedAction> <targetMediaAddress>1001001</targetMediaAddress> <actionParams> <ActionParam> <name>callbackTime</name> <value>2013-12-07T14:30</value> </ActionParam> </actionParams> </Dialog> HTTP Request (Update Scheduled Callback): <Dialog> <requestedAction>CANCEL_SCHEDULED_CALLBACK</requestedAction> <targetMediaAddress>100100</targetMediaAddress> </Dialog> HTTP Request (Cancel Scheduled Callback): dialogId (required): The ID of the dialog requestedAction (required): The action to perform (UPDATE_SCHEDULED_CALLBACK,CANCEL_SCHEDULED_CALLBACK) targetMediaAddress (required): The extension of the agent who is making the request actionParams (required): A collection of objects called ActionParam, which contain name/value pairs. The name must be UPDATE_SCHEDULED_CALLBACK. The value can be callbackTime or callbackNumber. A single parameter must be specified for the value. Any additional parameters are ignored. Request Parameters: 202: Successfully Accepted This response only indicates a successful completion of the request. The request is processed and the actual response is sent as part of a dialog notification. Note 400: Parameter Missing 400: Invalid Input 401: Authorization Failure 401: Invalid Authorization User Specified 404: Dialog Not Found 500: Internal Server Error 501: Not Implemented HTTP Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 113 Cisco Finesse Desktop APIs Dialog—Schedule or Cancel a Callback