This guide covers the network and system requirements to successfully deploy RingQ as well as the deployment methods.
For organizations with dedicated telephony needs, Single Tenant deployment offers full control and isolated resources — ideal for enterprises or call centers. Multi-Tenant deployment is designed for service providers or organizations managing multiple clients or departments on shared infrastructure, enabling cost-efficient scalability and centralized management. Both models support reliable operations, with the choice depending on your need for isolation versus resource efficiency.
| Concurrent Call Limit | Extensions | CPU | RAM | Storage | Notes |
|---|---|---|---|---|---|
| Up to 12 CC | Up to 50 ext. | 2 vCPU | 4 GB | 60 GB SSD | Ideal for small offices |
| 24 CC to 72 CC | 51-300 ext. | 4 vCPU | 8 GB | 80 GB SSD | Medium enterprise load |
| 96 CC to 200 CC | 301-800 ext. | 8 vCPU | 16 GB | 100 GB SSD | Ensure network latency <20ms |
| 250 CC to 500 CC | 801-2000 ext. | 16-32 vCPU | 32-64 GB | 2000 GB SSD+ | Enable media handling, QoS, recording, and SBC where needed |
| Concurrent Call Limit | Extensions | 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+5 | 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. Single tenant limits are based on the maximum simultaneous calls the system can handle.
