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

Compare with Current View Page History

« Previous Version 2 Current »

These instructions assume the SBC Edge is installed and running, and is connected to the WebUI.

Access the SBC Edge WebUI

Access the WebUI. Refer to Logging into the SBC Edge.

Configure Host Information and DNS

The Host Information and DNS configuration contains system information that is used by the SBC Edge, including host, domain, and NTP server information.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access System > Node-Level Settings. The Node-Level Settings page is displayed.
  3. Configure the NTP and DNS Servers with network-specific data.
  4. Leave all other parameters as default.

  5. Click Apply.

    TLS Configuration - Example Values

    ParameterExample Value
    Host Nameaepsite6
    Domain NameSonusMS01.com
    Use NTPYes
    NTP ServerSpecifies the FQDN, IPv4, or IPv6 address of the NTP server. If the host name is supplied, the SBC uses the DNS to connect to the NTP server.
    Use Primary DNSYes
    Primary Server IPXXX.XXX.XX.XXX

    Node-level Settings - Example

Configure Logical Interface

The SBC Edge supports system-supported Logical Interfaces, which are used to hold the IP address for each Ethernet port. One of these logical interfaces is assigned an IP address for transporting the VoIP media packets (i.e., RTP, SRTP) and protocol packets (i.e, SIP, RTCP, TLS). In this example, Ethernet 1 is configured for transporting packets for the Microsoft Teams Direct Routing connection.

Ensure the IP Routing Table contains the same information as in the network topology.
  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Node Interfaces > Logical Interfaces.
  3. Configure the parameters as shown below (example values are shown in the table; configure as per your network requirements). For details on field descriptions, refer to Configuring and Modifying Logical Interfaces.
  4. Leave all other parameters as default.

  5. Click Apply.

    Logical Interfaces Configuration - Example Values

    ParameterExample Value
    AliasTo Microsoft Phone 5
    DescriptionInterface to Interconnect with Microsoft Phone System
    Admin InterfaceEnable
    IP Assign MethodStatic
    Primary Address<Public IP of your SBC> (in the example 192.168.211.80)
    Primary Netmask<Mask of Public Interface of your SBC> (in the example 255.255.255.0)

    Logical Interfaces - Example


Create Profiles

For interconnecting with Microsoft System Direct Routing, the following profiles are required:

  • Teams Direct Routing Profile (SIP)
  • Analog Device Profile

Create Teams Direct Routing Profile

The Teams Direct Routing profile is used for connecting the SBC Edge to Microsoft Teams.

Create the Teams Direct Routing Profile as follows:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access SIP > SIP Profiles.
  3. Click Add at the top of left corner and add a new SIP profile.
  4. Configure the parameters as shown below (example values are shown in the table; configure as per your network requirements). For details on field descriptions, refer to Creating and Modifying SIP Profiles.
  5. Leave all other parameters as default.

  6. Click OK.

    SIP Profile Configuration - Example Values

    ParameterExample Value
    DescriptionTeams Direct Routing Profile
    FQDN in From HeaderSBC Edge FQDN
    FQDN In Contact HeaderSBC FQDNNOTE: For Microsoft Teams, the Signaling Group facing the Teams server must be configured as SBC Edge FQDN or Static (if there is more than one signaling group connected to Teams Direct Routing). The FQDN in Contact Header should be the same FQDN used in Office 365 Tenant Online Gateway. If the IP Address of the SBC is configured in the Contact Header instead of the FQDN of the SBC, a Forbidden message is received.NOTE: If you set this field to Static and you expect the port number of the Contact header in the outbound SIP messages, you must configure the Static Host FQDN/IP field with the Listen Port number of the SIP signaling group.
    Origin Field Username <FQDN of SBC> (in the example aepsite6.SonusMS01.com)

    SIP Profile - Example

Create Analog Device Profile

CAS Profiles control various aspects of loop start, DTMF, tone detection and other features associated with the variants of CAS calls. The Ribbon SBC 1000/2000 supports FXS, E&M and R2 signaling through CAS.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to CAS > CAS Signaling Profiles.
  3. From the Create CAS Profile drop down box, select FXS Profile.
  4. Configure the parameters as shown below. Leave the default values for all other parameters.

  5. Click OK.

    Analog Profile Entries - Example Values

    ParameterValue
    DescriptionAnalog Device
    Loop Start Type
    		Specifies the loop start method. This field is country-specific, and may need to be adjusted for your country.
    Disconnect Tone GenerationSpecifies whether or not a disconnect tone is generated when a call is disconnected from the far end. This field is country-specific, and may need to be adjusted for your country.

    Analog Device Profile - Example

Create SDES-SRTP Profile

The SDES-SRTP Profile defines the encryption mechanism used between the SBC and the Microsoft Teams Direct Routing interface; the Crypto Suite specifies the algorithm used to negotiate with a peer device.

Create a SDES-SRTP Profile as follows:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Media > SDES-SRTP.
  3. Click Add at the top left corner and add a new SDES-SRTP Profile.
  4. Configure the parameters as shown below. For details on field descriptions, refer to Creating and Modifying SIP Profiles.

  5. Leave all other parameters as default.

    Media Crypto Profile Configuration - Example Values

    ParameterExample Value
    DescriptionTeams Direct Routing SRTP
    Operation OptionRequired
    Crypto SuiteAES_CM_128_HMAC_SHA1_80

    Media Crypto Profile - Example

Create Media List

The Media List contains one or more of Media Profiles, which the SBC Edge uses for call transmission. A Media Profile specifies the individual voice codecs the SBC Edge uses for voice compression, voice quality, and associated settings.

Create a Media List for Teams Direct Routing as follows:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Media > Media List.
  3. Click Add at the top left corner and add a new Media List.
  4. Configure parameters as shown below. For details on field descriptions, refer to Creating and Modifying Media Lists.

  5. Leave all other parameters as default.

    Media List Configuration - Example Values

    ParameterExample Value
    DescriptionTeams Direct Routing Media List
    Media Profiles ListIn the Media Profiles List field, click Add/Edit. G711a and G711u are the default Media Profiles.
    • G711a
    • G711u
    NOTE: See Microsoft documentation for the list of codecs supported by Microsoft.
    SDES-SRTP Profile
    		Teams Direct Routing SRTP. This profile was created in the previous step.

    Media List - Example

Configure a SIP Server Table

SIP server tables define the information for the SIP interfaces connected to the SBC Edge; a SIP Server Table is required to support the Microsoft Phone System.

Create a Teams Direct Routing Server

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access SIP > SIP Server Tables
  3. Click Add at the top left corner and add a new SIP Server Table.
  4. For Description, enter Teams Direct Routing Server.

  5. Click OK.

    Create SIP Server Table

Configure Entries in the Teams Direct Routing Server

The information you configure in the SIP Server table pairs the SBC Edge to the Microsoft Teams Direct Routing interface. Three entries in the SIP Server table offer server redundancy to ensure a server is always up and communicating. If a server is down or not communicating, the SBC Edge will automatically move to the next Server entry on the list. 

Configure Teams Direct Routing Server entries as follows:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access SIP > SIP Server Tables.
  3. Select the name of the table created in the previous step.
  4. From the Create SIP Server drop down list, select IP/FQDN.

  5. Repeat this configuration for two additional SIP Server entries, using the field entries below. For details on field descriptions, refer to Creating and Modifying Entries in SIP Server Tables.

    SIP Server 1 Table - Example Values

    ParameterValue
    Priority1
    Hostsip.pstnhub.microsoft.com
    Port5061
    ProtocolTLS
    TLS ProfileTeams Direct Routing TLS
    MonitorSIP Options

    SIP Server 1 - Example Values

    SIP Server 2 Table - Example Values

    ParameterValue
    Priority2
    Hostsip2.pstnhub.microsoft.com
    Port5061
    ProtocolTLS
    TLS ProfileTeams Direct Routing TLS
    MonitorSIP Options

    SIP Server 2 - Example Values

     

    SIP Server 3 Table - Example Values

    ParameterValue
    Priority3
    Hostsip3.pstnhub.microsoft.com
    Port5061
    ProtocolTLS
    TLS ProfileMicrosoft Phone System
    MonitorSIP Options

    SIP Server 3 - Example Values

Create Transformation Tables and Entries

This Transformation Table contains a list of call routes that include routing configuration for calls between Microsoft Teams and an Analog Device. Two Transformation tables are required:

  • For Calls from Microsoft Teams to Analog Device
  • For Calls from Analog Device to Microsoft Teams

Calls From Microsoft Teams to Analog Device

This Transformation Table contains a list of call routes that include routing configuration for calls from Microsoft Teams to an Analog Device.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing > Transformation
  3. Click Add at the top left corner to add a new Transformation Table.
  4. For Description, enter From Microsoft Teams to Analog Device

  5. Click OK.

    Create Transformation Table

  6. In the left navigation panel, select the new table:  Transformation > From Microsoft Teams to Analog Device
  7. Click Create.
  8. Configure the parameters as shown below. Leave the default values for all other parameters.

  9. Click OK.

    Transformation Entries - Example Values

    ParameterValue
    DescriptionExtract Analog Device Extension Number
    Match TypeOptional (Match One)
    Input FieldType: Called Address/Number
    Value: .*3(\d{3})
    Output FieldType: Called Address Number
    Value: \1

    Transformation Entry - Example


     

    Transformation Table - Entry Added

Calls From Analog Device to Microsoft Teams

This Transformation Table contains a list of call routes that include routing configuration for calls from the Analog Device to Microsoft Teams.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing> Transformation
  3. Click Add at the top left corner to add a new Transformation Table.
  4. For Description, enter From Analog Device to Microsoft Teams

  5. Click OK.

    Create Transformation Table

  6. In the left navigation panel, select the new table:  Transformation > From Analog Device to Microsoft Teams
  7. Click Create.
  8. Configure the parameters as shown below. Leave the default values for all other parameters.

  9. Click OK.

    Transformation Entries - Example Values

    ParameterValue
    DescriptionConvert to Teams Client Number
    Match TypeOptional (Match One)
    Input FieldType: Called Address/NumberValue: (.*)
    Output FieldType: Called Address NumberValue: \1

    Transformation Table Entry

    Transformation Table - Entry Added

Create Signaling Groups

Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. In the case of SIP, they specify protocol settings and link to server, media and mapping tables. For Teams Direct Routing, you configure the Signaling Group to designate routing information for calls between SBC Edge and the Microsoft Phone System. Two Signaling Groups are required:

  • Signaling Group - Calls from Microsoft Teams to Analog Device
  • Signaling Group - Calls from Analog Device to Microsoft Teams


Calls From Microsoft Teams to Analog Device

  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

    ParameterValue
    DescriptionMicrosoft Teams
    SIP ProfileTeams Direct Routing Profile
    Media List IDTeam Direct Routing List
    Signaling Media/Private IP
    		Ethernet 1 (example, choose the interface which faces Microsoft Teams Direct Routing)
    Listen Port5061 TLS
    Federated IP/FQDNsip-all.pstnhub.microsoft.com
    SIP server tableTeams Direct Routing Server
    Load BalancingPriority: Register All
    SIP ProfileMicrosoft Phone System (from previous step)
    Call Routing TableDefault Routing Table
    Outbound NAT Traversal*Static NAT
    NAT Public IP*IP Address (Only required if “Static NAT” is selected)
    Static NAT InboundDisabled (this field should not be configured for Non-Media Bypass Teams deployment)
    *Outbound NAT Traversal and the NAT Public IP is required when the SBC is behind a NAT (the public IP address of the NAT device is required when the SBC has a Private IP).

    Signaling Group - Example



Calls from Analog Device to Microsoft Teams

  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 CAS 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

    ParameterValue
    DescriptionAnalog Device
    CAS Signaling ProfileSelect (FXS) Analog Device
    Caller ID TypeCountry-specific
    Assigned ChannelsAssign CAS channels.
    Call Routing TableDefault Routing Table

    Signaling Group - Example

Create Call Routing Tables

Two Call Routing Tables for transporting calls between the SBC and Microsoft Teams are required:

  • Call Route - Calls from Microsoft Teams to Analog Device
  • Call Route - Calls from Analog Device to Microsoft Teams

From Microsoft Teams to Analog Device

This Call Routing Table routes calls from Microsoft Teams.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing Table.

  3. Click Add at the top left corner and add a new Call Routing Table.

    Create Call Routing Table

  4. Configure the Description as From Microsoft Teams and click OK.
  5. From the left navigation pane, click on the Call Routing > Call Routing table.
  6. Select From Microsoft Teams (the entry you just created).
  7. Click Add.
  8. Configure the parameters as shown below. Leave all other parameters as default.

  9. Click OK.

    Call Routing Table Configuration - Example

    ParameterValue
    DescriptionFrom Microsoft Teams to Analog Device
    Number/Name Transformation TableFrom Microsoft Teams to Analog (select Transformation Table you created above)
    Destination Signaling GroupsFrom Microsoft Teams

    Call Routing Table - Example

From Analog Device to Microsoft Teams

This Call Routing Table routes calls from the Analog Device and sent to Microsoft Teams.

To add and configure a new Call Routing Table:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing Table.

  3. Click Add at the top of  left corner and add a new Call Routing Table.

    Create Call Routing Table

  4. Configure the Description as Microsoft Phone system and click OK.
  5. From the left navigation pane, click on the Call Routing > Call Routing table.
  6. Select From Analog Device (the entry you just created).
  7. Click Add.
  8. Configure the parameters as shown below. Leave all other parameters as default.

  9. Click OK.

    Call Routing Table Configuration - Example

    ParameterValue
    DescriptionFrom Analog Device to Microsoft Teams
    Number/Name Transformation TableFrom Analog Device to Microsoft Teams (select Transformation Table you created above)
    Destination Signaling GroupsFrom Analog Device

    Call Routing Table - Example

Update Signaling Groups for Call Route

The newly created Call Route must be associated to a Signaling Group as follows:

Associate Call Route to Signaling Group for Calls From Teams to Analog Device

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups > Teams Direct Routing.
  3. From the Call Routing Drop down list, select From Microsoft Teams.

  4. Click OK.

    Select Call Routing Table - Teams Direct Routing

Associate Call Route to Signaling Group for Calls from an Analog Device to Teams

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups > From Analog Device.
  3. From the Call Routing Drop down list, select From Analog Device.

  4. Click OK.

    Select Call Routing Table - From SIP Trunk

  • No labels