# Enforcing a single combined concurrency limit per tenant (not separate in/out)?

**URL:** https://forums.vitalpbx.org/t/enforcing-a-single-combined-concurrency-limit-per-tenant-not-separate-in-out/6081
**Category:** VitalPBX
**Created:** [February 22, 2026, 8:20pm UTC](https://forums.vitalpbx.org/t/enforcing-a-single-combined-concurrency-limit-per-tenant-not-separate-in-out/6081 "2026-02-22T20:20:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Connexium](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/connexium/32/4453_2.png) [@Connexium](https://forums.vitalpbx.org/u/Connexium)
#### Post date: [February 22, 2026, 8:20pm UTC](https://forums.vitalpbx.org/t/enforcing-a-single-combined-concurrency-limit-per-tenant-not-separate-in-out/6081/1 "2026-02-22T20:20:04Z")

</div>

Hi all,  
In VitalPBX we can set **max inbound calls** and **max outbound calls** per tenant, but our billing and packages are based on a **single combined concurrent call limit** (inbound + outbound together).

Example: customer pays for **8 concurrent trunk calls total**.  
If I configure **8 inbound + 8 outbound** , they can effectively use **16** (8 inbound _and_ 8 outbound at once), which isn’t what we want.

Requirements:

- Limit should apply to **trunk usage only** (calls that hit our SIP trunk providers).
- It should **not** restrict internal calls.
- Ideally it should work per tenant (multi-tenant), and ideally we can enforce it so customers can’t exceed their plan during peak.

Questions:

1. Is there a native way to enforce a **single combined concurrent trunk call limit** per tenant?
2. If not, what’s the recommended approach (tenant trunk grouping, dialplan rules, call limits, custom module, etc.)?
3. How do you handle this cleanly when inbound and outbound trunks are separate providers?

Thanks in advance!

---

<div class="post-metadata">

### Author: ![system](https://forums.vitalpbx.org/uploads/default/original/1X/672b458a1d454755270c2c16adc5316b641c3c6a.png) [@system](https://forums.vitalpbx.org/u/system)
#### Post date: [March 24, 2026, 8:20pm UTC](https://forums.vitalpbx.org/t/enforcing-a-single-combined-concurrency-limit-per-tenant-not-separate-in-out/6081/2 "2026-03-24T20:20:07Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.