MERLIN LEGEND Communications System Release 6.1
Feature Reference
555-661-110
Issue 1
August 1998
Features
Page 110Callback
Transfer A queued callback call cannot be transferred, but calls transferred to busy
extensions are eligible for Callback. When a user reaches a busy
extension while transferring a call, he or she can use Automatic Callback
or Selective Callback to queue the call before completing the transfer.
The caller hears ringback or Music On Hold, if programmed, as with any
transfer. When the extension is available, the call is transferred to the
extension automatically. If the extension is not available before the
transfer return interval expires, the call is removed from the callback
queue and returned to the transfer originator.
UDP Features Callback queuing is supported for lines/trunks connected to the caller’s
local system, including private network tandem trunks. When a call is sent
across the network and a non-local system’s trunks are busy, the caller
cannot queue the call using Callback.
When an extension has Automatic Callback turned on and originates a
call to a non-local extension, the call is queued at the local system for
Route 1 only. If all routes are busy, the caller hears callback tone. If the
caller is using ARS or the non-local dial plan to call out over trunks
connected to a remote system and the outside facilities at the remote
system are busy, the caller hears the fast busy tone. The caller hears the
busy tone if he or she is calling a busy non-local dial plan extension.
Neither call activates callback queueing because the caller is not
connected to the system from which the busy condition originates.
If a caller attempts Selective Callback upon hearing a busy tone and the
busy condition is not derived from the originating system, Selective
Callback has no effect. A caller can use Selective Callback to queue for
Route 1 when all local routes for a networked call are busy.
To Next Page
Loading...
Need help?
General
