Disable "recall" transfers

[lukeescude]

When doing a blind/attended transfer, and the target phone does not pick up, the call comes back to the receptionist as "RECALL"

How do we disable this? We just want it to go to voicemail.

[Jensen_Yealink]

Hi Lukeescude,

We have a configure feature that can disabled the "Recall", please testing with below:
transfer.hang_up_after_success_trans=4
thank you.

[lukeescude]

Jensen, it did not work - In fact that option doesn't seem to help at all.

Any other suggestions?

[jolouis]

This sounds like the PBX handing the call back to the caller rather than something the phone itself is doing. Not sure what PBX you're using so can't say for sure, but typically a "Recall" is when you Park a call and after a given amount of time nobody else picks it up. It gets sent back to you as a courtesy so the caller doesn't get lost in space forever, and you have the chance to try sending them to somebody else or doing a page/etc.

Even if it is happening due to direct transfers I would still expect it to be the PBX determining how to handle things, so check that side for your answer.

[lukeescude]

It's definitely happening due to direct transfers - our PBX (Asterisk, with our own cloud PBX software managing it) properly handles callbacks from call parking timeouts.

Apparently the phone is receiving a 503 Service Unavailable from the PBX in a NOTIFY event, which triggers this behavior.

Can we get an option to completely disable recall? Or simply ignore the 503 in response to a transfer?

This doesn't happen with any other phone manufacturer, which is weird.

SIP RFC 3515 s. 2.4.5:
A minimal, but complete, implementation can respond with a single
NOTIFY containing either the body: SIP/2.0 100 Trying
if the subscription is pending, the body: SIP/2.0 200 OK
if the reference was successful, the body: SIP/2.0 503 Service Unavailable
if the reference failed, or the body: SIP/2.0 603 Declined
if the REFER request was accepted before approval to follow the reference could be obtained and that approval was subsequently denied
(see Section 2.4.7).

[lukeescude]

There has to be a way to disable this annoying "feature". Grandstreams and Polycoms do not do this.

[necits2015]

This looks to be a Yealink bug. Please see the following post
https://community.asterisk.org/t/transfe...ents/69764

[Fraukas2]

Hello,

If anyone is looking for the answer, the option "transfer.hang_up_after_success_trans" is the right one. On my end, the value "4" wasn't working either, but "3" is working correctly.

Code:

transfer.hang_up_after_success_trans = 3

[BWIEBE]

(11-20-2019 04:31 PM)Fraukas2 Wrote:  Hello,

If anyone is looking for the answer, the option "transfer.hang_up_after_success_trans" is the right one. On my end, the value "4" wasn't working either, but "3" is working correctly.

Code:

transfer.hang_up_after_success_trans = 3

Thank you for that

I copy and pasted "transfer.hang_up_after_success_trans = 3" in the transfer section of the auto config and is working perfectly for us.