Skip to content
Private Cloud Deployment

VoipNow OpenStack Deployment Guide

This page contains instructions on how to deploy the VoipNow QCOW2 image on OpenStack using Horizon.

Requirements

To meet VoipNow's performance and computing requirements, the instance must have the following configuration:

  • Memory: 16GB (or more)
  • CPUs: 4 cores (or more)
  • Network: 1GbE (or more)
  • Root Disk: 50GB (or more)

"Resource reservation required"

For proper VoIP functionality, CPU and RAM must be reserved/dedicated for the VoipNow instance to prevent resource contention and timing issues.

Important Notes

"⚠️ DHCP Recommended"

VoipNow IP settings are configured during first boot. If you use a static IP or if the IP address changes after first boot, you must manually update the IP in the VoipNow web interface (Cloud Management section).

Deployment (Horizon)

  1. Upload the image

    Download the VoipNow QCOW2 image from https://repo.4psa.com/download/, then go to Project → Compute → Images → Create Image and upload voipnow-*.qcow2 (format: QCOW2).

  2. Create a security group

    Go to Project → Network → Security Groups and create a security group for VoipNow, allowing at minimum:

    • TCP 22 (SSH)
    • TCP 80, 443 (Web)
    • UDP 5060 (SIP)
    • TCP 5061 (SIP TLS)
    • UDP 10000–20000 (RTP media)
    • UDP 4000–4999 (T.38 fax media)
    • TCP 25 (SMTP)
  3. Ensure an SSH key pair is available (mandatory)

    Go to Project → Compute → Key Pairs and create/import a key pair. You must select a key pair at launch (SSH password auth is disabled by default).

  4. Launch the instance

    Go to Project → Compute → Instances → Launch Instance and select:

    • Source: the VoipNow image
    • Flavor: at least 4 vCPU / 16GB RAM
    • Networks: your target network
    • Security Groups: the VoipNow security group
    • Key Pair: your SSH key pair
  5. Assign a Floating IP (if required)

    If your network requires it, allocate and associate a Floating IP to the instance.

  6. Access VoipNow

    Open https://<instance-ip> and log in with the admin credentials.

""

The first boot will take longer than usual (about 5–10 minutes). Please wait for initialization to complete before taking further action.

Last updated: Feb 2, 2026