Using VoIP with Untangle Server
VoIP is bypassed in Bypass Rules by default so VoIP works "out of the box". Whether your Untangle Server is a bridge or gateway, Untangle scans all packets in order to protect your network. VoIP packets are very time-sensitive, so generally it is not desirable to scan them.
There are essentially a few VoIP implementations:
- Typical LAN phone → ATA → Ethernet → Router (Untangle Server) → Internet → VOIP Service Provider
- IP phone hardware → Ethernet → Router (Untangle Server) → Internet → VOIP Service Provider
- IP phone hardware → Ethernet → Router (Untangle Server) → Internet → Router → Ethernet → IP phone hardware
- IP phone software → Ethernet → Router (Untangle Server) → Internet → Router → Ethernet → IP phone software
Separate voice and data networks are ideal in any configuration, but Untangle recognizes that users don't have the luxury of dedicated networks. It's not uncommon to have an Untangle Sever between IP phone hardware or software. Bypass Rules and QoS provide solid support for VoIP over a shared internet connection.
In some cases your service provider might prevent you from using VoIP. As a result, some non-Untangle users resort to creating VPN tunnels between the caller's router and the sender's router. When you choose a service provider, choose one that supports VoIP. Untangle Server has a great VPN product, but VoIP over VPN produces poor results (for example, dropped calls). However, if you want to use VoIP over OpenVPN, Untangle wants to help improve your experience, so let us know if you have any difficulties, and we'll help you out.
To learn about VoIP, go to voip-info.org.