Microsoft Teams Direct Routing SBC
Yeti Switch acts as a Microsoft Teams Direct Routing SBC, letting service providers deliver calling services — call routing and phone numbers — to customers on the Microsoft Teams platform.
Microsoft Teams Direct Routing Configuration guide
Features for Teams Direct Routing
- Standards-based interconnect — TLS signaling and SRTP (SDES) media to
sip.pstnhub.microsoft.com, with SIP OPTIONS keep-alive so Teams keeps the trunk active. - Multi-tenant — connect multiple Teams tenants to one SBC with a wildcard certificate and per-tenant domain routing.
- Bring your own carriers — route Teams calls to any SIP trunk or PSTN provider through Yeti's routing plans and least-cost routing.
- Billing included — rate and bill Teams calls in real time on the same platform, with detailed CDRs for every call.
- Carrier-grade — runs behind the Yeti load balancer for high availability and TLS termination.
- Open source — public packages, source code and documentation.
Explore the related documentation: SIP OPTIONS Probers · Gateways · Customer Auths · Configuration guide
Frequently asked questions
Can Yeti Switch act as an SBC for Microsoft Teams Direct Routing?
Yes. Yeti Switch works as a Session Border Controller for Microsoft Teams Direct Routing, connecting Teams Phone to your SIP trunks and PSTN carriers over TLS with SRTP media.
Does Yeti support multi-tenant Microsoft Teams Direct Routing?
Yes. A single Yeti deployment can connect multiple Microsoft Teams tenants to the same SBC using a wildcard TLS certificate and per-tenant domain routing (X-RR-Domain).
Is Yeti Switch an open-source Teams Direct Routing SBC?
Yes. Yeti Switch is open-source software. The same platform that handles Teams Direct Routing also provides least-cost routing and real-time billing.