In this section:
This Best Practice includes instructions for migrating an
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
If Microsoft Teams Direct Routing is not configured on the SBC Edge, refer to Microsoft Teams Direct Routing - On Premises Deployment.
For Media Bypass, the following is supported:
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:
Connect Microsoft Teams admin tenant and enable Media Bypass on the PSTN Online Gateway:
Set-CsOnlinePSTNGateway -Identity sbc.domain.com -MediaBypass $true
Select the Signaling Group used for Microsoft Teams Direct Routing.
From the RTCP Multiplexing drop down list, select Enable.
Enable RTCP Multiplexing
From the ICE Support drown down list, select Enable.
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).
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
Click Apply.
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.
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
Ensure the SIP Signaling Port is different from the Non Bypass trunk. For details, refer to Creating and Modifying SIP Signaling Groups.
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.
If 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 because the FQDN in Contact Header field is set to Static.
Modified: for 8.0.2
Configure SIP Profile Fields
Configure the fields identical to the Non Bypass Signaling Group, except the Listen Ports must be different.
From the RTCP Multiplexing drop down list, select Enable.
Configure RTCP Multiplexing
From the ICE Support drown down list, select Enable.
From the ICE Mode drop down list, select Lite.
Configure ICE Support
For an SBC deployment behind a NAT only:
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
Click Apply.