I haven't been able to confirm it, though admittedly I haven't researched it thoroughly.
The CAD end user guide for CCX clearly states that "you can click the Not Ready button again..." but the CAD end user guide for Enterprise (7.5) does not.
I'm also not clear if this issue was addressed for - or if it even pertains to users of the CTIOS Toolkit Desktop.
The intent of the change was to allow agents to change Not Ready reason codes (without going Ready first) to accommodate the schedule adherance feature of Calabrio/Cisco WFO Workforce Management.
For example, if an agent is scheduled to be in training from 10:00 - 11:00am, they would be in a Not Ready state with reason code "Training."
If the agent is likewise scheduled to be at lunch from 11:00am - 12:00pm, they would remain in the Not Ready state, but change their reason code to "Lunch" by simply clicking the Not Ready button again.
If you check the forums on the Calabrio portal (http://portal.calabrio.com) this topic may be discussed there, as it pertains to the Cisco Agent Desktop. They also have links there that allow you to ask product-specific questions.
Appreciate your quick response. I was just curious and being lazy to find out or do my search. I agree it probably have little or no practical impact in a production environment and for sure negligible in enterprise.
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...