firstname.lastname@example.org Posted June 17, 2016 Report Share Posted June 17, 2016 We are upgrading our servers from 5.2.5 to 5.4.0. On 5.4.0 it looks like the name of the firmware config XML file was changed from snom_3xx_fs.xml vs. snom_firmware.xml. The upgrade is causing problems with any extension that has a custom snom_3xx_fs.xml because during the upgrade from 5.2.5 to 5.4.0 the snom_3xx_fs.xml was not changed to snom_firmware.xml for any domain or phone specific config file. The problem this is causing is that phones are rebooting and requesting the firmware file and the server does not recognize the legacy snom_3xx_fs.xml at the domain or phone level so it is handing out the server level snom_firmware.xml file causing the phones to load incorrect firmware images. These are multi-tennent systems with 50 to 100 domains per server and perhaps 750 to 1000 phones on each server. Is there any quick way to find and replace all the snom_3xx_fs.xml files with snom_firmware.xml? It will be a lot of work to check each domain and each phone to determine if it has a custom snom_3xx_fs.xml that needs to be replaced with snom_firmware.xml. This will require us to manually check 1000s of phones. Perhaps in the future the upgrades can take into account the types of changes that can affect 1000s of phones. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.