Log in
Ribbon Public Documentation Center
Spaces
Hit enter to search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
About Confluence
Log in
SBC Edge 12.1.x Documentation
Space shortcuts
Ribbon Public Product Documentation Home
SBC Edge 12.2.x
SBC Edge 12.0.x
SBC Edge 11.0.x
SBC Edge 9.0.x
Search
Page tree
Browse pages
Configure
Space tools
View Page
A
t
tachments (0)
Page History
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Pages
…
SBC Edge Portfolio 12.1.x Documentation
Configuring the SBC Edge Portfolio
Configuring Microsoft Teams Direct Routing
Page Information
Title:
Configuring Microsoft Teams Direct Routing
Author:
Ribbon Communications
Oct 11, 2023
Last Changed by:
Ribbon Communications
Nov 27, 2023
Tiny Link:
(useful for email)
https://publicdoc.rbbn.com/x/dpehG
Export As:
Word
·
PDF
Incoming Links
SBC Edge 12.1.x Documentation (9)
Page:
Connect SBC SWe Edge to Microsoft Teams Direct Routing Deployed in Azure
Home page:
SBC Edge Portfolio 12.1.x Documentation
Page:
Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing
Page:
Best Practice - How to Configure the SBC Edge Portfolio behind the NAT in Microsoft Teams Direct Routing
Page:
Best Practice - Configure Direct Routing Survivable Branch Appliance (SBA)
Page:
Best Practice - Configure Emergency Call for Microsoft Teams Direct Routing
Page:
Best Practice - How to Automate Migration to Microsoft Teams Direct Routing via Microsoft Azure AD
Page:
Best Practice - Configure Direct Routing Virtual Survivable Branch Appliance
Page:
Connect SBC SWe Edge to Microsoft Teams Direct Routing in AWS
Hierarchy
Parent Page
Page:
Configuring the SBC Edge Portfolio
Children (2)
Page:
Microsoft Teams Direct Routing - On Premises Deployment
Page:
Microsoft Teams Direct Routing - Public Cloud Deployment
Labels
There are no labels assigned to this page.
Recent Changes
Time
Editor
Nov 27, 2023 17:29
Ribbon Communications
View Changes
Oct 11, 2023 14:43
Ribbon Communications
View Page History
Overview
Content Tools
{"serverDuration": 129, "requestCorrelationId": "50d5fae85e11e151"}