Page History
...
- 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 Profiles
For interconnecting with Microsoft System Direct Routing, the following profiles are required:
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access SIP > SIP Profiles.
- Click the ( ) icon at Add 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 FQDNNOTE: 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.NOTE: If you set this field to Static and you expect the port number of the Contact header in the outbound SIP messages, you must configure the Static Host FQDN/IP field with the Listen Port number of the SIP signaling group. Origin Field Username <FQDN of SBC> (in the example aepsite6.SonusMS01.com) Pagebreak Caption 0 Figure 1 SIP Profile - Example
Create Analog Device Profile
...
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to CAS > CAS Signaling Profiles.
- From the Create CAS Profile drop down box, select FXS Profile.
- Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK.
Caption 0 Table 1 Analog Profile Entries - Example Values Parameter Value Description Analog Device Loop Start Type Specifies the loop start method. This field is country-specific, and may need to be adjusted for your country. Disconnect Tone Generation Specifies whether or not a disconnect tone is generated when a call is disconnected from the far end. This field is country-specific, and may need to be adjusted for your country. Caption 0 Figure 1 Analog Device 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 Add 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 Add 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
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 Add 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 Transformation Tables and Entries
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing > Transformation
- Click the ( ) icon at the Add at the top left corner to add a new Transformation Table.
- For Description, enter From Microsoft Teams to Analog Device
Click OK.
Caption 0 Figure 1 Create Transformation Table - In the left navigation panel, select the new table: Transformation > From Microsoft Teams to Analog Device
- Click the Create ( ) iconClick Create.
- 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 Extract Analog Device Extension Number Match Type Optional (Match One) Input Field Type: Called Address/Number
Value: .*3(\d{3})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 Analog Device to Microsoft Teams
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing> Transformation
- Click the ( ) icon at Add at the top left corner to add a new Transformation Table.
- For Description, enter From Analog Device to Microsoft Teams
Click OK.
Caption 0 Figure 1 Create Transformation Table - In the left navigation panel, select the new table: Transformation > From Analog Device to Microsoft Teams
- Click the Create ( ) iconClick Create.
- 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 Convert to Teams Client Number Match Type Optional (Match One) Input Field Type: Called Address/NumberValue: (.*) Output Field Type: Called Address NumberValue: \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 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 Routing Table 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 Analog Device 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 CAS 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 Analog Device CAS Signaling Profile Select (FXS) Analog Device Caller ID Type Country-specific Assigned Channels Assign CAS channels. Call Routing Table Default Routing Table 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 Add 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 () Add.
- 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 From Microsoft Teams to Analog Device Number/Name Transformation Table From Microsoft Teams to Analog (select Transformation Table you created above) Destination Signaling Groups From Microsoft Teams Pagebreak Caption 0 Figure 1 Call Routing Table - Example
From Analog Device to Microsoft Teams
...
- In the WebUI, click the Settings tab.
- In the left navigation page, access Call Routing Table.
Click the () icon at Add 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 Analog Device (the entry you just created).
- Click the () Add.
- 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 From Analog Device to Microsoft Teams Number/Name Transformation Table From Analog Device to Microsoft Teams (select Transformation Table you created above) Destination Signaling Groups From Analog Device 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 an Analog Device to Teams
- In the WebUI, click the Settings tab.
- In the left navigation page, access Signaling Groups > From Analog Device.
- From the Call Routing Drop down list, select From Analog Device.
Click OK.
Caption 0 Figure 1 Select Call Routing Table - From SIP Trunk