We recently had the opportunity to install the PBX on a Microsoft Azure server. This blog entry is about the lessons that we learned.

First if all, for those do don’t know it: what is Microsoft Azure? In short, it’s Microsoft’s cloud platform: a growing collection of integrated services—compute, storage, data, networking, and app—that help you move faster, do more, and save money. But that’s just scratching the surface. Here’s what else Azure is: Vodia PBX can easily be installed onto the Azure Server.
‍

The installation of the software itself is just like installing the Vodia PBX Software 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’ll like to have on the system.

In order for the PBX to receive and send audio on your virtual server you’ll have to open some endpoints.
A 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 you’ll have multiply the number of calls by 4 to get the number of ports you’ll need.

Navigate to the Dashboard and click on ENDPOINTS and open your RTP range here.