Source note · UC observability and synthetic monitoring
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.
Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- Troubleshooting tools
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- Monitor Direct Routing — Microsoft · tier 2 current vendor documentation · Section 'Monitor Call Quality Analytics dashboard and SBC logs', final paragraph
Cite this note
APA
WarmTransfer. (2026, September 24). UC observability and synthetic monitoring: source note observability-uc-dr-call-analytics-blind-spot. WarmTransfer. https://warmtransfer.net/knowledge/claims/observability-uc-dr-call-analytics-blind-spot
BibTeX
@misc{warmtransfer-claim-observability-uc-dr-call-analytics-blind-spot,
title = {UC observability and synthetic monitoring: source note observability-uc-dr-call-analytics-blind-spot},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/observability-uc-dr-call-analytics-blind-spot},
note = {Source note observability-uc-dr-call-analytics-blind-spot, checked 2026-09-24}
}