Stuck on a recurring SIP 408 Request Timeout issue affecting three of our 15 BYOC trunks in the APAC region specifically during the 08:00-09:00 SGT peak window. The outbound routing logic prioritizes these trunks for high-value campaigns, yet the Genesys Cloud Admin Console shows SIP Status: Registered while the carrier logs indicate successful 200 OK responses to REGISTER requests. However, when INVITE messages are sent, the timeout occurs before the 100 Trying response is fully processed by the Genesys edge. We have verified that the SIP Options ping interval is set to 30s and the Keep Alive method is SIP Options, which should be sufficient. Is there a known limitation with the GET /api/v2/trunks/{trunkId} endpoint regarding real-time health checks versus actual media path availability? We are seeing a discrepancy where the API reports healthy but calls are dropping. Has anyone encountered similar behavior with specific carriers like Telstra or Singtel when using BYOC? We are considering adjusting the failover logic to bypass these trunks after 2 consecutive failures, but want to ensure we are not masking a deeper configuration issue related to SIP credentials or outbound routing rules.