3CX with Teams integration

[stefkraaijeveld]

Hello everyone. I am getting Teams integrated within 3CX. I already made an FQDN in the exact domain of the MS365 tenant. A record that points to the IP address of the PBX. I am now trying to get an SSL certificate from a Microsoft-approved vendor.

The only thing that is bothering me, is that I need to open port 5062. We are hosting the PBX at KeenSystems in The Netherlands, and the SBC locally at our Office. Where do I need to open port 5062?

Because all I know is. When the SSL cert and port 5062 are done, everything from there on should work. Of course, when using the right M365 licenses.

Thanks in advance for helping out.

 

[Evolute IT]

Open TCP 5062 on the 3CX PBX. The SBC has nothing to do with this.

Also, make sure to get a regular SSL and not a wildcard as it won't work.

 

[stefkraaijeveld]

Open TCP 5062 on the 3CX PBX. The SBC has nothing to do with this.

Also, make sure to get a regular SSL and not a wildcard as it won't work.

Okay, thanks! So it is correct that the FQDN is pointing to the PBX right?

 

[Evolute IT]

Okay, thanks! So it is correct that the FQDN is pointing to the PBX right?

Yes

 

[stefkraaijeveld]

Okay, that's one step further in the process. Is it sufficient to have the M365 Business Premium + M365 Business Voice licenses to be able to use the functions within Teams?

 

[Evolute IT]

Okay, that's one step further in the process. Is it sufficient to have the M365 Business Premium + M365 Business Voice licenses to be able to use the functions within Teams?

Business Voice doesn't exist anymore. It's now "Teams Phone System Standard". Be careful as one is with a calling plan and one is without, make sure to use the one without.

 

[Charles_3CX]

Okay, that's one step further in the process. Is it sufficient to have the M365 Business Premium + M365 Business Voice licenses to be able to use the functions within Teams?

Within the guide, the requirement mentioned here, states that to have a 365 license the team's licenses are both required

If you have a user licensed with an M365 Business Premium and the Microsoft Teams Phone standard license add-on, this will suffice.

 

[Riccardo M.]

Hello everyone. I am getting Teams integrated within 3CX. I already made an FQDN in the exact domain of the MS365 tenant. A record that points to the IP address of the PBX. I am now trying to get an SSL certificate from a Microsoft-approved vendor.

The only thing that is bothering me, is that I need to open port 5062. We are hosting the PBX at KeenSystems in The Netherlands, and the SBC locally at our Office. Where do I need to open port 5062?

Because all I know is. When the SSL cert and port 5062 are done, everything from there on should work. Of course, when using the right M365 licenses.

Thanks in advance for helping out.

Hi @stefkraaijeveld,

I'm making the same think for a our customer but I dont' undestand how to add on M365 Domain the FQDN for teams.



Could you help me? thanks a lot in advance.

 

[Charles_3CX]

Hi @stefkraaijeveld,

I'm making the same think for a our customer but I dont' undestand how to add on M365 Domain the FQDN for teams.

View attachment 37374

Could you help me? thanks a lot in advance.

This guide will help: https://www.3cx.com/docs/microsoft-teams-integration-faqs/

The fqdn you require for the teams cert and to enter in to the 3cx can have whichever hostname you want but the suffix match the email domain with your 365 tenant.

 

[Riccardo M.]

This guide will help: https://www.3cx.com/docs/microsoft-teams-integration-faqs/

The fqdn you require for the teams cert and to enter in to the 3cx can have whichever hostname you want but the suffix match the email domain with your 365 tenant.

OK,
so the new record A has to be created on our DNS provider and not on M365 -> Domains...... right?



in this way



where 188.XX.XX.XX is the IP address of our 3CX.

 

[Charles_3CX]

The domain you have in 365 is your email domain, so yes, you create an A record under this domain's DNS for a hostname for this domain, so something like teams.yourdomain.com (where 'teams' is the hostname for the A record, and yourdmain.com equates to the email domain in 365), the A record for teams.yourdomain.com will then point to your 3CX systems public IP.

 

[Riccardo M.]

The domain you have in 365 is your email domain, so yes, you create an A record under this domain's DNS for a hostname for this domain, so something like teams.yourdomain.com (where 'teams' is the hostname for the A record, and yourdmain.com equates to the email domain in 365), the A record for teams.yourdomain.com will then point to your 3CX systems public IP.

Hi,
I've continued with the integration but after to run the dial plan script via powershell (using the admin account of our M365 tenant ) and set the Set-ExecutionPolicy in Bypass:

$: Get-ExecutionPolicy -List
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Bypass
LocalMachine RemoteSigned

during this task I get a lot of string like that:


while on our teams console->Direct Routing I see that:



Our PBX is on hosted by 3CX
thanks

 

[Charles_3CX]

This indicates that the dial plan already exists.

You can try running the command.

Get-CsTenantDialPlan

Get-CsTenantDialPlan

To check if it has already created

In any case, run through the configuration and check the following guide for any troubleshooting requirements.

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

 

[Riccardo M.]

Hi @Charles_3CX,

the result of that is:

Get-CsTenantDialPlan

Identity : Global
Description :
NormalizationRules : {}
ExternalAccessPrefix :
SimpleName : DefaultTenantDialPlan
OptimizeDeviceDialing : False

Identity : Tag:3CX Dial Plan
Description : 3CX via Direct Routing
NormalizationRules : {Description=Emergency Numbers;Pattern=^(112|113|115|118)$;Translation=$1;Name=3CX Emergency;IsInternalExtension=False,
Description=Internal Calls;Pattern=^(\d{3})$;Translation=$1;Name=3CX Internal;IsInternalExtension=False, Description=National
Calls;Pattern=^(0[1-9]{1}\d+)$;Translation=+39$1;Name=3CX National;IsInternalExtension=False, Description=Mobile
Calls;Pattern=^(3[1-9]{1}\d+)$;Translation=+39$1;Name=3CX National Mobiles;IsInternalExtension=False...}
ExternalAccessPrefix :
SimpleName : 3CX-Dial-Plan
OptimizeDeviceDialing : False

I'm seeing the guide but I don't find any about tha.

thanks and have a nice day

 

[Riccardo M.]

I continued with the guide an run the last script, on 3CX console my EXT is now sync


on teams the keyboard is now available. Making some inbound/outbound calls the system seems to be OK.



while on teams something is changed