blind transfer set up for CM 6.1

Unanswered Question
Oct 17th, 2008

Can anyone give me the link to set this up? I would like to set up blind transfer. This is done in the gateway?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
allan.thomas Fri, 10/17/2008 - 06:41

Call transfers can be blind or consultative.

A blind transfer is one in which the transferring extension connects the caller to a destination extension before ringback begins.

A consultative transfer is one in which the transferring party either connects the caller to a ringing phone (ringback heard) or speaks with the third party before connecting the caller to the third party.

There is nothing specific in the configuration for blind transfer. You simply dial the extension you wish the connected party to be transfered to, and when you hear ringback press the transfer softkey again. This is referred to as a blind transfer.

Is this what you are referring too?



Pls rate helpful posts.

patty_spieker Fri, 10/17/2008 - 06:53

Actually I am referring to when you transfer to ext. you pressess transfer once and ext and hang up. I come from the PBX world and we were able to do that. The system is set up now I have to hit transfer ext and transfer again which we call supervise transfer.

Jaime Valencia Fri, 10/17/2008 - 07:00

enable it via service parameter

Service > Service Parameters > CallManager > Transfer On-hook enabled



if this helps, please rate

allan.thomas Fri, 10/17/2008 - 07:15

Further to the good information provided by Java, below is an extract from the CUCM Systems Guide about the On-hook transfer.

Onhook Call Transfer

The Call Transfer feature supports the onhook (hangup) action as a possible last step to complete a call transfer. You must set the Transfer On-hook Enabled service parameter, which enables onhook call transfer, 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 Unified 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 Unified Communications Manager 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 onhook call transfer implementation, user B can hang up after dialing the number of user C, and the transfer completes. Both the existing and new implementations work in 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.

Taken from this document:-




This Discussion