Sound issues on a peer to peer call

[Marion]

I use Jami to speak to my brother, both of us in the UK. I have an echo ie I can hear my own voice after I have spoken. Why is this?

[hkk]

This could be jami’s problem, are you close enough to your brother?

[Rubus_chiliadenus]

@hkk

are you close enough to your brother?

I don’t think network latency and jitter can affect echo cancelling.

@Marion

I have an echo ie I can hear my own voice after I have spoken.

Sounds like default configuration of echo cancelling don’t work. There is a preference key named echoCancel in dring.yml, you can set it to audioProcessor (only use the chosen audio processor’s echo canceller)
On Windows, dring.yml is under %AppData%/Local/jami/
On GNU/Linux, dring.yml is under ~/.config/jami/

[ovari]

Are both participants using Jami for Desktop?

Two possible causes and solutions.

1. The participant you are talking to on Jami has their speaker pointed at, or behind, their microphone. Ensure that the participant’s microphone does not pick up the sound from their speakers.

2. The participant you are talking to on Jami has their microphone sensitivity set too high. Continually talk to the participant you are speaking with while they set their microphone sensitivity to 10% and increase until there is an echo for you. When you hear an echo, ask the participant you are talking with to reduce their microphone sensitivity by a few percent. A microphone sensitivity of Volume: 20%, as shown in the following image, should be more than enough.