McDewey

Response Scenario Stand-alone Finesse with Unified CCE: <data> <apiErrors> <apiError> <errorData>20999</errorData> <errorMessage><ConferenceCallCommand>: Conference failed...causes include agent already has a consult call or conferencing a non-conference controller. </errorMessage> <errorType>Generic Error</errorType> </apiError> </apiErrors> </data> Coresident Finesse with Unified CCX: <data> <apiErrors> <apiError> <errorData>22</errorData> <errorMessage>CF_INVALID_OBJECT_STATE</errorMessage> <errorType>Invalid State</errorType> </apiError> </apiErrors> </data> A participant who is not the conference controller tries to conference in another participant. Asynchronous Errors for Voice Dialogs 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 call transfer without an existing consult call. Generic Error All Attempt a call transfer on the original call (a direct call) after the original call has already been retrieved. Generic Error All Attempt to complete a conference on the original call after retrieving the original call. Generic Error All Attempt to exceed the maximum allowed conference participants. Generic Error All Attempt to RETRIEVE an incoming OutBoundPreview campaign call when the allowed actions are ACCEPT, CLOSE, and REJECT. Generic Error Unified CCE Non-conference-controller attempts to conference in another party. Generic Error Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 86 Cisco Finesse Desktop APIs Dialog—Take Action on Participant