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

Monitoring Your Vodia PBX: Ensuring Continuous Communication

The Vodia PBX comes equipped with powerful built-in monitoring tools and integration options to ensure seamless, uninterrupted communication. From real-time system graphs and syslog analysis to packet capture tracking and detailed CDRs, Vodia enables proactive issue detection, performance optimization, and enhanced call quality. With support for SNMP, Prometheus, and external services like Pingdom and Site24x7, you can monitor everything from registration anomalies to system resource usage and SIP connectivity across multiple servers—all in one comprehensive solution.

May 15, 2025

Real Telecom and CallSmart Announce the Integration of the Vodia PBX with the CallSmart

Real Telecom and CallSmart have announced the integration of the Vodia PBX with the CallSmart AI communication platform, delivering a feature-rich, cost-effective voice solution tailored for modern dental and healthcare practices. The integration empowers clinics with advanced call center functionality, HIPAA-compliant data security, and seamless communication tools that reduce missed appointments and enhance patient engagement. CallSmart’s AI captures missed calls and automatically engages patients via SMS, while Vodia PBX ensures easy installation and reliable performance.

May 13, 2025

Fast and Easy: Vodia Prepaid Cloud for Microsoft Azure

Vodia’s prepaid cloud PBX solution for Microsoft Azure enables businesses to quickly deploy a fully licensed, enterprise-grade phone system without the complexity of traditional installations. Designed for speed, scalability, and ease of use, the offering supports packages for up to 80 users and includes a Teams-certified Session Border Controller (SBC) that allows seamless integration of Vodia PBX features—such as auto-attendants, call queues, and intelligent routing—directly within Microsoft Teams. Whether you’re an SMB or a growing enterprise, Vodia’s prepaid PBX is a powerful and flexible solution that’s easy to scale as your business evolves.

May 12, 2025