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.
Vodia Wallboards gives supervisors, contact centers, service providers, and operations teams a self-hosted, real-time view of Vodia call queue activity. Monitor waiting, ringing, and active calls; agent availability; service levels; abandoned calls; and queue trends across one or more Vodia PBX systems. Start with a ready-made layout or build a custom wallboard using queue filters, live widgets, AI summaries, and alerts. Display the information your teams need in a browser, on an operations dashboard, or on a dedicated TV screen.
AI-powered calling gives businesses new ways to manage conversations, improve availability, and respond to callers more efficiently. It also introduces important questions about transparency, consent, privacy, data handling, and accountability. Organizations need clearly defined boundaries for what a Voice Agent may answer, which systems it can access, and when identity verification or human assistance is required. A thoughtful deployment balances automation with appropriate safeguards, helping businesses use conversational AI confidently while protecting callers and maintaining trust.
Yori Kasprzak, founder of Brandywine Technical Partners, joins Vodia’s Eric Altman to share how he built a multimillion-dollar business and the role Vodia has played in its growth. From cloud telephony and CRM integrations to door systems, AI and mobile workforces, he explains how Brandywine solves customer challenges with Vodia’s open platform and shares advice for partners looking to grow. His story shows how finding customer pain points can create business opportunities beyond traditional phone services.
.svg)
