On this page
Hearing the meeting does not prove that the meeting can hear you. Speakers and microphones are separate routes, and the application may select an unexpected input when a headset, webcam, dock, or monitor is connected. Trace the input path before reinstalling the app or resetting every device.
Start outside an important call if possible. Use the application's supported preview or test function with your own voice, in a private setting. Do not record other people without the appropriate permission or use a public meeting as an uncontrolled audio experiment.
Identify the available microphones
List the physical inputs connected to the device: built-in laptop microphone, headset microphone, webcam microphone, USB audio interface, or another accessory. A single headset can appear with more than one audio-related entry, depending on the platform and connection.
Look for hardware mute switches or buttons and check the manufacturer's instructions. A visible software unmute control cannot override every physical mute state. Likewise, a headset being paired does not establish that its microphone is the selected input.
Name the intended microphone before changing settings. The goal is to make the call use that input, not merely to make any meter move.
Check the operating system's input observation
Use the operating system's supported sound settings to inspect the selected input and any available level indicator. Speak normally and observe whether the intended device responds. Keep output volume at a comfortable level and avoid feedback-producing arrangements.
If the operating system does not detect the microphone, investigate its connection, power, permissions, and manufacturer guidance before focusing on the meeting app. Try a known supported connection when available, changing one factor at a time.
If the operating system detects the input correctly, keep that evidence. It narrows the next investigation to the application route or its access rather than proving the entire call is fixed.
Inspect the meeting application's selection
Open the application's current audio settings and read the microphone name. Do not assume “default” refers to the same device after a dock or headset change. Select the intended input explicitly where supported and use the preview or test function.
Check the speaker selection separately. A correct microphone with an unexpected output can make troubleshooting confusing: others may hear you while you cannot hear their response. Microsoft Teams, for example, exposes separate audio-device controls in its documented settings.
Availability and labels differ by application version, account, and platform. Follow the current instructions for the client you are using rather than expecting every web and desktop edition to show the same controls.
Check browser access for web meetings
A browser meeting needs permission to use the microphone. Review the permission for the actual meeting site and the operating system's access settings for the browser. Grant access only to a service you intend to use and have verified.
MDN documents that browser media capture has permission and secure-context requirements. If the browser cannot obtain the input, the site's error may describe a permissions or device issue rather than a broken microphone.
Avoid granting microphone access to unrelated sites as a troubleshooting shortcut. If you change a permission, retest the intended site and record the change so you can review it later.
Compare the symptom with the route
| Observation | Next area to inspect |
|---|---|
| No input response in system settings | Physical connection, device state, system access |
| System input works but app meter does not | App selection and permissions |
| App meter moves but others hear silence | Meeting mute state and application-specific support |
| Voice comes from far away | An unintended room or laptop microphone may be selected |
| Failure begins after connecting a dock | Device selection and the new connection path |
| Only the browser edition fails | Site permission and browser-specific behavior |
These observations suggest the next comparison. They do not prove a single cause, and several issues can occur together.
Isolate accessories without losing the evidence
If the problem began after a new accessory, disconnect or switch it through the supported process and compare the original setup. Save work before restarting applications. Avoid removing all Bluetooth pairings or uninstalling several drivers at once.
The Bluetooth guide distinguishes pairing, connection, and actual function. A device can satisfy the first two while the meeting still uses another microphone.
Keep a short change log: input selected, connection used, permission state, and test result. This helps identify whether the improvement came from the intended change or from an unrelated restart.
Evaluate sound quality after basic routing works
Once the correct input is confirmed, consider placement, background noise, and the application's supported processing options. Test one adjustment at a time using ordinary speech. A setting that removes background sound may affect some voices or audio uses differently.
Do not keep increasing gain to solve a microphone positioned too far away without checking the device's intended placement. Avoid unverified audio utilities that request broad system access merely to perform a basic input check.
If the call also freezes or drops, investigate connectivity separately. The internet speed comparison guide explains why a large download number alone does not establish that a live call's path is reliable.
Verify the setup after the next connection change
Repeat a brief supported check after reconnecting the dock, switching headphones, or moving between browser and desktop clients. Confirm that the input remains the intended one and that mute controls behave as expected.
If support is needed, provide the exact device names, application version, connection path, and where the signal stopped appearing. A clear route description is more useful than saying the microphone works “sometimes.” The successful outcome is the intended microphone reaching the intended call, with permissions and settings you can explain.
Sources and further reading
Primary and contextual sources used to verify definitions or give readers a relevant next resource.
- Microsoft: Manage meeting audio Meeting applications provide input and output selection and supported ways to check audio.
- MDN: MediaDevices getUserMedia Browser microphone access depends on permission and the relevant security and device conditions.