SIP 408 Timeout on AP-Southeast-1 BYOC Primary Trunk

Looking for advice on handling SIP 408 Request Timeout errors specifically on our AP-Southeast-1 BYOC primary trunks during peak hours. The secondary carrier picks up immediately, but the 5-second delay impacts our CSAT scores significantly.

We have verified that the carrier’s timeout settings are standard at 30 seconds, yet Genesys Cloud drops the leg before that threshold is reached. The failover logic works, but the initial attempt hangs too long.

Can we adjust the SIP transport timeout via the /api/v2/telephony/providers/edge/instances endpoint, or is this hardcoded for BYOC configurations?