Hello All,
I am experiencing some weird behavior while implementing a standard circular hunt-group. I wonder if someone else has seen this too, and possibly has a workaround.
The setup is as follows:
Hunt Pilot DN 111
connected with standard hunt list,
connected with standard circular line-group with following members:
member 1: 100
member 2: 200
member 3: 300
member 4: 400
1st case:
member 3 not logged in, member 1,2 and 4 are all idle
The callflow is clearly circular; when calling the HP 111 I arrive at 100->200->400->100->200->400->100->200->400, no problem here.
2nd case:
member 3 not logged in, member 1 is in a call, members 2 and 4 are idle:
The callflow is not circular anymore: when calling the HP 111 I arrive at 200->200->400->200->200->400->200->200->400->..
extension 200 receives the double amount of calls of 400
3th case
member 4 not logged in, member 2 is in a call, members 1 and 3 are idle:
Same problem: the callflow is not circular: hp 111 arrives at: 100->300->300->100->300->300->100->300->300->100->300->300
When all phones are logged in, (and one phone is busy) the same problem happens.
It seems like when the hunt-pilot wants to send a call to a phone that is busy the call gets dispatched to the next member in the line-group, however the next call arrives also at that member, meaning the flow is not really circular and some extensions experience more calls than others.
Cheers,
Jeremy
Before you create the circular hunt groups using Cisco CallManager Attendant Console, perform these steps:
Create the pilot points.
Create the hunt groups.
Hi, thanks for your response,
There is no attendant console-configuration made.
The setup is plain Hunt Pilot-Hunt List-Line group
greetings