We are happy to present the latest script which incorporates both Asterisks versions. The script does ask what Asterisk version you wish to install of course.

This script was tested on Debian Lenny 5.0x.

Enjoy and as usual your feedback is greatly appreciated.

Thanks

Intuit Team.

Script found here (right click save as): http://210.5.42.12/downloads/asterisk/asterisk-1-install

We are publishing the latest Asterisk install that will setup basically Asterisk 1.6.20 and 1.4.28 respectively. It is designed to be a single command line execution where you key in your MySQL password when you run the script and it will install everything in about 30 minutes with 200kbps download speed.

It has multiple tools via cli and web that we feel makes the whole installation simply sufficient to manage, monitor and administer your Asterisk box. It also enables SSL where possible.

All components of FreePBX works with default passwords, so you must change that after.

These scripts only works with Debian 5 fresh bare metal install. Do read the headers of the script file before doing anything.

1.4 – http://nagios.intuitinnovations.com/downloads/asterisk/asterisk1.4.2-A-install (MD5: 54af3cb0583bca1d059ae6bcbd65fadb)

1.6 – http://nagios.intuitinnovations.com/downloads/asterisk/v1.6/asterisk1.6.2-A-install (MD5: bfbd86acd7712ef61cc006528bb7b3da)

Have fun and please do give us your feedback and if you’ve improvised the script, please do share it back with us so we can share it back with the world.

Sharing is caring.

Merry Christmas and Happy New Year from all of us at

If you run FreePBX and Asterisk 1.6 and tried to execute “amportal stop” the script might throw an exception and treat that Asterisk is not running and attempts to restart or some weird stuff keep happening.

The issue is caused by the freepbx_engine script which amportal calls that has a depreciated command for stopping Asterisk called “stop gracefully” when it’s actually “core stop gracefully”. The script has two lines one of each, the second one, which is “stop gracefully”.

So, we found a quick workaround. Seem to make the execution of the amportal script to behave correctly. But before that, just so you check that;

1) This is an Asterisk 1.6 with FreePBX 2.5.x or higher systems which are on Debian Lenny (4) – It may happen on different OS/distros.

2) FreePBX permissions/configurations are all set properly in amportal.conf

3) Asterisk run directory /var/run/asterisk/ exist and that the ctl and pid are properly configured to use this directory (in amportal.conf and/or in freepbx_engine) and that the permission to read and write that directory is give to the user which runs asterisk (normally the asterisk user).

This is what i use to get when i “amportal stop” or “amportal restart”. We get a “Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)” command thrown at us and sometimes, it becomes worse and may cause Asterisk to crash.

This above sometimes goes on a crazy loop until i kill –9 the asterisk process properly.

This is how you fix this.

nano /var/lib/asterisk/bin/freepbx_engine

Locate (ctrl-w) the command “stop gracefully”. Comment out that whole line from the beginning and it should look something like this;

Notice the # before /usr/sbin/asterisk –rx “stop gracefully” well, that basically disables that line. Safe and do amportal “whatever” and see it will no longer throw and exception.

Now we are all happy campers.

No more crashes or weird error messages.

Just wanted to quickly write this tip.

When accessing FreePBX recordings or in any case, playing a QuickTime embedded video via a browser, the indication bar shows all black making it impossible to see the progress bar and what not.

This is somehow a bug in Windows 7 and/or Apple Quicktime. I’ve made a support incident on Apple’s website, waiting for a response.

The quick workaround around this is to run your browser in compatibility mode such as Vista SP1, 2..

I personally don’t care, but some customers may just raise an eyebrow. So those who want this “fix” do this below.

How to? Go to your Windows Start button, look for the affected browser/link (must be a link not the exe itself), right click, properties and select compatibility, enable the compatibility by selecting Vista SP1,2…then reload the browser. You should see it now.

Cheers and have a good weekend.