Instruction manual

FEATURES AND SERVICES
Considerations
Callback Queuing saves time for users because they can avoid repeated redialing of busy
numbers. It
allows trunks to be used more efficiently and can reduce the number of trunks
required for a system.
The feature is similar to the Busy-to-Idle Reminder feature but applies to different types of
calls. The two features can both be used to reduce redialing effort.
A single-line voice terminal can queue only one call at a time.
Calls originated by using Personal Line, Direct Facility Access, and Direct Station Selection
buttons cannot be queued.
On calls to busy facilities,
Callback Queuing occurs only after Coverage, Following,
Forwarding, and Hunting have been attempted.
Interactions
The following features interact with Callback Queuing.
Account Code Entry: An account code entered before queuing is saved for SMDR.
Attendant Camp-On: Trunk calls camped onto a station by an attendant are given priority
over queued calls. Multiple camp-on calls are allowed per station.
Attendant Direct Extension Selection: Callbacks to the attendant do not flash at the
associated Selector Console.
Attendant Positions: The attendant can queue calls that are extended using the normal
START-RELEASE button operation.
However, calls originated using only the START button
(no other call put on hold) cannot be queued.
Attendant Message Waiting: An attendant active on a queued inside call can toggle the
MESSAGE LED of the queued-for station by pressing the ATTENDANT MESSAGE WAITING
button.
Automatic Route Selection (ARS): Implementation of Callback Queuing affects ARS in three
respects:
● On-hook ARS queuing is allowed.
● Callback Queuing and ARS share a common queue, which has a capacity of 64 calls.
● When a station without automatic queuing originates an ARS call, the caller hears
reorder tone if all routes are busy; the call can then be queued manually.
2-84