Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-3579
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

CSS Stylesheet
img.confluence-embedded-image { display: inline-block !important; }

Overview

This document details the configuration required for an 

Spacevars
0product3
to offer Microsoft Teams Phone System-related Direct Routing services in Microsoft Azure. The 
Spacevars
0product3
can be used to connect an enterprise's Teams clients to:

  • Third-party party PBX and subtended clients
  • SIP trunk from a third-party provider (PSTN)

    Pagebreak

    SBC SWe Edge in Microsoft Azure offering Direct Routing Services to Teams Clients

From the Azure public cloud, the

Spacevars
0product3
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

Spacevars
0product3
is certified for Teams Direct Routing media bypass and non-media bypass services. Please refer to Microsoft Teams Phone System Direct Routing certification page.

Step 1: Deploy SBC SWe Edge via Azure Marketplace

These instructions assume the 

Spacevars
0product3
product is deployed via Microsoft Azure and running. If the product is not installed, refer to Deploying a an SBC SWe Lite via Edge from the Azure Marketplace.

Pagebreak

Step 2: Review Prerequisites for Microsoft Teams Direct Routing

Include Page
_Teams_Routing_Prerequisites_New
_Teams_Routing_Prerequisites_New

Step 3: 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.

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the left navigation pane, click Virtual Machines.
  3. Click the desired VM to be used for Microsoft Teams Direct Routing.

  4. Under Settings, click Networking to open the media interface.

  5. Click on the network interface.

  6. Under Settings, click IP Configuration.

  7. Click ipconfig1.
  8. Enable a Public IP address and create a new Static Public IP address on the media interface through a series of windows:
    1. From the Public IP address settings option, select Enabled.

    2. Click IP address.
    3. From the Choose public IP address window, click Create new.

    4. From the Create public IP address window and the Assignment options, select Static.

Pagebreak


Step 4: Configure SBC SWe Edge for Microsoft Teams Direct Routing

Run the Easy Configuration Wizard to configure Microsoft Teams Direct Routing:

  1. Access the WebUI. Refer to Logging into the SBC Edge.
  2. Click on the Tasks tab.
  3. From the left side menu, click SBC Easy Setup > Easy Config Wizard.
  4. 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.
    Easy Configuration - Microsoft Teams Direct Routing Configuration

    Deployment TypeRefer to Configuration:
    SBC Connects to Microsoft Teams via SIP TrunkSIP trunks ↔ Microsoft Phone System Direct Routing
    SBC connects to Microsoft Teams via IP PBXIP PBX ↔ Microsoft Phone System Direct Routing


  5. The Configuration Wizard is complete

Pagebreak

Step 5: Complete SBC SWe Edge Configuration for Microsoft Teams Direct Routing in Azure

Configure IP Routing

IP Routing must be customized in the 

Spacevars
0product3
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.

Anchor
DefaultRoute
DefaultRoute
Option 1: Set the Default Route on a Media Interface

When using multiple NICs on the

Spacevars
0product3
, 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.

Anchor
StaticRoute
StaticRoute
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).

Info

For details on creating Static Routes, refer to Creating Entries in a Static IP Route Table.

  1. Access the WebUI and click the Settings tab. Refer to Logging into the SBC Edge.
  2. In the left navigation pane, go to Protocols > IP > Static Routes. 
  3. Click Create Static IP Route at the top of the Static IP Route Table page.
  4. Add the following Static Route using your media interface:

    1. Destination IP: 52.112.0.0

    2. Mask: 255.252.0.0

    3. Gateway: 10.1.9.1

  5. 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:

  1. Access the WebUI and click the Settings tab. Refer to Logging into the SBC Edge.
  2. In the left navigation pane, go to Networking Interfaces > Logical Interfaces.
  3. Verify the following is configured:
    1. IP Assign Method: DHCP.
    2. DHCP Options to Use: IP Address and Default Route.

  4. Update if required.

Pagebreak

Step 6: Confirm SBC SWe Links to Microsoft Teams


Multiexcerpt
MultiExcerptNameConfirmLinks
  1. Access the WebUI. Refer to Logging into the SBC Edge.
  2. Click Monitor.
  3. Under each newly created Signaling Group (created for each Tenant), confirm the channels are green. For details on channel status, refer to Monitoring Real Time Status.

For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.


Step 7: Place a Test Call


Multiexcerpt
MultiExcerptNameTestCall

Place a test call as follows:

  1. Access the WebUI. Refer to Logging into the SBC Edge.
  2. In the WebUI, click the Diagnostics tab.
  3. In the left navigation pane, click Test a Call.
  4. Configure the parameters as shown below.
  5. Click OK. 
    Place a Test Call - Parameters

    ParameterValue
    Destination NumberNumber assigned to a Teams user.
    Origination/Calling NumberNumber assigned to a Local user
    Call Routing TableThe routing table that handles the call from Local resource.


    Test a Call - Configuration


The test call is now complete. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.