Unsupported Attended transfer not completed - Yealink T46s

[MetroAnakin]

Hi all,

I'm currently experiencing the following issue. The PBX is on V16 (Windows Intel NUC), the phones are on the latest version of firmware.

Caller A > rings Caller B
Caller B does an attended transfer via BLF to Caller C
Caller B hangs up the handset to complete the transfer.

The transfer is complete and Caller A and Caller C are both talking with each other however in the active calls section, it still shows that Caller B and Caller C are on a call.

You are unable to ring Caller B as it thinks it's still busy on a call.

 

[JohnS_3CX]

Hi MetroAnakin

That doesn't sound right to me, it's not the expected behavior in V16 or V18.
Once the transfer is complete, you should see the active calls update to show the new information of A talking to C.

I think you should read this first and provide more information on your installation. It might help us understand why this is happening: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[MetroAnakin]

Hi John, thank you for your reply.

My apologies here's the information on the current setup as I couldn't edit my original post.

Caller A = Mobile phone
Caller B = T46s (Reception phone)
Caller C = Analogue phone operating via TA3200 gateway.

• 3CX Version, Professional Annual 16.0.8.9
• Server OS, Windows 10 Intel NUC
• Is the 3CX Server Hosted and where? On-premise
• IP Phone Make/Model/Firmware version, Yealink T46s (66.86.0.15) & Yeastar TA3200 (47.0.0.54)
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model, Voyager SIP trunk (NZ)
• Has the Firewall Checker passed: Yes
• Are custom Phone Templates being used: No

 

[JohnS_3CX]

Can this be replicated if you use this method?

Caller A = Mobile phone
Caller B = T46S (Reception phone)
Caller C = Another T46S (or a Webclient extension)

 

[MetroAnakin]

Unfortunately it can't be replicated, when I use that method the transfer works as it's supposed to and only shows Caller A and Caller C talking in active calls.

It's the same if Caller B tries to transfer to a softphone extension also, that works perfectly fine.

 

[JohnS_3CX]

If it only happens when the FXS is involved in the call then I'm afraid the best I can recommend is switching to a supported device like the ones at the bottom of this page.