Page History
Add_workflow_for_techpubs AUTH1 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYM-27124 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'}
| CSS Stylesheet |
|---|
img.confluence-embedded-image { display: inline-block !important; } |
| Panel | ||||
|---|---|---|---|---|
In this section:
|
| Note |
|---|
This Best Practice applies to deployments in Microsoft Azure only and does not apply to on-premises deployments. For on-premises deployments, refer to Best Practice - Configuring SBC Edge for Microsoft Teams Phone System Direct Routing On-Premises Deployment. |
Introduction
This Best Practice details the configuration required for an
to offer Microsoft Teams Phone System-related Direct Routing services in Microsoft® Azure™.The Spacevars 0 product3
| Spacevars | ||
|---|---|---|
|
- Third-party party PBX and subtended clients
SIP trunk from a third-party provider (PSTN)
Caption 0 Figure 1 SBC SWe Lite in Microsoft Azure offering Direct Routing Services to Teams Clients 
From the Azure public cloud, the
| Spacevars | ||
|---|---|---|
|
...
Include Page Connect SBC SWe Lite to Microsoft Teams Direct Routing Deployed in Azure Connect SBC SWe Lite to Microsoft Teams Direct Routing Deployed in Azure
...
| Info | ||||
|---|---|---|---|---|
The
*Note: Media bypass support in Azure is a planned future feature; media bypass is available for on-premises deployments immediately. |
| Note |
|---|
Microsoft Teams Direct Routing Media Bypass is not supported when the SBC SWe Lite is hosted in Azure due to the lack of static NAT support. |
Prerequisites
Deploy SBC SWe Lite in Azure Marketplace
Deploy the SBC SWe Lite in Azure Marketplace. Refer to: Running a SWe Lite via Microsoft Azure Marketplace.
...
Configure Azure for Microsoft Teams Direct Routing
Assign a Static Public IP Address on the Media Port
Assign a Static Public IP address on the media interface in Azure for Microsoft Teams Direct Routing.
| Info |
|---|
These instructions assume the SBC SWe Lite has been deployed in Azure Marketplace. Refer to Running a SWe Lite via Microsoft Azure Marketplace. |
- Connect to the Azure portal. Refer to portal.azure.com.
- From the left navigation pane, click Virtual Machines.
Click the desired VM to be used for Microsoft Teams Direct Routing.
Caption 0 Figure 1 Click on VM 
Under Settings, click Networking to open the media interface.
Caption 0 Figure 1 Select Networking 
Click on the network interface.
Under Settings, click IP Configuration.
Caption 0 Figure 1 Select IP Configuration 
- Click ipconfig1.
- Enable a Public IP address and create a new Static Public IP address on the media interface through a series of windows:
From the Public IP address settings option, select Enabled.
- Click IP address.
From the Choose public IP address window, click Create new.
From the Create public IP address window and the Assignment options, select Static.
| Caption | ||||
|---|---|---|---|---|
| ||||
|
Run Easy Configuration Wizard for Microsoft Teams Direct Routing
Run the Easy Configuration Wizard to deploy a Microsoft Teams Direct Routing scenario. Refer to the following configurations under Working with SBC Easy Configuration:
Complete SBC SWe Lite Configuration for Microsoft Teams Direct Routing in Azure
Configure IP Routing
IP Routing must be customized in the SBC SWe Lite for Microsoft Teams Direct Routing in Azure. Two options are available for configuration:
- Set the Default Route on the Media Interface.
- Add a Static Route for Microsoft Teams Direct Routing traffic to the Media Interface.
...
When using multiple NICs on the SBC SWe Lite, Azure designates the first Network's Interface as the Primary Network Interface. Only the Primary Network Interface receives a network default gateway and routes via DHCP. To assign the Network Default Route on another Subnet, you must designate another Network's Interface as the Primary Network Interface.
To assign the network default route, refer to Change Azure Default Route.
...
Add a static route for the traffic to the following IP address and Mask: 52.112.0.0/14 (52.112.0.0/255.252.0.0).
| Info |
|---|
For details on creating Static Routes, refer to Creating Entries in a Static IP Route Table. |
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Protocols > IP > Static Routes.
- Click the Create Static IP Route (
) icon at the top of the Static IP Route Table page. Add the following Static Route using your media interface:
Destination IP: 52.112.0.0
Mask: 255.252.0.0
Gateway: 10.1.9.1
Caption 0 Figure 1 Create Static IP Route 
- Click OK.
Confirm the IP Configuration
| Info |
|---|
For details on IP Interfaces, refer to Managing Logical Interfaces |
Ensure that all network interfaces are configured as follows:
...
| Caption | ||||
|---|---|---|---|---|
| ||||
|
...
Configure the Outbound NAT Traversal
| Info |
|---|
For details on Signaling Groups, refer to Creating and Modifying SIP Signaling Groups. |
| Note |
|---|
Before configuring Outbound NAT Traversal, obtain the Public IP address for your network (the Public IP address specified in the screen graphic is an example only). |
Configure the Outbound Static NAT for all Signaling Groups that use an interface with a Public IP address (at the minimum for the Microsoft Teams Direct Routing Signaling Groups).
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Signaling Groups.
- Click on the Signaling Group used for Microsoft Teams Direct Routing. For details on modifying a signaling group, refer to Creating and Modifying SIP Signaling Groups.
- From the Outbound NAT Traversal drop down list, select Static NAT.
From the NAT Public IP (Signaling/Media) drop down list, enter the Public IP Address assigned on this media port (the Public IP used in the screen is an example only; use the Public IP for your network).
Caption 0 Figure 1 Configure Outbound NAT Traversal 
...
Hosting SBC in Microsoft Azure reduces the need for Direct Routing Media Bypass (Media Bypass in Azure is not recommended but will be supported in a future release). As a result, ICE Lite and RTCP Multiplexing must be disabled on the Teams Direct Routing Signaling Group, as follows:
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to System > Signaling Groups.
Select the Signaling Group used for Microsoft Teams Direct Routing.
From the RTCP Multiplexing drop-down list, select Disable.
Caption 0 Figure 1 Disable RTCP Multiplexing 
From the ICE Support drop down list, select Disabled.
Caption 0 Figure 1 Disable ICE Support 
Click OK.
Place a Test Call
Place a test call and verify the operation via Confirm the configuration. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
Overview
Content Tools