Skip to end of metadata
Go to start of metadata

Overview

The Direct Routing Survivable Branch Appliance (SBA) is a Ribbon Communications SBC 1000/2000 offer accomplished through close cooperation with Microsoft®. The SBA allows Direct Routing telephony services to remain available to Teams clients during a connectivity outage with Microsoft® 365 Phone System.

Figure : SBC 1000/2000 Direct Routing SBA offering Direct Routing call services to Teams clients


Direct Routing SBA - Quick Facts


Direct Routing SBA is available on SBC 1000/2000 Release 9.0.1 and later.

Contact your authorized Ribbon sales representative/partner for more information regarding approved SBC 1000/2000 Direct Routing SBA platforms and acquisition.


Direct Routing SBA FactsDetails
Platforms Supported

The Direct Routing SBA is available in select SBC 1000/2000 platforms that feature a late model Application Solution Module ;

  • The Direct Routing SBA is a software application found on the ASM HDD, and operates at run-time on the ASM's Windows Server OS
  • The Direct Routing SBA is activated based on a license key. Please refer to Working with Licenses for license specifics
  • The Direct Routing SBA is available for deployment on approved select SBC 1000 and SBC 2000 platforms shipped prior to Q4 2020
How SBA is OfferedThe Direct Routing SBA is offered in a physical appliance format; the SBA is not available within the SBC SWe Lite
SBA Deployment

The Direct Routing SBA should be deployed on the same site as an SBC connected to Direct Routing

SBA Services

The following services are available to Teams clients from the SBA

  • Making PSTN calls via local SBA/SBC with media flowing
  • Receiving PSTN calls via local SBA/SBC with media flowing
  • Hold & Resume of PSTN calls
Local Media/Media
  • Local Media Optimization (LMO) is not supported by the Direct Routing SBA
  • The media flows direct between Teams client and SBC, as opposed to Direct Routing SBA acting as a media relay

Prerequisites

Direct Routing


Direct Routing SBA (capable of SBC 1000 or SBC 2000)

Hardware and License

Please confirm: 

  • Licenses for the following features must be activated prior to deployment: 

    • SIP sessions

    • Direct Routing SBA

  • SBC and SBC Communication service must be on Ribbon SBC Edge Release 9.0.1.

  • The ASM must feature a licensed copy of Windows Server 2012 R2. Refer to the upgrade instructions to confirm the Windows Server OS found in your Direct Routing SBA-capable SBC 1000/2000 is correct.

  • The ASM should be loaded with the following ASM images: directrouting-ws2012r2-901b560-2020-11-23.

Migration from for Lync 2013 SBA/Skype for Business 2015 SBA

Please take the following actions to convert a Lync 2013/Skype for Business 2015 related ASM to support the Direct Routing SBA:

Name resolution

  • Public or Private FQDN that point Direct Routing SBA IP. No Public IP is required for the Direct Routing SBA.

  • Direct Routing SBA should resolve SBC Public FQDN with an address it can access; this is completed automatically for the SBC that hosts the ASM.

Use of Private FQDN for Direct Routing SBA

If you use a Private FQDN for Direct Routing SBA:

  • The SBC will have to be configured to use the DNS that host this Private zone.

  • You can not use a Public certificate for Direct Routing SBA, so Direct Routing SBA can not 336032102 .

Encryption-Related Certificates

Microsoft requires a SHA256 certificate for Direct Routing SBA in order to establish TLS connection with SBC. There are several options:

  1. Shared SBC Public certificate (recommended). This is only possible if your SBC certificate is matching one of the next 2 options:

    • SBC Certificate is a Wildcard certificate

      • i.e.: SBC Certificate Common Name "CN: *.mydomain.com" or SBC Certificate Subject Alternative Name "SAN: *.mydomain.com".

    • SBC Certificate have a SAN for Direct Routing SBA

      • i.e.: SBC Certificate Common Name "CN: sbc.mydomain.com" and SBC Certificate Subject Alternative Name "SAN: sba.mydomain.com".

  2. Use an existing Public or Private Certificate that cover Direct Routing SBA FQDN.

  3. Create a new Public or Private Certificate that cover Direct Routing SBA FQDN. In this case, a Public or Private Certificate Authority must be ready to sign the certificate for Direct Routing SBA.

Configure SBC 1000/SBC 2000

Run Easy Configuration Wizard

Follow the instructions for your specific scenario; both are listed below:

  • SCENARIO 1: If your SBC is not yet configured to connected Direct Routing (Greenfield), follow this section: 336032102

  • SCENARIO 2: If your SBC is already configured to connected Direct Routing (Upgrade from Standalone Direct Routing), follow this section: 336032102 .

SBC Not Configured for Direct Routing ("Greenfield")

LMO Incompatibility

Direct Routing SBA is not capable of offering Local Media Optimization (LMO) features, such as:

  • Teams Downstream SBC operations

  • Teams Central SBC operations

  • Teams Central Proxy operations

OPTION 1: To connect Direct Routing with a SIP Trunk, refer to: Configure SIP Trunk with Microsoft Teams.

  • On Step 2, be sure to set Configure Direct Routing SBA as True and enter the Direct Routing SBA FQDN.

OPTION 2: To connect Direct Routing with a ISDN PSTN, refer to: Configure ISDN PSTN with Microsoft Teams.

  • On Step 2, be sure to set Configure Direct Routing SBA as True and enter the Direct Routing SBA FQDN.


    Figure : Sample Easy Configuration Screen


Migration from for Lync 2013 SBA/Skype for Business 2015 SBA

After creating the new configuration, update the existing routing table to fork the call between the Signaling Group Direct Routing and Direct Routing SBA instead of Skype for Business.

SBC Already Connected to Direct Routing (Upgrade from Standalone Direct Routing)

  1. Follow the steps on this page: Configure Single Leg Endpoint for Microsoft Teams. On Step 2, configure Configure Direct Routing SBA as True and enter the Direct Routing SBA FQDN.

  2. Remap the call routing Direct Routing SBA Signaling Group:

    1. In the WebUI, click the Settings tab.

    2. From the left navigation pane, under Signaling Groups, select the Office 365 Direct Routing SBA SIP Signaling Group.

    3. Modify the Call Routing Table to select the From Microsoft Teams Direct Routing call routing table previously used on your device.

      Figure : Select Signaling Group


  3. Enable Forking to Direct Routing Server:

    1. From the left navigation pane, select  Call Routing > Call Routing Table. Select the From SIP Trunk call routing table.

    2. Select the existing entry with First Signaling Group set to Teams Direct Routing.

    3. Set the Fork Call to Yes.

    4. Click Apply.

      Figure : Enable Forking


  4. Add a call route entry for Direct Routing SBA:

    1. From the left navigation page, select Call Routing > Call Routing Table.

    2. Select From SIP Trunk table.

    3. Click the ().

    4. Configure the parameters as shown below. Leave all other parameters as default.

    5. Click OK.

      Table : Routing Entry - Example Values


      Parameter

      Value

      Description

      To Office 365 Direct Routing SBA

      Number/Name Transformation Table

      From SIP Trunk: Passthrough

      Destination Signaling Groups

      Office 365 Direct Routing SBA



      Figure : Create Call Route Entry


  5. Delete unused resources:

    1. From the left navigation pane, select Signaling Groups.

    2. Delete the SIP Signaling Group called Teams Direct Routing that has been created by the last Easy Config Wizard.

      Signaling Group Accuracy

      If you receive an error that a route entry is using this resource, you may have attempted to delete the wrong Signaling Group.


      Figure : Delete Signaling Group


    3. From the left panel, select Call Routing > Call Routing Table and delete the Call Routing Table From Microsoft Teams Direct Routing created by the most recent use of the Easy Configuration Wizard.

      SIP Signaling Group Error

      If you receive an error that the SIP_SG entry is using this resource, you may have attempted to delete the wrong Call Routing Table.


      Figure : Delete Call Route Table


      Migration from for Lync 2013 SBA/Skype for Business 2015 SBA

      Migrating from for Lync / Skype for Business SBA?

      After creating the new configuration, update the existing routing table to fork the call between the Signaling Group Direct Routing and Direct Routing SBA, instead of Skype for Business.


Sharing Trusted Certificate Authority Information

These steps are required only if the Direct Routing SBA does not share the SBC Public certificate.

The Trusted Certificate Authority information associated with the SBC and the Direct Routing SBA must be shared within the platform.

Export the SBC's Certificate Authority Information to the Direct Routing SBA:

  1. In the WebUI, click the Tasks tab.

  2. Under the SBC Easy Setup, select Certificates.

  3. From the Trusted CAs tab, select the certificate and click Export Trusted CA Certificate.

  4. Save the file on your PC. Repeat the step 3 and 4 for each CA certificate in the table. (These are the SBC CA Certificate used later per 336032102.)

Import the Direct Routing SBA's Certificate Authority Information to the SBC:

  1. Export the Root and Intermediate Certificate of the Certificate Authority (Public or Private) that as/will generate the Direct Routing SBA certificate.

  2. In the WebUI, click the Tasks tab.

  3. Under SBC Easy Setup, select Certificates.

  4. From the Trusted CAs tab, select Import Trusted CA Certificate.

  5. Select the right format (Copy and Paste or File Upload) then click OK. Repeat step 4 and 5 for each CA certificate.

Configure ASM for Direct Routing SBA

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Setup.

  3. Click the ASM Config tab and configure/verify the Network and IP settings of your ASM.

    1. From the Remote Desktop Enabled drop down list, select Yes (to enable Remote Desktop) or No (to disable Remote Desktop). Recommended setting is No).

    2. From the Windows Firewall Enabled drop down list, select Yes (to enable Windows Firewall) or No (to disable Windows Firewall). Recommended setting is Yes).

    3. From the Proxy Enabled drop down list, select Yes (enables use of the Proxy Server on the ASM) or No (disables Proxy Server).

    4. Configure/verify the Network and IP settings of your ASM.

  4. Click Apply.

    Figure : ASM Configuration


Generate CSR

These steps are required only if you need to c336032102

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Setup.

  3. Click the Generate CSR tab.

  4. Generate the CSR as shown below. To ensure creating a valid CSR for Direct Routing SBA usage, see Certificate requirements.

  5. Copy the CSR from the lower pane of the Generate CSR page and save it as a .txt file.

After the CSR is signed by the Certificate Authority, you receive the PKCS7 Certificate file.

Figure : Generate CSR

Manage Certificates

Import SBC CA in Direct Routing SBA

These steps are required only if Direct Routing SBA does not share the SBC Public certificate.

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Setup.

  3. Click the Manage Certificate tab.

  4. Click the Action drop-down list and select Import X.509 Signed Certificate.

  5. Paste the SBC CA certificate in the window and click OK.

Import Direct Routing SBA Certificate

Ensure you import the Root and Intermediate certificate before importing the SBA certificate. To import these certificates, follow the instructions below for Import X.509 Signed Certificate.

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Setup.

  3. Click the Manage Certificate tab.

  4. Click the Action drop-down list and select one of the following options:

    • Import X.509 Signed Certificate. This option is used if you generated a Certificate Request (CSR) and this is the initial deployment. Paste the certificate in the window and click OK.

    • Import PKCS12 Certificate and Key. This options imports a certificate you created. Enter the password, select the file (certificate) to import, and click OK.

  5. Proceed with the next step.

    Figure : Import Certificate

    image2020-9-28_10-25-19.png



Configure Office 365 Direct Routing SBA

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Setup.

  3. Click the Configure Office 365 Direct Routing SBA tab.

  4. Configure the information appropriately for your Direct Routing SBA:

    1. SBA FQDN. Must match the FQDN used to define this Direct Routing SBA in the Teams tenant item Teams Survivable Branch Appliance (New-CsTeamsSurvivableBranchAppliance).

    2. SBC FQDN. Must match theFQDN used to define the SBC that hosts this Direct Routing SBA in the Teams tenant item Online PSTN Gateway (New-CsOnlinePSTNGateway).

    3. Create Azure AD Application. Enables the option to create a new Azure AD Application credentials for this Direct Routing SBA.

      • If you already created an Azure AD Application credentials, select No and enter the credentials in Application ID and Application Secret.

      • If you did not previously create the Azure AD Application credentials (or if you are not sure what this means), select Yes and enter the credentials in Azure Administrator Account Name and Azure Administrator Account Password.

        Azure Administrator Account Considerations

        This Azure Administrator Account account needs Global Administrator, an Application Administrator, or a Cloud Application Administrator role.


    4. Enter a Teams Tenant ID. To locate this information, refer to: https://docs.microsoft.com/en-us/onedrive/find-your-office-365-tenant-id.

  5. Click Apply.

Configure Deployments with Additional SBCs

Additional SBC Context

This step is required only for networks with more than one SBC on a Branch Office.

  1. Enable Remote Desktop on the ASM. Refer to:  Enabling and Disabling Remote Desktop on the ASM.

  2. Connect the ASM using Remote Desktop Protocol.

  3. As an administrator, open the file C:\Windows\System32\drivers\etc\hosts

    Figure : Open Host File


  4. Add an entry for all the SBCs on the same Branch Office. The entry must contain the SBC Public FQDN and the Private IP Direct Routing SBA uses to reach this SBC.

    Figure : Edit Host File


  5. Save and close the file.

Test the Direct Routing SBA

Complete the following steps to confirm the configuration.

Import Direct Routing SBA Certificate Authority

  1. Navigate to Tasks > Office 365 Direct Routing SBA > Certificate.

  2. Ensure the Certificate Chain is reported as valid.

    • If the page reports Missing Root or Intermediate CA, return to the Setup / Manage Certificate tab, select Import X.509 Signed Certificate and import all the root and trusted certificate that generate the Certificate of the Direct Routing SBA. Once completed, return to the  Certificate tab and ensure the Certificate Chain is reported as valid.

      Figure : Verify Certificate



Confirm SBA Status

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Application Solution Module > Operational Status.

  3. Confirm the Office 365 Direct Routing SBA Service:

    • Service Status is reported as Running

    • Service Information is reported as ready

      Figure : Direct Routing SBA Service Status


Confirm SIP Option

The signaling groups configured for the Microsoft Teams Direct Routing SBA include counters for SIP request and response messages related to incoming and outgoing options. As the SBC 1000/2000 operates with Microsoft Teams Direct Routing SBA, the message counters show increasing numbers. Ensure the the message counts and investigate potential sources of related integration issues are as follows:

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, click Signaling Groups.

  3. From the signaling group configured for Microsoft Teams Direct Routing SBA, click Counters.

  4. Check for an increasing message count in Outgoing Options.

  5. Check for an increasing message count in Incoming 2xx. 

    1. If not, check the following: Ensure the Sip Server Entry for the Direct Routing SBA matches the cases of the Certificate CN or SAN used by Direct Routing SBA.

    2. If you just completed the deployment of SBA, a restart of the SBA service may be required before you see the 200 OK increasing message count.
  6. Check for an increasing message count in Incoming Options.

  7. Check the message count in Outgoing 2xx. If the number is increasing, changes you made during validation have resolved the integration issue(s).

    Figure : Signaling Group Counters


Confirm Teams Client Connection to SBA

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365™ Direct Routing SBA >Teams Client Connected.

  3. Confirm that your Teams client is reported.

    Figure : Confirm Teams Client Connection to SBA


Confirm Teams Client Can Run in Offline Mode

  1. Remove the Internet link between the Branch Office and the Microsoft Teams cloud.
  2. Open the Teams client. A banner is displayed, which indicates that the Teams client will ONLY use the SBA to make/receive calls when it is in offline mode.

    Figure : Confirm Teams Client Can Run in Offline Mode


Place Test Call

Complete the following steps to place a test call:

  1. In the WebUI, click the Diagnostics tab.

  2. In the left navigation pane, click Test a Call.  

    Figure : Test a Call Parameters in WebUI


  3. Configure the parameters for test calls as follows:

    Table : Values for Test Call Parameters


    Parameter

    Value

    Destination Number

    Type a telephone number assigned to a Teams user.

    Origination/Calling Number

    Type a telephone number assigned to a Local (SIP Trunk or PSTN) user.

    Call Routing Table

    Select the routing table that handles the calls from Local resources (From PSTN or From SIP Trunk).



  4. Click OK; the call should ring the Teams Client.

    Figure : Active Call Example


  5. If the test call does not ring the Teams client: 

    1. Check that the SBC IP routing is properly configured.

    2. Check whether you can place a call from Teams to the SBC. 

    3. If the call does not reach the SBC, then complete the following:

      1. Confirm that the firewall is properly configured to allow incoming SIP TLS messages.

      2. Confirm that the federated IP addresses are properly configured.

      3. If the call is Anonymous, refer to  Configuring SBC Edge for Select Microsoft Teams Direct Routing Related Migration Scenarios for more details.

      4. If the call from the SBC to Teams does not connect due to a SIP 488 "Not Acceptable Here" coming from Teams with the reason "IceCandidatesAbsent", disable Media Bypass on Teams or enable ICE Lite on the SBC. For details, refer to Configuring SBC Edge for Select Microsoft Teams Direct Routing Related Migration Scenarios.

Access Logs

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Diagnostics> Teams Direct Routing > SBA logs.

  3. From the Log Level drop down level, select the desired log level for the Direct Routing SBA.

    Figure : Set log lever for Direct Routing SBA


  4. Use the table on the same page to view or Download the Direct Routing SBA log files.

    Figure : Display Direct Routing SBA logs



Restart Services

  1. Login to the WebUI of the SBC Edge.

  2. Navigate to Tasks > Office 365 Direct Routing SBA > Start/stop Services.

  3. From the Service Action drop down list, select Stop Service, in Teams Server as the Service Name, and click OK.

  4. Wait for the action to complete.

  5. From the Service Action drop down list, select Start Service, in Service Name select Teams Server, and click OK.

  6. Wait for the action to succeed.

Figure : Start SBA service