Installation

There are several ways to install and deploy your PBX system. Depending on your infrastructure, budget, and technical expertise, you can choose from one of the following installation methods.

🔧 Installation Methods Overview

We support four primary installation methods:

1. Plug and Play Appliance – Ideal for quick setups without technical complexity.
2. Bare-Metal Server – Install PBX by uploading an OVA file or running a script over Ubuntu.
3. Private Cloud (Hyper-V, VMware, etc.) – Deploy via OVA or install manually with a script.
4. Public Cloud (AWS, Azure, etc.) – Use OVA, install via script, or launch via marketplace images like AMI (for AWS).

1️⃣ Plug and Play Appliance

Description

Pre-configured PBX appliances come with the OS and PBX system installed. Just connect to power and network to begin.

Steps

1. Unbox and place the appliance in a secure location.
2. Connect power and network cables.
3. Access web UI via IP shown on LCD or from the router’s DHCP.
4. Follow the on-screen setup wizard.

2️⃣ Bare-Metal Server Installation

Description

Install PBX directly on physical hardware by importing an OVA or running a script over Ubuntu. Best for high-performance or on-premise needs.

Option A: Deploy Using OVA/ISO Image

Steps

1. Download the latest PBX OVA file.
2. Use tools like Rufus or Etcher to create a bootable USB (for ISO).
3. Boot your physical server from the USB.
4. Follow on-screen installation instructions.

Option B: Script-Based Installation on Ubuntu

Steps

1. Install Ubuntu Server (recommended: 20.04 LTS).
2. Update the system:

sudo apt update && sudo apt upgrade -y

3.Download and run the PBX installation script:

wget https://example.com/install.sh && bash install.sh

4. Access the PBX via the web UI and complete the setup.

3️⃣ Private Cloud Deployment

Description

Run PBX in your private cloud using Hyper-V, VMware, or similar. Offers control, flexibility, and scalability within your internal infrastructure.

Supported Platforms

• VMware vSphere / ESXi
• Microsoft Hyper-V
• Proxmox, Nutanix, and others

Option A: OVA Deployment

Steps

1. Download the PBX OVA file from the official source.
2. Import the OVA into your virtualization platform:
   • VMware vSphere/ESXi: Use the vSphere Client to deploy the OVA.
   • Microsoft Hyper-V: Convert the OVA to VHDX using tools like StarWind V2V or qemu-img, then create a new VM.
   • Proxmox: Convert and import the OVA to a compatible format (e.g., qcow2 or raw).
3. Configure VM resources:
   • CPUs, RAM, Storage
   • Network
4. Start the VM and access the PBX web interface via the assigned IP address.

Option B: Script-Based Installation on Ubuntu VM

Steps

1. Create a new virtual machine in your private cloud environment.
2. Install Ubuntu Server (recommended version: 20.04 LTS).
3. Update the OS:

sudo apt update && sudo apt upgrade -y

4.Download and run the PBX installation script:

wget https://example.com/install.sh && bash install.sh

5.Complete setup via the web interface after installation.

4️⃣ Public Cloud Deployment

Description

Deploy PBX on platforms like AWS or Azure using an OVA, installation script, or official AMI. Ideal for remote access, global scalability, and high availability.

Supported Platforms

• AWS – Use available AMI or upload OVA.
• Azure – Upload VHD or OVA and deploy via custom image.
• And others

Note:
You can choose to install the system in one of two ways:

• Hosted by Xontel: Let Xontel manage the hosting and infrastructure for you.
• Self-hosted: Deploy the system on your own cloud server for full control.

Upload and Deploy OVA

Steps:

1. Convert OVA to a supported format (e.g., VHD for Azure).
2. Upload via S3/Blob or import as an image.
3. Launch VM using the image.
4. Configure network and security rules.

📌 Summary Table

Method	Skill Level	Infrastructure	Setup Time	Scalability
Plug & Play	🟢 Easy	Hardware	⚡ Fast	🔴 Low
Bare-Metal	🟡 Medium	Physical server	⏱️ Medium	🟡 Medium
Private Cloud	🟡 Medium	On-prem VM	⏱️ Medium	🟢 High
Public Cloud	🔴 Advanced	Cloud provider	⚡ Fast	🟢 High

🧠Hardware Requirements (By Extension Count)

Extensions	Concurrent Calls	CPU	RAM	Storage (SSD)	Notes
1–10	Up to 5	1 core / 1 GHz	1 GB	20–40 GB	Home/lab setup
10–50	5–20	2 cores	2–4 GB	40–60 GB	Small office
50–100	10–40	4 cores	4–8 GB	60–100 GB	Small to mid-sized business
100–300	40–100	4–8 cores	8–16 GB	100–200 GB	SMB or multi-site
300–1000+	100–500	8–16+ cores	16–32 GB	200 GB+	enterprise-grade

🎙️ If using call recording or voicemail:

• Add 50–100 GB+, depending on call duration.

🔄 If transcoding is required (e.g., G.729, G.722):

• Requires more CPU power (Asterisk uses floating-point operations).