Under the Radar

PBX-in-a-Flash Dynamic UI v3.0

2008-06-30T16:05:00.000-07:00

PBX-in-a-Flash v1.2 (PBIAF) has arrived hearkening back to the more community focused & friendlier days of Asterisk@Home, and before the Fonality corporate takeover & questionable practices that have overshadowed the TrixBox community.

In celebration of getting back to the basics (and what a step-forward PBIAF has done in terms of easy updates!) we thought it high time we bring out a new version of DynamicUI to match! We think you'll like the improvements, our friends and clients did!

As before, no configuration or editing necessary, just drop into place and it does the rest. Additionally, it has been written to accommodate new additions and web services as PBIAF & 3rd-Party projects continue to evolve.

What's New:

Updated specifically for PBIAF v1.x!
Logo changes for PBIAF installations (due to Fonality trademark overkill no Trixbox or Asterisk@Home logos, all installs show the PBIAF logo only)
Updated user-interface ("metal" style)
Optional RSS support
Web 2.0 enabled & initial effects applied
Cross-browser (Win: IE6/7, FF2/3 -- OSX: Safari 2/3, FF2/3)
XHTML Strict compliant (other than a couple non-W3C CSS hacks for IE6/7!)
Skinnable interface (additional skins below!)
Customizable/dynamic buttons (easy to add your own if need be, edit "welcome/.htindex.cfg")
Optional UI Wrapper for calling apps (easier nav back)
Optional Reseller/End-user branding by editing "_branding.htm"
End-user & Admin menus can have different branding
Internationalization by editing the button definition file "/welcome/.htindex.cfg"
Better secured data files & password at the server
Default install has an end-user menu enabled (you can disable of course!)
Supports components up to PBIAF v1.x release (AAH v2.8 & TrixBox v1.0 should still work but are technically untested)

Installation:

Instructions from the linux command prompt on your Asterisk box:

1) (login of course)
2) cd /var/www/html
3) mv index.php index-old.php (keep a backup in case you want to revert!)
4) wget http://www.kennonsoft.org/projects/pbiaf/admin-ui-3.tgz
5) tar -xzf admin-ui-3.tgz
6) rm admin-ui-3.tgz
7) chmod 777 welcome/.htindex.dat
8) chmod 777 welcome/.htindex.cfg

Optionally Enable Sample Branding ...
9) cp _branding_sample.htm _branding.htm

Optionally Disable Branding ...
10) cp _branding_empty.htm _branding.htm

That's All Folks!

Otherwise, please see the Asterisk@Home Dynamic UI v2.0 article (click left side or scroll below) for all other usage and feature details!

Have fun, gang ...

Screenshots:

Administrative core function in special area at bottom. Also, custom end-user/reseller branding region at the bottom

RSS feed & wrapper feature easily customized

Wrapper feature makes for easier navigation back to the main menu

Additional Skins:

A "minimalistic" skin created by a PBIAF community user cjkeeme - click to download.

Echo-Free Combinations, Asterisk & Digium Hardware

2007-01-11T12:29:00.000-08:00

How do I get echo-free with Digium boards (a running list) ...

Something that has plagued almost everyone in the Asterisk, Asterisk @ Home & TrixBox communities has been getting a nice clean echo-free experience with Digium Boards on various hardware platforms!

To that end, we felt it maybe wise to at least share our immediate experience & working combinations and continue to augment this list as people choose to throw in their tips in the comments over time!

So what's *really* the scoop on echo & Digium boards anyway?

There are various schools of thought on this, some say it's the server platform hardware incompatibility at issue, some an issue of dedicated IRQ's and correct BIOS isolation, and still others a matter of correct manipulation of the Zaptel echo settings & selected echo algorithms.

As for ourselves, we have found empirically that although all of these can be at issue and all of these can help reduce or even remove the echo, there is a far simpler and more subtle issue at the root that doesn't require any of these manipulations & trouble --- a correct combination of Linux kernel version & Zaptel driver version.

What we've found so far ...

In every case without exception, we have found that picking the right Linux kernel build & corresponding Zaptel driver release removes the echo completely and perfectly (or near enough the stock echo canceller configuration removes the minor remaining difference in a matter of minutes automatically)! We have tried every one of the other prescribed methods with varying degrees of success & alot of headache in every case.

However, correctly selecting the correct kernel/Zaptel combination seems to work everytime with the stock Asterisk @ Home / Trixbox installations with an absolute minimum of fuss. Now granted, this doesn't always provide the latest software releases of either but we've found in most cases the typical installation rarely if ever falls prey to the issues that get fixed or added from release to release of either the kernel or Zaptel.

Proven / Known Working Combinations (by Hardware Platform)

Dell Poweredge Servers & Digium TDM400P cards
-- Tower: SC420 / SC430 / 800 / 830
-- Rackmount: 750 / 1650

-- CentOS Kernel Build 34.0.2
-- Zaptel Driver Version 1.2.6

(alternatively, we found CentOS Build 43.0.2 from TrixBox v1.2.2 and Zaptel v1.2.9.1 seemed to work as well, but have been unable to further duplicate this combo for testing due to kernel source complications in the various TrixBox releases -- which have reverted to 34.0.2 ultimately).

We welcome any community feedback & more interestingly echo-free combinations for various hardware platforms that folks have been able to consistently & successfully reproduce!

Have fun!

AAH/TrixBox CDR Billing Report v1.0

2006-11-20T10:32:00.000-08:00

CDR Billing/Invoicing for AAH/TrixBox...

We had a request that we'd seen bouncing around the AAH/TrixBox community for sometime, and that was a simple billing/invoice solution. Spent a few moments and put together a simple Microsoft Access query & report that generates statements by Account Code for a given Year, Month & Per Minute Rate!

Solved a friends problem & gave them a template to customize from as desired. Maybe it'll help some others out as well ... regardless, enjoy!

Add a MySql user for reporting purposes...

1) Log into the TrixBox web interface, and navigate to the phpMyAdmin screen.

2) Click "Privileges" near the bottom

3) Click "Add a new user" also near the bottom

4) For "Username" enter a name (e.g. reporting), for "Password" enter a password, and for the "Global Privileges" section at the bottom -- since I know very little about MySql security I chose "Check All" as it worked flawlessly!

5) Click "Go" in the lower right to save your new user

Configure ODBC on your Windows machine for access...

6) Download & run the MySql ODBC Driver setup (popup link: click here)

7) Once installed, click "Start -> Control Panel -> Performance & Maintenance -> Administrative Tools -> Data Sources (ODBC)"

8) You may choose whether you want a User, System or File DSN as desired, however for this example we will create a "User" DSN by clicking the "Add..." button to the right.

9) Scroll to the bottom of the list, and select "MySQL ODBC 3.51 Driver" then click "Finished"

10) When the dialog pops up asking for the database information fill in the following:
Data Source Name: TrixBox CDR
Description: Call Detail Reporting
Server: 192.168.0.10 (put your server domain or IP address here!)
User: reporting (or whatever username you created in phpMyAdmin previously)
Password: xxxxxxx (again whatever you entered before goes here)
Database: asteriskcdrdb

11) You can click "Test" if you like to make sure the connection is working

12) Click "Ok" to save and finish

13) Click "Ok" again to close the ODBC dialog as well

Let's get the report!

14) Download the Microsoft Access 2003 database ZIP file (popup link: click here)

15) Unzip the file to wherever you wish

16) Double-click to start the database (you may have to answer a couple dialogs about "unsafe expressions" and ultimately a security dialog to "open" the database -- please do so, just part of Microsoft's attempts to patch holes in their security)

Let's connect the database to your server...

17) Open the database & click "Tables" on the left of the window

18) Select the linked table called "cdr" & delete it (toolbar button above "X")

19) Right-click on the white area and from the menu select "Linked table..."

20) From the dialog click the dropdown at the bottom & scroll to the very end, select ODBC Databases(), and click OK

21) Your ODBC datasources list dialog appears, you may have to click the second tab "Machine Data Sources" where you will find the "TrixBox CDR" DSN we created earlier -- select it & hit OK

22) Another dialog appears with a list of tables from your TrixBox, it should only list "cdr" -- select it & hit OK

23) A last dialog will appear asking you to pick a unique key, click the "CallDate" and "src" fields (so they are blue/selected) & hit OK

24) Your Done! Ready to run a report! Just click "Reports" on the left and double-click "Monthly Billing" ... answer the 3 prompts & Voila!

The report uses a query (in the "Query" section) that will prompt you for a Rate, Year, and Month to generate billings for the given month by Account Code. Play around with it, and modify the report layout as you wish!

Again, not a comprehensive solution but a clean/simple fix to an easy problem. Have fun.

Trixbox v1.2.2 Quickie HOW-TO!

2006-10-10T18:35:00.000-07:00

A Working How-To - Updated 1/11/2007!
Current for trixbox-update v1.0.0.13

This short guide is simply a "how to" to side-step a couple of basic landmines in TrixBox v1.2.2 installation and FreePBX v2.1.1 (included in TrixBox) or FreePBX v2.1.3 to get the base system operational with a Digium card as we have become accustomed to with previous release of the old Asterisk@Home v2.x series.

Let's Get to It!

1) If upgrading from an older Asterisk@Home installation, run backups from AMP and manually download the compression, as well as backing up "/tftpboot" for you Cisco handset users, get your custom voice prompts, hold music, etc.

2) Install TrixBox v1.1, v1.2 or v1.2.2 from the ISO/CD

3) Login to the command prompt

Continue a usual installation...

4) Type, "netconfig" and change your IP as needed

5) Type, "help-trixbox" to get a list of commands you can use

6) Run the commands listed to change your passwords as desired

Update TrixBox!

7) Type, "trixbox-update.sh update" (it will download a newer version of itself)

8) Type, "trixbox-update.sh update" (again, to run the newly downloaded version)

9) Type, "Reboot" (when it is done it will prompt you to do this)

OPTION: The Trixbox update v1.0.0.13 supposedly forces the linux kernel back to a stable release (build 34 vs 42) & the Zaptel drivers match so should be fine. However, for those who might be having echo/detection/Zaptel issues still --- please do the following to remedy ...

(NOTE: On some web browsers the double dash before the word "force" below sometimes appears as one bigger dash, watch out!)

10) rpm -ivh --force http://vault.centos.org/4.3/updates/i386/RPMS/kernel-2.6.9-34.0.2.EL.i686.rpm (thanks again to Mito for the update on the URL change & deprecated source - 1/11/2007!)

10a) yum -y install kernel-devel (or "kernel-devel-smp" for hyperthreading CPU's and multi-processors)

Check that the spinlock.h bug is fixed for the older kernel, type the following six commands ...

10b) cd /usr/src/kernels/2.6.9-34.0.3.EL-i686/include/linux

10c) cp spinlock.h spinlock.h.orig

10d) nano spinlock.h

10e) {ctrl-w} rw_lock_t

10f) Change "rw_lock_t" to "rwlock_t"

10g) {ctrl-x} to exit and save changes

11) cd /usr/src

12) wget http://ftp.digium.com/pub/zaptel/releases/zaptel-1.2.11.tar.gz

13) tar -xzvf zaptel-1.2.11.tar.gz

14) mv zaptel-1.2.11 zaptel

15) cd zaptel

16) make clean

17) make linux26

18) make install

19) reboot (this will restart your machine, you will need to login again after)

20) genzaptelconf (if you have Digium cards, etc. you'll need to do this)

Trixbox v1.2.2 bugs, quick fix from the TrixBox creator!

21) yum clean all

22) yum –y update asterisk

23) rpm -i --force /var/trixbox_load/rpms/asterisk-sounds-1.2.1-1.noarch.rpm

24) rm -rf /tmp/*

25) reboot

OPTION: Simplify & Secure your email support for voicemail & fax deliveries. We remove "sendmail" and replace it with "postfix" essentially for a better TrixBox experience!

26) service sendmail stop

27) rpm -e --nodeps sendmail

28) yum -y install postfix

29) service postfix start

30) nano /etc/postfix/main.cf

31) Find the lines that begin "#relayhost = ....", and add a line there that says (without the first "#" character): relayhost = your.smtp.server.dns.or.ip.address (replace the silly text with your actual mail server DNS or IP address!)

32) ctrl-x, Y, (to save & exit)

33) service postfix reload

34) nano /etc/hosts

35) Find the following lines and insert your FQDN or DNS for your system where indicated by "my.asterisk.com" ...

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost
127.0.0.1 my.asterisk.com asterisk1.local

35a) WEB SERVER STOPS (Fix!): Additionally, some folks (limited) have experienced the web server stopping due to DNS resolution issues. The fix appears to be editing the first line above to include "asterisk1.local" at the end. Example:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost asterisk1.local
127.0.0.1 my.asterisk.com asterisk1.local

36) ctrl-x, Y, (to save & exit)

OPTION: Add HTTPS support if you think you may be accessing the web interface from the outside Internet...

37) Type, "yum -y install mod_ssl"

38) Type, "reboot"

Test the online web interface ...

39) With a browser go to your TrixBox IP address, then navigate to System Administration and eventually FreePBX

40) Click on the Tools section and Module Admin

41) Click on the "Connect to online repository..."

42) If it works, great! If it doesn't consider the following steps (43-46) ...

SONICWALL FIREWALL USERS: If you can't connect to the online module repository, then there is an issue with your firewall more than likely (since FreePBX moved their module repository to a more reliable server recently). In the case of SonicWall firewalls with more recent firmware, the following will solve your problem!!

43) Login to your SonicWall via web browser

44) Navigate your browser to, http://xxx.xxx.xxx.xxx/diag.html (insert your firewall IP address or DNS name in the xxx.xxx.xxx.xxx)

45) Scroll down & uncheck "Enforce Host Tag Search with for CFS"

46) Click "Apply" at the top of the page, and voila!

SONICWALL FIREWALL USERS: If you instend to use IAX2 for site to site trunking, or even to deploy IAXy remote analog extensions AND you are running a newer generation of Sonicwall Firewall firmware, you must make the following adjustment otherwise you will lose your connections repeatedly! TrixBox has IAX configured to timeout after 60 seconds, Sonicwall's now come with a UDP protocol timeout of 30 seconds -- oops! See below for the fix.

47) Login to your SonicWall via web browser

48) Click "Firewall -> Advanced"

49) Change "Default UDP Connection Timeout (seconds):" to a value greater than 60, say 65

OPTION: FreePBX v2.1.1 or v2.1.3? FreePBX's best stable version at the moment seem to be v2.1.1 that is already installed or v2.1.3 which the following steps will help you upgrade to. Everyone has a favorite, I'll leave it to you to pick yours based on experience!

50) cd /usr/src

51) svn co https://svn.sourceforge.net/svnroot/amportal/freepbx/tags/2.1.3 freepbx-2.1.3

52) cd freepbx-2.1.3

53) ./install_amp

Workaround for FreePBX v2.1.1 and v2.1.3 "direct to voicemail" flakey bug -- if you experience it! Examples include direct to voicemail dialing gives you a message saying that your extension is busy (not the destination), or an inability to direct dial to voicemail from the IVR or internal extension, etc.

54) With a browser go to your TrixBox IP address, then navigate to System Administration and eventually FreePBX

55) Click on the Setup section and General Settings

56) Change the "Extension prefix for dialing direct to voicemail:" from an "*" to anything else (we have found "9" very effective)!

Voila! Essentially you are done. For the uninitiated, I'd recommend following steps beginning with #42 in our earlier How-To for the quickest setup of FreePBX and your phone system (How-To Quick Link).

Of course you will still have to handle your handset configurations as needed. However, if you are migrating from an old AAH install to TrixBox and you backed up your handset configuration files (e.g. Cisco users need only copy/paste the "/tftpboot" directory between installations) you won't even have to touch that except to maybe reboot the handsets to ensure they properly register with the new Asterisk/TrixBox machine.

Good Luck & we would like to direct ALL HELP REQUESTS not directly related to these instructions to TrixBox.org Help Forums!!

TrixBox v1.0 Quickie HOW-TO!

2006-07-12T09:15:00.000-07:00

A Working How-To - Updated 9/27/2006!
Current for trixbox-update v1.0.0.8

TrixBox v1.0 was released 5/31/2006 & updated to v1.1.1 in August, 2006 for the review and testing of the Asterisk@Home community. As to be expected, Andrew has done an amazing job of making all our lives easier no matter what may crop up in TrixBox. However, as with all initial releases there is a growing list of issues to be addressed.

This short guide is simply a "how to" to side-step a couple of basic landmines in TrixBox v1.x installation and FreePBX v2.1.1 (included in TrixBox) to get the base system operational with a Digium card as we have become accustomed to with previous release of the old Asterisk@Home v2.x series.

Let's Get to It!

1) If upgrading from an older Asterisk@Home installation, run backups from AMP and manually download the compression, as well as backing up "/tftpboot" for you Cisco handset users, get your custom voice prompts, hold music, etc.

2) Install TrixBox v1.0 or v1.1 from the ISO/CD

3) Login to the command prompt

Workaround bug in CentOS that can cause echo with Digium/Zaptel hardware & causes an error in trixbox-update.sh ...

4) Type, "cd /usr/src/kernels/2.6.9-34.0.2.EL-i686/include/linux" (note the portion in the middle with the numbers may be different on your machine depending on what kind of CPU you have!)

5) Either edit your spinlock.h file by finding the line referencing "rw_lock_t" and changing it to "rwlock_t" (around line 500 in the file) or you can download a copy of the file already edited (albeit it may be older than you current install - beware!) ... wget http://www.kennonsoft.org/projects/trixbox/spinlock.h

6) cd /usr/src

Warning(s): Zaptel 1.2.8, 1.2.9 & 1.2.9.1 all seem to have a jitterbuffer launching issue that can lead to echo on Digium cards. v1.2.7 seems to be stable/proper.

7) wget http://ftp.digium.com/pub/zaptel/releases/zaptel-1.2.7.tar.gz

8) tar -zxvf zaptel-1.2.7.tar.gz

9) mv zaptel-1.2.7 zaptel

10) cd /usr/src/zaptel

11) make clean

11a) make linux26 (OPTIONAL step, only if echo persists if tried without it already!)

12) make install

13) modprobe wctdm

14) modprobe zaptel

15) genzaptelconf

Workaround bug in auto-detection of Digium hardware for reboots...

15) Type, "nano /etc/sysconfig/zaptel"

16) Uncomment the line that references your Digium board (e.g. remove the "#" at the "wctdm" line, also mentioned as "TDM400P") if not already uncommented!

17) Save changes & exit Nano

Continue a usual installation...

18) Type, "netconfig" and change your IP as needed

19) Type, "help-trixbox" to get a list of commands you can use

20) Run the commands listed to change your passwords as desired

21) Type, "setup-mail" if you wish to have email support for voicemail messages, etc.

Update TrixBox!

22) Type, "trixbox-update.sh update" (it will download a newer version of itself)

23) Type, "trixbox-update.sh update" (again, to run the newly downloaded version)

24) Type, "Reboot" (when it is done it will prompt you to do this)

Fix the MeetMe Conference bug that is still there as of trixbox-update v1.0.0.7 ...

25) mkdir /var/spool/asterisk/meetme

26) chown asterisk.asterisk /var/spool/asterisk/meetme

27) chmod 775 /var/spool/asterisk/meetme

Add HTTPS support if you think you may be accessing the web interface from the web...

28) Type, "yum -y install mod_ssl"

29) Type, "reboot"

Test the online web interface ...

30) With a browser go to your TrixBox IP address, then navigate to System Administration and eventually FreePBX

31) Click on the Tools section and Module Admin

32) Click on the "Connect to online repository..."

33) If it works, great! If it doesn't do the following steps (34-37) ...

If you can't connect to the online module repository, then there is an issue with your firewall more than likely (since FreePBX moved their module repository to a more reliable server recently). In the case of *** SonicWall *** firewalls with more recent firmware, the following will solve your problem!!

34) Login to your SonicWall via web browser

35) Navigate your browser to, http://xxx.xxx.xxx.xxx/diag.html (insert your firewall IP address or DNS name in the xxx.xxx.xxx.xxx)

36) Scroll down & uncheck "Enforce Host Tag Search with for CFS"

37) Click "Apply" at the top of the page, and voila!

OPTIONAL: Change default for "Call Waiting" on handsets/extensions...
By default FreePBX creates new extensions with "call waiting" disabled, meaning when you are on the phone a second call will get a busy message and get sent immediately to voicemail. If you wish the option for your handset to beep and display on your LCD the second inbound call giving you the option to answer it or ignore it, then you need to dial *70 on each handset -OR- change the default for new extensions created ...

38) Click, "System Administration" then "Config Edit"

39) Click, "/etc" at the top/middle then "amportal.conf"

40) Scroll down in the window until you find "ENABLECW=no", change it to "yes"

41) Click, "update" button at the bottom

FreePBX v2.1.1 initial config order of events to reduce confusion for the first timer ...

42) Open your web browser and point it to your TrixBox IP address

43) Click, "System Administration" then "FreePBX"

44) Click, "Tools" then "Module Admin"

45) Click, "Connect to online module repository" (gets list of latest modules from our temporary workaround file)

46a) For the full experience select everything except maybe Gabcast, Asterisk API, & VoicePulse (as you will have to have mode advanced needs to use these).

46b) For the streamlined experience select what you wish but be sure to include "core" as it is necessary, and we might recommend you choose "voicemail" as well otherwise you're callers/users are in for a surprise!

FreePBX v2.1.1 example setup to reduce confusion for the first timer (i.e. things appear/disappear based on whether they have been configured in the first place!)...

47) Click, "Setup" (get into the main web admin for FreePBX)

48) Click, "Trunks" (update & create your settings as needed, e.g. make sure you set "Max Channels" on your Zap/g0 trunk)

49) Click, "Outbound Routes" (get your dialplan set here & pointing at the correct trunks)

50) Click, "Extensions" (set them up & be sure after saving each to go back and update the "Mailbox" field on each to reference "...@default" rather than the incorrect "...@device" or your Message Waiting Indicators won't light up when voicemail is left!)

51) Click, "General Settings" (do what you wish here)

52) NOTE: If you haven't already, this is a good time to setup your handsets (e.g. for Cisco junkies, copy back or setup your TFTPBOOT folder) as the next steps involve recording prompts, etc.

53) Click, "System Recordings" (and record your Digital Receptionist, Queue, etc. prompts -- or copy backup recordings from your previous AAH install to the "/var/lib/asterisk/sounds/custom" folder)

54) Click, "Ring Groups" (and do what you need)

55) Click, "Queues" (and do what you need)

56) Click, "Digital Receptionist" (and setup your IVR prompts)

57) Click, "Time Conditions" (and create at least one if you need it)

58) Click, "Inbound Route" (and at least setup a catchall default, maybe pointing to your 'Time Condition' you created!)

59) Click, "On Hold Music" (and upload your files, or copy them by hand to the "/var/lib/asterisk/mohmp3" folder)

For those upgrading from an old Asterisk@Home v2.x installation...

60) Click, "Tools" then "Backup and Restore"

61) Create a backup job and run it once to create the disk folder (e.g. named 'Weekly' maybe but have it run "Now" then reset it after to "Weekly (on Sunday)")

62) Copy your old AAH backup file by hand to the "/var/lib/asterisk/backups/Weekly" folder, the final folder name being whatever you named your scheduled backup)

63) Click, "Restore from Backup" then "Weekly" (or whatever you called it)

64) Select your OLD backup from the list

65) When prompted DO NOT restore the "Restore Entire Backup Set" -- INSTEAD, restore just your users "Voicemail Files" and maybe "Call Detail Report" (to keep your call history and reports!)

That's it! Of course you will have to handle your handset configurations as needed. However, if you are migrating from an old AAH install to TrixBox and you backed up your handset configuration files (e.g. Cisco users need only copy/paste the "/tftpboot" directory between installations) you won't even have to touch that except to maybe reboot the handsets to ensure they properly register with the new Asterisk/TrixBox machine.

Good Luck & we would like to direct ALL HELP REQUESTS to TrixBox.org Help Forums!!

TrixBox Dynamic UI v2.1

2006-06-05T12:58:00.000-07:00

Asterisk@Home v2.8 and now TrixBox v1.0 have arrived, and we thought it high time we update things to auto-detect TrixBox v1.x! We think you'll like the improvements, our friends and clients did!

As before, no configuration or editing necessary, just drop into place and it does the rest. Additionally, it has been written to accomodate new additions and web services as TrixBox & 3rd-Party projects continue to evolve.

What's New:

TrixBox v1.0 support!

Logo changes for TrixBox installations

Forums change for TrixBox installations

System Management button directs to the TrixBox maintenance screen (then FreePBX from there) for TrixBox installations

Cleaner install, only PHP's in root (the rest in a 'welcome' directory)

Default install has an end-user menu enabled (you can disable of course!)

Supports components up to the AAH v2.8 & TrixBox v1.0 releases

Installation:

Instructions from the linux command prompt on your Asterisk box:

1) (login of course)
2) cd /var/www/html
3) mv index.php index-old.php (keep a backup in case you want to revert!)
4) wget http://www.kennonsoft.org/projects/trixbox/admin-ui-21.tgz
5) tar -xzf admin-ui-21.tgz
6) rm admin-ui-21.tgz
7) chmod 777 welcome/index.dat

That's All Folks!

Otherwise, please see the Asterisk@Home Dynamic UI v2.0 article (click left side or scroll below) for all other usage and feature details!

Have fun, gang ...

After TrixBox Updating, Menu Disappears!

After running "trixbox-update.sh update" you will find often that the old menu has returned. The correction for this is a very simple adjustment & you don't lose any of your previous Dynamic Menu settings!

1) (login of course)
2) cd /var/www/html
3) rm index-old.php (in case you have done this before!)
4) mv index.php index-old.php
5) wget http://www.kennonsoft.org/projects/trixbox/index.php

That's it! You're back in business.

Restoring the Original Menu (we can't imagine why?! )

We can't imagine why you would want to do this , however in the case where you need to here's what you do:

1) (login of course)
2) cd /var/www/html
3) rm index.php
4) mv index-old.php index.php

That's it! The original Trixbox menu is back.

Asterisk@Home Dynamic UI v2.0

2006-03-15T18:00:00.000-08:00

After a lot of kind (and always welcome!) words, AAH v2.7 release, and a couple requests, we took it upon ourselves to try and clean up a few more things. We think you'll like the improvements, our friends and clients did!

As before, no configuration or editing necessary, just drop into place and it does the rest. Additionally, it has been written to accomodate new additions and web services as Asterisk@Home & 3rd-Party projects continue to evolve.

Admin Screenshots:
AAH v1.5 | AAH v2.7 | w/Webmin | w/All Apps | End-User Menu Config

End-User Screenshots:
AAH v1.5 | AAH v2.7 | AAH v2.7 w/All | Admin Password

What's New:

A2Billing and A2Billing Customer added!

Customizable optional End-user Menu added!

Simple/Poor-Man's (optional) Password protection of Full Admin Menu added!

Supports components up to the AAH v2.7 release

Installation:

Instructions from the linux command prompt on your Asterisk box:

1) (login of course)
2) cd /var/www/html
3) wget http://www.kennonsoft.org/projects/asterisk/admin-ui-2.tar
4) tar -xvf admin-ui-2.tar
5) rm index.html
6) rm admin-ui-2.tar
7) chmod 777 index.dat

End-User Menu Instructions:

By default the menu behaves as usual, a single administrative front-end with every available option enabled that you have installed. However, by clicking the "Menu Config" button you can enable an alternate "End-User Menu" and select which components (if they exist in your system) will display.

Additionally if you specify an admin password, end-users attempting to click the "Administration..." link off of the bottom of their menu will not have direct access without logging in first. Of course if you leave it blank, you can easily toggle back & forth without the initial password entry!

Anyhow, remember the list box is a multiselect, so use that CTRL key and mouse clicks to enable/disable menu choices.

Lastly, to return to the single full Admin menu only, simply disable the End-User Menu by unchecking it -- that's it!

Have fun, gang ...

Advanced Options:

Accomodate Custom Installations -- You can adjust the Admin UI simply by editing a single array of values in "index.php" at the very top with a text editor. Specifically, you can change folder path's or HTTP port's as applicable to match your installation in the event it us other than a default installation.

Create your own buttons -- Download our Photoshop/ImageReady template to make it easy & consistent (Download File)

Asterisk@Home Dynamic UI v1.0

2006-02-22T11:30:00.000-08:00

After an initial release of an updated main web interface entry page for the administration of the Asterisk@Home distribution, we have further improved it to support v1.x - v2.5 installations -- automatically!

No configuration or editing necessary, just drop into place and it does the rest. Additionally, it has been written to accomodate new additions and web services as Asterisk@Home & 3rd-Party projects continue to evolve.

Screenshots:
AAH v1.5 | AAH v2.5 | w/Webmin | w/All Apps

What's New:

Dynamically detects each component and enables buttons automatically based on your installation

Adapts to v1.x installations by updating the URL for accessing Voicemail recordings accordingly

Supports components up to the v2.5 release

Supports Webmin installations with appropriate icon/link

Supports "NerdVittles.com/Mundy.org" Asteridex and Asterisk Reminders applications with appropriate icons/links

2/22/2006 NEW! Added SSL support for Webmin detection under HTTPS

Installation:

Instructions from the linux command prompt on your Asterisk box:

1) (login of course)
2) cd /var/www/html
3) wget http://www.kennonsoft.org/projects/asterisk/admin-ui.tar
4) tar -xvf admin-ui.tar
5) rm index.html
6) rm admin-ui.tar

That's it, have fun!

Advanced Options:

Permanently disable buttons of unwanted components -- Either rename the directory of the unwanted component (base path: /var/www/html/), or edit the index.php file carefully if you're up to the challenge!

2/22/06 New! Create your own buttons -- Download our Photoshop/ImageReady template to make it easy & consistent (Download File)

2/24/06 New! 3Ware RAID Manager Support -- Download & decompress (or: wget http://www.kennonsoft.org/projects/asterisk/admin-ui-3ware.tar) our modified file & icon to add auto-detect support for the 3Ware RAID Web Manager (Download File)