Page History
...
Info |
---|
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 LiteEdge. If configuration is not specified for a field, use the default value. |
...
- In the WebUI, click the Settings tab.
In the left navigation pane, go to Security > TLS Profiles.
- Click the Create TLS Profile ( ) icon at the top of the TLS Profile page. The Create TLS Profile page is displayed.
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 Creating and Modifying TLS Profiles.
Leave all other parameters as default.
Click OK.
Caption 0 Table 1 TLS Configuration - Example Values Parameter Example Value Description Teams Direct Routing TLS TLS Protocol TLS 1.2 Only Client Cipher List Select at least one of the following Microsoft/Ribbon common cyphers must be configured:
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Validate Client FQDN Disabled Pagebreak Caption 0 Figure 1 TLS - Example
Configure Host Information and DNS
...
- 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.
Caption 0 Table 1 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 Caption 0 Figure 1 Node-level Settings - Example
Configure Logical Interface
...
- 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.
Pagebreak Caption 0 Table 1 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)
Caption 0 Figure 1 Logical Interfaces - Example
Create SIP Profile
The SIP Profile controls how the SBC Edge communicates with SIP devices; the profile controls important characteristics such as: session timers, SIP header customization (including FQDN), SIP timers, MIME payloads, and option tags .A SIP Profile also defines which FQDN (Fully Qualified Domain Name) is used in the Contact Header and From Headers. For interconnecting with Microsoft System Direct Routing, two SIP Profiles are required:
- Teams Direct Routing Profile
- SIP Trunk Profile
...
Create Teams Direct Routing Profile
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Profiles.
Click the (
) icon at the top of left corner and add a new SIP profile.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 Creating and Modifying SIP Profiles.
Leave all other parameters as default.
Click OK.
Caption 0 Table 1 SIP Profile Configuration - Example Values Parameter
Example Value
Description
Teams Direct Routing Profile
FQDN in From Header
SBC Edge FQDN
FQDN In Contact Header
SBC FQDN
NOTE: For Microsoft Teams, the Signaling Group facing the Teams server must be configured as SBC Edge FQDN or Static (if there is more than one signaling group connected to Teams Direct Routing). The FQDN in Contact Header should be the same FQDN used in Office 365 Tenant Online Gateway. If the IP Address of the SBC is configured in the Contact Header instead of the FQDN of the SBC, a Forbidden message is received.
Origin Field Username
<FQDN of SBC> (in the example aepsite6.SonusMS01.com)
Pagebreak Caption 0 Figure 1 SIP Profile - Example
Create SIP Trunk Profile
Create a SIP Profile for the SBC Edge's SIP Trunk as follows:
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Profiles.
Click the (
) icon at the top of left corner and add a new SIP profile.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 Creating and Modifying SIP Profiles.
Leave all other parameters as default.
Click OK.
Caption 0 Table 1 SIP Profile Configuration - Example Values Parameter
Example Value
Description
SIP Trunk Profile
FQDN in From Header
Disable
FQDN In Contact Header
Disable
Origin Field Username SBC Caption 0 Figure 1 SIP Profile - Example
Create SDES-SRTP Profile
The SDES-SRTP Profile defines the encryption mechanism used between the SBC and the Microsoft Teams Direct Routing interface; the Crypto Suite specifies the algorithm used to negotiate with a peer device.
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Media > SDES-SRTP.
- Click the ( ) icon at the top left corner and add a new SDES-SRTP Profile.
Configure the parameters as shown below. For details on field descriptions, refer to Creating and Modifying SIP Profiles.
Leave all other parameters as default.
Caption 0 Table 1 Media Crypto Profile Configuration - Example Values Parameter
Example Value
Description
Teams Direct Routing SRTP
Operation Option
Required
Crypto Suite
AES_CM_128_HMAC_SHA1_80
Caption 0 Figure 1 Media Crypto Profile - Example
Anchor | ||||
---|---|---|---|---|
|
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Media > Media List.
- Click the ( ) icon at the top left corner and add a new Media List.
Configure parameters as shown below. For details on field descriptions, refer to Creating and Modifying Media Lists.
Leave all other parameters as default.
Caption 0 Table 1 Media List Configuration - Example Values Parameter
Example Value
Description
Teams Direct Routing Media List
Media Profiles List
In the Media Profiles List field, click Add/Edit. G711a and G711u are the default Media Profiles.
- G711a
- G711u
NOTE: See Microsoft documentation for the list of codecs supported by Microsoft.
SDES-SRTP Profile
Teams Direct Routing SRTP. This profile was created in the previous step.
Caption 0 Figure 1 Media List - Example
Configure a SIP Server Table
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables
Click the (
) icon at the top left corner and add a new SIP Server Table.- For Description, enter Teams Direct Routing Server.
Click OK.
Caption 0 Figure 1 Create SIP Server Table
Configure Entries in the Teams Direct Routing Server
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables.
- Select the name of the table created in the previous step.
- From the Create SIP Server drop down list, select IP/FQDN.
Repeat this configuration for two additional SIP Server entries, using the field entries below. For details on field descriptions, refer to Creating and Modifying Entries in SIP Server Tables.
Caption 0 Table 1 SIP Server 1 Table - Example Values Parameter
Value
Priority
1
Host
sip.pstnhub.microsoft.com
Port
5061
Protocol
TLS
TLS Profile
Teams Direct Routing TLS
Monitor
SIP Options
Pagebreak Caption 0 Figure 1 SIP Server 1 - Example Values Caption 0 Table 1 SIP Server 2 Table - Example Values Parameter
Value
Priority
2
Host
sip2.pstnhub.microsoft.com
Port
5061
Protocol
TLS
TLS Profile
Teams Direct Routing TLS
Monitor
SIP Options
Caption 0 Figure 1 SIP Server 2 - Example Values Pagebreak Caption 0 Table 1 SIP Server 3 Table - Example Values Parameter
Value
Priority
3
Host
sip3.pstnhub.microsoft.com
Port
5061
Protocol
TLS
TLS Profile
Microsoft Phone System
Monitor
SIP Options
Caption 0 Figure 1 SIP Server 3 - Example Values
Create a SIP Trunk Server
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables
Click the (
) icon at the top left corner and add a new SIP Server Table.- For Description, enter SIP Trunk Server.
Click OK.
Caption 0 Figure 1 Create SIP Server Table
Configure an Entry in the SIP Trunk Server
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Server Tables.
- Select the name of the table created in the previous step.
- From the Create SIP Server drop down list, select IP/FQDN.
Leave the remaining fields as default. For details on field descriptions, refer to Creating and Modifying Entries in SIP Server Tables.
Click OK.
Caption 0 Table 1 SIP Trunk Server - Example Values Parameter
Value
Priority
1
Host
Host FQDN for SBC
Port
5060
Protocol
UDP
Monitor
None
Caption 0 Figure 1 SIP Trunk Server - Example Values
Create Transformation Table and Entries
...
- 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.
Caption 0 Figure 1 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.
Caption 0 Table 1 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: \1Pagebreak Caption 0 Figure 1 Transformation Entry - Example Caption 0 Figure 1 Transformation Table - Entry Added
Calls From 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.
Caption 0 Figure 1 Create Transformation Table In the left navigation panel, select the new table: Transformation > From SIP Trunk: Passthrough.
Click the Create (
) icon.- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Caption 0 Table 1 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
Caption 0 Figure 1 Transformation Table Entry Caption 0 Figure 1 Transformation Table - Entry Added
Create Signaling Groups
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. In the case of SIP, they specify protocol settings and link to server, media and mapping tables. For Teams Direct Routing, you configure the Signaling Group to designate routing information for calls between SBC Edge and the Microsoft Phone System. Two Signaling Groups are required:
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups
From the Create Signaling Group drop down box, select SIP Signaling Group.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Caption 0 Table 1 Signaling Group Configuration - Example Values Parameter
Value
Description
From Microsoft Teams
SIP Profile
Teams Direct Routing Profile
Media List ID
Team Direct Routing List
Signaling Media/Private IP
Ethernet 1 (example, choose the interface which faces Microsoft Teams Direct Routing)
Listen Port
5061 TLS
Federated IP/FQDN
sip-all.pstnhub.microsoft.com
SIP server table
Teams Direct Routing Server
Load Balancing
Priority: Register All
SIP Profile
Microsoft Phone System (from previous step)
Call Routing Table
Default
Outbound NAT Traversal* Static NAT NAT Public IP*
IP Address (Only required if “Static NAT” is selected)
Static NAT Inbound Disabled (this field should not be configured for Non-Media Bypass Teams deployment) *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the public IP address of the NAT device is required when the SBC has a Private IP).Pagebreak Caption 0 Figure 1 Signaling Group - Example
Calls from SBC's SIP Trunk to Microsoft Teams
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups
From the Create Signaling Group drop down box, select SIP Signaling Group.
Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Caption 0 Table 1 Signaling Group Configuration - Example Values Parameter
Value
Description
From SIP Trunk
SIP Profile
SIP Trunk
Media List ID
SIP Trunk List
Signaling Media/Source IP
Ethernet 2 (example, choose the interface which faces the SIP Trunk)
Listen Port
5060 UDP
Federated IP/FQDN
IP Address SIP Server table
SIP Trunk Server
Load Balancing
Round Robin
SIP Profile
SIP Trunk
Call Routing Table
Default
Outbound NAT Traversal* None NAT Public IP*
IP Address (Only required if “Static NAT” is selected)
Static NAT Inbound Disabled (this field should not be configured for Non-Media Bypass Teams deployment) *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the public IP address of the NAT device is required when the SBC has a Private IP).
Pagebreak Caption 0 Figure 1 Signaling Group - Example
Create Call Routing Tables
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing Table.
Click the (
) icon at the top left corner and add a new Call Routing Table.Caption 0 Figure 1 Create Call Routing Table Configure the Description as From Microsoft Teams and click OK.
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.
Caption 0 Table 1 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.
Pagebreak Caption 0 Figure 1 Call Routing Table - Example
From SBC's SIP Trunk to Microsoft Teams
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing Table.
Click the (
) icon at the top of left corner and add a new Call Routing Table.Caption 0 Figure 1 Create Call Routing Table Configure the Description as Microsoft Phone system and click OK.
From the left navigation pane, click on the Call Routing > Call Routing table.
Select From SIP Trunk (the entry you just created).
- Click the ( ).
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Caption 0 Table 1 Call Routing Table Configuration - Example Parameter
Value
Description
To Microsoft Teams (Passthrough)
Number/Name Transformation Table
From SIP Trunk: Passthrough (select Transformation Table you created above)
Destination Signaling Groups
Choose the Signaling Group for Microsoft Teams Direct Routing
Caption 0 Figure 1 Call Routing Table - Example
Update Signaling Groups for Call Route
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups > Teams Direct Routing.
- From the Call Routing Drop down list, select From Microsoft Teams.
Click OK.
Caption 0 Figure 1 Select Call Routing Table - Teams Direct Routing
Associate Call Route to Signaling Group for Calls from SBC's SIP Trunk to Teams
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups > SIP Trunk.
- From the Call Routing Drop down list, select From SIP Trunk.
Click OK.
Caption 0 Figure 1 Select Call Routing Table - From SIP Trunk