Destination
Availability
DISA
Analogue/ISDN Remote Maintenance
Idle Line Access no. + Phone no.
Trunk Group Access no. + Trunk Group no. + Phone no.
Other PBX Extension (TIE with no PBX Code)
Other PBX Extension (TIE with PBX Code)
*1
If the transfer destination does not answer, the call is sent to Voice Mail and a message can be recorded in the mailbox of the transfer
destination.
Conditions
•
When an extension is transferring a party to another destination, the party will be in consultation hold until
they reach the transfer destination.
Consultation Hold:
a condition that a party is in, when an extension is calling other parties in order to
perform Call Transfer, Conference, or Call Splitting.
In Consultation Hold, the original call is treated as if it is on hold, allowing the extension to call a third party
all on one line. In Call Hold, the party on hold and the third party are connected to the extension using
separate lines.
•
If Music on Hold is enabled, music can be sent to the held party while the call is transferred. (
®
on Hold) It is programmable whether a ringback tone or music is sent.
•
If the transfer destination extension has set FWD to an outside party, the call will be transferred to the
outside party. (
®
•
COS programming determines the extensions that are able to transfer a call to an outside party. COS can
also prohibit transferring to an extension of another PBX via the TIE line service using the PBX Code
method (Access with PBX Code) (
®
•
One-touch Transfer
One-touch Transfer can be performed by pressing a One-touch Dialling button that has been assigned the
TRANSFER command and the telephone number of the transfer destination. This is useful for transferring
calls to an outside destination. (
®
•
Automatic Transfer by SDN Button or DSS Button
Pressing an SDN button or DSS button during a conversation with an extension or outside party can
automatically transfer the call to the specified destination (
®
2.9.1 Primary Directory Number (PDN)/
Secondary Directory Number (SDN) Extension). It is possible through system programming to prevent this
feature from operating for extension to extension calls.
•
Transfer to Busy Extension using Queuing (Camp-on Transfer)
Through system programming, it is possible to enable the transferring of a call to a busy extension without
needing to send a call waiting notification, based on the transferring party’s COS setting. The transferred
call will be placed in a queue.
This feature is not available for SIP extensions.
•
When transferring a call from an analogue trunk, users are strongly recommended to perform a screened
transfer, so that the outside caller is not automatically connected to an extension using Hands-free
Answerback when the extension user is absent.
•
If a KX-UT series SIP phone user disconnects a call while the party to be transferred is still on consultation
hold (i.e., has not been transferred), Hold Recall is heard at the extension immediately (
®
Hold). On other types of extensions, Hold Recall is heard after the Hold Recall timer expires.
•
This PBX supports the Blind transfer feature found on some SIP phones. For details, refer to the phone’s
documentation.
188
Feature Guide
2.12.1 Call Transfer
Summary of Contents for KX-NS300
Page 14: ...14 Feature Guide Table of Contents ...
Page 15: ...Section 1 For Your Safety Feature Guide 15 ...
Page 18: ...18 Feature Guide 1 1 1 For Your Safety ...
Page 19: ...Section 2 Call Handling Features Feature Guide 19 ...
Page 107: ...User Manual References 1 2 1 Basic Calling Feature Guide 107 2 5 4 Trunk Call Features ...
Page 193: ...User Manual References 1 4 2 Holding a Call Feature Guide 193 2 13 1 Call Hold ...
Page 324: ...324 Feature Guide 2 30 2 Outgoing Message OGM ...
Page 325: ...Section 3 Unified Messaging System Feature Guide 325 ...
Page 375: ...Section 4 Network Features Feature Guide 375 ...
Page 464: ...464 Feature Guide 4 3 6 Network ICD Group ...
Page 465: ...Section 5 System Configuration and Administration Features Feature Guide 465 ...
Page 560: ...560 Feature Guide 5 6 7 PING Confirmation ...
Page 561: ...Section 6 Appendix Feature Guide 561 ...
Page 578: ...578 Feature Guide 6 5 2 PFMPR Software File Version 004 2xxxx ...
Page 579: ...Feature Guide 579 Notes ...