Versions Compared

Key

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

...

  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.

    Caption
    0Table
    1TLS 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



    Caption
    0Figure
    1Node-level Settings - Example
    Image Modified


Configure Logical Interface

...

  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.

    Pagebreak

    Caption
    0Table
    1Logical 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)



    Caption
    0Figure
    1Logical Interfaces - Example

    Image Modified

     



Create Profiles

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

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access SIP > SIP Profiles.
  3. Click the ( Image Removed) icon at 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.

    Caption
    0Table
    1SIP 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)


    Pagebreak

    Caption
    0Figure
    1SIP Profile - Example

    Image Modified


Create Analog Device Profile

...

  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.

    Caption
    0Table
    1Analog 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.



    Caption
    0Figure
    1Analog Device Profile - Example

    Image Modified


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.

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Media > SDES-SRTP.
  3. Click the ( Image Removed) icon at the 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.

    Caption
    0Table
    1Media Crypto Profile Configuration - Example Values


    ParameterExample Value
    DescriptionTeams Direct Routing SRTP
    Operation OptionRequired
    Crypto SuiteAES_CM_128_HMAC_SHA1_80



    Caption
    0Figure
    1Media Crypto Profile - Example

    Image Modified


Anchor
MediaList
MediaList
Create Media List

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Media > Media List.
  3. Click the ( Image Removed) icon at the 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.

    Caption
    0Table
    1Media 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.



    Caption
    0Figure
    1Media List - Example

    Image Modified


Configure a SIP Server Table

...

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

    Caption
    0Figure
    1Create SIP Server Table

    Image Modified


Configure Entries in the Teams Direct Routing Server

...

  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.

    Caption
    0Table
    1SIP Server 1 Table - Example Values


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


    Pagebreak

    Caption
    0Figure
    1SIP Server 1 - Example Values

    Image Modified


    Caption
    0Table
    1SIP Server 2 Table - Example Values


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



    Caption
    0Figure
    1SIP Server 2 - Example Values
     Image Modified

    Pagebreak

    Caption
    0Table
    1SIP Server 3 Table - Example Values


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



    Caption
    0Figure
    1SIP Server 3 - Example Values

    Image Modified


Create Transformation Tables and Entries

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing > Transformation
  3. Click the ( Image Removed) icon at the 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.

    Caption
    0Figure
    1Create Transformation Table

    Image Modified


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

    Caption
    0Table
    1Transformation 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


    Pagebreak

    Caption
    0Figure
    1Transformation Entry - Example
    Image Modified
     


    Caption
    0Figure
    1Transformation Table - Entry Added

    Image Modified


Calls From 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 the ( Image Removed) icon at 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.

    Caption
    0Figure
    1Create Transformation Table

    Image Modified


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

    Caption
    0Table
    1Transformation Entries - Example Values


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



    Caption
    0Figure
    1Transformation Table Entry

    Image Modified


    Caption
    0Figure
    1Transformation Table - Entry Added

    Image Modified


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:

...

  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.

    Caption
    0Table
    1Signaling 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).

    Pagebreak

    Caption
    0Figure
    1Signaling Group - Example

    Image Modified



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.

    Caption
    0Table
    1Signaling 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



    Caption
    0Figure
    1Signaling Group - Example

    Image Modified


Create Call Routing Tables

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing Table.
  3. Click the (Image Removed) icon at the Add at the top left corner and add a new Call Routing Table.

    Caption
    0Figure
    1Create Call Routing Table

    Image Modified


  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 the (Image Removed) Add.
  8. Configure the parameters as shown below. Leave all other parameters as default.
  9. Click OK.

    Caption
    0Table
    1Call 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


    Pagebreak

    Caption
    0Figure
    1Call Routing Table - Example

    Image Modified


From Analog Device to Microsoft Teams

...

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Call Routing Table.
  3. Click the (Image Removed) icon at Add at the top of  left corner and add a new Call Routing Table.

    Caption
    0Figure
    1Create Call Routing Table

    Image Modified


  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 the (Image Removed) Add.
  8. Configure the parameters as shown below. Leave all other parameters as default.
  9. Click OK.

    Caption
    0Table
    1Call 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



    Caption
    0Figure
    1Call Routing Table - Example

    Image Modified


Update Signaling Groups for Call Route

...

  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.

    Caption
    0Figure
    1Select Call Routing Table - Teams Direct Routing

    Image Modified


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.

    Caption
    0Figure
    1Select Call Routing Table - From SIP Trunk
    Image Modified