McDewey

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 400: Invalid Destination (the targetMediaAddress is not one of the parties in the dialog or is not an agent extension) 400: Invalid State (the dialog is not a conference call) 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 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 Supervisor barges in and attempts to drop a participant in a two-party call scenario. Generic Error Dialog—Start Recording This API allows a user to start recording an active call. This API applies to Unified CCX deployments only. If you attempt to use this API on a Finesse deployment with Unified CCE, Finesse returns a “Not Implemented” error. Note https://<FQDN>/finesse/api/Dialog/<dialogId> URI: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 106 Cisco Finesse Desktop APIs Dialog—Start Recording