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.
Vodia Phone 2 brings business calling directly into your Android smartphone experience. By integrating with Android's native calling framework, work calls ring, answer, and behave like regular phone calls, eliminating the need to switch between separate calling apps. Users can place calls from the standard phone dialer, answer from the lock screen, and take advantage of familiar Android features while still benefiting from business tools such as call history, messaging, voicemail, call forwarding, DND, and custom status settings.
Vodia Sales Engineer Eric Altman will attend HITEC North America 2026 in San Antonio, Texas, where he will discuss V70, the latest version of the Vodia PBX, and its applications for the hospitality industry. Vodia will showcase its AI-driven communications capabilities, hospitality-focused PBX features, integrations with leading property management systems and hotel phones, and solutions designed to help hotels improve guest experiences, streamline operations, and support modern communication requirements.
Modern business communication rarely happens within a single office or PBX environment. With V70 of the Vodia PBX, organizations and service providers can now share presence information between tenants and across separate PBX systems. External Presence Sharing extends BLF visibility beyond a single deployment, helping distributed teams maintain awareness of user availability across locations, departments, and communication environments while supporting more connected and flexible business communications.