Attendant VDNs

Last Updated : Sep 08, 2012 |

Prolog information

Metadata

Keywords:

The fact that VDN extensions can be dialed directly or calls can be transferred to VDN extensions is unchanged for attendant VDNs.

Currently, VDN extensions can be assigned to the following night destinations:

Hunt group

An attendant vectoring VDN can be assigned as the night destination of a hunt group. Calls to the hunt group when it is in night service are redirected to the VDN and attendant vectoring applies. Hunt group night service does not apply if the hunt group is vector controlled. When vector on the Hunt Group screen is y, the night service destination field is removed from the screen. In order for a hunt group to be available in vectoring for the queue-to hunt-group command, the hunt group must be vector controlled. The hunt group in the route-to command can be in night service and the call can terminate to the indicated night service destination. If the hunt group is accessed using the queue-to hunt-group command no night service applies.

LDN and trunk

One or all trunk groups can be placed into night service and an attendant vectoring VDN can be assigned as the night service destination of the LDN or trunk group. If a night destination is assigned for LDN calls, it overrides the trunk night destination of the trunk group. Either of these destinations can be an attendant vectoring VDN. However, if Tenant Partitioning is administered and the trunk group night service destination is the attendant group, the call is redirected to the VDN associated with the tenant number of the trunk group. If, instead, the night service destination is explicitly assigned to a particular attendant vectoring VDN, it cannot be the resulted VDN had the night destination been the attendant group.

Trunk group incoming

The incoming destination can be an attendant vectoring VDN except for RLT trunk groups. As in trunk group night service, an assigned incoming destination to an attendant vector can result in the call being sent to a different VDN than if the destination had been assigned to the attendant group.

Last coverage point in a coverage path

An attendant VDN can be assigned as a coverage point. If an attendant VDN is assigned as a coverage point, the VDN be the last point in the coverage path.

Abbreviated dialing lists

Attendant VDNs can be assigned to abbreviated dialing lists.

Emergency access redirection

An attendant VDN can be assigned to emergency access redirection. When the attendant’s emergency queue overflows or when the attendant group is in night service, all emergency calls are redirected to this VDN. Careful thought must be given to routing the calls off-switch.

QSIG CAS number for attendant group calls

An attendant VDN can be assigned the QSIG CAS number which determines where attendant group calls at a QSIG branch are processed. This allows local vectoring at a branch prior to routing the calls to the main or elsewhere.

Auxiliary data for the following button assignments

In keeping with existing procedures, attendant VDNs is not denied as auxiliary button data for:

Facility busy indication. Visual indication of busy or idle status for the associated extension.
Manual message waiting indication. Lights a message waiting lamp on the station associated with the button.
Manual signaling. Rings the station associated with the button.
Remote message waiting indicator. Message waiting status lamp automatically lights when a LWC message is stored in the system for the associated extension.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found