PBX TroubleshootingMade Easy with RingQ
Dropped calls, one-way audio, failed registrations, misrouted queues — most PBX issues trace back to a blocked port, a bad dial plan branch, or a network-level fault. Finding which one usually means digging through logs with no clear starting point.
Every RingQ admin panel ships with five built-in diagnostic tools for exactly this. Hover over a card below to see what each one does and when to reach for it.
The RingQ Troubleshooting Toolkit
Ports
Live, categorized status for every port RingQ relies on. Run an Internal or External scan, single-port or Scan All, and export the results as a report.
Call Debug
One switch to isolate a problem call. Debug Mode clears the current call log and starts a fresh one, so you capture exactly what happened the moment you reproduce it.
Capture
A raw packet capture on the server's network interfaces. Start it, reproduce the issue, stop it, and hand the .pcap to support for a byte-level look at SIP/RTP traffic.
Audit Logs
Every configuration change on the account — who made it, what feature, the result, and the source IP — searchable by user, feature, and date range.
Call Flow
Traces the live path a call takes through your dial plan — IVR branches, queues, time conditions, failover — so you see exactly where it went instead of guessing.
Still Stuck?
For step-by-step walkthroughs and screenshots of every tool above, read the full guide — or reach out and a real person will help you dig in.