Just noticed that outbound campaigns utilizing our 15 BYOC trunks in AP-Southeast-1 are exhibiting severe routing imbalance, with 70% of calls hitting only three specific SIP endpoints despite weighted distribution settings. The /api/v2/outbound/campaigns endpoint returns no configuration errors, and the carrier logs show uniform registration status. Is there a known issue with how Genesys Cloud handles predictive routing load balancing across high-throughput BYOC trunk groups in this region?