Page History
...
Add_workflow_for_techpubs AUTH2AUTH1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f08a00a02355cd1c2f0155cd26cb41059c, userName='null'} JIRAIDAUTH SYM-27516 REV5AUTH1 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYM-25556 REV6 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6REV3 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a02355cd1c2f0155cd26cdb40a89, userName='null'} REV3REV4 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f98a00a02355cd1c2f0155cd26cc5207f0, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f08a00a02355cd1c2f0155cd26c7f0006a, userName='null'} REV2 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c38a00a02355cd1c2f0155cd26ca2f03d1, userName='null'}
| Panel | ||||
|---|---|---|---|---|
In this section:
|
...
| Info |
|---|
If Microsoft Teams Direct Routing is not configured on the SBC Edge, refer to Best Practice - Configuring SBC Edge for to Microsoft Teams Phone System Direct Routing - On Premises Deployment. |
Prerequisites
- Microsoft Teams Direct Routing must be configured on the SBC Edge. Refer to Best Practice - Configuring SBC Edge for to Microsoft Teams Phone System Direct Routing - On Premises Deployment.
- The applicable firewall port on the SBC Edge must be opened . Refer to: Firewall Securing the SBC with Media Bypass.
Settings.
| Info |
|---|
For Media Bypass, the following is supported:
|
| Note |
| A Public IP address without NAT is required to implement Direct Routing with Media Bypass. |
Replace the Existing Microsoft Teams Direct Routing Trunk
...
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to Signaling Groups.
Select the Signaling Group used for Microsoft Teams Direct Routing.
From the RTCP Multiplexing drop down list, select Enable.
Caption 0 Figure 1 Enable RTCP Multiplexing 
From the ICE Support drown drop down list, select Enable.
From the ICE Mode drop down list, select Lite.
Caption 0 Figure 1 Enable ICE Support 
Note 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).
- For deployment behind a NAT only:
- From the Outbound NAT Traversal drop down list, select Static NAT.
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).
Caption 0 Figure 1 Enable NAT 
Click Apply.
Create a Second Microsoft Teams Direct Routing trunk
...
Connect Teams admin tenant and , create a new PSTN Online Gateway with Media Bypass enabled, and create an entry for the new FQDN in your DNS:
| Code Block |
|---|
New-CsOnlinePSTNGateway -Fqdn sbc2.domain.com -SipSignallingPort 5062 -Enable $True -MediaBypass $true |
...
- If not using a wild card, update the certificate with the proper SAN. For details on Certificates, refer to Working with Certificates.
- In the WebUI, click the Settings tab.
- In the left navigation pane, go to SIP > SIP Profiles.
- Click the Create SIP Profile (
) icon at the top of the SIP Profile View page. 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 0 Figure 1 Configure SIP Profile Fields 
- In the left navigation pane, go to System > Signaling Groups.
- From the Create Signaling Group drop down list, select SIP Signaling Group.
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 0 Figure 1 Configure RTCP Multiplexing 
From the ICE Support drown down list, select Enable.
From the ICE Mode drop down list, select Lite.
Caption 0 Figure 1 Configure ICE Support 
For an SBC deployment behind a NAT only:
- From the Outbound NAT Traversal drop down list, select Static NAT.
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).
Caption 0 Figure 1 Configure NAT 
Click Apply.
| Pagebreak |
|---|
Overview
Content Tools