In this section:
Overview
This document details the configuration required for an SBC SWe Lite to offer Microsoft Teams Phone System-related Direct Routing services in Microsoft Azure. The SBC SWe Lite 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)
SBC SWe Lite in Microsoft Azure offering Direct Routing Services to Teams Clients
From the Azure public cloud, the SBC SWe Lite 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 SBC SWe Lite 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 SWe Lite via Azure Marketplace
These instructions assume the SBC SWe Lite product is deployed via Microsoft Azure and running. If the product is not installed, refer to Deploying a SBC SWe Lite via Azure Marketplace.
Step 2: Review Prerequisites for Microsoft Teams Direct Routing
Microsoft Teams Direct Routing Configuration
Consult the Microsoft documentation for detailed information on Direct Routing interface configuration guidelines, including the RFC standards and the syntax of SIP messages.
SBC Edge Software
Ensure you are running the latest version of SBC software:
- To locate the SBC Edge software current running, refer to: Viewing the Software Version and Hardware ID.
- To download and upgrade a new version of SBC Edge software, refer to: Installing and Commissioning the SBC Edge and SBC SWe Lite.
Obtain IP Address and FQDN
Requirements for configuring the SBC Edge in support of Teams Direct Routing include:
SBC Edge Requirements
| Requirement | How it is Used |
|---|---|
Public IP address of NAT device (must be Static)* Private IP address of the SBC | Required for SBC Behind the NAT deployment. |
| Public IP address of SBC | Required for SBC with Public IP deployment. |
| Public FQDN | The Public FQDN must point to the Public IP Address. |
*NAT translates a public IP address to a Private IP address.
Domain Name
For the SBC Edge to pair with Microsoft Teams, the SBC FQDN domain name must match a name registered in both the Domains and DomainUrlMap fields of the Tenant. Verify the correct domain name is configured for the Tenant as follows:
- On the Microsoft Teams Tenant side, execute Get-CsTenant.
- Review the output.
- Verify that the Domain Name configured is listed in the Domains and DomainUrlMap attributes for the Tenant. If the Domain Name is incorrect or missing, the SBC will not pair with Microsoft Teams.
Users may be from any SIP domain registered for the tenant. For example, you can configure user user@SonusMS01.com with the SBC FQDN name sbc1.hybridvoice.org, as long as both names are registered for the tenant.
Domain Name Examples
| Domain Name* | Use for SBC FQDN? | FQDN Names - Examples |
|---|---|---|
| SonusMS01.com |  | Valid names:
|
hybridvoice.org | | Valid names:
Non-Valid name: sbc1.europe.hybridvoice.org (requires registering domain name europe. hybridvoice.org in “Domains” first) |
*Do not use the *.onmicrosoft.com tenant for the domain name.
Configure Domain Names - Example
Obtain Certificate
Public Certificate
The Certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.
Refer to Microsoft documentation for the supported CAs.
- Refer to Domain Name for certificate formats.
Configure and Generate Certificates on the SBC
Warning: Common Encryption Certificate Issues Arise from Missing Root Certificates
- Did you only install the CA-signed SBC certificate, along with the intermediate certificate(s) sent by your issuing CA?
- Did you get the following error message from the SBC?
If so, the likely reason is a missing CA Root Certificate. The SBC does not have any pre-installed CA root X.509 certificates, unlike typical browsers found on your PC. Ensure the entire certificate chain of trust is installed on the SBC, including the root certificate. Acquire the CA root certificate as follows:
- Contact your system administrator or certificate vendor to acquire the root, and any further missing intermediate certificate(s) to provision the entire certificate chain of trust within the SBC;
- Load the root certificate, along with the intermediate and SBC certificates, according to Importing Trusted Root CA Certificates.
NOTE: Root certificates are easily acquired from the certificate authorities. For example, the root certificate for the GoDaddy Class 2 Certification Authority may be found at https://ssl-ccp.godaddy.com/repository?origin=CALLISTO . For more information about root certificates, intermediate certificates, and the SBC server (“leaf”) certificates, refer to this tutorial.
For other certificate-related errors, refer to Common Troubleshooting Issues with Certificates in SBC Edge.
Microsoft Teams Direct Routing allows only TLS connections from the SBC for SIP traffic with a certificate signed by one of the trusted certification authorities.
Request a certificate for the SBC External interface and configure it based on the example using GlobalSign as follows:
- Generate a Certificate Signing Request (CSR) and obtain the certificate from a supported Certification Authority.
- Import the Public CA Root/Intermediate Certificate on the SBC.
- Import the Microsoft CA Certificate on the SBC.
- Import the SBC Certificate.
The certificate is obtained through the Certificate Signing Request (instructions below). The Trusted Root and Intermediary Signing Certificates are obtained from your certification authority.
Step 1: Generate a Certificate Signing Request and obtain the certificate from a supported Certification Authority (CA)
Many CA's do not support a private key with a length of 1024 bits. Validate with your CA requirements and select the appropriate length of the key.
- Access the WebUI.
- Access Settings > Security > SBC Certificates.
Click Generate SBC Edge CSR.
Enter data in the required fields.
Click OK. After the Certificate Signing request finishes generating, copy the result to the clipboard.
Generate Certificate Signing Request
- Use the generated CSR text from the clipboard to obtain the certificate.
Step 2: Deploy the SBC and Root/Intermediate Certificates on the SBC
After receiving the certificates from the certification authority, install the SBC Certificate and Root/Intermediate Certificates as follows:
- Obtain Trusted Root and Intermediary signing certificates from your certification authority.
- Access the WebUI.
- To install Trusted Root Certificates, click Settings > Security > SBC Certificates > Trusted Root Certificates.
- Click Import and select the trusted root certificates.
- To install the SBC certificate, open Settings > Security > SBC Certificates > SBC Edge Certificate.
Validate the certificate is installed correctly.
Validate Certificate
- Click Import and select X.509 Signed Certificate.
Validate the certificate is installed correctly.
Validate Certificate
Firewall Rules
Ribbon recommends the deployment of the SBC Edge product behind a firewall, within the DMZ, regardless of the assignment of a public IP to the SBC in question. Refer to SBC Edge Security Hardening Checklist for more information about the SBC and firewalls.
This section lists the ports, protocols and services for firewalls that are in the path of the SBC connecting to Teams Direct Routing.
Basic Firewall Rules for All Call Flows
Firewall Rules for the SBC with Media Bypass
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.
- 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.
Click on VM
Under Settings, click Networking to open the media interface.
Select Networking
Click on the network interface.
Under Settings, click IP Configuration.
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.
Create Static Public IP Address
Step 4: Configure SWe Lite for Microsoft Teams Direct Routing
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.
Easy Configuration - Microsoft Teams Direct Routing Configuration
Deployment Type Refer to Configuration: SBC Connects to Microsoft Teams via SIP Trunk SIP trunks ↔ Microsoft Phone System Direct Routing SBC connects to Microsoft Teams via IP PBX IP PBX ↔ Microsoft Phone System Direct Routing - The Configuration Wizard is complete
Step 5: 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.
Option 1: Set the Default Route on a 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.
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).
For details on creating Static Routes, refer to Creating Entries in a Static IP Route Table.
- 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 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
Create Static IP Route
- Click OK.
Confirm the IP Configuration
For details on IP Interfaces, refer to Managing Logical Interfaces
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.
Select Networking Options
- Update if required.
Step 6: Confirm SBC SWe Links to Microsoft Teams
For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
Step 7: Place a Test Call
Place a test call as follows: Click OK. Place a Test Call - Parameters Test a Call - Configuration Place a Test Call - Example The test call is now complete. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
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.
Overview
Content Tools