[modules/version/ComponentsVersions.js] <>: Got xmpp version: Prosody(0.9.10,Linux)
Logger.js:125 [modules/version/ComponentsVersions.js] <>: Got focus version: JiCoFo(18.104.22.168-444,Linux)
[modules/version/ComponentsVersions.js] <>: Got videobridge version: JVB(0.1.1093,Linux)
Voice Call(startAudioOnly=true), I found every 765 seconds(12mins+45seconds), participant encounter connection break one time, during the `re-connection period , the participant cannot hear each other
2020-02-26-11:34:25 [modules/connectivity/ParticipantConnectionStatus.js] Detector RTCEvents.ENDPOINT_CONN_STATUS_CHANGED(1582688065577): 8c2a2895: false
2020-02-26-11:34:25 [modules/connectivity/ParticipantConnectionStatus.js] Figure out conn status for 8c2a2895, is video muted: true is active(jvb): false video track frozen: false p2p mode: false is in last N: false currentStatus => newStatus: active => interrupted
2020-02-26-11:34:25 [modules/connectivity/ParticipantConnectionStatus.js] Emit endpoint conn status(1582688065585) 8c2a2895: interrupted
2020-02-26-11:34:29 [modules/RTC/BridgeChannel.js] Endpoint connection status changed: 8c2a2895 active ? true
2020-02-26-11:34:29 [modules/connectivity/ParticipantConnectionStatus.js] Detector RTCEvents.ENDPOINT_CONN_STATUS_CHANGED(1582688069578): 8c2a2895: true
2020-02-26-11:34:29 [modules/connectivity/ParticipantConnectionStatus.js] Figure out conn status for 8c2a2895, is video muted: true is active(jvb): true video track frozen: false p2p mode: false is in last N: false currentStatus => newStatus: interrupted => active
2020-02-26-11:34:29 [modules/connectivity/ParticipantConnectionStatus.js] Emit endpoint conn status(1582688069584) 8c2a2895: active
Interrupted means the client stopped receiving media from jvb, it maybe network problem … Also you are using very old jvb version so you better update to newer version …
Dear @Havid_Zheng, were you able to figure out this problem?
Dear @damencho, we are having this same problem and can’t find the solution. The people having this problem can either be behind turn or in a very good network connection (connected directly to the bridge via udp).
So far, the only thing we have found is that at the same time this error happens, this shows in the video bridge:
INFO: timeout for pair: XX.X.XX.XXX:32106/udp/srflx -> XX.XXX.XXX.XXX:60056/udp/prflx (stream-2e1a0008.RTP), failing.
We’ve seen also that when this happens, only some of the users lost the video.
For what is worth, we saw the same happening in jitsi. This is the conference we were at:
Here are some of the logs for the id 2a3e6033
For this user something funny happened: he was inside the premises and was connected to our network using a wireless router. Then he walk outside, his wireless changed to a different router (same network) and is when we stopped watching him. Later he walk back in again, was reconnected to a different router (again, same network) once again and then we begun seeing him again.
His ID did not change in any of these occasions.
When his wireless changed and he went back, this is what we saw in the logs:
Hopefully this helps!
Hello @acruz! Thanks for the detailed issue description. We suffer from the same issue(jitsi/jvb:stable-5142-4), did you find any possible solution?
We were able to fix the problem, but don’t remember exactly what we did.
However, we now have jvb in nodes with public ips. Once we did that most of our problems went away.
This specific error though seems to also happen in meet.jit.si. Not sure if it has a solution.
Welcome to the community!!