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.
From the moment humans learned to speak, communication has shaped how we live, work, and connect. Today, voice remains one of the most natural and information-rich forms of human interaction, even as business communication expands across chat, video, messaging, and digital platforms. As AI becomes more deeply integrated into phone systems and contact centers, voice may play an increasingly important role in how intelligent systems understand context, respond to people, and support real-time communication.
White-labeling the Vodia PBX enables MSPs and VARs to offer business communications under their own brand without developing and maintaining the underlying PBX technology. Providers control branding, packaging, pricing, service delivery, and customer relationships, while Vodia supplies the multi-tenant platform. With V70’s expanded branding and management tools, MSPs can get to market faster and create new recurring-revenue opportunities.
Apple CarPlay support is now available with the Vodia iOS app, bringing essential PBX communication features to the vehicle display through Apple’s native in-car interface. Users can access recent calls, browse the extension directory, view colleague presence, listen to voicemail, use Siri for calls and PBX messages, and receive communication alerts, while built-in readiness checks and automatic recovery help maintain reliable access when network conditions change. The experience supports compatible wired and wireless CarPlay systems.
.svg)
