[cisco-voip] Caller order when presented to hunt groups

[Brian Meade]

Are the same line group members in both HG1 and HG2?  You should have
separate line appearances for HG1 and HG2 so that agents will answer HG2
first if there's a call for it.

On Wed, May 27, 2015 at 10:45 AM, Nick <csvoip at googlemail.com> wrote:

> Hi All
>
> Anyone come across this scenario before?
>
>
>
> On 26 May 2015 at 11:51, Nick <csvoip at googlemail.com> wrote:
>
>> Fruther info on this is that the callers only lose the order of once they
>> have tripped to the secondary line group, new callers ringing n thr first
>> line group get answered first.
>>
>> Scenario as follows
>>
>>
>> Call A arrives at HG1
>>
>> Call B arrives at HG1 after call A
>>
>> Call A is unanswered and goes to HG 2
>>
>> Agent answers the next call presented and is presented call B even though
>> total time waiting is shorter than call A
>>
>>
>>
>> On 26 May 2015 at 10:04, Nick <csvoip at googlemail.com> wrote:
>>
>>> I have had a query from a customer where we have a small site with 6
>>> channels BRI, single number to a hunt pilot with a hunt list contraining
>>> two tiered line groups who claims that when they have multiple calls coming
>>> into the hunt group if they are not answered within the 12 seconds set on
>>> line group 1 and the calls trip to line group 2 when the first call is
>>> answered is will not be the caller who dialled into the hunt group
>>> first and the callers will randomly be presented for answer.
>>>
>>> Its not a sceanrio I have come across before and cannot find any
>>> information on this in any documentation, so does anyone know if that is
>>> workingcorrectly or if we have an issue here.
>>>
>>> Anyone come across anything like this before?
>>>
>>>
>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150527/8be71703/attachment.html>