Source note · Troubleshooting Teams Direct Routing
If a Direct Routing datacenter is busy, it can send the SBC a 503 with Retry-After (one-second interval) in response to an INVITE. The SBC must then terminate that connection and try the next available Microsoft datacenter.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- sip-signaling
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Teams Phone System Direct Routing: SIP protocol — Microsoft · tier 2 current vendor documentation · Retry-After
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-503-retry-after. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-503-retry-after
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-503-retry-after,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-503-retry-after},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-503-retry-after},
note = {Source note teams-direct-routing-troubleshooting-503-retry-after, checked 2026-09-25}
}