GDND Configuration and Activation

The Group Do Not Disturb (GDND) feature allows an authorized user, which can be PBX-operator or an extension with master extension CoS, or a generic extension with Group DND programming category, to mark a pre-defined group of extensions as having the GDND function active, i.e. calls to extensions in the group will not be alerting/ringing the terminals.

An extension can be set as a member of a Group Do Not Disturb group by an I/O-command. Both generic and non-generic extension numbers, ODN, and ADN/EDN can be set as members.

Note: Group do not disturb can also be configured with MX-ONE Service Node Manager.

When primary analog extensions are associated with a GDND group, all secondary numbers will automatically be set as group members.

Activation of the Group Do Not Disturb (GDND) feature for a group of extensions is done with a procedure from a PBX-operator, from a master extension (for ATS, DTS), or from a generic extension with Group DND programming category.

If the extension (with GDND) also has any diversion or Personal Number activated, or an individual divertee position exists, the call will be re-directed. The activation is done separately for each group.

Group Do Not Disturb cannot be activated for master extensions, extension with Group DND programming category, or alarm extensions.

The Multi Directory Diversion/DND (MDD) facility enables SIP extension (Mitel 6900/6800/6700 terminal models) users to activate/deactivate DND easily without doing the procedure for each EDN on the instrument.

A class of service, affiliated to the ODN, controls if the SIP extension has Multi Directory Diversion/DND facility or not. Note that this class of service affects DND and also the diversion activation of the EDNs. See the description for Diversion for details on the MDD feature.