Browser Calling: Microphone and No-Audio Checks
Troubleshoot a browser call in order: supported interface, secure page, microphone permission, audio devices and network. Avoid confusing audio with delivery.
By PhoneBorn Team3 min read
Quick answer: first establish whether the call is actually connecting. Then check the browser's microphone permission, operating-system privacy settings and selected audio devices. A connected call with no audio is a different problem from a number that cannot receive calls.
Start with the supported calling interface
Open the calling controls supplied by your provider for the active number. Do not assume every number product includes a web dialer, SIP account or a particular softphone integration. In PhoneBorn, inspect the current dashboard and product details rather than copying server settings from a different company's guide.
Note the symptom: no dial control, immediate rejection, ringing without answer, connected with no sound, or a dropped call. This description helps support choose the right investigation. A microphone setting cannot repair an unassigned number or an unsupported destination.
Check the page and site permission
Browser access to microphone devices normally requires a secure context and the user's permission. MDN documents these requirements for getUserMedia. Make sure you are on the correct HTTPS site before allowing microphone access.
If permission was previously denied, inspect the browser's site settings. Re-enable access only for the site you trust, then refresh the page if required. A prompt that never appears may reflect a remembered browser decision or an operating-system privacy setting rather than a problem with the phone number.
Inspect the physical audio path
| Symptom | Useful check |
|---|---|
| Nobody hears you | Selected microphone, mute switch and OS access |
| You cannot hear them | Output device and speaker volume |
| Echo | Headset use and speaker feedback |
| Audio changes mid-call | Bluetooth reconnection or device switching |
| Another app uses the headset | Close conflicting applications and reselect the device |
Test your microphone using an appropriate local recording or device-setting tool before blaming a remote call. Keep the test private and do not upload sensitive conversation recordings to unrelated services.
Isolate network problems carefully
If devices and permissions look correct, compare a trusted alternate connection where practical. Corporate networks, VPNs or restrictive firewalls can behave differently for real-time media. Do not disable security controls broadly or expose inbound ports on the assumption that it will fix a browser call.
Record whether the problem affects one browser, one device, one network or every attempt. Avoid many repeated paid calls while diagnosing. Check the provider's support guidance and use free local audio checks first.
Send a useful support report
Include the time and timezone, browser and OS versions, number or order reference, call state and the direction of missing audio. Share only the details support needs. Never send account passwords, API keys, verification codes or private conversation content as routine diagnostic material.
Does microphone access prove incoming SMS works?
No. Browser media access and message delivery are different systems. Use the SMS troubleshooting guide for message problems.
Should I install a SIP app instead?
Only if your service explicitly supports it and provides the required settings. Do not assume PhoneBorn uses another provider's SIP configuration.
Reference: MDN: getUserMedia requirements and errors.