Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 5

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
CSS Stylesheet
img.confluence-embedded-image { display: inline-block !important; }

 

UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
Add_workflow_for_techpubs
AUTH2
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHSYM-2555627208
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f98a00a02355cd1c2f0155cd26c99e02c0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f08a00a02355cd1c2f0155cd26ce5f0b8d, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c38a00a02355cd1c2f0155cd26ca2f03d1, userName='null'}
 

Panel

In this section:

Table of Contents
maxLevel3

Info

Support for an SBC behind a NAT is in SBC Edge 1000/2000 Release 8.0.2 and later only; support in SBC SWe Lite is planned for a later release.

This Best Practice includes instructions for migrating an 

Spacevars
0product
(either
Spacevars
0longproduct
or
Spacevars
0product3
) from Microsoft Teams Direct Routing Non Media Bypass (implemented on an SBC) to Microsoft Teams Direct Routing Media Bypass.

...

 

Info

For Media Bypass, the following is supported:

  • Deployment on a
Note
A
  • Public IP address
without NAT is required to implement Direct Routing with Media Bypass.
  • Deployment behind NAT

Replace the Existing Microsoft Teams Direct Routing Trunk

...

  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. 

    Caption
    0Figure
    1Enable RTCP Multiplexing


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

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

    Caption
    0Figure
    1Enable 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).

  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). 

      Caption
      0Figure
      1Enable NAT

      Image Added

  8. 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

...

  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.

    Caption
    0Figure
    1Configure 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.

    Caption
    0Figure
    1Configure RTCP Multiplexing

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

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

    Caption
    0Figure
    1Configure 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).

     

    Caption
    0Figure
    1Configure NAT

    Image Added

  13. Click Apply.

Pagebreak