All of my agents are getting stuck in a WORK state. This happened after performing a restart of the UCCX server. I tried restarting the queue and applications, but this didn't help. I did not perform a configuration change or update to the system.
This is what is happening:
1. Agents handle a call then hangup.
2. The agents are put into a WORK status by the system.
3. They stay in WORK status until they manually put themselves back into a READY state.
4. After manually putting themselves in READY they can receive calls again, but will get stuck in WORK status as soon as they hang up.
Normally there is a 15 second period that agents are in WORK status. Afterwords they are automatically put back into a READY status.
I am running IPCC Express Enhanced 4.0(5)_Build042
Thanks for replying. I opened a TAC case and found that a Service Release needed to be installed on our Contact Center. There is a documented bug regarding the Wrapup Timer Not Working. Please see case notes below:
On the Resource configuration, for each agent check that Automatic Available is set to Enabled.
Next, on the CSQ, check that Wrapup Time is enabled, and that the seconds field is set.
The defect you are most likely hitting is CSCsh43145 - Wrapup Timer Not Working. This is fixed in the SR1 patch for 4.0(5). I recommend the SR2 patch, since these are cumulative.
The SR2 patch is available for download on Cisco.com here-
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...