Topic: SAIL v3.1.1-22

[apmuthu]

The recent release of SME8FA18V311-22.iso has the latest SAIL v3.1.1-22.
The said SAIL version has not yet been released as an independent rpm.

Can it be installed over the existing -16/-17/-20?

[apmuthu]

On a fresh install using SME8FA18V311-22.iso, although the file sarkstart.db is present in the sail 3.1.1-22 rpm, once the /opt/sark/db/sark.db gets created, the /opt/sark/db/sarkstart.db gets deleted.

Is this by design and if so to what end?

The unused files in the sail 3.1.1-22 rpm :

• /opt/sark/db/DBSQL
• /opt/sark/db/lineIOdump
• /opt/sark/db/startDBSQL

have not been removed as yet, although the sail v4.0.0-39 onwards it stands removed.
The multiple Thumbs.db files have not been removed in both branches of sail as yet.

The unused undolog table in sark.db still exists.

4 new fields in the globals table in sark.db have been introduced - IVRKEYWAIT, IVRDIGITWAIT, LOCALAREA and LOCALDLEN - where are they set from and what do they signify?

Working on a new install wiki page for this iso.

[SARK devs]

Thanks ap.muthu

I will sort those issues this week.

Start db isn't really deleted.   The fresh install moves it to sark.db.

Best

S

[apmuthu]

Any reason why it was "moved" instead of "copied"?
If the sark.db got corrupted, where would it now copy/move another from?

Have created the SARK Feature Codes Wiki Page - please update it to reflect current usage.

[SARK devs]

If the sark.db got corrupted, where would it now copy/move another from?

Either from a backup, snapshot or re-install.   The system will never use sarkstart again.  It can never know when it could safely do so or when it should do so. 

Best

S

[SARK devs]

Hi apmuthu
re your questions on the 4 new variables.  They are briefly described in the rpm changelog.  You can retrieve the rpm changelog for the currently installed version by doing

Code: [Select]

rpm -q --changelog sail | less
As an example, here is a portion of the changelog from 4.0.0-35 to 4.0.0-42. It's a bit terse but it does at least give some description of each change that was made.

Code: [Select]

* Sun Feb 3 2013 Aelintra <coco@aelintra.com> -r1940 4.0.0-42
- fixes to responder commit and to srkhelper FOP generation
* Sat Feb 2 2013 Aelintra <coco@aelintra.com> -r1939 4.0.0-41
- fixes for S200 console; mods to service sark run, srkhelper, responder and snap
* Sat Feb 2 2013 Aelintra <coco@aelintra.com> -r1938 4.0.0-40
- fixed render problem for stats package in IE8
* Fri Feb 01 2013 Aelintra <coco@aelintra.com> -r1936 4.0.0.39
- fixed bugs in 3 routines
- operator/list.php - missing require
- sarktimer/javascript.js - edit layout bug
- sarktrunk/javascript.js - regexp bug in transform
* Mon Jan 28 2013 Aelintra <coco@aelintra.com> -r1933 4.0.0.37
- fixed bug in extension add
- added r1 prefix handler to allow short code dialling over SIP and IAX - 2 new variables
- LOCALAREA - area code prefix to be prepended
- LOCALDLEN - short dial length (used to decide when to add LOCALAREA)
* Wed Jan 23 2013 Aelintra <coco@aelintra.com> -r1931 4.0.0.36
- Included extalert in the dont_strip_tags list in srkHelper buildTuple
* Mon Jan 21 2013 Aelintra <coco@aelintra.com> -r1930 4.0.0.35
- added variable timers for IVR
- IVRKEYWAIT - default 6 seconds.  How long the IVR will wait for a keypress
- IVRDIGITWAIT - default 6000 millisecnds.  How long the IVR will wait between digits.]
It is still not absolutely clear from this above what the LOCALAREA and LOCALDLEN variables do.   They are an aid to local short-dialling over a SIP trunk but, as yet, far from complete (hence the r1 designation).   All it does is prepend whatever is in LOCALAREA to the dialled number, but only if the dialled number is LOCALDLEN digits in length.   In the UK, local subscriber numbers can be 5,6 or 7 digits in length.  Area codes are 4 5 or 6 digits in length.  It just means we can dial a short local number when dealing with a SIP trunk and SAIL will prepend the correct area code before it does the dial.

Hope this helps.

S       

[apmuthu]

In a fresh install, the fields IVRKEYWAIT and IVRDIGITWAIT in the globals table are blank and do not possess the default values stated in the changelog which mentions both seconds and milliseconds - which should we use?

Should the fields have the defaults set in the sqlite table definition itself or should we just rely on the defaults provided by the sarkhpe binary?

The changelog for sail v3.1.1 does not show the other two variables LOCALAREA and LOCALDLEN:

Code: [Select]

# rpm -q --changelog sail | less
* Sat Feb 02 2013 Aelintra <coco@aelintra.com> -r1938 3.1.1.22
- fixed render problem for stats package in IE8

* Mon Jan 21 2013 Aelintra <coco@aelintra.com> -r1930 3.1.1.21
- added variable timers for IVR
- IVRKEYWAIT - default 6 seconds.  How long the IVR will wait for a keypress
- IVRDIGITWAIT - default 6000 millisecnds.  How long the IVR will wait between digits.

* Wed Jan 16 2013 Aelintra <coco@aelintra.com> -r1925 3.1.1.20
- cleaned up sqlite access in sarkinternal and SarkSubs

* Tue Dec 18 2012 Aelintra <coco@aelintra.com> -r1918 3.1.1.19
- update amacs for new snoms

* Mon Oct 29 2012 Aelintra <coco@aelintra.com> -r1891 3.1.1.17
- fix to hostname retrieve (mainly for S500 no-dns problem)

* Wed Oct 17 2012 Aelintra <coco@aelintra.com> -r1871 3.1.1.16
- fix to dynamic call queueing
- change to hangup/busy logic for Ast 1.8

.....


[SARK devs]

Hi

IVRKEYWAIT is specified in seconds (default 6).
IVRDIGITWAIT is specified in milliseconds (default 6000)
don't blame me for the inconsistency, blame the Digium  API, .

The general rule we follow in SARK is that the HPE will impose a default value if the variable is empty.

Best

S

[apmuthu]

Please review the Wiki at:
http://www.sailpbx.com/mediawiki/index.php/SAIL_Defaults
and fill in the details or paste the info here to populate the wiki accordingly.