SIP Trunking with Microsoft Teams: Complete Guide
Microsoft Teams has become the default collaboration hub for millions of businesses worldwide. But its built-in calling capabilities come with a catch: Microsoft's Calling Plans are expensive, geographically limited, and lock you into a single vendor. SIP trunking for Microsoft Teams solves all three problems. By connecting your own SIP provider to Teams via Direct Routing, you gain enterprise-grade PSTN calling at a fraction of the cost — without sacrificing any functionality.
Why Connect SIP Trunking to Microsoft Teams?
Microsoft offers two paths to PSTN calling in Teams: its own Calling Plans and Direct Routing. Calling Plans are convenient but carry per-user monthly fees that escalate quickly at scale, and coverage outside North America and Western Europe remains inconsistent.
Direct Routing lets you bring your own SIP trunking provider, which means you control your carrier relationships, your pricing, and your number inventory. For businesses already running a legacy PBX or a dedicated SIP provider, this approach also preserves existing infrastructure investments while migrating collaboration to the cloud.
How Microsoft Teams Direct Routing Works
Direct Routing is Microsoft's certified framework for connecting third-party SIP trunks to the Teams Phone System. The architecture involves three core components:
- Session Border Controller (SBC): A certified SBC sits between your SIP provider and Microsoft's Teams infrastructure. It handles protocol translation, security, and media routing. Popular certified SBCs include AudioCodes, Ribbon, and Oracle.
- Microsoft Teams Phone System license: Each user who needs PSTN calling must hold a Phone System add-on license (included in some Microsoft 365 E5 plans).
- SIP trunk from a qualified provider: Your SIP trunking provider delivers the actual PSTN connectivity. The SBC connects to both the provider's SIP infrastructure and Microsoft's Direct Routing interface.
Traffic flows as follows: an outbound call from Teams passes through the SBC, exits via your SIP trunk to the PSTN, and terminates at the destination. Inbound calls reverse the path. The SBC handles all necessary SIP signaling and media negotiation.
Step-by-Step Setup Overview
Configuring SIP trunking with Microsoft Teams Direct Routing involves several well-defined steps:
- Obtain a certified SBC. Review Microsoft's published list of certified SBC vendors and models. Choose hardware or a virtual appliance sized for your concurrent call volume.
- Assign a public FQDN to the SBC. Microsoft requires a publicly resolvable fully qualified domain name for the SBC, with a valid TLS certificate from a trusted CA.
- Configure the SBC in the Teams Admin Center. Navigate to Voice > Direct Routing and add your SBC's FQDN. Set the SIP signaling port (typically 5067 for TLS).
- Create voice routing policies. Define PSTN usages, voice routes, and dial plans that map phone number patterns to your SIP trunk. Assign policies to users or groups.
- Provision users. Enable Phone System for each user, assign a phone number, and apply the appropriate voice routing policy.
- Test and validate. Place test calls in both directions, verify media quality, and confirm failover behavior if you have redundant SBC nodes.
Choosing the Right SIP Provider for Teams
Not every SIP trunking provider is equally suited for Teams Direct Routing. When evaluating options, prioritize providers that offer:
- Verified interoperability with your chosen SBC platform
- Elastic channel capacity that scales without hardware changes
- Geographic number coverage matching your office locations
- Low-latency interconnects to Microsoft's Azure network endpoints
- Clear SLAs covering uptime, call quality (MOS scores), and failover response
A provider experienced specifically in SIP trunking Microsoft Teams deployments will have pre-built SBC configuration templates that dramatically reduce setup time and troubleshooting cycles.
Common Pitfalls and How to Avoid Them
Even well-planned Direct Routing deployments hit predictable obstacles. The most common include:
- Certificate mismatches: Ensure the SBC certificate's Subject Alternative Name exactly matches the FQDN registered in Teams Admin Center.
- Firewall misconfiguration: Microsoft publishes specific IP ranges and ports for Direct Routing. Blocking any of these will silently drop calls. Whitelist all required ranges on both SBC-facing and internet-facing firewalls.
- Codec negotiation failures: Teams supports G.711, G.722, and SILK. Confirm your SBC and SIP provider support the same codec set and that transcoding is enabled as a fallback.
- Dial plan gaps: Incomplete normalization rules cause calls to fail or route incorrectly. Test every number format your users are likely to dial, including international prefixes.
Cost Analysis: SIP Trunking vs. Microsoft Calling Plans
For a 200-user organization, Microsoft's Domestic Calling Plan runs approximately $12–$15 per user per month in the US, totaling $2,400–$3,000 monthly for PSTN access alone. A comparable SIP trunking deployment using metered channels typically costs $400–$800 per month depending on call volume, with per-minute rates well below Microsoft's bundled pricing.
The SBC represents a capital or subscription cost, but most deployments recover that investment within 6–12 months. For businesses with international calling requirements, the savings are even more pronounced since SIP providers offer competitive international rates that Microsoft's Calling Plans cannot match in most markets.
Getting Started with Your Teams SIP Integration
The combination of Microsoft Teams' collaboration features and purpose-built SIP trunking infrastructure gives enterprise communications teams the best of both worlds: a modern, cloud-native interface for users and carrier-grade telephony economics for finance teams. Whether you're migrating from a legacy PBX, consolidating multiple office phone systems, or simply reducing your Microsoft licensing spend, Direct Routing is a proven, scalable path forward.
Start by auditing your current call volumes, number inventory, and geographic requirements. Then select a certified SBC and a SIP provider with demonstrated Teams expertise. With the right partners, a full Direct Routing deployment can go live in days — not months.