Saturday, November 23, 2019

Ignite 2019 - VCE20 - Updates for Direct Routing

Presented by: Nikolay Muravlyannikov

Session summary:
Direct Routing allows Microsoft 365 customers to use their telecom provider and phone numbers in Teams. In this session you will learn about the latest updates such as the new SIP Tester, troubleshooting with the latest Usage Reporting, Dynamic Emergency Calling (e911), new SBC vendors going through certification, choosing your media server by region, and more. Attendees who are new to Direct Routing are encouraged to review the video at

My notes:

Direct Routing for Teams
  • SIP Tester
    A PowerShell tool to validate the call flow end-to-end after pairing the Session Border Controller. Two bots are configured TeamsIn and TeamsOut and is used to make a call. Download the tool and documentation here:
    PowerShell script to test Direct Routing Session Border Controller connections
  • Health Dashboard and Call Details Records
    A view in the Teams Admin center which helps you to monitor and troubleshoot reliability issues in interconnection between an SBC and the Microsoft service. The information shown in the Health Dashboard is:
    • Network Effectiveness Ratio
      Microsoft guarantees 99.9% of availability of Direct Routing service. If a call reached Direct Routing, the call will be accepted from or delivered to an SBC. To notify about issues with SBC Microsoft provides a NER metric to the customers via the Health Dashboard.
    • Average Call Duration.
      On average a PSTN call lasts 4 to 5 minutes, values below 4-5 mins can indicate issues.
    • TLS Connectivity Status.
      Shows the status of TLS connections between the Direct Routing and the SBC. Health Dashboard also analyses the certificate expiration date and warns if certificate expires within 30 days so administrators can renew the certificate before the service disrupted.
    • SIP Options status.
      By default, an SBC sends SIP Options messages every minute. This configuration can vary for different SBC vendors. This field will show the status of these messages. Direct Routing warns if SIP options are not received or not configured.
    • Concurrent Calls Capacity.
      When an SBC is paired to Direct Routing, you can specify the limit of concurrent calls that SBC can handle. The parameter calculates how many calls were sent and received by Direct Routing using specific SBC and compare with the limit set. Note that is this SBC also handles calls to different PBXs this number will not show the actual concurrent calls over the SBC.
    • Network Parameters.
      Packet Loss, Jitter, Latency
  • Call Details Records
    In the usage report PSTN usage / Direct Routing all calls made to or from any client in the tenant will be listed. This data can be downloaded as an excel file, and analytics of this data is coming to the portal in the future.
  • E911 with Direct Routing overview
    You can pair your SBC and route emergency calls and send location information to a Public Safety Answer Point in the US.

Updates on partnership and more features

What’s New for Calling in Microsoft Teams (Ignite 2019 Edition)

Direct Routing allows the routing of calls to 3rd party systems such as mobile network, this also known as "Dual Forking". Occasionally this would generate a "false positive" missed call indication in Teams when the call was picked up at the other fork. Teams can now suppress this unwanted missed call message which provides a better experience. In order for this to work the SBC must be configured to send a Cancel on the other Fork as follows: REASON: SIP; cause=200;text"Call completed elsewhere" See the article Manage call notifications for more information.

Some great new SBC partners being added!

No comments:

Post a Comment