Mitel SX-200 Documentation page 104

SECTION MITL9105/911
AUTOMATIC CALLBACK - DON'T ANSWER
Page 50
Description
This feature allows an extension user, upon encountering an extension
which does not answer, to have the call completed after the called
extension has gone off-hook and on-hook After the feature has been
activated, the system continuously monitors the originating extension
and the required number. After the called extension goes off-hook, the
callback will be handled in
Busy. If more than one callback request is active on any extension, the
requests are queued and serviced on a first-in, first-out basis. All
callbacks may be cancelled
Conditions
An individual callback cannot be cancelled by the station or the
Attendant.
A callback will always ring the originating extension; Call For-
warding has no effect.
Automatic Callback may
hunt group access codes but not trunks or trunk groups.
Up to 30 callback requests may be active within the system at
any time.
If the two parties involved in a callback hold a conversation (not
a conference) before the callback is honoured, the callback will
be cancelled automatically.
Duplicate callback requests are ignored. (The original callback
request is cancelled.)
If a callback is not answered by the originating extension within
six rings, it is automatically cancelled.
If the called party becomes busy before the originating party
answers a callback the originating pa* will hear busy tone and
may dial the Callback - Busy
Programming
Originating extension's COS must include Option Number 33
l
(Automatic Callback).
Assign an access
l
Answer). This code may not
plan.
Operation
To set up an Automatic Callback - Don't Answer:
Dial the required
l
answer.
Flash the switchhook - dial tone is returned.
l
the
same way as an Automatic Callback -
from
the Attendant Console.
be
activated on extension numbers and
code.
code to Feature Number 2 (Callback - Don't
conflict
with the system numbering
extension number