Page History

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 

Spacevars
0 product3

to offer Microsoft Teams Phone System-related Direct Routing services in Amazon Web Services (AWS). The 

Spacevars
0 product3

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 Edge in Amazon Web Services (AWS) offering Direct Routing Services to Teams Clients

From the AWS public cloud, the

Spacevars
0 product3

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 3^rd  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

Spacevars
0 product3

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 

Spacevars
0 series3

via AWS

These instructions assume the 

Spacevars
0 series3

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.

Step 2: Review Prerequisites for Microsoft Teams Direct Routing

 

Include Page
_Teams_Routing_Prerequisites_New _Teams_Routing_Prerequisites_New

Step 3: Configure 

Spacevars
0 series3

for Microsoft Teams Direct Routing

Run the Easy Configuration Wizard to configure Microsoft Teams Direct Routing:

1. Access the WebUI. Refer to Logging into the SBC Edge Portfolio.
2. Click on the Tasks tab.
3. From the left side menu, click SBC Easy Setup > Easy Config Wizard.

4. From the Application drop down box, select the relevant Easy Configuration wizard.  Refer to the table below for guidance and the supporting user documentation.
   

   Caption0Table1

   Easy Configuration - Microsoft Teams Direct Routing Configuration

   Deployment Type	Refer to Configuration:
   Spacevars 0 series3  connects to Microsoft Teams via SIP Trunk	SIP trunks ↔ Microsoft Teams
   Spacevars 0 series3  connects to Microsoft Teams via IP PBX	IP PBX ↔ Microsoft Teams
   Spacevars 0 series3  connects to Microsoft Teams via SIP Trunk (Single Leg)	Single Leg SIP Trunk ↔ Microsoft Teams
   Spacevars 0 series3  connects to Microsoft Teams via IP PBX (Single Leg)	Single Leg IP PBX ↔ Microsoft Teams

   The Easy Configuration Wizard is complete.

Step 4: Confirm 

Spacevars
0 series3

links to Microsoft Teams

Following configuration, confirm the 

Spacevars
0 series3

links to Microsoft Teams as follows:

1. Access the WebUI. Refer to Logging into the 

   Spacevars
   0 series3

   .
2. Click Monitor.
3. 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:

1. Access the WebUI. Refer to Logging into the SBC Edge.

2. In the WebUI, click the Diagnostics tab.

3. In the left navigation pane, click Test a Call.

4. Configure the parameters as shown below.

5. Click OK. 

   Caption0Figure1

   
   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.

   Caption0Figure1

   
   

   Test a Call - Configuration

   Image Modified

   Info
   For information about troubleshooting the Spacevars 0 series3 's connection to Microsoft Teams, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.