SAIL Community Supported PBX

You would need to send me a screenshot of  the Asterisk entry for one of the phones.   Just go into the edit panel and take a shot of the asterisk entry.   In V6 we use a symbolic in the definition and a value in the database.   Earlier versions were hardcoded in the Asterisk definition and the password field in the DB was often empty.  Maybe this.

Here is how it should look under V6

type=peer
defaultuser=$desc
secret=$password
mailbox=404
host=dynamic
qualify=yes
context=internal
call-limit=3
callerid="$desc" <$ext>
canreinvite=no
pickupgroup=1
callgroup=1
subscribecontext=extensions
disallow=all
allow=alaw
allow=ulaw
nat=$nat
transport=$transport
encryption=$encryption

As you can see the secret stanza uses the symbolic $password.   The actual password should appear in the Password box in the left hand column.

There isn't really any dedicated support for DAHDI in V6.   The generators were not continued from V5 through lack of demand.  Most customers are either using pure SIP or SIP/ISDN gateways these days.   However, I think we can still get you to the picture show.   You can simply create a custom app to catch the DAHDI dialplan.  Something like _DAHDI/X.  should do it, that will catch any channel assignment and you can then  simply send it on to a regular DDI with a GoTo({myddinum},1).

Like this..


exten=>_DAHDI/X.,1,GoTo(mainmenu,{myddinum},1)


Create a DDI to catch it, doesn't even need to be a real DDI just something to anchor to.

That should get you home.

Sorry for the late reply to this.  We've been moving office in January and this got overlooked.  Upgrade from 5 to 6 is the same as upgrade from 4 to 5.   Take a backup of the 5 database, build the new box, restore the 5 database to the 6 machine and then run the reloader (see above).

However, because 6 uses a lot more jQuery than 5 you will need to clear your browser history before you attempt to login to 6 if it is on the same IP address as the 5 machine you just left.   Other than that, it should work fine.

You asked about S200.  The S200 will not get V6.   This is because we can't upgrade that platform to Debian 8/9.   There is a new 64 bit platform, called the SARK300, which will run V6 (and V7).    It currently runs Ubuntu 18 LTS, which is pretty much the equivalent of Debian 9.   The box is on beta test with a few customers at the moment and it will likely roll out in a few weeks.  The form factor is exactly the same as the S200 but it has faster cores, dual Gigabit ethernet, dual USB2 and a microSD slot.   It's a pretty cool little box.

Well, yes... and no.

There are in fact two timer panels in V6.   Recurring and Holidays.   Recurring are the old timers we've always had.   So, for example, Xmas recurs every 25th December and you would usually use a recurring timer to set it.   Holidays, on the other hand, are for non-recurring timers, or events which do not happen at the same time every year.   Examples of these would be Ramadan, Diwali, Easter and, of course, the Xmas office party!  These timers are "one shot", they don't recur.   For these you specify a year.   For recurring timers you don't.

Hope that all makes sense







   

This all seems to working OK now on Debian and Ubuntu.   Latest repo release is -47 at time of posting but -49 isn't far behind.  It's in testing now.

Thanks for letting us know.   It was caused by a snafu in the repo.   It's fixed now.   At the console run

apt-get update
apt-get install sail

It should be fine now.

For regular work you should install V6, the current release.   V7 is still very early in its life cycle and it is quite different under the covers so you should really only use it to play with for now.

Thanks again.

 

Just an update.   We created a sark buster deb package today and loaded it on a fresh buster install.   Aside from a few issues with buster itself, it all installed nicely and seems to be working.   This is a V6 system with the latest -47 release on it.  We did run into a few buster specific issues but nothing too dramatic.   In no particular order

buster favours nftables over iptables.   Because we use Shorewall we need iptables.  You can choose which you want with systemd as follows


update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy


We needed gnupg2 for our gpg key add to work.   Install with


apt install gnupg2


SSMTP won't install, they've dropped it from buster so we installed the default exim4-light


apt install default-mta


That's about it really.

I've updated the wiki to include notes for buster on the V6 install page

HA is being used less these days as people go to the cloud and use simpler tech like Route53 to do the failover.  However, we do have at least one customer running V5 on Deb9 with HA.   They've been in production for quite some time so yes you can go there.

Which release of 5 do you have please? 

Deb 10 testing will start shortly.   The biggest issue with 10 is the departure from iptables and the fact that shorewall will never be rewritten for nftables.   For now, we'll likely just enable iptables because the packet inspection we do doesn't look to be available in nftables yet. 

We are just about to test a new V6 point release with a fix in it for this.   Yes, we can link a file but the issue is the content.   It is different for wheezy, jessie and stretch.  Painful.   Moreover, we have to leave the file undisturbed because the jail.local file has to be available to the user to add her own changes.

I'll post once we've cut the release and done some testing 

We're in the process of putting out a series of short videos on V6.   They are listed below and we'll add to the list as we produce more.

SV6 first login - https://youtu.be/SlQMS6zr8Nc
SV6 Provisioning - https://youtu.be/i7gMyaUhaYw
SV6 Responsive Design principles - https://youtu.be/-PreASmdej4
SV6 Interactive Browser Console - https://youtu.be/oxH0OBrnWVU

We're in the process of putting out a series of short videos on V6.   They are listed below and we'll add to the list as we produce more.

SV6 first login - https://youtu.be/SlQMS6zr8Nc
SV6 Provisioning - https://youtu.be/i7gMyaUhaYw
SV6 Responsive Design principles - https://youtu.be/-PreASmdej4

Hi

Ubuntu18 is still very much an alpha install and it has not had major testing yet.  That's not an excuse it's just the way we have to allocate our scarce resources.   Most go into Debian and in particular Debian 9.   I have logged your issue and we will look at it as soon as we can.

Thank you for your input it is very valuable.   Please continue to give us input on Ubuntu18 if you are able.

Kind Regards 

Class of service works before anything else.   It is the first eval we do in the dialplan, before outbound routing ever takes place, so if you block all international calls in CoS then that's it I'm afraid.   The call will be killed right there.  CoS works on an extension basis, it's premise is that you can use it to stop certain extensions doing things or, sometimes stop ALL extensions from doing things (e.g. premium rate numbers).  But the point is it is extension based, quite the opposite of Routes which are dialplan based.

If you want to allow international outbound to just some countries then you can put them into your route, i.e.

_00353XXXX.   _0022XXXXX.   _0037XXXXXXX.

Don't include _00XXXXXXX. in your route.  If it isn't there then nothing can route on it.   This route above will ONLY allow international calls to the three country codes listed.

Hope this helps