FYI Endpoint Manager for IncrediblePBX 2020

[Eliad]

I have Yealink SIP-T41S phones, firmware 84, I guess this OSS EPM wont work since it does not have any packages for it.

 

[krzykat]

I've not used the T41 with it, but there is a package for the Yealink V70 which includes the T41P and T46G. I've successfully used that for the T46G, and since the variables are about identical, I've used the T46 for the T29 as well. I've seen where someone has also create a new package for V80 Yealink, so if I were you, I'd give that a look (just pulled down the package and Yes - it has T41S in it).

 

[krzykat]

I have Yealink SIP-T41S phones, firmware 84, I guess this OSS EPM wont work since it does not have any packages for it.

This should make you happy:

 

[Tonyclewis]

Well I think we will have some great news for non Clearly IP phones for provisioning in the very very near future.

 

[krzykat]

Well I think we will have some great news for non Clearly IP phones for provisioning in the very very near future.

Wow - that's great. Except for clients that already have Yea or GS that insist on consistency while upgrading, I'm pushing people towards the CIP 270, as it really has the best feature sets. This would make my life easier though.

 

[Tonyclewis]

it will be basic provisioning and button setup only. It’s all cloud based and not on the PBX direct.

 

[Eliad]

Well I think we will have some great news for non Clearly IP phones for provisioning in the very very near future.

That will be awesome. Please include Yealink phones too.

 

[Eliad]

This should make you happy:

View attachment 2807

do you have better instructions on how to install it?
for me it fails at tar command with
tar zcvf yealinkv80.tgz yealinkv80
tar: yealinkv80: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

 

[krzykat]

do you have better instructions on how to install it?
for me it fails at tar command with
tar zcvf yealinkv80.tgz yealinkv80
tar: yealinkv80: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

Then under Brands -> Package Manager, you'll find tab for Yealink V80

 

[Eliad]

View attachment 2808

View attachment 2809

Then under Brands -> Package Manager, you'll find tab for Yealink V80

Thank you.
i finally got it installed. I had to first uninstall the already installed Yealink package. Then it did install without the tar command which I thought was required prior to the install.

 

[wardmundy]

We've now added the Yealink V80 components to the OSS Endpoint Manager Configurator. Just rerun the original setup procedure. NOTE: Existing settings will be overwritten.

 

[wardmundy]

OSS End Point Manager Returns for Incredible PBX 2020

Photo Credit: Tony Lewis, ClearlyIP CEO

 

[jerrm]

@krzykat and anyone else actively using OSS EPM who may have a test system spun up - I would appreciate it if you could try https://github.com/jerrm/endpointman/archive/release/14.0.zip and report what behaves differently than OSS EPM 14.0.2.1.

Code fixes are the easy part, but I haven't had any meaningful time to test.

The goal of the updates is just to get things running and functionally equivalent under php-7.3/mysql-10.3.22 for debian folks like myself, but also maintain compatibility with IPBX's(and Sangoma Distro's) php-5.6/mysql-5.5.64.

The only existing "bug" addressed is the setup.php issue mentioned by @krzykat above (it just got too annoying to leave alone). Hopefully there would be no other functional changes over 14.0.2.1 (but fully expect there are still issues to address).

*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***
*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***
*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***

This makes minor mods to the EPM tables if upgrading an existing OSS EPM install. Current mysql versions require explicitly setting some default values that were previously implict... But that is part of what needs testing - does a null mysql blob/text column (new explicit default) behave differently than an empty blob/text (old implicit default).

If anyone cares to take the time to test under Debian, I can spin up an instance and provide access.

 

[krzykat]

@krzykat and anyone else actively using OSS EPM who may have a test system spun up - I would appreciate it if you could try https://github.com/jerrm/endpointman/archive/release/14.0.zip and report what behaves differently than OSS EPM 14.0.2.1.

Code fixes are the easy part, but I haven't had any meaningful time to test.

The goal of the updates is just to get things running and functionally equivalent under php-7.3/mysql-10.3.22 for debian folks like myself, but also maintain compatibility with IPBX's(and Sangoma Distro's) php-5.6/mysql-5.5.64.

The only existing "bug" addressed is the setup.php issue mentioned by @krzykat above (it just got too annoying to leave alone). Hopefully there would be no other functional changes over 14.0.2.1 (but fully expect there are still issues to address).

*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***
*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***
*** BE SURE TO HAVE A BACKUP OR SNAPHOT ***

This makes minor mods to the EPM tables if upgrading an existing OSS EPM install. Current mysql versions require explicitly setting some default values that were previously implict... But that is part of what needs testing - does a null mysql blob/text column (new explicit default) behave differently than an empty blob/text (old implicit default).

If anyone cares to take the time to test under Debian, I can spin up an instance and provide access.

I'll do as requested, but will have to be this evening, I'm working on converting a client from the old incredible 13-12 to Incredible 2020 right now.

 

[jerrm]

I'll do as requested, but will have to be this evening, I'm working on converting a client from the old incredible 13-12 to Incredible 2020 right now.

No worries. Any help appreciated, whenever convenient.

 

[smccloud]

I am trying to configure three Polycom VVX 500s using this. I have them set up to use t*f*t*p and the IP is set to the IncrediblePBX IP. They cannot contact the provisioning server though, is it just not working with Polycom phones at the current time?


Figured it out, installing a t*f*t*p server in CentOS 7 configures it to look at /var/lib/tftpboot instead of /tftpboot for the config files. Once I made that change all is good.

 

[kenn10]

I am trying to configure three Polycom VVX 500s using this. I have them set up to use t*f*t*p and the IP is set to the IncrediblePBX IP. They cannot contact the provisioning server though, is it just not working with Polycom phones at the current time?


Figured it out, installing a t*f*t*p server in CentOS 7 configures it to look at /var/lib/tftpboot instead of /tftpboot for the config files. Once I made that change all is good.

Is port 69 for t*f*t*p open thru your firewall?

 

[mainenotarynet]

In this post in this thread #15, the pic shows a GXP2140 in the list. Where did you get that, I get the 2130 and 2160 only I HAVE 2140s and would like to use OSS EPM. Where can I find the GXP2140 template ?? Thanks

 

[ropeguru]

In this post in this thread #15, the pic shows a GXP2140 in the list. Where did you get that, I get the 2130 and 2160 only I HAVE 2140s and would like to use OSS EPM. Where can I find the GXP2140 template ?? Thanks

I would like to know about that too. I have two of them I would like to get provisioning working on .

I see you have had no response.

 

[krzykat]

Well I think we will have some great news for non Clearly IP phones for provisioning in the very very near future.

Hey Tony, is now considered "very very near future" ??