© 2024 Ribbon Communications Operating Company, Inc. © 2024 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.
The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners. Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.
This document outlines the configuration best practices for the Ribbon solution covering the Ribbon Edge 8K when deployed with Microsoft Teams Direct Routing.
Ribbon’s Edge 8000 is the newest, high-performance member of our line of services gateway routers that combines security, routing, switching, and 10 Gbps WAN interfaces with next-generation voice and data services where the combination of broadband connectivity and advanced threat mitigation capabilities are required. By consolidating fast, highly available routing, security, and next-generation SBC capabilities in a single device, enterprises can remove network complexity, protect and prioritize resources, and improve user and application experience while lowering the total cost of ownership (TCO).
A Session Border Controller (SBC) is a network element deployed to protect SIP-based Voice over Internet Protocol (VoIP) networks. Early deployments of SBCs were focused on the borders between two service provider networks in a peering environment. This role has now expanded to include significant deployments between a service provider's access network and a backbone network to provide service to residential and/or enterprise customers.
The Edge 8000 series is comprised of two models,
The 8100/8300 platform is based on the Intel Atom 8-core processor with multiple interfaces. This platform shall meet the following high-level requirements:
Functionality
In the subsequent sections, Ribbon Edge 8100 and Edge 8300 are represented as Ribbon Edge 8K.
Direct Routing lets you connect a supported, customer-provided Session Border Controller (SBC) to Microsoft Teams Phone. With Direct Routing, you can connect your SBC to almost any telephony trunk or interconnect with third-party PSTN equipment. Direct Routing enables you to:
Use virtually any PSTN trunk with Teams Phone.
Configure interoperability between customer-owned telephony equipment, such as a third-party private branch exchange (PBX), analog devices, and Teams.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between the Ribbon Edge 8K and Teams Phone.
This guide contains the following configuration sections:
Captures the Microsoft Teams Direct Routing configuration.
It is not the goal of this guide to provide detailed configurations that meet the requirements of every customer. Use this guide as a starting point and build the Ribbon Edge 8K configurations in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers to configure both the Ribbon Edge 8K and the third-party product.
To perform this interop, you need to:
This configuration guide is offered as a convenience to Ribbon customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided “as is.” Users must take full responsibility for the application of the specifications and information in this guide.
The following aspects are required before proceeding with the interop:
The sample configuration in this document uses the following equipment and software:
This section covers the Ribbon Edge 8K deployment topology and the Interoperability Test Lab topology.
The following lab topology diagram shows connectivity between Ribbon Edge 8K and Microsoft Teams Direct Routing.
The sections in this document use the following sequence. The reader is advised to complete each section for successful configuration.
The following Ribbon Edge 8K configurations are included in this section:
TLS Configuration between Ribbon Edge 8K and Teams Direct Routing
Ribbon Edge 8K software image can be installed as mentioned below:
https://publicdoc.rbbn.com/display/E8KDOC10/Install+the+Image+File
The Edge 8300 model can be ordered with 24 active FXS analog ports, or 22 active FXS ports and 2 FXO ports.
Edge 8K is connected to the network as follows:
GE1: RJ45 is connected towards the PSTN leg. GE1, GE2, GE3 and GE4 are the members of BR1 VNF Private.
GE5: RJ45 is an additional interface on Edge 8K connected towards the Teams Direct Routing leg.
Log into the Edge 8K via serial console cable with "sysadm/<default password>".
Login as root "sudo -i" (enter the sysadm password).
Go to the setup wizard.
Navigate to System Startup Configuration > BR2 VNF Management.
SBC management is configured as follows:
Navigate to System Startup Configuration > Swe-Edge Configuration.
BR1 VNF Private IP can be configured as follows:
Navigate to System Startup Configuration > BR1 VNF Private.
The SBC is connected to the network as follows:
Ethernet 1: RJ45 "1" is connected towards the PSTN leg.
Ethernet 3: RJ45 "3" is connected towards the Teams leg.
Configure Ethernet 1 and Ethernet 3 of the SBC with the IP as follows:
Login to the SBC SWe Edge webUI.
Navigate to Networking Interfaces > Logical Interfaces.
Static routes are used to create communication to remote networks. In a production environment, static routes are mainly configured for routing from a specific network to a network that can only be accessed through one point or one interface (single path access or default route).
Add static routes towards the Eth1 interface 172.16.X.X (PSTN) and the Eth3 interface 172.16.X.X (Teams).
The default static route is towards the Eth1, which is in a private network.
Prerequisites:
Go Daddy Root Certificate Authority G2 and Go Daddy Secure Certificate Authority G2 are used as a trusted CA.
Request a certificate for the SBC and configure it based on the example using Go Daddy as follows:
Step 1: Generate a Certificate Signing Request and obtain the certificate from a Certificate Authority (CA).
Use the generated CSR text from the clipboard to obtain the certificate.
Step 2: Deploy the Root/Intermediate and SBC certificates on the SBC.
After receiving the certificates from the certificate authority, install the SBC Certificate and the Root/Intermediate certificates as follows:
Validate the certificate is installed correctly.
Configure the SBC with Teams Direct Routing using the Easy Config Wizard.
Fill in the details for Step 1 as follows:
Enter a value for SIP sessions as per the requirement. The value is listed up to 960.
Fill in the details for Step 2 as follows:
Review the configurations in Steps 1 and 2, and click the Finish button.
Follow these steps in Easy Config Wizard to deploy the Non NAT scenario for Teams Direct Routing.
Review the configurations in Steps 1 and 2, and click the Finish button.
Click OK. SBC will pop-up "System Configuration Completed".
Select the appropriate IP interface towards PSTN as shown below, as Signaling/Media source IP is set to Auto by default when configured with Easy Config Wizard.
Go to Settings > Signaling Groups > (SIP)Border Element > SIP IP Details.
The following Microsoft Teams Direct Routing configurations are included in this section:
Configure Office 365 Tenant Voice Routing
For Prerequisites on Teams Direct routing, refer to the following link:
https://learn.microsoft.com/en-us/MicrosoftTeams/direct-routing-plan
A Tenant is used within the Microsoft environment as a single independent enterprise that has subscribed to Office 365 services; through this tenant, administrators can manage projects, users, and roles. Access the Tenant configuration and configure as detailed below. (For details on accessing the Tenant, refer to Microsoft Teams Documentation).
a. Enter the SBC FQDN (Example below: test1.interopdomain.com). The FQDN must be configured for the Tenant in both the Domains and the DomainUrlMap fields.
b. Enter the SBC SIP Port (Example below - SipPort5061).
New-CsOnlinePSTNGateway -Fqdn test1.interopdomain.com -SipSignallingPort SipPort5061 -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true
2. Configure Teams usage for the user:
Enter the User Identity (Example below: -user1@domain.com).
Get-CsOnlineUser -Identity user1@domain.com Set-CsUser -Identity user1@domain.com -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI tel:+10001001008 Grant-CsOnlineVoiceRoutingPolicy -PolicyName "GeneralVRP" -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity user1@domain.com Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user1@domain.com
To configure Ribbon Edge 8K for Teams Direct Routing, follow Section A
The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide.
Sr. No. | Supplementary Features/Services | Coverage |
---|---|---|
1 | SIP OPTIONS and Failover | |
2 | Basic Call from PSTN to Teams | |
3 | Basic Call from Teams to PSTN | |
4 | Call Disconnect | |
5 | Call Hold & Call Resume | |
6 | Anonymous Call | |
7 | Long Duration Call | |
8 | Calling using Web Browser | |
9 | DTMF Support | |
10 | Comfort Noise and Mute/Unmute | |
11 | Early Media | |
12 | Blind Call Transfer | |
13 | Consultative Call Transfer | |
14 | Call Forward | |
15 | Simultaneous Ring | |
16 | Group Call Pickup | |
17 | Call escalation to an ad hoc conference | |
18 | Auto Attendant | |
19 | Call Queue | |
20 | Call Park |
Legend
Supported | |
Not Supported | |
N/A | Not Applicable |
For any support-related queries about this guide, contact your local Ribbon representative, or use the details below:
For detailed information about Ribbon products & solutions, go to:
https://ribboncommunications.com/products
For information about Microsoft Teams Direct Routing & solutions, go to:
https://learn.microsoft.com/en-us/microsoftteams/direct-routing-whats-new
This Interoperability Guide describes a successful configuration of the Ribbon Edge 8K and Microsoft Teams Direct Routing.
All features and capabilities tested are detailed within this document - any limitations, notes, or observations are also recorded to provide the reader with an accurate understanding of what has been covered and what has not.
Configuration guidance is provided to enable the reader to replicate the same base setup - there may be additional configuration changes required to suit the exact deployment environment.
© 2024 Ribbon Communications Operating Company, Inc. © 2024 ECI Telecom Ltd. All rights reserved.