In this section:
Overview
The SBC Edge is certified to offer Microsoft Teams Direct Routing services; the SBC Edge can be used to connect any Teams client to:
- A PSTN trunk, whether based on TDM (e.g. PRI, BRI, etc.), CAS, or SIP
- 3rd-party, non-Teams-certified SIP/TDM based PBXs, analog devices, and SIP clients
These instructions detail how to configure the SBC Edge (SBC 1000/2000) to connect Microsoft Teams Direct Routing services deployed in an Enterprise network (On Premises) to an analog device via FXS port. The network diagram below displays the connection topology for Microsoft Teams Direct Routing deployed in an Enterprise network.
SBC Edge connects to Microsoft Teams Direct Routing Deployed in an Enterprise Network
Step 1: Install SBC Edge
These instructions assume the SBC Edge product (SBC 1000/2000) is installed and running. If the product is not installed, refer to the links below. Installation Requirements
Product Installation SBC 1000 Installing the SBC 1000 Hardware SBC 2000
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 SBC Edge for Microsoft Teams Direct Routing to Support Analog Devices
These instructions assume the SBC Edge is installed and running, and is connected to the WebUI.
Access the SBC Edge WebUI
Access the WebUI. Refer to Logging into the SBC Edge.
Configure Host Information and DNS
The Host Information and DNS configuration contains system information that is used by the SBC Edge, including host, domain, and NTP server information.
- In the WebUI, click the Settings tab.
- In the left navigation page, access System > Node-Level Settings. The Node-Level Settings page is displayed.
- Configure the NTP and DNS Servers with network-specific data.
- Leave all other parameters as default.
Click Apply.
TLS Configuration - Example Values
Parameter Example Value Host Name aepsite6 Domain Name SonusMS01.com Use NTP Yes NTP Server Specifies the FQDN, IPv4, or IPv6 address of the NTP server. If the host name is supplied, the SBC uses the DNS to connect to the NTP server. Use Primary DNS Yes Primary Server IP XXX.XXX.XX.XXX Node-level Settings - Example
Configure Logical Interface
The SBC Edge supports system-supported Logical Interfaces, which are used to hold the IP address for each Ethernet port. One of these logical interfaces is assigned an IP address for transporting the VoIP media packets (i.e., RTP, SRTP) and protocol packets (i.e, SIP, RTCP, TLS). In this example, Ethernet 1 is configured for transporting packets for the Microsoft Teams Direct Routing connection.
Ensure the IP Routing Table contains the same information as in the network topology.
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Node Interfaces > Logical Interfaces.
- Configure the parameters as shown below (example values are shown in the table; configure as per your network requirements). For details on field descriptions, refer to Configuring and Modifying Logical Interfaces.
- Leave all other parameters as default.
Click Apply.
Logical Interfaces Configuration - Example Values
Parameter Example Value Alias To Microsoft Phone 5 Description Interface to Interconnect with Microsoft Phone System Admin Interface Enable IP Assign Method Static Primary Address <Public IP of your SBC> (in the example 192.168.211.80) Primary Netmask <Mask of Public Interface of your SBC> (in the example 255.255.255.0) Logical Interfaces - Example
Create Profiles
For interconnecting with Microsoft System Direct Routing, the following profiles are required:
- Teams Direct Routing Profile (SIP)
- Analog Device Profile
Create Teams Direct Routing Profile
The Teams Direct Routing profile is used for connecting the SBC Edge to Microsoft Teams.
Create the Teams Direct Routing Profile as follows:
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Profiles.
- Click the (
) icon at the top of left corner and add a new SIP profile. - Configure the parameters as shown below (example values are shown in the table; configure as per your network requirements). For details on field descriptions, refer to Creating and Modifying SIP Profiles.
- Leave all other parameters as default.
Click OK.
SIP Profile Configuration - Example Values
Parameter Example Value Description Teams Direct Routing Profile FQDN in From Header SBC Edge FQDN FQDN In Contact Header SBC FQDNNOTE: For Microsoft Teams, the Signaling Group facing the Teams server must be configured as SBC Edge FQDN or Static (if there is more than one signaling group connected to Teams Direct Routing). The FQDN in Contact Header should be the same FQDN used in Office 365 Tenant Online Gateway. If the IP Address of the SBC is configured in the Contact Header instead of the FQDN of the SBC, a Forbidden message is received.NOTE: If you set this field to Static and you expect the port number of the Contact header in the outbound SIP messages, you must configure the Static Host FQDN/IP field with the Listen Port number of the SIP signaling group. Origin Field Username <FQDN of SBC> (in the example aepsite6.SonusMS01.com) SIP Profile - Example
Create Analog Device Profile
CAS Profiles control various aspects of loop start, DTMF, tone detection and other features associated with the variants of CAS calls. The Ribbon SBC 1000/2000 supports FXS, E&M and R2 signaling through CAS.
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to CAS > CAS Signaling Profiles.
- From the Create CAS Profile drop down box, select FXS Profile.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Analog Profile Entries - Example Values
Parameter Value Description Analog Device Loop Start Type Specifies the loop start method. This field is country-specific, and may need to be adjusted for your country. Disconnect Tone Generation Specifies whether or not a disconnect tone is generated when a call is disconnected from the far end. This field is country-specific, and may need to be adjusted for your country. Analog Device Profile - Example
Create SDES-SRTP Profile
The SDES-SRTP Profile defines the encryption mechanism used between the SBC and the Microsoft Teams Direct Routing interface; the Crypto Suite specifies the algorithm used to negotiate with a peer device.
Create a SDES-SRTP Profile as follows:
- In the WebUI, click the Settings tab.
- In the left navigation page, access Media > SDES-SRTP.
- Click the ( ) icon at the top left corner and add a new SDES-SRTP Profile.
- Configure the parameters as shown below. For details on field descriptions, refer to Creating and Modifying SIP Profiles.
Leave all other parameters as default.
Media Crypto Profile Configuration - Example Values
Parameter Example Value Description Teams Direct Routing SRTP Operation Option Required Crypto Suite AES_CM_128_HMAC_SHA1_80 Media Crypto Profile - Example
Create Media List
The Media List contains one or more of Media Profiles, which the SBC Edge uses for call transmission. A Media Profile specifies the individual voice codecs the SBC Edge uses for voice compression, voice quality, and associated settings.
Create a Media List for Teams Direct Routing as follows:
- In the WebUI, click the Settings tab.
- In the left navigation page, access Media > Media List.
- Click the ( ) icon at the top left corner and add a new Media List.
- Configure parameters as shown below. For details on field descriptions, refer to Creating and Modifying Media Lists.
Leave all other parameters as default.
Media List Configuration - Example Values
Parameter Example Value Description Teams Direct Routing Media List Media Profiles List In the Media Profiles List field, click Add/Edit. G711a and G711u are the default Media Profiles. - G711a
- G711u
SDES-SRTP Profile Teams Direct Routing SRTP. This profile was created in the previous step. Media List - Example
Configure a SIP Server Table
SIP server tables define the information for the SIP interfaces connected to the SBC Edge; a SIP Server Table is required to support the Microsoft Phone System.
Create a Teams Direct Routing Server
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables
- Click the ( ) icon at the top left corner and add a new SIP Server Table.
- For Description, enter Teams Direct Routing Server.
Click OK.
Create SIP Server Table
Configure Entries in the Teams Direct Routing Server
The information you configure in the SIP Server table pairs the SBC Edge to the Microsoft Teams Direct Routing interface. Three entries in the SIP Server table offer server redundancy to ensure a server is always up and communicating. If a server is down or not communicating, the SBC Edge will automatically move to the next Server entry on the list.
Configure Teams Direct Routing Server entries as follows:
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables.
- Select the name of the table created in the previous step.
- From the Create SIP Server drop down list, select IP/FQDN.
Repeat this configuration for two additional SIP Server entries, using the field entries below. For details on field descriptions, refer to Creating and Modifying Entries in SIP Server Tables.
SIP Server 1 Table - Example Values
Parameter Value Priority 1 Host sip.pstnhub.microsoft.com Port 5061 Protocol TLS TLS Profile Teams Direct Routing TLS Monitor SIP Options SIP Server 1 - Example Values
SIP Server 2 Table - Example Values
Parameter Value Priority 2 Host sip2.pstnhub.microsoft.com Port 5061 Protocol TLS TLS Profile Teams Direct Routing TLS Monitor SIP Options SIP Server 2 - Example Values
SIP Server 3 Table - Example Values
Parameter Value Priority 3 Host sip3.pstnhub.microsoft.com Port 5061 Protocol TLS TLS Profile Microsoft Phone System Monitor SIP Options SIP Server 3 - Example Values
Create Transformation Tables and Entries
This Transformation Table contains a list of call routes that include routing configuration for calls between Microsoft Teams and an Analog Device. Two Transformation tables are required:
- For Calls from Microsoft Teams to Analog Device
- For Calls from Analog Device to Microsoft Teams
Calls From Microsoft Teams to Analog Device
This Transformation Table contains a list of call routes that include routing configuration for calls from Microsoft Teams to an Analog Device.
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing > Transformation
- Click the ( ) icon at the top left corner to add a new Transformation Table.
- For Description, enter From Microsoft Teams to Analog Device
Click OK.
Create Transformation Table
- In the left navigation panel, select the new table: Transformation > From Microsoft Teams to Analog Device
- Click the Create ( ) icon.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Transformation Entries - Example Values
Parameter Value Description Extract Analog Device Extension Number Match Type Optional (Match One) Input Field Type: Called Address/Number
Value: .*3(\d{3})Output Field Type: Called Address Number
Value: \1Transformation Entry - Example
Transformation Table - Entry Added
Calls From Analog Device to Microsoft Teams
This Transformation Table contains a list of call routes that include routing configuration for calls from the Analog Device to Microsoft Teams.
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing> Transformation
- Click the ( ) icon at the top left corner to add a new Transformation Table.
- For Description, enter From Analog Device to Microsoft Teams
Click OK.
Create Transformation Table
- In the left navigation panel, select the new table: Transformation > From Analog Device to Microsoft Teams
- Click the Create ( ) icon.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Transformation Entries - Example Values
Parameter Value Description Convert to Teams Client Number Match Type Optional (Match One) Input Field Type: Called Address/NumberValue: (.*) Output Field Type: Called Address NumberValue: \1 Transformation Table Entry
Transformation Table - Entry Added
Create Signaling Groups
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. In the case of SIP, they specify protocol settings and link to server, media and mapping tables. For Teams Direct Routing, you configure the Signaling Group to designate routing information for calls between SBC Edge and the Microsoft Phone System. Two Signaling Groups are required:
- Signaling Group - Calls from Microsoft Teams to Analog Device
- Signaling Group - Calls from Analog Device to Microsoft Teams
Calls From Microsoft Teams to Analog Device
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups
- From the Create Signaling Group drop down box, select SIP Signaling Group.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Signaling Group Configuration - Example Values
Parameter Value Description Microsoft Teams SIP Profile Teams Direct Routing Profile Media List ID Team Direct Routing List Signaling Media/Private IP Ethernet 1 (example, choose the interface which faces Microsoft Teams Direct Routing) Listen Port 5061 TLS Federated IP/FQDN sip-all.pstnhub.microsoft.com SIP server table Teams Direct Routing Server Load Balancing Priority: Register All SIP Profile Microsoft Phone System (from previous step) Call Routing Table Default Routing Table Outbound NAT Traversal* Static NAT NAT Public IP* IP Address (Only required if “Static NAT” is selected) Static NAT Inbound Disabled (this field should not be configured for Non-Media Bypass Teams deployment) *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the public IP address of the NAT device is required when the SBC has a Private IP).Signaling Group - Example
Calls from Analog Device to Microsoft Teams
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups
- From the Create Signaling Group drop down box, select CAS Signaling Group.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Signaling Group Configuration - Example Values
Parameter Value Description Analog Device CAS Signaling Profile Select (FXS) Analog Device Caller ID Type Country-specific Assigned Channels Assign CAS channels. Call Routing Table Default Routing Table Signaling Group - Example
Create Call Routing Tables
Two Call Routing Tables for transporting calls between the SBC and Microsoft Teams are required:
- Call Route - Calls from Microsoft Teams to Analog Device
- Call Route - Calls from Analog Device to Microsoft Teams
From Microsoft Teams to Analog Device
This Call Routing Table routes calls from Microsoft Teams.
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing Table.
Click the (
) icon at the top left corner and add a new Call Routing Table.Create Call Routing Table
- Configure the Description as From Microsoft Teams and click OK.
- From the left navigation pane, click on the Call Routing > Call Routing table.
- Select From Microsoft Teams (the entry you just created).
- Click the ().
- Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Call Routing Table Configuration - Example
Parameter Value Description From Microsoft Teams to Analog Device Number/Name Transformation Table From Microsoft Teams to Analog (select Transformation Table you created above) Destination Signaling Groups From Microsoft Teams Call Routing Table - Example
From Analog Device to Microsoft Teams
This Call Routing Table routes calls from the Analog Device and sent to Microsoft Teams.
To add and configure a new Call Routing Table:
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing Table.
Click the (
) icon at the top of left corner and add a new Call Routing Table.Create Call Routing Table
- Configure the Description as Microsoft Phone system and click OK.
- From the left navigation pane, click on the Call Routing > Call Routing table.
- Select From Analog Device (the entry you just created).
- Click the ().
- Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Call Routing Table Configuration - Example
Parameter Value Description From Analog Device to Microsoft Teams Number/Name Transformation Table From Analog Device to Microsoft Teams (select Transformation Table you created above) Destination Signaling Groups From Analog Device Call Routing Table - Example
Update Signaling Groups for Call Route
The newly created Call Route must be associated to a Signaling Group as follows:
Associate Call Route to Signaling Group for Calls From Teams to Analog Device
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups > Teams Direct Routing.
- From the Call Routing Drop down list, select From Microsoft Teams.
Click OK.
Select Call Routing Table - Teams Direct Routing
Associate Call Route to Signaling Group for Calls from an Analog Device to Teams
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups > From Analog Device.
- From the Call Routing Drop down list, select From Analog Device.
Click OK.
Select Call Routing Table - From SIP Trunk
Step 4: Configure SBC Edge when Microsoft Teams is in Media Bypass Mode
Non-Media Bypass vs. Media Bypass Deployment
Non-Media Bypass
Non-Media Bypass is Microsoft Teams Direct Routing related deployment where all media flows between Teams clients in the enterprise and the SBC transit the Teams Phone System based in the Azure cloud.
Teams Direct Routing - Without Media Bypass
Media Bypass
Media Bypass is a Microsoft Teams Direct Routing deployment where all media flows between Teams clients in the enterprise connect directly to the SBC without transiting the Teams Phone System.
If Microsoft Teams is in Media Bypass mode, you must configure the SBC Edge as detailed in this section (if Microsoft Teams is not in Media Bypass mode, this configuration is not required).
For Media Bypass, the following is supported:
- Deployment on a Public IP address
- Deployment behind NAT
Configure Signaling Group
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); configuration for NAT is required only if deployment is behind NAT.
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups
From the Create Signaling Group drop down box, select SIP Signaling Group.
Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Signaling Group Configuration - Example Values
Parameter
Value
RTCP Multiplexing Enable ICE Support Enabled ICE Mode Lite Outbound NAT Traversal* Static NAT NAT Public IP (Signaling/Media)* Public Address for the NAT device assigned on the media port for your network Static NAT Inbound Disabled (this field should not be configured for Media Bypass Teams deployment) *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the public IP address of the NAT device is required when the SBC has a Private IP).
The peer endpoint must support the a=rtcp-mux exchange in order for the RTP and RTCP ports to be multiplexed into one data port.
SIP Signaling Group - Example
Step 5: Confirm SBC Edge Links to Microsoft Teams
For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
Step 6: Place a Test Call
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. 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 Microsoft Teams. 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.
Overview
Content Tools