Topic: Fixed extension length in SAIL

[madadam]

Hi there,

I installed and had a play with SAIL and was impressed with the system. It has struck a good balance, better than most other GUI based implementations of Asterisk.

However I was dismayed to discover that I could only have 4 digit extension numbers. My organisation is based on 3 digit extensions.

Is there anyway to force SAIL to accept 3 digit extensions or any plans to remove this restriction in future versions?

Cheers,

adam

[SARK devs]

Hello Adam,

SAIL does use fixed length 4 digit extensions, however, there is a simple solution to your probem using Aliases.  Aliases are NOT fixed length.  So, let's say, for example, that your 3-digit extensions start at 200 (many do).  You can start Sail at (for example)  5200.  Once you have defined your extensions as four digits, the last three will now mirror your originals (200 will be 5200, 201 will be 5201 etc).  Now, in Globals, set "Auto create alias digits" to 3.  Next, go to the Aliases panel and click "Auto Create Aliases".  Sail will automatically generate and link 3 digit aliases to all of your 4 digit extensions.

That's it.  Your users can now use their old 3-digit numbers just as before.  They can also use the underlying 4 digit numbers if they wish. Also, because SAIL regards Aliases as virtual extensions, you can do all of your switching and grouping referring to the three digit aliases rather than the 4 digit extensions.

Kind Regards

S

[madadam]

Hi S!

Just re-installing SAIL, couldn't get 2.2.1 to work so am dropping back to 2.1.15.

Thats a great fix, simple yet quite powerful - could have a number of applications. Thanks for that! I will have a play with 2.1.15 and see how well it works with my application. I have been so used to editing the various .conf files myself and writing my own little macros etc, so it will be interesting if this framework is flexible enough for my application.

Cheers,

adam

[SARK devs]

We wouldn't advise going to 2.1.15.  It was an experimental alpha release purely for the mISDN support development and 1.4 testing.  It is now obsolete.  As such, it is functionally quite a long way behind 2.1.14/1.2 and 2.2.1/1.4 (the main-line products).

If you let us know what problems you had with 2.,2.1, then maybe we can help.  Alternatively, you should back off to 2.1.14/1.2 which is the current stable release leg.

Kind Regards

S