Source note · SIP trunk capacity and concurrent call planning
The parameter reference describes MaxConcurrentSessions only as an alerting threshold and says nothing about calls being rejected above it, so it should not be treated as an enforced cap, even though the cmdlet summary calls it 'the limit of maximum concurrent sessions'.
inferred · Checked 2026-09-24
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- SBC configuration
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- New-CsOnlinePSTNGateway (MicrosoftTeams) — Microsoft Learn · tier 2 current vendor documentation · Description section versus Parameters '-MaxConcurrentSessions'
Cite this note
APA
WarmTransfer. (2026, September 24). SIP trunk capacity and concurrent call planning: source note sip-trunk-capacity-planning-ms-maxsessions-not-enforced. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-trunk-capacity-planning-ms-maxsessions-not-enforced
BibTeX
@misc{warmtransfer-claim-sip-trunk-capacity-planning-ms-maxsessions-not-enforced,
title = {SIP trunk capacity and concurrent call planning: source note sip-trunk-capacity-planning-ms-maxsessions-not-enforced},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-trunk-capacity-planning-ms-maxsessions-not-enforced},
note = {Source note sip-trunk-capacity-planning-ms-maxsessions-not-enforced, checked 2026-09-24}
}