Instruction manual

Page 2026 of 3156 Meridian 1 Attendant Console Enhancements
553-3001-306 Standard 10.00 January 2002
Call Redirection features
Whenever an IADN call is made as a result of Call Redirection, this call
receives the standard IADN treatment (i.e. Priority Buzzing and IADN ICI).
The Attendant IADN feature does not distinguish between forwarded calls
and direct dial IADN calls.
Hunt
If an IADN is defined as part of a Hunt chain, calls terminate to the IADN,
following the Hunt chain. Once a call is placed in the attendant queue,
however, the next DN in the Hunt chain is not sought.
If the IADN console is in Position Busy, the call is presented to any one of
the available attendants in the Customer/Console Presentation Group.
Therefore, the next DN in the Hunt chain is not sought once an attempt is
made to present the call to the IADN attendant.
Message Center
If an IADN is given as an MWK DN, the Message Waiting calls receive
IADN treatment. Therefore, Priority Buzzing is provided, and the IADN ICI
key is lit (if configured).
Multi-Tenant Service
Sets belonging to a Customer can be divided into customer subgroups known
as tenants. A set belonging to one tenant can call an attendant belonging to
another tenant by dialing the attendant’s IADN. The IADN functionality
takes precedence over the Multi-Tenant Service feature.
Network Attendant Service
Network Attendant Service (NAS) treatment is applied when the Customer/
Console Presentation Group is in Night mode. An IADN call rerouted via
NAS loses its priority at the remote node.
If the NAS ID of one node is defined as the IADN/emergency code number
of the remote node, priority treatment is provided to all redirected calls,
including IADN/emergency code calls. In this case, the IADN ICI key has a
higher precedence than the corresponding NAS ICI key.