07-03-2014 12:57 PM - edited 03-15-2019 06:00 AM
Hey all,
We have a UCCX cluster running version 9.0.2.11001-24. We are also running Cisco Supervisor Desktop 9.0(2) (Premium Version) build number 9.0.2.1064. It appears for only one of our queues, it's reporting in the "Current Oldest" column that there are calls in the queue when in fact there are not.
I've attached a screenshot (omitted client related stuff) so you can see. In the "Current Oldest" column, it reports 3 Current Calls with Oldest time of 00:00:00. Our client has confirmed no calls in the queue.
Any ideas why this is happening and on only one CSQ? Any ideas on how to fix it?
08-20-2014 10:27 AM
Did you ever figure this out? We have one CSQ showing the same thing under CSD 9.0.2.1064. It's only 1 call, but we have a Workflow in CSD that colors the CSQ red and notes it has Calls Waiting. The Supervisors are very insistent on getting this resolved since the Workflow makes the real state of the CSQ misleading.
Thanks.
08-22-2014 11:56 AM
Hey jmakowski_2,
Yes the issue was resolved by restarting the UCCX Engine Services on Publisher and Subscriber (in that order).
In our setup, Publisher is the Master and Subscriber is the Slave. So you restart UCCX Engine service on Pub to make Sub Master, then when the transition is completed, restart UCCX Engine service on Sub to put Pub back to Master.
This was a solution from Cisco TAC.
Thanks,
John
08-22-2014 12:00 PM
Thanks. We found that out inadvertently. We had an issue with the VoIP Monitoring Subsystem on the Sub. We tried just restarting the Desktop VoIP Monitoring service, but that didn't help and caused us to have to restart the Engine on the Master then Sub. The next morning the false call was gone.
Appreciate the response.
08-22-2014 12:08 PM
Great to hear you got it resolved. You're welcome.
John
02-04-2016 12:01 PM
I also found this bug:
CSCsu40814 - The supervisor shows oldest in queue as 1(00:00:00)
https://tools.cisco.com/bugsearch/bug/CSCsu40814
It says that this issue can occur if your setup has some unsupported configurations which are listed here:
So if you have configured on this list configured in your UCCX/CUCM systems, then this problem can occur. We found a couple of these items were in our configuration and we have corrected them. Now we're going to see if it occurs again.
John
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: