Latest Documentation

Latest Release Notes
MPBX Datasheet
MPBX Quick Start Guide
MPBX Appliance User Guide
MPBX Hardware Manual


Source Code

PIKA Support Forums

Report An Issue

You can search the PIKA Mantis database to see a list of known issues with the WARP Appliance.

You will need a username and password to report an issue.

Please, before entering a new bug report, search the database to see if someone else has reported the same issue.

Child pages
  • Release 4.1.x
Skip to end of metadata
Go to start of metadata

Table Of Contents


1. Overview

The PIKA WARPTM Telephony Appliance is perfect for those wanting to provide voice, data, SMS and fax functionality. The solution is ideal for remote work sites such as oil rigs and construction sites where landlines are not always available, for businesses wanting to cut the cord on land-lines or who have a need to create a bring your own device (BYOD) solution. 

This release of the WARP appliance hardware (version 3) is based on X86 architecture. It also includes software based on Debian 7.0 Wheezy release.


2. Release Features

This release is an update to the 4.0.x version of software.

2.1. Software Features

2.2. Hardware Features

3. Release History


4. System Requirements

WARP 4.0 software requires WARP appliance hardware version 3. (PIK-APP-006xx)


5. Upgrade Instructions

To upgrade your PBX, log into the GUI and select "System Configuration > Upgrade".

  1. Click on "Update Check" only it list the new version.
  2. Click on "Update" button.

6. Known Issues

To view a list of current issues, check the list of bugs in our bug tracking system.

Before reporting a new issue, ensure that you have the latest version of all packages.


6.1. Additional Issues

  • Micro SD cards are not supported
  • BRI and FXO modules cannot co-exist in the same system
  • Screws must be used to secure the modules to the base board at all times to provide proper contact for frame grounding.
    Failure to do so may cause intermittent port connection failures.

6.1.1. GSM

  • Emergency calling (911/112/etc.) without a SIM card is not supported
  • There may be some initial noise when a GSM call is answered 
  • Incoming or outgoing calls on a GSM channel may have longer latencies  
  • There may be up to a five second delay before two way audio is established with outgoing GSM calls

6.1.2. Fanvil Phones

  • Currently the Software doesn't manage TimeZone on Fanvil phones it set to default of GMT+0000. Refer to issue 10758.

6.2. Hardware Issues

  • No provisioning of Eth1; Eth1 only comes up on power up of the unit when the Ethernet device is plugged in, otherwise it sets the MAC address to 00:00:00:00:00:00



7. Factory Images

The following procedure can be used to reset the unit to factory defaults. (Please note that this will wipe out all existing configuration.)

First obtain the software image from the link below, as an example, to a computer which can accept SD cards. Additional links are provided in the release history above. Select the newest link or the one that is appropriate for you. 


The software image expands so please ensure you have at least 6GB of free space on this PC.

Place a SD card into the computer with the download software image. Then to commit this image to the SD card you can use the commands below depending on the operating system you are using. (Assuming the SD card is on /dev/sdb) Once completed the process the SD card can be extracted from the PC and place into Warp.



7.1. Linux/Mac

  1. Place the sd‐card into your system. ( By default operating system will mount it)
  2. Un mount the current sd‐card
    1. umount <mount path>
  3. tar zxf mpbx_4.2.0.18_4Gig_Sandisk.bin.gz
  4. dd if=./mpbx_4.2.0.18_4Gig_Sandisk.bin of=/dev/sdb bs=1M

( Note: In Fedora the sd‐card device is called /dev/mmcblk0 )


 Alternate instructions for MAC if the above is not successful -

Step 1 Format the partition using the SD Formatter from SD Association

Step 2 Get the list of disks and partitions on the system with "diskutil list" and figure out which disk is the SD card (for example, /dev/disk2).

$ diskutil list

Step 3 unmount the partition using disk util (this may require sudo) 

$ sudo diskutil unmountDisk /dev/disk2
Unmount of all volumes on disk2 was successful

Step 4 extract the contents of the compressed image

$ tar zxf mpbx_4.2.0.18_4Gig_Sandisk.bin.gz

Step 5 copy the image to sd card using dd. (Notice that there is a "r" as a prefix for the disk)

$ sudo dd if=./mpbx_4.2.0.18_4Gig_Sandisk.bin of=/dev/rdisk2 bs=1m


7.2. Windows

In windows you can uses Win32 Disk Imager.


This tool allows you to write a software image to SD card. Before starting you will need to unzip the software image and extract the bin file. Once this is complete you can run the Disk Imager tool and follow the steps below.


First, select the image bin file as the source (Step '1'). (To do this select the file type as *.*)
Secondly, select the Sd card device (Step '2'). (Note: the SD card must be in a Windows recognizable format.)
Then select the 'Write' button. (Step '3').
If successful you will see the writing proceed with a status bar like shown in the picture above.


  • No labels