SOLVED Upgrade RasPi to Incredible PBX 2021

wardmundy · Jun 17, 2021

If you'd like to upgrade your Raspberry Pi from Incredible PBX 2020 to 2021 which offers Asterisk 18 and the latest FreePBX modules, here's a new script to handle it. Make a good backup first and let us know of any surprises. :chef:

Code:

cd /root
wget http://incrediblepbx.com/2021-raspi-upgrade.tar.gz
tar zxvf 2021-raspi-upgrade.tar.gz
rm -f 2021-raspi-upgrade.tar.gz
./upgrade-to-incrediblepbx2021

wardmundy · Jun 18, 2021

Moving from Incredible PBX 2020 to 2021 on the Raspberry Pi – Nerd Vittles

nerdvittles.com

dallas · Jun 19, 2021

@wardmundy So I've been trying to get to Asterisk 18 & FreePBX 15 on my Pi 4B. All I've been able to achieve is Asterisk 16.18.0 and Incredible GUI 15.0.12.68. My Pi 4 has never processed a call as I'm still using a Pi 3B for calls.
Do you think I'll be safe running upgrade-to-incrediblepbx2021 or have I messed up by updating FreePBX 'outside' the official upgrade path?

wardmundy · Jun 19, 2021

Make a backup and go for it.

ostridge · Jun 20, 2021

dallas said:
Do you think I'll be safe

Well that's a bit subjective - best if it isn't mission crytical production.

wardmundy · Jun 20, 2021

Follow the tutorial and work from the backup SDcard. Then you have nothing to lose.

dallas · Jun 22, 2021

Didn't go so well. After update, calling *97 resulted in hangup. Log has error "Couldn't find mailbox XXX in context default"
*98 got to VM prompt "mailbox?" but doesn't accept the password.

EDIT
Rolled back to Asterisk 16.17.0 and Incredible GUI 15.0.12.68 and it's ok.
Time to blow it away and start again with incrediblepbxfax2020.3.

Code:

root@incrediblepbx:~# asterisk -vvvvvvvr
Asterisk 18.4.0, Copyright (C) 1999 - 2021, Sangoma Technologies Corporation and others.
Created by Mark Spencer <[email protected]>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 18.4.0 currently running on incrediblepbx (pid = 2896)
[2021-06-23 15:40:04] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 701 in context default
[2021-06-23 15:40:04] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 704 in context default
[2021-06-23 15:40:04] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 702 in context default
[2021-06-23 15:40:04] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 705 in context default
[2021-06-23 15:40:04] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 703 in context default
[2021-06-23 15:40:14] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 701 in context default
[2021-06-23 15:40:14] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 704 in context default
[2021-06-23 15:40:14] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 702 in context default
[2021-06-23 15:40:14] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 705 in context default
[2021-06-23 15:40:14] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 703 in context default
  == Using SIP RTP TOS bits 184
  == Using SIP RTP CoS mark 5
       > 0xb3a19dd0 -- Strict RTP learning after remote address set to: 192.168.40.73:8000
    -- Executing [*97@from-internal:1] Macro("SIP/705-00000002", "user-callerid,") in new stack
    -- Executing [s@macro-user-callerid:1] Set("SIP/705-00000002", "TOUCH_MONITOR=1624426816.2") in new stack
    -- Executing [s@macro-user-callerid:2] Set("SIP/705-00000002", "AMPUSER=705") in new stack
    -- Executing [s@macro-user-callerid:3] Set("SIP/705-00000002", "HOTDESCKCHAN=705-00000002") in new stack
    -- Executing [s@macro-user-callerid:4] Set("SIP/705-00000002", "HOTDESKEXTEN=705") in new stack
    -- Executing [s@macro-user-callerid:5] Set("SIP/705-00000002", "HOTDESKCALL=0") in new stack
    -- Executing [s@macro-user-callerid:6] ExecIf("SIP/705-00000002", "0?Set(HOTDESKCALL=1)") in new stack
    -- Executing [s@macro-user-callerid:7] ExecIf("SIP/705-00000002", "0?Set(CALLERID(name)=)") in new stack
    -- Executing [s@macro-user-callerid:8] GotoIf("SIP/705-00000002", "0?report") in new stack
    -- Executing [s@macro-user-callerid:9] ExecIf("SIP/705-00000002", "1?Set(REALCALLERIDNUM=705)") in new stack
    -- Executing [s@macro-user-callerid:10] Set("SIP/705-00000002", "AMPUSER=705") in new stack
    -- Executing [s@macro-user-callerid:11] GotoIf("SIP/705-00000002", "0?limit") in new stack
    -- Executing [s@macro-user-callerid:12] Set("SIP/705-00000002", "AMPUSERCIDNAME=705") in new stack
    -- Executing [s@macro-user-callerid:13] ExecIf("SIP/705-00000002", "0?Set(__CIDMASQUERADING=TRUE)") in new stack
    -- Executing [s@macro-user-callerid:14] GotoIf("SIP/705-00000002", "0?report") in new stack
    -- Executing [s@macro-user-callerid:15] Set("SIP/705-00000002", "AMPUSERCID=705") in new stack
    -- Executing [s@macro-user-callerid:16] Set("SIP/705-00000002", "__DIAL_OPTIONS=HhTtr") in new stack
    -- Executing [s@macro-user-callerid:17] Set("SIP/705-00000002", "CALLERID(all)="705" <705>") in new stack
    -- Executing [s@macro-user-callerid:18] ExecIf("SIP/705-00000002", "0?Set(CUSDIAL=)") in new stack
    -- Executing [s@macro-user-callerid:19] ExecIf("SIP/705-00000002", "0?Set(CALLERID(all)="705" <705>)") in new stack
    -- Executing [s@macro-user-callerid:20] GotoIf("SIP/705-00000002", "0?limit") in new stack
    -- Executing [s@macro-user-callerid:21] ExecIf("SIP/705-00000002", "0?Set(GROUP(concurrency_limit)=705)") in new stack
    -- Executing [s@macro-user-callerid:22] NoOp("SIP/705-00000002", "Macro Depth is 1") in new stack
    -- Executing [s@macro-user-callerid:23] GotoIf("SIP/705-00000002", "1?report2:macroerror") in new stack
    -- Goto (macro-user-callerid,s,24)
    -- Executing [s@macro-user-callerid:24] GotoIf("SIP/705-00000002", "0?continue") in new stack
    -- Executing [s@macro-user-callerid:25] Set("SIP/705-00000002", "__TTL=64") in new stack
    -- Executing [s@macro-user-callerid:26] GotoIf("SIP/705-00000002", "1?continue") in new stack
    -- Goto (macro-user-callerid,s,42)
    -- Executing [s@macro-user-callerid:42] Set("SIP/705-00000002", "CALLERID(number)=705") in new stack
    -- Executing [s@macro-user-callerid:43] Set("SIP/705-00000002", "CALLERID(name)=705") in new stack
    -- Executing [s@macro-user-callerid:44] GotoIf("SIP/705-00000002", "0?cnum") in new stack
    -- Executing [s@macro-user-callerid:45] Set("SIP/705-00000002", "CDR(cnam)=705") in new stack
    -- Executing [s@macro-user-callerid:46] Set("SIP/705-00000002", "CDR(cnum)=705") in new stack
    -- Executing [s@macro-user-callerid:47] Set("SIP/705-00000002", "CHANNEL(language)=en") in new stack
    -- Executing [*97@from-internal:2] Set("SIP/705-00000002", "CONNECTEDLINE(name-charset,i)=utf8") in new stack
    -- Executing [*97@from-internal:3] Set("SIP/705-00000002", "CONNECTEDLINE(name,i)=My Voicemail") in new stack
    -- Executing [*97@from-internal:4] Set("SIP/705-00000002", "CONNECTEDLINE(num,i)=705") in new stack
    -- Executing [*97@from-internal:5] Answer("SIP/705-00000002", "") in new stack
       > 0xb3a19dd0 -- Strict RTP switching to RTP target address 192.168.40.73:8000 as source
    -- Executing [*97@from-internal:6] Wait("SIP/705-00000002", "1") in new stack
    -- Executing [*97@from-internal:7] Macro("SIP/705-00000002", "get-vmcontext,705") in new stack
    -- Executing [s@macro-get-vmcontext:1] Set("SIP/705-00000002", "VMCONTEXT=default") in new stack
    -- Executing [s@macro-get-vmcontext:2] GotoIf("SIP/705-00000002", "0?200:300") in new stack
    -- Goto (macro-get-vmcontext,s,300)
    -- Executing [s@macro-get-vmcontext:300] NoOp("SIP/705-00000002", "") in new stack
    -- Executing [*97@from-internal:8] Set("SIP/705-00000002", "VMBOXEXISTSSTATUS=FAILED") in new stack
    -- Executing [*97@from-internal:9] GotoIf("SIP/705-00000002", "0?mbexist") in new stack
[2021-06-23 15:40:17] WARNING[7361][C-00000003]: pbx.c:2927 pbx_extension_helper: No application 'VoiceMailMain' for extension (from-internal, *97, 10)
  == Spawn extension (from-internal, *97, 10) exited non-zero on 'SIP/705-00000002'
    -- Executing [h@from-internal:1] Macro("SIP/705-00000002", "hangupcall") in new stack
    -- Executing [s@macro-hangupcall:1] GotoIf("SIP/705-00000002", "1?theend") in new stack
    -- Goto (macro-hangupcall,s,3)
    -- Executing [s@macro-hangupcall:3] ExecIf("SIP/705-00000002", "0?Set(CDR(recordingfile)=)") in new stack
    -- Executing [s@macro-hangupcall:4] NoOp("SIP/705-00000002", " montior file= ") in new stack
    -- Executing [s@macro-hangupcall:5] GotoIf("SIP/705-00000002", "1?skipagi") in new stack
    -- Goto (macro-hangupcall,s,7)
    -- Executing [s@macro-hangupcall:7] Hangup("SIP/705-00000002", "") in new stack
  == Spawn extension (macro-hangupcall, s, 7) exited non-zero on 'SIP/705-00000002' in macro 'hangupcall'
  == Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/705-00000002'
[2021-06-23 15:40:24] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 701 in context default
[2021-06-23 15:40:24] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 704 in context default
[2021-06-23 15:40:24] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 702 in context default
[2021-06-23 15:40:24] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 705 in context default
[2021-06-23 15:40:24] ERROR[2980]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 703 in context default
incrediblepbx*CLI>
Disconnected from Asterisk server
Asterisk cleanly ending (0).
Executing last minute cleanups
root@incrediblepbx:~#
[Code/]

dallas · Jun 23, 2021

ostridge said:
Well that's a bit subjective - best if it isn't mission crytical production.

This is my play thing...

dallas · Jun 25, 2021

A little more info
"1701[2021-06-25 17:57:14] ERROR[19740] app_voicemail.c: Failure registering applications, functions or tests"

Code:

1680[2021-06-25 17:57:14] VERBOSE[19740] loader.c: Loading app_voicemail.so.
1681[2021-06-25 17:57:14] WARNING[19740] app_voicemail.c: maxsilence should be less than minsecs or you may get empty messages
1682[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 701 in context default
1683[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 701 in context device
1684[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 702 in context default
1685[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 702 in context device
1686[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 703 in context default
1687[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 703 in context device
1688[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 704 in context default
1689[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 704 in context device
1690[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 705 in context default
1691[2021-06-25 17:57:14] WARNING[19775] app_voicemail_imap.c: Couldn't find mailbox 705 in context device
1692[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Registered application 'VoiceMail'
1693[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Registered application 'VoiceMailMain'
1694[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Registered application 'VMAuthenticate'
1695[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Registered application 'VoiceMailPlayMsg'
1696[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Registered application 'VMSayName'
1697[2021-06-25 17:57:14] ERROR[19740] pbx_functions.c: Function VM_INFO already registered.
1698[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager registered action VoicemailUsersList
1699[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager registered action VoicemailUserStatus
1700[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager registered action VoicemailRefresh
1701[2021-06-25 17:57:14] ERROR[19740] app_voicemail.c: Failure registering applications, functions or tests
1702[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Unregistered application 'VoiceMail'
1703[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Unregistered application 'VoiceMailMain'
1704[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Unregistered application 'VMAuthenticate'
1705[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Unregistered application 'VoiceMailPlayMsg'
1706[2021-06-25 17:57:14] VERBOSE[19740] pbx_app.c: Unregistered application 'VMSayName'
1707[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager unregistered action VoicemailUsersList
1708[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager unregistered action VoicemailUserStatus
1709[2021-06-25 17:57:14] VERBOSE[19740] manager.c: Manager unregistered action VoicemailRefresh
1710[2021-06-25 17:57:14] VERBOSE[19740] loader.c: Loading func_blacklist.so.

dallas · Jun 26, 2021

Solution found here. https://www.voip-info.org/forum/threads/upgrade-raspi-to-incredible-pbx-2021.25703/#post-157924

wardmundy · Jun 27, 2021

Automatic Update Utility has pushed out the fix. Scripts have been patched as well.

ostridge · Jun 27, 2021

dallas said:
Solution found here.

Well spotted

Jake · Jul 22, 2021

I successfully updated to 2021! Everything works fine. Thanks

Stephen Harrington · Jul 23, 2021

@wardmundy

Would it be possible to make available an "update-asterisk18" script for our upgraded RasPi 2021 installations similar to the "upgrade-asterisk16" script we used to have?

It would be much appreciated by many I'm sure!

ostridge · Jul 23, 2021

Stephen Harrington said:
Would it be possible to make available an "update-asterisk18" script

Well it is possible, and I think it will be a case of when it is available and useable for several platforms.

wardmundy · Jul 23, 2021

@Stephen: Try this:

Code:

cd /root
wget http://incrediblepbx.com/upgrade-asterisk18-raspi.tar.gz
tar zxvf upgrade-asterisk18-raspi.tar.gz
rm -f upgrade-asterisk18-raspi.tar.gz
./upgrade-asterisk18

Stephen Harrington · Jul 23, 2021

@wardmundy

Had to massively edit this reply because ...

On my first go I had no luck, but I think that was because one of the required repositories just happened to be offline - Murphy's Law!

On my second attempt it all went well.

Actual update, for reference, was from 18.4.0 => 18.5.1 (latest at time of writing this).

Thanks for making this available Ward, much appreciated as always!

paradigmconnectivity · Dec 19, 2021

Greetings friends,

I'm buildling a new Incredible PBX on a Raspberry Pi 4. I'm using the latest incrediblepbxfax2020.3.img and this is a fresh install with no real FreePBX configuration changes yet. I'm using the super easy guide "Moving from Incredible PBX 2020 to 2021 on the Raspberry Pi" but I feel like I'm missing something. The upgrade process appears to complete successfully, I can watch it build and install Asterisk 18, but when I reboot I'm still on Asterisk 16. I feel like I'm probably being a dork and missing something simple, but I've actually re-built this Pi 3 times now for troubleshooting, and I'm consistently having the same result.

The process ends with:

Latest Asterisk 18 installed with latest FreePBX 15 modules.

Press Enter key to continue...

I reboot, and SSH into the Pi, and the CLI status page says I'm on the new Incredible PBX/FAX 2021.01. However, it says I'm still on Asterisk 16.7.0.

The reason I think I may just be being a dork is because I'm having a similar problem on an older Incredible PBX on a Pi 2. It has been running for several months, and it's on Incredible PBX 2020.3, with Asterisk 16.20.0. When I run the script "update-asterisk16" I can watch it build and install Asterisk 16.23.0, but when it's all done I'm still on 16.20.0.

Can someone kindly guide me on where I'm going wrong?

Thank you!
Russ

ostridge · Dec 22, 2021

paradigmconnectivity said:
Greetings friends,

I'm buildling a new Incredible PBX on a Raspberry Pi 4. I'm using the latest incrediblepbxfax2020.3.img and this is a fresh install with no real FreePBX configuration changes yet. I'm using the super easy guide "Moving from Incredible PBX 2020 to 2021 on the Raspberry Pi" but I feel like I'm missing something. The upgrade process appears to complete successfully, I can watch it build and install Asterisk 18, but when I reboot I'm still on Asterisk 16. I feel like I'm probably being a dork and missing something simple, but I've actually re-built this Pi 3 times now for troubleshooting, and I'm consistently having the same result.

The process ends with:

Latest Asterisk 18 installed with latest FreePBX 15 modules.

Press Enter key to continue...

I reboot, and SSH into the Pi, and the CLI status page says I'm on the new Incredible PBX/FAX 2021.01. However, it says I'm still on Asterisk 16.7.0.

View attachment 3814

The reason I think I may just be being a dork is because I'm having a similar problem on an older Incredible PBX on a Pi 2. It has been running for several months, and it's on Incredible PBX 2020.3, with Asterisk 16.20.0. When I run the script "update-asterisk16" I can watch it build and install Asterisk 16.23.0, but when it's all done I'm still on 16.20.0.

Can someone kindly guide me on where I'm going wrong?

Thank you!
Russ

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

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

kenn10 · Dec 22, 2021

@ostridge not sure why you tagged me. I've never had a problem with the upgrade scripts on my cloud instances. I don't use the Raspberry Pi. The issues I encountered were with Debian 11 and trying to piecemeal the IncredblePBX2022B1 script to work with Debian 11. Everything is good on Debian 10. I believe Ward is making progress with Debian 11 and the PHP issues.

SOLVED Upgrade RasPi to Incredible PBX 2021

Nerd Uno

Nerd Uno

Well-Known Member

Nerd Uno

Guru

Nerd Uno

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Nerd Uno

Guru

Active Member

Member

Guru

Nerd Uno

Member

New Member

Guru

Well-Known Member

Forum statistics