cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
1650
Views
5
Helpful
4
Replies

Agents Showing Up in Wrong Queue in Cisco Supervisor Desktop

bwolf
Level 1
Level 1

UCCX version 10.6.1.11001-31

I have two agents that transferred to a new department.

They have been skilled to the correct resource group and team. 

They have been removed from their previous resource group and team.

The agents receive calls correctly from their new department's queue.

Both agents show up in Cisco Supervisor Desktop under their old department, even though they are receiving and taking calls for their new department.

I tried Cisco Desktop Administrator -> Services Configuration -> Synchronize Directory Service

I had them log out of their Phones and Agent Desktop and back in

Tried a dbreplication and this is what we get:

admin:utils dbreplication repair all

 -------------------- utils dbreplication repair --------------------

Traceback (most recent call last):

  File "/usr/local/cm/bin/DbReplRepair.py", line 267, in <module>

    if found >= 0:

NameError: name 'found' is not defined

Any ideas?  Thanks

1 Accepted Solution

Accepted Solutions

Try restarting below services from Cisco Unified CCX Serviceability:

Cisco Desktop Sync Service
Cisco Desktop Call/Chat Service

If doing this does not fix the issue then go ahead with restarting Cisco Unified CCX Engine or restarting the whole server (whichever is more feasible) during after hours.

Regards

Deepak

View solution in original post

4 Replies 4

BOBBY LINDSEY
Level 1
Level 1

Did you find a resolution to this? I have this problem as well.

Try restarting below services from Cisco Unified CCX Serviceability:

Cisco Desktop Sync Service
Cisco Desktop Call/Chat Service

If doing this does not fix the issue then go ahead with restarting Cisco Unified CCX Engine or restarting the whole server (whichever is more feasible) during after hours.

Regards

Deepak

Thank you for the response.  I ended up restarting my UCCX servers, that took care of the issue.

I ended up restarting my UCCX servers outside of business hours.  That took care of it.