Yealink Forums

Full Version: Auto Provisioning Hangs
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Here is my issue:
A T46G running 28.73.0.28 boots and looks at the Yealink RPS where it picks up the url: https://<provurl>/Yealink/enc.cfg

The enc file is there to tell the phone to use encryption and then provide a new url: https://<provurl>/Yealink

This is where the <mac>.cfg, <mac>_Security.enc and Aeskey.txt files are kept.

This works very well if the firmware is, for example: 28.83.0.35

But with the earlier firmware, the enc.cfg file is accessed but the phone never loads.


I have tried including the following inside the enc.cfg file: but the phone still will not load the file so cannot pickup the firmware upgrade.
firmware.url = https://<provurl>/Yealink/Firmware/28.83.0.10.rom

even if I include: auto_provision.reboot_force.enable =1

Have you any clues as to what is going wrong here?

enc.cfg attached
(10-16-2018 11:49 AM)Rus Wrote: [ -> ]Here is my issue:
A T46G running 28.73.0.28 boots and looks at the Yealink RPS where it picks up the url: https://<provurl>/Yealink/enc.cfg

The enc file is there to tell the phone to use encryption and then provide a new url: https://<provurl>/Yealink

This is where the <mac>.cfg, <mac>_Security.enc and Aeskey.txt files are kept.

This works very well if the firmware is, for example: 28.83.0.35

But with the earlier firmware, the enc.cfg file is accessed but the phone never loads.


I have tried including the following inside the enc.cfg file: but the phone still will not load the file so cannot pickup the firmware upgrade.
firmware.url = https://<provurl>/Yealink/Firmware/28.83.0.10.rom

even if I include: auto_provision.reboot_force.enable =1

Have you any clues as to what is going wrong here?

enc.cfg attached

I have drilled down into this a little.

It seems that any fw release below 80 and below, does not correctly access the enc file.
all releases (tested 73-83) access the RPS which points to the provisioning url and includes the filename enc.cfg. However only fw v83 appears to attempt to access the enc.cfg file.

This only seems to have become an issue with the RPS redesign.

Is anyone else having these issues or know how to resolve?
Reference URL's