Agent desktop goes to not ready randomly

Hello,
We have ctios agent desktop version 8 and we have ucce version 8.  We have user that randomly was put to not ready state without clicking on anything and when she tries to put herself back all buttons are grayed out even she closed application and still the user could not log out. Until we rebooted cisco phone or called someone from her phone it worked fine.  Keep in mind it shows the right state of the agent on cisco supervisor it just shows wrong on the user agent desktop.
Any suggestions please.
Thanks,

I got some time to go through the logs.
 i see agent state has changed to not ready with reason code 32767.
08/08/14 12:34:09.798  3864  CTIOSSoftphone  Thd(3396)  CCtiOsSession::OnEvent( eAgentStateEvent ), EnablementMask = c1b0010
08/08/14 12:34:09.798  3864  CTIOSSoftphone  Thd(3396)  CCtiOsSession::OnEvent, (PrphID:5000 PrphTyp:17 AGState:eNotReady SG#:40106 SGID:5000 StateDur:0 SGPri:0 EvtRsnCode:32767 SGState:2 SessID:0 MRDID:1 ICMAGID:5124 AGMode:1 MaxTaskLim:1 NumTasks:0 AGExt:2192 AGID:278 AGInstr:2192 CTIClntSig:CTIOSServer Msk:0xc1b0010 UniqObjID:agent.5000.278 MsgID:eAgentStateEvent DvrKey:agent.5000.278 IncOrOut:21327 WrpupOKEnbl:1 AGAvailStatus:0 MskExt:1)
the reason code gets set when "redirect on no answer" occures, i know it as RONA.
Q 1>  how your solution is configured to handle RONA? i understood that you are using CVP, correct?
RONA in CVP is configured differently than in normal environment, you have to use Router Requry there. there are some good post on this topic, you may want to read those.
Q2> I see in the logs that, agent is trying to do singlestep transfer on two DN's
"2193" and "2194", so what are this DN's?
Q3> how many lines a Agents phone is configured with?
regards
Chintan

Similar Messages

  • UCCE v7.5 - Prevent Agent from going into Not-Ready on RONA

    Does any one know whther it is possible to prevent Agents using IP Phone Agent from going into Not-Ready once a call has been presented and the RONA timer has expired?
    My customer is fully aware of the implications of doing this. They are not using CAD or CTI-OS.
    Many thanks
    Freddie

    If you don't set the RNA timer in the agent desk settings, the agent will not be made not ready.
    Whoops: did not read carefully. You are using IP phone agent. Sorry, I don't know.
    Regards,
    Geoff

  • Agent going to not ready after call hangup, Siebel CRM Connector, reason code 50002

    Hi Everyone,
    We have Contact Center Enterprise UCCE 8.5.2 with CTOS integrated Siebel CRM 8.1.1 using
    Cisco Unified CRM connector
    On daily basis we are receiving about 100 incidents that Agents goes to not ready after
    talking to customer. and the reporting gives the reason code 50002.
    As per Cisco its because of CTI server Failure/Agent desktop closed/network Problem.  But
    In real there is no network issue, Agent not closing the Agent desktop. Also if this is
    the case agent should be logged out but in pratical its stays logged in but moved to
    not-ready state(Reason 50002)
    It could be  miss communication between UCCE and Siebal CRM connector.
    One more thing its not happening with one customer only it happening in many deployment on
    Version 8. Especially the one integrated with Siebel.
    If anyone face the same issue please share the experience and the solution if found any!
    Regards,
    Atif Tanveer

    Atif,
    If memory serves me right, CTI events are controlled and communicated by Siebel connector.  So when your users close Siebel or any other CTI controlling connector this will be same as closing CTIOS or CAD without proper logoff.  This will keep the phone out of synch and keep the user automatically into not ready to prevent any callers going to this device.
    Simple answer you have to train users and make sure they close Close applications properly.
    Thanks,
    Baseer.

  • Cisco Agents goes to Not ready state

    Hi,
    I have use IPCC ver:4.0(5) SR01ES09_Build095.
    We have encountered that our cisco agents automatically change state and it will goes from log-in state to Not ready state.
    what was the solution where i have to check the logs.
    regards
    Salman

    Hi Salman-ahmad,
    This could be the way you have your agents or CSQ configured, you can configure IPCC to have them to automatically goto Not ready or stay in ready. Have you check your system parameter's?
    Under RMCM Subsystem, click the resource link on the left hand side,
    there is a "automatically Available" radio box you need to select.
    Otherwise you maybe hitting this bug.... Are these your symptom's?
    CSCsf11662 Bug Details
    Agent goes to Not Ready after making Outbound call from Ready state
    Symptom:
    Agent makes outbound call from ICD extension (to a non-ICD extension), when
    the agent finishes the call, they go into Not Ready state when they expect
    to be returned to Ready state.
    Conditions:
    - Cisco Customer Response Solutions (CRS) 4.0(3)
    - Agent makes outbound call from ICd extension whilst in Work state (after just finishing an incoming ICD call).
    - Agent places the outbound call on Hold at some stage during the call.
    Workaround:
    If the above scenario occurs, Agent needs to manually change to Ready state.
    HTH, Please rate if so
    Regards,
    Justin

  • Agent real time display not ready time is inaccurate

    Agent Not Ready Detail in Webview-Agent Realtime Reports in CAD.
    I am looking at the agent: Agent Not Ready Detail Report in Webview and comparing this to the Agent Real Rime Display in CAD. If I manually add the Not Ready times (state durations) from the agent ACD state log, they equate to the Cisco Web View agent report. However, the Total Not Ready column from the Agent Detail Display report in CAD does not sync up with either Webview or CAD. Its more than an hour off.
    The Eastern managers are looking closely at these numbers now and one of the agents questioned the report in CAD today and brought this to a manager's attention. It is more than an hour off which is a big difference.
    It was comparing the state duration for not ready from the ACD State Log Display (for example the 5 seconds at 10:15:04 in screen shot 1) to the total not ready time from the Agent Real Time Display Displays report (3:48:59 in screen shot 2). The total individual state durations of unavailable time from report #1 does not equal report #2 and I would think it should. If not explain why?
    From CAD client > Real Time Displays > Agent ACD State Log Display. If you add up all the Not Ready times and compare with webview, it matches. No problem here.
    From CAD client > Real Time Displays > Agent Detail Display (this doesnt match up with webview report or the total Not Ready times in Agent ACD State Log Display).
    We're looking to know either
    1. How exactly the not ready state time is calculated
                   OR
    2. Where to find the information on how this is deteremined.
    I appreaciate any response. Thank you.

    Is it all agents or only one/some?
    What does CSD show? Can you post a screenshot of the CSD main screen for a team?
    Also, please post the traces from Desktop Recording and Statistics Server.

  • 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.

  • CTIOS agent goes in the Not Ready state randomly

    Hi all,
    It is a UCCE system version 7.0 with CTIOS Agent Desktop.
    I have one agent that is being put in the Not Ready state randomly and he can then re-put himself in the ready state.
    I have checked the following logfiles: ctios client, ctios server, cti server and I haven't found relevant information, all what I found was the timestamps when this agent was put in the Not Ready state.
    In the UCM pim logfile I found the below:
    9:38:59 pg1A-pim1 Trace: [  4608]CSTA CONNECTION CLEARED, TelephonyDriver::ConnectionCleared: SENT TO OPC
      CallID          = 39182119  DeviceID = 3942  DeviceType = Static
      ReleasingDevice = 3942
      LocalState      = NONE
      Cause           = EC_NONE
    Does the above mean that the connection from ICM to the agent phone has been lost and this caused the agent state to become Not Ready?
    Your help is highly appreciated.
    Thank you in advance.
    Lara

    Hi,
    can you also attach the above mentioned logfiles? We might be able to find something interesting in them. Thanks. G.

  • CAD "Select reason for not ready" not appearing for some agents? Please help!

    Hi all,
    I have some users who when they click on 'Not Ready' in CAD (Cisco Agent Desktop) - they are not presented with the 'Select Reason for Not Ready' dialog box - it just goes straight to Not Ready.
    I have searched high and low but have not found any suitable results (maybe I'm doing it all wrong?).
    Anyway - we use CUCM
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;
    mso-fareast-language:EN-US;}
    8.0.2.40000-1 and UCCX
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;
    mso-fareast-language:EN-US;}
    8.0.2.10000-41.
    Version 8.0(2) of CAD.
    Works for some agents and not others. All the same Windows operating system.
    Is there an individual setting which needs to be set on each user in CUCM or UCCX in order for this to be triggered?
    I would've thought it was universal?
    Cheers,
    Brett

    Ahhhh, spot on.
    Can't believe I missed it...
    Cisco Desktop Administrator (go) > Personnel > Agents > Set appropriate 'Work Flow Group'
    Agent logs out of and closes CAD, opens and logs back into CAD, tested, solved.
    Many thanks again

  • Interaction Center scenario: total time when agent is "not ready"

    Hi,
    I have a requirement to show the total time when an agent is "not ready" in IC. I know an agent is either "ready" (to pick up calls) or "not ready". Any idea which business content handles this?
    Thanks!

    As thomascollins said, you can build an Agent Management workflow. A couple of comments though.
    A lot of our agents have multiple extensions on their phone.  If they are talking on a non queue extension they let the queue extension ring out putting them in a "not Ready" State.
    It would be better if the agent went "not ready" immediately they take a call on their non-contact center line to prevent RONA which is not providing your customers with the best possible service. The routing engine will select another available agent. This positive action by the agent will remind them to take the inverse action and make themselves ready when they finish their call on their non-CC line (well, maybe ).
    Requested FunctionalityProvide Queue supervisors with an alert through email or another method to let them know that an agent have gone into a "Not Ready" State.
    You would not want this alert done immediately - the poor supervisors would get hammered. Perhaps an alert if an agent is in the "not ready" state for more than (say) 5 minutes. Of course, this now means that the not ready state is useless for meetings, short breaks, lunch and so on - and agents would have to logout for those. Not a problem, and logging out is my preferred method. Just making an observation.
    Regards,
    Geoff

  • UCCX agent stuck in Not Ready status

    Hi             There
    We are using uccx 7 and 1 agent's status stuck in the "Not Ready".
    We can not see his account in the supervisor but in the "Resource Cisco Unified Contact Center Express Stats" I can see his status is in Not Ready for more than 44 hours.
    Is there any way we can clear the session?
    Thank you in advance.

    Do you think there is an agent logged in and Not Ready, or do you think it's a hung session?
    If you think it's a real login, reboot the PC.
    If you think it's a hung session then you'll have to restart a service of two. I would just plan for a maintenance window and reboot the server along with your CUCM CTI Manager.
    Good luck and happy troubleshooting!
    Sent from Cisco Technical Support iPhone App

  • 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

  • Reminder for UCCX agent desktop

    Hi            There
    We are using uccx 7 and got some requirement to have a reminder pop up when the agent is not ready to remind them that they need to change their status to Ready.
    Our agents are not just sitting in the chair and waiting for the incoming call, they have to move to other area to do some other stuff sometimes, but during that time they may get incoming call and their agent status was changed to Not Ready, when they came back to the desk they just simply forgot to change the status back, is there any way that we can have a pop up window to remind them?
    In the Cisco Desktop Administrator, I can configure the popup window under Voice Contact Work Flows when the called number match the trigger, but there is no way I can add the condition that it only happen when the agent is not ready; In the Agent Management Work Flows, I can have the popup window when agent is not ready, but it is not what we want, it popup whenever the agent's status changed to Not Ready.
    Maybe there is a way in the script that when there is incoming call, it check the "Not Ready" agents and send the popup window to those agents, but I am not sure how to do it.
    Can anyone kindly give me some hint for this?
    Cheers

    As you can probably see reading this thread, there is no easy, built-in way to handle this.  I think the Cisco approved way, would be to leverage the Wrap up time, and force them into the Ready state, as oppose to warning them.
    I have one other method to throw into the mix, and your experience with it may be different from the next person's; so please test this out first before deploying it all over the place.
    If you have MS Office installed on the CAD PC, you can actually leverage a feature out of the MS Word COM Object to view a list of running Window Titles, and since CAD puts the state of the Agent in the Window title, this works.
    You will need to copy and paste the below code into a notepad document, and then save as "All Files" and name it something like "monitor.vbs".
    '=============================================================================='=='=='=='=='=='== This script will attempt to monitor the CAD title window and keep track'== of how long the state is Not Ready, then alert the user once a threshold'== is exceeded. The user can press OK to go ready or Cancel to stay Not Ready.'=='== Microsoft Word Required.'=='== Author=Anthony Holloway'==        [email protected]'=='== Last Update=04 AUG 2009'=='== User defined variables'=========================' The StateThreshold is in seconds, and sets a limit to how long the Agent' state can be "Not Ready"Const StateThreshold = 600' The AlertMessage is displayed to the user; keep it short and sweet.Const AlertMessage = "You are currently in a Not Ready state."' The AlertTitle is displayed as the alerts title barConst AlertTitle = "Cisco Agent Desktop"'==============================================================================Set oMicrosoftWord = CreateObject("Word.Application")Set cRunningApplications = oMicrosoftWord.TasksSet oShell = CreateObject("WScript.Shell")iCounter = 0sCADNotreadyTitle = "Not Ready - Cisco Agent Desktop"' Loop foreverDo While True     ' Does the CAD title contain "Not Ready"?     If cRunningApplications.Exists(sCADNotReadyTitle) Then          ' Yes, Has the state exceeded the threshold?          If iCounter >= StateThreshold Then               ' Yes, Alert the user               iUserChoice = MsgBox(AlertMessage & vbCrLf & "Press OK to go Ready", vbOKCancel + vbExclamation + vbDefaultButton2, AlertTitle)               If iUserChoice = vbOK Then                    oShell.AppActivate sCADNotreadyTitle                    WScript.Sleep 500                    oShell.SendKeys "^w"               End If               ' Reset the counter               iCounter = 0          Else               ' No, Increment the counter               iCounter = iCounter + 1          End If     Else          ' Yes, Clear the counter          iCounter = 0     End If     ' Pause 1 second before checking again     WScript.Sleep 1000Loop
    Then you will need to start it by one of several ways.  One way is to place it into the startup folder of the windows PC.  Another way is to have it launch via CDA Run External Application on CAD Startup.  It just runs in the background all the time, monitoring the title of the CAD window.
    Anthony Holloway
    Please use the star ratings to help drive great content to the top of searches.

  • CAD: not ready before Log on

    A supervisor in the application Cisco Supervisor Desktop observes a strange situation.
    Wrong sequence of events when logging agents:
    The first recording - not ready.
    After 1 second - logon.
    when correct:
    first:  Logon
    after: not ready
    The situation could be repeated, and can - do not.
    Version of CAD 8.5
    what could be wrong?
    Thanks a lot!

    resolved.
    T CAD does not take  milliseconds time
    states - only whole seconds. In the ICM - with millisecond precision.

  • Get Reporting Statistic - Not Ready Resources

    Hi All - I have a script that currently checks for LOGGED IN agents .. If there are none, it goes to a voicemail. We have agents all over the globe and unfortunatly some stay LOGGED IN, but in a NOT READY state. Therefore the call goes into queue, and not routed to the voicemail.
    Does anyone know, if I change the "get reporting statistic" to look for NOT READY agents, vs. LOGGED IN agents, does it consider agents on a call "not ready"? Or will it look for agents that specifically put themselves into a NOT READY state?
    Thanks
    Jeff

    Hello Jeff, the agents on an active call will not count for the Not Ready state. When receiving the call (ringing) they will be placed in Reserved state; while the call is connected they will be in Talking state and after the call ends they could be placed in Work state for a while.
    HTH
    Pablo

  • UCCX and agent desktop +E.164

    Hello - we are running 10.0 UCCX and looking to see if +E.164 is supported.  The issue we have with this is that with agent desktop it does not allow the + sign in the extension field.  IS there a work around for this?

    Hi Ed,
    Use of E.164 DN on agent devices requires Finesse. E.164 is not supported with CAD / IPPA.
    HTH
    Manish

Maybe you are looking for