Terminating The Call, When Transferer Hangs Up The Call During Attended Transfer

Home » Asterisk Users » Terminating The Call, When Transferer Hangs Up The Call During Attended Transfer
Asterisk Users 10 Comments

Hello guys,

I’m vainly trying to figure out how to setup quite a strange customers requirement:

they require that when during attended transfer, (A->B->C)
whenever B hangs up the call before it’s connected to C, the call just returns to B, instead of changing to blind transfer.

I tried using atxfer drop call option (enabling null channel in sources), but to no avail..

Is there some way how this could be achieved?

thanks a lot for any help..

with best regards

nikola ciprich

10 thoughts on - Terminating The Call, When Transferer Hangs Up The Call During Attended Transfer

  • So:
    A calls B
    B answers B puts A on hold B calls C
    B talks to C
    B ends conversation with C
    B talks to A again, regardless

    I this correct? Looks like a simple “Hold” exercise.

    jg

  • Hello JG,

    thanks for your reply..

    not exactly, it’s rather something like:

    A calls B
    B answers B starts attended transfer (thus puts A on hold)
    B dials C
    B hangs up before C answers

    now I need call to C to be terminated, so I can ring back to B.

    n.

  • Ok, that’s called “blond transfer”, though this is how some Asterisk people coined this. Should work that way when using features.conf (DTMF).

    With “Hold” and “Transfer”, I don’t know. It probably depends on the phone. Which phones are your using?

    jg

  • Hi JG,

    hmm, yes, I’ve seen this term before 🙂

    However, the problem is, I don’t really want blond transfer to happen, I need to have call to C terminate immediately… but I’m not really sure this is achievable, since such scenario even doesn’t make that much sense.. 🙁

    unfortunately this can’t be phone speciffic, I can use only internal asterisk features…

    BR

    nik

  • in features.conf there is the option “Disconnect Call” that retrieves the call from callee C.

    Depending on your setup you may need to change it to something like “*0”. I don’t like single
    ‘*’ or ‘#’ keys as some of these combinations might trigger a reboot of some phone models.

    jg

  • Hello JG,

    thanks for your reply..

    not exactly, it’s rather something like:

    A calls B
    B answers B starts attended transfer (thus puts A on hold) B dials C B hangs up before C answers

    now I need call to C to be terminated, so I can ring back to B.

    n.

    Is B deciding C is unavailable and hanging up? In that case, rather than hanging up, B wants to abandon the transfer and recover the original call. Is that right?

    –Don

  • Hi Don,

    well, yes actually.. I know this can be achieved by using hangup/cancel transfer feature, but the request is, that “when the user is confused, he can always just hangup the call and A is returned to him automatically” 🙁

    n.

  • I think I got it now:

    While A is on hold, B dials C
    after a few seconds B wants to stop dialing C and hangs up,
    “the system” calls back and B is connected again with A

    Is that correct?

    If (yes) {
    I see a logical problem
    } else {
    please be more specific about the events
    }

    jg

  • yes, I think this is what is required…

    I THINK this makes a bit of sense, (A party starts ringing on B again), even though it’s quite ridiculous request 🙁

    in principle, I need to DISABLE blond transfer function and force the Dial to C party to be terminated, so I can ring back to B..

    do You think there is some way to achieve this?

    n.

  • You should know this, not think what it could be. Even if the customer doesn’t know what he wants, you will look stupid eventually, because you can’t deliver. It does not make any sense. The problem is, once the call has been been hung up and the phone starts to ring again, you somebody else might be on the other end of the line. I have a customer who had similar brilliant ideas before I taught them to use the “Disconnect Call” feature, but never ever hang up the receiver when using features.conf sequences. You need something like the
    “active” call to make things unique.

    If you hang up the receiver, then things are actually easier, but only if, your phones have the
    “Hold” and “Transfer” keys. The signaling is a bit different in this case. Dealing with both parties is then completely independent. The only problem is, while A is on hold, more calls can come in for B (limits do not solve this), which typically requires some training until the receptionist B is able to select the proper party for the transfer. No, don’t do that. Blond transfer is quite convenient. Tell them to use the “Disconnect Call”
    feature, but make sure it also works if the phone is in “ringing” state. Yes, there are several ways to do exactly this and all are ugly. I would not implement such a non-standard feature. Sooner or later you will get bitten by that. If you really need it, and someone is willing to pay some money for this nonsense, I could do it before next Fool’s Day.

    In your situation, it might be worthwhile to explore the parking option. B might stop to ring C
    because C might not have been the right person, so B continues with D. Parking typically makes sense, when it is not known a priori which extension eventually takes A’s call. You could even map the parking slot to LEDs on the phones for easy pickup. Essentially B can decide whether to continue with something else or get back to A, whatever.

    jg