SAIL Community Supported PBX

Hi there,

All good here.  The local.lan file should show the subnet CIDR.  Like this

root@ip-10-0-1-34:~# cat /etc/shorewall/local.lan
LAN=10.0.1.0/24

A routine called setip (/opt/sark/generator/setip.php) runs as a systemd task (called setlan) each time you reboot the box.  Among other things, it attempts to figure out the local network CIDR and set it into local.lan

Things which can sometimes confuse it are multiple NICs on the box with the second (or higher) NIC attached to the LAN and NIC 0 empty.

The easiest way to see what it's doing is to simply run it inline and then look at syslog.

php /opt/sark/generator/setip.php
Syslog should look something like this

May  8 15:31:51 ip-10-0-1-34 php: SRK setip Interface name on this node: eth0
May  8 15:31:51 ip-10-0-1-34 php: SRK setip IPV4: 10.0.1.34
May  8 15:31:51 ip-10-0-1-34 php: SRK setip staticIPV4:
May  8 15:31:51 ip-10-0-1-34 php: SRK setip Network address: 10.0.1.0
May  8 15:31:51 ip-10-0-1-34 php: SRK setip netmask: 255.255.255.0
May  8 15:31:51 ip-10-0-1-34 php: SRK setip CIDR: 24
Hope this helps

May have found the answer
If you run
shorewall show zones

it returns 0.0.0.0/0 and when I modify the local.lan file from "/" to "0.0.0.0/0" it now works as expected.

Hi
Hope all is well on your side of the world.
PBX release: 16.28.0
SAIL Release: 6.2.0-16+deb10u1
HPE Release: 6.0.0-9

My trunks show as unreachable whilst I have shorewall running. Turn it off and the number of messages for options and register drop from 34 to 2.

Is there an adjustment to shorewall to reduce interference on sip traffic?


local.lan
xxx.xxx.xxx.x/24

local.if1
IF1=enp6s18

ACCEPT net:$LAN $FW tcp 5060 - -   
ACCEPT net:$LAN $FW tcp 80 - - # HTTP
ACCEPT net:$LAN $FW tcp 443 - - # HTTPS
ACCEPT net:$LAN $FW tcp 22 - - # SSH
ACCEPT net:$LAN $FW udp 123 - - # NTP
ACCEPT net:$LAN $FW tcp 389 - - # LDAP
ACCEPT net:$LAN $FW udp 389 - - # LDAP
ACCEPT net:$LAN $FW udp 4569 - - # IAX2
ACCEPT net:$LAN $FW udp 5060 - - 4/min:5 # SIP
ACCEPT net:$LAN $FW udp 10000:20000 - -  # RTP
This is the rules file
ACCEPT net:$LAN $FW tcp 5060 - -   
ACCEPT net:$LAN $FW tcp 80 - - # HTTP
ACCEPT net:$LAN $FW tcp 443 - - # HTTPS
ACCEPT net:$LAN $FW tcp 22 - - # SSH
ACCEPT net:$LAN $FW udp 123 - - # NTP
ACCEPT net:$LAN $FW tcp 389 - - # LDAP
ACCEPT net:$LAN $FW udp 389 - - # LDAP
ACCEPT net:$LAN $FW udp 4569 - - # IAX2
ACCEPT net:$LAN $FW udp 5060 - - 4/min:5 # SIP
ACCEPT net:$LAN $FW udp 10000:20000 - -  # RTP

Hi S
Thank you for the reply. The strange thing is, if the call is put onhold or transferred by the extension the MOH plays. Just not as a replacement of ring tone.

So is the solution to create a moh-default folder?
Thanks

Hi there

Good question.   6.1 optionally allows different MOH files for each tenant.  You can load the individual tenant MOH files in the tenant edit panel.  The sound files for each tenant are saved in /usr/share/asterisk/moh-{tenant name} and a reference is generated in sark_moh.conf

As you know, in Asterisk the sound directories are abstracted in that they are defined in /etc/asterisk/musiconhold.conf and, in the Digium sample file, there is a [default] entry which points to the sample moh files in the directory /usr/share/asterisk/moh

It is also the case that Asterisk will ignore empty MOH directories.

The confusion arises due to Asterisk defining an MOH class "default" (in the sample musiconhold.conf) and SARK having a "default" tenant (so it also has a class "default" in sark_moh.conf).  However, as long as the SARK entry is an empty directory then it gets ignored and Asterisk uses the Digium supplied sample music.  If, on the other hand, you save a music file into moh-default then that will be used instead.

It is, however, confusing so thanks for the question and I hope this above helps.




 

I am a little confused to the outcome of below
musiconhold.conf
[default]
mode=files
directory=moh
.....
#include sark_moh.conf

but sark_moh.conf says
[default]
mode=files
directory=moh-default
moh-default is not in the asterisk directory set and "moh show files" does not look at it. The sark_moh.conf is overwritten by the workbench so it can not be edited.

Do we need moh-default which is in /etc/asterisk and not /usr/share/asterisk?

Thanks

Is a deb coming for bullseye?

Yes, they will always differ.   GitHub has what we are working on right now.  Packagecloud has what we regard as a current release.   So GitHub will always be ahead of packagecloud.

You can of course download a later version from GitHub and install it but it may not be what we would call a release.   It also may have bugs that we didn't fix yet.   

Packagecloud releases will tend to go in jumps.   The next packagecloud release may, as an example, be -30.   Whenever we get to a point in GitHub where we think we have a stable release then that's when we upload it to packagecloud and it becomes the current release.

Hope this helps.
 

Noticed different sail versions available on github & packagecloud:

github
sail_6.2.0-25+ubuntu18_all.deb

packagecloud
sail_6.2.0-19+ubuntu18_all.deb

I was under the impression that packagecloud will be the new repo for v6.2 based on the instructions here:
http://www.sailpbx.com/mediawiki/index.php/SARK_V6.2.0_install

Could you please clarify the situation?

Thanks Guys
The HPE (6.0.0-8) file seems to have fixed it. Worked straight away.