Solved 3CX Hosted to self hosted - change FQDN for Teams Routing Integration

[neil_HRC]

Hi, we have an NFR Standard license and keen to test drive the MS Teams Direct Routing feature. As I understand it this is not possible on the 3CX Hosted service where the instance currently is due to the MS approved SSL and custom FQDN. So the solution is to spin up a self-hosted option and go from there.

I have searched the forum prior and the "move" process has been covered (https://www.3cx.com/community/threads/move-from-3cx-hosted-to-self-hosted.77376/), however we will need to amend the FQDN/SSL for Teams Routing compatibility. Brain fog on how to achieve this.

If anyone could point me in the right direction that would be great!

Many thanks!.

 

[NikosT_3CX]

@neil_HRC Lets clear things up to make it easier for you
You do not need to setup a Self Hosted PBX with your own FQDN on the PBX side.
FQDN of the PBX has nothing to do with the Team SSL Certificate.
You can keep 3CX FQDN and setup your own SSL Certificate for your own domain for the Teams integration.
The only thing you will have to do after this for the Teams Certificate to work, is to point an A Record on the Public IP address of the PBX. Check here :
https://www.3cx.com/docs/microsoft-teams-business-voice/

If you want, send me a PM and I can setup an SSL Cert for your Domain free for 90 Days in order you to test this.

 

[neil_HRC]

What a donk. I've even gone over those articles previously and for some reason was fixated on the 3CX FQDN and not the MS tenant.
Many thanks for that NikosT. Ok will PM shortly re SSL cert, sounds great!

 

[NikosT_3CX]

@neil_HRC as per our PM conversation all are clear now and cert has been genrated to your email from our side for your Teams Integration so i will mark this thread as resolved.

 

[neil_HRC]

Many thanks!