Struggling to figure out why the primary trunk drops to the secondary carrier with a 408 Request Timeout instead of a clean 503 Service Unavailable, even though the primary carrier is confirmed down via ping tests.
This occurs on the APAC region trunks using Genesys Cloud v2023.12. The failover logic in Architect routes to the secondary, but the initial attempt to the primary hangs for 30 seconds before timing out, causing a noticeable delay in call setup.
The SIP traces show the INVITE is sent but no response is received until the timeout threshold is hit. Is there a specific keepalive or registration timeout setting in the BYOC configuration that needs adjustment to force a faster failure detection?