803457f8c9
* Support for Disabling Non-configured ports on GXW42XX gateways When patching in an ATA at facilities like residential facilities, we don't want dial tone on un-configured ports. This makes it so that the device will disable ports that have no user id configured so they don't provide dial tone. The behavior can be reversed by setting grandstream_fxs_enabled to 1 in the settings. |
||
|---|---|---|
| .. | ||
| dp715 | ||
| dp715.sm | ||
| dp750 | ||
| gac2500 | ||
| gds3705 | ||
| gds3710 | ||
| grp26xx | ||
| grp261x | ||
| grp2612 | ||
| grp2612w | ||
| grp2613 | ||
| grp2614 | ||
| grp2615 | ||
| grp2616 | ||
| gswave | ||
| gxp16xx | ||
| gxp17xx | ||
| gxp20xx | ||
| gxp21xx | ||
| gxp21xxbk | ||
| gxp110x | ||
| gxp116x | ||
| gxp140x | ||
| gxp140xbk | ||
| gxp1450 | ||
| gxp1450bk | ||
| gxp2100 | ||
| gxp2124 | ||
| gxp2130 | ||
| gxp2135 | ||
| gxp2140 | ||
| gxp2160 | ||
| gxp2170 | ||
| gxp2200 | ||
| gxp3240 | ||
| gxv300x | ||
| gxv3140 | ||
| gxv3175 | ||
| gxv3175v2 | ||
| gxv3240 | ||
| gxv3275 | ||
| gxv3370 | ||
| gxv3504 | ||
| gxw40xx | ||
| gxw42xx | ||
| gxw410x | ||
| gxw4004 | ||
| gxw4008 | ||
| ht502 | ||
| ht503 | ||
| ht701 | ||
| ht702 | ||
| ht704 | ||
| ht801 | ||
| ht802 | ||
| ht818 | ||
| htx86 | ||
| wave | ||
| wp820 | ||
| README.md | ||
| gxv3380 | ||
README.md
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.