Thanks for the link to the other post, it was very helpful, and your thought process on FEC vs WAN Smoothing backs up my testing with Zoom and latency specific things.
I was able to configure several profiles but ran into a couple of things:
Since my FusionHub is hosted in AWS, I had to specify specific Data Ports for additional profiles other than the original, and open those ports in the AWS security group. Very straightforward for someone like me who uses AWS every day, all day, but might trip up someone else, so just noting that here.
The real reason I was trying to use this feature is still not working, though.
I’m trying to use Outbound rules specifically for Applications as I’ve seen in SpeedFusion Cloud demonstrations/webinars.
In particular, I want to catch VoIP/Zoom traffic with a rule and send it to a FEC enabled SpeedFusion tunnel profile. Just like you, I have multiple devices/people who use Zoom constantly, and I do not want to use WAN Smoothing, eating up tons of LTE bandwidth, when a FEC tunnel + 2 second failover time is more than adequate enough.
Here’s an example of an outbound rule that simply does not work, but should:
I’ve tried it both with the source being an IP address or MAC address, and neither works. In this example above, the machine is my laptop, and I have it intercepting traffic destined for the AWS SpeedFusion tunnel, looking at whether it is VoIP of any kind (I’ve tried this, Zoom specifically, etc. - none work).
Then using Priority to send it to the FEC profile, but it never goes there.
If I change the rule to send all traffic from the host to the FEC profile (and lose the Application option) then it works fine.
I even went as far as writing an outbound rule further up in the list to send everything to the SpeedFusion default profile (rule #2 in the list) but rule #3 never ever fires.
Are these supposed to work? Am I missing a setting somewhere?