Trying to understand why our custom SIP trunk integration is consistently returning 403 Forbidden during the REGISTER phase despite correct credentials. The platform_api logs show the request reaching the edge, but the auth token validation seems to be rejecting the digest response. Is there a specific clock skew tolerance or header format requirement for the platform_api v2.1.0 SDK that differs from standard RFC 3261 implementations?