Aug 28 2009

How-To: Installing FreePBX on Warp without PADS

Published by at 2:58 pm under How-To

In order to use FreePBX on your Warp appliance you will need to update the software images on your unit.  Typically, applications developers use PADS (PIKA’s Application Development Suite) to build the software images themselves and then use the utilties in PADS to install the images on the Warp.  Fortunately, for those who don’t want to get involved with PADS, there is another way:  You can copy the pre-compiled FreePBX images and an automated script to a USB stick and let the script install the images on your Warp for you.   The detailed procedure is decribed below.

1.  Download the tarball from this link:

Note:  At the time of this writing, the latest version was  Check for the latest version.

2.  Unpack the tarball file and copy the “autorun”, “cuImage.warp”, “image.jffs2”, “image1.jffs2”, “image2.jffs2” and “uRamdisk” files to a USB stick.

Optional:  Before proceeding, if you wish to monitor the progress of the software update, you can access the serial port on your Warp as described here:

3.  Then you can insert a USB stick into an appliance that is running, or insert it before system startup and then power up the appliance.  Either way, the autorun script should take care of the everything automatically.


i )  When you install the images, the WARP needs to reboot once to finalize the installation of FreePBX, it’s database files and regenerate the translation files. The last one in particular can take some time to complete, so please be patient after you flash the image files.  You will know it is ready to access when the LCD screen shows the line status of the modules in the WARP.

ii )  We recommended that you flash this image using a USB stick, since this load has the “transfer to SD card” functionality enabled in it.  If you use an SD card, at the end you will need to remove it and reboot the WARP an extra time. If you do not want the “transfer to SD” functionality enabled, you will need to compile your own version.

iii ) After you have updated the software images on your Warp, if you want to store voicemail, sound files, etc…insert the SD card and FreePBX will automatically transfer the files to it.

iv )  This version of FreePBX requires a username and password to access it.  The factory default admin username is asterisk with a password of amp109.   Note that you can also access FreePBX using user admin, password admin.  We recommend using user “admin” because you can change it in the GUI.


6 responses so far

6 Responses to “How-To: Installing FreePBX on Warp without PADS”

  1. Dougon 03 Sep 2009 at 1:37 am


    I just got my development Pika WARP today and updated as it says in this thread.

    1) I was using a Windows VISTA computer

    2) I unzipped the files from onto a 4GB USB

    3) I put the key in the PIKA Warp, and powered the PIKA on

    4) The Warp did some processing, rebooted as indicated, did some more updating, and then sat for a long time (> 10 minutes) with the LCD screen just saying “ – LCD waiting for asterisk”

    4) I figured I had screwed up somewhere and was almost ready to reset the system, but just decided to wait.

    5) Eventually it rebooted again, and then everything loaded as promised.

    I thought I would write this for any other new users to let them know that:
    - be very patient.
    - it is actually quite easy to update the system if you follow the procedure

  2. skaron 28 Sep 2009 at 4:33 pm

    Hi Doug,

    Thanks for that reply. Maybe we should have stressed the patience part here more. The 10+ minutes after LCD starts is due to us regenerating all of the translation files for FreePBX. You can disable this if you do your own build, but it is on in the releases we post here.

    Also, is you use SD card, it can take a while to format it and transfer files to it. Also be patient here.

    In total, the whole process can take 1/2 hour or more in our loads released here as we have alll options turned on.

  3. evanon 10 Dec 2009 at 11:04 am

    Hi there,

    I have successfully performed the above procedure using the latest version (29_10_2009).
    Now I would like to wipeout all the changes I’ve made to the unit and reflash it with the same image.
    When I try to repeat the procedure nothing happens. It does not appear to read the usb drive.

    How do I force the update again?


  4. marekon 10 Dec 2009 at 6:39 pm

    You should be able to ‘trick’ the script. With the USB key inserted, remove the ‘/persistent1/burnlog.txt’ file and reboot. If you want to save the burn history rename the file instead of completely removing it.

    A ‘force’ option in the script sounds like a good idea.

  5. marekon 11 Dec 2009 at 10:47 am

    It was pointed out to me that you can also change the ‘BURN_VERSION’ variable at the top of the autorun file as well and re-run the update process.

  6. vedradijauson 10 Sep 2012 at 9:36 pm

    Thanks for sharing such a useful stuff!

Trackback URI | Comments RSS

Leave a Reply