268 DBS 576 (USA), Revised 6/11/98 576-13-700
Chapter 7. SLT Features Section 700 - Operation
Camping a Call Onto a Busy Extension
Operation
To camp a call onto a busy extension:
Hardware Requirements
•N/A
Related Programming
FF1-0-03: Extension COS (Onhook Transfer at Ringback)
FF1-0-03: Extension COS (Onhook Transfer at Talk)
FF1-0-03: Extension COS (Onhook Transfer at Camp-on)
Considerations
On-Hook Transfer must be enabled for the transferring party’s Extensio n Class of Servic e
(COS).
If the call is not answered by the third party before the Transfer Recall Timer expires, the call
will recall to the transferring extension.
If a Transfer Recall is not answered befo re the Recall Duration Timer expires, the call will revert
to the Attendant group.
If the called party does not exist, the call recalls to the transferring extension.
You cannot transfer a call to an extension that has Do-Not-Disturb (DND) activate d.
You can transfer a call to an extension that has Call Forwarding activated. The transf erred call
will follow the call forwarding path of the extension it is transferred to. For example, if extension
221 is forwarded to extension 225, calls that are transf erred to extension 221 will be forwarded to
extension 225.
Calls can be transferred from paging using supervised transfer.
Camp-On (Call Waiting)
CPC-96, CPC-288, and CPC-576 Version 1.0
Description
If you dial a busy extension, you can camp onto that extension and send a Call Waiting signal to the
called party. The called party then needs only to replace the handset and pick it up again to be
Action Result
1. While on a call, hookflash to place the call on hold. Intercom dial tone
2. Dial the extension number to which the call is to be trans-
ferred.
3. If your extension does not have Auto Camp-On activated,
enter the Camp-On (Cal l Waiting) code (default = 2). Camp-on tone heard at called extension
4. Complete the transfer by replacing the handset.