Not very far in the past I posted a blog arrangement on Direct Routing, which I exceedingly urge you to look at if your association will go this course. To add on to this, Microsoft has as of late discharged a Health Dashboard for Microsoft Teams Direct Routing which will enable you to screen your association between your SBC and the Direct Routing interface. In this article we’ll separate the abilities of the Health Dashboard and show how valuable this new element can be for checking and investigating your Direct Routing condition. Click here to know about office setup

Wellbeing Dashboard for Direct Routing

With this most recent update to the Microsoft Teams administrator gateway you would now be able to screen data about your:

SBC

Communication Service

System parameters between the SBC and the Direct Routing interface

With this new all encompassing perspective to Direct Routing observing you can rapidly distinguish issues, for example, dropped calls and discover the main driver (for example lapsed testaments or system issues). Microsoft has moved toward this observing in 2 unique ways:

Taking a gander at generally speaking soundness of the associated SBC’s

Diving further into increasingly nitty gritty data about the associated SBC’s

Generally speaking Health of associated SBC’s

To give you a case of what you can hope to see when in the Teams administrator focus, you see int he screen shot underneath that the observing checks explicit angles like:

SBC

SBC FQDN

System adequacy

The deliberate capacity of the system to convey a call in respect to calls sent versus calls conveyed

Avoids call dismissals by the far-end client (this is considered a fruitful conveyance)

Recipe: NER (Network Effectiveness Ratio) = Answered calls + User occupied with +Ring no answer + Terminal reject seizures x 100

Normal call length

Call length can frequently help screen the nature of the calls

Shorter span normally shows quality issues

Calls under <15 sec normally mean something in the call turned out badly and the client was compelled to end the call

TLS availability status

Demonstrates the status of the TLS association between the SBC and the Direct Routing Interface.

Checks for authentication lapse on the SBC

Gives cautioning when authentication is 30 days from lapsing

Taste choice status

Shows if there is an issue with SIP choice stream. Likewise gives a point by point portrayal of the mistakes

Qualities for SIP alternatives status messages are as per the following:

Dynamic – Means SBC is dynamic and the Direct Routing interface sees the alternatives being conveyed on a normal interim

Cautioning, no SIP choices – This implies the SBC is discoverable in nature and is designed to send SIP choices, yet the Direct Routing administration isn’t accepting SIP alternatives returning from the SBC

Cautioning – SIP Messages aren’t designed – This implies the storage compartment observing for the SIP choices isn’t empowered.

Microsoft Calling System uses SIP choices + TLS handshake observing to recognize the soundness of the SBC at an application level

On the off chance that the storage compartment can be achieved when pinging it, however the SBC endorsement has lapsed or SIP stack doesn’t work appropriately, at that point Microsoft suggests empowering sending SIP alternatives.

Simultaneous call limit

Figures what number of calls were sent/gotten by Direct Routing

Utilize the New-CsOnlinePSTNGateway/Set-CsOnlinePSTNGateway order alongside the – MaxConcurrentSessions parameter

This nitty gritty SBC view demonstrates the accompanying:

TLS Connectivity status – Same measurement as “Generally speaking Health” page

TLS Connectivity last status – Shows the last time when the SBC made a TLS association with the Direct Routing administration

Taste choices status – same measurement as “Generally Health” page

Taste alternatives last checked – Shows the last time when SIP choices were gotten

SBC status – Current status of that specific SBC

Simultaneous call – Shows every simultaneous call being taken care of on that specific SBC

You can channel on a multi day, multi day, or multi day premise

Gives measurements to inbound, outbound, and all streams

System parameters – Shows all system parameters estimated from the Direct Routing interface to the SBC.

The accompanying measurements are estimated:

Jitter – Measures the variety in system engendering defer time between 2 endpoints that utilization RTCP in miliseconds (ms)

Bundle Loss – Measures parcel landing disappointment between 2 endpoints

Dormancy/RTT – Length of time it takes for a sign to be sent + the time it takes for an affirmation to be gotten. Comprises of engendering times between 2 points of a sign

System Effectiveness proportion (NER) – Same parameter that shows up on the “General Health” page

Gives you the extra capacity to channel information by time arrangement or call course

For a full breakdown of this new expansion to the Teams administrator focus, you can checkout the official documentation here.

Leave a comment

Your email address will not be published. Required fields are marked *