FQDN and Teams Integration

[dhill835]

Can the 3CX FQDN be used for Teams Integration or will you need our own domain? Wondering about certificates.

 

[Evolute IT]

Can the 3CX FQDN be used for Teams Integration or will you need our own domain? Wondering about certificates.

You need a FQDN that is in the TLD of one of your O365 domains.

If your PBX FQDN is a custom one, it's possible. If a 3CX one, no you cannot and you will need a separate SSL certificate (not wildcard.)

FAQ: https://www.3cx.com/docs/microsoft-teams-integration-faqs/

 

[Flo-R]

Sorry but i need to unterstand that to 100% ...

We are using 3CX onpremise. The 3CX is using the FQDN "pbx.ourcompanydomain.com". During the 3CX installation Process we've used our wildcard certificate "*.ourcompanydomain.com".

All Clients connect to the FQDN (i think they are using Port 5061 for signalling).

Can we use the "pbx.ourcompany.com" for Teams direct routing with Port 5061?

Can we go a safe way, to activate Secure SIP just for the Teams connection... but all 3CX Clients and Phones still connecting the old way through the 3cx tunnel?

If we activate SecureSIP von 5061 do we have to change the connection Settings of all 3CX Clients and IP-Phones?

 

[NickD_3CX]

This links may help you better understand:
https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.x0f836lq6dg9
https://www.3cx.com/docs/microsoft-teams-integration-faqs/#h.txihzzszti82
https://www.3cx.com/docs/microsoft-teams-business-voice/#h.y55demilnscn

In short, your main problem here is that you used a Wildcard Certificate to install 3CX.
So this means that you can't use the current FQDN as is for the Teams FQDN.

Now, if you:

• Changed the Wildcard Certificate for a single-FQDN cert
• The CA you used is from the list of supported CAs of MS: https://docs.microsoft.com/en-us/mi...g-plan#public-trusted-certificate-for-the-sbc

Then yes, you could use the same FQDN.

Also yes to your other questions, you can continue using your all 3CX Clients will continue working as they used to, via Tunnel if they are remote to the 3CX Server.