In this section:
Overview
This document details the configuration required for an
- Third-party party PBX and subtended clients
SIP trunk from a third-party provider (PSTN)
SBC SWe Edge in Amazon Web Services (AWS) offering Direct Routing Services to Teams Clients
From the AWS public cloud, the
- 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
Step 1: Deploy Unable to show "metadata-from": No such page "_space_variables" via AWS
These instructions assume the
Step 2: Review Prerequisites for Microsoft Teams Direct Routing
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 Portfolio.
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: | |
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 certificate information.
Refer to CCADB Documentation for the comprehensive list of supported CAs.
- Refer to Domain Name for certificate formats.
Configure and Generate Certificates on the SBC
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 Portfolio 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 Unable to show "metadata-from": No such page "_space_variables" 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 Portfolio.
- 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. Refer to the table below for guidance and the supporting user documentation.
The Easy Configuration Wizard is complete.
Step 4: Confirm Unable to show "metadata-from": No such page "_space_variables" links to Microsoft Teams
Following configuration, confirm the
- Access the WebUI. Refer to Logging into the Unable to show "metadata-from": No such page "_space_variables".
- Click Monitor.
- 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 5: Place a Test Call
Following configuration, 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.
For information about troubleshooting the
Unable to show "metadata-from": No such page "_space_variables"'s connection to Microsoft Teams, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.