Need some troubleshooting help with a sudden failure in our Genesys Cloud BYOC Edge deployment. The integration is a Premium AppFoundry application serving multiple tenant organizations. We recently rotated the TLS certificates for the SIP trunk authentication. The rotation process completed without errors on our side. However, the Edge nodes are now failing to register with the Genesys Cloud SIP endpoints. The logs show a consistent 401 Unauthorized response. This started approximately 15 minutes after the certificate update was pushed to the configuration store. The OAuth client credentials remain unchanged. The scopes assigned to the client include edge:read and edge:write. The application is deployed in the us-east-1 AWS region. The Genesys Cloud organization is located in the us-east-2 region. We are using the latest stable release of the Genesys Cloud Edge software, version 2.4.1. The error occurs specifically during the initial SIP REGISTER request. The response body contains a standard 401 WWW-Authenticate header. No other changes were made to the network topology or firewall rules. The DNS resolution for the SIP endpoints is correct. The ports 5060 and 5061 are open and verified via telnet tests from the Edge container. We have tried restarting the Edge pods multiple times. The issue persists across all three availability zones in our cluster. It appears the Genesys Cloud platform is rejecting the certificate presented during the TLS handshake. Or perhaps the certificate chain is not being validated correctly. We have verified the private key matches the public certificate. The intermediate CA certificates are included in the bundle. This is blocking our production traffic. We need to understand if there is a specific format requirement for the certificate bundle. Or if there is a delay in the certificate propagation within the Genesys Cloud infrastructure. Any insights into the 401 response in this context would be appreciated. We are checking the Edge logs for more detailed TLS handshake information. But the current output is limited to the HTTP status code.