aavaz/pbx repository overview

⁠About Aavaz PBX – Free Edition

Aavaz PBX is designed to be powerful, yet approachable.

PBX systems are inherently technical and do require system administration knowledge. However, we strongly believe they should not be unnecessarily complicated.

This system is built to:

• work reliably in real-world environments
• be understandable without deep telecom expertise
• provide enough features to run most organizations comfortably

We will continue to add features — but never at the cost of usability.

⁠🟢 Support

If you need help - send us an email at [email protected]⁠

• We will help with everything - including:
  • setup issues
  • deployment questions
  • initial configuration

⁠Before You Begin

Make sure your system meets the following:

⁠System Requirements

• OS: Ubuntu (recommended), should work on most Linux distributions
• RAM: Minimum 4 GB
• CPU: Modern Intel/AMD processor (typical $300 PC configs work well)
• Docker: Installed and working
• Network: Public IP recommended (for real deployments)

⁠Run the Container

⁠Method 1 - Automated Script

Easiest way to get started as it will check dependencies and guide you in fixing issues it encounters.

In your Terminal copy and paste the following:

curl -fsSL https://resources.aavaz.biz/install/aavaz-pbx-install.sh | bash

⁠Method 2

sudo docker run -d \
  --name aavaz-pbx \
  --restart always \
  --network host \
  --cap-add NET_ADMIN \
  -v /mnt/aavazHost:/aavaz/data \
  aavaz/pbx:latest

⁠Access the PBX

Once the container is running:

Open your browser:

http://<your-server-ip> OR https://<your-server-ip> (secure)

⁠Default login credentials:

• 👉 Username: admin
• 👉 Password: admin

That should get you logged in and ready to go! It will get you to change your password on first login.

⁠Notes:

1. HTTPS uses a self-signed certificate initially
2. You can configure proper certificates later
3. You can also map a domain (recommended for production)

⁠Aavaz Data

The docker run command part -v /mnt/aavazHost:/aavaz/data translates to:

• /mnt/aavazHost → folder on your server
• /aavaz/data → folder inside the container

⁠The /mnt/aavazHost folder contains

• configuration
• database files
• call recordings
• logs
• TLS certificates
• credentials

👉 If you care about your data — back up this folder

Your system can be restored, if you delete the container but keep this folder.

⁠Understanding the docker run Command

This is the only command you really need to understand to run Aavaz PBX correctly.

Let’s break it down clearly:

⁠What the flags mean

• -d (Detached Mode)
  • Runs the PBX in the background so your terminal is free.
• --restart always
  • restarts automatically on server reboot
  • recovers if it crashes
  • 👉 This is important for production stability.
• --network host
  • This is a key design choice.
  • Instead of using Docker’s internal networking, the PBX:
  • uses your server’s real network directly
  • binds directly to ports like 80, 443, 5060
  • Why this matters:
    • VoIP systems (SIP/RTP) behave poorly with NAT and port mapping.
    • avoids complex NAT issues and other networking issues
    • simplifies troubleshooting
• --cap-add NET_ADMIN 👉 This is intentional and part of the security model.
  • Gives the container permission to manage network rules on the host.
  • control firewall access for SIP
  • Aavaz blocks all SIP traffic by default
• -v /mnt/aavazHost:/aavaz/data
  • This is the most important part for your data.

⁠Useful Commands

• Stop PBX
  • docker stop aavaz-pbx
• Start PBX
  • docker start aavaz-pbx
• Check running container
  • docker ps
• View logs
  • docker logs -f aavaz-pbx

Developed and maintained by: Aavaz PBX⁠
A product of Aavaz Contact Center Solutions⁠