Health dashboard for Direct Routing

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/direct-routing-health-dashboard

Published

2026-04-29

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• Microsoft says it uses SIP OPTIONS together with TLS handshake monitoring to check SBC health at the application level. A trunk that answers a network ping can still fail if its certificate has expired or its SIP stack is not working. in context
• The Direct Routing health dashboard says the SBC sends OPTIONS every minute by default, that this can vary by SBC vendor, and that Direct Routing warns when OPTIONS are not being sent or are not configured. in context
• The dashboard's SIP options status can be Active (OPTIONS arriving on a regular interval), 'Warning, no SIP options' (the SBC is configured to send them but none have ever been seen), or 'Warning, SIP Messages aren't configured' (OPTIONS trunk monitoring is off). in context
• The dashboard's per-SBC detail view has a 'SIP options last checked' field showing when OPTIONS were last received from that SBC. in context
• The Direct Routing health dashboard, under Voice > Direct Routing in the Teams admin center, shows per-SBC TLS connectivity status with a warning when the certificate expires within 30 days, and a SIP options status of Active, Warning no SIP options, or Warning SIP messages aren't configured. in context
• Microsoft treats average call duration on the dashboard as a quality indicator. It recommends setting a company baseline, because a large drop, for example to about 15 seconds, can mean users are hanging up over quality or reliability problems. in context
• The dashboard's TLS connectivity status checks the SBC certificate's expiration date and warns when it expires within 30 days. in context
• The Direct Routing health dashboard is under Voice > Direct Routing in the Teams admin center. It shows total SBCs, voice routes, and SBCs with issues. Issues include low network effectiveness, certificate expiration, inactivity, no SIP OPTIONS, and capacity constraints. in context
• The dashboard's concurrent calls capacity compares the calls Direct Routing sent or received through an SBC with the limit set by -MaxConcurrentSessions on New-CsOnlinePSTNGateway or Set-CsOnlinePSTNGateway. If the SBC also serves other PBXs, the figure isn't the SBC's true concurrency. in context
• The dashboard calculates network effectiveness ratio as 100 x (Answered calls + User Busy + Ring no Answer + Terminal Reject Seizures) / Total Calls. User rejections and calls sent to voicemail count as successful deliveries. in context
• The dashboard shows how many calls each metric is based on. Microsoft cautions that when fewer than 100 calls are analysed, a low network effectiveness ratio may still be normal. in context
• The per-SBC view shows jitter, packet loss and latency (round-trip time), measured from the Direct Routing interface to the SBC, filterable by days and call direction. For recommended values Microsoft points to the Customer Edge to Microsoft Edge targets in its Teams network preparation guidance. in context
• An SBC added with PowerShell (New-CsOnlinePSTNGateway) that never connected appears on the health dashboard as unhealthy with issues. in context
• By default the SBC sends OPTIONS every minute, though this can vary by SBC vendor. in context
• The dashboard shows three SIP OPTIONS status values. 'Active' means OPTIONS arrive regularly. 'Warning, no SIP options' means the SBC exists but the service has never seen OPTIONS from it. 'Warning, SIP Messages aren't configured' means OPTIONS trunk monitoring isn't turned on. in context
• In the per-SBC view, SBC status 'Inactive' means the SBC has no recent calls or health checks. 'Active' means it is healthy and taking traffic. The page gives no numeric threshold for 'recent'. in context

Cite this source record

APA

WarmTransfer. (2026, April 29). Health dashboard for Direct Routing. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-dr-health-dashboard

BibTeX

@misc{warmtransfer-ms-learn-dr-health-dashboard,
  title  = {Health dashboard for Direct Routing},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-dr-health-dashboard},
  note   = {Microsoft, accessed 2026-09-24}
}