TLS not working on custom FQDN - Teams Integration

[Abid Ur Rehman]

TLS not working with custom FQDN although crt and pvt key matches and SSL is working fine on 3cx server. I want to integrate 3cx with teams for direct routing. Any urgent help will be appreciated.

 

[Evolute IT]

Are you using a wildcard cert?

 

[Abid Ur Rehman]

Yes, it is wildcard cert

 

[SweetAction]

According to 3CX wildcard certs are not supported (see:https://www.3cx.com/docs/microsoft-teams-business-voice/#h.2umq7yor8uhb)


I've never understood this as I have been doing Direct Routing (with other SBC devices not 3CX) with wildcard no issue, but it's a possible cause.

Do you have any errors or logs?

 

[Abid Ur Rehman]

Thanks but In the same thread I found this
So Wildcard are supported. The TLS connection has eventually started working but I am still getting warning on SIP OPTIONS

 

[SweetAction]

Your screenshot is of the Microsoft docs. My screenshot is of the 3CX docs.

I already said that I don't know why 3CX says wildcards are not supported - with other Teams Direct Routing SBCs I use wildcards with no issues. I'm saying that 3CX's Teams Direct Routing SBC implantation might have some issue with it - I don't know - so with the information you've provided so far all I can do is guess that's the cause.

If you have any logs of errors that can shed more light here we can help more.

Errors on SIP options often go away after some activity is passed on the connection. For example, here is a non-3CX SBC status from 1 minute ago:

Is the connection working?