At a glance
- List which of your devices joined the call's audio.
- Check speakers separately from a muted microphone.
- Remove an unnecessary second audio route and record the remaining symptom.
You joined a call on the computer and added your phone for another view. An echo remains even though the phone's microphone icon is crossed out. Before moving equipment around, find out whether that phone is still listening through an active speaker. Microphone state and audio participation are separate facts.
The useful first step is an inventory of your own devices. It gives you a specific route to change if it is unnecessary. Two devices connected to sound can be relevant, but their presence does not prove the sole cause of every echo.
1. Give each device an intended role
Write down the computer, phone, app or client, and the role you want each to perform. The computer may be the speaking and listening device while the phone supplies only a visual view. Alternatively, the phone may be intended to take over the call when you leave the desk.
Those intentions lead to different actions. Do not start by enabling both microphones while deciding which device should carry the conversation. Record whether a headset is selected and which device uses it. Having a headset on the desk does not establish the phone's speaker state.
Where the interface is unclear, keep the field unknown. “Phone audio participation not checked” is a useful next task. “Phone is silent because its microphone is muted” combines an observation with an assumption that needs to be separated.
2. Treat joined audio, microphone, and speaker as three fields
Zoom's echo guidance lists audio connected on both computer and phone, and nearby active devices, among possible causes. It also explains that muting a microphone can leave the speaker active.
For each device, note whether it joined audio, whether the microphone is active, and whether the selected output is playing the call. A microphone icon answers only part of this inventory. Look at the actual device choices and participation options documented for the client you are using.
This distinction avoids an unhelpful series of volume changes. Turning down several controls while leaving every route connected makes it harder to know what changed. If a secondary device has no intended sound role, identify its documented way to leave audio instead of relying on a single mute symbol.
3. Distinguish adding a device from transferring the call
Microsoft Teams guidance on a second device offers adding a device or transferring the call. When added, the second device's microphone is initially muted and can be enabled again. That specific behavior is not a promise that every speaker is disabled in every calling application.
If the phone is supposed to take over from the computer, examine the applicable transfer route. If it is only a secondary visual participant, examine the add-device route and its actual audio state. Record which you chose; “joined twice” does not explain whether the second connection should replace or accompany the first.
Use the instructions for your app and client. Teams behavior is not automatically Zoom behavior, and a remembered menu from another version may not describe your current choices. The client name is therefore part of the support record, not an incidental detail.
4. Change one unnecessary audio participation
When your second device has no sound role, use its documented leave-audio option while retaining the primary device's known microphone and output. The intended change is the secondary participation, not the phone's physical location or the material of its stand.
Write the change specifically: “phone left audio; computer and selected headset retained.” If you also switch microphones or outputs, note those as separate changes rather than attributing any evolution to the one route you originally intended to compare.
Observe the symptom during your authorized use of the call. This procedure does not ask you to record other people, contact participants for a test, or claim a test session happened. If you cannot establish the remaining symptom, record it as unknown. A carefully documented configuration is still useful even without a measured outcome.
5. Compare three hypothetical audio configurations
| Device / situation | Joined audio? | Microphone active? | Speaker active? | Intended role | One change | Remaining symptom |
|---|---|---|---|---|---|---|
| Phone in a Zoom call also open on computer | Yes in this example | No | Yes | Visual participation only | Leave phone audio through the documented option | To observe; no guaranteed cause assigned |
| Second device added in Teams | Check the actual client state | Initially muted under the documented add route | Not yet checked | Second view | Verify and remove unwanted secondary sound participation | Unknown until inventory is complete |
| Phone meant to take over a Teams call | Current route not yet recorded | To record | To record | Transfer from computer | Follow the applicable transfer route | Record resulting setup and any continuing echo |
The first case illustrates why a muted microphone can leave a speaker question. The second separates the documented initial mute from an output state still to inspect. The third starts with the desired handoff rather than assuming that another audio connection should remain active.
6. Carry a precise inventory into further support
If the echo remains after an unnecessary route is removed, retain the device list, client, selected microphone and output, and the change you made. Use the app's and device makers' official guidance for other possible causes. This narrow inventory is not a complete acoustic diagnosis.
The ClassicStand phone stand concerns the phone's position when product compatibility has been confirmed. Neither its name nor its catalog description establishes an echo-correction function or an acoustic performance of the wood.
Description
For a positioning comparison, consult the phone stand and charger guide. The work-from-home office guide addresses the surrounding setup. For audio support, provide the inventory rather than treating a furniture change as evidence about the call routes.
Frequently asked questions
Why might echo remain when the phone microphone is muted?
Zoom explains that the speaker may remain active. Check joined audio and the selected output separately from microphone state, then decide which device has the intended sound role.
Does Teams automatically turn off every second-device speaker?
The cited source describes an initially muted microphone when adding a second device. It does not establish a universal speaker-off guarantee. Inspect your actual client's output and audio participation.
Is there a fixed distance that prevents this problem?
No universal separation is specified here. This workflow identifies active routes and removes an unnecessary one where documented. It does not use a spacing measurement as a guarantee against all echo causes.
What if echo continues with only the intended route?
Keep the recorded setup and continuing symptom and move to official app or device support. Other causes may require different checks; the second-device inventory should remain part of that record.
