My trials of installing FreePBX
- 
 I'm using this thread to document my progress of installing a FreePBX system in a Dev3 CentOS 6.5 at CloudatCost. You might find this thread boring as all get out - I will sorta talk to myself in this thread explaining my thought process and solutions, even if every other Linux admin knows them, I don't and writing it down will help me remember for next time. I'm following these directions. 
 http://wiki.freepbx.org/display/HTGS/Installing+FreePBX+12+on+CentOS+6.5The install went a lot smoother once people here told me I could just SSH with Putty into the box - ok that problems solved. The directions have a small mistake or rather omission. When you download and install FreePBX itself, they don't have to go to /usr/src before downloading and untarring the files. So after digging around for about 10 mins I realized my problem and redownloaded (probably could have copied, oh well) and untarred in the correct directory. The rest of the steps worked without an issue. I want to keep this more secure, so I moved on to reneabling IPTables and Fail2ban 
- 
 @Hubtech was installing Elastix with FreePBX on C@C not sure if he got it working. 
- 
 @thecreativeone91 said: @Hubtech was installing Elastix with FreePBX on C@C not sure if he got it working. F Linux. 
- 
 This post is deleted!
- 
 @Hubtech said: @thecreativeone91 said: @Hubtech was installing Elastix with FreePBX on C@C not sure if he got it working. F Linux. I take it you aren't liking linux haha. 
- 
 @thecreativeone91 said: @Hubtech was installing Elastix with FreePBX on C@C not sure if he got it working. He wanted Elastix 2.5 which is CentOS 5 only and not available on CloudatCost. They don't go back that old. 
- 
 @scottalanmiller said: @thecreativeone91 said: @Hubtech was installing Elastix with FreePBX on C@C not sure if he got it working. He wanted Elastix 2.5 which is CentOS 5 only and not available on CloudatCost. They don't go back that old. Ah, no he was trying Elastix 4.0 beta. 
- 
 hey this is Dash's thread. 
 back to dash's failings not mine!
- 
 Not really understanding what Fail2ban did I found this helpful guide. 
 http://lintut.com/easy-steps-to-install-fail2ban-on-centos-6-5-protect-sshftp-using-fail2ban/I re enabled IPTables (the original instructions have you disable them) and of course my website was no longer reachable. -A INPUT -m state --state NEW -p tcp --dport 80 -j ACCEPT 
 -A INPUT -m state --state NEW -p tcp --dport 443 -j ACCEPTare added to /etc/sysconfig/iptables. OK now I reach the website, but the homepage indicated that it wasn't right and directed me to 
 http://wiki.freepbx.org/display/F2/Webserver+OverridesSo I edited /etc/httpd/conf/httpd.conf 
 searched for "<Directory "/var/www/html">" and changed AllowOverride from None to All
 and restarted the httpd service.OK that's fixed. 
- 
 After logging into the web page I notice that asterisk isn't running, or at least not connecting. After some digging around I found out (more like remembered) I didn't disable SELinux as the original instructions stated, so asterisk wasn't working correctly. Disabling SELinux solved this. Now I'm presented with 
  Some searches have lead to a possible explanation that apache might not be running as the user asterisk or I have another permissions problem. 
- 
 OK three copies of retrieve_conf on the system. ./usr/src/freepbx/amp_conf/bin/retrieve_conf 
 ./var/lib/asterisk/sounds/freepbx/amp_conf/bin/retrieve_conf
 ./var/lib/asterisk/bin/retrieve_confthe first being the install archive 
 and the third probably being the only one I care about for now.Check the permissions 
 ls -l retrieve_conf
 [root@c1115759-27921 bin]# ls -l retrieve_conf
 -rwxrwxr-x. 1 asterisk asterisk 37356 Apr 6 17:55 retrieve_confThat looks OK. 
- 
 Try executing retrieve_conf 
 ./retrieve_conf
 [root@c1115759-27921 bin]# ./retrieve_conf
 hostname: Unknown host
 found language dir fr for directory, not installed on system, skipping
 Added to globals: ASTETCDIR = /etc/asterisk
 Added to globals: ASTMODDIR = /usr/lib/asterisk/modules
 Added to globals: ASTVARLIBDIR = /var/lib/asterisk
 Added to globals: ASTAGIDIR = /var/lib/asterisk/agi-bin
 Added to globals: ASTSPOOLDIR = /var/spool/asterisk
 Added to globals: ASTRUNDIR = /var/run/asterisk
 Added to globals: ASTLOGDIR = /var/log/asterisk
 Added to globals: CWINUSEBUSY = true
 Added to globals: AMPMGRUSER = admin
 Added to globals: AMPMGRPASS = amp111
 Added to globals: AMPDBENGINE = mysql
 Added to globals: AMPDBHOST = localhost
 Added to globals: AMPDBNAME = asterisk
 Added to globals: AMPDBUSER = asteriskuser
 Added to globals: AMPDBPASS = amp109
 Added to globals: VMX_CONTEXT = from-internal
 Added to globals: VMX_PRI = 1
 Added to globals: VMX_TIMEDEST_CONTEXT =
 Added to globals: VMX_TIMEDEST_EXT = dovm
 Added to globals: VMX_TIMEDEST_PRI = 1
 Added to globals: VMX_LOOPDEST_CONTEXT =
 Added to globals: VMX_LOOPDEST_EXT = dovm
 Added to globals: VMX_LOOPDEST_PRI = 1
 Added to globals: MIXMON_DIR =
 Added to globals: MIXMON_POST =
 Added to globals: DIAL_OPTIONS = Ttr
 Added to globals: TRUNK_OPTIONS = Tt
 Added to globals: TRUNK_RING_TIMER = 300
 Added to globals: MIXMON_FORMAT = wav
 Added to globals: REC_POLICY = caller
 Added to globals: RINGTIMER_DEFAULT = 15
 Added to globals: TRANSFER_CONTEXT = from-internal-xfer
 Please update your modules and reload Asterisk by browsing to your server.
- 
 Please update your modules and reload Asterisk by browsing to your server. OK time to update 
 yum updateUpdating: 
 krb5-devel x86_64 1.10.3-37.el6_6 updates 499 k
 krb5-libs x86_64 1.10.3-37.el6_6 updates 766 kthese don't 'look' to be related to asterisk or FreePBX ? 
- 
 @Dashrender said: Please update your modules and reload Asterisk by browsing to your server. OK time to update 
 yum updateUpdating: 
 krb5-devel x86_64 1.10.3-37.el6_6 updates 499 k
 krb5-libs x86_64 1.10.3-37.el6_6 updates 766 kthese don't 'look' to be related to asterisk or FreePBX ? Kerberos are security libraries. 
- 
 OK found how to update FreePBX, from the webpage Admin tab at top, Module Admin about 2/3 down, then click the button for it to search for updates, then Process them. 
- 
 OK weird - i'm still getting the same error as listed above, but what's even weirder is that the time hasn't changed. I've installed the two update from yum and there were 3 modules in FreePBX that needed updating, did that (also reinstalled CID - removed it earlier to solve the asterisk problem) Will the error report continue to show me errors even if they are cleared? Do I just have to click the Ignore this button? Also, under summary near the top of the page, Asterisk has a yellow triangle with an explanation mark in it, but when I hover over it, it says Asterisk has been up for less than 10 mins, and then lists how long it's actually been up - is this an issue? 
- 
 While I wait for a few answer about that I'm moving on. I've created a user with an extension - easy enough.... but when I try to connect a Zioper softphone to it using username = ext, password (created by FPBX - really long) Domain = IP of FPBX I won't connect - We are sorry, we are unable to connect to your PBX with the information you provided. 
- 
 Check the firewall. 
- 
 Use netstat -tulpn to see what is listening. 
- 
 [root@c1115759-27921 ~]# netstat -tulpn 
 Active Internet connections (only servers)
 Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1418/sshd
 tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 2548/asterisk
 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1683/sendmail
 tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1564/mysqld
 tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 2548/asterisk
 tcp 0 0 :::22 :::* LISTEN 1418/sshd
 tcp 0 0 :::80 :::* LISTEN 1733/httpd
 udp 0 0 0.0.0.0:5060 0.0.0.0:* 2548/asterisk
 udp 0 0 0.0.0.0:5061 0.0.0.0:* 2548/asterisk
 udp 0 0 0.0.0.0:4569 0.0.0.0:* 2548/asterisk
 udp 0 0 0.0.0.0:51326 0.0.0.0:* 2548/asteriskMy iptables *filter 
 :INPUT ACCEPT [0:0]
 :FORWARD ACCEPT [0:0]
 :OUTPUT ACCEPT [0:0]
 -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
 -A INPUT -m state --state NEW -p tcp --dport 80 -j ACCEPT
 -A INPUT -m state --state NEW -p tcp --dport 443 -j ACCEPT
 -A INPUT -p udp -m udp --dport 5060 -j ACCEPT
 -A INPUT -p udp -m udp --dport 4569 -j ACCEPT
 -A INPUT -p udp -m udp --dport 5036 -j ACCEPT
 -A INPUT -p udp -m udp --dport 10000:20000 -j ACCEPT
 -A INPUT -p icmp -j ACCEPT
 -A INPUT -i lo -j ACCEPT
 -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
 -A INPUT -j REJECT --reject-with icmp-host-prohibited
 -A FORWARD -j REJECT --reject-with icmp-host-prohibited
 COMMIT

