Tech

Hosted PBX and SIP-ALG

Published on:

April 2, 2014

In 5.2.2 we’re addressing a common challenge for SIP phones in LANs that need an outbound proxy based on their location. To provide the required quality of service, devices like Edgewater VoIP routers, or even simpler routers, route SIP traffic separately from other office data. To offer more flexibility, we’ve introduced a pattern-based list for specifying outbound proxies. This allows you to define specific IP addresses, ports, and transport types for different networks. For example, if a tenant has two offices with different network setups, the domain setting allows administrators to configure outbound proxies for each office using patterns like "1.2.3.4/32/10.0.0.2" or "10.43.0.0/24/edge43.company.com:5061/tls".

Another piece in the hosted PBX puzzle we are addressing in 5.2.2 is that SIP phones in LAN often need an outbound proxy that depends on the location.

It is actually a scenario that makes sense. Using a local SIP-aware device is the ticket to providing a quality of service required by many offices. The device can be a full-blown device like an Edgewater VoIP router, but it can also be a trivial router using another DSL line. The point is the VoIP phones need to send their traffic to a specific IP address which will make sure the traffic will be routed differently from the other data traffic in the office.

To offer maximum flexibility, we are introducing a list of patterns in 5.2.2 that looks like this: src/mask/adr[:port[/transport]]. If the phone to be provisioned matches the source address src with the netmask mask, it will use the outbound proxy made of the adr:port and transport parameters. The port and the transport are optional. If they are not present, they will be replaced with 5060 and udp.

The setting is a domain setting so that customers can service themselves in hosted environments. The setting can be found in the PnP settings on the domain.

So let’s say that a tenant has two offices which have a VoIP router. The first office is at 1.2.3.4, and all traffic needs to be sent to 10.0.0.2. The first pattern would be “1.2.3.4/32/10.0.0.2”.

The second office would be in the VPN of the company using IP addresses 10.43.0.x, and the internal gateway is at edge43.company.com, using TLS on port 5061. Then the second pattern would be “10.43.0.0/24/edge43.company.com:5061/tls”. In the domain setting the administrator would have to enter “1.2.3.4/32/10.0.0.2 10.43.0.0/24/edge43.company.com:5061/tls”.

Latest Articles

View All

Why Area Codes Still Matter in a Mobile World

Even in 2025, area codes remain important for personal and business communications. People move frequently but usually keep their original phone numbers because changing them is inconvenient and tied to banking, two-factor authentication, and multiple online accounts. For PBX administrators, area codes are essential for routing calls accurately, displaying the correct caller ID, and managing costs. Vodia PBX simplifies area code management with pattern-based dial plans, automatic updates, and smart trunk selection. This ensures that calls reach the right destination efficiently, maintain a local presence to increase pickup rates, and provide reliable communication both in North America and internationally.

September 16, 2025

Keycloak OpenID Connect Integration for the Vodia PBX

Vodia’s PBX now integrates with Keycloak OpenID Connect, providing secure single sign-on for users so they can access all connected applications without repeated authentication. Logging out from one application automatically logs the user out of all connected systems, simplifying user management and improving security. Keycloak, a Cloud Native Computing Foundation project, supports standard protocols including OpenID Connect, OAuth 2.0, and SAML, offering enterprise-grade identity and access management. To ensure proper integration, Keycloak user emails must match the corresponding PBX extension emails. Complete guidance is available in the Vodia Keycloak integration guide.

September 12, 2025

Vodia Announces Partnership with Comms Group Global

Vodia Networks has announced a strategic distribution partnership with Comms Group Global (ASX: CCG), aiming to expand the reach of its feature-rich cloud PBX solutions across APAC and EMEA. Through this collaboration, Comms Group Global will serve as an official reseller, providing businesses of all sizes with scalable, secure, and integrated telephony solutions. Customers will benefit from advanced call management features, Microsoft Teams integration, and robust security standards, while also gaining access to Comms Group’s SIP coverage in over 65 countries. The partnership enables a streamlined “one-touch” provisioning process, ensuring fast and seamless deployment for enterprises and SMEs seeking to improve efficiency.

September 8, 2025