Page History
...
| Panel | ||||
|---|---|---|---|---|
In this section:
|
OverviewOverview
The
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.Spacevars 0 series3
...
- 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.
NOTE: ForField 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
Spacevars 0 series5
, only Teams Direct Routing is supported.
Step 2: Configure Microsoft Teams for Endpoint
...
Configure Teams Direct Routing
| Field | Description |
|---|---|
Teams Connection Type - Standalone Direction Connection | |
| Team Connection Type | The Teams connection type used for the network. Valid selections:
|
Note: For
, only Standalone Direct Connection is supported.Spacevars 0 series5
| 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. |
This field is available for
only with a Standalone Direct Connection. Spacevars 0 series5
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. |
|
| Spacevars | ||
|---|---|---|
|
| Public IP Address | Specifies the Public IP address of the NAT device. The SBC uses this IP as the source IP for all the outgoing messages. This field is required only when Outbound NAT Traversal is configured to Enable. |
| Apply ACL | Specifies whether an |
Access Control List (ACL) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP. Valid |
selections: 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. | ||||||
Teams Connection Type - Local Media Optimization (Microsoft Teams Direct Routing media flow uses the shortest path to improve the | |||||||
|---|---|---|---|---|---|---|---|
| Signaling/Media Source IP | External (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media. | ||||||
| Private Media Source IP | Private 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. | ||||||
| |||||
| Public IP Address | Specifies the Public IP address of the NAT device. The SBC uses this IP as the source IP for all the outgoing messages. This field is required only when Outbound NAT Traversal is configured to Enable. | ||||
| Apply ACL | Specifies whether an |
Access Control List (ACL) is applied to the Microsoft Teams connection. An ACL provides security to an SBC using a Public IP. Valid |
selections: 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. |
| Protocol | Hard-coded value for protocol used with federated FQDN: TLS. |
| Downstream SBC Signaling Listen Port | Port 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 SBC | Maximum 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
| Field | Description |
|---|---|
| Signaling/Media Source IP | External (Internet-facing) IP address of the Microsoft Teams Direct Routing server that handles routing of messages for signaling and media. |
| Teams Proxy SBC | The IP/FQDN for the Proxy SBC for TLX to properly establish. |
| Protocol | Hard-coded value for protocol used with federated FQDN: TLS. |
| Port Number | The port used for TLS. Valid entry: 1024 - 65535. |
| SBC FQDN | FQDN for the SBC. |
Step 3: Summary
Easy Configuration Step 3 includes a summary of the information configured in Step 1 and Step 3.
...
Overview
Content Tools