Page History
Panel | ||||
---|---|---|---|---|
In this section:
|
Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 and SBC SWe Lite) to connect Microsoft Teams Direct Routing services deployed in an Enterprise network (On Premises). For public cloud deployments, refer to Connect SBC SWe Lite to Microsoft Teams Direct Routing Deployed in Azure. The network diagram below displays the connection topology for Microsoft Teams Direct Routing deployed in an Enterprise network.
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|
Step 1: Install SBC Edge
Multiexcerpt | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
These instructions assume the SBC Edge product (SBC SWe Lite, SBC 1000/2000) is installed and running. If the product is not installed, refer to the links below.
|
Pagebreak |
---|
Step 2: Review Prerequisites for Microsoft Teams Direct Routing
Include Page | ||||
---|---|---|---|---|
|
Step 3: Configure Office 365 Tenant Voice Routing
A Tenant is used within the Microsoft environment as a single independent enterprise that has subscribed to Office 365 services; through this tenant, administrators can manage projects, users, and roles. Access the Tenant configuration and configure as detailed below. (For details on accessing the Tenant, refer to Microsoft Teams Documentation).
Create Online PSTN Gateway that points to the SBC:
Enter the SBC FQDN (Example below: aepsite6.SonusMS01.com). The FQDN must be configured for the Tenant in both the Domains and the DomainUrlMap fields.
Enter the SBC SIP Port (Example below - SipPort5061).
Code Block New-CsOnlinePSTNGateway -Fqdn aepsite6.SonusMS01.com -SipSignallingPort SipPort5061 -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true
Configure Teams usage for the user:
Enter the User Identity (Example below: -user1@domain.com)
Code Block |
---|
Get-CsOnlineUser -Identity user1@domain.com Set-CsUser -Identity user1@domain.com -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI tel:+10001001008 Grant-CsOnlineVoiceRoutingPolicy -PolicyName "GeneralVRP" -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity user1@domain.com Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user1@domain.com |
Pagebreak |
---|
Step 4: Configure SBC Edge for Microsoft Teams Direct Routing
The SBC Edge is configured via Easy Configuration Wizard.
- 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 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 PSTN Provider through ISDN. ISDN PSTN ↔ Microsoft Phone System Direct Routing SBC connects to Microsoft Teams via IP PBX IP PBX ↔ Microsoft Phone System Direct Routing - For an SBC behind the NAT deployment only: In Step 2 of the Easy Configuration wizard, ensure the following is configured:
- From the Outbound NAT Traversal drop down list, select Enable. Allows the SBC to be placed behind a NAT device, and uses the IP of the NAT device for all outgoing messages.
- In the Public IP Address, enter the Public IP of the NAT device. The SBC uses this IP as the source IP for all the outgoing messages.
- If Media Bypass is disabled in the server, proceed to Step 5.
- If Media Bypass is enabled in the server, this step is complete.
The Configuration Wizard is complete.
Info For the SBC 1000/SBC 2000 only:
By default, when configuring the SBC with Easy Configuration, the default Ethernet Interface for Border Element (PSTN Endpoint) is configured as Auto. Ribbon recommends changing this configuration manually to the Ethernet port that points to the SIP Trunk side.
For instructions on changing the Ethernet interface, refer to: Configuring and Modifying Logical Interfaces.
Pagebreak |
---|
Step 5
: Configure SBC Edge when Microsoft Teams is in Non-Media Bypass Modetitle | Click here to expand for overview of Media Bypass vs. Non Media Bypass |
---|
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.
Caption | ||||
---|---|---|---|---|
| ||||
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.
Pagebreak |
---|
Info |
---|
This additional step is required only in cases where Media Bypass is disabled on the Teams Server. Complete these steps after Easy Configuration is complete. |
Easy Configuration enables Media Bypass by default. If Media Bypass is disabled on the Teams server, in addition to running Easy Configuration, you must disable Media Bypass in the SBC:
Click OK.
Caption | ||||
---|---|---|---|---|
| ||||
Pagebreak |
---|
: Confirm SBC Edge Links to Microsoft Teams
Multiexcerpt | ||
---|---|---|
| ||
For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing. |
Pagebreak |
---|
Step
76: Place a Test Call
Multiexcerpt | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Place a test call as follows:
The test call is now complete. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing. |
Pagebreak |
---|