SAIL Community Supported PBX

Had to
unload app_voicemail_imap.so
and
load app_voicemail_imap

In the modules.conf so now phone calls get to the phone. Before the system sent a bye packet before the system rang.
But the voicemail gets the prompts but fails the password.

From what I have been reading only 1 voicemail module should be loaded. But it seems voicemail_imap.so supports comedian Mail (ie) *51* although it answered on *50* and then fails the password.
If you load app_voicemail_imap.so from the modules.conf and then try and unload from the cli (which fails) and then load app_voicemail.so we get the VoiceMailMain application back.

Is there an answer to this riddle? How to get it back to being stable?

PBX release: 20.4.0
SAIL Release: 6.2.0-35
HPE Release: 6.0.0-9

May have solved it
When we have this it works
Module                         Description                              Use Count  Status      Support Level
app_voicemail.so               Comedian Mail (Voicemail System)         0          Running              core
app_voicemail_imap.so          Comedian Mail (Voicemail System) with IM 0          Running              core
app_voicemail_odbc.so          Comedian Mail (Voicemail System) with OD 0          Not Running          core
3 modules loaded
So the default is only app_voicemail_imap.so running but that does not load VoiceMailMain

module load app_voicemail.so

unloading the odbc module also works
Module                         Description                              Use Count  Status      Support Level
app_voicemail.so               Comedian Mail (Voicemail System)         0          Running              core
app_voicemail_imap.so          Comedian Mail (Voicemail System) with IM 0          Running              core

But this should be set from modules.conf. Might try a preload in the conf file to get it automatically. It also solved another issue where trunks did not answer if linked to voicemail. Just dropped the call with a bye command.

Hi
I have tried this on Jammy and Mantic and no change to the issue.
This is standard output with the modules.conf file as installed

---

pbx-ub*CLI> module show like voicemail
Module                         Description                              Use Count  Status      Support Level
app_voicemail.so               Comedian Mail (Voicemail System)         0          Not Running          core
app_voicemail_imap.so          Comedian Mail (Voicemail System) with IM 0          Running              core                           
app_voicemail_odbc.so          Comedian Mail (Voicemail System) with OD 0          Not Running          core

---

the result
[2024-03-29 09:58:05] ERROR[572]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 501 in context default
    -- AGI Script Executing Application: (VoiceMailMain) Options: (501)
[2024-03-29 09:58:06] WARNING[1147][C-00000001]: res_agi.c:3181 handle_exec: Could not find application (VoiceMailMain)
    -- <SIP/501-00000000>AGI Script sarkhpe completed, returning 0
    -- Auto fallthrough, channel 'SIP/501-00000000' status is 'UNKNOWN'
[2024-03-29 09:58:28] ERROR[572]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 501 in context default
[2024-03-29 09:58:39] ERROR[572]: app_voicemail_imap.c:2816 inboxcount2: Couldn't find mailbox 501 in context default[/size]

If we noload app_voicemail_imap.so we do not get the error messages "Couldn't find mailbox..." But still get "Could not find application (VoiceMailMain)"

In Ubuntu there is a package (deb) for VoiceMail but it is for asterisk 16.
asterisk-voicemail_16.2.1~dfsg-2ubuntu1_amd64.deb
and if we unload off app_voicemail_imap.so and use the app_voicemail.so we loose the Mailbox errors but still have no VoiceMailMain appication. See attached list

Any ideas on how to get voicemail back?
Thanks.

I'll look at it.   You're right, it should burp.

Solved
The DID was the same ID as used for a trunk. We need the full number for the DID so dropped the trunk and recreated with different ID. Is a error trap possible instead of a blank screen?

PBX release: 20.1.0
SAIL Release: 6.2.0-35
HPE Release: 6.0.0-9
Endpoints defined: 4
Serial Num: 936191

Hi S
Anyone have an interpretation of this

---

Wed Feb 07 07:53:21.819550 2024] [php:warn] [pid 270] [client xxx.xxx.xxx.xxx:55830] PHP Warning:  Undefined array key "smartlink" in /opt/sark/php/sarkddi/view.php on line 370, refer
er: https://mail.torresbusiness.com.au:28443/php/sarkddi/main.php                                                                                                                     
[Wed Feb 07 07:53:21.819618 2024] [php:error] [pid 270] [client xxx.xxx.xxx.xxx:55830] PHP Fatal error:  Uncaught Error: Undefined constant "trunk" in /opt/sark/php/sarkddi/view.php:31
7\nStack trace:\n#0 /opt/sark/php/sarkddi/view.php(58): sarkddi->saveNew()\n#1 /opt/sark/php/srkmain.php(58): sarkddi->showForm()\n#2 /opt/sark/php/sarkddi/main.php(3): require_once(
'...')\n#3 {main}\n  thrown in /opt/sark/php/sarkddi/view.php on line 317, referer: https://xxx.xxx.xxx.xxx:28443/php/sarkddi/main.php

---

I have 3 DID's already in the list just need to add a 4th. Thanks

I've been playing around with a 64bit arm .img install for RaspberryPi.   You've always been able to install sark on the 64 bit Pi 4 but, to make it easier, we've put up a ready-to-run image here:-

http://www.sailpbx.com/sail/raspi-arm-64-img/

Download it and burn it onto a microSD card with the RaspberryPi imager and it should just run on any Pi 4. 
N.B.  The image inflates to about 7.6Gb so you'll need a micro SDcard of at least 8Gb.

SSH login creds are

UID sark
PWD sarkadmin

The front-end browser is just the same as always.

UID admin
PWD sarkadmin

No, I don't think we'll drop it.   It's difficult to know for now what will happen with Debian 12 and Asterisk.  I suspect it will come back in 13 and someone will do a backport to fetch it into 12 but that's just a guess so we'll have to see.

I've just tidied up the 6.2 installer for Ubu 22.04 and Deb11 and it looks OK.  You will see this appear as 6.2.0-34 or 35.   These will be the last few releases for 6.2 and it will move into maintenance as we begin to roll out 6.5 over the next few months. 

I've also been playing around with a 64bit arm install for RaspberryPi.   You've always been able to install sark on the 64 bit Pi but we've put up a ready-to-run image here:-

http://www.sailpbx.com/sail/raspi-arm-64-img/

Download it and burn it onto a microSD card with the RaspberryPi imager and it should just run on any Pi 4. 
N.B.  The image inflates to about 7.6Gb do you'll need a micro SDcard of at least 8Gb.

SSH creds are

UID sark
PWD sarkadmin

The front-end browser is just the same as always.

UID admin 
PWD sarkadmin