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

Mobile Apps, Desk Phones, and Browser Calling: Choosing the Right Endpoint by Role

Business communication is no longer tied to a single device. Desk phones remain valuable for employees who manage high call volumes, mobile apps give remote and travelling teams access to business calling wherever they work, and browser calling fits naturally into computer-based workflows. This article looks at the strengths and limitations of each endpoint, explains which roles they suit best and shows why most organizations benefit from building the right mix rather than selecting one option for everyone.

July 30, 2026

Your Vodia Extension, Built for iPhone

The new Vodia iOS app gives users a native way to use their Vodia PBX extension from iPhone and iPad. Built around a cleaner, card-based interface, the app makes it easier to manage calls, voicemail, chat, extensions, call history, and active call controls in one place. Users can place and receive calls, park or transfer calls, check voicemail, and view extension status from the app. It also adds readiness checks, visual audio feedback, call quality visibility, and adaptive recovery when network conditions change, helping teams stay connected with a reliable mobile PBX experience.

July 28, 2026

Why MSPs Should Own the Customer Relationship in Cloud Communications

Cloud communications can create a valuable recurring revenue opportunity for MSPs, but only when they remain in control of the customer relationship. By managing branding, pricing, service delivery, and support, MSPs can build stronger customer loyalty, protect long-term account value, and expand their offering as customer needs evolve. A white-label approach also gives them the flexibility to package voice, AI, integrations, and managed services under their own brand.

July 22, 2026