Can anyone clarify the expected behavior when a SIP trunk fails to register due to network latency spikes in the European data center?
We are experiencing intermittent 408 Request Timeout errors when our SIP provider attempts to re-register trunks to Genesys Cloud during peak load periods. The issue primarily affects the Frankfurt region endpoints, causing inbound call routing failures for approximately 15 minutes each morning. Our network team has confirmed stable connectivity and low jitter on their side, but the Genesys Cloud performance dashboard shows a spike in ‘Reg Failed’ metrics without corresponding API logs. The SIP trunk configuration uses standard TLS 1.2 with mutual authentication, and the registration interval is set to 3600 seconds. Despite increasing the timeout threshold on our side, the 408 errors persist. We need to understand if this is a known limitation of the cloud infrastructure or if there is a specific diagnostic tool available to trace the SIP OPTIONS requests before they timeout. The impact on our SLA is significant, as these failures result in lost inbound contacts during critical business hours.