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

Similar Messages

  • Employee replications stuck in 'Not started' status.

    Some of the Employee replication has been stuck in not started status.When you go to the edit mode and click on replicate and then save, the entries will be saved. But the status of the employee replication will be in not started status instead of successful or failed status.
    The reason might be discrepancy in the secondary persistence. This lead to the fact that you got records by the query which seemed to be relevant, but in the original persistence they were already marked as irrelevant. From SAP end we trigger a reload of the secondary persistence and the issue will be solved.
    Thanks.
    Cryssal

    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

  • 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

  • Help Agents remember when not ready

    I have a small group of nurses that take calls.  These nurses for the last year have issues with RONA calls and not going ready again.  They are nurses and there is no changing their behavior.
    Late at night when there is only one possably two nurses on shift I need to figure out a way for ICM to alert them of calls in queue if they are in a not ready or logged off state.  I have accomplished part of this by sending calls to a shared line on all their phones.
    I use an if statement SkillGroup.Nurse_EN_L1_SG.LoggedOn>0
    Trouble is when they RONA they go Not Ready.  I tried changing to SkillGroup.Nurse_EN_L1_SG.NotReady>0 but now when they are in a talking state the calls in queue ring the shared line.  Not what I was striving for.
    Does anyone have a good solution to check the many states an agent could be in?
    I thought about checking RouterLongestCallQ but becasue of the nature of the calls they get that was not sutable.
    Thanks for any suggestions!

    You could check:
    SkillGroup.Nurse_EN_L1_SG.Ready<1
    Keep in mind that Ready is not the same thing as Avail. Ready is basically any state other than NotReady or WorkNotReady. If you only route to the shared line when there is no one Ready, you can keep calls queued if they are actually logged in taking calls. Checking for NotReady>0 will route to that shared line even if only one of the nurses is in a NotReady state. That was kind of a roundabout way of explaining it, but I think the above should work out for you.

  • 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

  • Agents Toggle Between Reserved & Ready Status - UCCE 8.0(1a).

    Hello,
    In our UCCE 8.0(1a) Progger, we're facing this problem in one especific skill.
         The Agent Targeting Rule is configured with a correct range of extensions.
         The Routing Plans of our UCM don't conflict with any extension.
         The agents are below an Agent Desk Settings with no Auto Answer.
    Note: The agents don't hang up the call at Ring.
    How can we solve this issue?
    Thanks!

    Joao,
    This is looking like CUCM thing - confirm the exact behavior please as I asked in my other 2 questions?
    If ICM shortlist an agent and reserves it - ICM config is fine - it send out the Agent Extension as a label to the Routing Client which in-turn should send it to CUCM, so:
    1. 2 question I asked in my above post
    2. You using CVP or IP-IVR - if CVP do we have CUPS or DNP SRV record pointing to CUCM for these extensions?
    3. You using Agent Targeting Rule or Device Targets - if Device Targets do we have labels for these Device Targets in question?
    4. Unassociate and reassociate the extension to pguser in CUCM
    5. Also confirm Phone model and CUCM version please?
    Thanks,
    Kartik

  • UCCX script check "which agents not ready" and turn on MWI

    Hi!
    Is there a way to check which agents that are "not ready" i.e  gather user-id and extension?
    Then i want to use this "extension information" to light up the MWI on the "not ready" agents Cisco phones maybe by using unity and ctiports
    to turn on the MWI.
    OR do i need DB access to the UCCX to gather realtime of the agents name + extension + status?
    Somebody tried something similar before?
    Thx Mikael

    Its new but I like it!
    I would database dip back into the UCCX database (find the scheme guides online in the reporting guide) check status and gather all agent ID's / extensions they are logged into.
    Then do a for loop and a place call to the MWI number with the correct CSS on the CTI ports to do so... the interesting part is going to be turning them off!
    I would say you could make a UCCX thats runs more like a service with an trigger point and a service based TCL script on a router to hit that number every so often to launch it like a service.
    Or if your any good at coding you could write a small service and use something like OSIP(C Library) to trigger the MWI points over a custom built SIP trunk into CUCM with the service.  Tons of ways to skin a cat depending on your time and knowledge level.
    Chad

  • All agents become not ready Suddenly

    Does any one know what could be the reason why all the agents suddenly become not ready ?
    -Agents state after ring no answer set to : Ready
    -Automatic work and wrap up time disabled.
    -No skills,resource group based queue and circular call distribution.
    -Ip phone agents,no cad.
    What is wrong ? ,
    thanks in advance.

    Hi,
    perhaps the UCCX (or UCCE?) tries to deliver a call to the agent but due to a routing problem (CSS? Codec?) the call never arrived to the phone so the system forced the agent to Not Ready to avoid this situation with the subsequent call.
    Can you please tell us more. Is it UCCX? UCCE? What version? Did you check the logs.
    Thanks.
    G.

  • UCCX Agent Status when making a Outbound Call

    Hi Need a little Help ! Advice with the  Above subject matter.
    I have a customer, who is running reports with Historical reporting however the reports do not give a True reflection of Agents status.
    i.e. if the Agent makes an outgoing call the Reports show the agent as being not ready.
    I would like to know if it is possible to change how this is reported of if it is possible for the agent to add a note when on a call which would be reflected in the Historical reports.
    Can we change the state it shows when an agent is on an outbound call to show "Outbound Call" instead of "Not Ready" as it currently shows ?
    Cheers
    Charles

    Hi Charles
    We have raised the same problem towards Cisco a long time ago. The fact that an agent talking is reported as "Not ready", instead of ex. "Talking Out" is not only a problem in HR, but also in some steps of scripting, since the agent is infact on the system and is anything but "Not ready".
    Ex. you could check to se if any agent are logged in to CSQ, before selecting resource. If agents are logged in, you could check to see if number of agent logged in = number of agents not ready. If this is true, then no agents are available to answer call and another CSQ could be selected.
    But now since an agent talking is reported as "Not ready" because he's talking, the check for agents logged in = agents not reayd might be true, causing script no to work as intended.
    So for many reasons an agent talking should be "talking" and not "Not ready". I haven't heard about any workarounds on this agent state, but I do know that Cisco has been informed on this isseu and did recognise that it would make sense to implement but I don't know when this could happen. If not in verison 8.5, then perhaps in ver. 9.
    You might be able to pull something from the DB to show correct agent state, but thats not "out of the box"
    Regards
    Henrik

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

  • 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

  • One single button for "Ready" and "Not Ready"?

    Hi all!
    Is there a possibility to assign a service URL for changing the agent state from "Ready" to "Not Ready"? Just like the "One Button Login" ...
    Best regards; Florian

    I think this is what you are looking for. If you are using IPPA then you can use something like this as a registered service. It's what our installer configured for us.
    http://XXX.XXX.XXX.XXX:PORT/ipphone/js/sciphonexml/IPAgentChangeState.jsp?State=3&RC
    The 3 is your Agent State Code for Not Ready. For Ready just change it to a 4.
    Word of caution: Agents can not go from one Not Ready state into another Not Ready state if you are using Reason Codes. We have our agents selecting a Not Ready code from a list and with the IPPA you have to first select Ready then select Not Ready to change this state. If you are using CAD this is not an issue. Becomes a real problem if you have agents who came back from a meeting and need to go to lunch but there are calls in queue. If anyone knows a way to work around that little problem I'd be eternally grateful.

  • Not Ready Timer

    Hello,
    I got a requrement to display timer (to each representative) of how much time he is at "NOT READY" status.
    We are working with IC_AGENT profile with integrated CTI (sap sertified).
    Any Idea how this can be done?
    Thanks in Advanced
    Eli

    Hi Christina,
    Unfortunatley we didn't solved it yet.
    If you will solve it please share your solution.
    I open an innovation request foir this issue:
    please follow this request : https://influence.sap.com/D7196
    Maybe it will help :-)
    Regards
    Eli

  • Is there a setting in UCCX for long an agent phone rings before it sets him to NOT READY?

    Greetings,
    This is a new install, version 8.5.1.11..2-22, and we're in the testing phase. So, when calls are presented to an agent the phone rings for about 3 seconds (maybe 5) and then the agent is placed in the NOT READY state on the CAD and the call is presented to the next available agent. And the same thing happens, his phone rings for about 3 seconds (maybe 5) and then he's placed on NOT READY and if there is another agent the pattern repeats.
    IF you have the phone set to auto-answer with speakerphone - the call connects
    IF the agent is fast enough to answer via the CAD gui - the call connects
    So, I'm thinking there must be a setting buried somewhere we've missed on how long the agent phone will ring before the system puts him on NOT READY. Or could it be something else?
    Thanks for your time and attention!
    Keith

    The script is the culprit. So do I get credit for correctly answering my own question?  

Maybe you are looking for