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.
The Vodia Partner Program and new Vodia Partner Portal give service providers, MSPs, system integrators, and technology partners a clearer way to grow their Vodia business. Partners can earn status points through revenue, certifications, customer acquisition, referrals, and other activities, then use those points to progress through partner levels and unlock higher discounts. The launch also includes a limited-time Summer Launch Promotion, giving new partners a faster path toward Gold status and a 20% discount.
Traditional IVR and AI receptionists both help businesses manage incoming calls, but they are built for different caller experiences. IVR works well for predictable routing, fixed menus and simple call flows, especially when callers need to reach a department, queue or mailbox. AI receptionists support more natural conversations, smarter responses and more flexible automation, helping callers explain what they need and reach the right outcome faster. The right choice depends on call volume, caller needs, budget and how much personalization your business wants to offer.
Vodia Monitor is a self-hosted monitoring platform for Vodia PBX deployments that gives administrators and service providers centralized oversight across multiple systems. Monitor uptime, SIP trunks, TLS certificates, ports, tenant activity, blocked IPs, and infrastructure events from a single dashboard. With alerts, historical tracking, rankings, AI health summaries, and operational insights, Vodia Monitor helps teams identify issues faster, reduce manual monitoring, and maintain infrastructure health across distributed PBX environments.
.svg)
