Monitor Direct Routing

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/direct-routing-monitor-and-troubleshoot

Published

2026-09-10

Updated

unknown

Accessed

2026-09-21

HTTP status

200

License

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

Source notes citing this source

• Call Analytics only helps when calls reach the internal Direct Routing components and fail; for SBC pairing problems or rejected INVITEs such as a misconfigured trunk FQDN the administrator must read the SBC logs, to which Direct Routing sends a detailed description of the issue. in context
• When two or more SBCs in one route are considered healthy and equal, Direct Routing applies a Fisher-Yates shuffle to distribute the calls between them. in context
• Direct Routing treats an SBC as healthy if it sent SIP OPTIONS within the last three regular one-minute intervals, and an SBC that has not is demoted so that it is not tried first, though a demoted SBC is retried before the call fails. in context
• Call Analytics cannot diagnose Direct Routing SBC pairing problems or SIP INVITEs rejected before reaching Direct Routing internals (for example a misconfigured trunk FQDN); Microsoft directs admins to the SBC logs for those. in context
• Teams Direct Routing treats an SBC as healthy if it sent SIP OPTIONS within the last three minutes (three one-minute intervals); otherwise the SBC is demoted in the route but still retried before the call fails. in context
• An SBC that has not sent OPTIONS on schedule is demoted rather than removed: it is not tried first, but it is tried again before the call fails if the other SBCs in the route cannot deliver it. in context
• When two or more SBCs in a Direct Routing route are healthy and of equal priority, calls are spread across them with a Fisher-Yates shuffle. in context
• Direct Routing treats an SBC as healthy if it has sent SIP OPTIONS within the last three minutes, against an expected one-minute interval. in context
• Teams Call Analytics only helps when a call reaches Direct Routing's internal components; for SBC pairing problems or rejected INVITEs, Microsoft points to the SBC logs, where Direct Routing sends detailed error descriptions. in context
• An SBC that stops sending OPTIONS on the regular interval is demoted, meaning it is not tried first. If the other SBC in the route cannot deliver the call, the demoted SBC is tried again before the call fails. in context
• When two or more SBCs in one route are healthy and have equal priority, Direct Routing spreads calls between them with a Fisher-Yates shuffle. in context
• When a route contains several SBCs for a user, Direct Routing uses the OPTIONS information received from each SBC when choosing where to send the call. in context
• Teams Direct Routing monitors SBC health using the SIP OPTIONS messages the SBC sends, and the tenant administrator does not need to do anything to turn this monitoring on. in context
• Direct Routing treats an SBC as healthy if it sent OPTIONS at some point in the last three minutes, which is three times the regular one-minute interval. in context
• When two or more SBCs in a Direct Routing route are healthy and of equal priority, Direct Routing distributes calls between them with a Fisher-Yates shuffle; SBC health is judged from SIP OPTIONS received in the last three minutes. in context
• When two or more SBCs in one Direct Routing route are healthy and of equal priority, calls are spread across them with a Fisher-Yates shuffle. in context
• When routing a call, Direct Routing treats an SBC as healthy if it has sent OPTIONS within the last three minutes; otherwise the SBC is demoted, not removed, and is tried again before the call fails. in context
• Teams Call Analytics does not help with SBC pairing problems or rejected INVITEs such as a misconfigured trunk FQDN; for those Microsoft points to the SBC logs, where Direct Routing sends detailed error descriptions. in context
• Direct Routing treats an SBC as healthy if it sent SIP OPTIONS within the last three minutes, and an unhealthy SBC is demoted so it is tried after other SBCs in the route rather than first. in context
• Call Analytics does not help with SBC pairing problems or INVITEs rejected for reasons such as a misconfigured trunk FQDN; in those cases the SBC logs carry the detailed description that Direct Routing sends to the SBC. in context
• Call Analytics helps only when calls reach Direct Routing's internal components and then fail. For SBC pairing problems, or a SIP INVITE rejected because of a misconfigured trunk FQDN, Microsoft says to use the SBC logs, where Direct Routing sends detailed issue descriptions. in context
• Direct Routing treats an SBC as healthy for routing if it sent OPTIONS within the last three minutes, which is three one-minute intervals, before the call. Otherwise the SBC is demoted in the route. No tenant action is needed to enable this OPTIONS monitoring. in context
• A demoted SBC isn't tried first. Direct Routing tries the other SBCs in the route, then retries the demoted SBC before generating a failure. When two or more SBCs in a route are equally healthy and equal in priority, calls are spread across them with a Fisher-Yates shuffle. in context

Cite this source record

APA

WarmTransfer. (2026, September 10). Monitor Direct Routing. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-dr-monitor

BibTeX

@misc{warmtransfer-ms-learn-dr-monitor,
  title  = {Monitor Direct Routing},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-dr-monitor},
  note   = {Microsoft, accessed 2026-09-21}
}