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 was excited to attend IT Expo 2025 in Ft. Lauderdale, where Sales Engineer Eric Altman connected with industry leaders such as Tommy Lee from Fanvil, Gary Harbeck from Dinstar, Spencer Lee from Telin, Sebastian Balan from Fidelity, Todd Weikle from Soar Communications, Steve Scott from Borderless.com, and Mitch Kahl from BCM One. The discussions highlighted the role of AI in business communications, Vodia’s Microsoft Teams-certified PBX, and our integration with Realtime AI via APIs. This event followed a strategic planning session with key partners to outline Vodia’s goals for 2025. We look forward to connecting with you at future events!
Vodia has integrated OpenAI’s Realtime API with its PBX, enabling real-time AI-powered hotel phone systems that enhance guest services. By leveraging natural speech processing, guests can make reservations, request services, and access hotel amenities in multiple languages - all through voice commands. This integration streamlines hotel operations, reduces staff workload, and improves guest satisfaction. Whether booking a room, ordering room service, or arranging transportation, AI-powered phone systems provide seamless communication and efficiency. Hotels can now offer personalized, automated experiences while maintaining reliable, high-quality service.
ConnectPlus, a fictional call center with 150 agents and 20 support team members, faced several challenges in managing its phone systems and customer interactions. The company struggled with inefficient call routing, long wait times, and inadequate reporting, especially as it relied on Microsoft Teams for internal communication. To improve operational efficiency and enhance the customer experience, ConnectPlus sought a solution that could streamline its processes across multiple devices and platforms. Integrating Vodia’s PBX with Teams provided the ideal solution, optimizing their call handling and overall communication capabilities.
.svg)
