Microsoft Teams SIP Trunk and Direct Routing

Implementing a Microsoft Teams SIP trunk is a critical step for enterprises and service providers looking to integrate legacy telephony with modern cloud communications. This technology enables seamless voice connectivity between Microsoft Teams and the Public Switched Telephone Network (PSTN) through Session Initiation Protocol (SIP), allowing organizations to leverage Teams as their primary phone system. With Microsoft Teams SIP trunking, businesses can replace traditional PBX systems, reduce calling costs, and centralize communications within a unified collaboration platform. The deployment model typically involves either Microsoft’s Calling Plans or third-party PSTN connectivity via Teams Direct Routing. Understanding the technical and commercial aspects of Teams SIP trunking is essential for VoIP providers, resellers, and IT administrators. This guide covers the architecture, configuration requirements, provider selection criteria, and wholesale opportunities tied to Teams direct routing and SIP trunking. Whether you're a carrier, MSP, or enterprise telecom manager, mastering this ecosystem opens pathways to cost-efficient, scalable voice services.

What Is Microsoft Teams SIP Trunking?

Microsoft Teams SIP trunking refers to the use of SIP-based connectivity to link Microsoft Teams with external telephony networks, primarily the PSTN. Unlike native cloud calling solutions that rely on Microsoft’s own telephony infrastructure, a Teams SIP trunk allows third-party carriers or service providers to deliver inbound and outbound voice services directly into the Teams environment. This model operates under Microsoft’s Direct Routing framework, which enables organizations to maintain control over their PSTN connectivity while using Teams as the front-end user interface for calling. The SIP trunk functions as a virtual connection between a certified Session Border Controller (SBC) and Microsoft’s cloud infrastructure, carrying RTP and SRTP media streams for voice sessions.

For VoIP providers, offering Microsoft Teams SIP trunk services means becoming a certified Direct Routing partner. This requires compliance with Microsoft’s technical specifications, including support for TLS 1.2+, SRTP, and identity verification via certificate-based authentication. The SBC must be on Microsoft’s VoIP Wholesale Forum-recognized interoperability list, which includes vendors like AudioCodes, Ribbon, and Metaswitch. Once certified, the provider can register their SBC with Microsoft’s Teams tenant, enabling secure SIP signaling over the internet. The result is a fully functional PSTN gateway that supports E.164 dialing, CLI/NCLI handling, IVR integration, and emergency calling compliance.

From a routing perspective, Teams SIP trunking operates similarly to traditional SIP trunking but with added layers of cloud identity and policy enforcement. Calls originate from Teams clients, traverse Microsoft’s media gateways, and are routed to the provider’s SBC via SIP over TLS. The SBC then forwards the call to the appropriate destination using LCR logic, often leveraging wholesale rate tables. For example, a call from a user in London to Mumbai mobile might be priced at $0.008/min when routed through a low-latency Indian gateway. Providers can offer competitive rates by sourcing termination via platforms like VOS3000 or PortaBilling, then integrating those routes into their SBC configuration.

Direct Routing vs. Microsoft Calling Plans

Organizations deploying Microsoft Teams for voice have two primary options: Microsoft Calling Plans or Direct Routing with a third-party SIP trunk. Calling Plans are subscription-based services offered directly by Microsoft, including Domestic and International plans that provide PSTN connectivity without requiring external infrastructure. These plans are simple to deploy—users are licensed, phone numbers are assigned via the Microsoft 365 admin center, and Microsoft handles all PSTN interconnectivity. However, this convenience comes at a cost premium and limited flexibility in number porting, routing policies, and cost control.

In contrast, Teams Direct Routing allows enterprises and providers to use their own PSTN connectivity through a certified SBC. This model gives full control over call routing, number management, and cost structures. For example, a multinational corporation with offices in Germany, Brazil, and Japan can use a single SIP trunk provider to manage all international calling, applying LCR to route Brazilian landline calls via a $0.0035/min wholesale route instead of Microsoft’s $0.022/min retail rate. Direct Routing also supports hybrid scenarios where some users use Calling Plans while others use SIP trunks, enabling phased migrations.

From a provider standpoint, Direct Routing creates a recurring revenue opportunity. Instead of one-time setup fees, carriers can bill per-minute usage, offer bundled minutes, or provide flat-rate unlimited calling in select regions. A Tier 1 provider might offer $0.006/min for US termination with 95% ASR and sub-150ms ACD, while a budget carrier targets emerging markets with $0.0015/min for Nigerian mobile at 88% ASR. These rates are often sourced from wholesale marketplaces like Buy VoIP Routes, where providers compare CDR accuracy, PDD, and NER before onboarding.

Another key differentiator is regulatory compliance. In countries like India and South Africa, local telecom laws require PSTN traffic to terminate through licensed carriers. Direct Routing enables compliance by allowing local providers to act as the terminating entity, whereas Calling Plans may not meet localization requirements. Additionally, Direct Routing supports advanced features such as toll fraud prevention, dynamic IVR routing, and DID aggregation across multiple vendors—capabilities not available in native Calling Plans.

Technical Requirements for Teams Direct Routing

Deploying a Microsoft Teams SIP trunk via Direct Routing demands strict adherence to Microsoft’s technical framework. The core component is a certified Session Border Controller (SBC) that acts as the signaling and media gateway between Teams and the PSTN. Microsoft maintains a published list of compliant SBCs, including AudioCodes Mediant series, Ribbon SWe Lite, and Oracle Communications SBC. The SBC must support TLS 1.2 for SIP signaling, SRTP for media encryption, and certificate-based authentication using a Microsoft-issued tenant ID and certificate thumbprint. Without these, the SBC cannot register with the Teams tenant and establish a SIP trunk.

Network topology is another critical consideration. The SBC must be deployed in a highly available configuration, ideally in active/standby or active/active mode across geographically dispersed data centers. Public IP addresses must be static and registered in DNS, with firewall rules allowing SIP over TCP/5061 and media over UDP/10,000–20,000. QoS policies should prioritize SIP and RTP traffic using DSCP markings (EF for voice, AF41 for signaling). Latency should remain below 150ms one-way, jitter under 30ms, and packet loss below 1% to maintain MOS scores above 4.0. Providers using FreeSWITCH or Asterisk as backend platforms must ensure SRTP bridging and proper ICE negotiation to avoid media asymmetry.

Identity and certificate management is handled through Azure AD. The SBC must be registered as an enterprise application with the appropriate API permissions (e.g., “Place.Call” and “Answer.Call”). A self-signed or CA-issued certificate is bound to the SBC and uploaded to the Microsoft 365 tenant. Once verified, Microsoft issues a service instance ID that the SBC uses to authenticate during registration. This process occurs every 24 hours, so certificate expiration must be monitored. Failure to renew certificates results in SIP trunk downtime, a common cause of service disruption in production environments.

From a signaling perspective, the SBC must support SIP over TLS with mutual authentication, re-INVITE for media negotiation, and proper handling of SDP attributes such as crypto tags and fingerprint lines. DTMF must be transported via RFC 2833 or SIP INFO, and early media must be properly relayed to support IVR systems. The SBC also handles number normalization, converting E.164-formatted Teams dial strings into PSTN-routable formats and vice versa. For example, a Teams user dialing +442079460018 must have the number passed unchanged to the SBC, which then applies LCR based on destination prefix.

SIP Trunk Configuration Steps

Configuring a Microsoft Teams SIP trunk involves a sequence of steps that bridge cloud identity, SBC settings, and network connectivity. The first step is enabling Direct Routing in the Microsoft 365 admin center. This requires assigning the “Phone System” license to users and enabling the “Calling Plan” or “Operator Connect” service. Next, the organization must register their SBC as a trusted voice gateway. This is done via PowerShell using the New-CsOnlinePSTNGateway cmdlet, where administrators input the SBC’s FQDN, port, and certificate thumbprint. Once registered, the SBC attempts to connect to Teams using outbound SIP over TLS on port 5061.

The second phase involves SBC configuration. On an AudioCodes device, for example, administrators create a new SIP trunk profile under “VoIP Connectivity” with the following parameters: proxy server set to sip.pstnhub.microsoft.com, transport set to TLS, and authentication mode set to certificate-based. The private key and certificate must be installed, and the SBC’s DNS name must resolve publicly. Under media settings, SRTP must be enabled with AES_CM_128_HMAC_SHA1_80 policy, and DTMF set to RFC 2833. RTP ports should be restricted to a defined range (e.g., 10,000–15,000) to simplify firewall configuration.

Third, number management is configured using New-CsPhoneNumberAssignment PowerShell commands or via the Teams admin center. Direct Inward Dialing (DID) numbers are assigned to users or auto attendants, and normalization rules are applied to ensure correct formatting. For instance, a German user with +493012345678 must have a normalization rule that converts local dialing (e.g., 3012345678) into E.164 format. These rules are stored in Teams and enforced client-side, ensuring consistent dialing behavior across devices.

Finally, routing policies are defined. Using New-CsTenantDialPlan and New-CsVoiceRoutingPolicy, administrators map number patterns to specific gateways. For example, a route matching +1* can be associated with the SBC gateway, while +44* routes use a different provider. This enables granular control over call paths and allows enterprises to route US calls through a low-cost provider while using a premium carrier for UK emergency services. Testing should include call flow validation, CLI presentation, and emergency number handling to confirm compliance.

Choosing a Teams Direct Routing Provider

Selecting the right Teams direct routing provider is a strategic decision that impacts call quality, cost, and compliance. Providers must be certified by Microsoft and listed on the official SBC interoperability matrix. Beyond certification, enterprises and resellers should evaluate providers based on ASR, ACD, PDD, and NER metrics. A high-performing provider typically maintains an ASR above 94%, ACD below 1.8 seconds, PDD under 1,200ms, and NER below 0.5%. These KPIs directly affect user experience—low ASR leads to failed calls, high PDD causes caller abandonment, and poor NER impacts emergency service routing.

Rate structure is another critical factor. Providers should offer transparent, per-minute billing with no hidden fees. Competitive rates for key destinations include $0.002/min for US landline, $0.008/min for India mobile, $0.012/min for Brazil mobile, and $0.005/min for UK geographic numbers. Providers sourcing routes from wholesale exchanges like Sell VoIP Routes can offer lower rates by leveraging volume discounts and peering agreements. For example, a provider using a VOS3000 platform can import rate tables from multiple suppliers and apply LCR to minimize termination costs.

Geographic coverage is essential for multinational organizations. A top-tier provider should offer DIDs in over 60 countries, including North America, EMEA, APAC, and Latin America. Local presence in key markets—such as Germany, Japan, and Australia—ensures compliance with local telecom regulations and supports number portability. Providers should also support emergency calling (E911, 112, 000) with accurate location mapping and callback number delivery.

Support and SLAs are equally important. Look for providers offering 24/7 NOC monitoring, real-time CDR access, and proactive alerting for service degradation. A strong SLA should guarantee 99.99% uptime, with financial penalties for non-compliance. Integration capabilities—such as API access for provisioning, billing, and reporting—enable automation and reduce operational overhead. Providers like those listed in our Best SIP Trunk Providers Compared guide offer these features with proven track records in enterprise deployments.

Wholesale VoIP Opportunities in Teams Ecosystem

The rise of Microsoft Teams SIP trunking has created significant wholesale VoIP opportunities for carriers and resellers. As enterprises migrate from legacy PBX systems to cloud-first communications, demand for certified Direct Routing providers is growing. Wholesale providers can position themselves as backend termination partners, supplying low-cost routes to front-end SIP trunk operators. Using platforms like VOS3000 or PortaBilling, wholesalers can manage thousands of routes, apply dynamic LCR, and deliver CDRs with 99.9% accuracy. For example, a provider in Singapore can source Indian mobile termination at $0.0065/min from a local operator, then resell it to a US-based SIP trunk provider at $0.0075/min, generating margin while ensuring compliance.

Resellers can bundle Teams SIP trunking with managed services, offering complete UCaaS solutions. By partnering with a certified SBC provider and integrating wholesale routes, resellers can deliver branded calling plans with competitive pricing. A Canadian MSP might offer unlimited calling to 50 countries for $25/user/month by sourcing routes via Buy VoIP Routes and using FreeSWITCH for call control. This model shifts revenue from one-time hardware sales to recurring monthly billing, improving customer lifetime value.

Another opportunity lies in Operator Connect and Teams Gateway services. While Operator Connect is Microsoft’s partner program for PSTN integration, smaller providers can act as gateway operators by certifying their SBCs and onboarding enterprise tenants. This requires investment in infrastructure and compliance, but the return is direct access to Microsoft’s global customer base. Providers can also offer value-added services such as toll fraud monitoring, call recording, and AI-driven analytics using platforms like Oasis or PortaSwitch.

The UCaaS Wholesale Opportunities for VoIP Resellers guide details how providers can scale their offerings. By integrating with Microsoft’s ecosystem, wholesalers gain access to enterprise-grade contracts, SLA-driven billing, and multi-tenant management. The key is building a reliable, scalable infrastructure that meets Microsoft’s technical bar while maintaining cost leadership in termination pricing.

Call Quality and Security Considerations

Maintaining high call quality in a Microsoft Teams SIP trunk environment requires proactive network management and real-time monitoring. MOS (Mean Opinion Score) should consistently exceed 4.0, which depends on controlling jitter, latency, and packet loss. Jitter buffers on the SBC must be tuned to absorb network variation without introducing delay. For example, a 30ms jitter buffer can compensate for most WAN fluctuations, but if packet loss exceeds 1%, forward error correction (FEC) or redundant encoding (RED) should be enabled in SRTP. Codecs also play a role—Opus at 48kHz provides superior audio fidelity but consumes more bandwidth than G.711 or G.729.

Security is equally critical. SIP signaling must be encrypted with TLS 1.2+, and media with SRTP. The SBC should enforce strict certificate pinning to prevent man-in-the-middle attacks. Network-layer protections include DDoS mitigation, SIP flood detection, and rogue registration blocking. Providers should also implement CLI validation to prevent spoofing and comply with STIR/SHAKEN in North America. For enterprises, enabling Conditional Access policies in Azure AD ensures only authorized SBCs can register, reducing the attack surface.

Monitoring tools like Microsoft Call Quality Dashboard (CQD) and third-party platforms such as Plixer or VoIPMonitor provide visibility into ACD, PDD, and NER. CQD ingests SIP and RTP metrics from Teams clients and gateways, allowing administrators to identify issues like one-way audio or dropped calls. For example, a spike in PDD from 1,000ms to 2,500ms may indicate SBC CPU overload or WAN congestion. Real-time alerts and automated failover to backup SBCs can prevent widespread outages.

Emergency calling must be handled with precision. The SBC must support location-based routing and deliver accurate callback numbers and physical addresses to PSAPs. In the EU, this requires compliance with eCall and 112 regulations. Providers should conduct quarterly emergency call tests and maintain audit logs for regulatory review. Failure to meet these standards can result in service suspension or legal liability.

Integration with Existing VoIP Infrastructures

Many enterprises already operate legacy VoIP systems such as Asterisk, FreeSWITCH, or BroadWorks, and integrating these with Microsoft Teams SIP trunking requires careful planning. The SBC acts as the demarcation point, but backend platforms must support SIP interworking, media transcoding, and number translation. For example, a FreeSWITCH server handling IVR menus must accept SIP INVITE messages from the SBC, process DTMF input, and return appropriate responses without breaking SRTP. Transcoding between G.711 and Opus may be necessary if the IVR system doesn’t support modern codecs.

Number portability is another integration challenge. When migrating from a legacy PBX to Teams, DIDs must be ported and re-registered under the new SIP trunk. This requires coordination with the incumbent carrier, LOA submission, and validation in the Teams admin center. During the transition, a dual-tenant setup may be used, where some calls route through the old system and others through Teams. SIP header manipulation (e.g., rewriting From: and To: fields) ensures consistent caller ID presentation.

For providers using VOS3000, integration involves configuring the SBC as a gateway device and setting up trunk groups for Teams traffic. LCR tables must be updated to include Teams-specific prefixes, and CDRs must be tagged for billing separation. Oasis-based platforms can automate user provisioning via API, syncing Microsoft 365 user lists with internal billing systems. This level of integration enables seamless service delivery and accurate invoicing.

Hybrid deployments are common in large organizations. A global enterprise might use Teams for employees in North America while maintaining a legacy PBX in Asia due to regulatory constraints. In such cases, the SBC can bridge Teams and the PBX using SIP peering, enabling inter-office calling without PSTN transit. This reduces costs and maintains continuity during phased migrations. Detailed guidance on similar integrations can be found in our Zoom Phone SIP Trunk Integration Guide.

Monitoring and Troubleshooting Teams SIP Trunks

Effective monitoring is essential for maintaining reliable Microsoft Teams SIP trunk operations. The primary tool for enterprises is Microsoft’s Call Quality Dashboard (CQD), which aggregates telemetry from Teams clients, SBCs, and media gateways. CQD provides insights into MOS, packet loss, jitter, and call setup times. Administrators can filter data by user, location, or gateway to isolate issues. For example, a sudden drop in MOS for users in Sydney may indicate a routing change that introduced high latency via a suboptimal SBC path.

Providers should deploy their own monitoring stack using tools like Wireshark, sngrep, or Kamailio SIP trace. Real-time SIP packet capture helps diagnose registration failures, 403 Forbidden errors, or 503 Service Unavailable responses. Common issues include certificate expiration (resulting in 403), incorrect DNS resolution (causing 408 Timeout), and SRTP key mismatches (leading to one-way audio). Logs from the SBC, such as AudioCodes’ Syslog or Ribbon’s Event Viewer, should be centralized using SIEM platforms for correlation.

Proactive monitoring includes synthetic testing—automated call generation to verify SIP trunk availability and media quality. Tools like SIPp can simulate 1,000 concurrent calls to stress-test the SBC and measure ASR and ACD under load. Threshold-based alerts should trigger when PDD exceeds 1,500ms or NER surpasses 0.5%. Automated failover to a secondary SBC ensures continuity during outages.

Troubleshooting often involves PowerShell diagnostics. Commands like Test-CsOnlinePSTNGateway verify SBC registration status, while Get-CsOnlineSession checks connectivity to Microsoft’s cloud. If calls fail, administrators should examine the SIP trace for malformed headers, missing SDP attributes, or incorrect TLS handshake sequences. Provider support teams can use these logs to identify misconfigurations and apply fixes rapidly.

The Future of Microsoft Teams VoIP

The evolution of Microsoft Teams voip is driving deeper integration with global telecom networks and expanding opportunities for providers. Microsoft continues to enhance Direct Routing with features like media bypass, which allows SBCs to reside in customer premises for reduced latency, and Operator Connect improvements that simplify carrier onboarding. Future updates may include AI-driven call analytics, real-time translation, and deeper integration with emergency services infrastructure.

For wholesale providers, the trend toward cloud-native communications means increased demand for certified, high-quality SIP trunking services. As more enterprises adopt Teams as their primary phone system, the need for reliable, low-cost PSTN access will grow. Providers who invest in certified SBCs, global route coverage, and robust monitoring will capture market share. The VoIP Wholesale Forum remains a key resource for staying ahead of industry shifts and connecting with potential partners.

Frequently Asked Questions

What is the difference between Teams Direct Routing and Operator Connect?

Teams Direct Routing requires organizations to deploy and manage their own SBCs to connect to the PSTN, giving full control over routing and providers. Operator Connect is a Microsoft-partnered program where certified carriers manage the entire PSTN integration, simplifying deployment but offering less customization. Direct Routing is ideal for enterprises with existing telephony infrastructure, while Operator Connect suits those seeking a managed solution.

Can I use any SBC for Microsoft Teams SIP trunking?

No. Only SBCs listed on Microsoft’s certified interoperability list are supported. Common models include AudioCodes Mediant, Ribbon SWe Lite, and Oracle Communications SBC. The device must support TLS 1.2+, SRTP, and certificate-based authentication to register with Teams.

How do I troubleshoot one-way audio in Teams calls?

One-way audio typically stems from NAT traversal issues, firewall blocking RTP ports, or SRTP key mismatches. Verify that UDP ports 10,000–20,000 are open, the SBC is correctly relaying media, and both ends agree on crypto keys. Use packet capture tools to confirm RTP stream direction and check for asymmetric routing.

What rates should I expect for Teams SIP trunk termination?

Rates vary by destination and provider tier. Competitive pricing includes $0.002/min for US landline, $0.0045/min for UK geographic, and $0.008/min for India mobile. Providers sourcing routes wholesale can offer lower rates by leveraging LCR and volume discounts from platforms like VOS3000.

Is emergency calling supported in Teams Direct Routing?

Yes, but the SBC and provider must support location-based routing and deliver accurate callback numbers and physical addresses to PSAPs. Providers must comply with local emergency regulations such as E911, 112, or 000, and conduct regular testing to ensure reliability.

Microsoft Teams SIP trunking represents a fundamental shift in enterprise communications, enabling organizations to unify voice and collaboration in the cloud. By understanding the technical, operational, and commercial dimensions of Direct Routing, providers and enterprises can build scalable, cost-effective telephony solutions. As adoption grows, the role of certified SIP trunk providers will become increasingly vital in supporting global Teams deployments.