Quick question about the weight distribution logic in Predictive Routing when using multiple BYOC trunks. We are seeing uneven call distribution across our 15 APAC trunks despite setting equal weights in the outbound campaign configuration. The Architect flow uses a simple ‘Select Trunk’ action with no complex decision logic, just a list of trunks with weight 1.0 each.
The issue manifests as one trunk handling 70% of the load while others sit idle. No SIP errors are logged on the carrier side, and registration status is healthy across all endpoints. I suspect the predictive engine might be caching trunk availability or applying some hidden failover logic that prioritizes certain regions.
Has anyone encountered similar skew with BYOC trunks in Predictive Routing? We are using the latest Genesys Cloud API v2 endpoints for monitoring.
{
"trunk_id": "byoc_apac_01",
"calls_attempted": 450,
"calls_completed": 448,
"avg_latency_ms": 120
}
Looking for insights on how to force true round-robin or weighted distribution in this setup.