Best Practice - Migrating the SBC Edge from Direct Routing Non Media Bypass to Direct Routing Media Bypass

This Best Practice includes instructions for migrating an SBC Edge (either SBC 1000/2000 or SBC SWe Lite) from Microsoft Teams Direct Routing Non Media Bypass (implemented on an SBC) to Microsoft Teams Direct Routing Media Bypass.

Two options are available for migrating to Teams Direct Routing Media Bypass:

• Replace the existing Microsoft Teams Direct Routing trunk

• Create a second Microsoft Teams Direct Routing trunk
  
  

Prerequisites

• Microsoft Teams Direct Routing must be configured on the SBC Edge. Refer to Microsoft Teams Direct Routing - On Premises Deployment.
• The applicable firewall port on the SBC Edge must be opened Refer to: Firewall Settings.
  
  

Replace the Existing Microsoft Teams Direct Routing Trunk

Replacing the existing Microsoft Teams Direct Routing trunk is recommended if the Public Certificate is NOT a wildcard and a SAN (Subject Alternative Name) is unavailable; this solution moves all users to Media Bypass.

Replace the existing trunk as follows:

Configure Tenant

Connect Microsoft Teams admin tenant and enable Media Bypass on the PSTN Online Gateway:

Set-CsOnlinePSTNGateway -Identity sbc.domain.com -MediaBypass $true

Configure SBC

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Signaling Groups.

3. Select the Signaling Group used for Microsoft Teams Direct Routing.

4. From the RTCP Multiplexing drop down list, select Enable. 

   Enable RTCP Multiplexing

   
   
   

5. From the ICE Support drop down list, select Enable.

6. From the ICE Mode drop down list, select Lite.

   Enable ICE Support

    

   Before configuring Outbound NAT Traversal, obtain the Public IP address for your network (the Public IP address specified in the screen graphic is an example only).

7. For deployment behind a NAT only:
   
   1. From the Outbound NAT Traversal drop down list, select Static NAT.

   2. From the NAT Public IP (Signaling/Media) drop down list, enter the Public IP Address assigned on this media port (the Public IP used in the screen is an example only; use the Public IP for your network). 

      Enable NAT

      

8. Click Apply.

Create a Second Microsoft Teams Direct Routing trunk

Creating a second Microsoft Direct Routing trunk is recommended if the Public Certificate is a wildcard or a SAN (Subject Alternative Name) available; this solution allows a smooth migration of users to Media Bypass.

Add a second routing trunk as follows.

Configure Tenant

Connect Teams admin tenant, create a new PSTN Online Gateway with Media Bypass enabled, and create an entry for the new FQDN in your DNS:

New-CsOnlinePSTNGateway -Fqdn sbc2.domain.com -SipSignallingPort 5062 -Enable $True -MediaBypass $true

Configure SBC

1. If not using a wild card, update the certificate with the proper SAN. For details on Certificates, refer to Working with Certificates.
2. In the WebUI, click the Settings tab.
3. In the left navigation pane, go to SIP > SIP Profiles.
4. Click the Create SIP Profile ( ) icon at the top of the SIP Profile View page.

5. Configure the fields to be identical to the Non Bypass SIP Profile, except the FQDN in From Header and the FQDN in Contact Header are set to Static.

   Configure SIP Profile Fields

   

    

6. In the left navigation pane, go to System > Signaling Groups.
7. From the Create Signaling Group drop down list, select SIP Signaling Group.

8. Configure the fields identical to the Non Bypass Signaling Group, except the Listen Ports must be different.

9. From the RTCP Multiplexing drop down list, select Enable.
   

   Configure RTCP Multiplexing

   

10. From the ICE Support drown down list, select Enable.

11. From the ICE Mode drop down list, select Lite.

    Configure ICE Support

    

12. For an SBC deployment behind a NAT only:

    1. From the Outbound NAT Traversal drop down list, select Static NAT.

    2. From the NAT Public IP (Signaling/Media) drop down list, enter the Public IP Address of the NAT device assigned on this media port (the Public IP used in the screen is an example only; use the Public IP for your network).

     

    Configure NAT

    

13. Click Apply.