In the example below it looks like the outbound rules are not working. They have been ok for a long time. Upgraded to 7.1.2 recently so I’m suspecting thats where the issue is.
LAN 10.60.12.229 is our Asterisk server. All outbound traffic must go through one WAN for authentication on the other end. I normally do this with a simple outbound rule, source=10.60.12.229, algorithm=priority, WAN=Frontier. By using Priority the system still works if that WAN goes down. It doesn’t matter which WAN we use, as long as its not split.
We’ve been having trouble with outbound calls. The call will initiate but there is no audio. This usually means the RTP stream is not getting there, which is ports 10,000 - 20,000. Ports should not matter because my rule above prioritizes all ports from that LAN address. In spite of that rule, I found that some outbound traffic from that device was going to WAN:Frontier, and some was going to WAN:Cable.
I changed the rule to enforced. That should do it, right? Nope, still had the same problem.
I added rules for the ports as shown below. Even with these backup rules, the outbound sessions are being split between the WAN ports. I believe this is a bug in the new firmware.