McDewey

202: Successfully Accepted 400: Parameter Missing (the targetMediaAddress or requestedAction is not provided) 400: Invalid Input 401: Authorization Failure 401: Invalid Authorization User Specified 404: Dialog Not Found 500: Internal Server Error 503: Service Unavailable (for example, the Notification Service is not running). HTTP Response: For voice dialogs: <ApiErrors> <ApiError> <ErrorType>Invalid Input</ErrorType> <ErrorData>requestedAction</ErrorData> <ErrorMessage>Invalid 'requestedAction' specified for dialog</ErrorMessage> </ApiError> </ApiErrors> For nonvoice dialogs: <ApiErrors> <ApiError> <ErrorType>Agent is not logged in</ErrorType> <ErrorMessage>E_ARM_STAT_AGENT_NOT_LOGGED_IN</ErrorMessage> <ErrorData>6</ErrorData> <ErrorMedia>5001</ErrorMedia> </ApiError> </ApiErrors> Example Failure Response: For voice dialogs: Dialog notification Dialog CTI error notification (if a CTI error occurs) For nonvoice dialogs: Dialogs/Media notification Dialogs/Media asynchronous error notifications including CTI errors Notifications Triggered: Platform-Based API Differences The following table describes API differences between a stand-alone Finesse deployment with Unified CCE or a coresident Finesse deployment with Unified CCX. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 85 Cisco Finesse Desktop APIs Dialog—Take Action on Participant