Looking for advice on handling uneven distribution across 15 BYOC trunks in Asia/Singapore. The predictive_routing module in Architect favors the primary trunk despite failover logic being enabled, causing SIP registration spikes. Any known quirks with carrier-specific load balancing?
It’s worth reviewing at the trunk health scoring weights in your outbound campaign settings. Check this guide on balancing BYOC traffic: https://support.example.com/wfm-byoc-balance
I normally fix this by checking the queue activity metrics first. The dashboard often shows incomplete data when the export job overlaps with peak traffic. Try adjusting the time window in the performance views to isolate the skew. Verify if the SIP registration spikes correlate with specific trunk health scores.