CUIC Not Ready Reason Code Reporting Issue

We have a single node UCCX 9.0.2 environment with co-resident CUIC used for historical reporting.
When we run the Agent Not Ready Reason Code Summary Report it will only give statistics for the system generated reason codes (the 32XXX ones), even if we choose other reason codes in the filter parameters.
In the attached screenshots you can see where I chose a bunch of other reason codes as filter options, but none of them show on the report. It does the same thing regardless of who runs the report, including the admin super user that's created during installation.
Anyone have any ideas?

We do not run the same version that you are on, however, I would also take a look at the Agent State Detail report and filter by the reason code field.
The report includes a lot of additional data but at least you can get to the actual customized reason code values along with the duration the agent spent in that code per occurrence.
Hope this helps.

Similar Messages

Cisco Finesse - Not Ready Reason Codes

Hi,
Can anyone tell me if it's possible to go from one not ready reason code straight to another without going ready in between?
Example:
Agent goes to lunch, selects Not Ready (Lunch). Comes back from lunch and goes to a meeting - they need to go to Not Ready (Meeting) - without going Ready.
Thanks,
Brian

Here is a link to the doc:
http://docwiki.cisco.com/wiki/Desktop:_Agent_State_Changes

Not Ready Reason Codes

Is anyone familiar with configuring Not Ready Reason Codes in Desktop Administrator, more specifically creating a new one? From all Cisco's documentation it should be a simple task.
However, when I create the new Reason Code in ICM Configuration Manager, it does not populate to the Reason Code list in Desktop Workflow Administrator.
The version of UCCE we are running is version 8.0.

check your CAD is synced with ICM, especially check the configuration for AW in CAD post install.
in CAD, reason codes automatically synchronises once configured in ICM. and then you can assign them to workflows.

UCCE Not Ready Reason Code Removed after Internal Call

Here is the scenario. Agent puts themselves Not Ready which we have set to require a Not Ready reason. They enter the reason and go about their business. Someone internally calls their extension for whatever reason. The agent takes the call and hangs up. It seems they are left Not Ready but the reason for being Not Ready is removed. They are now in a undefined not ready code. Can it be set to put them back in the Not Ready Reason they were prior to the internal call? Here is what we are running:
CUCM: 8.0.3.21900-8
ICM: 8.0(3) (8.0 SR 8.03)
CTIOS: 8.0(3)
CAD: 8.0(1) (build: 8.0.1.47)
JTAPTI: 8.0(3.10000)

Hi Brad,
As I understand that the agent before receiving the internal call the agent already went to Not Ready. So after the internal call depending on the wrap-up setting agent will either go to the wrap-up node or directly to the Not Ready state.
If agent goes to wrap-up then need to provide the wrap-up code and after wrap-up need to select Ready or Not Ready. In this case agent will not get any option to select Not Ready. Because prior receiving the inter call the agent was in Not Ready state. By default this is how it works.
But if you use CTIOS agent desktop then with customizing the call event. For example customize the CTIOS code in such was that for internal calls after agent press the wrap-up complete button instead of going back to previous event it will go to the Not Ready event.
Unfortunately for your case it will not work as you are using CAD.
Thanks,
Ashfaque

Agents showing in NOT READY Reason Code Summary Report

I have a large install, with over 100 skills and CSQs. Three agents always show up in everybody's Not Reason Code Summary Report, even though they are not assigned to those skills. At this point none of these three agents has ever been active. My assumption is there is a bug that until an agent actually goes Active at least once this happens. I am looking for confirmation, documentation of such.
Thanks.

Hi,
What is the version of IPCC you are running?
What do you mean when you say agent goes active?
Please refer to this guide below for UCCX 5.0. Refer to pg 65 for Agent Summary report.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_6_0/user/guide/crs601hr.pdf
See if it has the information you are looking for.
So you mean to say you filter this report based on Skill name and still see those 3 agents evene when you chose a skill which is nto assigned to three of them?
Thanks
Ankita

CTI Not ready reason code 50010

Hi ,
We have a UCCE set up 8.0 . Agents automatically going to not ready state. When checked in report it shows Missed Tasks eroor code (50010). It is a default cisco reason code.Can anyone explain the exact reason for this issue .
Thanks,
Rahul

Hi,
the schema handbook says about this error code:
The agent did not receive multiple consecutive calls routed to him/her. The system makes the agent Not Ready automatically so that 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.
This means the system was able to see these agents as available, it tried to send calls there, but for some reason the calls never reached the agent.
A common mistake causing this issue is Device Target misconfiguration. Can you please check whether you have set up device target for agents, including labels for CUCM and IVR/VRU's?
G.

CTI OS Server Not ready Reason

Hi
I know that Not Ready with CTIOS is server base. I want to know if it's possible to have spefic reason for some agent and other reason for other agent.
My point is I didn't want all the agent to see all the reason code.
Regards
Frank

I'm not sure thats exactly correct. You have to define Not Rady Reason codes in the registry for CTIOS, not just in ICM. This coupled with the fact that you can indeed create new connection profiles, which is where the Reason codes are confiugred. I believe you can make multiple connection profiles, and tell the agents to choose the correct one. I may be wrong though, I haven't tried.
Chad

Global reason code report generation

Dear All,
I am running uccx8.0 standard Edition. I want to take global reason codes report, How can i do that. I think in the CCX historical report i can see the reports for preserved. But i want to see for custom reason codes.

Sorry i got the solution,

CUIC Reason code reports

I am trying to create a report that shows reason codes as words, eg 1 =meeting etc
I have made what I believe to be the relavant changes, however whilst the Parameters check out ok, when i go to creat the fields, I get a syntax error.
if anyone can take a look at this and let me know here I am goiing wrong, I would be grateful.
please be advised, I haven't had any training on SQL, I am learning as i go!

Thanks for getting back to me, unfortunately I don't have the ability to check this through an SQL application.
Hence the question.:-)
I will go through the query again
Cheers Sarah

"Drive not ready" error message; synching issue

Hi- this is my first posting!
I am having problems syncing my ipod and itunes. I keep getting the error message "Drive is not ready for use; its door may be open. Please check drive \Device\Harddisk1\DR3 (here it has been DR5, DR3 and DR21 at different times) and make sure that a disk is inserted and that the drive door is closed."
Of possible relevance-I am on a network computer and this message has occurred after 1. a computer upgrade and 2. the discovery of spyware on my computer, and 3. itunes and (attempted) ipod update. (The spyware issue has been fixed, but I wasn't involved in doing that.)
A final bit of info-I have tried to change the E: drive to a different letter, like Z: but that gave me the same message.
Any suggestions?
Thanks so so much!!!
Compaq Windows XP

My ipod was dead. It was trying to tell me that its little hard drive was worn out.

Siebel CRM Reason Code Commands

We are needing to enable some commands on the Cisco CTIOS Siebel connector and just not sure where they are enabled or edited at.
We are using connecter provided by CISCO for CTI between Siebel and CISCO. Connector provides the enabled command to Siebel that siebel can send as device command like "DeviceCommand = "ChangeNotReadyState"" using communication configuration DEF file.
Currently we have business requirement:
CTI agents can set their state to NOT READY on a click of button with reason code selected by the agents irrespective of there current state.
We configured the button, but the button is enabled only when the device command "ChangeNotReadyState" is enabled. Can it be possible to enable this button always and we can are able to change agents state at CTIOS level(CISCO)? Can we send "ChangeNotReadyState" command to CISCO irrespective of agents current state
Here is what we have done so far:
We configured DEF according to ORACLE support recommendation (ID 543337.1 listed below in this mail)
RELEVANT PARTIAL DEF FILE:
[Command:DSC_NOTREADY_POP_EXE]
   SubCommand_1 = "DSC_NOTREADY_NOPOPUP"
   SubCommand_2 = "DSC_NOTREADY_POPUP"
   SubCommand_3 = "CleanDashBoard"
   Comment      = "YQ8279: Add for Direct not ready Button Aug2012"
   Description = "Not Ready"
   ExecuteAll   = "TRUE"
   Hidden       = "TRUE"
[Command:DSC_NOTREADY_NOPOPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
[Command:DSC_NOTREADY_POPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
   CmdData       = "PopupforReason"
   [CmdData:PopupforReason]
      Comment          = "YQ8279: Add for Direct not ready Button Aug2012"
      Param.ReasonCode = "[Name]"
      SelectApplet     = "Transfer Multiple LOV Popup Applet"
      SelectBusComp    = "List Of Values"
      SelectBusObj     = "List Of Values"
      SelectParam      = "TRUE"
      SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle      = "Please select the reason for changing status to Not-Ready"
So with above configuration suggested by oracle support we are sending "ChangeNotReadyState" device command twice in a manner so that it will be processed one after the other. But it is not happing, second command is not going through as its not enabled after Siebel issued it once. Please see below logs and highlights.
SCOMM LOG: <In Time Context >
ChangeNotReadyState Command is enabled (status = 16)
see image 1 on attached doc
Now user applied the command once :
See Image 2 on attached doc
Now "ChangeNotReadyState" device command is disabled .
Can we make it "ChangeNotReadyState" enabled via connecter always by making some registry setting or some setup.
See image 3 on attached doc
Oracle Support Suggestion:
Not able to select Not Ready Reason Code [ID 543337.1]
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147
Symptoms
In the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
Cause
Users were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
Solution
Suggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"

Thanks for your response Cherilynn,
You are correct for a vanilla agetn desktop. However, if the agent has to become available to move from one aux reason to another, the agent may get a call in that process. With customiization, we can allow changing from one aux code to another without having to make the agent ready. Oracle suggested a solution but to do this, we need to enable and modify certain parameters within Cisco. What we are trying to find out is where are these parameters set, ex: AgentWorkMode and AgentWorkMode2, ChangeNotReadyState...
ORACLE SUPPORT SR
Not able to select Not Ready Reason Code [ID 543337.1]
SymptomsIn the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
CauseUsers were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
SolutionSuggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"
Regards,
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147

CAD UCCE Reason Codes Question

In UCCE CAD 7.5.4 and later Spanlink came out with a new feature where a agent can change thier "Not Ready" reason code without going "Ready"->"NotReady". I have a customer who is running 7.5.6 and does not like this feature and would like to turn it off. There is nothing in Cisco Administration Desktop application that controls this (i.e. enable / disable of this feature) Does any one know if there is a Registry or configuration file that can turn off this feature? - Thank for your help! - Jim

Not as far as I know. Haven't asked TAC or anything yet though. It's annoying because when going Not Ready > Not Ready it doesn't write an entry into the Agent_State_Trace table, only the Agent_Event_Detail which one of my clients needed to use for reporting..

CISCO unified CCX reason codes

Hi, I have generated an AGENT STATE DETAIL REPORT and two of the not ready reason codes are 36 and 38. Can anybody point to where in the CISCO literature I can find the explanation for those reason codes. Or explain them to me.
Also as a second question, when using CISCO Unified CCX to generate reports is there any way of showing what the call termination reason was.
ie Call has been handled but was it a) ended by the caller b) ended by the phone agent c) ended by a CISCO error.
This would be quite usefull to know at times.
many thanks in advance for any help, advice or pointers.

Hi Eric,
The reason codes are defined through the desktop administrator and the range are 0 - 999.Refer the below link page number 48 for more info.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/user/guide/cda85ccxug-cm.pdf
Page :191
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/user/guide/uccx85hrug.pdf
For the second query refer the database schema guide for more info.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_5/user/guide/uccx85dbschema.pdf
Regards,
Gnan.
Pls rate if this helps.

UCCE Agent_Logout table reason code 0

Hi all,
It is a UCCE system 9.0
we faced an issue last saturday, all the agents got logged_out from their cisco phones and then they were able to log in again.
when checking the reason code at that time in the agent_logout table I noticed that its value was 0.
has anyone encountered a similar issue? and what does the reason code 0 mean?
Thank you in advance
Lara

Lara,
could you please post a few rows from the Agent_Event_Detail (or if it's enabled, the Agent_State_Trace) database views? I would like to see the Not Ready reason code for the event that preceeded the Logout event.
Reasons may be plenty. For instance, agent phone lost connection to the CUCM and reset.
G.

Historical report issue with CCX Custom Reason codes

Hi Evryone,
I have CCX version 8.5,
In Cisco Desktop Administrator ,I have configured custom Reason codes for agent logout & Agent not ready,
These code are working ok when agent is loging out or Not ready,
But in Historical reports I am not able to see these custom Reason code base reports
I can only see the reports for agent not ready/login logout with only global reason codes, but report didnt show the cutom reason code base report
Please help me to troubleshoot this issue.
Regards
Deepak

hi Deepak,
Did you do something else while creating new global reason codes?
I have global reason codes, but in the the Historical Reports "detail" tab don't show up any of them. Report only shows system-genereted reason codes.
BEst regards

CUIC Not Ready Reason Code Reporting Issue

Similar Messages

Maybe you are looking for