Page History
Add_workflow_for_techpubs AUTH1 UserResourceIdentifier{userKey=
...
8a00a0c87befb553017c1aa323650024, userName='null'} JIRAIDAUTH CHOR-
...
8548 REV5 UserResourceIdentifier{userKey=
...
8a00a0c87befb553017c1aa323650024, userName='null'} REV6 UserResourceIdentifier{userKey=
...
8a00a02355cd1c2f0155cd26cb8305e9, userName='null'} REV3 UserResourceIdentifier{userKey=
...
8a00a0c86a61778d016a7d0876df0017, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a0c86a61778d016a7d0876df0017, userName='null'}
| Panel | ||||
|---|---|---|---|---|
In this section:
|
The
| Spacevars | ||
|---|---|---|
|
| Spacevars | ||
|---|---|---|
|
Step 1 - Select Scenario
| Anchor | ||||
|---|---|---|---|---|
|
Start
In the WebUI, click the Tasks tab.
In the left navigation pane, go to SBC Easy Setup > Easy Config Wizard.
Tip title Tip Make sure the
Easy Configuration wizard is running. For details, refer to Using the Easy Configuration Wizard. The Easy Config wizard on the SBC 1000/2000 creates the requested configuration by using the current configuration as a starting point. Existing configuration elements are retained, and the requested endpoint configuration are added as new configuration elements.Spacevars 0 product2
...
- From the Application
...
- dropdown list, select IP PBX ↔ Microsoft Teams
...
- .
...
- Configure per the field definitions below and click Next.
Scenario Field Definitions
| Field | Description |
|---|---|
| Scenario Parameters | |
| Application | Configuration template used: |
Scenario – Field Definitions
Application
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| IP PBX ↔ Microsoft Teams. |
| Scenario Description |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
Type a short description of the IP PBX ↔ Microsoft Teams deployment.
...
Name to describe the setup.
|
...
|
...
| |
| Telephone Country |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| Country in which the IP PBX ↔ Microsoft Teams is set up. |
| Emergency Services |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
Defines the Emergency Services |
...
for outgoing numbers. |
...
For the purpose of this illustration above, Emergency Services is not selected |
...
. Related field descriptions follow. Options:
|
...
|
...
|
...
| |||||
| Emergency Callback Number 1 |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| First Callback Number in string format. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field. |
| Emergency Callback Number 2 |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| Second Callback Number in string format. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field. |
| PSAP Number |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| Defines the Public Safety Answering Point Number. Valid entry: 1 - 127 characters. This field displays only when ELIN Identifier or E911/E112 is the value set for the Emergency Services field. |
| SIP Sessions (SIP Properties) |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| Specifies the number of simultaneous SIP-to-Destination sessions required for the deployment. |
...
| IP PBX |
|---|
...
| Type | |
...
Specify the type of the PBX used in the deployment. Valid |
...
options:
|
...
|
...
|
...
| Microsoft Teams | |
|---|---|
...
| bgColor | #FaFAFA |
|---|---|
| borderStyle | none |
| Teams Connection | The Teams connection type used for the network. Valid |
...
options:
|
NOTE: For Cloud Native, only Teams Direct Routing is supported.
...
Step 2 - Configure PBX and Teams Details for Endpoints
Start
Specify the configuration details based on the User- and Provider-side endpoints used for the deployment. Once completed, click Next to move to Step 3. (Or, click Previous to correct values on the previous screen.)
These fields apply if you selected IP PBX in 351074732.
Host
...
- Configure the IP PBX provider information (see below for field definitions).
- Configure the connection type information (see below for field definitions).
- Click Next.
Microsoft Teams: Teams Direct Routing - Standalone Direct Connection
Microsoft Teams: Teams Direct Routing - Local Media Optimization
Microsoft Teams: Teams Downstream SBC
Field Definitions
| Field | Description |
|---|---|
| IP PBX: <Type> | |
| Host | |
...
| Specify the IP address or FQDN for the host in the deployment. | |
| Protocol |
...
Specify the protocol to use for communicating with the IP PBX. Valid |
...
options:
|
...
|
...
| Port Number |
...
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| Specify the port number used for sending SIP messages to and receiving SIP messages from the IP PBX. |
| Use Secondary Server |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| Enables or disables a secondary server |
...
| for the deployment. |
...
Teams Connection Type
...
| borderColor | none |
|---|---|
| bgColor | #FAFAFA |
The Teams connection type used for the network. Valid selections:
- Standalone Direct Connection
- Local Media Optimization
| Secondary Server Host | Specifies the Secondary Server Host. This field is available only when Use Secondary Server is Enabled. |
| Protocol | The Protocol used for communicating with the Secondary Server Host. Valid options:
This field is available only when Use Secondary Server is Enabled. |
| Port Number | The Port Number used for sending and receiving messages between SBC and the Secondary Server Host. This field is available only when Use Secondary Server is Enabled. |
| Microsoft Teams: Teams Direct Routing | |
|---|---|
Teams Connection Type: Standalone Direct Connection | |
...
| Signaling/Media Source IP ( | |
...
| Teams |
...
| Attributes) |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| 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]
| Panel | ||||
|---|---|---|---|---|
| ||||
This field is available for Cloud Native 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
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| 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 options:
| |||||
| 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 options:
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 SBC Edge's media quality and bandwidth usage) | ||||||
| Signaling/Media Source IP (Teams Attributes) | 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 | |||||
...
options:
|
...
|
...
| Public IP Address |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| 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 |
...
options:
For details on configuring an ACL to be applied to an SBC, refer to Managing Access Control Lists. |
Server Pool Host 1
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| Protocol | Hard-coded |
...
Server Pool Host 2
| Panel | ||||
|---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 2: sip2.pstnhub.microsoft.com |
Server Pool Host 3
| Panel | ||||
|---|---|---|---|---|
| ||||
Hard-coded FQDN for the location of the server list for Server Pool Host 3: sip3.pstnhub.microsoft.com |
Federated FQDN
| Panel | ||||
|---|---|---|---|---|
| ||||
Hard-coded federated FQDN/IP for use with Microsoft Teams Direct Routing:
For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments |
Protocol
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
| 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 (Downstream Attributes) | 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. |
| Microsoft Teams: Teams Downstream SBC | |
|---|---|
| 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 |
...
| bgColor | #FAFAFA |
|---|---|
| borderStyle | none |
...
| The port used for TLS |
...
| . Valid entry: 1024 - 65535. | |
| SBC FQDN | FQDN for the SBC. |
...
Step 3 -
Confirm and Submit Configuration
This step displays a summary of the the configuration items from Step 1 and Step 2.
Start
- Click Finish.
...
This example displays an IP PBX ↔ Microsoft Teams with an Other IP PBX type.
Overview
Content Tools