Asterisk 23, anyone running it?

Nobody expected "drop of the hat" same day FreePBX support for Asterisk 23, but... Correct me if I'm wrong but I believe we are on our FIFTH release of Asterisk 23 and still no FreePBX support. The two open source products are owned and developed by the same company!
 
Nobody expected "drop of the hat" same day FreePBX support for Asterisk 23,
A statement was made that "if a certain someone was still in charge, it would have been resolved same day" and I just pointed out that FreePBX has historically lagged behind in releasing packages of new Asterisk versions. It's always been worse for standard versions because they only live for one year basically.

This is a conversation that happens every year about how long it takes to adopt an Asterisk version in official FreePBX systems. People will next complain about v24 not being available quick enough after its release in October.
 
A statement was made that "if a certain someone was still in charge, it would have been resolved same day" and I just pointed out that FreePBX has historically lagged behind in releasing packages of new Asterisk versions. It's always been worse for standard versions because they only live for one year basically.

This is a conversation that happens every year about how long it takes to adopt an Asterisk version in official FreePBX systems. People will next complain about v24 not being available quick enough after its release in October.
When you're only 3 months away from being a full version behind in FreePBX support for Asterisk, some of the criticism is probably warranted. Wouldn't you agree??
 
When Incredible PBX 2026 users can run the upgrade-asterisk script and get a working Asterisk 23 platform with zero breakage in under 15 minutes, you can't help wondering if Sangoma really cares about their VoIP platform any longer.

Screenshot 2026-06-18 at 11.12.08 AM copy.png
 
Allowing FreePBX-17 to install on an already installed Asterisk-23 version does not take RPM's for FreePBX. It takes changing the install.php to allow <= 23. RPM's have nothing to do with the installation of IncrediblePBX-2026 using Asterisk and FreePBX-17. This is what used to get corrected quickly, well before the RPM's were QA'd and released.

I changed this portion of the install.php myself but there may be other parts I missed.
Code:
 22 $engine_info = engine_getinfo();
 23 $astversion = $engine_info['version'];
 24 if (version_compare($astversion, "18", "lt") || version_compare($astversion, "25", "ge")) {
 25         out(sprintf(_("<error>Error!</error>")));
 26         out(sprintf(_("<error>Unsupported Version of %s </error>"), $astversion));
 27         out(sprintf(_("<error>Supported Asterisk versions: 18, 19, 20, 21, 22, 23</error>")));
 28         exit(1);
 
Allowing FreePBX-17 to install on an already installed Asterisk-23 version does not take RPM's for FreePBX. It takes changing the install.php to allow <= 23. RPM's have nothing to do with the installation of IncrediblePBX-2026 using Asterisk and FreePBX-17. This is what used to get corrected quickly, well before the RPM's were QA'd and released.

I changed this portion of the install.php myself but there may be other parts I missed.
Code:
 22 $engine_info = engine_getinfo();
 23 $astversion = $engine_info['version'];
 24 if (version_compare($astversion, "18", "lt") || version_compare($astversion, "25", "ge")) {
 25         out(sprintf(_("<error>Error!</error>")));
 26         out(sprintf(_("<error>Unsupported Version of %s </error>"), $astversion));
 27         out(sprintf(_("<error>Supported Asterisk versions: 18, 19, 20, 21, 22, 23</error>")));
 28         exit(1);
I think you missed one other spot to make the change. Testing the following now:
Code:
sed -i 's|22<|22, 23<|' /usr/src/freepbx/install.php
sed -i 's|23"|24"|' /usr/src/freepbx/install.php
sed -i 's|22<|22, 23<|' /usr/src/freepbx/installlib/installcommand.class.php
sed -i 's|23"|24"|' /usr/src/freepbx/installlib/installcommand.class.php
 
Try this and choose Asterisk 23 option:
Code:
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/IncrediblePBX2026new.sh
chmod +x IncrediblePBX2026new.sh
./IncrediblePBX2026new.sh
 
Try this and choose Asterisk 23 option:
Code:
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/IncrediblePBX2026new.sh
chmod +x IncrediblePBX2026new.sh
./IncrediblePBX2026new.sh
@hecatae give this a shot and see how it works for you.
 
I've gone ahead and pushed this out as the latest IncrediblePBX2026.sh installer since I see no surprises in either the install or in operation. Installer gives admins the option of Asterisk 22 or 23 when run. By all means, holler if it smokes.:sifone:
 
Last edited:
One cautionary note. Not that I don't trust 'em, but...

If the FreePBX devs were to change the logic in the current installer, that might cause breakage with the current install script which relies upon and downloads the current FreePBX installer from Sangoma. We've made a backup copy of the current open source FreePBX code which can be substituted in the installer should that ever happen.
 
Well, Chris over at FreePBX seems to think this was already fixed in the current shell install of FreePBX-17. I'm certainly not ready to try it as my system is up and running nor do I trust that the issue is fixed on Sangoma's end.

They appear to be pre-programmed to go blind and stupid if they see Debian-13 mentioned.

 

Members online

No members online now.

Forum statistics

Threads
26,706
Messages
174,531
Members
20,273
Latest member
rhys96999
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top