302C Console Operation

[ShikePoke]

I have a user that swears that the a, b, c, d buttons would beep and blink for additional calls to the console attendant. I recently re-installed a G3si V11 for them and now the "Individual Calls Waiting" light comes on for subsequent calls after the first. I can't find any doc's that reference these two types of call handling, and how to program for such.

Thanks,
Ben

 

[vaoldschl]

Individual calls waiting light indicates calls have been placed to the extension of the console operator as opposed to the attendant group.

The calls to the attendant group should queue and light the "calls waiting" indicator. I don't believe they ring to the call appearances (a,b,c,etc) unless the attendant places an active call on hold but I'm not sure of that; I've never sat down and watched the work flow to be honest.

My theory, though, is call rings to 'a' and if attendant chats with caller on 'a' then 'b' won't light with next call but console will beep and "calls waiting" will light. If, however, attendant places 'a' on hold then 'b' will ring down next caller as the attendant console has become available.

 

[AvayaTier3]

http://support.avaya.com/css/P8/documents/003676332

calls to "attd" as defined on the dialplan go to the attendant queue

calls to the attendant extension are individual extension calls which is different than the attendant queue.

calls to hunt-group that has members that are attendant extension are using hunt-group queue.

vdn and attendant vectoring also change the way incoming calls are routed to attendants.

tenant partitioning can also affect all of this.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[ShikePoke]

Thanks both. I do have tenant partitions, so routing to "attd" would not work for all of them (there are 4). I'll review the document...thanks for the heads up.

Ben