Hello Vasilis Thank you for your infoHi @Samuel Ma,
With 3CX Hosting you'll have to choose a 3CX FQDN, if you'd like custom FQDN, you'll need a PRO license and above and you'll need to self host.
Hi Vasilis Thank you very much. Do i have to warch on a important step at the Teams setup? Because i already seted it up one time but i had issues with the sync of the SBC in Temas. We cloudnt make any outgoing calls or Internal Calls:/Hi @Samuel Ma,
No, it's not a hard requirement. They don't need to be the same.
I would suggest taking this one step at a time, first get 3CX set up the way you want it to be then start the teams integration.
Hi Nick Thank you. So do i have to open the Port as well if my 3CX is Hosted in 3CX directly? My 3CX has the Domian *company.3cx.ch* and the Teams FQDN is *teams.company.com* it will work? ThxThere is only one different if the 3CX FQDN is the same as the Teams SBC FQDN.
In this case, Teams will contact your 3CX system on TCP port 5061.
If the FQDNs are different, Teams will contact your 3CX system on TCP port 5062.
This means that you will need to open this port on the Firewall between your 3CX and the Internet.
That is the only practical difference.
If your 3CX system will be Hosted by 3CX, then we have you covered, yes, port 5062 TCP will be open for you.Hi Nick Thank you. So do i have to open the Port as well if my 3CX is Hosted in 3CX directly? My 3CX has the Domian *company.3cx.ch* and the Teams FQDN is *teams.company.com* it will work? Thx
Okei great thank you. So i installed everything exactly like in the manual but i can get any connection in teams. Only incoming calls are working in teams outgoing calls ar not possible.If your 3CX system will be Hosted by 3CX, then we have you covered, yes, port 5062 TCP will be open for you.
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.