/mcpXML Input/Output Format: <Media> <state>LOGOUT</state> </Media> HTTP Request: id (required): The ID of the user mrdId (required): The ID of the MRD state (required): The new state that the user wants to be in (READY, NOT_READY, LOGIN, or LOGOUT) Request Parameters: requestId: A user provided unique string used to correlate originating request with the resulting HTTP response or asynchronous error. This parameter is not part of the resulting event/events. Header Parameters: 202: Successfully Accepted The requestId is included in the response header if provided. This response only indicates successful completion of the request. The request is processed and the actual response is sent as part of a media notification. Note 400: Bad Request (for example, malformed or incomplete request) 401: Unauthorized (for example, the user is not authenticated in the Web Session) 404: Not Found (for example, the user ID or mrdId is not known) 503: Service Unavailable (for example, the Notification Service is not running) HTTP Response: <ApiErrors> <ApiError> <ErrorData>6</ErrorData> <ErrorMedia>5001</ErrorMedia> <ErrorMessage>E_ARM_STAT_AGENT_NOT_LOGGED_IN</ErrorMessage> <ErrorType>Agent is not logged in</ErrorType> </ApiError> </ApiErrors> Example Failure Response: Media notification The system ignores requests to change agent state from READY to READY; these requests do not trigger a notification. Note Notifications Triggered: Asynchronous Errors If an error occurs after the initial validation is complete, an error notification is sent over XMPP to the Media notification. The requestId is included in the response XML. The ErrorMedia parameter in the ApiError information indicates the Media Routing Domain to which the error applies. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 170 Cisco Finesse Desktop APIs Media—Change State or Sign Out