NEW OSS EPM for FreePBX 16 & iPBX 2027

[kenn10]

So I seem to be having an issue that no one has experienced and this goes back to my last install (incredible pbx 2021). After scouring the forums I'm coming up empty handed. This is a fresh install of Incredible PBX 2027 on Debian 11 and I'm just stuck here no matter which set of instructions I follow. Any/all suggestions are appreciated.

View attachment 5356

Try clicking on this:

 

[K0JSC]

Try clicking on this:
View attachment 5358

LOL Ummm...now that was embarrassing don't mind me! Thank you!

 

[roussel2nis]

Try this for better results....

1. Open OSS EndPoint Manager under FreePBX Settings
2. On right pull-down, choose EndPoint Manager Settings
3. For Package Server, enter: https://ossepm.incrediblepbx.com/
4. Adjust other fields as desired. Then click in another field to save your entries
5. On right pull-down, choose Template Manager
6. Click link to download the latest templates
7. On right pull-down, choose Package Manager
8. Click Check for Updates
9. Click Install buttons for desired packages

View attachment 5272

@wardmundy does your repository open to contributions? In order to add some phones I have(Fanvil). Thanks

 

[wardmundy]

@wardmundy does your repository open to contributions? In order to add some phones I have(Fanvil). Thanks

Yes. Contact @billsimon.

 

[retrofreak]

Hi all,
I just set up a new FreePBX 16 machine using the FreePBX distro.
I have installed the OSS EndPoint Manager as referred to in #123.
PHP version is 7.4.16.
I ran into the same issue as @terazavi in #70: E_DEPRECATED errors when trying to access the extension mapping view.
I changed all lines the UTF conversion file, but run into another issue.
However, I'm confused, since, at least according to phpinfo when run on behalf of the web server, is telling me that E_DEPRECATED is *not* part of error_reporting - which exactly is what /etc/php.ini looks like.



I have two questions:
1. Any ideas how to bypass this errors in general? It looks like E_DEPRECATED errors still seem to be created. Maybe this is also something which would need to be configured in Whoops?
2. I'm interested in trying the EPM out with a Snom D385, which is basically a successor of the 370. I'd give it a try and just apply the 370 template to it. If this does not work out, is there any documentation avaiable on how the provisioning mechanism works?

 

[ropeguru]

Hi folks, hopefully posting in the right place here.. I have spent a couple of days digging into the EPM and trying to squash some errors. One was with the reboot function in the phone.php file complaining about an array inside the preg_match.. I am not a programmer by any means so I took a shot at using some AI help and it rewrote the code and everything in the phone.php seems to be working now. Would like to contribute what I have done and want someone to review. Just need to know the process.

Also, I have two Grandstream GXP2140's and that model was skipped over in the package manager. It is just a 4 line version of the 2130 and 2160. I have upgraded the firmware on my phones to 1.0.11.85 and completely migrated the old template file to the latest. Also will to contribute that. Again, just need to know the process.

One thing I would like to dive into how to add more configurable options based on each phone type. Like for the Grandstream, add more config options for the various soft keys. I there any documentation on this somewhere?

I was playing with a Cisco 7950G but Cisco just plain sucks. So gave up on that one. Kept not liking something with the format but never logs what it doesn't like.

Edit: Oh, and there was one other file, cannot remember which one, that complained I think of phone.php missing (might have been another file). It was looking for it in temp/endpoints/ in the php file and it didn't exist. Removing the temp allowed the code to run without issue. Again, I just made it work, not sure whether it is right or not.

Edit 2: Running 2027-D 16.0.40.4 on a Raspberry Pi 4 8GB

 

[kenn10]

Hi folks, hopefully posting in the right place here.. I have spent a couple of days digging into the EPM and trying to squash some errors. One was with the reboot function in the phone.php file complaining about an array inside the preg_match.. I am not a programmer by any means so I took a shot at using some AI help and it rewrote the code and everything in the phone.php seems to be working now. Would like to contribute what I have done and want someone to review. Just need to know the process.

Also, I have two Grandstream GXP2140's and that model was skipped over in the package manager. It is just a 4 line version of the 2130 and 2160. I have upgraded the firmware on my phones to 1.0.11.85 and completely migrated the old template file to the latest. Also will to contribute that. Again, just need to know the process.

One thing I would like to dive into how to add more configurable options based on each phone type. Like for the Grandstream, add more config options for the various soft keys. I there any documentation on this somewhere?

I was playing with a Cisco 7950G but Cisco just plain sucks. So gave up on that one. Kept not liking something with the format but never logs what it doesn't like.

Edit: Oh, and there was one other file, cannot remember which one, that complained I think of phone.php missing (might have been another file). It was looking for it in temp/endpoints/ in the php file and it didn't exist. Removing the temp allowed the code to run without issue. Again, I just made it work, not sure whether it is right or not.

Edit 2: Running 2027-D 16.0.40.4 on a Raspberry Pi 4 8GB

First of all, thank you very much for working this and giving it back to the community. I don't know who actually maintains it anymore and it definitely did not work with FreePBX-17. It hasn't updated for awhile and newer phone models have not been getting added. It is not an IncrediblePBX module per se. If I'm not mistaken, someone over at the FreePBX forum has been keeping an eye on it but I don't recall whom. It may be jfinstrom who is working for ClearlyIP or @billsimon on this forum. I'm sure @wardmundy can comment when he gets back from cooling his heels in the mountains.

Also, if you are dealing with mostly Grandstream phones, check out the Grandstream free provisioning tool called GDMS. I use it exclusively for my Grandsream stuff without any need to deal with a FreePBX module. See https://www.gdms.cloud/login and create a free account and check it out.

 

[ropeguru]

First of all, thank you very much for working this and giving it back to the community. I don't know who actually maintains it anymore and it definitely did not work with FreePBX-17. It hasn't updated for awhile and newer phone models have not been getting added. It is not an IncrediblePBX module per se. If I'm not mistaken, someone over at the FreePBX forum has been keeping an eye on it but I don't recall whom. It may be jfinstrom who is working for ClearlyIP or @billsimon on this forum. I'm sure @wardmundy can comment when he gets back from cooling his heels in the mountains.

Also, if you are dealing with mostly Grandstream phones, check out the Grandstream free provisioning tool called GDMS. I use it exclusively for my Grandsream stuff without any need to deal with a FreePBX module. See https://www.gdms.cloud/login and create a free account and check it out.

Thanks for the tip on GDMS. I saw that while I was searching for other things when working on the EPM but figured there was a cost to it. I got into fixing this as I was setting up IncrediblePBX for a non profit I am part of and they need sone phones in their office. I just happened to have two of the GXP2140's and a PI I am donating to the cause. So really, I could end up using this for almost any phone model.

And just realizing there is a phone.php for each of the model groups, this is the one I updated:

/var/www/html/admin/modules/_ep_phone_modules/endpoint/grandstream/gxphd/phone.php

 

[kenn10]

The main advantage to GDMS is that you can access it from anywhere and reprovision the phones and ATA's remotely (so long as they are accessible from the internet.) My systems are cloud based so all phones are on the internet. GDMS gives you the latest firmware, complete status of devices, instant changes to keys and settings, etc. It pretty nifty for a free service.

The whole change of FreePBX moving from PHP 7.x to 8.2 for FreePBX-17 has really messed with modules that have not been updated. Hopefully, someone will be able to incorporate your work into the OSS EPM.

 

[crashpb]

is there a documentation for how to create package files for oss epm ?
I've been trying to create a package template for cisco 7841 phones but I'm somehow stock on the line keys section,
some parameters need 3 variables, some need 4, some need 2, so an If statement would really come in handy.