Vous êtes sur la page 1sur 38

PBX in a Flash

Digitally signed by PBX in a Flash DN: cn=PBX in a Flash, c=US, o=PBX in a Flash, ou=Development, email=none Reason: I am the author of this document Date: 2008.04.23 15:44:33 -04'00'

1
Volume

PBX IN A FLASH VERSION 1.2

Thomas A. King

PBX in a Flash User Guide

PBX in a Flash v1.2 User Guide

Thomas A. King All Rights Reserved 2008 pbxinaflash@gmail.com

T able of Contents

V E R S I O N

1 . 2

U S E R

M A N U A L

1
Section

Installing PBX in a Flash


"Even in the darkest corners of despair there are glimmers of light we call truth. But what if it is a light to which the rest of the world is blind?" TVOC1963

W
Overview

elcome! This document will describe the configuration and installation PBX in a Flash. I have tested this on Lab, Production, and VMware machines with great success. Does this mean it is absolutely safe? Not in your life! No warranties express or implied at all! But I use it day to day in mission critical applications. Note this manual is a work in progress so if you find any errors please let me know.

PBX in a Flash version 1.2 is based on Centos 5.1, Asterisk 1.4 or Asterisk 1.6 BETA, FreePbx 2.4, and LAMP, all rolled into a very stable ISO. When the ISO is burned to a Cdrom and then booted on your machine of choice it will install a rock solid world class version of Asterisk. The ISO does not need frequent updating as we have chosen to compile the software on the fly as needed. Later there will be scripts available to manage your updates either automatically or manually. One thing you wont find is bloat! We have heard that bloat is simply extra space used by programs but we beg to differ. Many installations like to install the kitchen sink which does tend to slow the machine down significantly and use up extra hard drive space. If you want to install a crm product and we have written a script for it you simply download the script and run it. No muss no fuss! We feel our minimalist approach with the ability to add as much or as little as you want it superior. This manual was developed using PBX in a Flash version 1.2 running on Intel P4 based computers with a minimum of 2 gigabytes of RAM and a PATA hard drive. There were no SATA or Raid controllers present. Use of AMD based systems, older systems; systems with Raid, SCSI, or SATA controllers were not tested.

V E R S I O N

1 . 2

U S E R

M A N U A L

Preparing for Installation

lthough the installation of PBX in a Flash may appear technically challenging, this manual will take you through the entire installation and some of the configuration process in an easily followed step-by-step manner. Technospeak and jargon have been kept to a minimum but it is assumed that the user knows the basics of computer operation. Please contact PBX in a Flash on our support forums if you are having problems. Appendix A has full instructions on how to contact us in our support forums. Please read this guide in its entirety before starting the installation. Otherwise you may encounter difficulties. In several places during the installation, you may be asked for information that you may need to contact your Network Administrator about. These places are clearly marked in this guide. System Requirements The minimum recommended system requirements to install and run PBX in a Flash are given in the table below. Please ensure that the computer system on which PBX in a Flash is being installed meets or exceeds these requirements. PBX in a Flash will run in a lot less hardware! You may notice performance issues and other odd problems with lesser hardware.
DESCRIPTION Operating System Processor Memory Hard Drive Space Motherboard CD-ROM Drive FXO/FXS Card CD-ROM Drive Mouse PBX in a Flash 1.x Centos 5.x This is installed with our ISO Pentium 4 minimum or equivalent AMD system ** 64 bit processors now supported Minimum 1.0 gb 2.0 gb recommended * Minimum 80gb 7200 rpm 10,000 rpm recommend Server class for production For example Supermicro Any speed Digium or equivalent. Any speed Any type

** There seems to be driver support issues with some AMD systems. This is a Centos 5.x problem and not PIAF. Also PIAF will run on other processors but your may take a performance hit. * This is a recommended minimum. PIAF will run with a lot less ram and processor power but be prepared for performance issues. The general rule of thumb is the more extensions you have the more ram and processor power you need. Sometimes dramatically more.

V E R S I O N

1 . 2

U S E R

M A N U A L

Other Requirements There are a number of other minimum requirements to get up and running with a usable system. This is a general list for most installs. Working high speed internet connection Soft or Hard phone Working local network. Functional Overview PBX in a Flash Version 1.2 provides some dramatic changes over versions 1.0 and 1.1. I will briefly outline some of the new features below: Two different ISOs Centos 32 bit based and Centos 64 bit based Asterisk 1.4 source updated to very latest Multiple install options for Asterisk 1.4 o Install using Logical Volume Management o Install using ext3 partitioning o Install using sata-raid (You need the correct hardware for this!) o Install automatically with no user intervention o Install Centos from the internet Same ISO also supports the install of Asterisk 1.6 BETA Multiple install options for Asterisk 1.6 BETA o Install using Logical Volume Management (not recommended) o Install using ext3 partitioning (recommended) o Install using sata-raid (You need the correct hardware for this!) Ability to do redundant downloads of pbx load files in case some sites are down Ability to perform a local install of the pbx load files. *This feature only available to PBX in a Flash resellers/partners* Error checking of downloaded files to ensure transmission errors did not occur Added Painfully Detailed logging to install process. Now the install log is available to you in the /root directory. Most installed files are now compiled as opposed to installing binaries. This helps to provide a cleaner most custom install for your particular hardware. This also allows you to obtain technical support from Digium, in the *UNLIKELY* event, you need it. All source files for these programs are also installed in the appropriate directories to facilitate future user self compilation if required. Further details are available in the changelog once PBX in a Flash Version 1.2 has been installed

V E R S I O N

1 . 2

U S E R

M A N U A L

Choosing the correct PBX in a Flash The correct choice of which ISO and what version of asterisk to install is of critical importance. The guidelines below may help you to make this decision. Please note these are the opinion of the author and your choices need to be based in your own experience, hardware, and installation circumstance. The only guarantee offered with the use of this software is that it will take up space on your hard drive and that is it! 32 bit versus 64 bit The first choice is to decide what hardware you want to install PBX in a Flash Version 1.2 on to. Currently most production servers in use with our software are running on 32 bit hardware. With the availability of 64 bit/multicore processors it was decided to add 64 bit support for the operating system. The 64 bit Centos 5.1 Operating System runs quite well on most 64bit hardware with the exception of some bleeding edge stuff that has come out in the last few months. That being said there is very little anecdotal evidence about the stability and long term use of PBX in a Flash under the Centos 64bit Operating System. Currently all major functions seem to work *very* well under the 64bit OS with noticeable improvements in transcoding and several other key areas. We are currently running PBX in a Flash on a 64 bit based production server and it works flawlessly. The 32 bit hardware platform is well proven with lots of anecdotal evidence to support the stability and long term use of PBX in a Flash under Centos 32bit Operating System. For the moment I recommend you use the 32 bit version of PBX in a Flash for a rock solid production environment. Once a few more systems using the 64 bit version of PBX in a Flash come on line I feel confident that this recommendation will change. Remember that the operating system is the framework that Asterisk uses to do useful work and asterisk seems to work just fine under either 32 bit or 64 bit operating systems Asterisk 1.4 or Asterisk 1.6 BETA Now for the really exciting part of PBX in a Flash Version 1.2! Each of the ISOs, 32 bit and 64 bit, offer you the ability to install either asterisk 1.4 for production or Asterisk 1.6 BETA for experimentation. This feature was added to allow more people to test out the latest offering from Digium and to minimize the number of installation disks that are released in a year. We are hoping to release new ISOs only every 6 12 months so you dont have to keep downloading ISOs and burning a new CD whenever a new feature comes out. This is also better for the environment as you are throwing away less CDs into the landfills. While it may seem insignificant every little bit helps!

V E R S I O N

1 . 2

U S E R

M A N U A L

Asterisk 1.4 or Asterisk 1.6 BETA continued Asterisk 1.4 is recommended as the standard for production class servers. It has a very good track record with very few unresolved bugs. It is what the author uses on his client machines (more than 36 systems at the moment) and has had no problems at all with these installations. Thus if you are putting a machine up for someone else I recommend you stick to Asterisk 1.4 only! Asterisk 1.6 BETA is very much a work in progress with one or two features that just do not work yet. For example Flite/Festival/Cepestral is broken at the moment. This is a real show stopper for some production systems. Asterisk 1.6 beta is recommended for experimentation and test situations only. I run it as my personal PBX off of a 16 gb Compact Flash Card on a low power C7 processor motherboard under 32 bit and so far it works just great. This however is not recommended for beginners or the faint at heart! Have a look at the table below to decide which choice to use. Initial boot choices Boot Option ks ksalt ks-sataraid ksnet ksauto Description This will install PBX in a Flash Asterisk 1.4 based using LVM (logical volume management) My personal preference is to NOT use this choice. All of my systems use ext3 formatting instead. This will install PBX in a Flash Asterisk 1.4 based using ext3 formatting. This is my personal preference. This will install PBX in a Flash Asterisk 1.4 based using dual sata drive in a software based raid configuration. You need a motherboard or controller that supports this and 2 sata drives PBX in a Flash Asterisk 1.4 based using LVM (logical volume management) It is the same as ks except all of the centos files are pulled from the internet. This will install PBX in a Flash Asterisk 1.4 based using ext3 formatting. There is no user intervention required other than typing the ksauto at the first prompt of the ISO default password is passworm This will install PBX in a Flash Asterisk 1.6 BETA based using LVM (logical volume management) My personal preference is to NOT use this choice. All of my systems use ext3 formatting instead. This will install PBX in a Flash Asterisk 1.6 BETA based using ext3 formatting. This is my personal preference. This will install PBX in a Flash Asterisk 1.6 BETA based using dual sata drive in a software based raid configuration. You need a motherboard or controller that supports this and 2 sata drives

ks16

ks16alt ks16-sataraid

V E R S I O N

1 . 2

U S E R

M A N U A L

Installation

nitially you will have to decide if you want to install PBX in a Flash to a real computer or a vmware virtual one. Either way will work but this document will concentrate on installing PBX in a Flash onto a real as opposed to virtual computer. Once you have downloaded PBX in a Flash Version 1.2 ISO, either the 32 bit or the 64 bit, from www.pbxinaflash.net please burn it to a cdrom. Put the cdrom into the computer you want to install PBX in a Flash Version 1.2 to and reboot the system. WARNING THE PROCESS OF INSTALLING PBX IN A FLASH VERSION 1.2 WILL DELETE ALL PARTITIONS ON ALL HARD DRIVES ON THE TARGET COMPUTER BE WARNED! 1. Upon booting you will be presented with the following screen

For most installs simply tap the ENTER key to continue. If you have chosen something other than the default install please enter the option no and then tap the ENTER key. If you dont see this screen when the system boots you may have to change the boot device in your bios. This is custom to your computer so you will have to refer to the owners manual for further instructions. 2. Now you will see Selinux process loading the bootstrap to continue with the install process similar to the screen below

V E R S I O N

1 . 2

U S E R

M A N U A L

3. You will now be presented with a screen to choose your keyboard. To navigate in this screen use the up and down arrows until the red cursor is over the keyboard type you want. Then press Tab then press ENTER to continue

4. After several moments the Xwindow based graphical user install will start. (IF YOU CHOSE THE DEFAULT INSTALL!) The rest of the instructions refer to the standard install. There is not difference between the 32 bit and the 64 bit versions on these screens. You must ensure you have a mouse hooked up to the computer and you have the internet plugged into the machine.

V E R S I O N

1 . 2

U S E R

M A N U A L

5. You must change the pull down option from Use free space on selected drives and create default layout to Remove all partitions on selected drives and create default layout. If you are a Linux guru you can experiment with the advanced storage configuration however that is another manual!

Navigate the mouse pointer until it is hovering over the Next button and single left click the mouse. 6. A Warning window will pop up. This is normal and you need to navigate the mouse pointer over the Yes button and single left click the mouse.

7. The next screen you will be shown is the choose a time zone. On this screen you click the box immediately under the map and to the left and choose your time zone. Notice that the System clock uses UTC is unchecked and this is appropriate for most installations.
8

V E R S I O N

1 . 2

U S E R

M A N U A L

Navigate the mouse pointer until it is hovering over the Next button and single left click the mouse. 8. This screen is where you will enter the password for user root. You must enter is twice before you can continue. I have included some instructions on choosing a good password in APPENDIX TWO

Navigate the mouse pointer until it is hovering over the Next button and single left click the mouse 9. Now the install will proceed through a few steps. You should see something similar to the screens below.

V E R S I O N

1 . 2

U S E R

M A N U A L

10. Pay close attention to this stage. When the install process finishes the cdrom drive will eject the disk and you need to remove it. Once you have done this single left click the reboot button on the bottom right hand of the screen. After the system reboots you should see the following screens.

10

V E R S I O N

1 . 2

U S E R

M A N U A L

On this screen you will be able to download the latest version of the payload file and install PBX in a Flash Version 1.2. You must choose A unless you are a PBX in a Flash Reseller/Partner. If you are a Reseller/Partner you will have been provided with PBX in a Flash Disk 2 which contains special versions of the load files.

11

V E R S I O N

1 . 2

U S E R

M A N U A L

The second screen indicates that the computer has successfully connected to www.pbxinaflash.net and started the download and binary verification process

This process checks the payload file to ensure that there were no transmission errors during the process and then continues the install process. The program will also attempt to download the payload file from various mirrors in case one of the mirrors is down. If the verification procedure is successful PBX in a Flash will begin to install. Please be patient as this may take a while! You should see screens similar to the one below informing you of the progress of the install. There may be times when it appears that the install has frozen. This is NOT the case!

12

V E R S I O N

1 . 2

U S E R

M A N U A L

Eventually you will the final screen and then the system will reboot.

. To reiterate what the screen says: You may see a few errors after this screen and these can safely be ignored. The system is in a state of flux and requires rebooting for the final changes to take effect. These errors you see are NORMAL and inconsequential.
PLEASE DO NOT NOTIFY THE PBX IN A FLASH DEVELOPMENT TEAM ABOUT THESE ERRORS OR CLOG UP THE FORUMS WITH REPORTING OF THEM. It is OK just relax and take a break.

11. Once the system reboots you will see the following screens

The screen above is our custom boot screen.

13

V E R S I O N

1 . 2

U S E R

M A N U A L

12. Loading of PBX in a Flash will continue

You now need to log into your PBX in a Flash system. Type the username root and then enter the password you entered in Step 10. 13. You should now see the following screen. Welcome to PBX in a Flash!

14. Type help-pbx and then tap the ENTER key. Here you will see some scripts that will aid you in getting your PBX in a Flash setup.

14

V E R S I O N

1 . 2

U S E R

M A N U A L

Notice that our compiled scripts are no longer included with the load file. This is due to change in the way that these scripts and programs are provided to you. I recommend in you run update-scripts at this time to install these extra scripts. 15. At the prompt type update-scripts

16. Now page through the license agreement as below

15

V E R S I O N

1 . 2

U S E R

M A N U A L

Simply tap the Y key and the program will install all of the PBX in a Flash goodies you are used to having. 17. No do a help-pbx after the install program finishes and on the second page you will see all of the new programs that you can use.

The screen is slightly different for PBX in a Flash Version 1.2 Asterisk 1.6 BETA as some of the programs have 16 appended to the name. This is because the programs that function with Asterisk 1.6 are slightly different. A final word of caution; none of these programs are designed to run on the original PBX in a Flash Versions 1.0 and 1.1. Doing so may cause considerable harm! We have taken every precaution to preclude these programs being run on earlier versions of PBX in a Flash.

16

V E R S I O N

1 . 2

U S E R

M A N U A L

17

V E R S I O N

1 . 2

U S E R

M A N U A L

2
Section

Initial Configuration of PBX in a Flash


"Always listen to experts. They'll tell you what can't be done, and why. Then do it." R.A.H
Overview The next few pages will walk you through the steps required to get your PBX in a Flash system up and running in a minimalist configuration. This is by no means a complete configuration guide you just may have to wait for the book to come out! We will setup at least 2 extensions and give you the basics of setting up inbound and outbound trunks. Updating PBX in a Flash There may be some late breaking updates that did not make it into the current release of PBX in a Flash so you should check for upgrades. After you have ran update-scripts as outlined in section one you should be up to date for updatescripts. It is recommended you run update-scripts and update-fixes every so often to ensure your system is up to date. Please perform the following steps: 1. Log into the CLI (Command Line Interface) as user root using the password you typed in during the install.

18

V E R S I O N

1 . 2

U S E R

M A N U A L

2. This is the initial login screen and tells you about your system ip address and how to get help. Notice the green root@pbx:~ $ this is a customized version of the bash environment and is a visual queue that the install of PBX in a Flash seems to have completed successfully.

3. Lets update all of the scripts on our PBX in a Flash machine. At the CLI type update-scripts and tap the Enter key. You should see a screen similar to the one below.

19

V E R S I O N

1 . 2

U S E R

M A N U A L

4. Once the program update-scripts has completed please type help-pbx and you will see a screen similar to the one below.

Notice the date and version on the second line. This is the date of release of the last update and the version of the update. 5. Now we need to update PBX in a Flash with any patches that did not make it into the current release of PIAF. Please type update-fixes and then tap the Enter key. You should see a screen similar to the one below.

20

V E R S I O N

1 . 2

U S E R

M A N U A L

At the moment there are no fixes available but you would see various things showing the progress of the update and then you will be shown a screen that will allow you to review all of the changes to your machine.

Setting passwords PBX in a Flash must be secured! In order to do this you will need to set the passwords. You have already set the root password when you initially installed PIAF. We have written a script that sets most passwords and enhances the security of your PIAF install. If you use weak passwords your installation will be compromised. See Appendix one for tips on creating good quality passwords. Passwd-master is the script you will want to run in order to set most passwords in PIAF. This script will do the following. Sets up webmin to use user root and their password for access Changes freepbx to use .htaccess instead of database access. This will allow you to use your maint password to gain access to freepbx instead of admin/admin. Much handier not having to remember more passwords. Set the passwords for users maint, amp, and meetme to the same password. This is useful initially when you are setting up your PIAF system, however it is a bit of a security risk so once your system is up and running it is recommended you change the passwords to something unique. This can be accomplished by typing help-pbx and using the correct script to change each user individually. Passwd-master will not change the password of MySql or Asterisk Manager! It is recommended you do not change this unless you know what you are doing. When you configure FreePbx you will see it complaining that you are using the Default Asterisk Manager and SQL passwords. Resist the urge to fiddle as you PIAF system will stop unless you REALLY know what you are doing. Only a person with physical access to your actual PBX in a Flash server can gain access to MySQL using the default password. So sleep well.

21

V E R S I O N

1 . 2

U S E R

M A N U A L

Running passwd-master 1. Log into the CLI (Command Line Interface) as user root using the password you typed in during the install.

2. Type passwd-master and tap the Enter key. You should see a screen similar to the one below.

3. Now tap the Enter key and you should see a screen similar to the one below.

4. You have 3 choices. You can tap the Y key to continue and fix webmin, you can tap the N key to make no changes and continue, or you can hold the Control key down and tap the C key to exit. If you chose the Y you will see some information flash by on the screen. 5. The next screen should look similar to the one below. Here you can choose to use the maint username and password instead of admin/admin and turn on .htaccess (google this if you want to know what it is). You can also tap the N key and no changes will be made or you can hold the Control key down and tap the C key to exit.

22

V E R S I O N

1 . 2

U S E R

M A N U A L

6. The last screen will take a password you enter and set it for users maint, amp, and meetme. This is a real timesaver when you are setting up your PIAF machine but once it goes into production it is a good idea to set each password to something different. This can be accomplish by using the other passwd-XXXXX scripts which are listed in help-pbx.

7. Common errors with this script are attempting to just hit the Enter key and not typing the same password. Null passwords are not allowed so you have to enter something. For guidelines on choosing a password please look in Appendix 1. Below are the screens you may see if you encounter and error and if you successfully set the passwords.

23

V E R S I O N

1 . 2

U S E R

M A N U A L

Network Configuration This should be one of the easiest parts of the install however some have reported a non sticky IP address which could cause problems so we will outline a workaround for it. Also there is some controversy regarding the use of DHCP versus Static IP addresses for PIAF systems. The best plan for your PIAF system is to assign it a static IP address this will ensure that the phones can always find it on the network and solve a lot of common DNS errors. Using DHCP can work in some circumstances however my recommendation is to stick with static IP addresses only. A discussion of the pros and cons of each is beyond the scope of this document. 1. Gather the information you will need to create a static address. Have a look at the table below and fill it out prior to going on to step 2. If you are going to use a DHCP IP address skip this section entirely. A short explanation of each item is below the table. Table 1 Option Static IP Address Netmask Default Gateway Primary Nameserver -

Information

Static IP Address: This is generally one that your router does not assign by DHCP Netmask: This is generally 255.255.255.0 for Class C non sub netted networks Default Gateway: This is generally the IP address of your router Primary Nameserver: This should not be the same address as the Default Gateway (depending on your network). This is due to some routers used at the consumer level have problems with nameserver tasks. A better solution is to point to the nameserver of your ISP as opposed to your router. You will need to look at your router configuration pages to get this number. Thus if you simply point your Primary Nameserver to your router

24

V E R S I O N

1 . 2

U S E R

M A N U A L

will you have problems? Probably not; but if you run into errors with DNS resolution then you should try to point to your ISPs nameserver.

2. Log into the CLI using the root user and type netconfig and then tap the ENTER key

3. You should see a screen similar to the one below

If you get a command not found warning then netconfig may have been deleted from your PIAF system. This is occurring because CentOS 5.1 removes it and installs system-configure-network which is an inferior program! You will need to restore the netconfig program using a script that has been included. Type install-netconfig at the prompt and once it completes retry netconfig. If you get the screen above using the left or right arrow select the Yes button and then tap the ENTER key

25

V E R S I O N

1 . 2

U S E R

M A N U A L

4. You should now see the screen below

Tab down to the IP address field and fill out all of the information that is required. NOTE do not use the information contained in the image! Select the Ok button and tap the ENTER key. 5. You should be back at the Linux CLI now. We need to reboot the system by typing shutdown 0r now and then tapping the ENTER key.

6. Your system will now reboot. Once the boot process has finished log back into the Linux CLI as user root and repeat steps 2 4 over again. This time when you get back to the Linux CLI type the following service network restart and then tap the ENTER key.

26

V E R S I O N

1 . 2

U S E R

M A N U A L

7. Now lets test our connection type ping www.nerdvittles.com and then tap the ENTER key. You should see something similar to the screen below

After you see a few lines of reply hold down the Ctrl key and then tap the C key. You have now set up a static IP address. If you see anything else than the screen above try rebooting the computer using Step 5 and try Step 7 again. Configuring Zaptel Zaptel is already preconfigured when PIAF is installed and the following steps are added for completeness and to help users get a feel for what some of the mystery files files do. There are some options that are not pre-enabled so you would have to edit some files to get things running. The example below assumes you have not analog to digital devices, either external or internal, running with PIAF. Because this is our first foray into editing configuration files a few caveats are in order. You should not edit linux based files on a windows based computer! This is due to that Linux and Windows use a slightly different format for text files. If you do edit Linux files with a Windows editor you may find that things stop working mysteriously. With PBX in a Flash Version 1.2 I have already installed my favorite editor joe and I have included a brief command list in Appendix 3. 1. Log into the CLI (Command Line Interface) as user root using the password you typed in during the install.

2. This is the initial login screen and tells you about your system ip address and how to get help. Notice the green root@pbx:~ $ this is a customized version of the bash environment and is a visual queue that the install of PBX in a Flash seems to have completed successfully.

27

V E R S I O N

1 . 2

U S E R

M A N U A L

3. Now we need to change to the sysconfig folder. Please type cd /etc/sysconfig and then tap the ENTER key.

4. Please type type the following joe zaptel and then tap the ENTER key.

28

V E R S I O N

1 . 2

U S E R

M A N U A L

Using the arrow keys scroll up and down and ensure that a # is placed in the front of each of the entries in the file. If you have one of the cards listed please be sure to uncomment it. If you are running in a vmware system you only need ztdummy and TELEPHONY=yes choices uncommented 5. Now hold down the Ctrl key and hit the K then the X keys in order and your file will be saved. If you want to exit joe without saving hold down the Ctrl key and tap the C key You should see the screen below if the file was saved correctly

6. Now we can run genzaptelconf to correctly configure zaptel. In the CLI type genzaptelconf and then tap the ENTER key.

If you get errors the first time you run genzaptelconf simply rerun it and you should see a screen similar to the one above. While Asterisk will auto configure your hardware most times it does speed up loading of PIAF when it boots slightly. If you decide to install an analog to digital device you will have to uncomment the appropriate line and then rerun genzaptelconf.

29

V E R S I O N

1 . 2

U S E R

M A N U A L

Appendix 1
BOOT OPTIONS Boot Option ks ksalt ks-sataraid ksnet ksauto Description This will install PBX in a Flash Asterisk 1.4 based using LVM (logical volume management) My personal preference is to NOT use this choice. All of my systems use ext3 formatting instead. This will install PBX in a Flash Asterisk 1.4 based using ext3 formatting. This is my personal preference. This will install PBX in a Flash Asterisk 1.4 based using dual sata drive in a software based raid configuration. You need a motherboard or controller that supports this and 2 sata drives PBX in a Flash Asterisk 1.4 based using LVM (logical volume management) It is the same as ks except all of the centos files are pulled from the internet. This will install PBX in a Flash Asterisk 1.4 based using ext3 formatting. There is no user intervention required other than typing the ksauto at the first prompt of the ISO default password is passworm This will install PBX in a Flash Asterisk 1.6 BETA based using LVM (logical volume management) My personal preference is to NOT use this choice. All of my systems use ext3 formatting instead. This will install PBX in a Flash Asterisk 1.6 BETA based using ext3 formatting. This is my personal preference. This will install PBX in a Flash Asterisk 1.6 BETA based using dual sata drive in a software based raid configuration. You need a motherboard or controller that supports this and 2 sata drives

ks16

ks16alt ks16-sataraid

30

V E R S I O N

1 . 2

U S E R

M A N U A L

Appendix 2
Choosing a Password Passwords used by PBX in a Flash can be of any length and are both case and punctuation sensitive. We recommend using at least eight characters, some of which are punctuation marks or other special keyboard characters. Shorter and simpler passwords weaken your defenses. For example, the password JOHNJOHN is quite weak, particularly if your name is John. J_O%H#N@ is slightly better, but it still contains elements of your name. A password such as F#LLL&*_ would be a better choice (Note: Please do not use this example). Lastly, try to use a password you will remember, but which others will not guess (easier said than done), and NEVER write your password down and place it in a place that anyone can easily find. I stand by this recommendation and when I worked COMPSEC for a national police agency trying to penetrate their own security this was my favorite method of breaking into secure systems. One of the most common forms of social engineering (hacking) comes from people finding the passwords you wrote down and left laying around. If your memory is not too good and you write your passwords down please put them somewhere safe such as a lockbox or an encrypted USB key or a smartcard. All of these methods can be broken at the moment except for your memory (there is some question about that now with the advent of fPET/fMRI scans). We suggest using an easily remembered scheme such as the following that is almost impossible to guess: 1. Choose a nursery rhyme or other saying that you can remember. 2. Use the first letter of each word, either upper or lower case, in sequence to make up the password. 3. For words such as and, at, number or star use the symbols on the top row of the keyboard (&, @, # or *. 4. For numbers use the actual number key rather than the word. 5. Use punctuation where appropriate. 6. For example, Hey Diddle Diddle, the Cat and the Fiddle! would generate the following password: HDD,tC&tF!. (Do not use this example as your password) 7. Lastly there are multiple passwords that PIAF uses for various functions. You should NOT make all of the passwords the same on PRODUCTION MACHINES EVER! However when you are initially setting up the production server it is convenient to do so.

31

V E R S I O N

1 . 2

U S E R

M A N U A L

Appendix 3
Joes Own Editor Commands CURSOR ^B ^P ^Z Left Up Previous Word ^F ^N ^X SEARCH ^KF Find Text ^L Go To ^U ^A ^KU ^KL Previous Screen Beginning of Line Top of File Go to Line Number BLOCK ^KB ^KM Begin Block Move Block ^KK ^KC ^KY End Block Copy Block Delete Block ^V ^E ^KV Next Screen End of Line End of File Find Next Right Down Next Word

^KW File Block ^K/ Filter Block with.

DELETE ^D ^W ^J ^^ Delete Character Delete Word to right of Cursor Delete Line to Left of Cursor Redo Delete ^Y ^O ^_ Delete Line Delete Word to Left of Cursor Undo Delete

32

V E R S I O N

1 . 2

U S E R

M A N U A L

MISCELLANEOUS ^KJ ^R Format Text Refresh Screen SPELL ^[N Spell Word EXIT ^KX ^KZ Save File With Changes Open Shell Window FILE ^KE ^KD Edit Another File Save File ^KR Insert File ^C Exit File No Changes ^[L Spell Check File ^T ^@ Options Insert

33

V E R S I O N

1 . 2

U S E R

M A N U A L

Appendix 4
PBX in a Flash Functional Overview Install PBX in a Flash

4/23/2008

Decide which ISO version

PBX in a Flash version 1.1 using 32 bit Centos 5.0

PBX in a Flash Version 1.2 using 32 bit Centos 5.1

PBX in a Flash Version 1.2 using 64 bit Centos 5.1

PBX in a Flash 1.1 Install with Asterisk 1.4x (No further changes to the load files thus asterisk is not updated anymore using the load file. Instead you will use the updatesource to do your updates)

Install PBX in a Flash Based on Current Asterisk 1.4 source Recommended for production environments

Install PBX in a Flash Based on Current Asterisk 1.6 BETA source Recommended for test environments

Install PBX in a Flash Based on Current Asterisk 1.4 source Recommended for production environments

Install PBX in a Flash Based on Current Asterisk 1.6 BETA source Recommended for test environments

Further development of programs for PBX in a Flash 1.1 has ceased and the existing programs have been moved to maintenance status only

Further Enhancements of the Asterisk 1.4 install using various scripts and programs to accomplish this. For example install-gtalk. Development of new programs and scripts is ongoing. These scripts can only be run under PBX in a Flash Version 1.2 that has had Asterisk 1.4 installed

Further Enhancements of the Asterisk 1.6 BETA install using various scripts and programs to accomplish this. For example installgtalk16. Development of new programs and scripts is ongoing. These scripts can only be run under PBX in a Flash Version 1.2 that has had Asterisk 1.6 BETA installed

Ongoing program development and creation of new addons

34

V E R S I O N

1 . 2

U S E R

M A N U A L

Index

35