Difference between revisions of "Installation"

From FusionPBX
Jump to: navigation, search
(Installing onto an existing FreeSWITCH system)
(Installing onto an existing FreeSWITCH system)
Line 75: Line 75:
 
* the autoload_config files are not renamed but extensions, inbound routes, ivr menu, outbound routes, and dialplan entries uses the v_ file
 
* the autoload_config files are not renamed but extensions, inbound routes, ivr menu, outbound routes, and dialplan entries uses the v_ file
  
  prefix and the gui ignores files without that prefix allowing you to have custom settings anywhere you want in the config.  Fusionpbx  
+
prefix and the gui ignores files without that prefix allowing you to have custom settings anywhere you want in the config.  Fusionpbx  
  
  doesn't import the custom settings  
+
doesn't import the custom settings  
 
* the difference between freeswitch default dialplan is that the feature codes are prefixed with a * to free up numbers for user defined things  
 
* the difference between freeswitch default dialplan is that the feature codes are prefixed with a * to free up numbers for user defined things  
  
  and allow extension numbers to be whatever you want between 2-7 digits
+
and allow extension numbers to be whatever you want between 2-7 digits
 
* great care has been made to let people access to controlling freeswitch at any level desired with fusionpbx with as little or as much as you want.   
 
* great care has been made to let people access to controlling freeswitch at any level desired with fusionpbx with as little or as much as you want.   
  
The gui has been designed to make it easier to use freeswitch but also have had smart people in mind as well
+
The gui has been designed to make it easier to use freeswitch but also have had smart people in mind as well
  
 
===Testing:===
 
===Testing:===

Revision as of 15:30, 25 January 2015

Internet Connection VoIP test

If you are going to be using SIP connections for incoming/outgoing calls it is helpful to know if your internet connection
is going to be able to handle it. Speed tests like this one http://myspeed.visualware.com/voip/ are helpful in checking your connection.

Installation

FusionPBX is multi-platform and can be installed on many operating systems.

If you are wanting to install FusionPBXon an existing FreeSWITCH system then you should choose the relevant platform below and follow the appropriate

instructions (before starting this, do note the warnings further down this page about the implications for your existing FreeSWITCH installation).

If you are just wanting to test FusionPBX simply, then the best place to start is one of the ISO installs as it will get you up and running quickly

(note that the draw back with ISO installs is that they normally start by erasing your harddrive so you need an unused machine to try them on OR you

can try them in a virtual machine such as VirtualBox or VMware).

Below are instructions that have been provided for a few of the operating systems if yours is not listed the ones that exist should hint
towards the general install process.

Scripted Installs

  • Easy FusionPBX A scripted install that currently supports Debian Squeeze, Ubuntu 10.04LTS, and Ubuntu 12.04LTS.

Manual Install

Mac

Windows

Raspberry Pi

pfSense 2.1

Other Installs:

[If you need to run the FusionPBX install.php again simply remove the includes/config.php file then browse to the index.php

page on the root of the website - if you want to reinitialize the database, drop the entire DB, not just the tables]

General Tips

Installing onto an existing FreeSWITCH system

Installing FusionPBX onto an existing install of FreeSWITCH will reset all your files in the FreeSWITCH conf folder to the FusionPBX defaults.

Although FusionPBX tries to make a backup of your config, located in the folder conf.orig, it is still a good idea to back them up.

Comments from IRC conversation about this:

  • the main thing overwritten during the install would be freeswitch's default dialplan
  • in fusionpbx I prefix most files with a v_ that way fusionpbx indicates to you the majority of the files it creates
  • the autoload_config files are not renamed but extensions, inbound routes, ivr menu, outbound routes, and dialplan entries uses the v_ file

prefix and the gui ignores files without that prefix allowing you to have custom settings anywhere you want in the config. Fusionpbx

doesn't import the custom settings

  • the difference between freeswitch default dialplan is that the feature codes are prefixed with a * to free up numbers for user defined things

and allow extension numbers to be whatever you want between 2-7 digits

  • great care has been made to let people access to controlling freeswitch at any level desired with fusionpbx with as little or as much as you want.

The gui has been designed to make it easier to use freeswitch but also have had smart people in mind as well

Testing:

Editing the config safely

Guide to Editing Config Files Safely. FusionPBX guide for editing the config files manually. Got a handle on the graphical interface and want to dig deeper into the power of FreeSWITCH? This guide describes what files are written by FusionPBX and should help indicate what files can be edited without losing changes.

If your menus don't show

Go to http://domain_or_ip/core/menu/menu_list.php and press Restore Default. That should fix it.

Links