Microsoft Teams Direct Routing
Make and receive business phone calls
Organizations are already using Teams for video conferencing, file sharing and chat. Microsoft Phone System Direct Routing is the service inside of Teams that allows organizations to connect external phone lines and use Teams as an office phone system.
Switch4Teams provides the Microsoft certified Session Border Controller (SBC) required to connect Teams to a Communications Service Provider (aka phone lines).
Teams uses IP-based voice connections, commonly referred to as SIP Trunks to connect to the rest of the world. We use Ribbon’s SBCs secure these connections and assure interoperability so organizations can select from hundreds of service providers across the globe.
Organizations can use Teams for all their business calls or slowly migrate from a legacy PBX, depending on their needs. And since Teams clients work on a PC/Mac or smartphone, users can make and receive calls from almost anywhere, on any device, staying connected and productive.
What Do I Need to Get Started with Teams Calling?
Getting started is easier than you think, here are the 4 key requirements:
- Microsoft Phone System license in Microsoft 365 (typically included in the E5 package and an add-on for E3 – check your contract for details).
- A Communications Service Provider that can provide SIP Trunks for Teams (AKA a dial tone provider). SIP Trunks are the industry term for what Microsoft calls Direct Routing. If you choose a new dial tone provider, you will need to either port your existing phone numbers to the new provider or get new phone numbers (the provider can offer details and timing for each option).
- A Microsoft-certified Session Border Controller to terminate the SIP Trunks (Ribbon’s Software Edition – SWe Lite session border controller is fully certified). The SBC acts as a voice firewall and can mitigate interoperability issues.
- A trained staff member or an IT professional that can assist with set-up of the solution.
What is the SBC’s Role in Direct Routing?
Microsoft requires a certified SBC to act as bridge between Teams and the telephone network. The session border controller provides multiple functions:
- Security – it acts as a voice-aware firewall and encrypts traffic to protect the voice traffic itself and to prevent bad actors from entering the data network via the voice network
- Interoperability – not every SIP Trunking provider is identical, Ribbon’s SBCs can adjust key parameters to make set-up easy and trouble-free
- Legacy Connectivity – many organizations still have analog phones, elevator phones, door phones and fax machines. Ribbon’s hardware–based SBCs have analog ports (FXS) to keep these assets working for years to come
- Migration – often organizations want to slowly migrate to Teams, keeping their legacy PBX in place for weeks or even months or years. Ribbon SBCs can provide simultaneous ringing so that both Teams and the old PBX share connectivity.
- Resiliency or Fail over – Ribbon SBCs have multiple options to manage disruptions in service depending on the deployment model. These tools can keep your organization connected even if the unexpected happens.
Easily deploy Ribbon SBC software in the Azure Cloud
Ribbon’s Session Border Controller, Software Edition Lite (SBC – SWe Lite) can operate natively in the Azure Cloud, providing an as a service deployment model option. In minutes, an organization can deploy a Ribbon SBC to connect Teams Direct Routing to a Communication Service Provider for dial tone. There is no hardware to deploy or manage and the solution can scale up or down as needed. Ribbon even offers a 30-day trial license so your organization can try it out.
GET AN INSTANT 30-DAY FREE TRIAL
Small & Medium Business and Branch Offices
From the Cloud, Our Hardware or Your Hardware. The same capabilities, choose the deployment model that fits your needs.
Ribbon’s Session Border Controller software is designed to operate from the cloud, as a virtual instance in a data center or on Ribbon own appliance hardware. Unlike our competitors that try to force a deployment model or ask organizations to sacrifice functionality, with Ribbon the choice is yours.