Instruction manual

Meridian 1 Attendant Console Enhancements Page 2019 of 3156
Features and Services
The DN programmed on the Autoline key is not verified for validity during
configuration. If the DN is invalid, the attendant receives an overflow tone
when the Autoline key is used.
The Attendant Autoline key lamp always remains dark.
Individual Attendant Console Directory Number (IADN)
IADN functionality is supported on digital Attendant Consoles (M2250)
only.
IADNs must be unique DNs. Therefore, they cannot be Multiple Appearance
DNs.
The IADN is a way to contact an attendant and not a DN key. Hence, when
an attendant originates a call, the IADN is not relevant.
The IADN can be programmed from the existing range of DID numbers
purchased by the customer.
The Calling Party Name Display (CPND) associated with an IADN is the
same as the CPND associated with the Attendant DN.
When an IADN call is placed to a particular attendant when the customer/
tenant is in Night Mode, the call receives standard Night treatment as defined
for the Customer. During Night Treatment, the call has no priority over other
calls in the queue.
As per existing operation, when an attendant places an IADN/LDN call on
hold and the system initializes, the IADN/LDN call that is on hold is lost.
As per existing operation, when there is an IADN/LDN call in the attendant
queue and the system initializes, all calls in the queue are dropped.
The Call Waiting lamp on the Attendant Console reflects the IADN calls
waiting in the attendant queue.
When an IADN call is placed in the attendant queue, a maximum of a two
second delay may occur before Priority Buzzing begins.