Direct Routing for Teams

Here are the main reasons why organization would want to deploy Direct Routing instead of Calling Plans: 

  • Connect the PSTN trunk – One of the reasons why customers want to use Direct Routing is that the Calling Plans are not available in all regions.
  • Interoperability with third-party systems (for example, PBXs, Call Centers) – The second reason is to provide the interoperability between existing telephony PBX(s) and Microsoft Phone System.
  • Lowering Cost – by adopting Direct Routing and using host SBC, you save substantially over Microsoft Calling Plans.
  • Uniformity cross different platform – the same look and feel no matter what device/operating system is used, the same client used on Windows, MAC, Smart Phones, Tablets or even browsers.
  • Simplified IT – No VPN required, No maintenance , No hardware to install, manage or maintain.

Network component providing:

  • Connectivity – allows Teams to interconnect to other voice components (i.e.: on-Prem PBX, PSTN Gateways)
  • Security – SIP traffic over TLS and build-in firewalls to protect SIP traffic and Toll Fraud.
  • Media Services – transcoding, support for voice/video calls

Migrating Voice to Direct Routing:

  • Session Border Controller(s) is Key.
  • Microsoft Phone System License to activate Voice system and Dialpad for end user.
  • Registering SBC domains in Client Teams Tenant to established Direct Routing derived sip trunks.
  • Creating SBC in Customer Team Tenant and define priorities.
  • Establishing dial plans and dial Policies for extension calling and PSTN calling.
  • Establishing sip trunk to current phone systems.
  • Configuring call forking on-prem phone system (if required) to ring Team client simultaneously for incoming calls to end user extensions on their desk phones.

Enough Talk, Let's Build Something Together

Reach out now