PBX supports both modes:

• LDAP Server
• LDAP Client

LDAP Server

The LDAP service and LDAP Server mode are enabled by default in the PBX system.

In this mode, the PBX operates as an internal LDAP directory server. The PBX stores and manages directory information such as extensions and call center’s contacts, allowing external devices to query it directly.

LDAP Client

When the PBX is configured in LDAP Client mode, it connects to an external LDAP directory server to retrieve directory information.

In call center environments, this mode allows the PBX to Retrieve contact records from an external LDAP directory

1-Log in to your ESXi web interface.

2-Go to Storage > Select datastore > Datastore browser.

3-Create a new folder (optional) and upload the PBX ISO.

Create a New Virtual Machine

1-Click Create / Register VM.

2-Select Create a new virtual machine.

3-Enter VM name (e.g., PBX_Manager).

Select:

• Compatibility: ESXI
• Guest OS Family: Linux
• Guest OS Version: Debian

4-Storage

Select a datastore for the virtual machine.

5-Configure VM Hardware

• CPU: Allocate resources based on your expected system usage
• Memory: Allocate memory according to the expected system usage
• Hard Disk: Provision storage based on anticipated system requirements
• Network Adapter: VMXNET3 or E1000
• CD/DVD Drive: Select the uploaded PBX ISO

Save the configuration.

Boot the VM and Start Installation

1-Power on the VM.

2-Open the console.

3-Select Install XonTel Manager from the boot menu.

Follow the On-Screen Installation Steps

The installer will perform actions such as:

• Installing system dependencies
• Configuring Asterisk and PostgreSQL
• Setting firewall rules
• Enabling services

At the end, you should see Installation Completed Successfully. The system will reboot automatically.

First Login After Reboot

Once the system boots, you will see a login screen:

Enter SSH username and password.

Access the Web Interface

Open a browser and navigate to:

https://192.168.2.32

PBX Manager is developed by XonTel from the ground up, using the Asterisk open-source telephony engine as the core framework. By building on Asterisk’s flexible architecture, we design and implement fully tailored communication platforms that support both voice and video services. Our PBX solutions are engineered for stability, scalability, and integration with modern telephony standards, ensuring reliable performance in a wide range of business environments.

For more detailed information,

• Overview
• Event Center
• System
• PBX

To activate your system’s license, you need to follow a simple verification and setup process with the XonTel support team. This guide outlines the steps required after the first login, and how future license changes are managed.

Initial Activation Process

After logging in for the first time, follow these steps to activate your license:

1. Obtain Your Keys
   Navigate to License → License Usage to view the following:
   • Client Key
   • Hash Key
   • License Key
2. Send Keys to XonTel
   Provide the Client Key and Hash Key to the XonTel support team. These are required to register your server on the licensing server.
3. Receive License Key
   Once verified, the XonTel team will activate your license and confirm your entitlement.
4. Enter License Key
   Go to Settings → Edit License and paste the received License Key in the designated field.

Updating License Features

To activate additional features or make changes to your license (e.g., enabling a new app or increasing agent/webdialer capacity):

1. Contact XonTel Support with your requirements.
2. XonTel will update your license accordingly on the server.
3. No need to re-enter the license key — the system syncs with the server and applies the changes automatically.

Viewing Active Licensed Applications

Once your system license is active, you can easily monitor which applications are currently licensed and active.

To view active apps:

1. Navigate to License → Allowed Apps Usage.
2. Here, you’ll see a list of licensed applications with the following details:
   • Application Name (e.g., CRM, Auto Dialer, Helpdesk, Web Phone)
   • Subscription Date (when the license was activated)
   • Expiration Date (validity of the license)
   • App License State (e.g., License Active)

Viewing Licensed Capacity (Agents & WebPhone)

To monitor your current license limits for agent and WebPhone usage:
Navigate to License → License Usage.

• Max Concurrent Agents (Licensed): Total number of agents allowed to log in concurrently under the current license.
• Max Concurrent WebPhone Sessions (Licensed): Maximum number of simultaneous web phone sessions permitted.
• Access CDR Survey:Indicates whether CDR survey features are enabled (Yes or No).
• Concurrent Agents: Agents who are currently logged in.

The Call Center module is an essential tool for any organization that handles a high volume of customer calls. It provides a centralized system to monitor performance and optimize call flow. Integrated directly with the PBX manager, it supports multiple digital channels including SMS, web chat, auto-dialing campaigns, ticketing systems, social media platforms, live dashboards, and reporting tools. The Call Center module offers the visibility and control needed to maintain high-quality interactions and operational excellence.

First-Time Login – License Activation Required

Upon first login to your PBX system, a valid license must be applied before accessing the full system features.

Activation Process

Step 1: Retrieve Your License Info

You will see two important values displayed:

• Client Code – a unique identifier for your PBX installation
• Hash Key – a security hash generated for license validation

Step 2: Request a License Key

Send your Client Code and Hash Key to XonTel Support .

Step 3: Enter Your License Key

1. Click on Apply Your License.
2. A pop-up will appear asking for your License Key.
3. Paste the key provided by XonTel.
4. Click OK to activate.

Once successfully applied, the system will reload and allow full access.

Viewing Current License

To check your license status or confirm successful activation, go to:

Event Center → License

You’ll find the section:

License Information Fields:

• Client Key: Your device’s unique identifier.
• Hash Key: The secure fingerprint for verification.
• License Key: The key that unlocks your PBX functionality.

Note:
The Call Center module must be installed with the PBX and cannot operate without it. Ensure that PBX services remain active.

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 Debian.
3. Private Cloud (Hyper-V, VMware, etc.) – Deploy via OVA or install manually with a script.
4. Public Cloud (AWS, Azure, etc.) – Use OVA 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.

2⃣ Bare-Metal Server Installation

Description

Install the system directly on physical hardware by importing an OVA or running a script over Debian. 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 Debian

Steps

1. Install Debian Server.
2. Update the system:

sudo apt update 

3.Download and run the system installation script:

wget https://xontel.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 Debian VM

Steps

1. Create a new virtual machine in your private cloud environment.
2. Install Debian Server.
3. Update the OS:

sudo apt update

4.Download and run the system installation script:

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

5. Access the system web interface via the assigned IP address.

6. Complete setup via the web interface after installation.

4⃣ Public Cloud Deployment

Description

Deploy the system on platforms like AWS or Azure using an OVA 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

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. Choose instance type and configure storage.
5. Configure network and security rules.
6. Access the system Web Interface by public IP.

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)

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