Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | CHOR-1578 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c85c46b657015d4f57d577001c, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccf70906, userName='null'} |
---|
REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'} |
---|
|
Overview
This document details the configuration required for an to offer Microsoft Teams Phone System-related Direct Routing services in Amazon Web Services (AWS). The
can be used to connect an enterprise's Teams clients to:
SBC SWe Edge in Amazon Web Services (AWS) offering Direct Routing Services to Teams Clients
Image Modified
From the AWS public cloud, the
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
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
via AWS
These instructions assume the
product is deployed via AWS and running. If the product is not installed, refer to
Deploying an SBC SWe Edge via Amazon Web Services - AWS.
Include Page |
---|
| _Teams_Routing_Prerequisites_New |
---|
| _Teams_Routing_Prerequisites_New |
---|
|
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.
Caption |
---|
0 | Table |
---|
1 | Easy Configuration - Microsoft Teams Direct Routing Configuration |
---|
|
|
The Easy Configuration Wizard is complete.
Step 4: Confirm
links to Microsoft Teams
Following configuration, confirm the
links to Microsoft Teams as follows:
- Access the WebUI. Refer to Logging into the .
- 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.
Caption |
---|
0 | Figure |
---|
1 | 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 the Local resource. |
|
Caption |
---|
0 | Figure |
---|
1 | Test a Call - Configuration |
---|
|
|