SAIL Community Supported PBX

Thanks S
That solved the issue.
Are you planning on drooping Debian as a base OS?

Here's some further information and observation on the latest SARK/SAIL packages

Ubuntu users only

The latest SARK 6.2 will install on Ubuntu 20.04LTS (Focal Fossa) or Ubuntu 22.04LTS (Jammy Jellyfish). It may install on other releases but these are the two which we currently test with and have packages for.

Debian users only

Debian has been a little bit of a rollercoaster ride for SARK and Asterisk over the last few years.-

Debian 10 (Buster) did not include the package for our preferred mail agent (ssmtp). As far as we know this was because ssmtp was unmaintained at that time. It was later re-included in Debian 11. Also, in Buster, Debian changed from using iptables to nftables. The problem for SARK is that we use the shorewall firewall which only runs with iptables. Furthermore, iptables can do packet searching whereas nftables can not. In spite of these changes, SARK/SAIL will install fine on Buster but you will need to use an alternative mail agent if you wish to do things like voicemail-to-email and you will need to set iptables as your preferred filter (see below).

Debian 11 (Bullseye) installs without issue but you still need to select iptables as your filter.

Debian 12 (Bookworm) does not include the Asterisk PBX package at all (you're kidding me, right? - Nope) Again, this appears to be due to a lack of resource to maintain it within the Debian group. If you want to know more then you can look at this thread..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031046

It may be that the next release - Debian 13 (Trixie) will have the necessary work done to include Asterisk but for now, if you want to run Asterisk under Debian12, then you'll likely need to install it from sources or from a third party package.

Summary

We ourselves have pretty much exclusively moved to Ubuntu for our own development and deployment.  Almost all of our customer systems are Ubuntu/AWS/ARM based instances.   Right now, it's just less of a hassle to deal with.   

Ubunru 18.04 is the last stable release

Ubuntu 20.04 is just about ready and we use it in production but it still has a few glitches which we're currently ironing out

Ubuntu 22.04 is pretty much in the same place as 20.04.

We're doing some further testing this week and I'll publish an update once we've finished.

The problems we've seen have been minor permissions issues and so forth but frustrating if you're doing a first time install.

which sail ver and debian should i using?
thanks

OK, I think we have a fix for this.  We're testing it in source at the moment but you can try it too if you wish.  There are two modules you need to change. 

The first module is /opt/sark/scripts/getmaclist.  Take a copy of it and save it somewhere safe.  Now open the module in your favorite editor and completely replace the existing code with this new code:-

#!/bin/sh
# get a list of macs amd manufacturers from IEEE
#

[ ! -e /opt/sark/www/sark-common/manuf.txt ]  && touch /opt/sark/www/sark-common/manuf.txt
chown www-data:www-data /opt/sark/www/sark-common/manuf.txt
curl -L -s "http://www.sailpbx.com/sail/public/manuf.txt" > /tmp/manuf.txt
ret=$?
if test "$ret" != "0"; then
     logger SARKgetmaclist - **** Link fail - Could not fetch new manufacturer MAC DB ****
     exit 4
fi   

if [ -s /tmp/manuf.txt ]; then
        diff /opt/sark/www/sark-common/manuf.txt /tmp/manuf.txt
        if [  "$?" -ne "0" ] ; then
                mv /tmp/manuf.txt /opt/sark/www/sark-common/manuf.txt
                logger SARKgetmaclist - updated manufacturer MAC DB
        else
                logger SARKgetmaclist - manufacturer MAC DB up to date
        fi
else
        logger SARKgetmaclist - **** Could not fetch new manufacturer MAC DB ****
fi

Next you must make a small change to /opt/sark/php/sarkextensions/view.php

At, or around, line 1956 you should find the following line

$short_vendor_cols = explode($delim,$vendorline,3);

You should replace this line with...

$short_vendor_cols = preg_split('/\s+/',$vendorline,3);

That's the changes done.  Now you can run the maclist...

sudo rm /opt/sark/www/sark-common/manuf.txt
sudo sh /opt/sark/scripts/getmaclist.sh

You should now have a new file in /opt/sark/www/sark-common/manuf.txt.  It will look a little different to the MAC list you used to have.

Now go ahead and add your new Yealink.  It should be picked up OK.

Let me know how this works for you.

Apologies for the late reply.  We've been moving offices and it took longer than we planned.  Anyhow, we're settled now.  I just did a from scratch install of Ubuntu 22.04 on a VM here.  It appears that our MAC/Manufacturer source is giving problems.   I'll address it with some haste and come back to you.  Thanks for calling this in to us.

OK Edited the /opt/sark/www/sark-common/manuf.txt file and added a line for that manufacturer. So now get the "mac already exists"
Looking in the IPphone table in the DB, both extensions that use 24:9A:D8 macs are there but do not display in extensions screen. I reset the system to factory and reapplied a backup and still the same failure.
Any clues as to why the phones with those macs would not add or display?

Hi S
PBX release: 16.28.0
SAIL Release: 6.2.0-16+deb10u1
HPE Release: 6.0.0-9

If I add and extension using 249AD82AB0FA as the mac it says it is invalid, but if I add 001565.... it works. Both are Yealink phones.
Maybe a clue, it is a system where I restored the backup from ver5 and all extensions bar the 2 that start with 249AD8... came across.
Do we need to update the DB with the OUI?

Usually if it is "LAN=/" then something went wrong in the IP discovery.   I haven't used Proxmox for quite some time and my memory is hazy.  The example I showed you above was from a live AWS Debian instance.  We also use Parallels for local testing and it behaves the same as AWS.

I'd be interested to see what "ip a" gives on your Proxmox instance. That may give some clues.



   

Thank you for the reply.
What lead us to this was in sngrep the packets were not getting back to the PBX from ITSP. Turn off shorewall and worked perfectly. The local.lan file read "LAN=/" and on some other systems it was 0.0.0.0/0 which works.

The PBX is a node in a Proxmox server with only 1 NIC defined.

I will run the php line and see what we get back.