have 4.6.2 and have set up the ring no answer time and the ring no answer dn in agent desktop settings but it still doesn't seem to be working. When a call goes to an agent and he doesn't answer, it just keeps ringing...when the caller finally hangs up, the agent is made not ready. If the agent answers the call after the ring no answer timeout, the call is handled normally and the agent state is not changed. Any ideas would be greatly appreciated.
Try setting the forward no answer time in CallManager to 21 seconds and the forward no answer time in the Agent Desk Settings to 18 seconds .The forward no answer timer in CallManager should always be less than ICM.
You can also see if the notification is sent via the Peripheral Gateway , you will see that the Peripheral gateway shows "agent answer timeout exceed "
We have the forward no answer setting at the default of 12 secs in Callmanager and 9 seconds in Agent desk settings. Do we also need to set a forward no answer dialed number in Callmanager? On the pg it says "agent failed to answer alerting line" but it just keeps ringing until the caller hangs up or the agent answers.
One other thing to check: is the RONA destination DN attached to the same routing client as the original route request that sent the call to the agent?
I've found that this causes similar behavior to what you are seeing at your site. The ICM RONA number for that agent must be valid for the same RC as the original call, or the post-route to find another agent won't work properly.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...