/mcpCONSULT_CALL Example <Dialog> <requestedAction>CONSULT_CALL</requestedAction> <toAddress>1001002</toAddress> <targetMediaAddress>1001001</targetMediaAddress> </Dialog> HTTP Request: dialogId (required): The ID of the dialog requestedAction (required): The way in which the dialog is created (CONSULT_CALL) toAddress (required): The destination for the call targetMediaAddress (required): The extension of the agent, used to locate the participant to target with the requestedAction Request Parameters: 202: Successfully Accepted 400: Parameter Missing 400: Invalid Input 401: Authorization Failure 401: Invalid Authorization User Specified 500: Internal Server Error HTTP Response: <ApiErrors> <ApiError> <ErrorType>Authorization Failure</ErrorType> <ErrorMessage>UNAUTHORIZED</ErrorMessage> <ErrorData>jsmith</ErrorData> </ApiError> </ApiErrors> Example Failure Response: Dialog notification Dialog CTI error notification (if a CTI error occurs) Notifications Triggered: Asynchronous Errors When accessing the Finesse REST API through the Finesse JavaScript library, asynchronous errors have a status code of 400. When receiving the asynchronous error directly through XMPP, the error message has the format described in "Dialog CTI Error Notification." Note Deployment Type Reason ErrorType ALL Attempt a CONSULT_CALL on an incoming OutBoundPreview campaign call while the allowed actions are ACCEPT, CLOSE, and REJECT. Generic Error ALL Attempt a CONSULT_CALL while the call is alerting. Generic Error ALL Attempt a CONSULT_CALL while the call is on HOLD. Generic Error Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 95 Cisco Finesse Desktop APIs Dialog—Make a Consult Call Request
