![Yealink W52P Инструкция по работе с сервером Autoprovision онлайн [13/180] 166931](/img/pdf.png)
Yealink W52P Инструкция по работе с сервером Autoprovision онлайн [13/180] 166931
![Yealink W52P Инструкция по работе с сервером Autoprovision онлайн [13/180] 166931](/views2/1192029/page13/bgd.png)
Getting Started
5
3. Click to locate the TFTP root directory you have configured from the local
system.
4. Click Confirm to finish configuring the TFTP server.
The server URL “tftp://IP address of provisioning server/” (e.g., tftp://192.168.1.100/) is
where the IP phone downloads configuration files from.
Before auto provisioning, you need to obtain configuration files. There are 2
configuration files both of which are CFG-formatted. We call these two files Common
CFG file and MAC-Oriented CFG file. IP phones try to download these two configuration
files from the provisioning server during auto provisioning.
IP phones with firmware version 73 or later also support a local configuration file named
as <MAC>-local.cfg. When a user modifies configurations of the base station via the
handset or web user interface, the configurations will be automatically saved to the
<MAC>-local.cfg file on the IP phone.
The <MAC>.cfg and <MAC>-local.cfg files are only effectual for the specific phone.
They use the 12-digit MAC address of the phone as the file name. For example, if the
MAC address of the phone is 0015651130F9, the <MAC>.cfg and <MAC>-local.cfg files
have to be named as 0015651130F9.cfg and 0015651130F9-local.cfg respectively.
However, the Common CFG file is effectual for all phones of the same phone model. The
Common CFG file of the W52P IP DECT phone uses the fixed name “y000000000025.cfg”.
You can export/import the <MAC>-local.cfg file via web user interface. For more
information on how to export/import a local configuration file, refer to Scenario D
Importing or exporting the local configuration file on page 48.
You can ask the distributor or Yealink FAE for the y000000000025.cfg and <MAC>.cfg
The <MAC>-local.cfg file only saves configurations of the base station configured via
the handset or web user interface. Configurations of the handset cannot be saved to the
<MAC>-local.cfg file.
Содержание
- Getting started 3 3
- Introduction 1 3
- Obtaining provisioning server address 21 3
- Summary of changes vii 3
- Table of contents iii 3
- Appendix 53 4
- Configuring the updating mode 27 4
- Downloading and updating configuration files 35 4
- Troubleshooting 51 4
- Local cfg file 20
- Specifying the access url 25
- Specifying the access url 26
- Example 2 yealink w52p ip dect phone downloads the configuration files from the ftp 45
- Example 3 yealink w52p ip dect phone downloads the configuration files from the http 45
- Generally the administrator deploys ip phones in batch via auto provisioning yet some 45
- Handset name after auto provisioning w52p ip dect phones running firmware version 45
- Or later can be configured to protect personalized settings after auto provisioning 45
- Server 45
- Several specific scenarios are illustrated in the following sections to assist in explaining 45
- The personalized settings protecting process 45
- Users would like to remain the personalized settings e g ring tone dial plan and 45
- Custom handset auto_answer enable 48
- Custom handset auto_intercom 48
- Custom handset backlight_in_charger enable 48
- Custom handset backlight_out_of_charger enable 48
- Custom handset confirmation_tone enable 48
- Custom handset eco_mode enable 48
- Custom handset keypad_light enable 48
- Custom handset keypad_tone enable 48
- Custom handset low_battery_tone enable 48
- Custom handset missed_call_notify_light enable 48
- Custom handset voice_mail_notify_light enable 48
- And then import the file to the phone the ip phone will remain the original configurations 58
- But the configurations can be change via next auto provisioning 58
- If the administrator or user deletes the configurations in the 001565221229 local cfg file 58
- Importing the configurations in the importing 001565221229 local cfg file will be saved 58
- The existing local configuration file will be overridden by the imported one after 58
- The web user interface prompts upload local configuration succeeded 58
- To the phone flash and take effect 58
- Contact your system administrator for more information 59
- Ensure that authentication credentials configured on the phone are correct 59
- Ensure that auto provisioning feature is enabled 59
- Ensure that the access url is correct 59
- Ensure that the configuration files exist on the provisioning server 59
- Ensure that the ethernet cable is plugged into the internet port on the phone and 59
- Ensure that the http server is properly set up 59
- Ensure that the provisioning server or the network is reachable 59
- Ensure that the requested configuration files exist on the http server 59
- Ensure that the root directory of the ftp server contains the complete directory path 59
- Ensure that the switch or hub in your network is operational 59
- Ensure that your settings are right on the dhcp server 59
- Ensure the configurations of network are properly set in the configuration files 59
- Ensure your phone is configured to obtain the ip address via dhcp server 59
- If you require additional information or assistance with the deployment contact your 59
- On the provisioning server check the file permissions if necessary change the file 59
- Permission 59
- System administrator 59
- The ethernet cable is not loose 59
- This chapter provides general troubleshooting information to help you solve problems 59
- Troubleshooting 59
- Why does not the phone obtain the ip address from dhcp server 59
- Why does the phone display network unavailable 59
- Why does the phone fail to download configuration files 59
- Why does the provisioning server return an http 404 error 59
- Why the permission is denied when uploading files to an ftp server 59
- You might encounter when deploying yealink w52p ip dect phones 59
- Contact your system administrator for more information 60
- Ensure the file header in the configuration file is not deleted 60
- Ensure the parameters are correctly set in the configuration files 60
- Ensure the phone have downloaded the configuration files 60
- Why does not the phone apply the configurations 60
- Yealink w52p ip dect phones auto provisioning guide 60
- The following table lists configuration parameters that are integrated with broadsoft platform for more information on broadsoft features refer to 171
- Uc one firmware version 171
- X 3 93 x 171
- Yealink_w52p_ip_dect_phones_deployment_guide_for_broadsoft_uc one_environment 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 175
- This guide 175
- Yealink w52p ip dect phones auto provisioning guide 180
Похожие устройства
- Yealink W52P Технические характеристики
- Yealink W52P Сравнительная таблица оборудования
- Yealink W52H Инструкция по эксплуатации
- Yealink W52H Краткое руководство пользователя
- Yealink W52H Инструкция по работе с сервером Autoprovision
- Yealink W52H Технические характеристики
- Yealink W52H Сравнительная таблица оборудования
- Yealink SIP-T48G Инструкция по эксплуатации
- Yealink SIP-T48G Краткое руководство пользователя
- Yealink SIP-T48G Руководство администратора
- Yealink SIP-T48G Инструкция по работе с сервером Autoprovision
- Yealink SIP-T48G Сброс настроек телефона
- Yealink SIP-T48G Технические характеристики
- Yealink SIP-T48G Сравнительная таблица оборудования
- Yealink SIP-T46G Инструкция по эксплуатации
- Yealink SIP-T46G Краткое руководство пользователя
- Yealink SIP-T46G Руководство администратора
- Yealink SIP-T46G Инструкция по работе с сервером Autoprovision
- Yealink SIP-T46G Сброс настроек телефона
- Yealink SIP-T46G Технические характеристики
Скачать
Случайные обсуждения