Tech

Vodia PBX on Microsoft Azure Platform

Published on:

March 5, 2015

Installing the Vodia PBX on a Microsoft Azure server provides an easy solution for businesses looking for a cloud PBX. The installation process is similar to that on any Windows operating system, but there are key steps to ensure smooth operation. First, make sure to open all necessary ports, including HTTP (80), HTTPS (443), TFTP (69), NTP (123), and LDAP (2345 for StartTLS, 2346 for TLS). Additionally, for audio traffic, virtual networks require specific endpoints with both public and private ports. The RTP range (e.g., 49900-50000 for 25 calls) must be configured based on how many calls you need. Each call uses four ports, so adjust accordingly for your system.

We recently had the opportunity to install the PBX on a Microsoft Azure server. This blog entry is about what we learned.

First if all, what is Microsoft Azure? In short, it’s Microsoft’s cloud platform. It's a growing collection of integrated services - computing, storage, data, networking, and app - that help you move faster, do more, and save money. But that’s just scratching the surface. The Vodia PBX can be easily installed on the Azure Server.
‍

The installation of the software itself is just like installing the Vodia PBX on any other Windows operating system.
Once the PBX is installed on your virtual server, you’ll have to open some ports (for example):

  • HTTP Port: 80
  • HTTPS Port: 443
  • TFTP Port: 69
  • NTP Port: 123
  • LDAP Port: (TCP, StartTLS): 2345
  • LDAP Port (TLS): 2346
  • RTP range: This setting will depend on how many calls you’d like to have on the system.

For the PBX to receive and send audio on your virtual server, you’ll have to open some endpoints. Virtual networks require endpoints to direct the inbound network traffic to a virtual machine. Each endpoint has a public port and a private port.

  • The public port is used by the Azure load balancer to listen for incoming traffic to the virtual machine from the Internet.
  • The private port is used by the virtual machine to listen for incoming traffic, typically destined to an application or service running on the virtual machine.

To open an endpoint on your Virtual Machine please navigate to create an Endpoint.

NOTE: An RTP range of 49900-50000 will allow you 25 calls. That’s 100 ports for RTP. Each call uses 4 ports, so you’ll have to decide how many calls you want on the system. To determine how many calls you would like on your system, multiply the number of calls by 4 to get the number of ports you’ll need.

Navigate to the Dashboard, click on ENDPOINTS, and open your RTP range here.

Latest Articles

View All

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026

It’s an App-First World, but Businesses Still Need Hardware

Apps have changed how businesses communicate and work, but every digital experience still depends on physical hardware. From smartphones, desk phones, and headsets to networking equipment and cloud servers, reliable infrastructure supports productivity, security, and call quality. Here’s why hardware still matters in an app-first world and what businesses should consider when choosing dependable devices and secure connectivity for the office, hybrid teams, and remote work, while preparing for evolving technology.

October 7, 2026