Hunt Group Calls Stuck In Que

[prflash]

We have an IPO 3.1.48 in an office and since yesterday whenever a call is transfered into the C/S Hunt Group the call gets stuck there. The only thing that has been done with this site was yesterday morning I remotely re-booted the system to clear a call that was "hung" on one of the trunk lines. Should I have the onsite personnel perform a hard re-boot of all the modules???

Prflash

 

[tlpeter]

give it a shot
if you don't shoot it is alway a missed shot


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[IPOUK]

You using $ACD by any chance? or in your case, you may need to use $ACD in the queue!

Later versions be sure to get rid of it - it is not needed anymore and so not supported (helpful for people who upgrade isn't it and Avaya don't make us aware!!)

 

[memphistim]

Are you using Queue buttons on the Agent phones?

There was a situation in 3.1 (don't remember what release) where calls picked out of the Queue by selecting the queue button resulted in the call being answered but not cleared out of Queue...phantom calls essentially. There was a fix in either the Manager release or the Delta Server release, but I don't remember the details.

Thanks,

 

[intrigrant]

There can be various reasons for a call getting stuck in the queue (version 3.2, don't know about 4.0):
[ul]
[li]Calls transferred by a user with a transfer return time set, if a transferred call is not answered within the transfer return time it will result in a call stuck in queue.
However, this is NOT a real call but it will lock up new calls to stay in the queue![/li]
[li]If a groupmember has call forwarding including huntgroup calls back into the same group will result in a call stuck in the queue[/li]
[li]Using $ACD in VM Pro may get calls stuck in queue[/li]
[/ul]