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

Transforming Customer Service: Vodia PBX Integrates Seamlessly with Freshdesk

Vodia PBX now integrates seamlessly with Freshdesk, an AI-powered customer service platform used by over 73,000 companies worldwide. This integration combines intelligent ticketing and automation with enterprise-grade telephony, enabling automatic contact creation, detailed call tracking, and streamlined agent workflows. By improving call center efficiency and customer interaction management, it helps businesses enhance productivity and customer satisfaction. Vodia continues to strengthen its ecosystem with integrations to leading business software, delivering top-tier cloud PBX solutions.

July 29, 2025

Prepaid Cloud Instances: The Future of PBX Deployment

Prepaid cloud instances are transforming how PBX systems are deployed by offering a faster, simpler, and more flexible approach. With Vodia PBX now available on AWS, Azure, and DigitalOcean, businesses can launch a fully licensed, production-ready phone system in just minutes, without complicated setup or licensing delays. These preconfigured environments allow IT teams, decision-makers, and MSPs to test real-world VoIP performance, MS Teams integration, and mobile apps directly within their own cloud account. By removing traditional friction and offering full control, Vodia’s prepaid cloud instances provide a smarter and more efficient way to evaluate and deploy a modern PBX.

July 25, 2025

Vodia to Attend ChannelCon 2025

Vodia will participate in ChannelCon 2025, taking place in Nashville, TN, from July 29 to 31, with Sales Engineer Eric Altman attending on behalf of the company. ChannelCon, hosted by the Global Technology Industry Alliance (GTIA), is the premier vendor-neutral event dedicated to the worldwide IT channel. It brings together MSPs, service providers, vendors, and distributors for three days of expert panels, networking sessions, and special events designed to foster innovation and collaboration in the tech industry. Altman will highlight Vodia’s latest CRM integrations underscoring Vodia’s commitment to equipping partners with dynamic, enterprise-grade phone systems.

July 24, 2025