SIP TLS Certificate Rotation Impact on AP-Southeast-1 BYOC Trunks

Context:
Managing 15 BYOC trunks across regions, with a heavy cluster in AP-Southeast-1. We are attempting to align our security compliance reporting with recent carrier-level certificate rotations. The environment is Genesys Cloud, and we are using the standard SIP trunk configuration. The timezone is Asia/Singapore.

Question:
Trying to understand why the analytics reporting for these trunks shows a discrepancy in call success rates post-rotation. Is there a specific API endpoint to verify the TLS handshake status for individual BYOC trunks without triggering a full failover test?