This document describes the reasons of Agent not ready with the reason code.
Agent Not Ready Reason codes
There are reports that show the codes agents select when entering Not Ready state, that calculate the percentage of time spent in the Not Ready state, and that show specific Not Ready reasons based on the time range you specify. These reports help you identify whether agents are taking the appropriate number of breaks and whether their breaks are the appropriate length.Some reports display both the text of the reason code (if configured) and the corresponding number. For example, if an agent enters Not Ready state and selects "Break" as the reason code,and if you have configured text for this code in Configuration Manager, reports display "Break ". Other reports display the numeric Not Ready reason code only.If an agent's total login session is not included in the specified time range (for example, the agent was still logged in at the end of the time range), an asterisk (*) appears next to the agent's name in the report to indicate that data for that agent is not complete for the range. For Unified CC, in addition to Not Ready reason codes that you define, there are predefined Not Ready reason codes for situations in which the agent is made Not Ready automatically by the software. The following table describes these predefined Not Ready reason codes.
Predefined Not Ready Code Description
The CTI OS client disconnected, logging the agent out.Note: This reason code is converted to a 50002, so 50001 does not
display in the agent log out records.
A CTI OS component failed, causing the agent to be logged out. This could be due to closing the agent desktop application, heartbeat time out, a CTI OS Server failure, or a CTI OS failure.
Agent was logged out because the Unified CM reported the device out of service.
Agent was logged out due to agent inactivity as configured in agent desk settings.
For a Unified CCE deployment where the Multi Line Agent Control is enabled in the peripheral, and the Multi Line Agent Behavior is
configured to impact agent state, the Agent will be set to not ready with this code while talking on a call on the Non ACD line.
The agent did not receive multiple consecutive calls routed to him/her. The system makes the agent Not Ready automatically so that
50010 additional calls are not routed to the agent. By default, the number of consecutive calls missed before the agent is made Not Ready is 2.
Agent was logged out when the agent's skill group dynamically changed on the Administration & Data Server.
If an agent is logged in to a dynamic device target that is using the same dialed number (DN) as the PG static device target, the agent is logged out.
Mobile agent was logged out because the call failed.
Mobile agent state changed to Not Ready because the call fails when the mobile agent's phone line rings busy.
Mobile agent was logged out because the phone line disconnected while using nailed connection mode.
The agent's state was changed to Not Ready because the call fails when the agent's phone line rings busy.
The agent's state was changed to Not Ready because the agent did not answer a call and the call was redirected to a different agent or skill group.
20001 - applicable if you
are using the Cisco
Places the agent in the Not Ready state first before forcefully logging them off.
20002 - applicable if you
are using the Cisco
Forces the logout request; for example, when Agent A attempts to log in to Cisco Agent Desktop and Agent B is already logged in under that agent ID, Agent A is asked whether or not to force the login.
If Agent A answers yes, Agent B is logged out and Agent A is logged in. Reports would then show that Agent B logged out at a certain time with a reason code of 20002 (Agent B was forcibly logged out).
20003 - applicable if you
are using the Cisco
Not Ready for logout.
If not already in the Logout state, request is made to place agent in the Not Ready state. Then logout request is made to log the agent out.
Supervisor Not Ready
This code is reserved.
This code is reserved.
Agent reinitialized (used if peripheral restarts).
PG reset the agent, normally due to a PG failure.
An administrator modified the agent's extension while the agent was logged in.
By default, predefined Not Ready reason codes do not have associated textual reason codes.They appear as numbers in reports. If you want to see a textual code for these Not Ready reason codes, enter the predefined Not Ready reason code into the Reason Code List tool with the related text. For example, you might want to label the 32767 Not Ready reason code "Redirection on No Answer".
• To report on Not Ready reason codes, ensure that the reporting of agent event detail data is enabled on the PG with the Cisco Unified CM peripheral. This is enabled by default.
We have a plan to migrate the exiting Call manager and unity cluster from a physical server to virtual servers. The current version 9.x.We want to make sure to have a minimum downtime. The plan is to create the same version of the cucm & cuc servers o...
im having a big issue with my new 4451-x not registering on the cucm , it is stuck on registering ? under cucm i added as 4451 mgcp gateway , is 4451 different than 4451-x and that is why it is not getting added? i already didccm-manager configccm-ma...
hello, if anyone can help here. both inbound and outbound calls are failing but I can't find in the logs if we are sending the disconnect or its initiated by the carrier just like we do in the regular ISDN. all I can see is B-Channel ...
Hello all,I have a question. Is there a wait timer in Call studio? I have an application that attempts to get information from a rest client. The client way specify that it is still gathering data. So the proposal is to set a wait ...
Hello, I ran into a problem with the ESXi host after power outage. The VM doesn't load and a pink screen appears with the following error:NOT_IMPLEMENTED bora/vmkernel/core/bootModule.c:122 VMware have an article for it:https://kb.vmware.com/s/a...