McDewey

errors as asynchronous updates. Error notifications include the error type and the CTI error code and error constant. The error type is “Call Operation Failure”. XML Format: /finesse/api/User/{id}/Dialogs Node: /finesse/api/Dialog/{id} Source: apiErrors Data: <Update> <data> <apiErrors> <apiError> <errorData>[CTI Error Code]</errorData> <errorMessage>[CTI Error Constant]</errorMessage> <errorType>Call Operation Failure</errorType> </apiError> </apiErrors> </data> <event>PUT</event> <requestId></requestId> <source>/finesse/api/Dialog/[ID]</source> </Update> Payload: <Update> <data> <apiErrors> <apiError> <errorData>34</errorData> <errorMessage>CF_RESOURCE_OUT_OF_SERVICE</errorMessage> <errorType>Call Operation Failure</errorType> </apiError> </apiErrors> </data> <event>PUT</event> <requestId></requestId> <source>/finesse/api/Dialog/12345</source> </Update> Sample Notification Payload The notification system delivers this error notification if call operations on a Dialog (such as MAKE_CALL, HOLD, RETRIEVE, ANSWER, END, TRANSFER, CONSULT, and CONFERENCE) result in a CTI error Notification Triggers: 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 the description above for Dialog CTI Error Notification. Note Deployment Type Reason ErrorType Unified CCE Attempt to exceed maximum allowed conference participants. Call Operation Failure Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 359 Cisco Finesse Notifications Dialog CTI Error Notification