Ribbon SBC 1000/2000 V9.0.4 IOT MS Teams Virgin Media SIP Trunk Application Note

Interoperable Vendors

Copyright

© 2021 Ribbon Communications Operating Company, Inc. © 2021 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.

Document Overview

This document outlines the configuration best practices for Virgin Media SIP Trunk involving Ribbon SBC 2000 when deployed with Microsoft Teams. This document also provides the configuration snapshot of the interoperability performed between Ribbon's SBC 2000 and MS Teams.

Scope

This document provides configuration best practices for deploying Ribbon's SBC 2000 with MS Teams and associated clients. Note that these are configuration best practices and each customer may have unique needs and networks. Ribbon recommends that customers work with network design and deployment engineers to establish the network design which best meets their requirements.

Non-Goals

It is not the goal of this document to provide detailed configurations that will meet the requirements of every customer. Use this document as a starting point and build the SBC configurations in consultation with network design and deployment engineers.

Audience

This technical document is intended for telecommunications engineers with the purpose of configuring both the Ribbon SBC 2000 and the MS Teams and associated clients.

Steps will require navigating the third-party product as well as the Ribbon product using graphical user interface (GUI) or command line interface (CLI). An understanding of the basic concepts of TCP/UDP/TLS, IP/Routing, and SIP/RTP/SRTP is needed to complete the configuration and any necessary troubleshooting.

Pre-Requisites

The following aspects are required before proceeding with Ribbon SBC 2000 and MS Teams:

• MS Teams needs to create users with the correct tenant, add SBC IP in MS Teams, and provide certificates to Ribbon Team.

• Remote Desktop access to a Windows host is available for installing MS Teams client.

• Install certificates in Ribbon SBC 2000.

Product and Device Details

Network Topology Diagram

Interoperability Test Lab Topology (or Call Flow Diagram)

IOT high-level architecture covering call flows and overall topology is depicted below.

Section-A: SBC 2000 Configuration

Configuring SBC 2000

The following configuration steps provide an example of how to configure the Ribbon SBC 1000/2000 to interoperate with MS Teams and Virgin Media SIP Trunk:

1. SIP Profile
2. SIP Server
3. Media System
4. Media Profiles
5. Media List
6. Remote Authorization Tables
7. Message Manipulation
8. Signaling Groups
9. Transformation
10. Call Routing Table 
11. SBC Primary Certificate
12. Trusted CA Certificates

1. SIP Profile

SIP Profiles control how the Ribbon SBC 1000/2000 communicates with SIP devices. The profiles control important characteristics such as session timers, SIP Header customization, SIP timers, MIME payloads, and option tags. 

Select Settings > SIP > SIP Profiles to access the SIP Profile screen.

The following figures show the default SIP profile used for the Ribbon 1000/2000 used for this configuration.

Virgin Media SIP Profile

MS Teams SIP Profile

Fax SIP Profile

2. SIP Server

SIP Server Tables contain information about the SIP devices connected to the Ribbon SBC 1000/2000. 

Select Settings > SIP > SIP Server Tables to access the SIP Server Tables screen.

The entries in the tables provide information about the IP addresses, ports, and protocols used to communicate with each SIP server. The entries also contain links to counters that are useful for troubleshooting, as shown in the following figures.

Fax SIP Server

3. Media System

The Media System Configuration contains system-wide settings for the Media System. Configuring the media system means setting the number of RTP/RTCP port pairs and the starting port.

Select Settings > Media > Media System Configuration to access the Media System configuration screen.

Media System

4. Media Profiles

Media Profiles specify the individual voice and fax compression codecs and their associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing the reduction of bandwidth requirements at the expense of voice quality. 

Select Settings > Media > Media Profiles. 

The following figures illustrate possible media profiles of the voice codecs used for the SBC 1000/2000.  The examples are for reference only.

5. Media List

The Media List shows the selected voice and fax compression codecs and their associated settings. 

 Select Settings > Media > Media List to access the Media List configuration screen.

6. Remote Authorization Tables

Remote Authorization Tables and their entries contain information used to respond to request message challenges by an upstream server. The Remote Authorization Tables on this page appear as options in Creating and Modifying Entries in the SIP Servers. (For additional information about Remote Authorization Tables, see the Ribbon online SBC 1000/2000 documentation.)

Select Settings > SIP > Remote Authorization Tables to access the Remote Authorization Tables configuration screen.

Remote Authorization Table

7. Message Manipulation

SIP Message Manipulation feature is used by a SIP Signaling Group to manipulate the incoming or outgoing messages. This feature is intended to enhance interoperability with different vendor equipment and applications, and for correcting any fixable protocol errors in SIP messages on a fly without any changes to firmware/software.

The feature's Message Manipulation Engine (MME) manipulates SIP messages to compensate for interoperability issues between different vendor equipment and for dynamically correcting reparable protocol errors in SIP messages. The flows described in this article are message flows and should not be confused with call flows.

Select Settings > Message Manipulation > Message Rule Tables to access the Message Manipulation configuration screen.

1. MS teams by default adds a Privacy :id. You must create this message manipulation to remove it, and the called can see the calling party number.

8. Signaling Groups

Signaling Groups allow telephony channels for routing and sharing configuration. They are used for 

• routing calls and selecting Call Routes
• selecting Tone Tables and Action Sets
  
• specifying protocol settings and links to server, media, and mapping tables for SIP

Select Settings > Signaling Groups to access the Signaling Groups configuration screens.

9. Transformation

Transformation Tables facilitate the conversion of names, numbers, and other fields when routing a call. For example, transformations can convert a public PSTN number into a private extension number, or a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table. In addition, the Action Set Table can configure Transformation tables as a reusable pool.

Select Settings > Transformation to access the Transformation configuration screen.

10. Call Routing Table

Call Routing tables allow you to configure flexible routes for transferring calls between Signaling Groups and for translating the calls. They allow call transfers between ports and protocols, such as ISDN to SIP.  These tables serve as one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists, and the three types of Signaling Groups (ISDN, SIP, and CAS).

Select Settings > Call Routing Table to access the Call Routing Table configuration screen.

11. SBC Primary Certificate

You can change the certificate installed on the SBC Edge system by obtaining the signed certificate from a Trusted CA or from a local Stand-Alone Windows Certificate Authority.

Select Settings > Security > SBC Certificates > SBC Primary Certificate.

SBC Primary Certificate

12. Trusted CA Certificates

A trusted certificate authority issues a Trusted CA Certificate. These certificates are imported to the SBC Edge to establish its authenticity on the network.

Select Settings > Security > SBC Certificates > Trusted CA Certificates.

Section-B: MS Teams Configuration

Configuring MS Teams

The following Microsoft Teams configurations are included in this section:

1. Configuring Microsoft Teams
2. Obtain IP address and FQDN
3. Domain Name
4. Obtain a Certificate
5. Public Certificate
6. Configure and Generate Certificates on the SBC
7. Configure Office 365 Tenant Voice Routing

Configuring Microsoft Teams

Microsoft Teams Direct Routing Configuration

Consult the Microsoft documentation for detailed information on Direct Routing interface configuration guidelines, including the RFC standards and the syntax of SIP messages.

Obtain IP Address and FQDN

The following table provides the requirements for configuring the SBC to support Teams Direct Routing.

Domain Name

For the SBC to pair with Microsoft Teams, the SBC FQDN domain name must match a name registered in both the Domains and DomainUrlMap fields of the Tenant. Follow the steps to verify that the correct domain name is configured for the Tenant:

1. On the Microsoft Teams Tenant side, execute Get-CsTenant.
2. Review the output.
3. Verify that the Domain Name configured is listed in the Domains and DomainUrlMap attributes for the Tenant. If the Domain Name is incorrect or missing, the SBC will not pair with Microsoft Teams.

You can configure users from any SIP domain registered for the tenant. For example, you can configure user user@example.com with the SBC FQDN name sbc2.examplevoice.com, as long as both names are registered for the tenant.

Configure Domain Names - Example

Obtain a Certificate

Public Certificate

Make sure the certificate is issued by one of the supported certification authorities (CAs). Note that wildcard certificates are supported.

• Refer to Microsoft documentation for the supported CAs.
• Refer to Domain Name for certificate Common name formats.

Configure and Generate Certificates on the SBC

Microsoft Teams Direct Routing allows only TLS connections from the SBC for SIP traffic with a certificate signed by one of the trusted certification authorities.

Follow the steps to request a certificate for the SBC External interface and configure it based on the example using the GlobalSign:

• Generate a Certificate Signing Request (CSR) and obtain the certificate from a supported Certification Authority.
• Import the Public CA Root/Intermediate Certificate on the SBC.
• Import the Microsoft CA Certificate on the SBC.
• Import the SBC Certificate.

You can obtain the certificate through the Certificate Signing Request (see the following instructions). You can obtain the Trusted Root and Intermediary Signing Certificates from your certification authority.

Configure Office 365 Tenant Voice Routing

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. Perform the following steps to configure the Tenant. For details on accessing the Tenant, refer to Microsoft Teams Documentation.

1. Create Online PSTN Gateway that points to the SBC:
   1.  Enter the SBC FQDN (Example below: sbc1.rbbn.com).  Be sure to configure the FQDN for the Tenant in both the Domains and the DomainUrlMap fields.

   2.  Enter the SBC SIP Port (Example below - SipPort5061).

      New-CsOnlinePSTNGateway -Fqdn sbc1.rbbn.com -SipSignallingPort SipPort5061 -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true

2. Configure Teams usage for the user:
   1. 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

Supplementary Services and Features Coverage

The following checklist identifies the set of supplementary services/features covered through the configuration defined in this Interop document. 

Legend

Caveats

The following items should be noted in relation to this Interop document. These are either limitations, untested elements, or useful information pertaining to the Interoperability.

• IOP 17 - IP-PBX Line to PSTN - No answer timeout test. Ribbon SBC sent the call to second Virgin Media SBC, after the first Virgin Media SBC didn't answer, after that, the SBC sent "user not available" to MS Teams.

Support

For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:

• Sales and Support: 1-833-742-2661
• Other Queries: 1-877-412-8867
• Website: https://ribboncommunications.com/about-us

References

For detailed information about Ribbon products & solutions, please visit:

https://ribboncommunications.com/products

Conclusion

This Interoperability document describes a successful configuration and interop involving Ribbon SBC 2000 and MS Teams.

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.

© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.