If a Direct Routing trunk cannot be connected (refused connection, TLS timeout or other network-level issue), Microsoft retries the same trunk from a different Microsoft datacenter, possibly in another region.
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- outbound routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Trunk failover on outbound calls - Microsoft Teams — Microsoft · tier 2 current vendor documentation · Section 'Failover on network errors'
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-ms-network-failover-other-dc. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-ms-network-failover-other-dc
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-ms-network-failover-other-dc,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-ms-network-failover-other-dc},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-ms-network-failover-other-dc},
note = {Source note sip-408-timeout-troubleshooting-ms-network-failover-other-dc, checked 2026-10-02}
}