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

SMBs: Never Miss a Call with the Vodia Phone System

Missing a call is never just a minor slip for SMBs. It can mean losing a customer for good. In today’s competitive landscape, businesses cannot afford missed opportunities. While legacy phone systems often lead to frustration and inefficiency, modern cloud solutions like Vodia PBX make it easy to stay connected anytime and anywhere. With AI powered features such as intelligent call routing, real time transcription and 24/7 availability, your customers will always reach the right person. Vodia gives SMBs enterprise grade communication without the enterprise price tag so you can protect revenue, strengthen customer trust and grow confidently.

October 27, 2025

Boost Call Center Performance with Vodia’s Enhanced Analytics Dashboard

The Vodia Enhanced Analytics Dashboard empowers call centers and enterprises to transform raw call data into clear, actionable intelligence. With real-time and historical metrics on agent performance, call volumes, abandonment rates, wait times, and routing efficiency, it delivers a complete view of communication activity across locations. These insights help identify peak traffic periods, uncover CX gaps, optimize staffing strategies, and improve service quality. By reducing missed and abandoned calls, organizations can deliver faster, more consistent support and strengthen customer loyalty.

October 24, 2025

Strengthening PBX security: Passkeys and the Vodia Phone System

Vodia PBX strengthens security with passkeys, giving users and administrators a secure, passwordless login method that eliminates many vulnerabilities tied to traditional credentials. Passkeys use public key cryptography, storing the private key on the user’s device and the public key on the server, making them resistant to phishing and credential theft. By reducing reliance on passwords, Vodia minimizes the attack surface in cloud environments and makes authentication simpler and more secure, while ensuring a smoother, faster login experience for all users.

October 21, 2025