07-14-2010 12:20 PM - edited 03-15-2019 11:43 PM
I have CM version: 6.0.1.2000-3 with Cisco Unity Connection version: 2.0.1.2000-337
I have set up the Call Handlers to make calls to hunt.
The Line Group I set up has 13 People in it.
I have it set the Distribution Algorithm to Longest Idle time, and the phone template has the Hlog function so they can log out of the hunt group when they are away from their desk.
One agent stated that she received a call from the hunt list and answered. Two seconds later she received a second call from the hunt list.
I figured it was so close that Cisco still considered her having the longest idle time.
She said later in the day it happened again. This time it was about 10 seconds after she picked up and was on a call.
Is there a place I can tweak this?
How/when does CM determine your idle time. I would assume as you receive the call that it would reset your idle time to zero.
07-14-2010 12:29 PM
Hi
I would take a look at the CDR records for this users' phone.
A hunt group will not send a call to a line that is in use; whilst it's possible that you are seeing a bug it's far more likely that someone or something else dialled the users' handset directly rather than through the hunt group.
Regards
Aaron
Please rate helpful posts...
07-15-2010 08:57 AM
She did not answer the 2nd call, she just noted that it was calling her when she was on a call.
I'm not proficient with CDR. Which report should I run? I did run some reports but I am not seeing the activity of a call ringing at her desk.
07-15-2010 09:28 AM
Hi
There is a service parameter for the CallManager service named 'Log calls with zero duration' - it defaults to false... so if the call isn't answered, it won't appear.
As I say, I doubt heavily it was a hunt call....
Regards
Aaron
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide