I’m doing automated phone provisioning via the /xepm-provision URL, and I’m wondering if vitalpbx supports firmware upgrades via the built-in provision system?
I’m hoping there is a directory somewhere on the system I can just drop the firmware files have it work. The thought of manually firmware updating hundreds of phones isn’t pleasant.
I believe you can make modules that would update the firmware, the only issue is that the phone and PBX have to support modules for the type of phone. If it does then you could find which part of the parameter or so does the firmware update which you would then set for the firmware from a url or file. This all theoretical, I have not had much time to really mess around with the endpoint manager.
I worked around the missing feature with a small hack. This will also allow for overriding phone configurations to work around other provisioning problems currently present in the VitalPBX interface (Properly layout of the polycom color expansion module for instance – monitored extensions not mashed on the main phone display and spilled over to the expansion module).
For the work around, you will need to setup a local FTP server (either on the PBX or another system). I install vsftpd on the local pbx.
create a local user for the polycom phone login (default is PlcmSpIp/PlcmSpIp)
create a directory to house the phone software and extra configuration files (i.e. /ftproot)
Change ownership of the directory to the user/group created for the phones
Configure the ftp server to not allow anonymous login, use the newly created directory, and allow reading and writing, and the appropriate umask to give files permissions of rw-rw-r–
These are the settings I’m using for vsftpd:
# Turn off Anonymous user access anonymous_enable=no
# Enable local system users, and give write access. local_enable=YES write_enable=YES
# Turn on Debugging – set xferlog_std_format=NO and log_ftp_protocol=YES log_ftp_protocol=YES xferlog_std_format=NO
unpack your firmware in to the directory (I used the split version of the polycom firmware to decrease the file size sent to the phone), and edit 000000000000.cfg
Change the APPLICATION section to point to the VitalPBX provisioning system for the individual config files using the substitution commands from the Polycom documentation. Here is the section from my cfg file: