![]() |
Ribbon Documentation Portal will be unavailable Thursday February 2nd 2023 between 2:00 PM EST ~ 12:00 PM. More Info |
In this section:
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 with the following parameters:
Step | Configuration | Description | Example |
---|---|---|---|
1 | Carrier | Create a DNS entry for the SBC | mycarrier.com -> 15.8.7.65 |
Configure the Office 365 Tenant for each new client with the following parameters:
Step | Configuration | Description | Example |
---|---|---|---|
1 | Carrier | Create a DNS entry for Customer 1 | customer1.mycarrier.com -> 15.8.7.65 |
2 | Customer | Add the SBC FQDN as the domain for the tenant. The customer will then provide the TXT entry to the Carrier. | customer1.mycarrier.com |
3 | Carrier | Add the TXT entry in the DNS to validate the SBC connection | customer1.mycarrier.com TXT -> MS=5462165656 |
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.
Follow the instructions below to configure each carrier:
The SIP Profile enables configuration for parameters, such as SIP Header customization, option tags, etc.
Click the (+
icon at the top of left corner and add a new SIP profile.Configure parameters shown below:
SIP Profile Configuration - Example Values Parameter FQDN in From Header FQDN In Contact Header Origin Field name Example Value Description Microsoft Phone System Customer 1 Static Static Host <FQDN assigned to customer 1> customer1.mycarrier.com Static <FQDN assigned to customer 1> customer1.mycarrier.com
SIP Profile Customer 1 - Example
From the Create Signaling Groupdrop down box, select SIP Signaling Group.
Configure the parameters as shown below. Leave the default values for all other parameters.
Click OK. Signaling Group 1 Customer Configuration - Example Values 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 SIP server table Load Balancing Call Routing Table Outbound NAT traversal*
Parameter Example Value None Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice) Priority Microsoft Phone System (from Microsoft Teams Direct Routing Best Practice) Static NAT
Signaling Group Customer 1 - Example
Click the (+
Configure the parameters as shown below.
Transformation Table - Example Values Row ID Assigned by the system Description Microsoft Phone System Customer 1(example name)Parameter Example Value
Create Transformation Table
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Transformation Entry Customer 1 Configuration - Example Description To Microsoft Phone System Customer 1 (example name) Input Type Called Address/Number Input Value <Enter Customer 1 Phone Number > (\+151048512\d{2}) Output Type Output ValueParameter Example Value Match Type Mandatory Called Address/Number \1
Transformation Entry Customer 1- Example
To configure a new Call Routing Table:
From the left navigation pane, click on the Call Routing > From Carrier SIP Trunk.
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
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)
Call Routing Table - Example
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.