You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

 

In this section:

This Best Practice includes instructions for migrating an 

Unable to show "metadata-from": No such page "_space_variables"
(either
Unable to show "metadata-from": No such page "_space_variables"
or
Unable to show "metadata-from": No such page "_space_variables"
) 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

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.

Prerequisites

A Public IP address without NAT is required to implement Direct Routing with Media Bypass.

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 drown down list, select Enable.

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

    Enable ICE Support

     

  7. 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 and create a new PSTN Online Gateway with Media Bypass enabled:

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

Configure SBC

Ensure the SIP Signaling Port is different from the Non Bypass trunk. For details, refer to Creating and Modifying SIP Signaling Groups.

  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. Click Apply.

  • No labels