Topic: V4 Beta available

[SARK devs]

Hello

sail-4.0.0-beta is available to download as self-installing iso.  It has a lot of new features and is considerably faster than V3.  The main differences are in the way the web interface works (although the layout is much the same as it was) and in the architecture of the HPE.

You can read about the main differences here

http://www.sailpbx.com/mediawiki/index.php/SARK_V4.0.0

You can download it here

http://www.sailpbx.com/iso/SME8/sail-4.0.0/

It will happily install as a VM so you can spin it up on your favourite  virtualizer.  If you have the available resource then please install it and let us have your feedback.

Kind Regards

S

[waqasbj]

Can i upgrade  my sail version from V3 to V4 ?

[Stefano]

Can i upgrade  my sail version from V3 to V4 ?

V4 is a BETA version.. if you are using V3 in production, you should NOT do it..

[SARK devs]

Hi

Stefano is absolutely correct; this is a beta and should not be installed on a live system.  You can, if you wish and at your own risk, upgrade a test V3 system by installing the 4.0 rpms which you will find here

http://sailpbx.com/sail/sail-4.0-testing

Kind Regards

S
   

[groutley]

Happy New Year S !!
  I have installed the ISO and upgraded sark to the latest .16 level.
I am yet to configure and play properly,  but one minor initial observation is when pointing Chrome Browser to the https://server.ip.address:8443
The Browser Tab has "SARK Server V3.1" on it  yet Globals definitely says "Release #: 4.0.0-16"

[SARK devs]

Thank you for this

The bug is fixed in -31 which will be available for download shortly#

Kind Regards

s

[apmuthu]

SAIL v4.0.0-33 is out.

[groutley]

I notice sail-4.0.0-34 http://sailpbx.com/sail/sail-4.0-testing/rpms/sail-4.0.0-34.noarch.rpm
is available,  however it has a dependency of smesailenv-4.0.0-10 which is not available for download.

[SARK devs]

HI Gordon

My bad

It's there now

S

[apmuthu]

The recommendation that SAIL must first be installed and then the smesailenv rpm - does that still hold good?

What about publicising the smesailenvast18 rpm as well - is it necessary for SAIL 4?

[SARK devs]

The recommendation that SAIL must first be installed and then the smesailenv rpm - does that still hold good?

Good question.  Answer is no, smesailenv should be installed first.   Usually, when I am building a test unit I install them together with

Code: [Select]

rpm -Uvh sail... smesailenv...

What about publicising the smesailenvast18 rpm as well - is it necessary for SAIL 4?

All it does is set the asterisk delimiter in globals to a comma, Digium changed the delimiter from pipe (|) to comma(,) in 1.8.  You can use it, if you are running 1.8, or set the value manually, doesn't matter which.  It's in the repo because we know ahead of time which asterisk we are running.  V3/V4 will also run with 1.4 so the variable has to be changeable.  Don't run with Asterisk 1.6 because it's nasty.

Best

S

[apmuthu]

CSS Bugfix for SAIL v4.0.0-34

Lines 257-259 in /opt/sark/www/sark-common-css/sark.css are listed below. Line 258 in it needs closing comment characters:

Code: [Select]

/*  width: 700px; */
/*  height: 358px;
/*  background: #cccccc; */


[SARK devs]

thanks

I've updated svn

Kind Regards

S

[groutley]

Hi again..
  playing around with 4.0.0-34 I have a problem with defining a Trunk Transformation mask.
For one Trunk I have a fairly complex Transformation mask, and while I restored the configuration from my v3.2 sail to this V4 sail
it did put the transformation mask in as expected,  but when I went to modify the trunk, I am unable to save my change as it complains about..

Mask can only contain 0-9#*+: and space characters

yet my transformation mask (as was working in sail 3.2 and prior) is within those rules.
I find that as soon as I put a 'space' after the first mask definition I get the error and inability to save.

[SARK devs]

It's a little bug in the javascript Gordon.

load the file /opt/sark/php/sarktrunk/javascript.js into your favourite editor

At or around line 7 find

Code: [Select]

return this.optional(element) || /^[0-9#*+:]+$/i.test(value);
replace it with

Code: [Select]

return this.optional(element) || /^[0-9#*+: ]+$/i.test(value);
save it away and job done. 

Thanks for your input - I've fixed this in svn and it will be good in the next release.

Best

S