Deployment Methods – System Requirements

Introduction

---

Single Tenant deployment provides full control, dedicated resources, and consistent performance—ideal for enterprises and call centers. Multi Tenant deployment is suited for service providers or businesses managing multiple clients or departments. Multi-tenant offers cost-effective scalability and centralized management. Choose your deployment method based on your need for control versus costs.

Single-Tenant

---

Concurrent Call Limit	Simultaneous Calls (SC	CPU	RAM	Storage	Notes
25 Calls	Up to 50 SC	2 vCPU	4 GB	60 GB SSD	Ideal for small offices
150 Calls	51-300 SC	4 vCPU	8 GB	80 GB SSD	Medium enterprise load
400 Calls	301-800 SC	8 vCPU	16 GB	100 GB SSD	Ensure network latency <20ms
1000 Calls	801-2000 SC	16-32 vCPU	32-64 GB	2000 GB SSD+	Enable media handling, QoS, recording, and SBC where needed

Concurrent Call Calculation: For single-tenant deployments, limits are based on maximum simultaneous calls the system can handle.

Multi-Tenant

---

Concurrent Call Limit	Capacity	CPU	RAM	Storage	Notes
50 Extensions	Up to 50 Extensions	4 vCPU	4 GB	60 GB SSD	Light load tenants
75 Extensions	51-75 Extensions	8 vCPU	8 GB	80 GB SSD+	For peak hours, enable auto-scaling if cloud-based
1500 Extensions	75-1500 Extensions	16+ vCPU (Cluster)	16 GB	120+ GB SSD+	Use load balancing and HA configuration

Concurrent Call Calculation: For multi-tenant environments, assume 10-15% of total extensions will be active simultaneously during peak hours.

Network and System Requirements

---

 

Component	Minimum Spec	Concurrent Call Impact
Bandwidth	100 Mbps up/down (1Gbps preferred)	80-100 Kbps per concurrent call (G.711 codec)
OS	51-75 Extensions	Debian 11/12
Firewall	FortiGate / UFW with VoIP rules	Configure SIP/RTP port ranges for call capacity

Bandwidth Planning: Calculate total bandwidth as (Concurrent Calls × 100 Kbps) + 20% overhead. For 100 concurrent calls, allocate a minimum of 12 Mbps dedicated bandwidth.