An attendant is given an individual number known as the personal number with the code ATNDIND

Unlike user station terminals and trunk circuits, the Attendants are not yet ready for operation, they invariably have to be assigned to an ATND group (VFGR).

This is done using the VFGR AMO. Since night options are also assigned to every attendant terminal (at least one dummy option if night service is not provided), they have to be created beforehand with the NAVAR AMO.

The following night options can be assigned with the AMO NAVAR:

The VFGR AMO is used to allocate all the relevant ATNDs as well as night options to the ATND group to be set up.

A choice of the following type of attendants: AC4, AC-WIN and AC-WIN MQ. is made by the parameter ACTYPE in AMO ACSU.

For a group of AC-WIN MQs the AMO-VFGR has to create an attendant group with QUEMODE=MQ (multiple queue) whereas a group of other attendants (AC4, ACWin-4.x) is created via QUEMODE=DQ (double queue).

AC-WIN MQ attendants cannot be within the same attendant group with other type of attendants.

The night options are given a neutral number created in the NAVAR AMO and allocated in the ATNDGR as night option 1, 2 etc.

Once the ATND group has been defined it is assigned the codes:

It is necessary to assign the ATNDDID access code and also the ATND access code for every used attendant group (VFGR) via the AMO VFGKZ. The attendant group cannot be reached without the assignment of these access codes (even in case of intercept calls or personal calls to the attendant).

If an ATND group takes over the tasks of another ATNDGR as a night variant, it becomes a "Centralized Attendant Services" group (CASGR). This CASGR can be in the home system (CASINT) or in another node of a network (CASEXT).

An ITR group and/or DPLN group does not need to be specified unless access to the attendant terminal group is to be restricted. This is necessary, for example, if several customers share one system and one ATND group is set up per customer.

If all customers share a common attendant group, up to 1000 ATNDDID access codes can be assigned for incoming CO calls and for each access code a particular company name can be assigned.

This is done via AMO-ZAND, TYPE=ATND, COMP1000=YES and the appropriate AMO VFGKZ assignments for the access codes and the company names.

If the AMO-ZAND value COMP1000 is set to NO then up to 10 ATNDDID code numbers can be added per customer for incoming CO calls and each number (00-09) can be assigned to a particular company name (VBZGR AMO). Before the implementation of up to 1000 company names this limit was 10 company names. The limited option is kept in order to simplify the software upgrade of switches to a higher software release.

ATNDs can be added to, or deleted from, an ATND group any time; one ATND may not belong to more than one ATNDGR at a time. Night ATNDs are not supported anymore.

Special night answer stations (ANATE or DIGITE) can be assigned to several night options. Only one station (ANATE), which is assigned with the SSC AMO, is entered in the GENANS night option.

Before being deleted, day ATNDs, special night answer positions and GENANS positions must be cancelled from any groups to which they are assigned (ATNDGR, night option, hunting groups).

Before an ATNDGR is deleted, any code allocation and integration into the device search must be deleted with the VFGKZ AMO.

The overflow position option, (required when all positions of an ATNDGR are busy), is described in detail in the VFGR AMO Description. The individual attendant terminals can be assigned a name and an organizational unit under their respective call numbers using the PERSI AMO.

Up to 16 attendant groups can be configured in one system.

Special access authorizations must be entered for stations assigned as special night answer stations (using the AMO ZAND). When the night switch is active, the authorizations contained in COS1/COS2 of these stations are replaced by the authorizations defined with the AMO ZAND.