“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.

 

[DMitchell]

Yes, I'm aware of that but it's a pain in the a.. to follow this process for every hosted client.

 

[Chris Walters]

Add us to the list

 

[FUFU]

Indeed I confirm that several features are missing following the update.
I downgraded the 5 phones I tested (T57W) to go back to version 96.86.0.72.

In order to avoid bad experiences for other users/customers/integrators, 3CX may remove the alarms from the 3CX Web Admin for phones not updated to the problematic version (96.86.100.5)...and thus prevent people do the update and let them be screwed.

The FW version recommended by 3CX on the site is still 96.86.0.72.

https://www.3cx.com/support/phone-firmwares/

Thank you in advance

 

[David.Shoebridge]

Have latest self-hosted 3cx v18.5.build418 , but also installed new yealink firmware update for phones 96.86.100.5
Prior to update the DND button on phone ,when pressed ( phone shows DND symbol ), would reflect Do Not Disturb DND on under 3cx management console User->ext xxx->status
Also if you changed the status within the 3cx management console user->ext xxx->status then the provisioned yealink phone would show DND.

After the update this does not happen. Press DND on phone --- There is NO synced DND status in the 3cx management.
And the same in reverse.

In otherwords - pressing DND on the phone does not put change the phone status to DND in the 3cx console , and so no forwarding rules that depend on DND status will work.

You can manually set DND in the 3cx console and forwarding rules will work; but the phone does not display it is in DND mode;

 

[JohnS_3CX]

Thanks for the update David, I can indeed confirm that this is caused by the same issue.

Yealink are working to provide us with a new firmware soon which should take care of this.

 

[David.Shoebridge]

John,

Thank you for confirming. I have been bashing my head for the last 2 days on this. Is there an easy way to downgrade the firmware other than going to the site and webbing into each phone? Can I upload the old firmware to the backend of the 3CX and pick it to push to all the phones?

Thank you

 

[JohnS_3CX]

The release that will come out will be an upgrade so there won't be an issue going upwards, but I would recommend against downgrading in this case.

This is to prevent any unforeseen possibility of damaging the phones, especially as we are getting closer to receiving the next update.

 

[David.Shoebridge]

I know multiple people have asked so I hate to ask again, but what is closer? Is the update coming this week? This Month?

 

[JohnS_3CX]

I don't have the ETA yet but will by updating this thread as soon as I know more

 

[Mercuris]

+1

In my case, 3CX pbx donwloaded the 96.86.100.5 but i didin't apply it quickly. Now all phones are in red telling Not supported and update is stuck because firmware should have been blocked by 3cx.

No more aéction on the phone is possible. reboot ; reprovisioning are stuck. Even if i manually reboot the phone, it can't reprovision.

Waiting for a solution for a week on the help platform ...

 

[JohnS_3CX]

+1

In my case, 3CX pbx donwloaded the 96.86.100.5 but i didin't apply it quickly. Now all phones are in red telling Not supported and update is stuck because firmware should have been blocked by 3cx.

No more aéction on the phone is possible. reboot ; reprovisioning are stuck. Even if i manually reboot the phone, it can't reprovision.

Waiting for a solution for a week on the help platform ...

I think you are facing an entirely different problem. They can be red and still function normally - reboot and reprovision should work regardless of the "Not Supported" message.

What you appear to have is phones that are registered, but their MAC is not assigned to any extension.
Or you are using custom templates perhaps?

 

[BEANLING]

Is this what is causing my answer button to be greyed out and I can't dial out through the desktop app anymore? It's still connected to my Yealink, but I have to answer and dial out with the physical phone now.

 

[David.Shoebridge]

Hate to ask but this is really a big issue for my customer that can't tell if they are on DND or not. Any ETA?

 

[FUFU]

I also hate to ask but could we have any news regarding this issue please ?

 

[N-AGPRO]

Is there anything new about this?
Our customers are still impacted

 

[Wihan]

anything new here? Most clients will be understanding if we can give them a rough time frame.

 

[QueBall]

Probably need to go over and ask Yealink.

In the meantime just use the working version.
Instructions to manually update and link to working versions are here.
https://www.3cx.com/sip-phones/firmware-update-yealink/

 

[dmat1175]

Looks like 96.86.0.74 just came out. I tested it on my T53W and it seems to operate as normal as far as DND goes.

 

[Erwin2MRC]

Looks like 96.86.0.74 just came out. I tested it on my T53W and it seems to operate as normal as far as DND goes.

But the fact is 96.86.0.74 is lower than 96.86.100.5. Therefore this new update won't be pushed by 3cx to phones that already installed the bad firmware.

 

[Helpdesk-SW-IT]

Hi all,

So we have a self hosted PBX and have the same problem.

So the solution is to remove the firmware 100.5 from the 3CX folder and then downgrade the phones? So simply download 0.74 (https://www.3cx.com/support/phone-firmwares/) via the web GUI and reflash the phone with it?
Kind regards,

Liam