A call that connects without audio can have three origins: your device (microphone, headset, audio output), the network between the PBX and your correspondent, or the configuration of the carrier connection. Start with the case that matches what you're observing.
| What you're observing | Most likely cause | Go to |
|---|---|---|
| You can't hear your correspondent, but they can hear you | Wrong audio output, volume, headset not recognized | You can't hear |
| Your correspondent can't hear you | Microphone muted, denied by the browser, or unplugged | You can't be heard |
| Total silence in both directions, including across multiple calls and multiple devices | Network path or address announced to the correspondent | Silence in both directions |
| The problem only occurs with one carrier, or only with outgoing or incoming calls | Carrier connection (trunk) | Silence in both directions |
| The problem only occurs in meetings | Permissions or devices selected on entry | No audio in a meeting |
A simple test already sorts out many cases: make an internal call to a colleague, then an external call. If the internal call is fine and the external call is silent, the device is probably not at fault.
You can't hear your correspondent
- During the call, use Choose audio output and select the headset or speakers you're actually using. The list offered comes from your browser: a headset plugged in after the page was opened may not appear until you reload.
- Open Settings › Audio and headset and check the Audio output (speaking / listening). Don't confuse it with the Ringtone output, which is set separately under Ringtone and notifications: hearing the ringtone doesn't prove the conversation will come out through the same output.
- Run the Audio test: click Start, speak for three seconds, then listen to the playback. If the test plays back on the default output with a warning, the output you selected cannot be used: choose another one.
- Check the headset volume, the system volume, and the browser tab volume.
Details: Choosing the microphone and outputs and Testing audio.
Your correspondent can't hear you
- Check the call's microphone control: a Muted microphone leaves the call active but removes your voice. Re-enable it.
- Verify that the browser has permission to use the microphone for this site. A denied permission is fixed in the browser settings, not in the phone.
- In Settings › Audio and headset, choose the correct Microphone (or Default device), then run the Audio test.
- If you unplugged a headset during a call, the application attempts to switch to another microphone and indicates this in a banner: read it in full. If it reports a failure, or if no replacement works, the call no longer transmits your voice: plug a microphone back in, then select it again. Close hides the banner without fixing the audio.
- If the audio test is fine but only this call is silent, hang up and call back before going further.
Silence in both directions, or with a single carrier
This section is for the person who manages telephony. If a call "connects but remains without audio" while the devices themselves are fine, this is almost always a network path issue: the address that the PBX communicates to the correspondent for receiving audio is not the one reachable by them.
1. Find the call and read its legs. In the call log, open the call in question and expand Call data. For each leg (the part of the call connecting a participant or carrier to the PBX), note the Network, the Local address, and the Announced address. Compare them to the expected network: a carrier on a private link should use its intended output; the client's device may use a different interface. Missing information may indicate data that wasn't collected: it doesn't prove the use of another output.
2. Check the carrier connection. Open the trunk record and check the Network section, then the Applied address status. As long as Pending network application is displayed, have the platform administrator apply the plan before any testing. If the PBX is behind a firewall that translates addresses (NAT), check the announced public address. Detail: Outgoing network and local address.
3. Check the network plan. When the machine is behind a router, devices on its local network receive its local address for audio. A device located on a different internal network, for example a voice VLAN, that reaches the machine via its public address requires the router to also translate the source address on this return path, or direct access to the machine's address on its network. Without one or the other, the call connects but remains without audio. Detail: Checking the network plan result.
4. Observe in real time. Active calls displays, for each active call, the codec (the format used to transport voice) and the carrier connection used. If the problem is reproducible, a SIP trace limited to a number, extension, or trunk, of short duration, helps understand what each side announced.
5. Conclude with a test. After each correction, test an incoming call and an outgoing call, with audio in both directions, before considering the problem resolved.
No audio in a meeting
When entering a meeting, allow microphone access in the browser, then choose your Microphone and your Speaker and check the mic level on the preview. Avoid checking Join muted if you want to be heard right away. Detail: Joining a meeting as a guest.
What to note down for support
Before contacting support, note down:
- the time and identifier of the call in question;
- whether the problem occurs in one direction or both, and whether it affects one device or several;
- whether internal calls are affected;
- the carrier or trunk, and the call direction (incoming or outgoing);
- the Network, Local address, and Announced address values for each leg;
- the result of the Audio test on the affected device.
This information avoids back-and-forth exchanges and makes it possible to know immediately whether to look at the device, the network, or the carrier connection.
