cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3955
Views
5
Helpful
10
Replies

One button transfer

flash2200
Level 1
Level 1

Receptionist at client site is equipped with 7961 and 7914 expansion. She wants to be able to transfer calls to CEO on demand just by hitting one button on 7914(which must in turn be some how predefined to transfer the caller to the extension fo the CEO.)

She is basically not happy with having to hit the transfer softkey, enter the CEO's ext (Or hit his speed dial) and then having to press Transfer again.

She wants a faster one button transfer method to him.

Any ideas on how this might be setup if possible at all? TIA

10 Replies 10

Rob Huffman
Hall of Fame
Hall of Fame

Hi Steven,

Sadly there is no "one button" Transfer method. The quickest possible is "two button" using On-Hook Transfer;

Have you enabled the "On Hook" Transfer? Have a look at how it works;

Transfer a call without talking to the transfer recipient

Press Trnsfer and enter the target number. When you hear the call ringing, hang up **(If On Hook Transfer Enabled).

If your system administrator did not enable on-hook transfer, you must press Trnsfer again to complete the transfer. To cancel the transfer, press EndCall.

Tips

When "on-hook" transfer is enabled, you can either hang up or press Trnsfer, then hang up.

If on-hook transfer is not enabled on your phone, be aware that hanging up instead of pressing Trnsfer cancels the transfer action and places the party to be transferred on hold.

You cannot use Trnsfer to redirect a call on hold. Press Hold to remove the call from hold before transferring it

From this 4.1.3 doc;

http://www.cisco.com/en/US/products/hw/phones/ps379/products_user_guide_chapter09186a0080403ad0.html#wp1007824

Onhook Call Transfer

Modifications to the Call Transfer feature add the onhook (hangup) action as a possible last step to complete a call transfer. The Transfer On-hook Enabled service parameter, which enables onhook call transfer, must be set to True for onhook call transfer to succeed. If the service parameter is set to False, the onhook action ends the secondary call to the third party.

In the existing implementation, if user B has an active call on a particular line (from user A) and user B has not reached the maximum number of calls on this line, the Cisco IP Phone provides a Transfer softkey to user B. If user B presses the Transfer softkey (or Transfer button, if available) once, user B receives dial tone and can make a secondary call: user B dials the number of a third party (user C). Cisco CallManager provides a Transfer softkey to user B again. If user B presses the Transfer softkey again (or Transfer button, if available), the transfer operation completes.

With the new onhook call transfer implementation, user B can hang up after dialing user C's number, and the transfer completes. Both the existing and new implementations work in both the case of a blind transfer (user B disconnects before user C answers) and also in the case of a consult transfer (user B waits for user C to answer and announces the call from user A).

The previous implementation remains unchanged: user B can press the Transfer softkey twice to complete the transfer.

From this doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803edb46.html#wp1088627

Hope this helps!

Rob

Rob Huffman
Hall of Fame
Hall of Fame

Hi Steven,

Sadly there is no "one button" Transfer method. The quickest possible is "two button" using On-Hook Transfer;

Have you enabled the "On Hook" Transfer? Have a look at how it works;

Transfer a call without talking to the transfer recipient

Press Trnsfer and enter the target number. When you hear the call ringing, hang up **(If On Hook Transfer Enabled).

If your system administrator did not enable on-hook transfer, you must press Trnsfer again to complete the transfer. To cancel the transfer, press EndCall.

Tips

When "on-hook" transfer is enabled, you can either hang up or press Trnsfer, then hang up.

If on-hook transfer is not enabled on your phone, be aware that hanging up instead of pressing Trnsfer cancels the transfer action and places the party to be transferred on hold.

You cannot use Trnsfer to redirect a call on hold. Press Hold to remove the call from hold before transferring it

From this 4.1.3 doc;

http://www.cisco.com/en/US/products/hw/phones/ps379/products_user_guide_chapter09186a0080403ad0.html#wp1007824

Onhook Call Transfer

Modifications to the Call Transfer feature add the onhook (hangup) action as a possible last step to complete a call transfer. The Transfer On-hook Enabled service parameter, which enables onhook call transfer, must be set to True for onhook call transfer to succeed. If the service parameter is set to False, the onhook action ends the secondary call to the third party.

In the existing implementation, if user B has an active call on a particular line (from user A) and user B has not reached the maximum number of calls on this line, the Cisco IP Phone provides a Transfer softkey to user B. If user B presses the Transfer softkey (or Transfer button, if available) once, user B receives dial tone and can make a secondary call: user B dials the number of a third party (user C). Cisco CallManager provides a Transfer softkey to user B again. If user B presses the Transfer softkey again (or Transfer button, if available), the transfer operation completes.

With the new onhook call transfer implementation, user B can hang up after dialing user C's number, and the transfer completes. Both the existing and new implementations work in both the case of a blind transfer (user B disconnects before user C answers) and also in the case of a consult transfer (user B waits for user C to answer and announces the call from user A).

The previous implementation remains unchanged: user B can press the Transfer softkey twice to complete the transfer.

From this doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803edb46.html#wp1088627

Hope this helps!

Rob

Thanks Rob,

Maybe in the next version :) Thanks for your help as always.

It's possible with CME now :)

And how? Please explain?

Thanks

I would be interest as well....

sticano
Level 1
Level 1

I had a similar request from an admin. I created a speed dial for her, so now she has a 2 button transfer.

Here is a 1 touch version for call forward all to a mobile cell phone.

Under the ephone configure a speed-dial, like this. You need to activate, Feature Access Code under telephony-service.

speed-dial 1 **17284# label "Callforward Mobile"

The number 7284 is the mobile number.

Configure the speed-dial to a free button on your phone and there you go.

Regards.

Hey Folks,

This is the closest thing that is available in CME;

In Cisco Unified CME 4.0(2) and later versions, the DSS (Direct Station Select) Service feature allows the phone user to press a single speed-dial line button to transfer an incoming call when the call is in the connected state. This feature is supported on all phones on which monitor line buttons for speed dial or speed-dial line buttons are configured.

When the DSS service is enabled, the system automatically generates a simulated transfer key event when needed, eliminating the requirement for the phone user to press the Transfer button.

From this excellent doc;

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmespeed.html#wp1035362

Hope this helps!

Rob

Hi everyone,

I've used DSS feature since CCME 4.0(2) but unfortunately it changed its behavior in CCME 4.1 (IOS 12.4(15)T5). Now, pressing monitor line button when the call is in connected state doesn't transfer the call in "one touch" as previously but only activates transfer mode. Meanwhile DSS for speed-dial buttons works in the same way as previously, i.e. in "one touch".

Has anyone encountered the same problem?

Regards,

Andrey

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: