YEALINK NETWORK TECHNOLOGY CO.,LTD.

www.yealink.com

Auto Provisioning Issue

 Feature mechanism:
You can refer to the latest Yealink “Auto Provisioning” guide on support.yealink.com for the
details.
Below is the process of the whole provisioning, during the steps, some points need to make
sure
1） The phone send the request to the provisioning URL to download CFG files
Note: The provisioning URL can be obtained through RPS, DHCP, PNP, Phone flash, so in this
scenario, please make sure the phone can obtain the correct URL, if the phone can’t obtain the
correct URL, the phone can’t do the following steps.
2） Phone first require for the Common.cfg and then for the MAC.cfg
Note: if URL can’t be accessed, it will show like below:

If you use HTTP auto provisioning server, you can see below information in the trace.

You can find the URL in the Get packet

1
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com

Normally you can see the server response with 200 OK means the files has been downloaded
successfully.
You can copy the content of CFG file through the 200OK packet, the method:
Expand the packet, right click “Hypertext Transfer Protocol “, Copy->Bytes->Printable Text Only

And then copy the content in the UE.

2
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
Note: You can find the data sent from the TFTP server by catch the trace as well.

If using HTTPS, we can’t find the details in the trace, but we can find the details through level 6
syslog as well.
Below you can find the phone first request for the Common.cfg and then MAC.cfg.

3） If the phone find the CFG doesn’t exist, it will send three requests to make sure the files
really doesn’t exist.

4） The phone won’t apply the setting until all the files have been finished downloaded, first
apply the setting and then the upgrade the rom file.
Note, the phone will store a MD5 for each files downloaded, you can find the MD5 in the
config.bin file (encrypted from the version V73).
Like below, the phone only has downloaded Common.cfg file, so only record the MD5 for the

3
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
Common.cfg file.
MD5_CFG = 70d33b463f01507a51285ba30a62d9e0
MD5_MAC_CFG =
5） When the phone doing auto provisioning next time, it will compare the new MD5 with the
MD5 stored in the phone, if they are not the same, the phone will apply the setting in the
CFG and update the MD5 value but it will end the auto provision if the new MD5 is the same
as previous, it won’t do any apply, you can find “MD5 is the same “in the log.
You can filter the log with ATP message, please note, after the phone doing provisioning, if you
change the settings on the phone manually, the MD5 stored in the phone won’t change, and in
this case, if you didn’t change the CFG files in the provisioning server, the phone won’t apply the
setting in the CFG file.
This LOG you can find it show “MD5 is the same “, the phone won’t apply the setting.

The Log show the MD5 is different, so it will do provisioning and apply the settings.

4
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com

 Issue Description:
Issue 1: The phone fail do download CFG files.

 Resolution: （Checking list）

1） Check whether the phone has obtained the correct URL.
If using RPS, please refer to below FAQ: http://support.yealink.com/faq/faqInfo?id=22
If using DHCP, please make sure the environment is correct, you can catch the trace to check,
for example DHCP option 43.Filter with ‘bootp’

5
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
2） If the phone can obtained URL, the phone will send the request to the provisioning server, if
not using HTTPS, we can check the trace. You can refer to the level 6 syslog for all the
scenarios.
We need to check the URL is correct, the phone can visit the URL normally --- in this case, we
can ask the customer copy the URL (the full path) to the web browser to see if the web
browser can download the CFG file.

If using HTTPS, please make sure the phone has the imported the correct certificate in the
phone. You can check the trace, filter with SSL, you can find “bad certificate” or “unknown
certificate”

And also you can find some information in the log to prompt the download is failed：
HttpsDownload
May 18 00:00:43 Log [588]: TASK<6+info > ssl_trust[1]
May 18 00:00:43 Log [588]: ETLL<6+info > mkit_call return(0,0,0='^D')
May 18 00:00:43 Log [588]: TASK<6+info > dl_http_recv_to_file: return -3, code_msg :
Connect Failed
May 18 00:00:43 Log [588]: TASK<6+info > download Fail

Or like below：

Apr 22 00:02:10 LIBD[484]: DCMN<6+info > SSL_connect (read done)

Apr 22 00:02:10 LIBD[484]: DCMN<6+info > Server Certificate verify error!
Apr 22 00:02:10 LIBD[484]: HTTP<3+error > Connect Error
Apr 22 00:02:10 ATP [484]: ATP <3+error > https to file failed, code = -3, msg = Connect
Failed, retry = 2

We can disable the “Only Accept Trusted Certificates” under Security->Trusted Certificates to
verify the issue, if disabled this option, the phone can do provisioning successfully but fail
when enabled this option, means the issue is really caused by the certificate.
In this case, ask the customer to upload the certificate or disable “Security->Trusted

6
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
Certificates” to fix the issue.

3) If the provisioning is domain name, please make sure the DNS server has configured normally,
the phone can resolve the correct IP. If the phone can’t resolve the IP, and it will show like below:
May 29 15:09:12 LIBD[484]: DCMN<6+info > URL After Modify = http://xsp.yealinkpbx.net/dms/Yeali
nkT46G/0015655b5c40-

local.cfg

May 29 15:09:12 LIBD[484]: DCMN<6+info > Connecting xsp.yealinkpbx.net:80

May 29 15:09:12 LIBD[484]: DCMN<3+error > getaddrinfo: Name or service not known
May 29 15:09:12 LIBD[484]: HTTP<3+error >

Connect Error

If it can resolve the IP, it will show like below：

May 29 15:30:49 LIBD[387]: DCMN<6+info > URL After Modify = http://xsp.yealinkpbx.net/dms/Yeali

nkT46G/28.73.193.50.rom
May 29 15:30:49 LIBD[387]: DCMN<6+info > Connecting xsp.yealinkpbx.net:80

May 29 15:30:49 LIBD[387]: DCMN<6+info > onnecting IP = 66.63.192.111, Port = 80

If all the above steps can’t fix the issue, ask the customer to provide config.bin files (before and after
provisioning), trace ,level 6 syslog and CFG files for Yealink do debug.

 Issue Description:
7
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com
Issue 2: The phone has downloaded the auto provisioning files (CFG) but doesn’t apply the
setting

 Resolution: （Checking list）

1) Ask the customer to provide the config.bin file and the CFGs that can test locally.
2) Make sure CFG is correct, the format is correct, can refer to below FAQ
http://support.yealink.com/faq/faqInfo?id=27
3) Make sure the MD5 is different from the previous one.
4) The CFG file can read, if it is encrypted, make sure the phone has added the related AES
key.
5) If you can find “Peek error” in syslog, the reason is servers send update file to phone
after more than 5 seconds.

The default download time of Yealink phone is 5 seconds, if server sends update files
after more than 5 seconds, it will fail. You can change the setting by
“auto_provision.attempt_expired_time = 20”. 20 seconds is the maximum value.
6) Make sure whether the CFG has contained firmware upgrade, as mentioned above, the
firmware upgrade process is in the last step.
So it may cause an issue like below,
Current version is .1, included a parameter value is A
CFG has changed the value from A to B
But the parameter is configured with A in the firmware .2 and it take effect after upgrade, so
once the firmware is upgrade to .2, the value will be changed back to A.

If all the above steps can’t fix the issue, ask the customer to provide config.bin files (before and after
provisioning), trace, level 6 syslog and CFG files for Yealink do debug.

Note, normal process you can see in the http server：

8
 YEALINK NETWORK TECHNOLOGY CO.,LTD.
www.yealink.com