• Welcome to SAIL Community Supported PBX . Please login or sign up.
 
May 07, 2024, 06:04:56 PM

News:

SMF updated to 2.0


Sail source code

Started by giovanni.v, January 12, 2015, 11:41:30 AM

Previous topic - Next topic

giovanni.v

Hi all,
I'm working on an open source embedded pbx distristribution, while I was already planning/coding my asterisk configuration user interface I discovered that SAIL already meet most of my requirements/goals.

So I'd like to use it and contribute back to the development but unfortunately discovered that no public source repository exists and the only way to get the SAIL code is by unpacking the rpm/deb package.
Moreover sailhpe is only distributed in binary form despite the fact that the package documentation says it's GPL, I could do without it but involves a little more effort.

I will not put a link to the project site to avoid being accused of advertising.
Regars, Giovanni.

sysadmin

Hi

Sail-4.0.1 front-end source is available on GitHub.   Search for aelintra or sail.

This will give you access to all of the php & javascript browser code and to the sql layouts and generators.  With the exception of the extensions.conf generator (which calls the AGI), all of the other generators should work as-is for your project.

The AGI backend (which isn't required by the front-end - it is used only by Asterisk; is not yet available in anything but binary.   We're working on that but it may be a little while before we can release.   As an alternative we are also considering re-writing the C code into a PHP fastAGI back-end.

Good luck with your work and please feel free to contact us if you want to discuss further.

Kind Regards

S


giovanni.v

Quote from: sysadmin on January 12, 2015, 09:52:23 PM
Sail-4.0.1 front-end source is available on GitHub.   Search for aelintra or sail.

Already done before my first post but found only asha (https://github.com/aelintra/asha).

Quote
The AGI backend (which isn't required by the front-end - it is used only by Asterisk; is not yet available in anything but binary.

But the generated dialplan eavily use the AGI backend so I will be forced to rewrite most of the logic behind that. This is not a problem but also mean an fork with little chance to contribute back.

Quote
We're working on that but it may be a little while before we can release.   As an alternative we are also considering re-writing the C code into a PHP fastAGI back-end.

I think the agi binary was a good choice compared to the resources and memory footprint required by most language interpreter, this becomes very significant on embedded platforms. I'll try to do the same using LUA, may be a good compromise between resource and maintainability.

Thank you.

sysadmin

It's public now.

I thought that had already been done but obviously not.

You should be able to fork it now