Install PBX as Virtual Machine or Server HW | Virtualization

How to Install a PBX on a VMware or on Linux server


Memory requirements

A virtual PBX can run on any modern server as long as the server has enough resources available (RAM, Disc space). In case you run several virtual machines on one server, take into consideration that more VMs use more resources. A good example of a server that can host a Wildix system is Dell PowerEdge T110 II.

Minimum memory resources available required

PBX model Disc space RAM
WGW08, WGW16, WGW40, WGW90, WGW250, WGW500 2GB for the system + min 1GB to save extra data 2GB
WGW1000, WGW5000 2GB for the system + min 1GB to save extra data 4GB



  • NFS version 3
  • MySQL MySQL version 5.4 or higher / MSSQL version starting from 2008
  • Storage engine InnoDB or MyISAM
  • VMware: current .ova can operate on ESX/ESXi version 4.0 or later; VM Hardware version 7

Information on Per User licenses and periodic license check:

Linux Server or VM on VMware / Xen / Azure / VirtualBox / Hyper-V / KVM, or other virtualization platform supporting Linux

Important: Host Linux system should use default partition scheme without LVM!

Proceed as follows:

  • Install Linux; suggested versions:
  • Reboot the system
  • Check the list of ports that are used by Virtual PBX and make sure they are not occupied
  • Login to the machine via ssh / console with root rights
  • Go to /usr/src/: cd /usr/src/
  • Download the PBX image from the link:
    • use the command: wget [link]
    • unpack the archive wildix_pbx_install.tar.gz:
    • use the command: tar -xzf [archive_name]
  • Change the network interface name. This step is necessary for Linux distributions with Udev version starting from 197, since in this version the network interface has a generic name format (is different from “ethX”):
    • open file /etc/default/grub
    • add option “net.ifnames=0″ in line GRUB_CMDLINE_LINUX=”net.ifnames=0”

for Debian: run update-grub2

for CentOS: run grub2-mkconfig -o /boot/grub2/grub.cfg

    • reboot
    • after host system reboot, you need to manually verify that the correct interface naming format was applied:

for Debian: cat /etc/network/interfaces

the output should contain a line similar to this one (it can vary depending on system configuration): iface eth0 inet dhcp

“eth0” in this line is the interface name, which means, the naming format has been successfully changed (by default modern debian-like systems contain ens32 interface naming).


For CentOS: run command: ip r

In the output find that line which begins with ‘default’; this line should contain “dev eth0”; which means the naming format has been successfully changed.


  • In case of Per User PBX: before installing the virtual machine, change the MAC address on VM to “Serial” copied from WMP.
  • To install a virtual machine, run: “./”
  • Check the output

Console history:

MacBook-admin:~ admin$ ssh wildix@

wildix@’s password:

Linux Hyper-Debian 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686

The programs included with the Debian GNU/Linux system are free software;

the exact distribution terms for each program are described in the

individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Thu Sep 18 17:30:58 2014

wildix@Hyper-Debian:~$ su


root@Hyper-Debian:/home/wildix# wget

–2014-10-02 17:58:38–

Resolving (…,,, …

Connecting to (||:80… connected.

HTTP request sent, awaiting response… 200 OK

Length: 264937287 (253M) [


Saving to: `wildix_pbx_install.tar.gz’


==============================================================================>] 264,937,287 613K/s in 5m 11s

2014-10-02 18:03:51 (831 KB/s) – `wildix_pbx_install.tar.gz’ saved [


root@Hyper-Debian:/home/wildix# tar xzf wildix_pbx_install.tar.gz

root@Hyper-Debian:/home/wildix# ./install_

bash: ./install_: No such file or directory

root@Hyper-Debian:/home/wildix# ./

update-rc.d: using dependency based boot sequencing

Copying apt and archive to /wms…


Unpacking archive…


Mounting filesystems…


Running chroot…


Creating tmpfs…

Setting up RAM filesystem structure: tmpfstmpfs on /dev/shm/wmsdb.d type tmpfs (rw,size=50M,mode=777)

`/rw2/var/lib/wmsdb.d/devdb’ -> `/dev/shm/wmsdb.d/devdb’

tmpfs on /dev/shm/wmsdb.d/ejabberd type tmpfs (rw,size=25M,mode=777)

tmpfs on /dev/shm/tmp/session type tmpfs (rw,size=80M,mode=777)

tmpfs on /dev/shm/tmp/session/lighty type tmpfs (rw,size=5M,mode=777)



Fixing some configs…

Restarting jabber server: ejabberd is not running. Starting ejabberd.

Stopping wildix-con_client:No /usr/sbin/wildix-con_client found running; none killed.


Stopping wildix-con_server:No /usr/bin/wildix-con_srv found running; none killed.


Stopping OpenLDAP: slapd.

Starting OpenLDAP: slapd.

Stopping sipproxy: sipproxy.

creating usrloc.db

creating presence.db

Starting sipproxy: sipproxy.


Starting services…

Starting enhanced syslogd: rsyslogd.

Starting Shell In A Box Daemon: shellinabox.

Starting daemon monitor: monit.

Restarting DNS forwarder and DHCP server: dnsmasq.


Mounting additional directories…



Official VMware VM image

Proceed as follows:

  • Select your machine, click on the menu File > Deploy OVF Template

  • Select the file on your PC with the PBX image and click on “Next”

  • Verify OVF template details: click on “Next”
  • Specify a name and location for the deployed template: click on “Next”
  • Select the host (PC) on which you want to run the deployed template: click on “Next”
  • Select the disk on which you want to store the virtual machine file: click on “Next”
  • Select the format for storing the virtual disks: click on “Next”
  • Select the networks that the deployed template should use: click on “Next”
  • Click “Finish”

  • Wait till the image is deployed

  • In case of Per User PBX: before starting your VMware, change the MAC address on VM to “Serial” copied from WMP.

How to set static MAC address on VMware:


    1 Star2 Stars3 Stars4 Stars5 Stars (7 votes, average: 5.00 out of 5)