Topic: SAIL-2.4.1

[SARK devs]

Hi

SAIL-2.4.1.1 is up on the server...

http://sarkpbx.com/sail/sail-2.4.1/

This is a BIG release with soft panels, TT Help and new CSS throughout.  There will be bugs so you should not deploy it into production, however we'd love you to try it and give us your feedback.

Install as you would for the 2.3 releases.     Do NOT install with Zaptel Asterisk, 2.4 is DAHDI only (Asterisk 1.4.23 or later).

We'll put some tips and howtos for the new stuff up onto the wiki shortly but for now you can just go ahead and use it.


Kind Regards

S

[apmuthu]

Upgraded to v2.4.1-2 from v2.3.1-20 with the following instructions:

Starting Folder

Code: [Select]

cd ~
Perl Patch for v2.4.x version (one time only for entering into this version)

Code: [Select]

wget http://www.sarkpbx.com/sail/sail-2.4.1/perl-File-ReadBackwards-1.04-1.2.el4.rf.noarch.rpm
yum localinstall -y --enablerepo=base perl-File-ReadBackwards-1.04-1.2.el4.rf.noarch.rpm
SAIL upgrade to v2.4.1-2

Code: [Select]

wget http://www.sarkpbx.com/sail/sail-2.4.1/sail-2.4.1-2.noarch.rpm
yum localinstall -y --enablerepo=base sail-2.4.1-2.noarch.rpm
signal-event post-upgrade; signal-event reboot
Now commit for all variables to be populated into the install correctly and for the operator panel to show the actual extensions. Login to the server-manager after the reboot and under Global Settings:

Code: [Select]

Commit
A screenshot of the resultant Global Settings page is shown below:

[SARK devs]

Thanks


That looks encouraging

Best

S

[apmuthu]

Please note that in this version, there is no menu entry for Carriers (see menu in screenshot above). The entry should have been a link to http://domain.com/server-manager//cgi-bin/sarkcarrier . The link, however, does not work even if used independantly of the menu.

The file /etc/e-smith/web/functions/sarkcarrier is missing in this version.
If we copy the file from the previous version and set the file permission to 750 as the others, it still does not work as there is no link entry /etc/e-smith/web/panels/manager/cgi-bin/sarkcarrier as well!

How do we go back to the previous version?

[apmuthu]

RANT: This board does not have any file attachment capability.
RANT: SAIL does not have any SVM / CVS to link to files.

The /etc/e-smith/web/functions/sarkcarrier file from SAIL v2.3.2-19 works. The following should fix the issue till a new version rolls out.

Code: [Select]

cd /etc/e-smith/web/functions
wget http://www.chrishonline.com/files/sarkcarrier
chown root:admin sarkcarrier
chmod 4750 sarkcarrier
cd /etc/e-smith/web/panels/manager/cgi-bin
ln -s ../../../functions/sarkcarrier sarkcarrier


[SARK devs]

Hi apmuthu

The Carrier panel was deliberately removed in 2.4 because it is redundant.

Previous releases of the carrier code will NOT work correctly with 2.4.  Mixing and matching Perl source files from different releases will, at best, execute incorrectly, at worst it will corrupt the SAIL database.  We really would urge you to retract your advice and your download before it causes damage to someone's PBX.

We did explain that 2.4 is NOT a production release.  If the removal of the carriers panel is causing a problem then please explain why and we'll attempt to address the issue.

In the meantime you can freely regress sail with

rpm -e  sail

Simply reinstall whichever 2.3 version you wish to use.  Assuming your database isn't damaged then it will backport transparently to any of the 2.3 releases.


Kind Regards

S

[apmuthu]

Previous releases of the carrier code will NOT work correctly with 2.4.  Mixing and matching Perl source files from different releases will, at best, execute incorrectly, at worst it will corrupt the SAIL database.  We really would urge you to retract your advice and your download before it causes damage to someone's PBX.

Let me assure you that it has not caused any damage so far to my PBX's DB while using the v2.3.2-19's sarkcarrier file in v2.4.1-2. There has been no change in this file atleast from v2.2.4 onwards till the last presence in v2.3.2-19. The release statement for v2.4.1 did not list the removal of this functionality.

If the removal of the carriers panel is causing a problem then please explain why and we'll attempt to address the issue.

The Add/Modify (and maybe the list panel as well) Panels for Trunklines menu entry still has the Carrier form field and the template for a carrier is useful when populating parameters specific for each carrier. So is the IP Devices Menu entry that helps both auto configs and parameter templating. In fact it is this facility that actually attracted me to SAIL in the first place, even though many entries' parameters are the same.

[SARK devs]

The release statement for v2.4.1 did not list the removal of this functionality.

  I'm afraid it did... the release information is, as always, in the rpm changelog.

The Add/Modify  (and maybe the list panel as well) Panels for Trunklines menu entry still has the Carrier form field...

There seems to be a little confusion here, so allow me to summarize...
Carriers panel has been removed, the concept of carrier templates has not; there will continue to be general carrier templates but we no longer wish to maintain an endless list of carrier names, each with the same, or very similar, SIP requirements.

Kind Regards

S



   

[apmuthu]

the release information is, as always, in the rpm changelog

It would be nice to have the CHANGELOG available outside the rpm as well.

Carriers panel has been removed, the concept of carrier templates has not

How do we add new Carrier Template if the Carriers Panel has been removed?

I needed a Carrier Template to use a Singaporean SIP Service Provider's Trunk and after adding it to the previous SAIL version, and subsequently upgrading to SAIL v2.4.1-2, I find the following entry in the /home/e-smith/db/selintra file:

Code: [Select]

Aglow=Carrier|carrier|Aglow|carriertype|VOIP|desc|Aglow|host|sip.aglow.sg|md5encrypt||register||sipiaxpeer|type=peer\nhost=\nqualify=3000\ncanreinvite=no\nusername=\nfromuser=\nsecret=\n\n\nallow=g723\nallow=ilbc\n\nallow=speex\ninsecure=port,invite|sipiaxuser|type=user\nhost=\nfromuser=\nqualify=no\ncanreinvite=no\ncontext=mainmenu\ninsecure=port,invite|technology|SIP|zzeor|EOR
In case the Carriers Panel is removed, where should I put in this entry so that the file /home/e-smith/db/selintra will get populated with the requisite entry so as to be available when creating a Trunk?

It will be of interest to know that the file /home/e-smith/db/navigation/navigation.en and the default language file navigation.en-us in the same folder besides all the other language files have an entry in Line 32:

Code: [Select]

sarkcarrier=panel|Description|Carriers|DescriptionWeight|4843|Heading|Telephony|HeadingWeight|4000

[SARK devs]

We seem to be revisiting the same thing here.  One more time, let me try to explain...

I needed a Carrier Template to use a Singaporean SIP Service Provider's Trunk and after adding it to the previous SAIL version, and subsequently upgrading to SAIL v2.4.1-2, I find the following entry in the /home/e-smith/db/selintra  file:

Our point is that you can simply create a GeneralSIP trunk and name it however you like.  It is not necessary to create a special carrier entry for your Singaporean SIP carrier (or any other carrier for that matter), the GeneralSIP template will suffice.  There are literally thousands of carriers across the Globe.  It makes no sense to create carriier-specific templates for each and every one. Carriers come and go, their IP addresses change etc etc.  It is simply beyond our ability to manage, it is unnecessary and it detracts from the real work of enhancing SARK/SAIL. 

I find the following entry in the /home/e-smith/db/selintra  file:
Code: [Select]
Aglow=Carrier|carrier|Aglow|carriertype|VOIP|desc|Aglow|host|sip.aglow.sg|md5encrypt||register||sipiaxpeer|type=peer\nhost=\nqualify=3000\ncanreinvite=no\nuser

That is normal.  SAIL upgrades are, as far as possible, non-destructive of user-supplied data.  What you had you keep... we won't delete it. 

Finally, with reference to the sarkcarrier nav panel entry; it should probably have been deleted by the 2.4 rpm, but it isn't doing any harm so perhaps in the next point release.

Kind Regards

S

[apmuthu]

In being prepared for removal of the Carriers Panel, will the carriers template format be the same so that existing entries can be ported to a new installation with a future version of SAIL in the file /home/e-smith/db/selintra?

Other than in the /home/e-smith/db/selintra file, where else (any DB or other template file) should this record for the carrier be stored in a new install that does not sport the Carriers Panel?

Actually, a Wiki Page for Carriers Template Entries is better a small list of Carriers that exemplify common entries be left in place along with the carriers Panel - is the middle ground between an endless list of carriers and none at all!

[SARK devs]

Actually, a Wiki Page for Carriers Template Entries is better a small list of Carriers that exemplify common entries be left in place along with the carriers Panel - is the middle ground between an endless list of carriers and none at all!

Good input - we'll put this on the list of things to add.

Kind Regards

S