PIONEERS IncrediblePBX 2022B on Ubuntu 22.04

[kenn10]

Its a work in progress but since Oracle has moved to Ubuntu 22.04 as the standard, I've been working to get IncrediblePBX going on the current Ubuntu release.

 

[qtlnx]

Any plans to get going on current RHEL/OL/CentOS release? I did manage to get IncrediblePBX up on 20.04 but it required severe learning efforts to get SSL and other things working.

 

[kenn10]

Any plans to get going on current RHEL/OL/CentOS release? I did manage to get IncrediblePBX up on 20.04 but it required severe learning efforts to get SSL and other things working.

CentOS became CentOS Stream and we have abandoned it. Rocky 8 is a fork but is far less stable than Debian or even Ubuntu. I don't foresee anyone fighting any longer with CentOS for IncrediblePBX.

Of course, the ultimate answer would have to come from our fearless benefactor @wardmundy.

 

[qtlnx]

CentOS became CentOS Stream and we have abandoned it. Rocky 8 is a fork but is far less stable than Debian or even Ubuntu. I don't foresee anyone fighting any longer with CentOS for IncrediblePBX.

Of course, the ultimate answer would have to come from our fearless benefactor @wardmundy.

Oracle Linux is still free and as stable as required for mission critical production. No idea what Rocky is but Alma Linux is free as well and is used in much more mission critical applications then any PBX can think of. All provide full compatibility with original RHEL.

 

[kenn10]

Oracle Linux is still free and as stable as required for mission critical production. No idea what Rocky is but Alma Linux is free as well and is used in much more mission critical applications then any PBX can think of. All provide full compatibility with original RHEL.

Absolutely feel free to develop working versions of IncrediblePBX on any of your preferred distros so you can contribute back to our community.

 

[qtlnx]

CentOS7 version still exist, I believe. Again, since spinoffs like Oracle Linux and Alma Linux are 100% compatible and still under full maintenance for quite some time, there is no need to develop something new. Just don't abandon support for existing IncrediblePBX variant.

 

[krzykat]

I agree with @kenn10 I don't think any future development will occur on Centos

 

[wardmundy]

A Rocky 8 release of Incredible PBX is already available. Not sure where we go from there.

 

[wardmundy]

The major problem with Rocky 8, Debian 11, and Ubuntu 22.04 is they all broke free faxing. If that matters to you, stick with the Debian 10 release of Incredible PBX which is available as an install script as well as a VirtualBox image, VMware image, Proxmox image, and CrownCloud image. See the Wiki for links.

FYI to @qtlnx: An install script for Ubuntu 20.04 (with faxing) is also available here.

 

[krzykat]

The major problem with Rocky 8, Debian 11, and Ubuntu 22.04 is they all broke free faxing. If that matters to you, stick with the Debian 10 release of Incredible PBX which is available as an install script as well as a VirtualBox image, VMware image, Proxmox image, and CrownCloud image. See the Wiki for links.

FYI to @qtlnx: An install script for Ubuntu 20.04 (with faxing) is also available here.

That's why I have a server dedicated to faxing. Everyone can get new servers, but if they have a fax line - it goes through the fax server (that is older and don't think will be upgraded for a while).

 

[wardmundy]

That's why I have a server dedicated to faxing. Everyone can get new servers, but if they have a fax line - it goes through the fax server (that is older and don't think will be upgraded for a while).

Or you can buy a dedicated FAX DID from VoIP.ms for $1.99 a month and 3 cents a minute.

 

[qtlnx]

A Rocky 8 release of Incredible PBX is already available. Not sure where we go from there.

View attachment 4417

I just found it myself, thank you. Will try at earliest opportunity. Is transfer via a script from Incredible PBX 13.0.197.21 supported or better configure only one handful of extensions manually?

 

[kenn10]

1. Update the FreePBX 13 server modules to current using the Admin > Module Admin. Check for updates and apply all of them.
2. Run a FreePBX backup under Admin > Backup and Restore
3. Download the completed FreePBX backup file to your local desktop
4. Once the new system is set up, on that system go to Admin > Module Admin
5. Check for updates and install all new module updates
6. Go to Admin > Backup and restore
7. Upload the FreePBX 13 backup into the restore tab.
8. Run the restore and select the option with legacy CDR to restore the old call records (may or may not work)
9. This should restore most or all the stuff from the old system.

 

[kenn10]

@wardmundy another challenge with Ubuntu 22.04 is that it will no longer use key pairs from Putty. They have moved to a higher level of keying and basic rsa is not working any longer. This isn't a show stopper on a locked down system but I've always used a key with Putty to prevent any incidental login attempts.

 

[qtlnx]

@wardmundy another challenge with Ubuntu 22.04 is that it will no longer use key pairs from Putty. They have moved to a higher level of keying and basic rsa is not working any longer. This isn't a show stopper on a locked down system but I've always used a key with Putty to prevent any incidental login attempts.

You can always modify ssh config, local and global, and add rsa back. Fedora 36 did the same and I had to create my own .ssh/config to continue connecting to legacy systems.

 

[kenn10]

You can always modify ssh config, local and global, and add rsa back.

This thread explains how to do that:

SSH without password does not work after upgrading from 18.04 to 22.04

SSH without password does not work after upgrading from Ubuntu 18.04 to Ubuntu 22.04. The client is Ubuntu 22.04 and the server is Ubuntu 14.04. Using Ubuntu 18.04 as client works correctly. I have...

askubuntu.com

 

[dicko]

From all this are we to believe that it it is easier to patch your server around a security risk ( why it is why it is 'deprecated' ) rather than take the time to have the client just generate more secure ECDSA public keys (which are not deprecated) ?

edit

Ah!! I got it Windoze!! (there is a totally usable Linux subsystem for windows (2) if you take the effort ;-) )

but apparently

Using public keys for SSH authentication

the.earth.li

has recipes for generating better secured keys

 

[kenn10]

but apparently

Using public keys for SSH authentication
has recipes for generating better secured keys

Which is what I use. Considering I'm behind TM3 and essentially invisible unless white-listed (as most of the IncrediblePBX systems who don't go "Public' are, I don't think it is much of a risk nor has it been since 2007.