NEW OSS EPM for FreePBX 16 & iPBX 2027

[billsimon]

I spent some time over the past week making OSS Endpointman work with FreePBX 16. But it's an anachronism, because the phone models from the original provisioner.net archives are obsolete now.

I'm curious whether anyone has kept up with making current phone model packages.

 

[wardmundy]

If we start adding OSS EPM back into Incredible PBX 2027 builds, perhaps it will light a fire in a few companies to work on this. This is mostly a corporate tool anyway.

 

[krzykat]

I spent some time over the past week making OSS Endpointman work with FreePBX 16. But it's an anachronism, because the phone models from the original provisioner.net archives are obsolete now.

I'm curious whether anyone has kept up with making current phone model packages.

I've got a Grandstream HD Color set which includes GXP21xx phones. I know someone that's been working on this with Kazoo (which was built off of our OSS EPM) and I think he might be willing to handle some of those upgrades. I had him add ClearlyIP phones to Kazoo's platform.

 

[Sayso]

I have done some work updating polycom and will write up what I know in the next month or two. Adding new phones should be pretty easy.

 

[billsimon]

Provisioning is so weirdly diverse. http, t*f*t*p, https, DPMA; XML, INI, proprietary formats; relying on various HTTP headers; the list goes on and on.

Doing EPM for multiple vendors is crazy. That Andrew did all of this in the past amazes me. It also annoys me greatly because my next thought is "it shouldn't have to be this way."

TR-069 is implemented by some phones but it's hardly a well-accepted standard for VoIP endpoints.

I think the way forward for IncrediblePBX or any project that wants to add provisioning is to standardize on one or two endpoint vendors and just get those perfect. And stick to your guns on it, because there's always someone coming along "Hey why isn't my Cisco Selsius 7910 supported?" that needs to be told it ain't going to happen.

 

[krzykat]

Provisioning is so weirdly diverse. http, t*f*t*p, https, DPMA; XML, INI, proprietary formats; relying on various HTTP headers; the list goes on and on.

Doing EPM for multiple vendors is crazy. That Andrew did all of this in the past amazes me. It also annoys me greatly because my next thought is "it shouldn't have to be this way."

TR-069 is implemented by some phones but it's hardly a well-accepted standard for VoIP endpoints.

I think the way forward for IncrediblePBX or any project that wants to add provisioning is to standardize on one or two endpoint vendors and just get those perfect. And stick to your guns on it, because there's always someone coming along "Hey why isn't my Cisco Selsius 7910 supported?" that needs to be told it ain't going to happen.

That or why not get your 1 or 2 good ones done complete, and then if a vendor wants to be added to the list, have them work with to get implemented, and perhaps they need to pay for the development to be added. Certainly it would benefit them.

 

[Samot]

Provisioning is so weirdly diverse. http, t*f*t*p, https, DPMA; XML, INI, proprietary formats; relying on various HTTP headers; the list goes on and on.

Can you elaborate on this a bit? I run a provisioning server that has Poly, Grandstream, Yealink, Yeastar and at one point snom's. What various HTTP headers are you referring to? Overall HTTP/HTTPS provisioning is the same outside of one doesn't use TLS but everything else is the same. t*f*t*p is just obsolete and insecure, shouldn't really be running it if you have other viable options.

then if a vendor wants to be added to the list, have them work with to get implemented, and perhaps they need to pay for the development to be added.

Well now you're entering the realm of commercial activity. Who will the phone vendors be paying? An individual person, a business/corporate entity? Where will the test phones, etc be sent?

Certainly it would benefit them.

How? What benefit does IncrediblePBX give Yealink or Poly/HP or Grandstream? That's going to be a real question that would need to be answered if any of those vendors are going to throw money at this. There were 8,222 downloads in 2022 from sourceforge, accounting for 423 downloads of "greatest hits" that left 7,799 downloads of everything else. Based on those numbers, 148 weekly download average of all the versions of all the OSes. Really that 7,799 would get scrutinized even more as things like a single user download all the OS versions of a release to test each of them. This would also apply to the user installing the same version/OS on multiple cloud services...to test.

Just to clarify something, I thought all the Clearly modules like ClearlyDevices was free for IncrediblePBX users. Why would OSS EPM be needed at this point? Or is it more that it's free to use as long as you're using ClearlyIP phones (or white labeled phones)?

 

[krzykat]

I spent some time over the past week making OSS Endpointman work with FreePBX 16. But it's an anachronism, because the phone models from the original provisioner.net archives are obsolete now.

I'm curious whether anyone has kept up with making current phone model packages.

Hey @billsimon do you have your OSS EPM mods online somewhere? I want to play with what you've got and see if I can't add to it.

 

[wardmundy]

Just to clarify something, I thought all the Clearly modules like ClearlyDevices was free for IncrediblePBX users. Why would OSS EPM be needed at this point? Or is it more that it's free to use as long as you're using ClearlyIP phones (or white labeled phones)?

Not sure what you're talking about. Just because ClearlyIP supports our project with free repositories does not mean we require the use of ClearlyIP phones. How do you come up with this ??

 

[Samot]

Not sure what you're talking about. Just because ClearlyIP supports our project with free repositories does not mean we require the use of ClearlyIP phones. How do you come up with this ??

From you, NEW - Sangoma Beefs Up FreePBX Security... For a Price | The VoIP-info Forum where you made it clear they were free to use with Incredible PBX. So are you saying it's not the case now?

 

[wardmundy]

@Samot: The discussion was about deploying a new OSS Endpoint Manager and then getting SIP phone providers to add config files for their phones. This has nothing to do with ClearlyIP unless they wish to add their phone configurations to OSS EPM. Users can choose ClearlyIP phones or any other brand without any restrictions. To restate the obvious, Incredible PBX does not require and never has required use of any specific brand of phone or SIP provider.

 

[Samot]

@Samot: The discussion was about deploying a new OSS Endpoint Manager and then getting SIP phone providers to add config files for their phones. This has nothing to do with ClearlyIP unless they wish to add their phone configurations to OSS EPM. Users can choose ClearlyIP phones or any other brand without any restrictions. To restate the obvious, Incredible PBX does not require and never has required use of any specific brand of phone or SIP provider.

I never said it required to use any specific brand of phone or SIP providers. Doesn't matter, I figured out the answer to my question.

 

[krzykat]

@Samot, I don't understand some of what you're getting at here. Do you think Incredible should only be created with OSS? I mean if someone has a commercial module and Ward gets them to agree to a freebie of it in Incredible, wouldn't you want that? Why does everything have to be an argument? You have some good input at times, but damned you just seem like a negative person always half empty instead of half full.

 

[Samot]

@Samot, I don't understand some of what you're getting at here. Do you think Incredible should only be created with OSS? I mean if someone has a commercial module and Ward gets them to agree to a freebie of it in Incredible, wouldn't you want that? Why does everything have to be an argument? You have some good input at times, but damned you just seem like a negative person always half empty instead of half full.

I was asking for specific information for clarification. I got that on my own after I asked the question. I've got no problem with Incredible PBX being OSS and/or having commercial modules. Why would I have a problem with that? It's basically the FreePBX setup.

As for the arguing, matter of perspective I guess. I mean let's take your idea/suggestion that vendors should pay to be in the OSS EPM and how it benefits them. From one perspective all the questions I asked could look like I was just shredding your idea to the ground. From another perspective I was actually trying to address all the things that would need to be addressed if the idea was to move forward. Because vendors are going to want to know how giving money to said project actually benefits them.

But here's a personal tidbit about me. When I come up with an idea, I apply the Devil's Advocate step to it. That is, I bounce it of someone(s) who's entire position is to find the holes. In those odd cases where I might not have someone to bounce it off of, I will start fleshing out the idea to try and find the holes. I still employ the use of notebooks with pen/pencil to jot this crap down and makes the pro/con lists, etc. cuz honestly, I'm more harsh to my own stuff than anything on this forum.

 

[krzykat]

Thanks appreciate your input, guess sometimes its in the way its presented.

Now back to normal programming.

Does anyone have OSS EPM working on Incredible 2027 with php 7.4 ?? I'm having heartburn with it.

 

[Samot]

you just seem like a negative person always half empty instead of half full.

All I have to say to this is:

 

[krzykat]

FYI - the OSS EPM that is being loaded in Incredible2027 doesn't like php 7.x ... Try to load Jerrm's and you might find better success.

 

[krzykat]

All I have to say to this is:

View attachment 4649

I KNEW IT ... this all makes sense now. Someone pissed in your coolaid. LOL

 

[billsimon]

Does anyone have OSS EPM working on Incredible 2027 with php 7.4 ?? I'm having heartburn with it.

Yeah I will put up a PR probably later today that you can grab.

It's the jerrm modifications for php 7.3 plus some more to get to 7.4.

 

[krzykat]

Yeah I will put up a PR probably later today that you can grab.

It's the jerrm modifications for php 7.3 plus some more to get to 7.4.

Excellent, let me know and I'll include your mods. I also plan to add the latest Grandstream GXP HDC phones and the Yealink V.80 as default. Then we need to accomodate for PJSIP automatically instead of manually like I do now.