Admin
Users & Call Controls
- Creating Extensions for Users
- Editing and Managing Extensions
- Creating Teams & Assigning Extensions
- Configuring Agent Status & BLF
- Managing Extension Schedules
- Managing User Roles
- Managing Call Controls
- Setting up Shared Parking
- Voicemails
- The BLF Function
- Configuring the Speed Dial
- Configuring the Busy Lamp Field (BLF)
Deployment Methods & System Requirements
Installation Guides
Deployment Methods – System Requirements
Introduction
This guide provides everything you need to know before deploying RingQ, covering key considerations such as single-tenant vs. multi-tenant setups, the network ports required for smooth communication, and the system requirements to ensure reliable performance. Understanding these fundamentals will help you choose the right deployment model, configure your environment properly, and avoid common pitfalls during installation and operation.
RingQ Network Ports Reference
(UDP, TCP, RTP, WSS, SIP, Media, and Push Services)
UDP Port | Use | Notes |
---|---|---|
3478 | STUN/TURN | NAT traversal (main port) |
3479 | STUN/TURN | Backup/alternative to 3478 |
5060 | SIP signaling | Standard SIP (call setup) |
5061 | SIP over TLS | Secure SIP (encrypted) |
5070 | Alt. SIP signaling | Used if 5060/5061 blocked |
5080 | Alt. SIP signaling | Another backup SIP port |
TCP Port | Use | Notes |
---|---|---|
5060 | SIP signaling | Standard SIP over TCP (call setup/control). |
5061 | SIP over TLS | Secure SIP (encrypted signaling over TCP). |
5066 | SIP / alternative transport | Often used for SIP over WebSocket (WS/WSS) in some systems. |
5080 | Alt. SIP signaling | Backup/alternative SIP port over TCP. |
TCP : 20, 21, 22, 80, 443, 3389, 8443 [HTTPS RINGQ BACKEND]
UDP: 53, 67, 68, 123
RTP: 16384–32767; 5004–5005; 5060–5067
WSS: 9443;7443
SIP: 5060[TCP]; 5061[UDP]
MEDIA: 9000-10999
Apple iOS PUSH: 5223 [Outbound TCP]
Audio and Video: 48000-65535 (outbound, UDP)
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