You can use Call Analytics, which provides standard SIP codes to help you with troubleshooting.
However, Call Analytics can only help when calls reach the internal components of Direct Routing and fail. In case of issues with SBC pairing or issues where SIP "Invite" was rejected (for example, the name of the trunk FQDN is misconfigured), Call Analytics will not help. In this case, refer to the SBC logs. Direct Routing sends a detailed description of issues to the SBCs; these issues can be read from the SBC logs.
About how to use Call Analytics to troubleshoot poor call quality, please focus on Troubleshoot user call quality problems part in this link.
Moreover, Direct Routing Diagnostic Tool is another choice. For more information, please refer to Direct Routing Diagnostic Tool section in this article.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.