Source note · SIP 503 and trunk out-of-service failures
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.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SBC health monitoring
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Monitor Direct Routing — Microsoft · tier 2 current vendor documentation · Section 'Monitoring availability of Session Border Controllers using Session Initiation Protocol (SIP) options messages', last paragraph
Cite this note
APA
WarmTransfer. (2026, September 25). SIP 503 and trunk out-of-service failures: source note sip-503-trunk-failures-dr-fisher-yates. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-503-trunk-failures-dr-fisher-yates
BibTeX
@misc{warmtransfer-claim-sip-503-trunk-failures-dr-fisher-yates,
title = {SIP 503 and trunk out-of-service failures: source note sip-503-trunk-failures-dr-fisher-yates},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-503-trunk-failures-dr-fisher-yates},
note = {Source note sip-503-trunk-failures-dr-fisher-yates, checked 2026-09-25}
}