AutoProvisioning Yealink Phones on a Multi-Tenant Server

Nubink

New Member
Mar 7, 2025
3
0
1
56
I'm either missing something, the provider is missing something, or it's just not possible...

1. Phone's Admin Password.
This seems to be set, after the first autoprovision, to whatever is set at the top level of the FusionPBX server.

I manage a couple of services running at domain1.fusionpbx-server.tld and domain2.fusionpbx-server.tld. I have no control over the top level server.

When provisioning phones on either of these services, the phones are given the same Admin password. Is there a way to configure the whole system such that phones admin passwords provisioning (and, by extension, user passwords) are delegated to the subdomains?

2. Configuring phone settings other than keys
As a trivial example, I have been trying to set the background image (I have actually been trying other settings too, but to no avail)
I have a devices profile which contains settings that I have gleaned from various places (I think the final solution was from a post here). In that profile I have the following settings:

NAME: yealink_t34W_wallpaper VALUE: https://a.website.with/picture.png
NAME: yealink_t34W_wallpaper_filename VALUE: picture.png

Nothing changes.

I can affect all of the keys, programmable buttons etc, but nothing that sits in the Settings section of the profile (I thought that might fix number one above)

If I log into the web GUI (using the password given to me by my provider), I can upload the image and change it at will.

If I upload the image to the phone and just use the second settings line from above, nothing happens.

I think the tenants in a multi-tenant setup are restricted, but in a way that is too restrictive for the user.

Is this other peoples experiences of this or should the provisioning process be able to affect all elements of the phone that I can from the web GUI?

Thank you
 
OK, sort of came across the answer by accident and remembering a comment from a solution to something else...

Hyphens mean something in the config files.

I was using an image filename containing hyphens "this-image-file.png" for instance

With the hyphens, the image file was being uploaded to the phone, but the filename wasn't being selected.

Without the hyphens, the filename was being selected....

Interstingly, with the hyphens removed, point 1 above also worked. It's as if the hyphens were breaking more than just the one thing...

On a side note; is there a list of all parameters that can be entered into a FusionPBX providing script? I have taken to finding the templates in GitHub and hunting for the parameters I need, thus finding the required variable names.

Thank you