(04-18-2019 06:22 PM)jolouis Wrote: Not sure about your point #2 with the DSS keys but generally Yealink tries to do provisioning "in the background". So normally the phone will boot, show the already configured setup on the display, and then a few seconds later after it has sent out provisioning requests and received updated config, it will do the merge and apply the updated settings.
Typically from time of the display showing the "normal idle" state to the updated one I expect it to be around 10-20 seconds, but that's using an unencrypted provisioning file being served by a local device rather than something "out in the cloud". You might be encountering additional delays due to provisioning file generation, network latency, etc.
Easiest way to tell for sure is to turn the syslog up to level 6, then reboot and let the phone do it's provisioning/updates. When you look at the syslog entries, you'll see lines for either ATP or AUTOP (depending on what Firmware version you're running). They are all timestamped, so you should be able to follow through the process and see if there are any excessive delays anywhere.
For reference, if your goal is simply to enable/disable Account 2 it may be faster to provision all of the account details at the same time your provision account 1, but just leave it disabled. Then, when you want to actually activate it, provision just the "account.2.enabled" as the only difference. I have not dealt with this in a while, but a few versions back that used to be the more efficient way of doing it.
In the past, I haven't seen much of a delay at all from cloud provisioning. However, you may have a point. There could be changes with our Cloud PBX provider causing slowness with authentication and configuration download. I could try later times for this and compare with busier times during the day.
Regarding #2---without programming any other DSS keys except the first 3 account 1 line keys. I move on to doing a provision that adds the second account from a config file.
Normally, the Yealink phone would then add the account 2 line key after the 3 account 1 line keys and it happens rather quickly. However, recently during the configuration/provisioning for account 2, all the unprogrammed DSS keys display as a I mentioned in my original post. I will call them ghost DSS keys. Once the configuration/provisioning finishes, then the single account 2 line key displays in one location and all the ghost DSS keys go back to their default setting.
