“Call using” behaviour change between firmware 96.86.0.72 and 96.86.100.5

[SeanT]

Hi,

When using the 3CX desktop app to make a call, with “Call using” set to the Yealink handset;

• If the phone has firmware 96.86.0.72 the phone immediately dials the number entered, the caller hears the dialling tones, the number is displayed on the handset.
• If the phone has the latest firmware 96.86.100.5, 3CX calls the handset, “Make Call” is displayed as the CID. When answered, the caller hears hold music until the callee answers.

Is this expected? Is there a way to revert it back?

Thanks



3CX Version Number 18.0 (Build 415)

Yealink T54W

Old firmware: 96.86.0.72

Latest firmware: 96.86.100.5

The phone and PBX are local.

 

[JohnS_3CX]

Hi,

We are investigating this at the moment and will get back to you.

 

[adamsmithbz]

Hi Team,

Is there any update on this as we also have customers being affected by this firmware change?

 

[JohnS_3CX]

Currently under investigation by Yealink, we will update you here as soon as we get news on the subject.

 

[DavidFPM]

Hi,

Having the same issue, glad to know it is being investigated, this was a bit of a shock!

Thanks

 

[DMitchell]

@JohnS_3CX while this may be a firmware issue 3CX hosted doesn't allow us to disable updates. We found that replacing them with the previous firmware solves the problem however 3CX is automatically updating the firmware to this latest faulty release so we're right back to where we started.
If this issue isn't resolved today or tomorrow we believe 3CX bears a responsibility for at least removing this update from their update library so we can use the previous firmware.

 

[Evolute IT]

@JohnS_3CX while this may be a firmware issue 3CX hosted doesn't allow us to disable updates. We found that replacing them with the previous firmware solves the problem however 3CX is automatically updating the firmware to this latest faulty release so we're right back to where we started.
If this issue isn't resolved today or tomorrow we believe 3CX bears a responsibility for at least removing this update from their update library so we can use the previous firmware.

Little note: you can remove the recent firmware yourself. Connect to the PBX (via either SSH or RDP) and go to the 3CX Data Instance1 under Http/Interface/Provisioning/<random>/firmware/yealink and delete the file for your model. Make sure to delete it also from the firmware_new folder and don't redownload it. Then, manually downgrade the others.

 

[DMitchell]

Thank you for the quick reply. We are aware of this however it was my understanding that 3CX Hosted instances (those 3CX hosts) do not allow SSH.

Has this changed?

 

[Evolute IT]

Thank you for the quick reply. We are aware of this however it was my understanding that 3CX Hosted instances (those 3CX hosts) do not allow SSH.

Has this changed?

Oh if you're hosted by them, you're stuck. Maybe they can SSH into it and do it for you in the meantime.

That's why we host ourselves. Keeping full control.

 

[JohnS_3CX]

@JohnS_3CX while this may be a firmware issue 3CX hosted doesn't allow us to disable updates. We found that replacing them with the previous firmware solves the problem however 3CX is automatically updating the firmware to this latest faulty release so we're right back to where we started.
If this issue isn't resolved today or tomorrow we believe 3CX bears a responsibility for at least removing this update from their update library so we can use the previous firmware.

It has has been removed, but your PBX already downloaded it.

For 3CX-Hosted instances, please contact our Support team and they can take care of it.

 

[BrenttG]

We are now being affected by this as well, and currently 1,977 of our total 3,785 Endpoints are Yealink T5x series phones out in the field...

 

[SweetAction]

Suddenly...
"PBX monitor can now push any firmware, including old versions, to devices in bulk. See this video here"

 

[BrenttG]

funny, i wish it was that simple

 

[ChristopherN]

Any update on this?

 

[cecon-Berlin]

Any news? We need urgent help at our customers.

 

[JohnS_3CX]

Update: we are working with Yealink to produce a new firmware that addresses the issue. There is no ETA yet, but we will inform you on this thread when it is ready for production.

 

[BrenttG]

Update: we are working with Yealink to produce a new firmware that addresses the issue. There is no ETA yet, but we will inform you on this thread when it is ready for production.

Thank you for the update sir.

 

[cecon-Berlin]

Hi together, its me again :/
is it realy so hard to fix it after more than 2 weeks? Our customers wont accept that anymore. Is there any other workaround? except from downgrade via tftp!

best regards

 

[DMitchell]

Yeah downgrade doesn't work if you have 3CX hosted clients. I share the above comment, really? 2 weeks later and you still haven't addressed this issue? Please give us some working Yealink firmware that restores communication between 3CX and the T5x series. Clients can't even use the DND button's on these phones but must use the client as a workaround.

 

[SweetAction]

Yeah downgrade doesn't work if you have 3CX hosted clients. <snip>

<snip>

For 3CX-Hosted instances, please contact our Support team and they can take care of it.