I recently updated our CallManager to version 4.1(3) with the latest service release. Since then, the attendant console failover has stopped working. I have the Hunt Group configured to route to:
Operator1 Line 1
Operator2 Line 2
Operator3 Line 3
Extension 7201 (always route member is checked)
The acconfig.bat is configured with queuing enabled checked. The routing algorithm is First Available Hunting. The hold time is set to 90 seconds.
Before the update, if someone was on hold longer than 90 seconds they would automatically get routed to extension 7201. Now our customers sit on hold until an operator signs into the attendant console. Any recommendations would be appreciated, or if anyone has a better suggention for Operator failover I am all ears. Thanks.
Are you talking about a Call Park duration or a Hold duration of 90 seconds? In CCM 4.1(3) there is a Clusterwide Parameter - Hold Reversion defualt reversion timer of 0 (nothing happens when a user is on hold) and a reversion notification timer of 30 seconds (the person that placed the call on hold gets a notification beep on their headset.
During your upgrade, your 90 second reversion timer probably got reset to 0 (the default).
Thanks for replying. The acconfig.bat tool has a section for Hold Time. The way this has worked in the past is that if a call is parked for more that 90 seconds, it will revert back to the person whom parked the call. In addition, if a person was trying to get an attendant, but all attendants were busy longer than 90 seconds, they would be routed to an extension whether or not that extension was busy. I used this for failover incase the TCD service failed or our operators forgot to logon to the attendant console client.
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 ...