By chance I discovered that TP-link UB400 works the same as Yealink's own adapter. The phone thinks it's a Yealink adapter - the same chipset I think. Difference is that it's only $10 each and TP-link is easy to find.
I don't see a firmware for the T54W nor is the EXP50 available.
These phones are basically new since October or so. They will not be in EPM anytime soon because of how that has traditionally worked. The device manufacturer has to sing an agreement with Sangoma (Schmoozecom) to get a device supported. I assume, but do not know for a fact, that the agrement includes monetary compensation also, as anything in EPM is fully tested by Sangoma also, and testing takes manpower (money).
The IT benefit to this entire thing is, by enabling this feature, IT will now have a backup of the configuration of all the phones. Even if a user changes a button. Now a phone can die and IT will simply change the MAC on the provisioning server and put the new phone on the desk.
To the business, the benefit is to let users control their own buttons without IT getting involved. Buttons can easily be programmed by a user simply holding it down until the menu pops up. It takes very little instruction to teach users to pick Speed Dial or BLF and enter the number or extension.
For most small shops, this doesn't matter in the first place. They rarely change anything.
But for an organization over 20, it is very common to have users all needing different configurations on their phone buttons. Their Boss, their Queue Pause, their specific parking lots, etc.
Do you generally use the Endpoint Manager or any of the other commercial modules?
There is no commercial module that we use regularly. But we've got some clients that use many.
There are pretty much zero reasons not to add SysAdmin Pro for $25. Getting the email config in the GUI and the ability to tell the web server to use authentication for the config files saves more time than the cost to do it yourself manually.
It sounds like @lansalot might have been pushing an old config file to Yealink phones with newer firmware, and that old style config MIGHT have been slightly incompatible - and caused the issue. which @lansalot was able to resolve, not by completely modernizing his config files, but instead by adding a few lines to expressly bring OPUS back into the config.
That should not matter. If the config is old and does not have the setting specified at all, it should go to the default value.
Sure, of course you'd like to think so - but bugs do happen... and it appears that it is in this case.
I bet you were waiting for this question which is, can a second instance be run so we have two directories listed, one for the internal phonebook and a second for example external suppliers (Using the external phonebook in contact manager?
Thanks so much
If you update to the current version, it accepts a parameter for the group name. So you can different directories on different buttons or say, per site.