Skip to end of metadata
Go to start of metadata

In this article:

Tip

The configuration steps described in this article are examples.

Ribbon recommends referring to the SBC and PSX product documentation for detailed information on the commands, parameters, and flags used in the configuration examples of this guide.

Execute the steps in the same order as described in this article.

Certificate Exchange

If the TLS negotiation fails during a certificate exchange, try the following actions to resolve the issue:

  • Install/re-install the root and all intermediate certificates provided by your CA on the SBC.

  • Ensure that SBC's FQDN configured on the Teams side is identical to the one on the SBC's certificate.

  • Wildcard certificate exchange – Ensure the correct number of spaces exist before the domain name. For example, a wild card certificate generated for "*.example.com" is not valid for "*.customers.example.com". Refer to the article Ribbon Configurations with ACS Direct Routing - Configure SBC for TLS for details on SBC-supported certificate format.

Configuration of Direct Routing on Azure Portal

This section provides the configurations screenshots from the Azure portal for reference.

Ensure the DNS entry for the FQDN that is going to be provisioned is available before adding the SBC.


  1. Navigate to Communication Service → Direct Routing.

    Figure : Gateway Configuration - 1

  2. Configure the SBC FQDN and the port number.

    Figure : Gateway Configuration - 1

  3. Configure the Voice Route Name, Number Pattern and choose the SBC created above.

    Figure : Gateway Configuration - 1

  • No labels