To set up the Vodia PBX on Google Cloud, start by creating a VM instance in Google Cloud's Compute Engine - choose a region, zone and a compatible operating system, like Debian. Once the instance is running, configure firewall rules to allow essential ports, such as 80, 443 and SIP-specific ports (5060/5061) to enable communication. Use SSH to install the Vodia PBX by downloading and executing the installation script. After installation, configure the Vodia PBX login, then adjust IP routing settings to recognize the Google Cloud NAT by specifying internal and external IPs. This setup helps you effectively run the Vodia PBX in a cloud environment with secure, remote access and full functionality.
In this blog, we will cover the basic steps for setting up the Vodia PBX with Google Cloud. If you don’t have a google account, you can sign up at https://cloud.google.com/ and get $300 to spend on Google Cloud Platform over the next 12 months!
Once you have access to your Google Cloud, navigate to (Compute Engine) to create a VM.
Click on create
Setting up your VM
Name Your instance (lower case) no spaces
Choose your region and zone
Machine configuration (choose General-Purpose)
Building your instance
Choose your operating system (for this tutorial we are using Debian). You can use Windows or any other Linux flavor.
Service Account (Choose Compute Engine default service account)
Access Scope (Choose Allow default access)
Firewall Setting (Choose Allow HTTP traffic and Allow HTTPS Traffic)
When done, click create.
Running instance
Now that the VM is running, Google has provided us with internal IP and external IP addresses. These IP addresses will be assigned to the Vodia PBX to determine the audio packets.
Edit the firewall
Next, we are going to set up the firewall on Google Cloud.
Click on your instance as shown below.
Next, scroll down to (Network details) and click on (View details)
In the right-hand panel, choose (Firewall rule).
Create Firewall Rules
Click on (default-allow-internal)
Change the IP source address from to 10.128.0.0/9 to 0.0.0.0/0 and save.
This will take care of the following ports:
80 (TCP)
443 (TCP
5060 (UDP)
5061 (TCP)
RTP Ports 49152- 64512
LDAP Ports 2345-2346
Installing the Vodia PBX Phone System
To install the Vodia PBX, we need to log in with SSH. To do this, click on the SSH drop down and choose (open in the browser window).
Allow login only from listed address ( is optional)
Save the password in a safe place
Behind NAT
Since Google Cloud is behind NAT, we need to program the Vodia PBX to use the external IP address of the VM. The (IP Routing list) in the Vodia PBX is used to override the operating system IP routing table (this setting will be consulted by the system before consulting/using the operating system).
To check your internal/external IP address, click on the three-line icon and scroll down to (Compute Engine).
In this example, my internal IP is 10.150.0.2 and my external IP is 35.236.234.40
Legacy phone systems may still work, but they often come with hidden costs, limited scalability, and little support for hybrid work. Aging hardware, ongoing maintenance, and rigid infrastructure can quietly hold businesses back as they grow. Cloud-based VoIP systems remove these constraints by reducing telephony expenses, improving flexibility, and enabling teams to communicate seamlessly from anywhere. For many organizations, modernizing business telephony is no longer optional, it is a practical step toward efficiency and resilience.
A streamlined integration connects the Vodia PBX with the ElevenLabs Voice AI Platform using a lightweight IVR JavaScript script and native SIP REFER for call transfers. Audio and call control are handled entirely through standard SIP signaling, while all conversational logic, prompts, voice selection, and routing rules are configured in the ElevenLabs dashboard. This approach removes the need for webhooks or WebSocket connections and keeps the PBX side intentionally minimal, making the deployment clean and production-ready.
Multi-tenant architecture allows MSPs to manage multiple customers efficiently on a single, secure PBX while maintaining strict tenant isolation. By sharing infrastructure, MSPs can reduce operational costs, apply updates and security patches centrally, scale customers on demand, and onboard faster without increasing complexity. As cloud and SaaS models continue to dominate, a well-designed multi-tenant phone system provides the control, flexibility, and reliability MSPs need to support growth, evolving requirements, and modern communications workloads.
.svg)
