Yealink Teams Phones Auto Provisioning
We’ve had multiple customers recently ask for how to bypass setting the admin password during the OOBE. I finally sat down and spent time working on it.
First, I spent way too much time trying to set multiple things. The one thing we can do is bypass setting the password during OOBE. You CANNOT bypass OOBE. EDIT: Yes, you can. See below.
Here are the docs from Yealink: Yealink Support - (HD IP Phones Auto Provisioning Guide (this applies to all of the MPXX devices))
First step, fire up your provisioning server of choice. I used SolarWinds TFTP server here on my home network. You can put the files on a accessible website (HTTP/HTTPS), FTP, TFTP site.
You will need to set DHCP Option 66 and/or Option 43 to point at your provisioning server.
Then, there are two files needed. The first is the BOOT file and all it does is point at the CFG file.
The BOOT file must be named y000000000000.boot OR you can get MAC specific by doing the MAC Address with a .boot extension. Obviously if you do the MAC specific, it will only apply to that specific phone.
Here is what needs to be in the BOOT file:
#!version:1.0.0.1
overwrite_mode=1
include:config <tftp://aaa.bbb.ccc.ddd/general.cfg>
In the “include” line, you must put the specific URL/address to where your CFG file is kept.
Then, you can put this in the CFG file:
#!version:1.0.0.1
overwrite_mode=1
# Bypass Setting Admin Password During OOBE
security.password_use_default.mode=0
Once that is there, the security.password_use_default.mode=0 will make it so during OOBE the phone won’t ask for an admin password.
This leaves a problem though, the default username/password combo of admin:admin is left in tact. You cannot set the admin password via the provisioning server. IMO, this is good as it is all kept in plain text.
That means in order to set the password, you must utilize the Configuration Profiles in Teams. In here, you can set the admin password (along with things like time zones, etc.). This is the proper place to do these configs so that a customer can maintain them.
I will give my unsolicited opinion here, I don’t think customers should globally deploy the provisioning server. I would suggest that they place it on a VLAN where they can setup the phones and boot them and go through the OOBE and then place them on desks. That would be the best way so that they don’t end up with conflicting Option 66 or Option 43 settings but I also get for the speed of a deployment putting it out there across the network is not that big of a deal.
Hopefully this helps folks who are trying to deploy these types of phones!
UPDATE Thanks to Yealink, I found the magic command to skip the OOBE!
You need to add setup_wizard.completed=1 to the file to make it skip OOBE. So your CFG file should look like this:
#!version:1.0.0.1
overwrite_mode=1
# Bypass Setting Admin Password During OOBE
security.password_use_default.mode=0
setup_wizard.completed=1