Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | CHOR-3579 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
---|
|
CSS Stylesheet |
---|
img.confluence-embedded-image { display: inline-block !important; } |
Overview
This document details the configuration required for an to offer Microsoft Teams Phone System-related Direct Routing services in Microsoft Azure. The
can be used to connect an enterprise's Teams clients to:
From the Azure public cloud, the
offers the same features offered in an on-premises deployment (based on Microsoft®, Hyper-V®, VMware® vSphere® ESXi, or Linux® KVM) in support of Direct Routing, such as:
- Security: Call encryption/decryption, denial-of-service (DoS)/distributed DoS attack neutralization, and protection from toll fraud.
- Interoperability: Call mediation services to connect Teams certified clients to non-Teams clients, including popular 3rd party SIP trunking and SIP PBX platforms such as the Avaya® Aura® Communication Manager and the Cisco® Unified Communications Manager.
- Survivability: Uninterrupted calling services for SIP clients (including Polycom® and Yealink® phones) through built-in SIP registrar and re-routing around failed routes/proxy servers/destination endpoints.
The
is certified for Teams Direct Routing media bypass and non-media bypass services. Please refer to Microsoft Teams Phone System Direct Routing
certification page.These instructions assume the
product is deployed via Microsoft Azure and running. If the product is not installed, refer to
Deploying a SBC SWe Lite via Azure Marketplace. Include Page |
---|
| _Teams_Routing_Prerequisites_New |
---|
| _Teams_Routing_Prerequisites_New |
---|
|
Assign a Static Public IP address on the media interface in Azure for Microsoft Teams Direct Routing.
- 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 |
---|
|
|
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 |
---|
0 | Figure |
---|
1 | Create Static Public IP Address |
---|
|
|
Run the Easy Configuration Wizard to configure Microsoft Teams Direct Routing:
- Access the WebUI. Refer to Logging into the SBC Edge.
- Click on the Tasks tab.
- From the left side menu, click SBC Easy Setup > Easy Config Wizard.
From the Application drop down box, select the relevant Easy Configuration wizard. Depending on your network, follow a relevant Easy Configuration wizard. Refer to the table below for guidance.
Caption |
---|
0 | Table |
---|
1 | Easy Configuration - Microsoft Teams Direct Routing Configuration |
---|
|
|
- The Configuration Wizard is complete
IP Routing must be customized in the
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.
Option 1: Set the Default Route on a Media Interface
When using multiple NICs on the
, 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.
Option 2: Add a Static Route for Microsoft Teams traffic to a Media Interface
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).
- Access the WebUI and click the Settings tab. Refer to Logging into the SBC Edge.
- In the left navigation pane, go to Protocols > IP > Static Routes.
- Click Create Static IP Route 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
Ensure that all network interfaces are configured as follows:
- Access the WebUI and click the Settings tab. Refer to Logging into the SBC Edge.
- In the left navigation pane, go to Networking Interfaces > Logical Interfaces.
- Verify the following is configured:
- IP Assign Method: DHCP.
DHCP Options to Use: IP Address and Default Route.
Caption |
---|
0 | Figure |
---|
1 | Select Networking Options |
---|
|
|
- Update if required.
Step 6: Confirm SBC SWe Links to Microsoft Teams
Step 7: Place a Test Call
Multiexcerpt |
---|
|
Place a test call as follows:
- Access the WebUI. Refer to Logging into the SBC Edge.
- In the WebUI, click the Diagnostics tab.
- In the left navigation pane, click Test a Call.
- Configure the parameters as shown below.
Click OK. Caption |
---|
0 | Table |
---|
1 | Place a Test Call - Parameters |
---|
|
Parameter | Value |
---|
Destination Number | Number assigned to a Teams user. | Origination/Calling Number | Number assigned to a Local user | Call Routing Table | The routing table that handles the call from Local resource. |
|
Caption |
---|
0 | Figure |
---|
1 | Test a Call - Configuration |
---|
|
|
Caption |
---|
0 | Figure |
---|
1 | Place a Test Call - Example |
---|
| Image Removed |
The test call is now complete. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing. |