/mcpSupervisors can use this API. A supervisor must be signed in to the fromAddress (extension) being used to create the silent monitor call. Agent to be monitored must be assigned to a team that the supervisor is responsible for. A supervisor can silently monitor any call except a silent monitor call. If an agent drops from or transfers the call that the supervisor is monitoring, the silent monitoring session ends. Security Constraints: POST HTTP Method: Application/XML Content Type: XML Input/Output Format: <Dialog> <requestedAction>SILENT_MONITOR</requestedAction> <fromAddress>1001002</fromAddress> <toAddress>1001001</toAddress> </Dialog> HTTP Request: id (required): The ID of the user requestedAction (required): The way in which the dialog is created (SILENT_MONITOR) fromAddress (required): The extension of the supervisor who initiated the silent monitor request toAddress (required): The extension of the agent that the supervisor wants to monitor Request Parameters: 202: Successfully Accepted This response only indicates a successful completion of the request. The request is processed and the actual response is sent as part of a dialog notification. Note 400: Parameter Missing 400: Invalid Input 400: Invalid Destination 400: Invalid State 401: Authorization Failure 401: Invalid Authorization User Specified 500: Internal Server Error HTTP Response: <ApiErrors> <ApiError> <ErrorType>Authorization Failure</ErrorType> <ErrorMessage>UNAUTHORIZED</ErrorMessage> <ErrorData>jsmith</ErrorData> </ApiError> </ApiErrors> Example Failure Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 98 Cisco Finesse Desktop APIs Dialog—Make a Silent Monitor Call