Transferring Features

2.12.1 Call Transfer

Description

An extension user can transfer a call to another extension or an outside party. The following features are available:

Feature Transferring method

With Announcement Transfer is completed after announcing the destination party.

Without Announcement

Transfer is completed without an announcement.

After dialling the destination, while hearing a ringback tone, the originator can replace the handset.

Call Transfer with Announcement is also known as Call Transfer—Screened.

Call Transfer without Announcement is also known as Call Transfer—Unscreened.

Transfer Recall for Call Transfer without Announcement

If the transfer destination does not answer within the preprogrammed Transfer Recall time, the call will be redirected to the Transfer Recall destination assigned to the extension which transferred the call.

If the transfer destination has a destination set as Intercept Routing—No Answer, the call will be routed to that destination.

A call is transferred without announcement.

No

Does the transferrer have a Transfer Recall

destination assigned?

Yes

The Transfer Recall timer is started.

Is the first transfer destination an extension?

Does the first transfer destination have a destination set as

Intercept Routing No Answer?

Yes

Yes

Is the intercept destination an extension, ICD group, centralised VM, or UM group?

The set extension, ICD group, centralised VM, or UM group is memorised as the Transfer Recall destination.

Yes

Is the recall destination an extension, ICD group, or UM

group?

The set extension, ICD group, or UM group is memorised as the Transfer Recall destination.

No

The transferrer is memorised as the Transfer Recall destination.

Wired Extension (PT/SLT/SIP Extension/ISDN Extension) ü

PS ü

Incoming Call Distribution Group ü

PS Ring Group

UM Group ü^*1

External Pager (TAFAS) DISA

Destination Availability 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. (® 2.13.4 Music 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. (® 2.3.2 Call Forwarding (FWD))

• 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) (® 4.3.1 TIE Line Service).

• 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. (® 2.6 Memory Dialling Features)

• 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.

• 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 (® 2.13.1 Call Hold). On other types of extensions, Hold Recall is heard after the Hold Recall timer expires.

PC Programming Manual References

10.2 PBX Configuration—System—Operator & BGM— BGM and Music on Hold—Sound on Transfer 10.3 PBX Configuration—System—Timers & Counters—Dial / IRNA / Recall / Tone— Recall—Transfer Recall

10.7.1 PBX Configuration—System—Class of Service—COS Settings—CO & SMDR— Transfer to CO 10.7.1 PBX Configuration—System—Class of Service—COS Settings—Assistant— Transfer to busy Extension w/o BSS Operation

10.9 PBX Configuration—System—System Options—Option 4— DSS Key—Automatic Transfer for Extension Call

12.1.1 PBX Configuration—Extension—Wired Extension—Extension Settings—Option 1— Transfer Recall Destination

12.2.1 PBX Configuration—Extension—Portable Station—Extension Settings—Option 1— Transfer Recall Destination

Feature Guide References

5.1.1 Class of Service (COS)

User Manual References

1.4.1 Transferring a Call (Call Transfer)