Solved SSL Issue in Teams Integration

[Jeff Koertzen]

I posted some time ago that I was having trouble calling out from Teams, but I haven't been able to get that resolved yet, and as such I haven't introduced it to our users. Every call from Teams (internal or external) rings for the 10 seconds and then says the call could not be completed. No call is ever entered in the 3CX logs. (Incoming calls are routed just fine.)

While reviewing posts, I found an excellent suggestion to test the SSL cert for issues at https://www.sslshopper.com/ssl-checker.html. When I enter the FQDN we use for Teams with the 5062 port, everything returns fine except a note to upgrade the encryption type for better security (from SHA1 to SHA2). When I enter the FQDN with the 5061 port, however, the SLL returned is the one we use for our external web interface and is assigned to us by 3CX (***.ca.3cx.us).

None of the common names in the certificate match the name that was entered (***.***.com). You may receive an error when accessing this site in a web browser. Learn more about name mismatch errors.​

I'm assuming that this is the primary problem the calls aren't working. Is there something I missed in the configuration or something I can easily do to correct this?

Thanks!

 

[Jeff Koertzen]

In the FAQ, I see that I may need to update my secure SIP records. I'm checking on that now.

 

[NickD_3CX]

Hi!

This error you are getting on SSL Shopper could very well be the cause, yes.

So what this error means is that the Certificate you created is fora different FQDN than the one you are using.
If this is the case, then you have 2 choices:

a) Check for which FQDN you issued the Certificate for, and if you own that domain, create an A Record and point that to your 3CX (also enter it in the 3CX settings...)
b) Issue a new Certificate for the FQDN you are actually using.

 

[NickD_3CX]

I also sent you a PM with an alternative suggestion...

 

[Jeff Koertzen]

This issue has been resolved. Thanks.