![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 28.999999999999996%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPV%3C/text%3E%3C/svg%3E)
10,939 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Based on the error message you provided, it seems that the SBC certificate is not issued correctly. The provided trunk FQDN '34.XX.93.132' is not included in the certificate's CN or SAN list. The certificate only allows the following FQDNs: sbc .regularadmin.online, regularadmin.online.
AudioCodes has a configuration note on connecting AudioCodes’ SBC to Microsoft Teams Direct Routing . It provides detailed instructions on how to configure the connection between AudioCodes’ SBC and Teams Direct Routing with a generic SIP Trunk.
You may also want to check Microsoft's documentation on troubleshooting SIP options and TLS certificate issues 2. It explains that the SIP proxy checks the TLS connection request and if the request is not valid, the TLS connection is closed and the SIP proxy does not receive SIP options from the SBC.
I hope this information helps you resolve the issue.
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.