Hunt Group Overflow Problem 8.1

[mjroam]

I have had an ongoing issues since an upgrade from IP 406 5.0 to New IPO 500 8.1.

Issue: Single member hunt group for receptionist with overflow after 5 rings. Cannot seem to figure out how to prevent immediate overflow when receptionist is on call.
Customer only wants overflow after no answer (over flow timer 17) regardless of whether on call or not. Phone is 1416.

Tried sequential, collective, collective call waiting, with and with out queuing. Changed No answer and overflow timers. Phone has 10 call appearances.

Nothing seems to change the fact that if that single member of the hunt group is on a call it will overflow immediately when it should be ringing an available call appearance until the overflow time has expired and queuing is enabled. (If I'm reading the docs correct)

I've looked at docs, knowledgebase etc. Never had this issue on older versions that I can remember. Matter of fact I think it worked fine until they swapped out the old 4424.
But that really wouldn't make sense would it?

Thanks any ideas would be appreciated.

 

[intrigrant]

Did you enable call waiting in the user settings?
Did you read this:
When is Overflow Used?

A call will overflow in the following scenarios:
· If Queuing is off and all members of the hunt group are busy, a call presented to the group will overflow immediately, irrespective of the Overflow Time.
· If Queuing is on and all members of the hunt group are busy, a call presented to the group will queue for up to the Overflow Time before overflowing.
· If Queuing is on but there are no members logged in or enabled, calls can be set to overflow immediately by setting the Overflow Immediate setting to No Active Members.
Otherwise calls will queue until the Overflow Time expires.
· If no Overflow Time is set, a call will overflow when it has rung each available hunt group member without being answered.
· Once one call is in overflow mode, any additional calls will also overflow if the Overflow Mode is set to Group (the default).

You could delete the user, reboot and re-create the user, maybe something got corrupted dureing the upgrade process.