.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=878008bf159fcc4964d0c0d508b6e400)
Check browser permissions
Hoop uses WebRTC for in-browser calling, which requires microphone access from your browser.Verify microphone permission
When you first make or receive a call in Hoop, your browser should prompt you to allow microphone access. If you previously denied this permission, you need to re-enable it manually.
Update permissions in Chrome
Click the lock icon (or tune icon) in the address bar next to the Hoop URL. Find Microphone and set it to Allow. Reload the page.
No audio on calls
If you or the other party cannot hear anything during a call:One-way audio (you can hear them but they cannot hear you)
One-way audio (you can hear them but they cannot hear you)
Your microphone is likely muted or not selected. Check the call controls in Hoop for the mute button. Also verify that the correct microphone is selected under Settings > Phone System > Audio Devices. Test your microphone in your operating system’s sound settings to confirm it is working outside of Hoop.
One-way audio (they can hear you but you cannot hear them)
One-way audio (they can hear you but you cannot hear them)
Check your speaker or headphone output. Make sure the volume is not muted on your device. In Hoop, go to Settings > Phone System > Audio Devices and verify the correct output device is selected. Try switching between speakers and headphones.
No audio in either direction
No audio in either direction
This is typically a network issue. WebRTC requires specific ports and protocols to be open. If you are on a corporate network, ask your IT team to allow UDP traffic on ports 10000-60000 and ensure STUN/TURN servers are not blocked. Try switching to a different network to test.
Audio works on first call but drops on subsequent calls
Audio works on first call but drops on subsequent calls
Refresh the browser tab between calls. Some browsers release the audio stream when a call ends but do not properly reacquire it for the next call. If this happens frequently, enable the Persistent Audio Connection option under Settings > Phone System if available.
Echo and feedback
Echo during calls is usually caused by audio looping between your speaker and microphone.| Cause | Solution |
|---|---|
| Using laptop speakers and built-in microphone | Switch to a headset or earbuds. This physically separates the speaker from the microphone and eliminates feedback loops. |
| Speaker volume too high | Lower your speaker volume. When audio is loud enough to be picked up by the microphone, it creates echo for the other party. |
| Multiple browser tabs with Hoop open | Close duplicate Hoop tabs. Having multiple tabs open can cause audio to be captured and played back in a loop. |
| External speakers near the microphone | Move your external speakers away from your microphone, or use a headset instead. |
Mobile app audio
If you are experiencing audio issues on the HoopAI mobile app:- Check app permissions — Go to your phone’s settings and ensure the Hoop app has microphone permission enabled
- Disable Bluetooth conflicts — If you have multiple Bluetooth devices paired, your phone may route audio to the wrong device. Disconnect unused Bluetooth devices
- Check Do Not Disturb — DND mode on your phone can suppress call audio and notifications. Disable it or add Hoop to your DND exceptions
- Update the app — Ensure you are running the latest version of the Hoop mobile app from the App Store or Google Play
- Restart the app — Force-close the app and reopen it. This resets the audio session and clears temporary glitches
Network and firewall requirements
WebRTC audio requires the following network configuration:| Requirement | Details |
|---|---|
| Protocol | UDP preferred, TCP as fallback |
| Ports | 10000-60000 (UDP) for media traffic |
| STUN/TURN | Access to STUN/TURN servers for NAT traversal |
| Bandwidth | Minimum 100 kbps up and down per call |
| VPN | Some VPNs block or degrade WebRTC traffic — test with VPN disconnected |
If you are behind a strict corporate firewall that blocks UDP traffic, Hoop will attempt to fall back to TCP. However, TCP may introduce latency and reduced audio quality. Work with your IT team to allowlist the required ports for the best experience.
Quick diagnostic steps
Test your microphone
Use your operating system’s sound settings or an online microphone test to confirm your mic is working outside of Hoop.
Check device selection in Hoop
Go to Settings > Phone System > Audio Devices and verify the correct input and output devices are selected.
Try an incognito window
Open Hoop in a private/incognito window to rule out extension interference. Grant microphone permission when prompted.