Files
fusionpbx/resources/templates/provision/grandstream
DanandJesse Gruver f6c64054fa Add missing $ to variables in HT802 template (#6427)
* Grandstream HT802 Added Offhook Auto-dial variables

* Grandstream HT802 Added Offhook Auto-dial variables

* Grandstream GRP261x Make Configuration Keypad Lock configurable, fix default

* Grandstream Add grandstream_dhcp_time_zone across all templates

* Yealink Added yealink_missed_calllog to control whether missed calls are logged or not

* Grandstream HT802 update variable name to not use dash (which was breaking the template)

* added default settings for grandstreams
added "grandstream_configuration_via_keypad" and
"grandstream_dhcp_time_zone" as settings
also changed "grandstream_long_label" to 1

* Add custom transcription providers to email queue, fix spelling error

* Correct missing $ in Grandstream template

Co-authored-by: Jesse Gruver (piajesse) <me@piajesse.com>
2022-06-21 16:04:28 -06:00
..
2020-12-11 15:07:20 -07:00
2020-12-11 15:14:01 -07:00
2021-05-11 13:06:59 -06:00
2020-12-11 16:05:19 -07:00
2020-12-11 16:09:33 -07:00
2020-12-11 16:10:15 -07:00
2018-03-01 00:43:46 -07:00

Device Specific Firmware Versions

Select Grandstream phones (particularly the GXP2140 and similar) need firmware upgrades in a certain order. Grandstream also offers beta firmware quite often, which you may want to test on only some devices.

We've attempted to make the process of changing firmware easier, by serving a phone with the firmware specified in a field called Firmware under Accounts => Devices then click on the MAC address of the relevant device, filling in said field.

To use configurable firmware locations, enable device_firmware for the superadmin group under Advanced => Group Manager, set the URL for grandstream_firmware_path under Advanced => Default Variables and set Enabled to True for grandstream_firmware_path.

We would suggest creating a folder called firmware on the webserver that you host the firmware on, setting grandstream_firmware_path to the full URL (excluding the protocol - leave off the http://) for example mydomain.com/firmware or mydomain.com/firmware/grandstream if you are hosting multiple different vendors firmware images. When a device goes to hit this server, it will attempt to load <grandstream_firmware_path>/<device model>/<firmware version>/<firmware file>, or mydomain.com/firmware/gxp2140/1.0.9.69/gxp2140fw.bin in our case, assuming we have a Grandstream GXP2140 phone and we are feeding it firmware version 1.0.9.69. For Grandstream phones, the firmware filename is relatively static, and the files Grandstream distributes are generally named correctly for their phones to download.