CSS Stylesheet |
---|
img.confluence-embedded-image { display: inline-block !important; } |
Add_workflow_for_techpubs AUTH2 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} AUTH1 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYM-25556 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} REV2 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c3, userName='null'}
Panel | ||||
---|---|---|---|---|
In this section:
|
This Best Practice includes instructions for migrating an
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
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
Info |
---|
If Microsoft Teams Direct Routing is not configured on the SBC Edge, refer to Best Practice - Configuring SBC Edge for Microsoft Teams Phone System Direct Routing On-Premises Deployment. |
The applicable firewall port on the SBC Edge must be opened. Refer to: Firewall Settings.
Note |
---|
A Public IP address without NAT is required to implement Direct Routing with Media Bypass. |
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:
Code Block |
---|
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.
Caption | ||||
---|---|---|---|---|
| ||||
From the ICE Support drown down list, select Enable.
From the ICE Mode drop down list, select Lite.
Caption | ||||
---|---|---|---|---|
| ||||
|
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 and create a new PSTN Online Gateway with Media Bypass enabled:
Code Block |
---|
New-CsOnlinePSTNGateway -Fqdn sbc2.domain.com -SipSignallingPort 5062 -Enable $True -MediaBypass $true |
Note |
---|
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.
Caption | ||||
---|---|---|---|---|
| ||||
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.
Caption | ||||
---|---|---|---|---|
| ||||
From the ICE Support drown down list, select Enable.
From the ICE Mode drop down list, select Lite.
Caption | ||||
---|---|---|---|---|
| ||||
Click Apply.
Pagebreak |
---|