_Teams_Configuration_Single_Leg_Call

These instructions assume the SBC Edge is installed and running, and is connected to the WebUI.

For the purposes of this documentation, the screens displayed are for an SBC 1000/2000; the interface configuration may vary slightly for the SBC SWe Lite. If configuration is not specified for a field, use the default value.

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

Use Easy Config Wizard

Easy Config Wizard can be used to create all the resource required for Microsoft Teams Direct Routing.

Step 1: Select Microsoft Teams Connection

In the WebUI, click the Tasks tab.
In the left navigation panel, go to SBC Easy Setup > Easy Config Wizard.
From the Application drop down list, select Microsoft Teams.

Configure per the field definitions below and click Next.

Configure Microsoft Teams Connection

Configure Scenario Parameters - Field Definitions

Field	Description
Application	Configuration template used: Microsoft Teams.
Scenario Description	Name to describe the setup.
Telephone Country	Country in which Microsoft Teams is setup.
SIP Sessions	Number of simultaneous SIP Sessions. Valid entry: 1 - 960.
Teams Connection	The Teams connection type used for the network. Valid selections: Teams Direct Routing Teams Downstream SBC

Step 2: Configure Microsoft Teams for Endpoint

Easy Configuration Step 2 includes configuration for the Microsoft Teams endpoint. The configuration items displayed in Step 2 depends on the connection type for the Microsoft Teams leg you configured in Step 1. See below for each type.

Configure the connection type information.
Click Next.

Step 2 Example Screen

The fields below are displayed if you select Teams Direct Routing from the Teams Connection drop down list in Step 1.

Configure Teams Direct Routing

Field	Description
Teams Connection Type - Standalone Direction Connection
Signaling/Media Source IP	Click the drop-down arrow to select the external (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media.
Outbound NAT Traversal	Allows the SBC to be placed behind a NAT device, and uses the IP of the NAT device for all outgoing messages. If this field is set to Enable, the Public IP address field configuration is required. Valid selections: Enable: Network Address Translation is used for the NAT device's Public IP address. Disable: Network Address Translation address translation is not used. NOTE: This field is required when the SBC interface has a private IP and the NAT device is using a public IP. For details on configuring an SBC behind the NAT, refer to Configuring the SBC Edge for NAT Traversal.
Apply ACL	Specifies whether an ACL (Access Control List) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP. Valid selection: True: Applies the ACL. False: Does not apply the ACL. For details on configuring an ACL to be applied to an SBC, refer to Managing Access Control Lists.
Protocol	Hard-coded value for protocol used with federated FQDN: TLS.
Server Port Number	Hard-coded value for the port used for TLS: 5061.
Listening Port Number	Port number used for sending and receiving SIP messages between the SBC and the Border Element Server.

Step 3: Summary

Easy Configuration Step 3 includes a summary of the information configured in Step 1 and Step 3.

Review the information and click Finish.

See below for an example:

Step 3 Example Screen

Create Transformation Table and Entries

This Transformation Table contains a list of call routes that include routing configuration for calls from Microsoft Teams and SIP Trunk. Two Transformation tables are required:

For Calls from Microsoft Teams to SIP Trunk
For Calls from SBC's SIP Trunk to Microsoft Teams

Calls From Microsoft Teams to SBC's SIP Trunk

This Transformation Table contains a list of call routes that include routing configuration for calls from Microsoft Teams to SBC's SIP Trunk.

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
Click OK.

Create Transformation Table
In the left navigation panel, select the new table: Transformation > From Microsoft Teams: Passthrough.
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 From Microsoft Teams: Passthrough
Match Type Mandatory (Must Match)
Input Field Type: Called Address/Number
Value: (.*)
Output Field Type: Called Address Number
Value: \1

Transformation Entry - Example

Transformation Table - Entry Added

Calls From SBC's SIP Trunk to Microsoft Teams

This Transformation Table contains a list of call routes that include routing configuration for calls from the SBC's SIP Trunk 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 SIP Trunk.
Click OK.

Create Transformation Table
In the left navigation panel, select the new table: Transformation > From SIP Trunk to Microsoft Teams: Passthrough.
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
From SIP Trunk: Passthrough
Match Type
Mandatory (Must Match)
Input Field
Type: Called Address/Number
Value: (.*)
Output Field
Type: Called Address Number
Value: \1

Transformation Table Entry

Transformation Table - Entry Added

Create Call Routing entries

Two Call Routing Tables need to be modified for transporting calls between the SBC's SIP Trunk and Microsoft Teams:

Call Route - Calls from Microsoft Teams to SBC's SIP Trunk
Call Route - Calls from the SBC's SIP Trunk to Microsoft Teams

From Microsoft Teams to SBC's SIP Trunk

This Call Routing Table routes calls from Microsoft Teams.

In the WebUI, click the Settings tab.
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	To SIP Trunk (Passthrough)
Number/Name Transformation Table	From Microsoft Teams: Passthrough (select Transformation Table you created above)
Destination Signaling Groups	Choose the Signaling Group of a local equipment.

Call Routing Table - Example

From SBC's SIP Trunk to Microsoft Teams

This Call Routing Table routes calls from the SBC's SIP Trunk and sent to Microsoft Teams.

To add and configure a new Call Routing Table:

In the WebUI, click the Settings tab.
From the left navigation pane, click on the Call Routing > Call Routing table.
Select From SIP Trunk, this table already contains an entry to route the calls to CCE.
Select the existing entry where First Signaling Group is CCE
Set the Admin State to Disabled
Click OK.
From the left navigation pane, click on the Call Routing > Call Routing table.
Select From SIP Trunk, this table already contains an entry to route the calls to CCE.
Click the ().
Configure the parameters as shown below. Leave all other parameters as default.