...

Access the WebUI. Refer to Logging into the SBC Edge.

Configure TLS Profile

The TLS profile defines the crypto parameters for the SIP protocol; it is used as the transport type for incoming and outgoing SIP trunks.

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access SIP > SIP Profiles.

3. Click the ( ) icon at the top of left corner and add a new SIP profile.

4. 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.

5. Leave all other parameters as default.

6. 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

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Signaling Groups
   

3. From the Create Signaling Group drop down box, select SIP Signaling Group.

4. Configure the parameters as shown below. Leave the default values for all other parameters.

5. Click OK.

   Caption
   0 Table 1 Signaling Group Configuration - Example Values
   traversal 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

   
   

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Signaling Groups
   

3. From the Create Signaling Group drop down box, select SIP Signaling Group.

4. Configure the parameters as shown below. Leave the default values for all other parameters.

5. Click OK.

    

   Caption
   0 Table 1 Signaling Group Configuration - Example Values
   traversal 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

...