SAIL Community Supported PBX

Thanks for the info.

https://github.com/aelintra/sail

I have just created a page on the wiki to list common issues and fixes in SAIL / Asterisk / Endpoints. The community can now expand on it for all to benefit.

Thanks. It certainly helps.

We currently have either CLID or DiD based inward routing.
Inclusion of a new CLID+DiD based inward routing would be welcome.

Thanks for the info:

Quote.... see the full name by hovering your curser over the cell you wish to inspect.  It will appear in a speech bubble above the cell.

and future inclusion of the 1 sec delay:

Quote.... a one second delay is no big deal so I'll look at taking it into the mainline.

Removal of OpenVZ from Debian has forced many a data center relying on OpenVZ to stay put at Wheezy. Default inclusion of PHP7 in Ubuntu 16.04 has had the same effect on upgradation.

Is there any GitHub repo you have created for SARK/SAIL code? Atleast the web interface / php portion? If not, is it okay to start one? I'd rather you, being the founding dev of SARK, start it and we all fork it.

The display of the user in Endpoints => Extensions menu shows upto 7 characters user but if longer, it truncates it to 5 characters and a period. This can be extended to display upto 12 characters by editing /opt/sark/php/sarkextension/view.php line 206:

if ( strlen($row['desc']) > 7 ) {

to

if ( strlen($row['desc']) > 12 ) {


A similar truncation is done for display of device name at the 8th character in line 215 of the same file.

For OpenVZ like shared containers, we need a sleep(1) before returning from the routine that stops asterisk.

All changes needed are attached in this post.

A better solution would be to make the support.htm a generic page for end users to edit as required. Please do not remove it in any future point release.

A generic set of files to be placed in the /opt/sark/www folder to overwrite them is attached to this post. Please compare them with your existing counterparts before overwriting them with this or any edited versions.

The SAIL_Feature_Codes.pdf can be prepared from the PBX Wiki and placed in the /opt/sark/www folder.

There are 2 service providers who expect us to send them calls differently:

Provider 1:
Local Calls - [36-9]XXXXXXX
International Calls - 0ZXXXXXXXXX.
Current Mask: :0 065:

Provider 2:
Local Calls - 65[36-9]XXXXXXX
International Calls - ZXXXXXXXXX.
Current Mask: None

We need to give internal users the ability to call:
Local Calls - [36-9]XXXXXXX (Like Provider 1) - Currently 65[36-9]XXXXXXX is used
International Calls - ZXXXXXXXXX. (Like Provider 2)

What recommended masks are needed in the

• Trunk's Transformation Mask
• Outbound Routing DialPlan

When we login into the SARK v4.1 (possibly in other versions as well) a blank page appears.
The /opt/sark/www/support.htm still has the ProVue info.
To be generic, remove all proprietary info from the said file and modify the navigation.php and index.html in the /opt/sark/www folder to show the support.htm page on login.

Line 17 of /opt/sark/www/index.html:
<frame  name="main">
should become:
<frame  src="support.htm" name="main">

Line 20 of /opt/sark/www/navigation.php:

<ul class="menu collapsible">

should become:

<ul class="menu collapsible">
<li>
<a href="#">Home</a>
<ul class="acitem" style="display: none;">
<li>
<a target="main" href="./support.htm">Support</a>
</li>
</ul>
</li>


Edit /opt/sark/www/support.htm as needed, placing a link to the SARK Feature codes page in it.