SBC Microsoft Teams architecture is a key part of connecting Microsoft Teams Phone with external telephony through Direct Routing. In this guide, SkypeExchange4U™ explains how the Session Border Controller handles SIP signaling, call routing, security, media and PSTN connectivity in an enterprise voice environment.

The SBC is not simply a device that passes calls from one network to another. It is an important control point between Microsoft cloud voice services and the organization’s existing telephony environment.

This guide is designed for Microsoft Teams administrators, voice engineers, SBC engineers, network teams and enterprise architects who want a practical understanding of the complete call flow.

🔌 What Is an SBC in Microsoft Teams?

A Session Border Controller (SBC) is a specialized voice-network device or software platform that controls and protects real-time communications across network boundaries.

In Microsoft Teams Direct Routing, the SBC provides the controlled connection between Teams Phone and an organization’s external telephony environment. Microsoft describes Direct Routing as a capability that connects a supported customer-provided SBC to Teams Phone so organizations can use their own PSTN connectivity.

Microsoft Learn: Plan Direct Routing

🏗️ SBC Microsoft Teams Architecture

The exact design depends on the organization’s carrier, network topology, SBC platform and Direct Routing configuration. However, the SBC remains the key interconnection point between Teams Phone and the external voice environment.

🧠 How Does SBC Microsoft Teams Architecture Work?

The easiest way to understand an SBC with Microsoft Teams is to separate the call into two major components: SIP signaling and media.

📞 How an SBC Handles an Outbound Teams Call

Imagine a Teams user dialing an external telephone number.

1. The user enters the external number in Microsoft Teams.
2. Teams Phone applies the organization’s configured voice-routing policy.
3. Direct Routing sends the call toward the selected SBC.
4. The SBC receives the SIP signaling.
5. The SBC applies its configured routing and number-manipulation logic.
6. The SBC sends the call toward the carrier, SIP trunk or connected PBX.
7. The external telephone network completes the call.
8. Voice media flows according to the configured Direct Routing architecture.

Microsoft documents different Direct Routing media paths depending on the architecture, including scenarios with and without media bypass. SIP signaling continues through the Direct Routing SIP proxy.

Microsoft Learn: Direct Routing protocols

📲 How an SBC Handles an Inbound Teams Call

Inbound calling reverses the basic direction:

1. An external caller dials a Teams user’s telephone number.
2. The PSTN carrier or connected telephony system sends the call toward the SBC.
3. The SBC receives and processes the SIP request.
4. The call is routed through Direct Routing toward Teams Phone.
5. Teams identifies the destination user.
6. The Teams client alerts the user.
7. When answered, media follows the configured media architecture.

This makes the SBC an important point for both inbound and outbound enterprise voice traffic.

🔐 How Microsoft Teams Secures the SBC Connection

Security is a fundamental part of Direct Routing. Microsoft documents TLS-based SIP signaling between the customer SBC and the Direct Routing SIP proxy, along with certificate requirements for the SBC.

The SBC FQDN must be correctly configured, and certificates must meet Microsoft’s Direct Routing requirements. Administrators should verify the current Microsoft requirements before deploying or renewing certificates.

Microsoft Learn: Direct Routing planning and requirements

🎙️ What Happens to Voice Media?

Media is separate from SIP signaling. Microsoft documents RTP/SRTP-based media behavior for Direct Routing and different paths depending on whether media bypass is enabled.

With media bypass, supported Teams clients can send media directly toward the SBC rather than using the normal media-processor path. Microsoft documents specific SBC, ICE Lite, encryption and interoperability requirements for media bypass.

Microsoft Learn: Direct Routing media protocols

Media bypass should therefore be treated as an architecture decision—not simply a switch to turn on without validating firewall rules, SBC support, network paths and client scenarios.

🛣️ SBC Microsoft Teams Call Routing Explained

Teams Direct Routing uses voice-routing configuration to determine how calls are sent. Microsoft documents key components including:

• Voice routing policies
• PSTN usages
• Voice routes
• Online PSTN gateways

A voice route can contain number patterns and one or more online PSTN gateways. This allows organizations to build routing logic for countries, regions, number ranges, carriers and backup paths.

Microsoft Learn: Configure call routing for Direct Routing

❤️ How Teams Monitors SBC Health

Direct Routing uses SIP OPTIONS messages from SBCs as part of SBC health monitoring and routing behavior. This becomes particularly important in resilient deployments where multiple SBCs or gateways are available.

If an SBC is unhealthy or no longer meets the expected connectivity behavior, routing can move toward another available path according to the configured architecture.

🧩 Why Use an SBC with Microsoft Teams Direct Routing?

Direct Routing is particularly useful when an organization wants to connect Teams Phone with an existing PSTN carrier or telephony environment rather than replacing the entire voice infrastructure at once.

🏢 Example Enterprise SBC Microsoft Teams Architecture

A larger enterprise may use multiple SBCs across regions, multiple PSTN carriers, redundant network paths, Local Media Optimization, survivability options, centralized monitoring and integration with contact centers or legacy voice platforms.

Microsoft Learn: Local Media Optimization

🛠️ Common SBC Microsoft Teams Problems

🔎 Practical SBC Microsoft Teams Troubleshooting Order

1. Check the user: Confirm Teams Phone, Direct Routing and required licensing/configuration.
2. Check routing: Verify the voice routing policy, PSTN usage, route and selected gateway.
3. Check the SBC: Confirm pairing and health.
4. Check SIP: Trace the INVITE and SIP responses.
5. Check number manipulation: Verify the number format presented to the carrier or PBX.
6. Check media separately: If signaling succeeds but audio fails, investigate the media path.
7. Check the carrier/PBX: Confirm the downstream system accepted and routed the call.

Microsoft Learn: Monitor and troubleshoot Direct Routing

🏅 Which SBCs Are Supported by Microsoft Teams?

Microsoft maintains a certification program for SBC vendors and devices used with Direct Routing. Microsoft states that Teams Phone with Direct Routing is supported when using certified SBC devices. Certification is tied to documented firmware versions, so administrators should check Microsoft’s current certification list before selecting or upgrading an SBC.

Microsoft Learn: Certified SBCs for Direct Routing

Examples of vendors represented in Microsoft’s certification ecosystem include AudioCodes, Ribbon, Cisco, Oracle, Avaya and other vendors. The exact certified model and firmware combination matters more than the vendor name alone.

📋 SBC Microsoft Teams Deployment Checklist

• ✅ Confirm the SBC is Microsoft-certified for Direct Routing.
• ✅ Confirm the SBC FQDN and DNS configuration.
• ✅ Obtain a certificate that meets Microsoft’s requirements.
• ✅ Confirm SIP signaling connectivity and firewall rules.
• ✅ Plan the media path separately from SIP signaling.
• ✅ Configure voice routing policies, PSTN usages and routes.
• ✅ Test inbound and outbound calls.
• ✅ Test number normalization and caller ID behavior.
• ✅ Test one-way audio and call-quality scenarios.
• ✅ Test SBC failure and recovery scenarios before production rollout.
• ✅ Document the carrier, SBC and Teams dependencies.

❓ Frequently Asked Questions