bulk firmware update?

[nobody]

I updated 3cx to the 15.5 SP5 Version.
Also, I tried to update about 30+ yealink T58V phones to the 3cx recommended firmware. Using IE or Firefox, tried to CTRL-Click or Shift-Click. However, at best only 2 phones at at time will receive the update.

I read that a bulk update of the Firmware was possible with v14.x, and I read about users which were able to do a bulk update with version 15.x. But does not work for me. At first sight looks like another proof of failure creating a Web-UI instead of a native software.

Should this work, and if, how?
Updating 30 phones and in the near future maybe 50 one by one, that is something I would not expect,

 

[phonemaster]

I updated 3cx to the 15.5 SP5 Version.
Also, I tried to update about 30+ yealink T58V phones to the 3cx recommended firmware. Using IE or Firefox, tried to CTRL-Click or Shift-Click. However, at best only 2 phones at at time will receive the update.

I read that a bulk update of the Firmware was possible with v14.x, and I read about users which were able to do a bulk update with version 15.x. But does not work for me. At first sight looks like another proof of failure creating a Web-UI instead of a native software.

Should this work, and if, how?
Updating 30 phones and in the near future maybe 50 one by one, that is something I would not expect,

Hi nobody,
I made a successful bulk firmware update of around 40-45 phones (mixed models) when moved to the latest 15.5.
Try to check the limitations of your Operating System or Firewall.
Also, remember that the firmware file of T58 is big - around 210 MB. Probably you have some limitations in your network.

 

[nobody]

The firewall is off, network is Gigabit, the server ist hosted in house, and in the same subnet as the phones. Unlikely that this is the culprit.
Still all phones besides 6 are using the old firmware after waiting 12hrs.
I check another firefox version.

 

[nobody]

Something else must be wrong. I even tried chromium for a test. no update. Any ideas?

From the logs:

2018/06/30 11:13:07.244|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.246|5352|0047|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.256|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.259|5352|0034|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.277|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.297|5352|0047|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.330|5352|0054|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:13:07.336|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:13:07.375|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.048|5352|0054|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0056|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0041|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0023|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0059|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
.
.
.
.
2018/06/30 11:27:49.766|5352|0017|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 12:13:44.922|5352|0059|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 12:42:38.297|5352|0056|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:00:22.939|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:20:28.477|5352|0038|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:21:30.332|5352|0017|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:21:55.617|5352|0034|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated

 

[phonemaster]

Something else must be wrong. I even tried chromium for a test. no update. Any ideas?

From the logs:

2018/06/30 11:13:07.244|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.246|5352|0047|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.256|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.259|5352|0034|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.277|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/logo/yealinkt58.png' cannot be generated
2018/06/30 11:13:07.297|5352|0047|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/Directory_setting.xml' cannot be generated
2018/06/30 11:13:07.330|5352|0054|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:13:07.336|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:13:07.375|5352|0050|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.048|5352|0054|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0056|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0041|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0023|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
2018/06/30 11:14:15.053|5352|0059|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/firmware/yealink/T5XA-58.80.0.65.rom' cannot be generated
.
.
.
.
2018/06/30 11:27:49.766|5352|0017|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 12:13:44.922|5352|0059|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 12:42:38.297|5352|0056|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:00:22.939|5352|0033|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:20:28.477|5352|0038|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:21:30.332|5352|0017|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated
2018/06/30 13:21:55.617|5352|0034|Inf|PRV: Requested file '/provisioning/9byh02zyk25way/yealink_phonebook.xml' cannot be generated

These logs are Okay. These files (logo, phonebook) are already in the system and not need to be generated.
It looks like they first trying to generate the requested file and if it's not possible only after that they are trying to find them in requested repository. This is good and can prevent the phones to download the existed old/not supported/corrupted files. You can ignore these logs.

What operating system are you using?
Try to check the phone logs and capture. Start the capture on the phone, reproduce the issue, wait 5-10 seconds, stop capture, download the logs and capture and try to find the error/problem.

My personal filling is that you have something (OS limitations, or some other software, or something else) that is occupying the TCP ports and phones can't download the firmware files.

 

[nobody]

Thank you for your ideas.

OS is a virtual server 2012R2, 4GB Ram, 4 virtual CPUs.
I also think the messages in the log are not important, even if its strange that instead of the backslash the slash is used, but this might because of the webserver using slashes.
After I confirm the updates, the Ram utilization of the server goes up to 2.8GB for the console process. I find this a little suspicious, just because some phones are rebooted and a few downloads are starting from the server using https, you should not need several gigabytes ram.
Otherwise I see nothing in the system or application logs which would point to a problem.
I now am up to about 6 remaining phones, an hope I can finish that today.
PS: all the phones are using the hotdesking feature.