Skip to end of metadata
Go to start of metadata

 

In this section:

Overview

These instructions detail how to configure Teams Direct Routing with a Carrier.

For the Carrier DNS and Customer Tenant configuration, refer to the Microsoft configuration guide.

These instructions assume that the Carrier's SBC FQDN is mycarrier.com, and the Customer SBC's FQDN is customer1.mycarrier.com.

Configure the Office 365 Tenant

Configure the Office 365 Tenant with the following parameters:

StepConfigurationDescriptionExample
1CarrierCreate a DNS entry for the SBCmycarrier.com -> 15.8.7.65

Configure the Office 365 Tenant for each new Client

Configure the Office 365 Tenant for each new client with the following parameters:

StepConfigurationDescriptionExample
1CarrierCreate a DNS entry for Customer 1customer1.mycarrier.com -> 15.8.7.65
2CustomerAdd the SBC FQDN as the domain for the tenant. The customer will then provide the TXT entry to the Carrier.customer1.mycarrier.com
3CarrierAdd the TXT entry in the DNS to validate the SBC connectioncustomer1.mycarrier.com TXT -> MS=5462165656

 

Configure the SBC for each new Client

For SBC deployment with Teams Direct Routing, refer to Best Practice - Configuring SBC Edge for Microsoft Teams Direct Routing.

Use the carrier SBC's FQDN (mycarrier.com) as the Static SBC FQDN into the SIP Profile.

Configure the Carrier SBC for each new Client

Follow the instructions below to configure each carrier:

Configure SIP Profile

The SIP Profile enables configuration for parameters, such as SIP Header customization, option tags, etc.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, access SIP > SIP Profiles.
  3. Click the (+) icon at the top of left corner and add a new SIP profile.

  4. Configure parameters shown below:

    Table : SIP Profile Configuration - Example Values

    Parameter

    Example Value
    DescriptionMicrosoft Phone System Customer 1

    FQDN in From Header

    Static
    Static Host<FQDN assigned to customer 1> customer1.mycarrier.com

    FQDN In Contact Header

    Static

    Origin Field name

    <FQDN assigned to customer 1> customer1.mycarrier.com

    Figure : SIP Profile Customer 1 - Example

     

Configure Signaling Group

  1. In the WebUI, click the Settings tab.
  2. In the left navigation page, access Signaling Groups.
  3. From the Create Signaling Groupdrop down box, select SIP Signaling Group.

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

  • Click OK.

    Table : Signaling Group 1 Customer Configuration - Example Values

     ParameterExample Value

    Description

    Microsoft Phone System Customer 1

    SIP Profile

    Microsoft Phone System Customer 1 (from the previous steps)

    Media List ID

    Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice)

    Signaling Media/Source IP

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

    Listen Port

    5061 (arbitrary port as assigned on the OnlinePSTNGateway)

    TLS

    TLS Profile ID: Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice)

    Federated IP/FQDN

     None

    SIP server table

     Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice)

    Load Balancing

     Priority

    Call Routing Table

     Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice)

    Outbound NAT traversal*

     Static NAT
    *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.


    Figure : Signaling Group Customer 1 - Example

     

Configure Transformation Table

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

  4. Configure the parameters as shown below. 

    Table : Transformation Table - Example Values

    ParameterExample Value

    Row ID

    Assigned by the system

    Description

    Microsoft Phone System Customer 1(example name)

     

     

    Figure : Create Transformation Table

      

     

  5. From the left navigation pane, click on the Transformation Table> Microsoft Phone System (the entry created in the last step).
  6. Click the (+) icon.
  7. Configure the parameters as shown below. Leave all other parameters as default.

  8. Click OK. 

    Figure : Transformation Entry Customer 1 Configuration - Example

    ParameterExample Value

    Description

    To Microsoft Phone System Customer 1 (example name)

    Match TypeMandatory

    Input Type

    Called Address/Number

    Input Value

    <Enter Customer 1 Phone Number > (\+151048512\d{2})

    Output Type

    Called Address/Number

    Output Value

    \1

    Figure : Transformation Entry Customer 1- Example

     

Configure Call Routing Table

To configure a new Call Routing Table:

  1. In the WebUI, click the Settings tab.
  2. From the left navigation pane, click on the Call Routing > From Carrier SIP Trunk.

  3. Click the (+) icon.
  4. Configure the parameters as shown below. Leave all other parameters as default.

  5. Click OK. 

    Figure : Call Routing Customer 1 - Routing Table configuration

    Parameter

    Example Value

    Description

    From Microsoft Phone System Customer 1 (example name)

    Number/Name Transformation Table

    Microsoft Phone System Customer 1

    Destination Signaling Groups

    Microsoft Phone System Customer 1 (from the previous steps)

    Figure : Call Routing Table - Example

     

Known Issue

The SBC sends a SIP Option for each delegate trunk. To resolve this, create a new SIP Server table that contains an unmonitored SIP Server Entry. Side effect is, assuming Microsoft Teams goes down, this delegate SG will not go down.