Have a customer with an old EE-1000 chassis running ver 1.0, everything has been working just fine for them... CCR tree, voicemail, etc.
They've now got the need to have multiple CSR's take calls for several of the items in the CCR tree, so I thought the best fit would be to set up huntgroups for those items. Changes made to the CCR tree ok, and the calls go through to the huntgroup DN's just fine.
The problem occurs when the call is not answered by any member of the hunt group... instead of the call falling through to the overflow position, I simply get 4 rings and then a "the person you have called is not available" (or if I program a vmail box for the huntgroup DN it falls into voicemail) and then drops back to the CCR tree.
Huntgroup (529) is defined as broadcast mode, if busy- overflow, queue timeout 15, overflow to 221. I have played with the queue timeout and also tried with the huntgroup in rotary and linear modes... all with the same result... 4 rings and then the not available message.
As I read the docs... in broadcast mode if nobody answers I should fall through to the overflow destination after the timeout.
This could be a bug in 1.0... or I'm missing something really obvious in the configuration. It's one of those "I've pulled out my last remaining hair" days... any ideas/suggestions?
Thanks,
>>>>> Mike <<<<<
They've now got the need to have multiple CSR's take calls for several of the items in the CCR tree, so I thought the best fit would be to set up huntgroups for those items. Changes made to the CCR tree ok, and the calls go through to the huntgroup DN's just fine.
The problem occurs when the call is not answered by any member of the hunt group... instead of the call falling through to the overflow position, I simply get 4 rings and then a "the person you have called is not available" (or if I program a vmail box for the huntgroup DN it falls into voicemail) and then drops back to the CCR tree.
Huntgroup (529) is defined as broadcast mode, if busy- overflow, queue timeout 15, overflow to 221. I have played with the queue timeout and also tried with the huntgroup in rotary and linear modes... all with the same result... 4 rings and then the not available message.
As I read the docs... in broadcast mode if nobody answers I should fall through to the overflow destination after the timeout.
This could be a bug in 1.0... or I'm missing something really obvious in the configuration. It's one of those "I've pulled out my last remaining hair" days... any ideas/suggestions?
Thanks,
>>>>> Mike <<<<<