Is it possible to enforce strict failover ordering for our 15 Singapore BYOC trunks via the /api/v2/outbound/campaigns API instead of relying on the default round-robin logic in the web UI? We are seeing inconsistent carrier selection during peak APAC hours where the secondary carrier receives traffic despite the primary trunk having healthy SIP registrations, and the current UI configuration does not expose a priority weight parameter. The specific error manifests as increased call setup time rather than a hard failure, but we need deterministic routing for compliance reporting.