Detailed boot process and ways to add local configuration?

[DanH]

(I post here since I was not able to post this text below in "Auto Provisioning". I appologize.

However, ultimatively it's a question about configuration.. :-)

Is there somewhere a detailed description of the boot process of yealink phones available?

I mean really detailed. I find lots of information on the boot process, but distributed in several places in several detail levels. However, I did not find anywhere a description that includes for example a (boot) flow diagram or the complete boot process from applying power, until the phone is ready to be used.

On each step through the boot process, there are several ways to give a configuration to a phone.
Also the boot process is different between a phone that has no configuration (i.e. there was a factory reset), and a phone that has a configuration.

Why do I ask these questions?
1 - I would like to understand de boot sequence in detail
2 - I want to find out when and how I can introduce additional configuration to a phone


Example:
I have phones (T46S) that are autoprovisioned by an asterisk server located in the cloud. Unfortunately, I cannot change the .cfg files that server is providing to the phones as I do not have direct access to those files on the asterisk server.
The phones need some additional configuration that the server config files are not delivering. Since I cannot add an include file on the server, which would be the most elegant solution, I need to find another way.
The question here is where and in what boot phase can I add those configurations to the phone, without access to the .cfg files on the server?
I could introduce a tftp server with DHCP, but I would have to be careful not to break the provisioning relationship between the phone and the asterisk server.

So, can I tell the phone during the boot process something like:
"Here is your IP address and there is a tftp server.. but only load one small .cfg file on the tftp server and then continue with getting the rest of your configuration from your autoprovisioning server in the cloud..

Having better knowledge of the boot process in detail might help me understand.

Thanks for your help
Dan