Thank you very much for the explanations. I will have to digest. It sounds like I should give some more thought to how I am handling WiFi/VoIP calls versus video conferencing versus normal internet traffic.
My highest priorities are keeping WiFi calling, VoIP calls, and my video conferences going. Sounds like I might not need to use Smoothing for my Video conferences though and FEC with a Fast failover time may be sufficient. I was originally thinking of moving my cellular link to Priority two as there are two WiFi as WAN but then that would impact my WiFi calling and VoIP calls that I dont want to disconnect when/if the WiFi as WAN links degrade.
So you created several Speedfusion tunnels? One for video conferencing with FEC but not smoothing, one for smoothing, and any others? How did you section out / set rules for the video conferencing? I use Webex, Zoom, Skype, and Teams. Did you have to get all the destination IPs/hosts and create rules for them to use the sub-tunnel that only had FEC enabled?
As for enabling QoS for WiFi calling and VoIP, is that done at: Advanced > QoS > Application ? For WiFi calling, do I have to figure out the destination hosts/IPs/ports and enter those in somewhere?
Some devices that do video conferencing (i.e. computers) currently are using the Speedfusion Smoothing tunnel and the problem is not only that video conferencing eats a lot of bandwidth but those devices also stream video (Youtube, Netflix, etc). I was able to cut down on bandwidth usage by routing security cameras and dedicated streaming devices (i.e. TVs/Roku) directly through the WANs that are not cellular (and not through the Speedfusion tunnel) so that was a big improvement. Just trying to further refine things now.
As for Smoothing cap, please see this screenshot: