Open omazin opened 3 years ago
Is this a delay in the actual audio, a delay in the initial setup, or something else? Do the calls go p2p, through a turn server, or through jitsi-videobridge (you can see this if you hover over the local thumbnail and select "show more")?
@bgrozev the delay is in the actual audio. Calls should go either through p2p or a turn server, attaching the screen below
This call goes through the bridge (you would see "p2p" otherwise). Of course there shouldn't be a delay, but I don't know why it occurs.
@bgrozev thank you for the response, I can also notice a little delay in p2p opening two browser tabs
Can the delay be a result of a bad ping or VPN?
@bgrozev thank you for the response, I can also notice a little delay in p2p opening two browser tabs
These clients are connected locally, so the network can't be the issue. Perhaps the machine client machine is overloaded or has an issue with the mic/speakers?
@bgrozev ok I see two potential sources of delays on the client machine:
We ask our clients to close all browser tabs but the one with a jitsi call or restart their computers in some cases. Also click on the local thumbnail and check connection indicators. If it says "Connection: Good" for both participants of the one-on-one call then there're no problems with the network, is that correct? Is there anything else we can do?
We’re experiencing 5-20 seconds delays in some of our one-on-one audio-only calls. We have a custom jitsi server running on docker containers. Any ideas would be greatly appreciated. Perhaps having a custom stun/turn server would fix the issue. Did anyone solve delay issues having their own stun server? Below are docker-compose & web config.js files: