McDewey

<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 Unified CCE Attempt a TRANSFER_SST before the call gets answered. Generic Error Unified CCE Attempt a TRANSFER_SST on an incoming OutBoundPreview campaign call while the allowed actions are ACCEPT, CLOSE, and REJECT. Generic Error Dialog—Make a Silent Monitor Call This API allows a supervisor to silently monitor an agent who is on an active call and in TALKING state. A new dialog is created, specifying the fromAddress (the supervisor's extension) and the toAddress (the agent's extension). The dialog is posted to the supervisor's dialog collection. Agent phones to be monitored must support silent monitoring and must be configured in Cisco Unified Communications Manager as follows: • The correct device type must be configured. • The device must have Bridge Monitoring enabled. • The correct permissions must be configured (under User Management > End User > PG User, in the Permissions area, select Standard CTI Allow Call Recording, and then click Add to User Group). Note https://<FQDN>/finesse/api/User/<id>/Dialogs URI: https://finesse1.xyz.com/finesse/api/User/1234/Dialogs Example URI: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 97 Cisco Finesse Desktop APIs Dialog—Make a Silent Monitor Call