Trixbox v1.2.2 Quickie HOW-TO!
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,
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,
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!!
posted by Kennon Software at 6:35 PM | 11 comments
First thanks for both:
the guide and the superbe UI [i do not thanks for the other stuff because i had't try it and i want you know that my thanks are filled with sincerity :) ]
just a little question:
Is your guide usable for i 586 cpu?
Cheer
liku
posted by 
on 10/22/2006 3:45 PM
the guide and the superbe UI [i do not thanks for the other stuff because i had't try it and i want you know that my thanks are filled with sincerity :) ]
just a little question:
Is your guide usable for i 586 cpu?
Cheer
liku
The sincerity & thanks are always appreciated. Probably the only reason we do it! So thank you as well.
As for your question, they should work, however there is a difference in the Asterisk code to enable i586 that does require a recompile. Here is a thread of some folks talking about it (in case it helps) ...
http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=5217&forum=1&viewmode=flat&order=ASC&start=10
posted by 
Kennon Software on 10/23/2006 8:20 AM
As for your question, they should work, however there is a difference in the Asterisk code to enable i586 that does require a recompile. Here is a thread of some folks talking about it (in case it helps) ...
http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=5217&forum=1&viewmode=flat&order=ASC&start=10
Kennon Softwarethanks...
but i'm part of those "some folks" ;) =) i already tried it, and that doesent'do any change.. tonight i 'm trying another way.. ;)
posted by on 10/23/2006 2:31 PM
but i'm part of those "some folks" ;) =) i already tried it, and that doesent'do any change.. tonight i 'm trying another way.. ;)
Note that the link to the kernel in step 10 is now invalid (centos has depreciated the 4.3 version, and the .34 kernel). The new link to the kernel is http://vault.centos.org/4.3/updates/i386/RPMS/kernel-2.6.9-34.0.2.EL.i686.rpm
Mito
posted by on 11/29/2006 7:01 AM
Mito
Hi, very interresting stuff and good work.
Do you plan to support Trixbox V2.x in the near futur?
Thank you very much.
Daniel G. sys eng
www.biss-integration.com
posted by on 1/10/2007 9:00 PM
Do you plan to support Trixbox V2.x in the near futur?
Thank you very much.
Daniel G. sys eng
www.biss-integration.com
Mito - thanks, will update the article!
Daniel - Yes, we intend to put out an upgraded v3.0 that will be more customizable and support TrixBox v2.0 (hopefully provide a nice, faster replacement!).
ksDevGuy
posted by Kennon Software on 1/11/2007 12:23 PM
Daniel - Yes, we intend to put out an upgraded v3.0 that will be more customizable and support TrixBox v2.0 (hopefully provide a nice, faster replacement!).
ksDevGuy
Kennon SoftwareDevGuy, I don't want to put you on the spot, but can you give a general time-frame on when you think the support for Trixbox v2.0 will be available? What y'all have done so far is awesome. Thank you for your work.
Alvin
posted by A & S Technology Solutions, LLC on 1/15/2007 10:00 AM
Alvin
A & S Technology Solutions, LLCCan someone post instructions to remove this software Trixbox Dynamic I like the original trixbox stuff better (sorry)
posted by on 10/18/2007 1:58 PM
Do you have any recommendations for the Sonicwall TZ and QoS settings (relating to IAX2 trunks)
posted by 
razzarphenix on 7/01/2008 7:49 PM
razzarphenixWe would recommend at a minimum that on the QoS tab for the Wan->LAN access rule for your PBX you set an "explicit" map to the "Voice" mapping. This will ensure your voice traffic takes priority on your bandwidth usage whether it's 1 call or several.
posted by Kennon Software on 7/02/2008 10:09 AM
Kennon Software
Thanks a lot!