V20 Will Not Upgrade Firmware (upgraded from V18)

Tom Graff

Customer
Joined
May 29, 2018
Messages
4
Reaction score
0
I just completed my V18 -> V20 upgrade. I noticed that all of my Yealink phones were tagged for a firmware upgrade. I clicked on upgrade from both Users and Phones but nothing happened. The phones did not start the upgrade process despite the Pop-Up box stating it will take 5 minutes to complete. I also noted that selecting REBOOT after tagging a phone likewise did nothing. I was able to manually update the firmware by accessing the Web Console URL under IP Phone in User and uploading from the phone manually. Once upgraded, 3CX recognized the new version right away.
 
Maybe I missed it: What is the question?
 
Sorry. My question is… how do I get it to function as designed? In V18 when I clicked any UPGRADE link associated with a user or extension, it would do just that - upgrade the phones firmware.
 
This works exactly the same in a v20.

But you may have encountered a firmware issue with the Yealink phones. Which Yealink devices and what firmware are you using?
 
so there is an issue with the Yealink phones nothing to do with 3cx
version 96.86.0.81 cant be upgraded to 96.87.0.16
even if you login to the phone and try and update the firmware it will fail you have to do an interim update i think it is 96.86.0.118
 
  • Like
Reactions: fxbastler
This works exactly the same in a v20.

But you may have encountered a firmware issue with the Yealink phones. Which Yealink devices and what firmware are you using?
T48U, T46U & T33G. I actually downloaded the firmware from the 3CX site and used it to manually update each phone.
 
Is there already a fix ? Because I have the same issue and 75 phones ..
Regards ,
Harry
 
I suspect that this is happening to you because you are just now upgrading to v20. This could be because there were several firmware updates in v20 along the way that were not applied. So now you are jumping to the latest one where 3CX cannot auto update. In cases like this, you then must do it manually to a certain firmware vision.

As a habit, because I have seen issues like this before, I always download a copy of any final version release to keep on hand. This way, I can do my updates one version at a time in date order as opposed to jumping over updates to the latest update. As I do each update, I make sure update any firmware along the way.
 
T48U, T46U & T33G. I actually downloaded the firmware from the 3CX site and used it to manually update each phone.
then there weren't many devices

Is there already a fix ? Because I have the same issue and 75 phones ..
change the 3CX update process:
  1. upload the yealink / 3CX .86.0.118 firmware to
    /var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/<provisioning_id>/firmware_new/yealink
  2. change firmware file user and owner to user phonesystem
  3. edit firmware.json and enter the desired data
  4. update all phones as necessary
  5. proceed and do the same with the firmware .87.0.16
or use the phone update process:
  1. set up a simple HTTP server
  2. provide a correct y0000000000xx.cfg (96 for T54W, 97 for T57W ...) there
  3. provide the yealink firmware file there
  4. set up dhcp option 66 for the phone network to this directory
  5. factory reset the phone
 
Hello @fxbastler ,

This the real hardcore (love it), have not seen many people do this.
Deep respect :cool:

Paulo
 
Go do phones/ options and Switch to use untested- unsuported firmware.
Under phones / firmware use the add button to add the interim update.
Later change back to use supported firmware and Apple the latest update.
 
Hello,

In the 3CX v20 there is like a 'forced User' version of updating the Firmware on the phones.

Goto:
Admin - Phones - Options - "Use Untested - Unsupported Firmwares" (enable this option)
Admin - Phones - Firmwares - "Add" (upload .rom file)

Then goto Admin- Phones and select the IP Phones for Firmware update.

Paulo da Graca
 
So was it just the provision URL had changed to drop the 5000/5001?
 
have not seen many people do this
We have a customer (edit 3CX firmware.json) with Snom phones for whom we had to implement the first solution repeatedly (I think three times in the last few years) because of firmware issues. This was the only solution that worked. I had described it in the German forum in the form of a guide. As it turns out, we weren't the only ones. Other partners had the same problems with their customers and solved them using this guide.

We use the second solution (DHCP option 66) in our own network for new phones. This way, they automatically receive the .118 firmware upon first startup - unless we prevent it.
 

Forum statistics

Threads
111,955
Messages
589,926
Members
164,855
Latest member
parik24pro