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

Compare with Current View Page History

Version 1 Current »

If Microsoft Teams is in Media Bypass mode, you must configure the SBC Edge as detailed in this section (if Microsoft Teams is not in Media Bypass mode, this configuration is not required).

For Media Bypass, the following is supported:

  • Deployment on a Public IP address
  • Deployment behind NAT

Configure Signaling Group 

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); configuration for NAT is required only if deployment is behind NAT.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups

  3. From the Create Signaling Group drop down box, select SIP Signaling Group.

  4. Configure the parameters as shown below. Leave the default values for all other parameters.

  5. Click OK.

    Signaling Group Configuration - Example Values

    Parameter

    Value

    RTCP MultiplexingEnable
    ICE SupportEnabled
    ICE ModeLite
    Outbound NAT Traversal*Static NAT
    NAT Public IP (Signaling/Media)*Public Address for the NAT device assigned on the media port for your network
    Static NAT InboundDisabled (this field should not be configured for Media Bypass Teams deployment)

    *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the pubic IP address of NAT device is required when the SBC has Private IP).

    The peer endpoint must support the a=rtcp-mux exchange in order for the RTP and RTCP ports to be multiplexed into one data port.

    SIP Signaling Group - Example

  • No labels