AudioCodes Mediant User Manual

Configuration Note

AudioCodes Mediant™ Family of Media Gateways & Session Border Controllers

Connecting AudioCodes' SBC with Analog Device to Microsoft Teams Direct Routing Enterprise Model

Version 7.2

Configuration Note Contents

1 Introduction ......................................................................................................... 7

1.1 About Microsoft Teams Direct Routing .................................................................... 7

1.2 About AudioCodes SBC Product Series .................................................................. 7

1.3 Validated AudioCodes SBC Version ........................................................................ 8

2 Topology Example .............................................................................................. 9

2.1.1 Enterprise Model Implementation .............................................................................. 9

2.1.2 Environment Setup .................................................................................................. 11

2.1.3 Infrastructure Prerequisites ..................................................................................... 11

3 Configuring Teams Direct Routing .................................................................. 13

3.1 Prerequisites .......................................................................................................... 13

3.2 SBC Domain Name in the Teams Enterprise Model .............................................. 13

3.3 Configuration Example of Office 365 Tenant Direct Routing ................................. 14

3.3.1 Online PSTN Gateway Configuration ...................................................................... 14

3.3.2 Online PSTN Usage Configuration .......................................................................... 14

3.3.3 Online Voice Route Configuration ........................................................................... 15

3.3.4 Online Voice Routing Policy Configuration .............................................................. 15

3.3.5 Enable Online User .................................................................................................. 15

3.3.6 Assigning Online User to the Voice Route .............................................................. 15

3.3.7 Analog Device Voice Route Configuration .............................................................. 16

3.3.8 Configure with User Management Pack 365 (Optional) .......................................... 16

4 Configuring AudioCodes SBC ......................................................................... 17

4.1 SBC Configuration Concept in Teams Direct Routing ........................................... 17

4.2 IP Network Interfaces Configuration ...................................................................... 18

4.2.1 Configure VLANs ..................................................................................................... 18

4.2.2 Configure Network Interfaces .................................................................................. 19

4.3 SIP TLS Connection Configuration ........................................................................ 20

4.3.1 Configure the NTP Server Address ......................................................................... 20

4.3.2 Create a TLS Context for Teams Direct Routing ..................................................... 21

4.3.3 Configure a Certificate ............................................................................................. 22

4.3.4 Method for Generating and Installing the Wildcard Certificate ................................ 25

4.3.5 Deploy Baltimore Trusted Root Certificate .............................................................. 26

4.4 Configure Media Realms ........................................................................................ 27

4.5 Configure SIP Signaling Interfaces ........................................................................ 28

4.6 Configure Proxy Sets and Proxy Address .............................................................. 29

4.6.1 Configure Proxy Sets ............................................................................................... 29

4.6.2 Configure a Proxy Address ...................................................................................... 30

4.7 Configure Coders ................................................................................................... 32

4.8 Configure IP Profiles .............................................................................................. 35

4.9 Configure IP Groups .............................................................................................. 39

4.10 Configure SRTP ..................................................................................................... 41

4.11 Configuring Message Condition Rules ................................................................... 42

4.12 Configure Classification Rules ............................................................................... 43

4.13 Configure IP-to-IP Call Routing Rules .................................................................... 45

4.14 Configure Firewall Settings .................................................................................... 47

Version 7.2 3 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

5 Verify the Pairing Between the SBC and Direct Routing ............................... 49

6 Verify ATA Registered Users in the SBC ........................................................ 51

A Configuring MP-1xx ATA for Connecting Analog Devices ............................ 53

A.1 Configure Proxy Server and Registration ............................................................... 53

A.2 Configure the Endpoint Phone Number Table ....................................................... 54

A.3 Configure the Hunt Group ...................................................................................... 55

A.4 Configure IP-to-Hunt Group Routing ...................................................................... 55

A.5 Configure SIP UDP Transport Type and Fax Signaling Method ............................ 56

B Configuring MP-20x ATA for Connecting Analog Devices ............................ 57

B.1 Configure SIP Interface Settings ............................................................................ 57

B.2 Configure Media Streaming Parameters ................................................................ 58

B.3 Configuring Line Settings ....................................................................................... 59

C Syntax Requirements for SIP Messages 'INVITE' and 'OPTIONS' ................. 61

C.1 Terminology ........................................................................................................... 61

C.2 Syntax Requirements for 'INVITE' Messages ........................................................ 61

C.3 Requirements for 'OPTIONS' Messages Syntax .................................................... 62

C.4 Connectivity Interface Characteristics .................................................................... 63

AudioCodes Mediant SBC 4 Document #: LTRT-33426

Configuration Note Notices

Notice

Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document can be downloaded from

https://www.audiocodes.com/library/technical-documents.

This document is subject to change without notice.

Date Published: August-13-2020

WEEE EU Directive

Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product.

Customer Support

Customer technical support and services are provided by AudioCodes or by an authorized AudioCodes Service Partner. For more information on how to buy technical support for AudioCodes products and for contact information, please visit our website at

https://www.audiocodes.com/services-support/maintenance-and-support

Stay in the Loop with AudioCodes

Abbreviations and Terminology

Each abbreviation, unless widely used, is spelled out in full when first used.

Version 7.2 5 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

(added note for Baltimore

Document Revision Record

LTRT Description

33421 Initial document release for Version 7.2. Teams Enterprise Model.

33422 Modified Section: Deploy Baltimore Trusted Root Certificate

Trusted Root Certificate and MTLS implementation).; Configure SIP Signaling Interfaces; Configure IP Groups

33423 Note removed regarding external firewall.

33424 Licenses consolidated into one section.

33425

33426 Update to the “Related Documentation” table to include the Mediant 1000B Gateway

Update to topology figures and correction for parameter “Remote Update Support” to “SIP UPDATE Support”.

& E-SBC product.

Documentation Feedback

AudioCodes continually strives to produce high quality documentation. If you have any comments (suggestions or errors) regarding this document, please fill out the Documentation Feedback form on our website at https://online.audiocodes.com/documentation-feedback

AudioCodes Mediant SBC 6 Document #: LTRT-33426

Configuration Note 1. Introduction

1 Introduction

This Configuration Note describes an example setup of the AudioCodes Enterprise Session Border Controller (hereafter, referred to as SBC) for interworking between Company's SIP Trunk, ATA device and Microsoft's Teams Direct Routing environment. For configuring the Office 365 side, please refer to

us/microsoftteams/direct-routing-configure.

This document is intended for IT or telephony professionals.

1.1 About Microsoft Teams Direct Routing

Teams Direct Routing allows connecting a customer-provided SBC to the Microsoft Phone System. The customer-provided SBC can be connected to almost any telephony trunk, or connect with third-party PSTN equipment. The connection allows:

 Using virtually any PSTN trunk with Microsoft Phone System

 Configuring interoperability between customer-owned telephony equipment, such as

third-party PBXs, analog devices, and Microsoft Phone System

1.2 About AudioCodes SBC Product Series

https://docs.microsoft.com/en-

AudioCodes' family of SBC devices enables reliable connectivity and security between the Enterprise's and the service provider's VoIP networks.

The SBC provides perimeter defense as a way of protecting Enterprises from malicious VoIP attacks; mediation for allowing the connection of any PBX and/or IP-PBX to any service provider; and Service Assurance for service quality and manageability.

Designed as a cost-effective appliance, the SBC is based on field-proven VoIP and network services with a native host processor, allowing the creation of purpose-built multiservice appliances, providing smooth connectivity to cloud services, with integrated quality of service, SLA monitoring, security and manageability. The native implementation of SBC provides a host of additional capabilities that are not possible with standalone SBC appliances such as VoIP mediation, PSTN access survivability, and third-party value-added services applications. This enables Enterprises to utilize the advantages of converged networks and eliminate the need for standalone appliances.

AudioCodes SBC is available as an integrated solution running on top of its field-proven Mediant Media Gateway and Multi-Service Business Router platforms, or as a software-only solution for deployment with third-party hardware. The SBC can be offered as a Virtualized SBC, supporting the following platforms: Hyper-V, AWS, AZURE, AWP, KVM and VMWare.

Version 7.2 7 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

AudioCodes sales

1.3 Validated AudioCodes SBC Version

Microsoft has successfully conducted validation tests with AudioCodes' Mediant SBC Ver. 7.20A.250. Previous firmware versions may run successfully; however, Microsoft did not test such versions. For updated list refer to

for Direct Routing.

Note: For implementing Microsoft Teams Direct Routing based on the configuration

described in this document, AudioCodes SBC must be installed with a License Key that includes the following features:

• MSFT (general Microsoft license)

Note: By default, all AudioCodes media gateways and SBCs are shipped with this license (except MSBR products, Mediant 500 SBC, and Mediant 500 Media Gateway).

• SW/TEAMS (Microsoft Teams license)

• Number of SBC sessions (based on requirements)

• Transcoding sessions (only if media transcoding is needed)

• Coders (based on requirements)

For more information about the License Key, contact your representative.

List of Session Border Controllers certified

AudioCodes Mediant SBC 8 Document #: LTRT-33426

Configuration Note 2. Topology Example

SIP Trunk

Enterprise Network

DMZ

Manag ement

Stat ion (OAMP)

ITSP

IP-PBX

Anal og D evice s

ATA

Session Bor der Controller

LAN

PSTN

Internet

Phone System

Firew all

2 Topology Example

Teams Direct Routing can be implemented in the Enterprise or Hosting Models.

2.1.1 Enterprise Model Implementation

The interoperability example between AudioCodes SBC and Company SIP Trunk with Teams Direct Routing Enterprise Model assume the following topology setup:

 Enterprise deployed with ATA, connected analog devices and the administrator's

management station, located on the LAN

 Enterprise deployed with Teams Phone System Direct Routing Interface located on

the WAN for enhanced communication within the Enterprise

 Enterprise wishes to offer its employees enterprise-voice capabilities and to connect

the Enterprise to the PSTN network using Company's SIP Trunking service

 AudioCodes SBC is implemented to interconnect between the SIP Trunk and Teams

Direct Routing located in the WAN

The figure below illustrates this topology example:

Figure 2-1: Connection Topology with SIP Trunk on the LAN

Version 7.2 9 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

SIP Trunk

Enterprise Network

DMZ

Manag ement

Stat ion (OAMP)

ITSP

IP-PBX

Anal og D evice s

ATA

Session Bor der Controller

LAN

PSTN

Internet

Phone System

Firew all

Figure 2-2: Connection Topology with SIP Trunk on the WAN

AudioCodes Mediant SBC 10 Document #: LTRT-33426

Configuration Note 2. Topology Example

Company SIP Trunk operates with RTP media type

2.1.2 Environment Setup

The example topology includes the following environment setup:

Table 2-1: Environment Setup

Area Setup

Network

 Teams Direct Routing environment is located on the Enterprise'

(or Service Provider’s) WAN

 Company SIP Trunk is located on the LAN

Signaling Transcoding

Codecs Transcoding

 Teams Direct Routing operates with SIP-over-TLS transport type  Company SIP Trunk operates with SIP-over-UDP transport type

 Teams Direct Routing supports G.711A-law, G.711U-law, G.729

and SILK (NB and WB) coders

 Company SIP Trunk supports G.711A-law, G.711U-law, and

G.729 coders

Media Transcoding

 Teams Direct Routing operates with SRTP media type



2.1.3 Infrastructure Prerequisites

The table below shows the list of infrastructure prerequisites for deploying Teams Direct Routing.

Table 2-2: Infrastructure Prerequisites

Infrastructure Prerequisite Details

Certified Session Border Controller (SBC)

SIP Trunks connected to the SBC

Office 365 Tenant

Domains

Public IP address for the SBC

Fully Qualified Domain Name (FQDN) for the SBC

Public DNS entry for the SBC

Public trusted certificate for the SBC

Firewall ports for Direct Routing Signaling

Firewall IP addresses and ports for Direct Routing Media

Media Transport Profile

Firewall ports for Teams Clients Media

See Microsoft's document Plan Direct Routing

Version 7.2 11 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

This page is intentionally left blank.

AudioCodes Mediant SBC 12 Document #: LTRT-33426

Configuration Note 3. Configuring Teams Direct Routing

3 Configuring Teams Direct Routing

This section describes an example of Teams Direct Routing configuration to operate with AudioCodes SBC.

3.1 Prerequisites

Before you begin configuration, make sure you have the following for every SBC you want to pair:

 Public IP address

 FQDN name matching SIP addresses of the users

 Public certificate, issued by one of the supported CAs

3.2 SBC Domain Name in the Teams Enterprise Model

The SBC domain name must be from one of the names registered in 'Domains' of the tenant. You cannot use the *.onmicrosoft.com tenant for the domain name. For example, in Figure 3-1, the administrator registered the following DNS names for the tenant:

Table 3-1: DNS Names Registered by an Administrator for a Tenant

DNS name

ACeducation.info Yes Valid names:

adatumbiz.onmicrosoft.com No

hybridvoice.org Yes Valid names:

Users can be from any SIP domain registered for the tenant. For example, you can provide users user@ACeducation.info names are registered for this tenant.

Can be used

for SBC FQDN

with the SBC FQDN sbc1.hybridvoice.org so long as both

Examples of FQDN names

 sbc.ACeducation.info  ussbcs15.ACeducation.info  europe.ACeducation.info

Invalid name: sbc1.europe.ACeducation.info (requires

registering domain name europe.atatum.biz in 'Domains' first)

Using *.onmicrosoft.com domains is not supported for SBC names

 sbc1.hybridvoice.org  ussbcs15.hybridvoice.org  europe.hybridvoice.org

Invalid name: sbc1.europe.hybridvoice.org (requires registering

domain name europe.hybridvoice.org in 'Domains' first

Version 7.2 13 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

Figure 3-1: Example of Registered DNS Names

During creation of the Domain you will be forced to create public DNS record (sbc1.hybridvoice.org in our example.)

3.3 Configuration Example of Office 365 Tenant Direct Routing

Note: This section shows an example only. For more detailed information please refer

to Microsoft Site: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-

configure

3.3.1 Online PSTN Gateway Configuration

Use following PowerShell command for creating new Online PSTN Gateway:

New-CsOnlinePSTNGateway -Identity sbc1.hybridvoice.org -SipSignallingPort 5068 ForwardCallHistory $True -ForwardPai $True -MediaBypass $True -Enabled $True

3.3.2 Online PSTN Usage Configuration

Use following PowerShell command for creating an empty PSTN Usage: Set-CsOnlinePstnUsage -Identity Global -Usage @{Add="Interop"}

AudioCodes Mediant SBC 14 Document #: LTRT-33426

Configuration Note 3. Configuring Teams Direct Routing

3.3.3 Online Voice Route Configuration

Use following PowerShell command for creating new Online Voice Route and associate it with PSTN Usage:

New-CsOnlineVoiceRoute -Identity "audc-interop" -NumberPattern "^\+" OnlinePstnGatewayList sbc1.hybridvoice.org -Priority 1 -OnlinePstnUsages "Interop"

3.3.4 Online Voice Routing Policy Configuration

Use following PowerShell command for assigning the Voice Route to the PSTN Usage:

New-CsOnlineVoiceRoutingPolicy "audc-interop" -OnlinePstnUsages "Interop"

Use the following command on the Teams Direct Routing Management Shell after reconfiguration to verify correct values:

Get-CsOnlinePSTNGateway

Identity : sbc1.hybridvoice.org Fqdn : sbc1.hybridvoice.org SipSignallingPort : 5068 CodecPriority : SILKWB, SILKNB, PCMU, PCMA ExcludedCodecs :

FailoverTimeSeconds : 10 ForwardCallHistory : True ForwardPai : True SendSipOptions : True MaxConcurrentSessions : Enabled : True MediaBypass : True

Note: The commands specified in Sections 3.3.5 and 3.3.6, should be run for each

Teams user (excluding ATA device users) in the company tenant.

3.3.5 Enable Online User

Use following PowerShell command for enabling online user:

Set-CsUser -Identity user1@company.com -EnterpriseVoiceEnabled $true - HostedVoiceMail $true -OnPremLineURI tel:+12345678900

3.3.6 Assigning Online User to the Voice Route

Use following PowerShell command for assigning online user to the Voice Route:

Grant-CsOnlineVoiceRoutingPolicy -PolicyName "audc-interop" -Identity user1@company.com

Note: The command specified in Section 3.3.7 does not need to be run for each ATA

device user, if the number pattern already points to the PSTNGateway and has been associated with PSTN Usage (see Section 3.3.3).

Version 7.2 15 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

3.3.7 Analog Device Voice Route Configuration

Use the following PowerShell command for creating a new Online Voice Route and associating it with PSTN Usage:

New-CsOnlineVoiceRoute -Identity "audc-interop" -NumberPattern "^\+12345678901" OnlinePstnGatewayList sbc1.hybridvoice.org -Priority 1 -OnlinePstnUsages "Interop"

3.3.8 Configure with User Management Pack 365 (Optional)

As an alternative to PowerShell commands, AudioCodes recommend using User Management Pack 365 (UMP365). UMP365 provides a simple web-portal user interface for configuring and managing the Online Voice Route and associating it with PSTN Usage and PSTN Gateway. See examples below:

Figure 3-2: Example of Adding new Voice Route

Figure 3-3: Example of Voice Routes Table

AudioCodes Mediant SBC 16 Document #: LTRT-33426

Configuration Note 4. Configuring AudioCodes SBC

Ana log

Device s

SI P

Trunk

Pro xy Set IP Group

SIP

Interface

SIP

Interface

IP Group Proxy Set

SIP

Interface

IP Group

SBC

Phone System

4 Configuring AudioCodes SBC

This section provides example of step-by-step procedures on how to configure AudioCodes SBC for interworking between Teams Direct Routing and the Company SIP Trunk. These configuration procedures are based on the topology example described in Section 2.1.1 on page 9, and includes the following main areas:

 SBC LAN interface – ATA devices environment

 SBC WAN interface - Company SIP Trunking and Teams Direct Routing environment

This configuration is done using the SBC's embedded Web server (hereafter, referred to as Web interface).

Notes:

• For implementing Teams Direct Routing based on the configuration described in

this section, AudioCodes SBC must be installed with a License Key. For more information, see Section 1.3 on page 8.

• The scope of this document does not cover all security aspects for configuring this

topology. Comprehensive security measures should be implemented per your organization's security policies. For security recommendations on AudioCodes’ products, refer to the Recommended Security Guidelines document, which can be found at AudioCodes web site

4.1 SBC Configuration Concept in Teams Direct Routing

The diagram below represents AudioCodes’ device configuration concept.

Figure 4-1: SBC Configuration Concept

Version 7.2 17 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

ITSP

Management

Stat ion (OAMP )

LAN

WAN

DMZ

LAN Port

Vlan ID 1

Vlan ID 2

Session B order Controll er

Phone System

Firew all

ATA

IP-PBX

4.2 IP Network Interfaces Configuration

This section describes how to configure the SBC's IP network interfaces. There are several ways to deploy the SBC; however, this example employs the following deployment method:

 SBC interfaces with the following IP entities:

• Teams Direct Routing and Company SIP Trunk, located on the WAN

• IP-PBX and/or ATA, located on the LAN

 SBC connects to the WAN through a DMZ network

 Physical connection: The type of physical connection depends on the method used to

connect to the Enterprise's network. In the example topology, SBC connects to the LAN and DMZ using dedicated ethernet ports (i.e., two ports and two network cables are used).

 SBC also uses two logical network interfaces:

• LAN (VLAN ID 1)

• DMZ (VLAN ID 2)

Figure 4-2: Network Interfaces in the Example Topology

4.2.1 Configure VLANs

This section describes how to configure VLANs for each of the following interfaces:

 LAN VoIP (assigned the name "LAN_IF")

 WAN VoIP (assigned the name "WAN_IF")

 To configure the VLANs:

1. Open the Ethernet Device table (Setup menu > IP Network tab > Core Entities folder

> Ethernet Devices).

2. There will be one existing row for VLAN ID 1 and underlying interface GROUP_1.

3. Add another VLAN ID 2 for the WAN side

Figure 4-3: Configured VLAN IDs in Ethernet Device

AudioCodes Mediant SBC 18 Document #: LTRT-33426

Configuration Note 4. Configuring AudioCodes SBC

Prefix

Length

According to your Internet

4.2.2 Configure Network Interfaces

This section describes how to configure the IP network interfaces for each of the following interfaces:

 LAN Interface (assigned the name "LAN_IF")

 WAN Interface (assigned the name "WAN_IF")

 To configure the IP network interfaces:

1. Open the IP Interfaces table (Setup menu > IP Network tab > Core Entities folder >

IP Interfaces).

2. Configure the IP interfaces as follows (your network parameters might be different):

Table 4-1: Configuration Example of the Network Interface Table

Index

Application

Types

OAMP+ Media +

Control

Media + Control (as this interface points

to the internet,

enabling OAMP is

not recommended)

The configured IP network interfaces are shown below:

Interfac

e Mode

IPv4

Manual

IPv4

Manual

IP Address

10.15.77.77 16 10.15.0.1 10.15.27.1 LAN_IF vlan 1

195.189.192.157

(DMZ IP address of

SBC)

Gateway DNS I/F Name

195.189.192.129 (router's IP

address)

provider's

instructions

Figure 4-4: Configured Network Interfaces in IP Interfaces Table

Ethernet

Device

WAN_IF vlan 2

Version 7.2 19 AudioCodes Mediant SBC

Teams Direct Routing & Analog Devices

4.3 SIP TLS Connection Configuration

This section describes how to configure the SBC for using a TLS connection with the Teams Direct Routing Phone System. This configuration is essential for a secure SIP TLS connection. The configuration instructions example in this section are based on the following domain structure that must be implemented as part of the certificate which must be loaded to the host SBC:

 CN: sbc1.hybridvoice.org

 SAN: sbc1.hybridvoice.org

This certificate module is based on the Service Provider's own TLS Certificate. For more certificate structure options, see Microsoft Teams Direct Routing documentation.

The Phone System Direct Routing Interface allows only TLS connections from SBCs for SIP traffic with a certificate signed by one of the Trusted Certification Authorities.

Currently, supported Certification Authorities can be found in the following link:

https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#public-trustedcertificate-for-the-sbc

4.3.1 Configure the NTP Server Address

This section describes how to configure the NTP server's IP address. It is recommended to implement an NTP server (Microsoft NTP server or another global server) to ensure that the SBC receives the current date and time. This is necessary for validating certificates of remote parties. It is important, that NTP Server will locate on the OAMP IP Interface (LAN_IF in our case) or will be accessible through it.

 To configure the NTP server address:

1. Open the Time & Date page (Setup menu > Administration tab > Time & Date).

2. In the 'Primary NTP Server Address' field, enter the IP address of the NTP server

(e.g., 10.15.28.1).

Figure 4-5: Configuring NTP Server Address

3. Click Apply.

AudioCodes Mediant SBC 20 Document #: LTRT-33426

Configuration Note 4. Configuring AudioCodes SBC

media. You might want to configure additional parameters according to your company's policies. For example, you might want to configure Online Certificate

4.3.2 Create a TLS Context for Teams Direct Routing

This section describes how to configure TLS Context in the SBC. AudioCodes recommends implementing only TLS to avoid flaws in SSL.

 To configure the TLS version:

1. Open the TLS Contexts table (Setup menu > IP Network tab > Security folder > TLS

Contexts).

2. Create a new TLS Context by clicking New at the top of the interface, and then configure

the parameters using the table below as reference:

Table 4-2: New TLS Context

Index Name TLS Version

1 Teams (arbitrary descriptive name) TLSv1.2

All other parameters can be left unchanged with their default values.

Note: The table above exemplifies configuration focusing on interconnecting SIP and

Status Protocol (OCSP) to check if SBC certificates presented in the online server are still valid or revoked. For more information on the SBC's configuration, see the User's Manual, available for download from https://www.audiocodes.com/library/technical-

documents.

Figure 4-6: Configuring TLS Context for Teams Direct Routing

3. Click Apply.

Version 7.2 21 AudioCodes Mediant SBC

+ 46 hidden pages

AudioCodes Mediant User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Configuration Note

Table of Contents

Configuration Note Notices

WEEE EU Directive

Customer Support

Abbreviations and Terminology

Related Documentation

Document Revision Record

Documentation Feedback

1 Introduction

1.1 About Microsoft Teams Direct Routing

1.2 About AudioCodes SBC Product Series

1.3 Validated AudioCodes SBC Version

2 Topology Example

2.1.1 Enterprise Model Implementation

2.1.2 Environment Setup

2.1.3 Infrastructure Prerequisites

3 Configuring Teams Direct Routing

3.1 Prerequisites

3.2 SBC Domain Name in the Teams Enterprise Model

3.3 Configuration Example of Office 365 Tenant Direct Routing

3.3.1 Online PSTN Gateway Configuration

3.3.2 Online PSTN Usage Configuration

3.3.3 Online Voice Route Configuration

3.3.5 Enable Online User

3.3.6 Assigning Online User to the Voice Route

3.3.7 Analog Device Voice Route Configuration

3.3.8 Configure with User Management Pack 365 (Optional)

4 Configuring AudioCodes SBC

4.1 SBC Configuration Concept in Teams Direct Routing

4.2 IP Network Interfaces Configuration

4.2.1 Configure VLANs

4.2.2 Configure Network Interfaces

4.3 SIP TLS Connection Configuration

4.3.1 Configure the NTP Server Address

4.3.2 Create a TLS Context for Teams Direct Routing