SSL Mismatch Question

[Ocean Support]

hi there,
We're trying to set up Teams Direct Routing.
We're currently hosting our system through 3CX.

We have created a sub domain called
teams."ourdomain"

We have then created an “A” record to point to the IP address of our hosted solution.
We have purchased an SSL through SSL.com as advised through the 3CX guide and generated a CSR.

We have had a Cert generated and uploaded it to the system. The security doesn’t appear because its stating that there is a mis match.

It states
Domain Matching
Your SSL certificate does not match your domain name!
Protected Domains:
"our domain".3cx.uk

It has the common name being
Common name: "ourdomain".3cx.uk
SANs: "ourdomain".3cx.uk
Valid from October 30, 2024 to January 28, 2025
Serial Number: 037472fae4339d627b895d70fe6cfb4dddc1
Signature Algorithm: sha256WithRSAEncryption
Issuer: R10

We have no access to the FQDN "ourdomain".3cx.uk but as the A record of the original sub domain is pointing via an A record to the IP address of "ourdomain".3cx.uk its always going to cause the security issue.

Please can someone tell me how we get past this
Thanks

 

[Charles_3CX]

You do not need to access the system using the Teams FQDN. The Teams FQDN and the A record you created are solely for Microsoft’s side to route traffic back to the 3CX system and are used only for the SIP/TLS portion of the communication.

To access your system, you should use the FQDN configured for the 3CX system specifically for HTTPS.