/mcpResponse Scenario Stand-alone Finesse with Unified CCE: Finesse sends a User notification with state=TALKING. Coresident Finesse with Unified CCX: Finesse does not send a User notification. The agent remains in NOT_READY state. Agent receives and answers a non-ICD call. Stand-alone Finesse with Unified CCE: Finesse sends a User notification with state=HOLD. Coresident Finesse with Unified CCX: Finesse does not send a User notification. The agent remains in TALKING state. Agent puts an ICD call on hold. Stand-alone Finesse with Unified CCE: Agent transitions to READY state after the call ends. Coresident Finesse with Unified CCX: Unified CCX does not allow an agent to set a pending state of READY while that agent is talking on an ICD call. <data> <apiErrors> <apiError> <errorData>265</errorData> <errorMessage>CF_INVALID_AGENT_WORKMODE</errorMessage> <errorType>Invalid State</errorType> </apiError> </apiErrors> </data> While talking on an ICD call, the agent sets a pending state of READY. Stand-alone Finesse with Unified CCE: Agent transitions to READY state after the call ends. Coresident Finesse with Unified CCX: Unified CCX does not allow an agent to set a pending state of READY while that agent is talking on a non-ICD call. <data> <apiErrors> <apiError> <errorData>33</errorData> <errorMessage>CF_RESOURCE_BUSY</errorMessage> <errorType>Invalid State</errorType> </apiError> </apiErrors> </data> While talking on a non-ICD call (agent state can be TALKING in Unified CCE or NOT_READY in Unified CCX), the agent sets a pending state of READY. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 49 Cisco Finesse Desktop APIs User—Change Agent State