Teams Phone Overview :
Before we begin defining steps to plan for direct routing , this is an overview of teams phone :
1 -Core call Control and infra which is cloud based call control by teams phone PBX
2 - PSTN service provider and phone numbers : 3 choices ==> direct routing , Operator Connect , Microsoft calling plans.
3 - Devices and endpoints .
What is Direct routing :
Bring your own operator and infrastructure :
Directly route dial tone to Teams users
Connect SIP trunks directly from their network. Customers can work with their local Telecommunications provider to enable Microsoft Teams users to make and receive telephone calls. No porting required – Keep your numbers
Interoperability with 3rd party systems
Direct Routing allows customers with users in the Microsoft cloud to continue using 3rd party systems such as PBXs, Call Center, and Analog Telephony Adaptors (ATA) helping preserve key investments
Direct Routing benefits
Planning for Direct Routing :
Direct Routing considerations
Service numbers
Designed to handle high concurrency of calls
Call queues, auto attendant – supported through Direct Routing
Conferencing – not available through Direct Routing (except in GCC-H/DoD)
1.Dial in numbers are provided by the conferencing service (Microsoft numbers)
2.Dial back from a conference will be initiated from the conference bridge (not through Direct Routing)
Dynamic emergency calling
Available for Calling Plans and Direct Routing
Direct Routing requires additional emergency routing service provider: https://aka.ms/dr-sbc
See https://aka.ms/TeamsAcademy for deep-dive session
Emergency calling
Works different from traditional telephony
Direct Routing requires additional Emergency Routing Service Provider: https://aka.ms/dr-sbc
Need to acknowledge and provide notice to users
•Teams might not know the actual location of a caller
•If the user's device has no power, no calls will be possible
•Emergency calls should not be made if user is outside their office country/region
Details: https://aka.ms/emergency-calling
See https://aka.ms/TeamsAcademy for deep-dive session
Planning steps
Direct Routing deployment options
Direct Routing allows for Hosted SBC model and Multi-tenancy for scale
Customer premises model
The SBC is deployed at the customers premises
An SBC is connected only to one tenant
SBC hosting model
A carrier hosts an SBC in their datacenter / Azure
One SBC interconnected to one or many tenants
Self-deployed vs. hosted SBC
Direct routing allows for hosted SBC model
Allows partner to offer single or multiple SBCs with single certificate to multiple customers
Checklist for partners
Currently no certification program from Microsoft
Be sure you understand cost structure, support process, partner architecture and to test for quality
Customer self-deployment planning model
Requirements to each involved party:
!!!! the Configuration and support includes interaction between four entities: Microsoft, SBC vendor, customer support and consultants, carrier .
SBC hosting option 1: Carrier also provides the data services
Requirements to each involved party:
SBC hosting option 2: Carrier only provides the telephony
Requirements to each involved party:
Licensing and endpoints
Licensing
Microsoft Teams Phone
Microsoft Teams + Skype for Business Plan 2, if included in licensing
Microsoft Audio Conferencing*
1.Required for adding external participants to scheduled meetings (dial in/dial out)
2.Ad-hoc conferencing behavior dictated by this license
Endpoint support
Any Teams client
Common area phones Skype for Business 3PIP phones (https://aka.ms/3pip for limitations)
Session Border Controllers (SBCs)
Network component providing:
Connectivity – allows Microsoft Teams to interconnect to other voice components [B2BUA]
Security – firewall for SIP traffic
Media services – transcoding, support for voice/video calls
Hope It gives you a larg idea about this offer .
Comments