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 Models & System Requirements
Introduction
This guide covers the network and system requirements to successfully deploy RingQ as well as the deployment methods.
Network Ports
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. |
| 9999 | Android Push Notification | Required for Android Push Notification Service |
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)
Deployment Models & System Requirements for RingQ
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.
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 |
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+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 maximum simultaneous calls the system can handle.