When my agents lodin and go into ready state all is weel. Then when they get a call and complete it they go to not ready and have to open the window and press the ready icon. Is there a way to have the agent go back to ready stae when they hang up the phone.
I have run into this same issue where the agent state is put into work after hanging up. Each Resource that I have configured has the "Automatic Available" parameter enabled. (This was enabled from the beginning and I have restarted the CRS server and agents have shutdown the Agent Desktop client.) However, each agent is still going into a Work / Not Ready state and they have to manually make their state Ready after EACH call. I have read additional posts and see that one possible work around would be to edit the SubsystenRmCm.properties file. I am just not convinced that this will resolve this issue as the symptoms for this fix are for incoming calls moving on to agent2 after agent1 does not answer the call even thought they are in a Ready state. I am not sure what else to look at. There may be something with in the Desktop Administrator that needs configuring however I am not exactly sure. Any suggestions?
What version of IPCC are you using? I tried to navigate to subsystems--->ICD--->CQS--->CQS Name -----> Automatic Work and I do not see it. I am able to enable for the ICD agent but can not find where I disable for the CQS.
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...