| Callback A Callback can be placed to a busy or idle extension or to a busy
exchange line or trunk route. When the extension or exchange line is available for access,
a callback is made to the originating extension. The two types of callback are described
below. This feature differs from a camp-on call in that the originator goes off-hook after
placing the callback.
Callback - Busy (Suffix 5)
A callback request may be placed to a busy extension, exchange line or trunk route. When
the wanted extension, exchange line or trunk route becomes free, the extension that
initiated the callback is signalled. They can go off-hook to automatically place a call to
the now-idle extension or to seize the wanted exchange line or to access a free line in
the desired trunk route.
Callback - Idle (Suffix 5)
If a callback request is placed at an extension that does not answer, he next time that
the called extension goes off-hook and then on-hook, the extension that placed the
callback is signalled and can go off-hook to automatically place an intercom call to the
wanted extension.
| Benefits |
Using this feature saves both time and labour. A user
attempting a connection to a busy or not-answering resource does not have to waste time
and effort repeatedly recalling that resource to see if is now available. |
|
