Other

This install procedure was tested using the Redhat Enterprise Linux distribution known as CentOS.

Software used:

CentOS v5.7 or CentOS v6.2
SugarCRM 6.3 Community Edition

This install guide was tested using the Redhat Enterprise Linux v5 distribution known as CentOS . 

Most of the install procedures for OpenSIPS assume Debian.  I prefer working with RHEL which is the reason for this install procedure.  This guide should work on Debian with some minor modifications but I haven't tried.

This guide will show how to install A2Billing on a Redhat Enterprise Linux based system.  It is assumed you already have Linux and Asterisk and FreePBX installed using a procedure similar to this one.  We do not cover the installation of the callback daemon.

These are my notes on how I replace TFTP with FTP for Aastra SIP phone configuration files on a Redhat Enterprise Linux server.  With the TFTP port exposed to the internet and no IP restrictions for remote phone configuration the directory is wide open. This makes it easy for someone to obtain extension passwords.

This guide is a reference for myself on how to create a RedHat Enterprise Linux v6 template for OpenVZ.  I am publishing it in case others find it useful.  There are other ways and variations on how one can go about this.  The method I will present here is the way I do it.

In this case I used the recompiled from source distribution known as Scientific Linux.  This guide should work equally well for any distribution including Redhat, CentOS etc.  It also works for v5 with a few minor changes or omissions which should be obvious.

Bluebox was formerly known as FreePBX v3.  It has now been spun off into it's own project.  This version of FreePBX supports Freeswitch in addition to Asterisk.

Bluebox is still a work in progress. We felt it was far enough along to create an install guide for those who want to dip their toes in and try out FreeSwitch at the same time.  The Bluebox portion of this guide can be used in conjunction with the Asterisk install portion of one of our other guides although we have not tested the combination.

External SIP or in other words SIP through firewalls and routers or more accurately SIP traversal through Network Address Translation (NAT) is arguably one of if not the most common problem people face.  SIP is notorious for this.  This little article is my attempt to provide a simple no nonsense method of finding and fixing these problems.  Ideally before they ever happen.  To keep it simple I will assume everything on the PBX itself is configured correctly. 

Includes every detail in the form of step by step instructions from bare metal to a running VoIP PBX in about 2 hours.  Because it does not require MySql or Apache, Asterisk GUI v2.x is a good alternative to FreePBX for someone looking for a less resource intensive install, possibly on a flash drive and/or embedded appliance hardware with limited CPU/RAM.  The whole install including source files takes up about 1.2Gigs of drive space and uses about 100MB of RAM while idle.  It could probably be reduced to 1Gig of drive space or less with very little effort.  Assuming you

Here are a few advanced topics covering some things that can be done to any FreePBX or strictly Asterisk distribution.  These would be things one might be interested in doing beyond the standard Linux-Asterisk-Freepbx installation.

This is a general overview of some of the more common mile high mistakes people make when doing an open source VoIP PBX project.  I won't be going into details about hardware dimensioning or software configuration.  I will just be providing a general overview of some of the system level common sense mistakes people make in terms of a typical consultant/client type of project.