Source note · One SBC serving several calling platforms
In the Teams carrier model, a derived trunk in a customer tenant takes all of its configuration from the carrier trunk. SIP OPTIONS are sent only to the carrier trunk FQDN, and its health status applies to every derived trunk.
Checked 2026-10-14
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- Direct Routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- Configure a Session Border Controller for multiple tenants — Microsoft · tier 2 current vendor documentation · Create a trunk and provision users > Provisioning logic and example
Cite this note
APA
WarmTransfer. (2026, October 14). One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-derived-trunk. WarmTransfer. https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-derived-trunk
BibTeX
@misc{warmtransfer-claim-multi-platform-sbc-design-teams-derived-trunk,
title = {One SBC serving several calling platforms: source note multi-platform-sbc-design-teams-derived-trunk},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/multi-platform-sbc-design-teams-derived-trunk},
note = {Source note multi-platform-sbc-design-teams-derived-trunk, checked 2026-10-14}
}