Section 700 - Operation Chapter 7. SLT FeaturesS-ICX-50-700 S-ICX (International) issued October 2000 285Camping a Call Onto a Busy ExtensionOperationTo camp a call onto a busy extension:Hardware Requirements• N/ARelated 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 Extension Class of Service(COS).• If the call is not answered by the third party before the Transfer Recall Timer expires, the callwill recall to the transferring extension.• If a Transfer Recall is not answered before the Recall Duration Timer expires, the call will revertto 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) activated.• You can transfer a call to an extension that has Call Forwarding activated. The transferred callwill follow the call forwarding path of the extension it is transferred to. For example, if extension221 is forwarded to extension 225, calls that are transferred to extension 221 will be forwarded toextension 225.• Calls can be transferred from paging using supervised transfer.Camp-On (Call Waiting)DescriptionIf you dial a busy extension, you can camp onto that extension and send a Call Waiting signal to thecalled party. The called party then needs only to replace the handset and pick it up again to beAction Result1. While on a call, hookflash to place the call on hold. Intercom dial tone2. 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 (Call Waiting) code (default = 2 [UK/HK] or 2# [Taiwan, Malaysia, Indonesia]).Camp-on tone heard at called extension4. Complete the transfer by replacing the handset.
