Microsoft Teams Calling

Direct Routing
Abdelmonem Alaa
MWP | UC Junior Engineer
Agenda
• What is Direct Routing and when to use it
• Planning for Direct Routing
• Configuring Direct Routing
What is Direct Routing and when to use it
 [Link]
Enterprise Voice for the cloud

Office 365
The hub for
teamwork
Microsoft Phone System,
Teams when paired with
Microsoft Calling
PB Phone System Plans and/or
X Direct Routing,
provides a full
enterprise calling
experience for
Office 365 users
in Teams on a
PSTN dial global scale
tone Microsoft Direct Routing
Calling Plans in Teams
(Telco calling services)
What is Phone
System?
o Phone System is Microsoft’s Private
Branch Exchange (PBX) capabilities
in the Microsoft 365 with Microsoft
Teams.
o Calls between users in your
organization are handled internally
within
Phone Phone
System System
Features:
• Auto attendants and Call queues
• Cloud Voicemail
• Calling identity
• Call forwarding and simultaneous ring
• Common Area Phone
Direct Routing for Teams

PSTN TRUNK INTERNET Phone System

Certified Session Border
PSTN
Controller(s)
network

Analog
telephony
adapter Third-
(ATA) party PBX
(supported by
certified SBC
Partners)
Direct Routing Benefits
Leverage
Interoperability
existing Single DID for
with third-party
contracts with every user
systems
service providers

Less Hardware
Where Calling Can be Footprint
Plans not combined with (compared to
available Calling Plans Skype for
Business)
Planning for Direct Routing
Planning steps

Session
Self-deployed Licensing and FQDNs &
Border
vs. hosting Endpoints Certificates
Controllers

IP Ranges Optimize
and Ports Voice Routing Media
(Firewall) (optional)
Licensing and Endpoints
• Licensing
• Microsoft Phone System
• Microsoft Teams + Skype for Business Plan 2, if included in licensing
• Microsoft Audio Conferencing
• Required for adding external participants to scheduled meetings (dial in/dial out)
• Ad-hoc conferencing behavior dictated by this license

• Endpoint Support
• Any Teams client
• Common Area Phones
• Skype for Business 3PIP phones ([Link] for limitations)
Session Border Controller (SBCs)
• Certification process
• Validated via third-party lab
• All certified devices tested daily in pre-production environment
• Joint support process with the SBC vendors

• List of supported SBCs -

[Link]
• SBCs can be physical appliances, or
deployed in the cloud (Azure, AWS)
SBC FQDN requirements

IP: [Link] Internet Phone System

DNS Name: (Cloud PBX)
[Link]

DNS name registered in

Can be used for SBC FQDN Examples of FQDNs
Office 365 tenant
Using *.[Link] domains is not supported for SBC
[Link]
names
Valid names:
 [Link];
 [Link];
[Link]  [Link]
Non-valid name:
 [Link] (requires registering domain name
[Link] in “Domains” first)
Certificates
• Validate identity of trusted SBC
Minimize certificate cost Balance the cost Maximize security
and security
This scenario is good for companies
that do not change the gateways
In this scenario the company
This scenario is for companies that frequently.
Descriptio assigns a certificate to each
want to pair many SBCs or change In the example below. a company has
n gateway. There is only one
them frequently four SBCs ([Link]; certificate for every gateway.
[Link]; [Link];
[Link]).
Subject
[Link] [Link] [Link]
name
[Link]
[Link] [Link]
SAN *.[Link]
[Link]
[Link]

• Supported certificate authorities

• [Link]
IP ranges and ports
• SBC requirements different from client requirements
• Check SBC vendor guidance if NAT can be used
SIP signaling ports (TLS/SIP) FQDNs and IP
Destination
ranges FQDN Connection Points (in order):
From IP To IP Source port
port [Link] – Global FQDN [must be
tried first]
Defined on the [Link] – Secondary FQDN
SIP Proxy SBC 1,024 – 65,535
SBC [Link] – Tertiary FQDN
Defined on the
SBC SIP Proxy 5061
SBC
IP Address Connection Points:
The above FQDNs resolve to one of the following IPs:
SIP Proxy [Link]
Media ports (UDP/SRTP) [Link]
[Link]
Destination [Link]
From IP To IP Source port
port [Link]
[Link]
Media 49,152 – Defined on the
SBC
Processor 53,247 SBC [Link] also resolves to all above
IPs
Defined on the
SBC Media Processor 49,152 – 53,247
SBC
Recommend at least two ports per concurrent call on Media [Link]/14
the SBC.
Processors [Link]/14
Voice Routing
Voice Configuration Objects
Voice Routing Policy Dial Plan
User authorization Dialing Habits & Number patterns
Class of service

Gateway (Trunk)
PSTN Usage Number manipulation (optional)
Purpose (usage, caller’s intent) Gateway features (E-911, LBR)
Calling location
Priority

Voice Route
Called number
Cost of call
PSTN Usages
A PSTN usage record specifies a class of call (such as internal,
local, or long distance) that can be made by various users or
groups of users in an organization

By themselves, PSTN usage records do not do anything. For

them to work, they must be associated with:
Voice routing policies, which are assigned to users
Voice routes, which are assigned to gateways (SBCs)
Voice Routing Policies PSTN Usages Voice Routes

Order of Usages is critical

Usages are applied in order
Upon first match – other usages are not evaluated
Voice routing basics Usages evaluated in order
User from Netherlands
makes a call to +1 (425) Each usage can have multiple
555-1212 routes
At least one
route
Try the call via SBC(s) in
Voice Voice Routing Policy matches the
the route(s)
Routing dialed
Policy Yes pattern
exists? PSTN Usage 3

No PSTN Usage 2

User has
No match PSTN Usage 1
Microsoft
Calling
Plan?
All SBCs not
Success
Yes functional

No
Domestic
or International?

Domestic
International
only

Call via Microsoft Call via Direct

Call Failed
Calling Plan Routing
Leveraging multiple SBCs
• Load Distribution and High Availability
• Multiple SBCs can be grouped in a single voice route
• Depending on SBC vendor, multiple SBCs can be combined to cluster
• Cluster will look like single SBC to Teams

• High Availability with back-up routes

• Voice routes have priorities assigned
• Route can only be used if no SBC in higher priority route is available

• Disaster Recovery
• Voice routing policies can be used to allow only certain user to use specific routes
• E.g. after losing all SBCs in US, a subset of users can place calls to US via Europe
gateways
Summary
Thank You!