3CX Integration — Microsoft Teams
The 3CX + Microsoft Teams integration lets your Teams users make and receive external phone calls through your WebTic SIP trunk, without leaving the Teams interface.
Two integration modes
Mode 1 — Direct Routing (Microsoft Phone System)
3CX acts as a certified SBC (Session Border Controller) between Teams and your SIP trunk:
- Prerequisite: Microsoft 365 license with the Phone System add-on
- Prerequisite: 3CX V18+ license (Professional or Enterprise plan)
- Benefit: PSTN calls directly from Teams (external phone)
- Cost: Microsoft Phone System license (~€8/user/month)
Mode 2 — Presence/Chat Integration (without Phone System)
3CX ↔ Teams presence synchronization and click-to-call from Teams:
- No Phone System license required
- See colleagues' availability across both systems
- Click a Teams contact to start a call via 3CX
Direct Routing configuration (key steps)
- In the Microsoft 365 Admin portal:
- Enable Phone System on user licenses
- Create an SBC domain:
sbc.votre-domaine.com - Register the SBC via Teams PowerShell:
New-CsOnlinePSTNGateway -Identity sbc.votre-domaine.com -SipSignalingPort 5067
- In the 3CX console:
- Settings → Integrations → Microsoft Teams
- Enter the Microsoft 365 tenant ID
- Generate and upload the TLS certificate for the SBC
- Configure the WebTic SIP trunk as outbound for Teams
- Assign the numbers:
- Assign a WebTic DID number to each Teams user
- Configure the Voice Routing Policy in the Teams Admin Center
Network prerequisites
- Port 5067 TCP/TLS open (SIP Direct Routing)
- Ports 49152-53247 UDP (Teams RTP media)
- Valid SSL certificate for the SBC name (Let's Encrypt compatible)
- Static public IP or resolvable FQDN for the 3CX SBC
Verifying the integration
# Test SBC connectivity from Teams Test-CsOnlineLisCivicAddress Get-CsOnlinePSTNGateway | Select Identity, Enabled, SipSignalingPort # Check the 3CX logs tail -f /var/log/3cxpbx/callcontrol*.log | grep -i teams
