FIRMWARE VERSION 1.0.3.1 HT70X USER MANUAL Page 31 of 52
The URL for the HTTP/HTTPS server used for firmware upgrade and configuration via
HTTP.
For example, http://provisioning.mycompany.com:6688/Grandstream/1.0.0.67“:6688” is
the specific TCP port where the HTTP or HTTPS server is listening; it can be omitted if
using default port 80.
Note: If Auto Upgrade is set to No, HT70X will only do HTTP/HTTPS download once at
boot up.
IP address or domain name of firmware server.
IP address or domain name of configuration server.
The password used for encrypting the XML configuration file using OpenSSL.
This is required for the phone to decrypt the encrypted XML configuration file.
The user name needed to authenticate with the HTTP/HTTPS server.
The password needed to authenticate with the HTTP/HTTPS server.
Default is blank. If configured, HT701 will request firmware file with the prefix. This
setting is useful for ITSPs. End user should keep it blank.
Default is blank. End user should keep it blank.
Default is blank. End user should keep it blank.
Default is blank. End user should keep it blank.
Allow DHCP Option 66
to override server
If set to “Yes”, configuration and upgrade server information can be obtained using DHCP
option 66 from DHCP server located in customer’s environment. Default setting is Yes.
Choose “Yes” to enable automatic upgrade and provisioning. If select “Check every
minutes” input the amount of minutes you want it to check for update. If select “Yes, daily
at hour” make sure to input the hour of the day you want it to check for update, e.g. for 11
pm type 23. If select “Yes, weekly on day” make sure you input the day of the week (in
format 0-6, 0 is Sunday) you want it to check for update. When set to No, HT70X will only
do the following option you select; “Always check for New Firmware at Boot up” will check
for new firmware every time the device reboots. “Check New Firmware only when F/W
pre/suffix changes” will check for updates only when the pre/suffix has been changed.
If set to Yes, config file is authenticated before acceptance. This protects the
configuration from an unauthorized change.
