Filter
Top Products
FIRMWARE VERSION 1.0.4.23 GXP2120/GXP2110/GXP2100/GXP1450 USER MANUAL Page 66 of 69
Firmware upgrades take around 60 seconds in a controlled LAN or 5-10 minutes over the Internet. We
recommend completing firmware upgrades in a controlled LAN environment whenever possible.
NO LOCAL TFTP/HTTP SERVERS
For users that would like to use remote upgrading without a local TFTP/HTTP server, Grandstream offers a
NAT-friendly HTTP server. This enables users to download the latest software upgrades for their phone via
this server. Please refer to the webpage:
http://www.grandstream.com/support/firmware.
Alternatively, users can download a free TFTP or HTTP server and conduct a local firmware upgrade. A
free windows version TFTP server is available for download from :
http://support.solarwinds.net/updates/New-customerFree.cfm
http://tftpd32.jounin.net/.
Instructions for local firmware upgrade via TFTP:
1. Unzip the firmware files and put all of them in the root directory of the TFTP server;
2. Connect the PC running the TFTP server and the phone to the same LAN segment;
3. Launch the TFTP server and go to the File menu->Configure->Security to change the TFTP server's
default setting from "Receive Only" to "Transmit Only" for the firmware upgrade;
4. Start the TFTP server and configure the TFTP server in the phone’s web configuration interface;
5. Configure the Firmware Server Path to the IP address of the PC;
6. Update the changes and reboot the phone.
End users can also choose to download a free HTTP server from
http://httpd.apache.org/ or use
Microsoft IIS web server.
Note:
When the phone boots up, it will send a TFTP or HTTP request to download the configuration file
"cfgxxxxxxxxxxxx" where "xxxxxxxxxxxx" is the MAC address of the phone. If it is a normal TFTP or HTTP
upgrade, the following messages “TFTP Error from [IP ADRESS] requesting cfg000b82023dd4 : File does
not exist. Configuration File Download” can be ignored in the TFTP/HTTP server log.
CONFIGURATION FILE DOWNLOAD
Grandstream SIP Devices can be configured via the Web Interface as well as via a Configuration File
(binary or XML) through TFTP or HTTP/HTTPS. The "Config Server Path" is the TFTP or HTTP/HTTPS