Yealink W52H Инструкция по работе с сервером Autoprovision онлайн [43/180] 166932
![Yealink W52P Инструкция по работе с сервером Autoprovision онлайн [43/180] 166931](/views2/1192029/page43/bg2b.png)
Downloading and Updating Configuration Files
35
After obtaining the provisioning server address in one of the ways introduced above,
the phone will request to download the configuration files from the provisioning server
when it is triggered to perform auto provisioning. During the auto provisioning process,
the phone will try to download the y000000000025.cfg file firstly, and then the
<MAC>.cfg file from the provisioning server. If the access URLs of the resource files
have been specified in the configuration files, the phone will try to download and
update the resource files.
After downloading, the phone resolves the configuration files and resource files (if
specified in the configuration files), and then updates the configurations and resource
files to the phone flash. Generally, updated configurations will automatically take effect
after the auto provisioning process is completed. For update of some specific
configurations which require a reboot before taking effect, for example, network
configurations, the phone will reboot to make the configurations effective after the auto
provisioning process is completed.
The phone calculates the MD5 values of the downloaded files before updating them. If
the MD5 values of the y000000000025.cfg and <MAC>.cfg configuration files are the
same as those of the last downloaded configuration files, this means that these two
configuration files on the provisioning server are not changed. The phone will complete
auto provisioning without repeated update. This is used to avoid unnecessary restart
and impact of phone use. On the contrary, the IP phone will update configurations.
If the configuration files have been AES encrypted, the phone uses the Common AES
key to decrypt the y000000000025.cfg file and the MAC-Oriented AES key to decrypt the
<MAC>.cfg file after downloading the configuration files.
The latest values to be applied to the IP phone are the values that take effect.
The phone only reboots when there is at least a specific configuration requiring reboot
after auto provisioning. If you want to force the IP phone to perform a reboot after auto
provisioning, you can configure “auto_provision.reboot_force.enable = 1” in the
configuration file.
For more information on the specific configurations which require reboot during
provisioning and the parameter “auto_provision.reboot_force.enable”, refer to the
section Description of Configuration Parameters in CFG Files on page 69.
Содержание
- Obtaining provisioning server address 21 p.3
- Getting started 3 p.3
- Table of contents iii p.3
- Summary of changes vii p.3
- Introduction 1 p.3
- Troubleshooting 51 p.4
- Downloading and updating configuration files 35 p.4
- Configuring the updating mode 27 p.4
- Appendix 53 p.4
- Local cfg file p.20
- Specifying the access url p.25
- Specifying the access url p.26
- Example 2 yealink w52p ip dect phone downloads the configuration files from the ftp p.45
- Users would like to remain the personalized settings e g ring tone dial plan and p.45
- The personalized settings protecting process p.45
- Several specific scenarios are illustrated in the following sections to assist in explaining p.45
- Server p.45
- Or later can be configured to protect personalized settings after auto provisioning p.45
- Handset name after auto provisioning w52p ip dect phones running firmware version p.45
- Generally the administrator deploys ip phones in batch via auto provisioning yet some p.45
- Example 3 yealink w52p ip dect phone downloads the configuration files from the http p.45
- Custom handset keypad_tone enable p.48
- Custom handset keypad_light enable p.48
- Custom handset eco_mode enable p.48
- Custom handset confirmation_tone enable p.48
- Custom handset backlight_out_of_charger enable p.48
- Custom handset backlight_in_charger enable p.48
- Custom handset auto_intercom p.48
- Custom handset auto_answer enable p.48
- Custom handset voice_mail_notify_light enable p.48
- Custom handset missed_call_notify_light enable p.48
- Custom handset low_battery_tone enable p.48
- To the phone flash and take effect p.58
- The web user interface prompts upload local configuration succeeded p.58
- The existing local configuration file will be overridden by the imported one after p.58
- Importing the configurations in the importing 001565221229 local cfg file will be saved p.58
- If the administrator or user deletes the configurations in the 001565221229 local cfg file p.58
- But the configurations can be change via next auto provisioning p.58
- And then import the file to the phone the ip phone will remain the original configurations p.58
- Ensure that the ethernet cable is plugged into the internet port on the phone and p.59
- Why does not the phone obtain the ip address from dhcp server p.59
- Ensure that the configuration files exist on the provisioning server p.59
- Troubleshooting p.59
- Ensure that the access url is correct p.59
- This chapter provides general troubleshooting information to help you solve problems p.59
- Ensure that auto provisioning feature is enabled p.59
- The ethernet cable is not loose p.59
- Ensure that authentication credentials configured on the phone are correct p.59
- System administrator p.59
- Permission p.59
- Contact your system administrator for more information p.59
- On the provisioning server check the file permissions if necessary change the file p.59
- If you require additional information or assistance with the deployment contact your p.59
- Ensure your phone is configured to obtain the ip address via dhcp server p.59
- Ensure the configurations of network are properly set in the configuration files p.59
- Ensure that your settings are right on the dhcp server p.59
- You might encounter when deploying yealink w52p ip dect phones p.59
- Ensure that the switch or hub in your network is operational p.59
- Why the permission is denied when uploading files to an ftp server p.59
- Ensure that the root directory of the ftp server contains the complete directory path p.59
- Why does the provisioning server return an http 404 error p.59
- Ensure that the requested configuration files exist on the http server p.59
- Why does the phone fail to download configuration files p.59
- Ensure that the provisioning server or the network is reachable p.59
- Why does the phone display network unavailable p.59
- Ensure that the http server is properly set up p.59
- Yealink w52p ip dect phones auto provisioning guide p.60
- Why does not the phone apply the configurations p.60
- Ensure the phone have downloaded the configuration files p.60
- Ensure the parameters are correctly set in the configuration files p.60
- Ensure the file header in the configuration file is not deleted p.60
- Contact your system administrator for more information p.60
- Yealink_w52p_ip_dect_phones_deployment_guide_for_broadsoft_uc one_environment p.171
- X 3 93 x p.171
- Uc one firmware version p.171
- The following table lists configuration parameters that are integrated with broadsoft platform for more information on broadsoft features refer to p.171
- The following parameters are not applicable to ip phones running firmware version 73 or later so the description of these parameters has been deleted in p.175
- This guide p.175
- Yealink w52p ip dect phones auto provisioning guide p.180
Похожие устройства
-
Yealink W52HСравнительная таблица оборудования -
Yealink W52HТехнические характеристики -
Yealink W52HКраткое руководство пользователя -
Yealink W52HИнструкция по эксплуатации -
Yealink W52PСравнительная таблица оборудования -
Yealink W52PТехнические характеристики -
Yealink W52PИнструкция по работе с сервером Autoprovision -
Yealink W52PКраткое руководство пользователя -
Yealink W52PИнструкция по эксплуатации -
Yealink W56HИнструкция по эксплуатации -
Yealink W56PИнструкция по эксплуатации -
Panasonic KX-TG6712RUMтРуководство по эксплуатации