T23G Auto Provisioning Issues

[Billyy]

I have been trying to set up a provisioning server for our Yealink phones and have had some success but I can't get the T23G phone I have to provisioning. I've managed to get a T26P, T21P E2, and T29G phone to connect to the server and download their respective configuration files, but while the T23G can reach the server it can't download any config files.

They all have the same auto provisioning configuration: IP Address, User, Password, Certificate, Certificate settings, and the T23G has the latest firmware but for some reason it does not want to provision. This is the first time I've set up anything like this and it's been quite challenging building it all from scratch so any help would be appreciated.

I've attached a pcap and level 6 log file, as well as a few screen shots of my configuration. Also I noticed on my server logs (IIS 10.0) that the same HTTP error keeps appearing (500 - Internal server error) and the same Windows error (64 - The specified network name is no longer available)


Thank you

[complex1]

Hi,

Strange, the only phone you cannot get provisioned is the T23G phone with the same setting as the other phones.
Please remove (if possible) the “PCL-SVR.pcl.local” certificate first and change the Provision Server URL in http://192.168.66.9 then try again.

Hope this will help.

[Lucia_Yealink]

Dear Sir,

I am afraid you do not provide the level 6 syslog, but only the pace trace and the config.bin, the information is not enough to locate the problem.

Please kindly provide the level 6 syslog, config.bin and pace trace in one time when you reproduce the issue.

To make a comparision, please also provide the three files when you use other model to do auto provision succeed. Then we can locate the problem more easily.

Please refer to the FAQ below to collect the three files:
http://support.yealink.com/faq/faqInfo?id=313

Also, can you also provide your server log to us to check? What do you mean about the Window error? Please also provide it.

Besides, may i know how many phones you have in total? And how many of them have the issue?

Looking forward to your reply.

Best Regards
Lucia

[Billyy]

I removed the certificate and changed the URL to http but still no luck.

[Billyy]

(08-29-2017 03:37 AM)Lucia Wrote:  Dear Sir,

I am afraid you do not provide the level 6 syslog, but only the pace trace and the config.bin, the information is not enough to locate the problem.

Please kindly provide the level 6 syslog, config.bin and pace trace in one time when you reproduce the issue.

To make a comparision, please also provide the three files when you use other model to do auto provision succeed. Then we can locate the problem more easily.

Please refer to the FAQ below to collect the three files:
http://support.yealink.com/faq/faqInfo?id=313

Also, can you also provide your server log to us to check? What do you mean about the Window error? Please also provide it.

Besides, may i know how many phones you have in total? And how many of them have the issue?

Looking forward to your reply.

Best Regards
Lucia

Sorry I though I had attached the level 6 log. i have attached the pcap & level 6 logs for all phones as requested (I hope). At the moment I am just testing with the 4 phones I have mentioned and it is just the T23G that has the issue.

I've also attached the log from my server. The last 4 columns are sc-status (500), sc-substatus, sc-win32-status (64), and time-taken. The 500 refers to the "Internal server error" http error, and the 64 refers to the "The specified network name is no longer available" Windows error. I only mentioned those in case they helped to troubleshoot things

Thank you.

[Lucia_Yealink]

Dear Sir,

I have checked the level 6 syslog you provide, and find it is Peek Error, like the picture:
   

Please use the parameter below to do auto provision and test:
auto_provision.attempt_expired_time = 20

Best Regards
Lucia

[Billyy]

(09-04-2017 03:05 AM)Lucia Wrote:  Dear Sir,

I have checked the level 6 syslog you provide, and find it is Peek Error, like the picture:


Please use the parameter below to do auto provision and test:
auto_provision.attempt_expired_time = 20

Best Regards
Lucia

I have changed that setting to 20 but still no luck.

[Lucia_Yealink]

Dear Sir，

Thank you for your test.
I have submited the files to our R&D to double check and locate the issue, any update, will let you know.

Besides, may i know how many phones you have in total? What about T23G?

Best Regards
Lucia

[Billyy]

(09-07-2017 01:53 AM)Lucia Wrote:  Dear Sir，

Thank you for your test.
I have submited the files to our R&D to double check and locate the issue, any update, will let you know.

Besides, may i know how many phones you have in total? What about T23G?

Best Regards
Lucia

I'm just testing with 4 different phones one of which is the T23G, the others are a T26P, a T29G, and a T21P E2

Thank you for your help

[Lucia_Yealink]

Dear Sir,

I have just got the analyze result from our R&D, please see below:

1. when do the SSL handshake, the other side can not recognize the handshare message the T23 sent, and set the reset message to T23 to request negotiate again which cause the problem.

  ssl.bmp (Size: 2.16 MB / Downloads: 10)
2. check the info of T29G, the T29G use the TLS1.0, but the T23 use the TLS1.2, for the present, the server feedback with 500 error when the phone use TLS1.2.

  second.bmp (Size: 1.84 MB / Downloads: 7)
Suggestion configure the T23 to use the TLS1.0

Method:
use the HTTP to do auto provision with the parameter below to configure the TLS version as 1.0
static.security.default_ssl_method = 0

After configure like above, if the issue still exist, please provide the test accounts, config,bin, pace trace and syslog for us to do further test and analyze.
(You can sent the test account to Lucia@yealink.com)

Best Regards
Lucia