In this section:

 Overview

The SBC SWe Edge includes the Easy Configuration option to add a partially configured signaling group with a new single end-point scenario for Microsoft Teams: Teams Direct Routing or Teams Downstream SBC.


The Configure Single Leg Wizard for Microsoft Teams option applies to SBC SWe Edge only.

The SBC Easy Configuration interface includes a built-in, step-by-step setup configuration wizard to enable quick and easy deployment of a partially configured signaling group with a new single end-point scenario for a Microsoft Teams. 

For the single endpoint configuration, since the peer end if not known/configured, in the Easy Configuration Wizard, the Transformation and Routing entries for the endpoint being configured are created independent of the peer end. If you have two endpoints connected and use the Single Leg Wizard to add the third endpoint, you'll need to create/modify the Transformation and Routing entries to complete routing.

Easy Configuration Wizard - Single Leg Configuration Notes
  • Use the single leg wizard to add a 3rd, 4th, or 5th peer to a device, when at least two legs are already configured via the standard Easy Configuration Wizard.
  • Emergency configuration is not supported for single end scenarios.

Step 1: Select Microsoft Teams Connection

Easy Configuration Step 1 includes configuration for scenario parameters.

  1. In the WebUI, click the Tasks tab.
  2. In the left navigation panel, go to SBC Easy Setup > Easy Config Wizard.

  3. From the Application drop down list, select Microsoft Teams.

  4. Configure per the field definitions below and click Next.

    FieldDescription
    ApplicationConfiguration template used: Microsoft Teams.
    Scenario DescriptionName to describe the setup.
    Telephone CountryCountry in which Microsoft Teams is setup.
    SIP SessionsNumber 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

    NOTE: For , only Teams Direct Routing is supported.

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. 

  1. Configure the connection type information.
  2. Click Next.

Teams Direct Routing

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

FieldDescription

Teams Connection Type - Standalone Direction Connection

Team Connection Type 

The Teams connection type used for the network. Valid selections:

  • Standalone Direct Connection
  • Local Media Optimization

Note: For , only Standalone Direct Connection is supported.

Signaling/Media Source IPClick 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.

Static Host FQDN/IP[;port] 

This field is available for  only with a Standalone Direct Connection. 

The SBC inserts the configured FQDN in the requests and responses sent toward Microsoft Teams. Microsoft Teams can then reach the SBC successfully based on the configured FQDN.

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.

NOTE: This field is not applicable to .

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.

ProtocolHard-coded value for protocol used with federated FQDN: TLS.
Server Port NumberHard-coded value for the port used for TLS: 5061.
Listening Port NumberPort number used for sending and receiving SIP messages between the SBC and the Border Element Server.

Teams Connection Type - Local Media Optimization (Microsoft Teams Direct Routing media flow uses the shortest path to improve the SBC Edge Portfolio's media quality and bandwidth usage)

Signaling/Media Source IPExternal (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media. 
Private Media Source IPPrivate IP address that handles routing of messages for 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.

ProtocolHard-coded value for protocol used with federated FQDN: TLS
Server Port NumberHard-coded value for the port used for TLS: 5061.
Listening Port NumberPort number used for sending and receiving SIP messages between the SBC and the Border Element Server.
ProtocolHard-coded value for protocol used with federated FQDN: TLS
Downstream SBC Signaling Listen PortPort number used for sending and receiving SIP messages between the Downstream SBC and the Border Element Server. Valid entry: 1024-65535.
Max Users per Downstream SBCMaximum number of users per Downstream SBC. Valid entry: 1 - 1000.

Teams Downstream SBC

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

Configure Teams Downstream SBC

FieldDescription
Signaling/Media Source IPExternal (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media.
Teams Proxy SBCThe IP/FQDN for the Proxy SBC for TLX to properly establish.
ProtocolHard-coded value for protocol used with federated FQDN: TLS
Port NumberThe port used for TLS. Valid entry: 1024 - 65535.
SBC FQDNFQDN for the SBC.

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.