Yealink Forums
personalized configuration settings protection not working - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Auto Provisioning (/forumdisplay.php?fid=14)
+--- Thread: personalized configuration settings protection not working (/showthread.php?tid=16823)



personalized configuration settings protection not working - jmdigneffe - 06-21-2016 10:07 PM

Hi,

Just tried on a bunch of T42G and T46G to setup the personalized settings protection but it's not working.

I added : "
auto_provision.custom.protect = 1
auto_provision.custom.sync= 1
"
to the provisioning file.

When the phones are booting they are trying to read the mac-local.cfg on the TFTP server and retry a few times but after that they never write the local settings to the TFTP.
I tried creating an empty dummy file but it doesn't help, it only prevent the retries

By pure luck it seemed to work on one of the phone while i did some tests but it stopped working after that without any reason.

I tested it with the 28.80.0.95 firmware on the T46Gs.

Any clue ?

Thanks in advance.


RE: personalized configuration settings protection not working - Karl_Yealink - 06-23-2016 10:43 AM

Hi,

I test here, any thing work normally.

Normally, the phone won't upload the file immediately after any configuration change.
Suggest that you can wait more time to test.

Any update, please let me know. Meantime, please tell me the auto provision URL.


RE: personalized configuration settings protection not working - haighj@kesw.org - 06-23-2016 09:06 PM

I may be wrong, but in our experience it doesn't update the MAC-local.cfg file to the server until after about 5min after the phone boots.


RE: personalized configuration settings protection not working - jmdigneffe - 06-24-2016 05:59 PM

Well it has been running for days and the TFTP log doesn't show any write request...
the autoprovision url is tftp://10.4.10.87/yealink/ It's a TFTP server on a local linux.
I tried upgrading to the latest firmware (28.80.0.125) but still the same.