search

kiwiirc / plugin-conference

Audio / Video conference calling
Apache License 2.0
19 stars 9 forks source link

Sound issue with mobile devices #73

Open TimeRider07 opened 3 years ago

TimeRider07 commented 3 years ago

There seems be 2 problems of currently with kiwiirc plugin conference for me.

  1. If someone joins from mobile device to conference, you can't hear his/her voice. And the rest of the conference users has to rejoin to be able to hear the person joining from mobile.

  2. When someone is using mobile device to join the conference; a. Using Jitsi public server seems to have echo issues in the mobile devices. b. Using own Jitsi instance is causing the sound to shatter also in the mobile devices.

Using headphone makes it little better but you can still hear the slight noise. However, using Jitsi directly on their web or app does not seem to have problem with mobile devices at all.

I would be grateful if someone knows about it or could fix it.

My Jitsi version; ii jitsi-meet 2.0.5870-1 all WebRTC JavaScript video conferences ii jitsi-meet-prosody 1.0.4985-1 all Prosody configuration for Jitsi Meet ii jitsi-meet-tokens 1.0.4985-1 all Prosody token authentication plugin for Jitsi Meet ii jitsi-meet-web 1.0.4985-1 all WebRTC JavaScript video conferences ii jitsi-meet-web-config 1.0.4985-1 all Configuration for web serving of Jitsi Meet ii jitsi-videobridge2 2.1-492-g5edaf7dd-1 all WebRTC compatible Selective Forwarding Unit (SFU)

Shillos commented 3 years ago

This is a jitsi problem, not a kiwiirc problem. I think the best solution is to ask in https://community.jitsi.org/ they might know why this is happening. That's my first suggestion, ask there if they have that problem. If this is local or hosted on your own server, you might want to upgrade that. The latest releases show a different number from those above https://github.com/jitsi/jitsi-videobridge/releases

TimeRider07 commented 2 years ago

Hello Shillos, thanks for the reply. Yeah, it does look like a jitsi problem. I upgraded jitsi to the latest but the problem still exists. I have created a topic on their community, hoping to get it resolved.