Occasional one-way audio behind dual-wan firewall
Posted: Mon Feb 01, 2016 4:14 pm
I have an Allworx 6x system that is behind a Netgear FVS336G dual-wan firewall. Our ISP that provides the SIP trunking is on WAN1 and WAN2 is a general purpose COMCAST internet-only connection to offload that traffic from WAN1. If the firewall is in the "Load Balancing" mode you have to "bind" all ports associated with Allworx calls to WAN1. Here are the current port bindings to WAN1: UDP 5060, TCP 5060, TCP 3400, TCP 8081, UDP 15000-15511, UDP 2088.
The problem is that on some (not all) incoming calls from SIP trunks, there is no audio in the incoming direction. You can't hear the person talking on the other end, and their attempt to dial an extension from an auto-attendant announcement does not get recognized. Again, this is only in the "Load Balancing" mode. If I change the firewall to only use WAN1, all calls work just fine. My conclusion is that there probably need to be additional ports bound to WAN1 in the load balancing mode but I don't see any documentation to that effect.
Since the problem doesn't always occur, since load balancing will sometimes send the ports over WAN1, that will make it work fine; but other times it will send them to WAN2 which causes the problem.
Does anyone know what additional ports I need to bind to WAN1 to solve this problem?
The problem is that on some (not all) incoming calls from SIP trunks, there is no audio in the incoming direction. You can't hear the person talking on the other end, and their attempt to dial an extension from an auto-attendant announcement does not get recognized. Again, this is only in the "Load Balancing" mode. If I change the firewall to only use WAN1, all calls work just fine. My conclusion is that there probably need to be additional ports bound to WAN1 in the load balancing mode but I don't see any documentation to that effect.
Since the problem doesn't always occur, since load balancing will sometimes send the ports over WAN1, that will make it work fine; but other times it will send them to WAN2 which causes the problem.
Does anyone know what additional ports I need to bind to WAN1 to solve this problem?