AT&T MERLIN LEGEND Release 4.0 Feature Reference page 468

Feature Reference
When a system includes QCCs, the first MLX module used to connect QCCs
must be installed in the control unit to the left of any other type of module with
extension jacks. A QCC can be connected only on the first and fifth extension
jack on each MLX module.
Unless calls to unassigned extension numbers received on DID or dial-in tie
trunks or from remote access users are programmed to go to a backup position,
and the QCC queue is programmed as the backup position for these calls,
assigning a QCC operator to receive the calls does not cause the calls to ring
into the queue.
Trunks cannot be programmed to ring both into the QCC queue and into a
calling group.
Trunks assigned to ring into the QCC queue can also be assigned as personal
lines on one or more telephones.
When a QCC operator wants to make an outgoing call, he or she should press
the Position Busy button before pressing the Hold button for an existing call.
This makes the console temporarily unavailable for calls from the queue. (The
operator can receive calls forwarded or made to the operator's individual
extension number.) If the operator presses only the Hold button, the position is
still available for calls and a call can be delivered from the queue. Receipt of a
call at this time can prevent the operator from making the outgoing call or cause
the call ringing on the console to remain unanswered until the operator finishes
the outgoing call.
Voice announcements do not come over QCC speakerphones.
QCCs have no programmable buttons (all features are factory-assigned) and
cannot use feature codes.
If a QCC operator receives a call and another user joins the call by using a
shared personal line or Shared SA button, the QCC operator can press the
Start button to begin the direction process and then press the Join button to
connect all three parties in a conference call. However. the operator cannot
release the call; the QCC operator sees the
on the screen.
When a QCC operator is assigned to receive calls on a tie trunk (excluding
dial-in tie trunks), and the caller at the other system uses the trunk and dials
the call is treated as an unassigned DID call. The QCC operator who receives
the call sees
on the display, instead of seeing
In Release 3.1 and later, if a station is changed from a Direct-Line Console to a
Queued Call Console, pool dial-out codes are disallowed on the QCC. You must
reprogram the system if you want to allow access to dial-out codes on the QCC.
468
Queued Call Console
as the call type (along with the trunk label and trunk number)
DID#
Dial 0
Denied: Cannot Release
as the call type.
message
,
0