Autoprovision Admin Password Set Fails

[brb5548]

Has anyone had issues with setting the admin password for yealink phones via provisioning? I am testing with the latest firmware on t21, t48g and cp920 and they will not set the admin password after a factory reset of the phone. I confirmed the common cfg file is set with the correct format:

security.user_name.admin = {$admin_name}
security.user_password = {$admin_name}:{$admin_password}

which translates to:
security.user_name.admin = admin
security.user_password = admin:12345

I have also tried the newer configuration template that uses 'static' (but only for these two fields):

static.security.user_name.admin = {$admin_name}
static.security.user_password = {$admin_name}:{$admin_password}

Setting the password works fine on other models (t29g, t42s, and t20 all work fine).

Scratching my head a bit and will open a ticket with yealink but thought I would ask here first.

 

[JamesBorne]

As a test, change the password manually on the cp920 and export the config and see what changed.

 

[brb5548]

I tried to do that but the config exports don't appear to show the passwords.

 

[DigitalDaz]

But they will show you the field you should be using?

 

[brb5548]

I see the value being set for the admin password and I also see other values being set. I can update the phone's configuration on the fly via the device configuration in fusionpbx but the admin password is never being updated. I opened a ticket and will update when I get a response back.

 

[gunemalli]

Yealink export CFG function removes any/all passwords as a security measure. So you would not see any passwords in plain text.

 

[JamesBorne]

Point isn't to see passwords @gunemalli, it's to capture the required variables; which would be there, just blanked out.

 

[benw]

do not turn on admin name in default settings as it does have issues cross the board with other devices.

easier to leave just password set

here is the string for device admin though

#Device Admin
security.user_password = admin:{$admin_password}

 

[Craig Fox]

This is a confirmed bug by Yealink. It's been a while since I opened the case with them and they haven't done anything to my knowledge. It has to do with the admin name and password being set at the same time. Basically, when the phone changes the name during the provision process it no longer knows where to set the password. So you can change either the password or the username but not both.

Of course, all this is via provisioning. You can do this manually all day. Yealink's advice "do this is two separate processes"... I never figured how to really do that.

Note... It has to do with the new "no override" (forget the technical term) settings in the latest templates as this used to work just fine.