Good Afternoon All,
I came across a rather interesting issue with a T54W and wanted to share the findings as it was most unusual and initially made me think I broke something in FusionPBX, as it is also happening with a T53W; however after testing from a T46, that was not affected by this issue, it pointed to the Yealink Firmware.
Firmware on my T54W - 96.85.0.5
While on an active call pressing a DSSKey sends a call into a "void". The call remains active on FusionPBX, the caller hears nothing and the channel is open, but never makes an attempt to connect to the other phone. If SLA is being used it can pull the call back, but not from the phone where the transfer initiated from.
The workaround I am using is under the device (a profile can be used as well) is setting:
yealink_dsskey_transfer_mode = 1
This changes from the default of a blind transfer to attended and upon testing works to transfer a call.
I came across a rather interesting issue with a T54W and wanted to share the findings as it was most unusual and initially made me think I broke something in FusionPBX, as it is also happening with a T53W; however after testing from a T46, that was not affected by this issue, it pointed to the Yealink Firmware.
Firmware on my T54W - 96.85.0.5
While on an active call pressing a DSSKey sends a call into a "void". The call remains active on FusionPBX, the caller hears nothing and the channel is open, but never makes an attempt to connect to the other phone. If SLA is being used it can pull the call back, but not from the phone where the transfer initiated from.
The workaround I am using is under the device (a profile can be used as well) is setting:
yealink_dsskey_transfer_mode = 1
This changes from the default of a blind transfer to attended and upon testing works to transfer a call.