Microsoft gives as an example of trunk connection failure an SBC access control list that omits the IP addresses of some Microsoft Direct Routing datacenters.
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Direct Routing
- Subsystem
- SBC firewall
- 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', second paragraph
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-sbc-acl-missing-dc-ips. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-ms-sbc-acl-missing-dc-ips
BibTeX
@misc{warmtransfer-claim-sip-408-timeout-troubleshooting-ms-sbc-acl-missing-dc-ips,
title = {Troubleshooting SIP 408 Request Timeout and calls that get no response: source note sip-408-timeout-troubleshooting-ms-sbc-acl-missing-dc-ips},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-408-timeout-troubleshooting-ms-sbc-acl-missing-dc-ips},
note = {Source note sip-408-timeout-troubleshooting-ms-sbc-acl-missing-dc-ips, checked 2026-10-02}
}