Encountering intermittent 408 Request Timeout errors during SIP trunk registration attempts from a Genesys Cloud Edge node located in the UK South region. The edge is running the latest stable release, but the registration packets seem to stall before reaching the core Genesys Cloud SIP endpoint.
This is particularly problematic because the SIP headers include a custom X-Correlation-ID intended to map the telephony session directly to a ServiceNow incident created via a parallel Data Action. When the registration fails, the subsequent media path negotiation also collapses, resulting in a complete call drop before the agent screen pop can trigger.
Has anyone observed similar latency issues with BYOC deployments in the London timezone? We have verified that the firewall rules allow outbound UDP on ports 5060-5080 and that the edge health dashboard reports no packet loss. The issue appears to correlate with peak traffic hours in GMT, suggesting a potential bottleneck in the edge-to-core handshake mechanism rather than a local configuration error. Any insights into debugging the SIP signaling flow between Edge and Core would be appreciated.