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.
The US Chamber of Commerce is encouraging small and midsize businesses to adopt VoIP systems for better efficiency, lower costs, and improved accessibility. VoIP enables communication over the internet instead of traditional phone lines, giving SMBs access to advanced tools like call analytics, automation, and AI. With integrations across CRMs and business apps, VoIP enhances customer experience and productivity while remaining scalable and cost-effective. Vodia Networks builds on this foundation, offering a secure, feature-rich PBX.
Vodia attended CVxExpo 2025, one of the nation’s leading IT and telecom trade shows, to connect with industry leaders and explore the latest innovations in cloud communications and AI. Eric highlighted how this year’s event focused heavily on AI adoption and shared Vodia’s commitment to integrating intelligent call routing, real-time transcription, and 24/7 availability into the Vodia PBX. These enhancements aim to simplify business communications, boost collaboration, and elevate customer experiences for enterprises and service providers.
Microsoft Teams has become a cornerstone of modern business communication, empowering over 250 million users worldwide with tools for collaboration, automation, and productivity. Yet while Teams excels at internal communication, it lacks native support for traditional phone systems and analog devices. That’s where certified integrations like the Vodia PBX come in. As a Microsoft-certified solution, Vodia bridges Teams with SIP phones, VoIP devices, and analog endpoints, enabling businesses to make and receive external calls directly within Teams.