Page History

...

• Public IP address

  Info
  If you plan to use Media Bypass, Microsoft requires ICE Lite. ICE RFC 5245 requires a public IP address assigned on the SBC interface without NAT. If you do not plan to use Media Bypass, ICE Lite is not required. The SBC can use a Public IP behind a NAT.

• FQDN name matching the Public IP address.
  
• Public certificate (issued by one of the supported CAs; see Domain Name for details about Wildcard certificate supported Certification Authorities). Wild Card certificates are supported.
  

Anchor
DomainName DomainName

Obtain Domain Name

...

Ensure you are running the latest SBC Edge Release:

...

1. Obtain Trusted Root and Intermediary signing certificates from your certification authority.
2. Access the WebUI.
3. To install Trusted Root Certificates, click Settings > Security > SBC Certificates > Trusted CA Certificates.
   
4. Click Import and select the trusted root certificates.
5. To install the SBC certificate, open Settings > Security > SBC Certificates > Sonus Certificate.

6. Validate the certificate is installed correctly.

   Caption
   0 Figure 1 Validate Certificate

7. Click Import  and select X.509 Signed Certificate.

8. Validate the certificate is installed correctly.

   Caption
   0 Figure 1 Validate Certificate
   Image Modified

Step 3: Deploy Baltimore Trusted Root Certificate

...

1. In the WebUI, click the Settings tab.

2. In the left navigation pane, go to Security > TLS Profiles.

3. Click the CreateTLS Profile ( ) icon at the top of the TLS Profile page.

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

   Caption
   0 Table 1 TLS Configuration - Example Values
   Parameter Example Value Description Microsoft Phone system (example name) TLS Protocol TLS 1.2 Only Validate Client FQDN Disabled

   Caption
   0 Figure 1 TLS - Example
   Image RemovedImage Added

Configure Node-Level Settings

1. In the WebUI, click the Settings tab.

2. In the left navigation page, access System > Node-Level Settings.

3. Configure the NTP and DNS Server with the appropriate configuration.

   Caption
   0 Figure 1 Node-level Settings - Example
   Image RemovedImage Added

Configure Node Interface

...

1. In the WebUI, click the Settings tab.

2. In the left navigation pane, go to Node Interfaces > Logical Interfaces.

3. Configure the parameters shown below:

   Note
   The Media Next Hop IP field (available on SWe Lite only; not shown below) must be configured with the Default Gateway for this interface.

   Caption
   0 Table 1 Logical Interfaces Configuration - Example Values
   Parameter Example Value Description To Microsoft Phone System Admin Interface Enable IP Assign Method Static (example) 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
   Image RemovedImage Added

Configure SIP Profile

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Media >Media List.
3. Click the ( ) icon at the top of  left corner and add a new Media List.

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

   Caption
   0 Table 1 Media List Configuration - Example Values
   Parameter Example Value Description Microsoft Phone System Media Profiles List Default G711a Default G711u NOTE: See Microsoft documentation for the list of codecs supported by Microsoft. Crypto Profile ID Microsoft Phone System (created on the previous step)

   Caption
   0 Figure 1 Media List - Example
   Image RemovedImage Added

Configure SIP Server Tables

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access SIP > SIP Server Tables.
3. Select the name of the table created in the previous step.
4. At the top left corner of the main configuration pane click Create New SIP Server, select IP/FQDN and add the pairing to the Direct Routing interface .

5. Repeat the operation for the other two SIP Server entries. Leave all other parameters as default.

   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 Microsoft Phone System Monitor SIP Options

   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 Microsoft Phone System Monitor SIP Options

   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 - Example
   Image RemovedImage Added

Configure Voice routing

...

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Call Routing Table.
   

3. Click the () icon at the top of  left corner and add a new Call Routing Table.

   Caption
   0 Figure 1 Create Call Routing Table

4. Configure the parameters as shown below. Click OK.

   Caption
   0 Table 1 Call Routing Table - Example Values
   Parameter Value Row ID Assigned by the system Description Microsoft Phone System (example name)

5. From the left navigation pane, click on the Call Routing > Microsoft Phone System (the entry created in the last step).

6. Click the ().

7. Configure the parameters as shown below. Leave all other parameters as default.

8. Click OK.

   Caption
   0 Table 1 Call Routing Table Configuration - Example
   Parameter Value Description From Microsoft Phone System (example name) Number/Name Transformation Table Microsoft Phone System Destination Signaling Groups Choose the Signaling Group of a local equipment

   Caption
   0 Figure 1 Call Routing Table - Example
   Image RemovedImage Added

Anchor
Signaling Group Signaling Group

Configure Signaling Group

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

3. For the SBC 1000-2000, from the Create Signaling Group drop down box, select SIP Signaling Group.

4. For the SWe Lite,click Add SIP SG.
   

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

6. Click OK.

   Caption
   0 Table 1 Signaling Group Configuration - Example Values
   Parameter Value Description Microsoft Phone System SIP Profile Microsoft Phone System (from the previous steps) Media List ID Microsoft Phone System (from the previous steps) Signaling Media/Source IP Ethernet 1 (example, pick the interface which faces the Microsoft Phone System) Listen Port 5068 (arbitrary port) TLS TLS Profile ID: Microsoft Phone System (from the previous steps) Federated IP/FQDN sip-all.pstnhub.microsoft.com SIP server table Microsoft Phone System (from the previous steps) Load Balancing Priority SIP Profile Microsoft Phone System (from the previous steps) Call Routing Table Microsoft Phone System (from the previous steps) Outbound NAT traversal[1] Static NAT NAT Public IP 192.168.211.80 (Only required if “Static NAT” is selected) [1] Please ignore if the SBC has a Public IP assigned on the interface. The NAT Public IP is required only when the SBC is behind a NAT.

   Caption
   0 Figure 1 Signaling Group - Example
   Image Removed

...

When the remote peer forwards all the REFER messages without checking the destination, the SBC EDGE can be reconfigured to force the call through the remote peer. See below for configuration.

Modify Message Manipulation

1. In the WebUI, click the Settings tab.

2. In the left navigation pane, go to SIP > Message Manipulation > Message Rule Table.

3. Create a new Message Rule Table configured as shown below.

   Caption
   0 Figure 1 Create Message Rule Table
   Image Removed

4. In the left navigation pane, click the newly created Rule Table entry. 

5. Click Create Rule > Request Line Rule.

6. Configure the Request Line Rule as shown below.

   Caption
   0 Figure 1 Create SIP Request Line Tool
   Image Removed

Modify Signaling Group

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

3. Access the Signaling Group used for Teams.
   

4. Assign the Message Rule Table to the Teams Signaling Group as Inbound Message Manipulation.

   Caption
   0 Figure 1 Configure Signaling Group
   Image Removed

Modify Transformation Table

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

3. Click the ( Image Removed) icon at the top left corner to add a new Transformation Table.

4. Configure as shown below.

   Caption
   0 Figure 1 Create Transformation Table
   Image Removed

Modify Call Routing

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Call Routing Table.
   

3. In the Routing Table designated "From Teams," create a routing entry that points to the destination Teams Signaling Group (this must be the first routing entry in the list) and assign the newly created Transformation Table.

   Caption
   0 Figure 1 Create Call Routing Entry
   Image RemovedImage Added

Confirm the Configuration

...