Microsoft recently unveiled the latest options for enabling voice in Microsoft Teams using a new method “Direct Routing”, previously tagged as “bring your own trunk (BYOT).
Why this is more attractive is there will be no requirement of maintaining any kind of on-premises service components that SfB used such as an on-prem SfB pool or a Cloud Connector Edition as the minimum.
This capability will allow customers to choose a certified Direct Routing for Microsoft Teams (subject to availability in countries) which could be preferred Sip provider of a customer or use a certified Session Border Controller (SBC) from a vendor such as Audiocodes or Ribbon Communications.
The first method simply provides the flexibility of choosing a preferred Sip provider opposed to the default Microsoft PSTN offering.
But, in reality, it will be difficult and challenging to transform on-prem telephony to a direct route over night due to the technical limitations and specific customer telephony requirements being built-up over the time.
So, using a certified SBC would be the best options for established businesses to transform their telephony with peace of mind.
The SBCs may be the ideal option if you have;
- a significant investment on a contact center solution which needs to be intact but not to be excluded (inter-op)
- specific anloag services such as Fax, boom gates, fire alarms, doors etc.
- an existing SfB/Lync enterprise voice environment with multiple number ranges
- established Auto Attendant and Response Group based services to be available during the transformation
- specific number presentation/manipulation requirements
The bottom line is SBCs are relatively cheap appliances and has been in the market ever since Sip services’ existence, so it is proved tech we can leverage in many ways.
Note: Microsoft Teams is rapidly evolving as I write this post and we expect to see the feature parity gap is closing by the time of General Availability of the service.