I’m setting up hotdesking with Yealink Phones. In endpoint manager, for Yealink T54W, the BLF type XML-API is missing. It is there for the T54S.
Endpoint Manager 184.108.40.206
Phones Apps 15.0.23
I also found out that the default profile is not generated for T54W. When configuring hotdesking, the default profile is used to provision phones with a Login Button. A bunch of files are generated in the TFTP folder (y000000000000.cfg, y000000000002.cfg, etc). When looking at the apache logs, when I try to auto-provision a T54W that is not in the list of configured phones in Endpoint Manager, I see that the phone tries to download a file named y000000000096.cfg. This file is not created automatically by Endpoint Manager, so the T54W does not get the “Login” button. If I copy the file from another yxxxxxxxxxx.cfg files and rename it y000000000096.cfg, the default provisioning works and the login button is added. After loging in, the phone configure itselfs correctly with the default profile, but since I do not have the XML-API blf available for T54W in Endpoint Manager, the Login BLF cannot be added to the template, so there is no way to logout the phone.
Ok… Any plans on adding the newer models ? I mean, pretty much all Yealink phones work the same way, so getting Endpoint manager to generate the y000000000096.cfg file and allowing the creation of XML-API blf is probably not very hard.
We have a customer who’s waiting to buy a 500USD commercial module from Sangoma, and if it works, we’re probably have a few more.
Our customer who has around 50 Yealink T54w phones wants to be able to do some hotdesking from any phone, so replacing only a few of them with Sangoma phones is not a good option. We would have to replace them all.
Has anyone been able to work around the Phone Apps limitation on T54W phones ? I’ve tried to manually program the logout BLF with basefile edit but the value of the BLF is dynamic, with a token and an extension number, so it doesn’t work.
We might sell Sangoma phones to our future customers to work around this, but not being able to use Phone Apps on the latest generation of Yealink phones is a real bummer.
Not sure that will work. In the past the apps look to EPM to get information on the device based on Mac to lookup permissions in User Manager and also verify the model is a supported model for apps. It has a bunch of belt and suspenders built into it.
Because the URL also requires the token for the user not just the extension number.
Secondly because on logout the app needs EPM to write out a new config and it does that from the template but since that is not a model that supports it the config won’t have the needed info to login again. Again my knowledge is a couple years dated on this but that is how it always worked before.
Also the apps do a user agent check to make sure the model and brand is supported so it knows what to return for the app screens since models and brands are different.
Thanks for that, you made me remember the rest of the details from 2019.
I wrote my own script to use fwconsole epm commands for this at a site because their login/logout was more complex than the default EPM process. The current login/logout method was designed with on CHAN_SIP in mind.
That site uses EPM for the -1 as per normal, but then uses the custom script to login / logout a device on the -2 profile. They use old Aastra phones, but I tinkered with a Yealink in case they wanted to start replacing phones.
Edit: found a code snippet. I do not have access to the client server atm and am not sure if this is what I ended up with or not.
Well the token was used for auth when phone apps were originally built otherwise anyone could use the apps by just passing any ext in the url and have no real auth. That is scary that if someone opens up port 84 for a remote phone they have full access to any app just by guessing a valid exit on the system.