Hey everyone, I’ve run into a really strange issue with our BYOC trunk failover logic in the AP-SE-2 region. We are managing fifteen distinct BYOC trunks across multiple carriers, and while standard routing works flawlessly, the manual failover trigger introduces a consistent SIP 408 Request Timeout. The issue manifests specifically when the primary carrier drops the INVITE after exactly three seconds, causing Genesys Cloud to attempt a re-registration on the secondary trunk. The SIP registration holds steady, but the browser agent receives a 408 error immediately after the failover command is executed. We have verified that the SIP credentials are correct and that the outbound routing rules are properly configured for both primary and secondary carriers. The problem seems to be related to the timing of the SIP REGISTER request during the failover window. We have tried adjusting the registration interval and the retry logic, but the 408 error persists. The logs show that the secondary trunk is ready to accept traffic, but the Genesys Cloud platform does not seem to recognize this state change in time. We are using the latest version of the WebRTC softphone, and the issue is reproducible across all agents in the AP-SE-2 region. We have also checked the carrier-specific quirks and confirmed that the secondary carrier does not have any strict timing requirements that would cause this issue. The problem is not related to network latency or packet loss, as we have performed extensive testing with ping and traceroute. We are looking for a solution that allows us to bypass this 408 error during the failover process. Has anyone encountered a similar issue with BYOC trunk failover in the AP-SE-2 region? Any advice on how to adjust the SIP registration logic or the failover timing would be greatly appreciated. We need to ensure that our agents can continue to handle calls without interruption during a carrier failover event.