MS Teams Direct Routing License Question

Migrate_to_ThreeSeeAches

Free User
Joined
Feb 9, 2024
Messages
11
Reaction score
3
From this link:
https://www.3cx.com/docs/manual/microsoft-365-v18/

I see the following language:
1708716085958.png
The second bullet point states:
  • Requires Microsoft 365 E5 subscription plan or Microsoft Teams + Microsoft Phone System (add-on) for those teams users that wish to call or be called.
If we want our existing MS Teams users to be able use MS Teams for both INTERNAL and EXTERNAL calling - what MS365 license option do we need? The "or" in the above bullet point seems to imply you have a choice of:

1. MS 365 E5 OR
2. MS Teams + Microsoft Phone System.

Our current license level is MS365 E3 and obviously, the goal is to try to reduce any additional licensing costs from MS.

TIA!
 

Attachments

  • 1708715927701.png
    1708715927701.png
    93.4 KB · Views: 3
The 3CX team's integration option is designed to use the team's app to provide the ability to make and take calls that are made and received through the 3cx system. It is, however, in no way related to internal calling using any team's call features. In fact, most teams' features, such as voicemail or call forwarding, need to be disabled to use the team's app with the 3CX.

What is required to integrate 3CX with teams is one of the mentioned 365 licenses plus the Microsoft Teams Phone standard license for each user that will be integrated. Or an E5 license, which has the Microsoft Teams Phone standard already included.
 
Thank you Charles. Sorry if this is really more a MS licensing question ( could they make it more confusing ? ).

For a subset of our end users - they will use the 3CX Direct Routing integration with Teams for internal / external calling. For these users, I have to get with our MS reseller and tell him I need X number of licenses upgraded and get that in my budget.

But I guess I don't understand if I should ask him for MS365 E5 or MS Teams + MS Phone System.

Since all of our users have MS365 E3 - what does one take into consideration to choose one of these options?

1. MS 365 E5 OR
2. MS Teams + Microsoft Phone System
 
If you have an M365 E3 license for all your users already, then all you need is the Microsoft Teams Phone standard license (add-on) for each of them.
 
Man - 3CX crushes it again! Thank you!
 
You are welcome also, here is the guide to the team's integration for v20: https://www.3cx.com/docs/microsoft-teams/
In the documentation you provided, it states that V20 is limited to 16 SC and greater for Teams integrations. Does this mean that when V20 upgrades become mandatory existing ENT 4 SC and 8 SC Teams will be disabled, or am I just missing something there?
 
  • Like
Reactions: eMind
Teams has numpad now after script run but calls are not coming to Microsoft. How can I fix this?
 
Teams has numpad now after script run but calls are not coming to Microsoft. How can I fix this?
Check your SSL and make sure the integration shows synced for Teams for those users.
 
  • Like
Reactions: eMind
My SSL is wildcard from Digicert and I assigned 3cx to 3cx.mydomain.com
should I create a different FQDN for teams or is it possible to use it as a 3CX sub-domain for teams SBC?
 
My SSL is wildcard from Digicert and I assigned 3cx to 3cx.mydomain.com
should I create a different FQDN for teams or is it possible to use it as a 3CX sub-domain for teams SBC?

Please see this guide regarding what is required for the certificate.
 
Please see this guide regarding what is required for the certificate.
I read many documents about the installation but I couldn't see if Teams requires a separate domain from 3CX.
 
I read many documents about the installation but I couldn't see if Teams requires a separate domain from 3CX.
Different cases:

1. Your 3CX is using a 3CX FQDN: then you need a A record under a domain that is in your Office 365 pointing to the IP of the PBX, with a dedicated (not wildcard) certificate for that A record address (ex.: teams.mycompany.com)

2. Your 3CX uses a custom FQDN, which the domain is in O365: then use the same one, no need for second hostname. Just make sure to use a non-wildcard certificate.

3. Your 3CX uses a custom FQDN, which the domain is NOT in O365: either add it and become case #2 or go to case #1.
 
I really don't understand this: I have a domain mydomain.com in O365 and I use subdomain 3cx.mydomain.com for 3cx. Can I also use 3cx.mydomain.com for Microsoft Teams Integration? Also, why is there no validation tool to verify if the certificate is appropriate? I read that some users can integrate with wildcard, but I couldn't find any clear information about this.
 
Yes, you will be able to use your 3cx.mydomain.com as the teams SBC FQDN in 3CX. Just ensure that your certificate IS NOT a wildcard certificate and is SPECIFICALLY for 3cx.mydomain.com.

I read that some users can integrate with wildcard, but I couldn't find any clear information about this.

The fact that no clear information is available about people having success about using a wildcard certificate is because it is bogus.
 
Can anyone specify which certificate should I buy? I’ve read Microsoft documentation but it’s too complex..
 
You can check here for the supported authorities from Microsoft.
 
  • Like
Reactions: eMind
You can check here for the supported authorities from Microsoft.
Hi Sir,

There is an extraordinarily lengthy list in this link. I get very confused. I had no problems installing 3CX and I'm pleased with it, but I haven't been able to figure out the SSL required for Microsoft for months. I wish someone would tell me specifically to buy this certificate and I would buy it and use it.

Best,
 
Hi Sir,

There is an extraordinarily lengthy list in this link. I get very confused. I had no problems installing 3CX and I'm pleased with it, but I haven't been able to figure out the SSL required for Microsoft for months. I wish someone would tell me specifically to buy this certificate and I would buy it and use it.

Best,
We use ssl.com in our examples, you can use them.

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

Don’t forget to add the intermediate and root certificates for the CA to the fqdn cert pem file before uploading it 3cx for the teams integration.
 

Latest Posts

Forum statistics

Threads
111,973
Messages
590,075
Members
164,895
Latest member
jasonkkrause