I’d like to see the OSS Endpoint manager fixed for FreePBX-17. I’m sure its more PHP craziness that generates errors. Bill Simon previously worked on it for FreePBX-16 but I don’t think anyone has maintained it for awhile.
2 Likes
The beauty of open source is that you can also try and get it updated for v17! If Bill already got it working on v16 then it should already be very close.
2 Likes
I’m an applications utilization guy and not much of a programmer. When it comes to modules for FreePBX, I’m definitely not up to snuff on modifications.
Got a URL for that on GiHub?
So a community member, the one who updated it for 15 has started but seems to have stalled. It is a very broad scope of work as php 8.X is not as friendly or “loose” as older php versions. His repo and progress are at:
Note he may be encouraged to $peed up his effort$ if the price i$ right or with a decent bounty i$ enough if you understand my meaning. Obviously that would be a discussion for him.
Someone also opened a PHP 7.3 PR on the repo which may be a good starting point.
1 Like
@kenn10 I confess to getting OSS EPM working for FreePBX 16 but in every way, it was a hack job born out of curiosity. It was a very good module at one time and may still have life in it, but I suggest that a redesign and rewrite could be better. Not that I am volunteering to do it, at least not today.
What would I do differently? Dynamic configs generated by PHP (that is, a FreePBX module) rather than static files written to /tftpboot, for one. That means getting rid of tftp provisioning–sorry we can no longer provision ancient devices using a plain and insecure protocol.
We are in the future now with AI, maybe some way of feeding a hand-built config into an LLM and having it return a template for provisioning that type of phone.
2 Likes
Good to see you here. I just read your post on the “other softswitch” with security issues and devs insisting on pay-to-secure
1 Like