Call Quality

Call quality depends on network stability, microphone permission, audio device routing, app version, browser/mobile environment, and the path the call takes through WebRTC, mobile, SIP, forwarding, or carrier networks.

Before you begin

• Use a stable network before testing.
• Grant microphone permission.
• Know whether the problem happens on web, mobile, SIP/deskphone, or forwarded calls.

Where to find it

Start with the affected device and call path, then compare against another device or network.

Step-by-step

1. Check whether the issue affects one user, one inbox, or every call.
2. Switch from Wi-Fi to wired or cellular data, or from cellular to Wi-Fi.
3. Check microphone and speaker permissions in the browser or mobile OS.
4. Try another headset or audio output.
5. Restart the Waveline app or refresh the browser.
6. Place a short test call from another number and compare quality.

What happens next

• If only one device has trouble, the cause is likely local permission, hardware, or network quality.
• If every user has trouble on one inbox, review routing, forwarding, SIP, or provider status.
• If only forwarded calls are poor, test a direct Waveline app call for comparison.

Best practices

• Use a wired headset or reliable Bluetooth device for long calls.
• Avoid congested public Wi-Fi for customer calls.
• Keep browser and mobile apps updated.

Troubleshooting

• Robotic audio usually points to packet loss or unstable network.
• One-way audio usually points to microphone permission, device routing, or SIP/network rules.
• Delayed audio can come from Bluetooth, network latency, or forwarded paths.

Related pages

• Microphone permissions
• App connection issues
• Deskphones and IP phones
• Mobile call controls