UC900 Series IP Phones Provisioning
- 1 1. Introduction
- 2 2. Manage Configuration
- 3 3. Obtain Provisioning Server's Address
- 4 4. Encrypt cfgMAC.xml
- 5 5. Customize Resource Files
- 6 6. Upgrade resource files
- 7 7. Upgrade Firmware
- 8 8. Update mode
- 9 9. Download and Verify Configurations
- 10 10. Firmware and Configuration File Prefix and Postfix
- 11 11. Firmware Server and Configuration File Server
- 12 12. Manage Firmware and Download Configuration File
- 13 13. Pre_Configuration and Configuration Redirection
- 14 14. Automatic Provisioning Within LAN
- 15 15. Troubleshooting
- 16 16. Glossary
- 17 17. Making Ringtone Notes
- 18 18. LCD and Web Language Custom Guide
- 19 19. LCD and Web GUI custom Guide
- 19.1 19.1 How to custom the wallpaper1-wallpaper6?
- 19.2 19.2 How to custom the screensaver1- screensaver3?
- 19.3 19.3 How to custom the weblogo?
- 19.4 19.4 How to custom the eights menus(.png)in the main menu?
- 19.5 19.5 How to custom the ...Icon.png?
- 19.6 19.6 How to custom the lcdlogo_color.png?
- 19.7 19.7 How to customthe lcdlogo_bw.png?
- 20 20. Firmware Upgrade
1. Introduction
Htek UC900 Series including all models:
UC901 | UC902(S) | UC903 | UC912(G/E) | UC921(E) | UC923(U) | UC924(E/W/U) | UC926(E/S/U) |
This guide provides instructions on how to provision Htek IP Phone with the minimum settings.
Htek IP Phone supports FTP, TFTP, HTTP, and HTTPS for auto provisioning and are configured by default to use the HTTP.
Note: The auto provision just applies to FW 1.0.3.70 or FW after 1.0.3.70. For the latest FW, please visit Htek Firmware .
2. Manage Configuration
2.1 Htek IP Phone Provision Process
When Htek IP Phone boots up, it will issue request one by one for these configuration files named "cfgDeviceCode.xml" → "cfgMAC" → "cfgMAC.xml ".
DeviceCode: Device Code is a short code represents a series model. e.g., device code 0012 represent UC924, so all UC924 will request cfg0012.xml; device code 0019 represent UC912 and UC912G, so both of the two models will request cfg0019.xml.
For all the device code, please refer to Device Information for ProvisioningMAC: The device MAC address, a unique 12-digit serial number of the phone. You can obtain it from the label back of the phone, and you can also press OK button twice to check it on the phone, another way is get it from the homepage of the phone’s web.
Please note that the MAC address within the filename must be lowercase.
Configuration File Type | Example | Description |
---|---|---|
cfgDeviceCode.xml | cfg0012.xml | all phones belong to one model or series share one DeviceCode |
cfgMAC | cfg001fc110d3a9 | this file is a private format for specific device |
cfgMAC.xml | cfg001fc110d3a9.xml | unique for each device, and it is the mainly file we used to provision phones. |
Provisioning Flow Chart:
Note: factory000x.bin is used in Htek factory, please don't try to provision it, otherwise it will influence the stability.
2.2 Obtain Configuration Template Files
The fastest way you could obtain the cfgMAC.xml configuration template is to download it from any phones with factory default settings.
Just enter phone's webpage → Management → Configuration → Download Xml File.
2.3 Edit cfgDeviceCode.xml and cfgMAC.xml
All the settings are contained in such a fixed structure like below.
<?xml version="1.0" encoding="UTF-8" ?>
<hl_provision version="1">
<config version="1">
<P47 para="Profile1_Sipserver">example</P47>
......
...settings area...
......
</config>
</hl_provision>
And the format of the setting is <P-Code para="Description">P-Value</P-Code>
, e.g., <P47 para="Account1_Sipserver">192.168.0.68:5060</P47>. Although the Description
field is not required, it is friendly for read.
You may see some settings don't have the same format, like <P-Code Para="Description" />, this format is only used when a setting is blank and has no default value.
Here is an example which contains a few settings to show the unbroken structure.
<?xml version="1.0" encoding="UTF-8" ?>
<hl_provision version="1">
<config version="1">
<!--Profile1/Basic-->
<P47 para="Profile1_Sipserver">192.168.0.68:5060</P47>
<P967 para="Profile1_FailoverSipserver" />
<P4567 para="Profile1_PreferPrimaryServer">1</P4567>
<P24065 para="Profile1_DHCPSIPServer">0</P24065>
<P48 para="Profile1_OutboundProxy" />
<P20047 para="Profile1_BackUpOutboundProxy" />
<P130 para="Profile1_SipTransport">0</P130>
<P52 para="Profile1_NatTraversal">2</P52>
<P103 para="Profile1_DnsMode">0</P103>
<P63 para="Profile1_CallMessageFormat">0</P63>
<P24785 para="Profile1_TrsRelSetting">0</P24785>
<P31 para="Profile1_SipRegistration">1</P31>
<P81 para="Profile1_UnregisterOnReboot">1</P81>
<P32 para="Profile1_RegisterExpiration">15</P32>
<P24816 para="Profile1_FallBackInterval">600</P24816>
<P25092 para="Profile1_ServerRetryCounts">3</P25092>
<P109 para="Profile1_OutCallWithoutReg">1</P109>
<P136 para="Profile1_RPort">0</P136>
<P1100 para="Profile1_RFC2543Hold">1</P1100>
<P8775 para="Profile1_ConnectMode">1</P8775>
</config>
</hl_provision>
If a P-Code is missed in a "cfgDeviceCode.xml" or "cfgMAC.xml" file, you could add it in the <settings area> just follow the format, but please note the validity of the P-Value.
For all P-Codes and the P-Value, please ask your sale, provider or support@htek.com for the file Htek_Parameter_List.
3. Obtain Provisioning Server's Address
Htek IP Phone supports to obtain the provisioning server address in below 3 ways:
Plug and Play (PnP) Server
DHCP Options
Phone Flash
The priority of obtaining the provisioning server address: PNP Server (SIP PnP MCAST) --> DHCP Option 128 or 150 or 66 --> Configuration in Flash.
The PNP Server feature is enable default.
Webpage --> Management --> Auto Provision --> PnP Active: No/Yes
If you set "Yes", the Phone will obtain the provisioning server address from the PnP Server.
Setting of "DHCP Options 128 or 150 or 66":
Webpage --> Management --> Auto Provision, there are two settings for DHCP Options
Allow DHCP Option: you could set it to 66 or 128 or 150
Allow DHCP Option Server: set Yes to allow the phone get Config Server Path through DHCP Options.
Configuration in Flash.
Another way to get the provisioning server address is from the setting "Config Server Path".
For examples as the below screenshot, the phone will get the configuration file from http://192.168.0.254/cfg.
Note: You can set the phone to automatically upgrade every certain time:
For examples:
The phone will check the configuration file and the firmware every 10080 minutes (7 days). If there are the new cfg files or the new firmware, the phone will upgrade automatically.
4. Encrypt cfgMAC.xml
4.1 How to encrypt the XML configuration file
The XML configuration file could be encrypted using algorithm.
You could encrypt the cfgMAC.xml file using openssl.
The supported algorithm is AES-128-CBC.
The parameter iv
is fixed 0B1E1D000F0B07091D1F04071F1E0407
and may not be changed, other wise configuration files cannot be encrypted by the phone and settings are not made.
The valid key (parameter K
) length is from 1-16, and may only contain [0-9, A-F].
Here is an example.
openssl enc -aes-128-cbc -K 001FC1BC -iv 0B1E1D000F0B07091D1F04071F1E0407 -in cfg001fc11e5105.xml -out cfg001fc11e5105b.xml
After you encrypt the cfgMAC file, you need to enable Authenticate Cfg File
and set a common AES key to let the phone could decrypt the file. In the above case, you should set it as 001FC1BC
.
You could find this setting on webpage → Management → Auto Provision → Set Common AES Key. (P-Code is P8631)
5. Customize Resource Files
Htek IP Phone allows to customize some resource files, like ring tone file, language package file and logo files. For how to customize resource files, as follows:
5.1 Customize ring tone
Htek IP Phone has several factory-default ring tones (Ring1, Ring2, Ring3). You can customize Ring4, Ring5, Ring6, Ring7 and Ring8 tone and upload them to the phone via auto provisioning.
You can change the ring tone configuration parameter to personalize ring tone:
For example: P8721 = 8
For more information on customizing ring tone file, please refer to <<Making Ringtone Notes>> in page 60.
5.2 Customize LCD language
Htek IP Phone supports multiple language,you can modify the language and add a new language to the phone. The following table lists all available languages, associated language files and language template file:
Available language | Associated language files | Language template file |
English | (Default, can't be customized) | LCD_English_Template.xml |
French | 1_Français(French).xml | |
German | 2_Deutsch(German).xml | |
Spanish | 3_Español(Spanish).xml | |
Portuguese | 4_Português(Portuguese).xml | |
Russian | 5_русский(Russian).xml | |
Italian | 6_Italiano(Italian).xml | |
Polish | 7_Polski(Polish).xml | |
Turkish | 8_Türk(Turkish).xml | |
Serbian | 9_Srpski(Serbian).xml | |
ChinesSimplified | 10_简体中文(ChineseSimplified).xml | |
ChineseTraditional | 11_繁体中文(ChineseTraditional).xml | |
Slovenian | 13_Slovenščina(Slovenian).xml | |
Persian | 14_Persian(Farsi).xml | |
Hebrew | 15_עברית(Hebrew).xml | |
Slovak | 16_Slovak.xml | |
Czech | 17_Czech.xml | |
JapaneseSimplified | 18_日本語(JapaneseSimplified).xml | |
Dutch | 19_Nederlands(Dutch).xml |
Below picture shows a portion of LCD_English_Template.xml file:
English is the default language, you can change configuration parameter to other languages:
For more information on customizing an LCD language, please refer to <<LCD Language custom guide>> in page 62.
5.3 Customize web language
Htek IP Phone supports multiple language,you can modify the language and add a new language to the phone's webpage. The following table lists all available languages, associated language files and language template file:
Available language | Associated language files | Language template file |
English | (Default, can't be customized) | Web_English_Template.js |
French | 1_French.js | |
German | 2_German.js | |
Spanish | 3_Spanish.js | |
Portuguese | 4_Portuguese.js | |
Russian | 5_Russian.js | |
Italian | 6_Italian.js | |
Polish | 7_Polish.js | |
Turkish | 8_Turkish.js | |
ChineseSimplified | 10_ChineseSimplified.js | |
ChineseTraditional | 11_ChineseTraditional.js | |
Dutch | 19_Dutch.js |
Below picture shows a portion of Web_English_Template.js file:
English is the default language,you can change configuration parameter to other languages:
For more information on customizing web language file, please refer to << Web Language custom guide>> in page 64.
5.4 Customizing wallpaper
You can customize Htek UC923/UC924/UC926 IP phones' wallpaper.
Below table shows wallpaper's format and resolution for UC923/UC924/UC926 IP phones:
Phone model | Photo format | Resolution | One file size | Photo number |
UC923 | .jpg, .bmp | 320*240 | <=100KB | 3 |
UC924 | .jpg, .bmp | 480*320 | <=100KB | 3 |
UC924E | .jpg, .bmp | 480*320 | <=100KB | 3 |
UC926 | .jpg, .bmp | 480*272 | <=100KB | 3 |
UC926E | .jpg, .bmp | 480*272 | <=100KB | 3 |
Wallpaper2 is default wallpaper, you can change configuration parameter to other wallpaper:
For more information on customizing wallpaper, please refer to <<LCD and Web GUI custom Guide >> in page 68.
5.5 Customizing screensaver
You can customize Htek UC923/UC924/UC926 IP phones' screensaver.
Below table shows screensaver's format and resolution for UC923/UC924/UC926 IP phones:
Phone model | Photo format | Resolution | One file size | Photo number |
UC923 | .jpg, .bmp | 320*240 | <=100KB | 3 |
UC924 | .jpg, .bmp | 480*320 | <=100KB | 3 |
UC924E | .jpg, .bmp | 480*320 | <=100KB | 3 |
UC926 | .jpg, .bmp | 480*272 | <=100KB | 3 |
UC926E | .jpg, .bmp | 480*272 | <=100KB | 3 |
Screensaver default is Off, you can change configuration parameter to activate the Screensaver :
For more information on customizing screensaver, please refer to <<LCD and Web GUI custom Guide >> in page 68.
5.6 Customizing weblogo
You can customize Htek all phone models' weblogo on webpage.
Phone model | Photo format | Resolution | File size |
UC601/UC901/UC902/UC903/UC912/UC912G/UC912GM/UC923/UC924/UC924E/UC926/UC926E | .jpg | 225*93 | <=2M |
For more information on customizing weblogo, please refer to << LCD and Web GUI custom Guide >> in page 68.
6. Upgrade resource files
Htek IP phone supports upgrade resource files through URL (support HTTP(s) server). The files contain hlpres.tar, Language.tar, ring4.bin, ring5.bin, ring6.bin, ring7.bin, ring8.bin, exp_pres.tar, Screensaver and Wallpaper. For how to configure these files URL as follow:
6.1 How to configure URL for hlpres.tar
You can change the hlpres server configuration parameter to locate the file:
P20176=http(s)://192.168.0.254/hlpres.tar
6.2 How to configure URL for Language.tar
You can change the Language server configuration parameter to locate the file:
P20175=http(s)://192.168.0.254/Language.tar
6.3 How to configure URL for exp_pres.tar
You can change the exp_pres server configuration parameter to locate the file:
P20177=http(s)://192.168.0.254/exp_pres.tar
6.4 How to configure Path for ringx.bin
You can change the Ring server configuration Path, and IP Phone will get the files: ring4.bin, ring5.bin, ring6.bin, ring7.bin, ring8.bin automatically:
P20174=http(s)://192.168.0.254
6.5 How to configure URL for Screensaver
This parameter is only applicable to UC923, UC924, UC924E, UC926, UC926E.
You can change the Screensaver server configuration to locate the file:
P20051=http(s)://192.168.0.254/Screensaver.jpg
Note: 1. Screensaver file phone gets from server will cover the screensaver photo1.
2. Only support format .jpg, .bmp.
6.6 How to configure URL for Wallpaper
You can change the Wallpaper server configuration to locate the file:
P20052=http(s)://192.168.0.254/wallpaper.jpg
Note: 1. Wallpaper file phone gets from server will cover the wallpaper6.
2. Only support format .jpg, .bmp.
7. Upgrade Firmware
Version number and support files list:
1.0.3.58-1.0.3.72 | 1.0.3.73 or later |
boot_9xx.bin | fw9xx.rom |
Note:
When the phone which version is 1.0.3.71 or older upgrade to 1.0.3.73, phone will upgrade img_9xx.bin then automatically upgrade fw9xx.rom. fw9xx.rom is all-in-one firmware file. After upgrading to the 1.0.3.73 firmware, in the next time, phone will only need upgrade one file fw9xx.rom.
7.1 Configuring HTTP Server
Htek IP Phone supports using FTP, TFTP, HTTP and HTTPS protocols to obtain the address of provision server. Default way is HTTP. For how to configure a HTTP server, as follows:
You can download a free HTTP server from http://httpd.apache.org/ or use Microsoft IIS web server. Then setup HTTP server.
For more information on how to configure TFTP, FTP and HTTPS servers, please refer to Upgrade through TFTP in page 71, Upgrade through FTP in page 74 and Upgrade through HTTPS in page 75.
7.2 How to Configuring HTTP Server
Login webpage, "Management" -> "Auto Provision" -> "Firmware Upgrade" -> "Upgrade Mode" needs to be set to HTTP. "Firmware Server Path" needs to be set to be a valid URL of a HTTP server, and server name can be in either FQDN or IP address format. Below are examples of some valid URLs.
e.g. firmware.mycompany.com:5688/Htek
e.g. www.mycompany.com:5688/fm/Htek
e.g. 218.2.83.110
Below are Instructions for FW upgrade via HTTP:
(1) You can download a free HTTP server from http://httpd.apache.org/ or use Microsoft IIS web server. Then setup HTTP server.
(2) Unzip the firmware file and put the files under the root/fm directory of the HTTP server.
(3) Visiting "http://192.168.0.254/fm/fw924.rom on localhost by browser" to verify the HTTP Server. If visiting "http://192.168.0.254/fm/fw924.rom on another computer is no prompt to download fw924.rom file, please check the firewall (Suggest to close the firewall).
(4) Change the setting of UC9xx (192.168.0.254 is HTTP server):
Click "SaveSet".
(5) Restart the UC9xx, IP Phone will restart and automatically get firmware files from HTTP server.
NOTES:
(1) We recommend you to use Htek HTTP server, or you can also use your own TFTP/HTTP/FTP/HTTPS server for upgrade and provisioning procedures.
(2) You need to update the settings and restart the IP Phone after "Firmware Server Path" is set. If the configured firmware server is found and a new code image is available, UC9xx IP Phone will attempt to retrieve the new image files by downloading them into the UC9xx's SDRAM. During this stage, the phones LEDs will blink more frequently until the checking/downloading process is finished. Upon verification of checksum, the new code image will be saved into the Flash. If TFTP/HTTP/FTP/HTTPS fails for any reason (e.g. TFTP/HTTP/FTP/HTTPS server is not responding, there are no code image files available for upgrade, or checksum test fails, etc.), the phone will stop the TFTP/HTTP/FTP/HTTPS process and simply boot using the existing code image in the flash.
(3) Firmware upgrade takes 3 to 8 minutes over Internet, or just 1 minute on a LAN. We recommend you to upgrade the FW in a controlled LAN environment.
8. Update mode
Update mode sets the desired time frames for phone to perform the auto provisioning process.
Below is the introduction of the 3 updating modes in detail:
Power On
Repeatedly
SIP NOTIFY Message
Power On
Power On mode is set as default. The phone will perform auto provisioning process when it is power on.
Repeatedly
The phone performs auto provisioning process at a regular interval. You can configure the interval for the Repeatedly mode. The default interval is 10080 minutes.
To activate the Repeatedly mode via web user interface:
1. Click the Management->Auto Provision:
2. AUTO Upgrade set Yes:
3. Click the "SaveSet" button to save the change.
SIP NOTIFY Message
The phone will perform auto provisioning process when receiving a SIP NOTIFY message which contains the header "Event: check-sync". If the header of the SIP NOTIFY message contains an additional string "reboot=true", the phone will reboot immediately and then perform the auto provisioning process. For this update mode, it requires the server supports.
Below picture shows the message flow:
9. Download and Verify Configurations
9.1 Download configuration files
Once obtaining a provisioning server address in one of the ways introduced above, the phone will connect to the provisioning server and download configuration files. During the auto provisioning process, the phone will try to download the common configuration file cfg000x.xml firstly, and then try to download the cfgMAC.xml file from the provisioning server.
9.2 Resolve and Update configurations
The phone will resolve the configuration files after downloading, then update the configurations to the phone flash. Generally, the phone will reboot to make the configurations effective after the auto provisioning process is finished.
9.3 Verify configurations
You can verify the update via phone user interface after auto provisioning, or you can verify it via web user interface
During the auto provisioning process, you can monitor the downloading requests and response messages by a wireshark tool.
Some examples show as follows:
Example1: Htek UC924 IP Phone downloads configuration files from TFTP server.
Example2: Htek UC924 IP Phone downloads configuration files from FTP server .
Example3: Htek UC924 IP Phone downloads configuration files from HTTP server .
10. Firmware and Configuration File Prefix and Postfix
Htek IP Phone supports Prefix and Postfix for both firmware and configuration files.
Parameter P232 and P233 are for Prefix and Postfix for Firmware, respectively. Parameter P234 and P235 are for Prefix and Postfix for Configuration file, respectively.
Firmware Prefix and Postfix allows device to download the firmware name with the matching Prefix and Postfix.
In addition, when Parameter P238 (Check New Firmware only when F/W pre/suffix changes) is set to 1, the device will only issue the Firmware Upgrade request if there are changes in the firmware Prefix or Postfix.
Below are the firmware BASIC NAMES that are related to UC924P:
If the firmware version is earlier than 1.0.3.73, the firmware BASIC NAMES as follows:
boot_924.bin
img_924.bin
ring4.bin
ring5.bin
ring6.bin
ring7.bin
ring8.bin
Language.tar
hlpres.tar
Service provider can use "hl_" as prefix, and "_1.0.3.70" as postfix, the above files will be changed to:
hl_boot_924.bin_1.0.3.70
hl_img_924.bin_1.0.3.70
hl_ring4.bin_1.0.3.70
hl_ ring5.bin_1.0.3.70
hl_ ring6.bin_1.0.3.70
hl_ ring7.bin_1.0.3.70
hl_ ring8.bin_1.0.3.70
hl_ Language.tar _1.0.3.70
hl_ hlpres.tar _1.0.3.70
If the firmware version is 1.0.3.73 or later than 1.0.3.73, the firmware BASIC NAME as follows:
fw924.rom
Service provider can use "hl_" as prefix, and "_1.0.3.73" as postfix, the above files will be changed to:
hl_ fw924.rom _1.0.3.73
In this way, all of the firmware with different version could be stored in one single directory, and they could be differentiated by using prefix or postfix, i.e., all files with a postfix of "_1.0.3.73" belong to the firmware version 1.0.3.73.
Same rule applies to configuration files, i.e., for configuration file named "cfg001fc1001708", there could be 3 versions: "hl_ cfg001fc1001708_cfg001", "hl_ cfg001fc1001708_cfg002", and "hl_ cfg001fc1001708_cfg003". The BASIC NAME of the configuration file is "cfg001fc1001708", but there are 3 different versions, the one that will be accepted is the one with matching prefix and postfix specified in the current configuration.
11. Firmware Server and Configuration File Server
Beside the Prefix and Postfix for firmware and configuration files, different server paths for firmware upgrade or Configuration File Server can be specified in different FQDN, i.e.:
The parameters are P192 and P237 for Firmware and Config Server
12. Manage Firmware and Download Configuration File
When parameter P194 (Auto Upgrade) is set to 1, Service Provider can use P193 (Auto Check Interval) to have the devices periodically check with either Firmware Server or Config Server, whenever they are defined. This allows the device periodically check if there are any new changes need to be taken on a scheduled time. By defining different intervals in P193 for different devices, Service Provider can distribute the Firmware or Configuration File download schedule to reduce the Firmware or Provisioning Server load at any given time.
13. Pre_Configuration and Configuration Redirection
Please note:If your phone default setting is as below:
Currently Htek Phone does not support pre_configuration and configutration Redirection, please refer to section 6 in page 24.
For mass deployment, we provide TFTP/HTTP redirection service. By default, all Htek products point to our provisioning system. When a unit is powered up, it will automatically contact our provisioning server. Our provisioning server will redirect the unit to customer's TFTP/FTP/HTTP/HTTPS server. The unit will reboot and send further provisioning request to ask for configuration file (or firmware file) from customer's TFTP/FTP/HTTP/HTTPS server.
Below is the information that we need from service providers for TFTP/HTTP redirection:
MAC address range, this should be printed on the carton box
Your TFTP/FTP/HTTP/HTTPS server IP address
Your company name and address
Here are the things that service providers should do:
Create configuration files for all the devices and put them on your TFTP/HTTP server.
Download the latest official release from www.htek.com/support/Document_And_Firmware and put them on your TFTP/FTP/HTTP/HTTPS server (same directory as above)
After we inform you that the devices have been entered into our central provisioning database, please take out a few devices to test. Upon powering up, they should contact our provisioning server https://rps.htek.com/index.php/fn/g first, and then get redirected to your TFTP/FTP/HTTP/HTTPS server and pull out the configuration files and the firmware files. They will be upgraded to the latest firmware with your configurations.
14. Automatic Provisioning Within LAN
Htek products support DHCP Option 66 or 128 or 150 for automatic provisioning within a Local Area Network. The provisioning server URL is embedded inside standard option 66 or 128 or 150 of DHCP responses.
Htek IP Phones send DHCP DISCOVER with the following information:
DHCP Server can be configured to send the following information in its DHCP OFFER. Please notice that in this example, an HTTP://URL is provided in the Option 66 "TFTP Server Name" field or Option 128 "TFTP server IP address" or Option 150 "TFTP server address". Device will then issue HTTP requests instead of the traditional TFTP requests to the server. This design makes more flexible in device provisioning.
15. Troubleshooting
This part provides guidance to help you solve problems you might encounter when deploying phones.
If you require additional information or assistance with the deployment, please contact your system administrator.
Why does the phone fail to download configuration files?
Ensure that auto provisioning feature is configured properly.
Ensure that the provisioning server and network are reachable.
Ensure that authentication credentials configured on the phone are correct.
Ensure that configuration files exist on the provisioning server.
Why does the provisioning server return HTTP 404?
Ensure that the provisioning server is properly set up.
Ensure that the access URL is correct.
Ensure that the requested files exist on the provisioning server.
Why does the phone display "Network Down"?
Ensure that the Ethernet cable is plugged into the Internet port on the phone and the Ethernet cable is not loose.
Ensure that the switch or hub in your network is operational.
Ensure that the configurations of network are properly set in the configuration files.
Why is the permission denied when uploading files to the root directory of the FTP server?
Ensure that the complete path to the root directory of the FTP server is authorized.
Check security permissions on the root directory of the FTP server, if necessary, change the permissions.
Why doesn't the phone obtain the IP address from the DHCP server?
Ensure that settings are correct on the DHCP server.
Ensure that the phone is configured to obtain the IP address from the DHCP server.
Why doesn't the phone display the Language, only display English on LCD and Web?
Ensure that the name of the language is correct.
Ensure that the network is available and the root directory is right for downloading.
Ensure that the parameters are correctly set in the configuration files.
Ensure that the language's Coding format is UTF-8.
Why doesn't the phone display the wallpaper or ScreenSaver or the weblogo of webpage?
Ensure that the file format of the wallpaper, ScreenSaver and weblogo is *.jpg.
Ensure that the size of the wallpaper, ScreenSaver and weblogo file is not larger than that the phone supports, or check the hlpres.tar is not larger than 2M.
Ensure that the name of the wallpaper, ScreenSaver and weblogo are correct.
Ensure that the network is available and the root directory is right for downloading.
Ensure that the wallpaper, ScreenSaver and weblogo files in the hlpres.tar file.
Why doesn't the phone update configurations?
Ensure that the configuration files are different from the last ones.
Ensure that the phone has downloaded the configuration files.
Ensure that the parameters are correctly set in the configuration files.
16. Glossary
MAC Address: A Media Access Control address (MAC address) is a unique identifier assigned to network interfaces for communications on the physical network segment.
DHCP: Dynamic Host Configuration Protocol (DHCP) is a network configuration protocol for hosts on Internet Protocol (IP) networks. Computers that are connected to IP networks must be configured before they can communicate with other hosts.
FTP: File Transfer Protocol (FTP) is a standard network protocol used to transfer files from one host to another host over a TCP -based network, such as the Internet. It is often used to upload web pages and other documents from a private development machine to a public web-hosting server.
HTTP: The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web.
HTTPS: Hypertext Transfer Protocol Secure (HTTPS) is a combination of Hypertext Transfer Protocol (HTTP) with SSL/TLS protocol. It provides encrypted communication and secure identification of a network web server.
TFTP: Trivial File Transfer Protocol (TFTP) is a simple protocol to transfer files. It has been implemented on top of the User Datagram Protocol (UDP) using port number 69.
AES: Advanced Encryption Standard (AES) is a specification for the encryption of electronic data.
URL: A uniform resource locator or universal resource locator (URL) is a specific character string that constitutes a reference to an Internet resource.
XML: Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
P-Code: A code starts with a capital letter P and follow by at least one digit, for example P2, P147.
One P-Code represents one single setting, like P47 represents Primary SIP Server of Profile 1, P747 represents Primary SIP Server of Profile 2.
P-Value: The value of a P-Code is called P-Value.
For example, the Primary SIP Server of Profile 1 is 192.168.0.68:5060. In this case, P-Code is P47, P-Value is 192.168.0.68:5060.
17. Making Ringtone Notes
Prepare:
Tool: ringtool.exe
Ring file format: pcm
1. To make ring tone for UC9xx
1.1 Double click ringtool.exe
1.2 Select the Maximum Length and Output Filename:
For example, 16 seconds, ring 2.bin
1.3 Click Select to Input the desired ring tone file, and then click Generate Ringfile.
Then, you will get Ringfile Created.
1.4 Now, you get the ring2.bin, also you can rename it as ring5.bin, or other the one you want to replace.
1.5 Upload the ring file by TFTP or HTTP, the ringtone is replaced successfully.
18. LCD and Web Language Custom Guide
18.1 LCD Language custom guide
1. You need to contact us about how to obtain the Language.tar file.
2. Unzip the Language.tar using 7-zip tool.
3. Open the Language folder:
Note: The file name must be " digital_" at the beginning,the format of the file name is the order of the on the LCD.
4. For example, custom Chinese Language
If your country's language is not existing in the language folder, you can new a xml file with correct naming format. [e.g. 13_xxx(xxx).xml]
If your country's language in the folder, you can custom directly your language.
Open the LCD_English_Template.xml with UltraEdit→ Translate English into Chinese (Can't leave out any items, otherwise the upgrade failed) →save as 10_简体中文(ChineseSimplified).xml in Language folder (Coding format is UTF-8)
→ Select the Language folder→ Compress Language.tar package using 7-zip tool and Cover the original→Delete the Language folder
Note: |
If you want to put your language on the front of other languages, you can also rename the file, for example:
18.2 Web Language custom guide
1. You need to contact us about how to obtain the Language.tar file
2. Unzip the Language.tar using 7-zip tool.
3. Open the Language folder:
Note: The file name must be " digital_letter" at the beginning. The format of the file name is the order of that on the Web.
4. For example, custom Chinese Language
If your country's language is not existing in the language folder, you can new a xml file with correct naming format. [e.g. 13_xxx.js]
If your country's language in the folder, you can custom directly your language reference Web_English_Template.js.
Open the Web_English_Template.js with UltraEdit→ Translate English into Chinese (Can't leave out any items, otherwise the upgrade failed) →save as 10_ChineseSimplified.js in Language folder (Coding format is UTF-8)
→ Select the Language folder→ Compress Language.tar package using 7-zip tool and Cover the original→Delete the Language folder
Note: |
If you want to put your language on the front of other languages, you can also rename the file, for example:
When you finish the Language.tar, you must send the Language.tar package to us, then we provide the firmware to you.
19. LCD and Web GUI custom Guide
Unzip the hlpres.tar package (Need to contact us to obtain the hlpres.tar package)
You can replace some file in the hlpres to finish the customization of 1.1 to 1.7
19.1 How to custom the wallpaper1-wallpaper6?
Open hlpres folder→you can custom the wallpaper4.jpg-wallpaper6.jpg (dimension:480*320 size: through Photoshop tools make the size smaller→Select the hlpres folder→Compress hlpres.tar package
19.2 How to custom the screensaver1- screensaver3?
Open hlpres folder→you can custom the screensaver1.jpg-screensaver3.jpg (dimension:480*320 size:through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tar package
19.3 How to custom the weblogo?
Open hlpres folder→you can custom the weblogo.jpg (dimension:225*93 size: through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tar package
19.4 How to custom the eights menus(.png)in the main menu?
Open hlpres folder→you can custom the .png(dimension:65*65 size: through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tar package
19.5 How to custom the ...Icon.png?
Open hlpres folder→you can custom the ...Icon.png (dimension:65*65 size: through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tarpackage
19.6 How to custom the lcdlogo_color.png?
This logo is only applicable to UC923, UC924,UC924E, UC926, UC926E.
Open hlpres folder→you can custom the lcdlogo_color.png (dimension:400*42 size: through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tar package.
Enter Menu→Display→Screensaver Time-out:1min; Screensaver Type: Time & Logo→Save, this logo displays correctly.
19.7 How to customthe lcdlogo_bw.png?
This logo is only applicable to UC601, UC901, UC902, UC903, UC912/G/GM.
Open hlpres folder→you can custom the lcdlogo_bw.png (dimension:100*11 size: through Photoshop tools make the size smaller) →Select the hlpres folder→Compress hlpres.tar package.
Enter Menu→Display->Screensaver Time-out:1min; Scrrensaver Type:Time & Logo→Save, this logo display correctly.
The lcdlogo_bw.png's property must be the following standard:
Note:
The photo's name and format must be the same as before;
The size of hlpres file is not more than 2M.
When you finish the hlpres.tar, you must send the hlpres.tar package to us, then we provide the firmware to you.
20. Firmware Upgrade
Please note: When the phone whose firmware version is 1.0.3.62 or earlier upgrades to 1.0.3.73, you must put the upgrade files(include fw8xx.rom/ fw9xx.rom and img_8xx.bin/ img_9xx.bin ) into the server path and the phone will upgrade img_8xx.bin/ img_9xx.bin then automatically upgrade fw8xx.rom/ fw9xx.rom.
After upgrading to the new firmware, in the next time, you will only need to put one file fw8xx.rom/ fw9xx.rom into the server path. Upgrade steps of later than 1.0.3.73 version and earlier than 1.0.3.73 version is the same.
20.1 Upgrade through HTTP
To upgrade via HTTP, the "Management"->"Auto Provision" ->"Firmware Upgrade" -> "Upgrade Mode" field needs to be set to HTTP, respectively. "Firmware Server Path" needs to be set to a valid URL of a HTTP server, server name can be in either FQDN or IP address format. Here are examples of some valid URL.
e.g. firmware.mycompany.com:5688/Hanlong
e.g. www.mycompany.com:5688/fm/Hanlong
e.g. 218.2.83.110
Instructions for firmware upgrade via HTTP:
(1) End users can choose to download the free HTTP server from http://httpd.apache.org/ or use Microsoft IIS web server. Then set up HTTP server.
(2) Unzip the firmware file and put all of them under the root/phone directory of the HTTP server.
(3) Visit "http://192.168.0.106/phone/fw924.rom" on localhost by browser to verify the HTTP Server. If visiting "http://192.168.0.106/phone/fw924.rom" on other computer is no prompt to download fw924.rom file, please check the firewall (Suggest close the firewall).
(4) Change the setting of the IP Phone (192.168.0.106 is HTTP server):
Click "SaveSet".
(5) Restart the IP Phone, and it will restart and auto-get firmware files from HTTP server.
NOTES:
Htek recommends end-user use the Htek HTTP server. For large companies, we recommend to maintain their own TFTP/HTTP/FTP/HTTPS server for upgrade and provisioning procedures.
Once a "Firmware Server Path" is set, user needs to update the settings and restart the IP Phone. If the configured firmware server is found and a new code image is available, the IP Phone will attempt to retrieve the new image files by downloading them into the IP Phone's SDRAM. During this stage, the IP Phone's LEDs will blink fastly until the checking/downloading process is completed. Upon verification of checksum, the new code image will then be saved into the Flash. If TFTP/HTTP/FTP/HTTPS fails for any reason (e.g. TFTP/HTTP/FTP/HTTPS server is not responding, there are no code image files available for upgrade, or checksum test fails, etc), the IP Phone will stop the TFTP/HTTP/FTP/HTTPS process and simply boot using the existing code image in the flash.
Firmware upgrade may take as long as 3 to 8 minutes over Internet, or just 1 minutes if it is performed on a LAN. It is recommended to conduct firmware upgrade in a controlled LAN environment if possible.
Hanlong's latest firmware is available at www.htek.com →Support →Document & Firmware.
Oversea users are strongly recommended to download the binary files and upgrade firmware locally in a controlled LAN environment.
20.2 Upgrade through TFTP
(1) We recommend that you can install a TFTP Server(e.g. SolarWinds -TFTP -Server.exe).
(2) Make a new directory, such as D:\FM.
(3) Unzip the firmware file and put all of them under the directory D:\FM.
(4) The PC running the TFTP server and the IP Phone should be in the same LAN segment.
(5) Set TFTP Root Directory to D:\FM.
TFTP SERVER → File → Configure
(6) Go to File -> Configure -> Security to change the TFTP server's default setting from "Receive Only" to "Transmit Only" for the firmware upgrade.
(7) Start the TFTP server, Configure the Firmware Server Path with the IP address (192.168.0.240 is TFTP server) in the IP Phone's web configuration page.
(8) Save the change and restart the IP Phone.
(9) You can test your TFTP server by other PC which is in the same LAN segment.
For examples, in PC which IP address is 192.168.0.126, type command:
TFTP -i 192.168.0.240 get fw924.rom f:/fw924.rom
If your TFTP server is OK, something like "Transfer successful: " will be printed in command windows.
20.3 Upgrade through FTP
(1) Setup a FTP Server(e.g. FileZilla Server).
(2) Unzip the firmware file and put all of them under the root/phone directory of the FTP Server.
(3) Configure the FTP Server.
(4) Visit ftp://192.168.0.106/phone/fw924.rom on localhost by browser, enter username and password, and you will view upgrade file. If visiting ftp://192.168.0.106/phone/fw924.rom on other computer is no prompt to download fw924.rom file, please check the firewall (Suggest close the firewall).
(5) Configure the Firmware Server Path in the IP Phone's web configuration page.( 192.168.0.106 is FTP server)
(6) Click the "SaveSet" and then click "Restart" in the webpage.
20.4 Upgrade through HTTPS
(1) Install and configure an Apache HTTPS Server in local computer.
(2) Unzip the firmware file and put all of them under the root/phone directory of the HTTPS Server.
(3) Visit "https://192.168.0.106/phone/fw924.rom" on localhost by browser to verify the HTTPS Server. If visiting "https://192.168.0.106/phone/fw924.rom" on other computer is no prompt to download fw924.rom file, please check the firewall (Suggest close the firewall).
(4) Configure the Firmware Server Path in the IP Phone's web configuration page. (192.168.0.106 is HTTPS server)
(5) Click the "SaveSet" and then click "Restart" in the webpage.