Configuring your firewall for remote users is essential for enabling VoIP communications through the Vodia PBX. This setup requires allowing specific TCP and UDP ports, including 5060 and 5061 for SIP signaling, UDP ports 49152 to 64512 for RTP and TCP ports 80 and 443 for web access. Additionally, setting the appropriate IP routing entries ensures both internal and remote phones can communicate effectively, utilizing a netmask that accommodates local network traffic while allowing access from external sources. This dual configuration allows for seamless call management across different network environments.
A firewall controls the incoming and outgoing network traffic based on an applied rule set and establishes a barrier between a trusted, secure LAN and/or WAN network(s) and the internet (neither secure nor trusted).
Vodia Networks recommends a LAN architecture where the voice traffic bypasses the firewall:
If a firewall feature is configured, it must allow the following ports to pass (if you want to connect remote users to the PBX then you will need to configure the Vodia SBC settings):
Allow TCP/UDP ports 5060, 5061 (for SIP)
Allow UDP ports 49152–64512(for RTP)1
Allow UDP port 123 (for NTP)
Allow TCP port 80 (for HTTP)
Allow TCP port 443 (for HTTPS)
Vodia PBX SBC
In order to make the PBX show the public IP address, you need an entry that matches "every other IP address". In other words, the netmask must be 0.0.0.0 (for example, "0.0.0.0/0.0.0.0/123.124.125.126"). The problem is it will block all calls on the private network, so there is also a necessary rule for the private network.
Example: Let's say the PBX is running on 192.168.1.2 address, the netmask is 255.255.0.0 and the internal SIP phones have 192.168.x.x addresses. So the first part of the entry will be "192.168.0.0/255.255.0.0/192.168.1.2". This part will take care of the internal phones. Now, if the phone and PBX have to talk to remote phones and servers, then you have added another part to the "IP Routing List". Consider the public IP address is 123.124.125.126 (this the IP address provided/assigned by the internet service provider). You can check the public IP using http://whatismyip.com/), then you will have "0.0.0.0/0.0.0.0/123.124.125.126" as the other part of the entry.
Putting it all together, an entry of "192.168.0.0/255.255.0.0/192.168.1.2 0.0.0.0/0.0.0.0/123.124.125.126" will make the PBX serve both internal and remote phones.
In this example, the PBX would not look at the routing presented by the operating system.
Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.
Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.
Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.
.svg)
