ALERT Buh-bye CentOS.

Fresh install as of about 3 hours ago on December 24th. (9 PM Pacific Time USA GMT -8). Install went smoothly. Conversion to Public went smoothly.

Having trouble with /root/add-ip: When I allow ssh access, it allows port 22, but I have customized the SSH port during Public setup.

Having trouble with /root/add-fqdn: See previous entry...

You'd also need to change the port in add-ip and add-fqdn if you want to use the SSH option.
 
Hmm. Restored a backup from CentOS version. That seemed to go Okay, but now 'fwconsole ma updateall' fails:

Code:
Installing clearlydevices
Updating tables clearlydevices_extension_mapping, clearlydevices_brand_common_code_translation, clearlydevices_brand_common_codes, clearlydevices_config_files, clearlydevices_config_files_custom, clearlydevices_custom_device_details, clearlydevices_firmware, clearlydevices_firmware_compatibility, clearlydevices_firmware_config_files, clearlydevices_horkey_defaults, clearlydevices_horkey_states, clearlydevices_horkey_states_mapping, clearlydevices_images, clearlydevices_location_details, clearlydevices_location_options, clearlydevices_model_details, clearlydevices_model_options, clearlydevices_model_options_required, clearlydevices_models, clearlydevices_template_details, clearlydevices_template_device_details, clearlydevices_template_devices, clearlydevices_template_options, clearlydevices_templates, clearlydevices_apps, clearlydevices_rebuild...Done
Could not update database. Please contact support.

Moving from CentOS platform to Debian 10 is precarious as you discovered. I think you'd have better luck using a FreePBX backup/restore once you get the Incredible PBX 2021 platform up and running.
 
Already bored with holiday festivities and snowed in in the mountains, I just wiped my backup system VPS, replacing Centos IncrediblePBX 2020 with Debian IncrediblePBX 2021 Beta 5. The install was flawless and runs much faster than the Centos predecessor. I now have two Debian installs running perfectly.
 
Already bored with holiday festivities and snowed in in the mountains
Was a humid 21C here today with scattered showers. Not the normal Oz Christmas Day weather. :)
 
Was a humid 21C here today with scattered showers. Not the normal Oz Christmas Day weather. :)
You live in the land of Oz? Did you ever get a new wizard to replace the last one? How are the munchkins and the scarecrow??
 
With a little tweaking, I now have IncrediblePBX 2021 on Debian 10.7 running Asterisk 18.1.1. With the latest FreePBX module updates to core and framework Asterisk 18 is handled correctly. There are missing pieces that Asterisk 18 wants that FreePBX is not yet providing (stir_shaken.conf, a couple of dictation sound files) but otherwise, things work as expected.

1609005212246.png
 
Last edited:
Already bored with holiday festivities and snowed in in the mountains, I just wiped my backup system VPS, replacing Centos IncrediblePBX 2020 with Debian IncrediblePBX 2021 Beta 5. The install was flawless and runs much faster than the Centos predecessor. I now have two Debian installs running perfectly.
I was a good boy, so Santa has just delivered all the new blades that we are going to deploy next month at our new Ashburn colocation data center. My fellow IT guys will do the heavy lifting but I am keeping one of the blades for myself so that I can play to my heart's satisfaction.
And I am going to make iPBX2021 run this time without that stupid delay issue on the dashboard!
@kenn10 : Is there any reason you're using B4 instead of B5? I was under the impression that the latest on the git is B5.
More generally what should be my best bet (version-wise) for a fresh start?
@wardmundy : emm.. are 16 cores and 64 GB of RAM enough or should I throw in the kitchen sink with 32 cores and 128 GB? :rofl:
 
@kenn10 : Is there any reason you're using B4 instead of B5?
I upgraded the Asterisk on my B4 sandbox install. I had already made the minor changes that are included in B5. I was not doing a fresh install. I'd like to see Ward examine what I sent him on upgrading to Asterisk 18 and then release it into the wild before I do a fresh install. FreePBX still has a ways to go before the new features of Asterisk are included.
 
I'd stick with the Debian 2021 B5 for a fresh install of Asterisk-16. So far, its pretty bullet proof. There are some gotchas in moving to Asterisk-18 and it took me a good bit of googling and comparing scripts to get it to work. I don't know what other hidden gotchas are waiting to be discovered.
 
For those that want to experiment with Asterisk 18, I've added the upgrade-asterisk18 script from @kenn10 to the latest Incredible PBX 2021 installer. It requires the latest FreePBX modules which also are incorporated into new builds. Thanks, @kenn10 for all the hard work!!
 
Is it normal to see this many Apache2 processes spawned by Asterisk? There is no web usage active when this snapshot was taken. All 4 debian setups I've done look like this:
Code:
ps -ef |grep asterisk
root      1640     1  0 Dec26 ?        00:00:00 /bin/sh /usr/sbin/safe_asterisk -U asterisk -G asterisk
asterisk  1642  1640  0 Dec26 ?        00:16:47 /usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c
asterisk  1761     1  0 Dec26 ?        00:01:25 PM2 v4.5.0: God Daemon (/var/lib/asterisk/.pm2)
asterisk  6336   489  0 16:47 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk  6349   489  0 16:47 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk  6687   489  0 16:49 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk  6708   489  0 16:50 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk 21622   489  0 00:00 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk 21623   489  0 00:00 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk 22028  1761  0 13:17 ?        00:02:19 node /var/www/html/admin/modules/ucp/node/index.js
root     26292 25524  0 20:47 pts/0    00:00:00 grep asterisk
asterisk 32383   489  0 09:18 ?        00:00:01 /usr/sbin/apache2 -k start
asterisk 32386   489  0 09:18 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk 32387   489  0 09:18 ?        00:00:00 /usr/sbin/apache2 -k start
asterisk 32389   489  0 09:18 ?        00:00:00 /usr/sbin/apache2 -k start
 
@kenn10: Try this which gets my server down to 3:
Code:
sed -i 's|5|2|' /etc/apache2/mods-available/mpm_prefork.conf
systemctl restart apache2
ps -ef | grep asterisk
 
Much better. Only a couple of processes running.
 
@kenn10: But, as soon as I moved around in the FreePBX GUI, it shot back up to 11. So... I think we're SOL. Apache does what it does.
 
The processes don't seem to be sucking up resources, so I guess it doesn't matter. I just wanted to be sure there was nothing creating runaway Apache2 processes.
 
Last edited:
Final Working Asterisk 18 Upgrade Script

Code:
#!/bin/bash

# Special thanks to @kenn10 for all his work on this script.

echo "This utility stops Asterisk and upgrades it to latest Asterisk 18."
read -p "Press Enter to proceed at your own risk or Ctrl-C to abort..."
echo "Upgrading FreePBX 15 modules to avoid potential disaster..."
fwconsole ma upgradeall
fwconsole reload
/root/sig-fix
/root/sig-fix
fwconsole stop
echo "Beginning Asterisk 18 install process..."
cd /usr/src
rm -rf /usr/lib/asterisk
rm -rf /usr/lib64/asterisk
rm -rf asterisk-18*
touch /etc/asterisk/stir_shaken.conf
wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-18-current.tar.gz
tar zxvf asterisk-18*
rm -f asterisk-18*.tar.gz
cd asterisk-18*
contrib/scripts/get_mp3_source.sh
contrib/scripts/install_prereq install
make distclean
wget http://incrediblepbx.com/menuselect-incredible16-debian10.tar.gz
tar zxvf menuselect*.tar.gz
CFLAGS='-DENABLE_SRTP_AES_256 -DENABLE_SRTP_AES_GCM' ./configure  --libdir=/usr/lib64 --with-pjproject-bundled --with-jansson-bundled
make menuselect.makeopts
echo "Cleaning up missing modules noted above..."
menuselect/menuselect --enable-category MENUSELECT_ADDONS menuselect.makeopts
menuselect/menuselect --enable-category MENUSELECT_CODECS menuselect.makeopts
menuselect/menuselect --disable-category MENUSELECT_TESTS menuselect.makeopts
menuselect/menuselect --enable CORE-SOUNDS-EN-GSM --enable MOH-OPSOUND-WAV --enable EXTRA-SOUNDS-EN-GSM --enable cdr_mysql menuselect.makeopts
menuselect/menuselect --disable test_named_lock --disable test_res_pjsip_scheduler --disable test_file --disable test_bridging --disable test_res_pjsip_scheduler menuselect.makeopts
menuselect/menuselect --disable test_res_rtp --disable app_voicemail_odbc --disable app_voicemail_imap menuselect.makeopts
menuselect/menuselect --enable app_macro menuselect.makeopts
menuselect/menuselect --disable test_mwi --disable test_res_pjsip_session_caps --disable test_stasis_state --disable test_res_prometheus menuselect.makeopts
make menuselect.makeopts
make menuselect
read -p "Press Enter to proceed at your own risk or Ctrl-C to abort..."
make && make install && ldconfig && make config
fwconsole restart
read -p "All done. Press Enter key to load pbxstatus..."
pbxstatus

EqVfabFXYAMKyCf
 
Last edited:
I was wondering I have a solo repair shop and want to move from my current provider to a Vultr deploy possibly I have used the Cent OS version at my church I was wondering how easy it would be to install the latest beta and then upgrade to the production version? If it is possible to migrate that easily? I also wanted to ask if OSS Endpoint Manager is working in 2021 I have an old Cisco 508G I also have a Snom M3 laying around somewhere.

Thanks for your knowledge,
Robert
 
I have used the Cent OS version at my church I was wondering how easy it would be to install the latest beta and then upgrade to the production version?
Only @wardmundy can answer authoritatively, but I think the current beta will be pretty darn close to "production" and Ward will likely have patch scripts to get you there if needed.

I also wanted to ask if OSS Endpoint Manager is working in 2021
It should work if you want to stay with php 5,6. I worked on patching a lot of the php 7.3 issues, but it's a huge game of whack-a-mole and hard to determine what are the (many) existing bugs vs php version induced bugs. Each individual brand/model has php code embedded that needs to be touched.

My guess is FreePBX 16 will officially drop php 5.x support and OSS EPM may well be left to rot. It may not be the best to depend upon it.
 

Members online

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
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