Does anyone know why our SIP trunk registration requests are consistently failing with a 408 Request Timeout when routed through the Genesys Cloud Edge infrastructure? We are currently integrating a premium AppFoundry solution for a client in the PST timezone that requires high-volume outbound SIP signaling. The integration relies on the platform API to provision SIP endpoints, but the actual registration packets sent to the edge are timing out before a challenge is received. The error manifests on the SIP proxy logs as a 408 followed by a immediate 403 Forbidden on retry, indicating the session was never established. We have verified that the NAT traversal settings in the Architect flow are configured for UDP and that the firewall rules allow traffic on ports 5060-5061. The issue persists across multiple tenant environments, suggesting it is not isolated to a single configuration error but rather a broader compatibility issue with the current Edge release. We are using the latest version of the SIP trunk connector and have confirmed that the OAuth tokens used for the initial API handshake are valid. The latency between our partner infrastructure and the Genesys Edge nodes appears normal, so network delay is unlikely the culprit. Any insights into specific SIP header requirements or edge routing behaviors that might cause this timeout?