Purpose
This document provides a structured troubleshooting procedure to identify and resolve Wi-Fi channel conflicts and RF interference in Pronto Networks deployments.
RF interference is primarily a Layer-1 (Radio Frequency) issue that directly impacts:
Throughput
Roaming performance
Latency
Application stability
Frequent Disconnections
Scope
This procedure applies to environments where:
Multiple Pronto Access Points operate under centralized cloud management
Integrated Router + AP architecture is deployed
Retail, hospitality, or enterprise indoor networks exist
LTE-enabled Pronto routers operate near Wi-Fi radios
Typical deployment scenarios include:
Multi-AP indoor coverage designs
High client density environments
Cloud-managed Pronto networks
Symptoms of Channel Conflict
Technicians should correlate user-reported issues with technical RF indicators.
Common User Symptoms
High latency
Frequent Wi-Fi disconnections
Clients not roaming properly
Good signal strength but poor performance
Corresponding Technical Indicators
Symptom | Technical Indicator |
High latency | Internal ping spikes (e.g., 20 ms → 150+ ms) |
Frequent disconnections | Retry rate above 15% |
Clients not roaming | Sticky client behavior |
Good signal but poor performance | Channel utilization above 60% |
These indicators suggest airtime contention or interference rather than IP or routing issues.
Understanding the Problem
🔹 Co-Channel Interference (CCI)
Occurs when multiple Pronto APs operate on the same frequency channel within overlapping coverage areas.
Effects:
APs must share airtime
Devices wait before transmitting
Throughput decreases
Latency increases
Because Wi-Fi is a shared medium, devices coordinate access to the channel, reducing overall efficiency.
Common Root Causes in Pronto Deployments
Channel conflicts typically result from radio configuration issues or environmental factors, including:
Manual channel locking in Pronto radio profile
All APs configured on the same 5 GHz channel (e.g., 36 or 149)
Excessive channel width (e.g., 80 MHz in dense environments)
2.4 GHz radios enabled unnecessarily on all APs
Transmit power set to High across the site
External interference (neighbouring Wi-Fi, microwaves, Bluetooth devices)
Pronto router placed too close to AP antennas, causing RF noise
Step-by-Step Troubleshooting Procedure
Step 1 — Verify Channel Allocation
Review AP radio configuration.
Check for:
Review the current radio profile for both band 2.4 and 5 GHz
Check for any static channel selection (Exp: 6 for 2.4GHz & Channel 36 for 5 GHz), if selected try to change it to auto or select channel with less conjunction
Check for manual power allocation, Adjust the power based on required power to overlap the signal between AP with appropriate power not too low or High
If not required turn off 2.4 GHz
Associate steering is not enabled
Step 2 — Review Channel Width
Recommended settings:
Environment | Recommended Channel Width |
High-density retail | 20 MHz |
Medium office | 20–40 MHz |
Low-density sites | 40 MHz |
⚠ Avoid 80 MHz channels in malls, hotels, or dense deployments.
Step 3 — Validate Transmit Power
If transmit power is set to High on all APs:
Coverage overlap increases
Roaming performance degrades
Recommended approach:
Reduce power to Medium or Low
Maintain approximately -65 dBm signal at cell edge
Configure 5 GHz slightly stronger than 2.4 GHz
Step 4 — Perform Wi-Fi Scan
Use Pronto AP diagnostic tools to:
Detect neighbouring Wi-Fi networks
Identify non-Wi-Fi interference
Observe channel shifts
Step 5 — Review Auto Optimization vs Manual Settings
If Pronto automatic channel optimization is enabled:
Ensure:
No channels are manually locked
Channel width is not fixed globally
Static radio profiles are not cloned across all APs
Manual overrides may disable intelligent RF optimization.
Corrective Actions
2.4 GHz Best Practices
Set channel width to 20 MHz
Disable 2.4 GHz on unnecessary APs
These steps reduce overlap in the limited 2.4 GHz spectrum.
5 GHz Best Practices
Use 20 MHz channels in dense deployments
Distribute APs across channel ranges (e.g., 36–48 and 149–165)
Avoid assigning the same channel across an entire floor
Proper channel distribution minimizes co-channel interference.
Validation Checklist After Fix
Confirm RF stability by verifying:
Retry rate below 8%
Smooth client roaming
No adjacent channel overlap
Improved throughput
Escalation Data Collection (Pronto Deployments)
If issues persist, collect the following before escalation:
Pronto router model and firmware version
AP model and firmware version
Channel utilization screenshots
Site floor plan
Current radio profile configuration
Preventive Best Practices
Perform RF survey before deployment
Avoid cloning identical radio profiles to all APs
Implement staged channel plan changes
Avoid 80 MHz channels in dense sites
Maintain physical separation between Pronto router and AP antennas