/mcp<ApiErrors> <ApiError> <ErrorType>User Not Found</ErrorType> <ErrorMessage>UNKNOWN_USER</ErrorMessage> <ErrorData>4023</ErrorData> </ApiError> </ApiErrors> Example Failure Response: User notification Notifications Triggered: Platform-Based API Differences Stand-alone Finesse with Unified CCE: Finesse does not support agent sign-in with an E.164 extension when Finesse is deployed with Unified CCE. However, agents can make calls to and receive calls from E.164 phone numbers. Coresident Finesse with Unified CCX: Finesse supports agent sign-in with an E.164 extension when Finesse is deployed with Unified CCX. The maximum number of characters supported for an E.164 extension is 15 (a single plus sign followed by 14 digits). Asynchronous Errors 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 to sign in an agent with a multiline device without the correct Unified CM configuration for maximum calls and busy trigger for these devices. Invalid Device All Attempt to sign in an agent with a device that does not exist. Invalid Device All Attempt to sign in an agent with a device that is offline. Invalid Device All Attempt to sign in an agent with an extension that is not associated with the Unified CCX Resource Manager provider. Invalid Device All Attempt to sign in an agent with a device that is already in use. Device Busy User—Sign In as a Mobile Agent The User—Sign in as a mobile agent API allows a user to sign in to the CTI server as a mobile agent. This API uses the existing User object with a LOGIN state only. The user must be authenticated to use this API successfully. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 30 Cisco Finesse Desktop APIs User—Sign In as a Mobile Agent