/mcpDescription Error Type Status The toAddress and fromAddress are the same (if users attempt to call their own extension). For the Dialog—Drop Participant from Conference API, this error occurs if the targetMediaAddress is not one of the parties on the call or is not an agent extension. For the Dialog—Make a Barge Call API, this error occurs if the supervisor tries to barge in on an agent call when the agent's extension is in HELD state. Invalid Destination 400 One of the parameters provided as part of the user input is invalid or not recognized (for example, the fromAddress, toAddress, targetMediaAddress, requestedAction). For the Dialog—Update Call Variable Data API, the call variable name or action is invalid or not recognized, or there are duplicate call variable names. This error is also returned if a user attempts to set any of the following Outbound Option variables: BACampaign, BAAccountNumber, BAResponse, BAStatus, BADialedListID, BATimeZone, BABuddyName, BACustomerNumber (Unified CCX only). Invalid Input 400 A supervisor who is already on an active call (in TALKING or HOLD state) makes a silent monitor request. Invalid State 400 A required parameter was not provided in the request. For example, if creating a dialog, the fromAddess or toAddress was not provided. Parameter Missing 400 Unauthorized (for example, the user is not yet authenticated in the Web Session). The user is not authorized to use the API (for example, an agent tries to use an API that only a supervisor or administrator is authorized to use). Authorization Failure 401 The authenticated user tried to make a request for another user. The authenticated user tried to use a fromAddress that does not belong to that user. Invalid Authorization User Specified 401 The targetMediaAddress in a Dialog—Start Recording request specifies an extension of a participant in HELD state. Invalid State 401 Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 137 Cisco Finesse Desktop APIs Dialog API Errors