Installation

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

Note:
The Call Center module is installed together with the PBX and cannot function without it. Ensure PBX services remain active.

🔧 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 the system 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 system appliances come with the OS and 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 the system 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 system 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 system installation script:

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

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

3️⃣ Private Cloud Deployment

Description

Run system 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 system 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 system 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 system 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 system 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 other platforms

AWS Example (Using AMI)

Steps

1. Log into the AWS Console.
2. Search for the system AMI in the EC2 Marketplace or shared AMIs.
3. Launch a new EC2 instance using the AMI.
4. Allocate a static IP (Elastic IP) and adjust security groups.

Azure Example (OVA/VHD Upload)

Steps

1. Upload OVA or convert it to VHD format.
2. Create a new VM using a custom image.
3. Assign a public IP and open necessary ports via NSG (Network Security Groups).

📌 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

🖥️ Call Center PBX Hardware Requirements (Based on Agent Count)

Agent Count	Concurrent Calls (Est.)	CPU (vCores)	RAM	Storage
10–25	10–20	2 cores	4 GB	40–80 GB SSD
25–50	20–40	4 cores	8 GB	80–120 GB SSD
50–100	40–80	6–8 cores	12–16 GB	120–250 GB SSD/RAID
100–200	80–150	8–12 cores	16–24 GB	250–500 GB SSD RAID
200–500	150–300+	16+ cores	32+ GB	500 GB – 1 TB SSD RAID

🎙️ 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).