Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ReleaseSpecifications

SWe Lite 7.0.4 or later

SBC 1000/2000 7.0.3 or later

Does not support Media Bypass.*
8.0.0 or later

Supports Media Bypass.*

NOTE: If Release 8.0.0 is not generally available, contact your local Ribbon sales representative for early access options.

*Teams Direct Routing With/Without Media Bypass - Example Below

Caption
0Figure
1Teams Direct Routing - Without Media Bypass

 

Caption
0Figure
1Teams Direct Routing - With Media Bypass

 

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups
  3. For the SBC 1000-2000, from the Create Signaling Group drop down box, select SIP Signaling Group.

  4. For the SWe Lite,click Add SIP SG.

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

  6. Click OK.

    Caption
    0Table
    1Signaling Group Configuration - Example Values

    Parameter

    Value

    Description

    Microsoft Phone System

    SIP Profile

    Microsoft Phone System (from the previous steps)

    Media List ID

    Microsoft Phone System (from the previous steps)

    Signaling Media/Source IP

    Ethernet 1 (example, pick the interface which faces the Microsoft Phone System)

    Listen Port

    5068 (arbitrary port)

    TLS

    TLS Profile ID: Microsoft Phone System (from the previous steps)

    Federated IP/FQDN

    sip-all.pstnhub.microsoft.com

    SIP server table

    Microsoft Phone System (from the previous steps)

    Load Balancing

    Priority

    SIP Profile

    Microsoft Phone System (from the previous steps)

    Call Routing Table

    Microsoft Phone System (from the previous steps)

    Outbound NAT traversal[1]

    Static NAT

    NAT Public IP

    192.168.211.80 (Only required if “Static NAT” is selected)



    [1] Please ignore if the SBC has a Public IP assigned on the interface. The NAT Public IP is required only when the SBC is behind a NAT.

    Caption
    0Figure
    1Signaling Group - Example

Anchor
forward
forward
Configure REFER and Re-Invites for Call Forwarding

Info

This section is applicable to SBC SWe Lite only.

When the remote peer forwards all the REFER messages without checking the destination, the SBC EDGE can be reconfigured to force the call through the remote peer. See below for configuration.

Modify Message Manipulation

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to SIP > Message Manipulation > Message Rule Table.

  3. Create a new Message Rule Table configured as shown below.

    Caption
    0Figure
    1Create Message Rule Table

    Image Added

  4. In the left navigation pane, click the newly created Rule Table entry. 
  5. Click Create Rule > Request Line Rule.

  6. Configure the Request Line Rule as shown below.

Modify Signaling Group

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups
  3. Access the Signaling Group used for Teams.

  4. Assign the Message Rule Table to the Teams Signaling Group as Inbound Message Manipulation.

    Caption
    0Figure
    1Configure Signaling Group

    Image Added

Modify Transformation Table

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access SIP > Transformation Tables.
  3. Click the ( Image Added) icon at the top left corner to add a new Transformation Table.

  4. Configure as shown below.

    Caption
    0Figure
    1Create Transformation Table

    Image Added

Modify Call Routing

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing Table.
  3. In the Routing Table designated "From Teams," create a routing entry that points to the destination Teams Signaling Group (this must be the first routing entry in the list) and assign the newly created Transformation Table.

    Caption
    0Figure
    1Create Call Routing Entry

    Image Added

Confirm the Configuration

...