SOLVED Upgrade RasPi to Incredible PBX 2021

[kenn10]

@ostridge I will remove my post above as it might confuse others.

 

[paradigmconnectivity]

@paradigmconnectivity
Can you post the result of the code:-

asterisk -rx "core show version"
Asterisk 18.x.x built by root @ incrediblepbx on a armv7l running Linux on 2021-11-16 13:41:38 UTC
## Note the 'pbxstatus uses the above "core show version" for the display - let me know if it does not work.
# and also post the alternative command
asterisk -V
# Asterisk 18.x.x

# also The source code directory name to show what you compiled from.
 ls -d /usr/src/asterisk-1*
# /usr/src/asterisk-18.x.x

EDIT: Sorry - my ...
Ignore the following -
now deleted from here down so not to confuse

@ostridge,

Fresh install from image this morning, with just basic initialization steps completed. Running the Asterisk 18 upgrade script, and here's the output you asked for:

root@incrediblepbx:~# asterisk -rx "core show version"
Asterisk 16.7.0 built by root @ incrediblepbx on a armv7l running Linux on 2020-01-21 14:30:47 UTC

root@incrediblepbx:~# asterisk -V
Asterisk 16.7.0

root@incrediblepbx:~# ls -d /usr/src/asterisk-1*
/usr/src/asterisk-18.9.0

Many thanks for looking at this with me. I'm stumped!

 

[wardmundy]

See this post. We will fix the upgrade installer BUT IT'S NOT FIXED YET. Merry Christmas.

Until Sangoma/Asterisk devs sort out their "improvements," we have frozen the Asterisk 18 upgrade at 18.8.0 for the time being. Here are the steps to install and run the new installer:

cd /root
rm -f upgrade-to-incrediblepbx2021
wget http://incrediblepbx.com/upgrade-to-incrediblepbx2021
chmod +x upgrade-to-incrediblepbx2021
./upgrade-to-incrediblepbx2021

UPDATE: As of Dec. 28, we have revised the upgrade script above to remove the affected modules:

codec_opus
codec_silk
codec_siren7
codec_siren14
codec_g729a

 

[ostridge]

I'm stumped!

= The asterisk-18* install failed. follow @wardmundy post above

 

[paradigmconnectivity]

Awesome. You guys are simply the greatest. Thank you very much, and Merry Christmas!!

 

[wardmundy]

Until Sangoma/Asterisk devs sort out their "improvements," we have frozen the Asterisk 18 upgrade at 18.7.0 for the time being. Here are the steps to install and run the new installer:

cd /root
rm -f upgrade-to-incrediblepbx2021
wget http://incrediblepbx.com/upgrade-to-incrediblepbx2021
chmod +x upgrade-to-incrediblepbx2021
./upgrade-to-incrediblepbx2021

 

[paradigmconnectivity]

Until Sangoma/Asterisk devs sort out their "improvements," we have frozen the Asterisk 18 upgrade at 18.7.0 for the time being. Here are the steps to install and run the new installer:

cd /root
rm -f upgrade-to-incrediblepbx2021
wget http://incrediblepbx.com/upgrade-to-incrediblepbx2021
chmod +x upgrade-to-incrediblepbx2021
./upgrade-to-incrediblepbx2021

Works like champ. Thank you for your great work, Ward. I've been a fan for a long time.

 

[Samot]

Until Sangoma/Asterisk devs sort out their "improvements,"

I'm not sure what there is to sort out, this change was covered in the changelogs for 16.23, 18.9 and 19.1. I know I'm going to sound like a skipping record but the changelogs need to be reviewed for version updates.

2021-10-12 13:17 +0000 [bac66e9743] Mike Bradeen <[email protected]>

* build: prevent binary downloads for non x86 architectures

download_externals: Add check for i686 and i386 (in addition
to the current x86_64) and exit if not one of the three.

ASTERISK-26497

Change-Id: Ia4d429fcefa5b2f5b6e99159d4607de8e8325b2f

Basically, previous versions this was a silent error and didn't exit.

 

[ostridge]

Until Sangoma/Asterisk devs sort out their "improvements," we have frozen the Asterisk 18 upgrade at 18.8.0

Until Sangoma/Asterisk devs sort out their "improvements," we have frozen the Asterisk 18 upgrade at 18.7.0 for the time being.

2020.3 upgraded to 2021 RPi4-8GB argononed.py

I guess that puts me out of step @ asterisk -V = 18.8.0
asterisk -x "core show version" =Asterisk 18.8.0
and /etc/php/5.6
so 'install-dual-php' not installed

Why do I need to backtrack to Asterisk 18.7.0 ??

 

[dallas]

I know I'm going to sound like a skipping record

But it's much better than silence if you know something we don't.

 

[wardmundy]

Of course, the big question is WHY such a stupid "improvement" that breaks existing upgrade scripts of everyone on the planet

UPGRADES SHOULDN'T NEEDLESSLY BREAK .

 

[Samot]

Of course, the big question is WHY such a stupid "improvement" that breaks existing upgrade scripts of everyone on the planet

UPGRADES SHOULDN'T NEEDLESSLY BREAK .

So an improvement that tells you things didnt actually install and stops the install to tell you why and fix it is stupid? Got it.

What isnt stupid is ignoring the changelogs and not making the proper adjustments to your scripts?

You keep not following the project and its changes then get bitten in the ass with it. I also doubt this broke every update script on the planet because there are others that pay attention and adjust to changes.

Stop blaming Asterisk and Sangoma for something you had full control over but just didnt do the work.

 

[wardmundy]

No @Samot, the “improvement” was removing these modules from the install entirely when they’ve been included for years. The fact that you get an error message now instead of a successful install wasn’t the kind of enhancement most of us are looking for. But, yes, we should read all of the change logs for every component in Incredible PBX and modify every script accordingly. Tell me again what you do for the open source community.

 

[Samot]

the “improvement” was removing these modules from the install entirely when they’ve been included for years.

Asterisk is designed and built for x86 systems. In the case of the RasPI, which is not x86, in the past Asterisk would have silently just downloaded the x86 versions of the modules. These modules, if enabled, would not have worked. So this improvement is to help those with non-x86 systems installing this to know certain things aren't going to work since the system is trying to get the x86 versions. So now you know that you need to either not enable certain things or see if there is a version for the non-x86 platform being used. This complaint is basically boiling down to "It didn't work as it should before and I got no warnings or notice but now I do and that sucks".

The fact that you get an error message now instead of a successful install wasn’t the kind of enhancement most of us are looking for.

That's the point, the install wasn't truly successful. The x86 modules wouldn't work on an non-x86 system, you just never knew.

But, yes, we should read all of the change logs for every component in Incredible PBX and modify every script accordingly.

That would be excellent.

Tell me again what you do for the open source community.

I pay attention to the actual projects of said community and help those in the community use it. In regards to Asterisk, specifically; I watch the mailing lists on a regular basis, I watch the activity on Gerrit where code reviews and discussions are done. I am active on the forums, I am active in dev/community channels. I even check in on Jira tickets. Same is pretty much true for FreePBX.

For someone that is offering a re-skin of FreePBX with some extra stuff included you should be aware of what FreePBX and Asterisk are doing. As I pointed out before, there are things from Asterisk that even FreePBX isn't paying attention to. If you were paying attention and realized that you could have made changes in IPBX that would have made it more improved and feature rich than FreePBX itself.

 

[wardmundy]

It's an open source project. You are more than welcome to contribute, @Samot.

 

[Samot]

It's an open source project. You are more than welcome to contribute, @Samot.

And what is the process for contributions?

 

[wardmundy]

DM me. Email me (myname at gmail). Post it here. Your choice.

 

[wardmundy]

@Samot: Just curious if you know...

Running make menuselect.makeopts used to disable modules that couldn't be installed. Same was true by running make menuselect manually. When you clicked Save, you always got a clean make going forward. Why the different behavior with these codecs?? Throwing up an error after going through the entire make process (for 20+ minutes on a RasPi) is very different behavior and would be confusing even to experts which I don't profess to be.

 

[Samot]

@Samot: Just curious if you know...

Running make menuselect.makeopts used to disable modules that couldn't be installed. Same was true by running make menuselect manually. When you clicked Save, you always got a clean make going forward. Why the different behavior with these codecs?? Throwing up an error after going through the entire make process (for 20+ minutes on a RasPi) is very different behavior and would be confusing even to experts which I don't profess to be.

menuselect, as far as I know, is unaware of what the platform is as is the binary module stuff remotely. I believe this is one of the things where support could be added but since the subset of users it would impact is really tiny the simpler option of warnings and what the errors are was opted for.

Asterisk is an open source project, much like IncrediblePBX, so adding support for this can be contributed.

 

[wardmundy]

@Samot: If you think Asterisk as an "open source project" is "much like Incredible PBX," I'd suggest you re-read the Contributor License Agreement that is required for Asterisk contributions. We don't sell our stuff nor that of our contributors. Nor do we use it in closed source, commercial projects.

As for menuselect, I think it is worth noting that this is very different behavior than what. occurs with every other Asterisk module. Deciphering an OS platform is trivial. I'd be surprised if it's not already in the menuselect source code.