Free Yealink Endpoint Manager

Hey all, I’ve been using FPBX since way back in the Trixbox days. I’m an end user for my small office and used to use the OSS EPM. That project is unfortunately dead and stopped me from upgrading to FPBX17. I’ve setup my cousins larger office and since he has lots of changes, I had him buy the commercial EPM. It cost a lot and I don’t love it for my needs.

Since I use exclusively Yealink phones I created (with the help of Gemini) a EPM module just for Yealink phones. Since I only have old legacy (t28) phones and he only had T46’s I could only test my module on those.

Thought I’d contribute back to the community since I’ve gotten so much from you all. If you want to try it out, GitHub - hgolbar/FPBX_Yealink_EMP: Freepbx Endpoint Manager for Yealink Phones · GitHub.

Feel free to let me know if you find any bugs or have suggestions to make it function better.

I have multiple clients that are Yealink only users. They primarily use the Yealink T5 series, which is what Frontier (Verizon) and other ISP service providers provision with. Clients “growing up” from their ISP provisioned systems to FreePBX are easier to sell when the hardware is familiar to them. Also, the Yealink AX86R WiFi IP Phones are popular with the clinical staff at the medical practices we service (the bulk of our clients). The Yealinks are so popular that I keep several cartons of them in inventory. At the Yealink price point and broad range of offerings, if there was a reliable EPM just for Yealinks, I can likely move several clients off of older Digium and Sangoma phones, and on others with Yealink’s already, discontinue the Sangoma ETM and its cost and associated issues. I’ll be testing your Yealink EPM. This sounds promising!

There’s a small bug that I found. I’ll upload 1.0.0.7 tonight. I haven’t tried it with anything that new but lmk if there’s anything that needs fixes.

I’ve observed a slow move to Grandstreams over Yealink. That migration has mostly been driven by pricing

I’ve actually observed the opposite. For many years going back at least to 2002 Grandstream was the “Budget” phone of choice for many small offices. I still like them for their ease of configuration and extensive catalog of devices. But they never caught on with the major telecom and ISPs as the migration from POTS to SIP accelerated. These days its Yealinks that many of the big guys are rolling out, and the price difference between Yealink and Grandstream devices is not large. Yealink also at least from my experience has better margins for resellers. Its tough to try to convince a new client migrating from Verizon (Frontier) or Ring Central to switch phone models, and currently the Yealink T54W is the most ubiquitous model we see. At my office we use Grandstreams though - have for close to two decades.

Hi ,
you can try my fork of OSS EPM and give me a keep back
https://github.com/jcattan/autoprov/tree/17

FYI, that URL gives a 404

Sorry, my repository was private… I’ve changed it to public.
You can try again.

I don’t know if it was yours or someone else that I saw a link for in the forums for the 17 branch, but I had a ton of php errors trying to do anything. I got it installed and partially working on Incredible pbx but not good enough for me to make the switch. I just tried yours and it won’t install. Debian12/FreePBX 17 (via script)

Sorry, I hadn’t pushed the latest changes.
It’s fixed now!!
The error is : $sql = "UPDATE `sysadmin_options` SET `value` = 'none' where `key` = 'provisauth';"
instead of : $sql = "UPDATE `sysadmin_options` SET `value` = 'none' where `key` = 'provisauth'“;

Yeah, had I know about this I might have used it instead of creating mine. There are still some of the inherited bugs from the original if you don’t do everything exactly right, but it’s usable. There’s a lot of features in there that I just don’t use so mine is more simplified and ultimately works better for me. Nice work though! I initially tried to make that one work and it was a nightmare.

It’s true that the update from 15 to 16 (PHP 5 to 7) was easy, but going from 16 to 17 (PHP 7 to 8) is a nightmare!!!
Feel free to suggest any changes or corrections :wink: