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 PBX V70 introduces a redesigned admin interface, multi-core scalability supporting more than a thousand concurrent calls per server, and integrated AI voice agents for both inbound and outbound communication. Reusable AI templates make automation easier to deploy, while snapshots and centralized provisioning reduce operational risk. With custom dashboards, emergency alerts, and WhatsApp Business integration, V70 provides greater control and flexibility for real-world deployments.
The Vodia PBX now integrates with Jitsi Meet, bringing secure, self-hosted video conferencing directly into the web portal. Users can launch meetings with a single click, while built-in features like JWT-based authentication, automatic room creation tied to extensions, and controlled guest access ensure a seamless and secure experience. By combining voice and video within one system, businesses and service providers gain greater control over their communication environment, reduce reliance on external platforms, and scale more efficiently.
The Vodia PBX now integrates with efficy CRM, enabling organizations to connect their phone system directly with their customer relationship management platform. Incoming and outgoing calls can automatically identify contacts, display caller information in real time, and provide direct access to contact records within the CRM. By combining telephony with customer data, the integration helps teams respond more efficiently, log interactions automatically, and maintain accurate customer information within their existing workflows.
.svg)
