Looking for some advice on troubleshooting this recurring SIP 408 Request Timeout issue occurring during our peak business hours in the Singapore timezone. We manage fifteen BYOC trunks across three regions, and the failover logic appears to be triggering prematurely on two specific trunks connected to our primary carrier in Jakarta. The initial INVITE request times out after 30 seconds, causing the system to attempt a failover to the secondary carrier, which then results in a 408 on the re-INVITE as well. This creates a noticeable delay of over 45 seconds before the call is either dropped or successfully routed via the tertiary path. The SIP logs show that the initial request is sent to the correct carrier IP, but no 100 Trying response is received within the expected window. We have verified that the carrier’s SIP server is reachable via telnet on port 5060, and the credentials are valid. The issue seems isolated to outbound calls originating from specific DID ranges assigned to these trunks. Is there a known threshold for SIP retransmissions in the Genesys Cloud BYOC configuration that might be causing this aggressive timeout behavior? We are currently running the latest release of the Edge software, and the carrier has confirmed they are receiving the requests but are experiencing high latency on their end. We need to adjust the timeout settings to prevent unnecessary failovers and call drops, but the standard documentation does not provide granular control over these specific SIP timer values for BYOC trunks. Any insights on how to tune these settings or if there is a known bug affecting this behavior would be greatly appreciated.