[jitsi-users] LastN issue on newer jvb versions


#1

Hello,

I'm having some issues with the lastN feature. I currently have two
jitsi stacks installed, let's call the "new" one and the "old" one;

Using Meet at the new one with lastN active I have several call quality
issues, making it unusable.

Using firefox (50) it adds a big de-synchronization between audio and
video, of several seconds (like 5 seconds).

On google chrome (55) beside the sync issue there's a major video
quality loss and frequently the other endpoints receive no video at all
from the new active endpoint.

In these cases where's there's no video is common to see the message
"XXXX is having connection issues". But the one who is supposedly with
issues still receive media normally.
Following the logs as I test I found that there's a cascade of the
following error when someone is having connection issues:

JVB 2016-12-29 11:47:10.875 SEVERE: [845922] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to handle an outgoing packet: java.lang.NullPointerException

In parallel to this "no video" issue. On both chrome and firefox I can
frequently see the following logs:

JVB 2016-12-29 11:49:47.732 INFO: [845923] org.jitsi.impl.neomedia.MediaStreamStatsImpl.log() Stream: b74ebb15ed391216, RTT computation may be wrong (-1): now 1483041384608, lsr 3907552804, dlsr 5994

And

JVB 2016-12-29 11:55:20.766 INFO: [848610] org.jitsi.impl.neomedia.rtp.translator.RTCPFeedbackMessageSender.log() Sending a FIR to ssrc=2786389800 remainingRetries=3
JVB 2016-12-29 11:55:20.766 WARNING: [848610] org.jitsi.impl.neomedia.rtp.translator.RTCPFeedbackMessageSender.log() Not sending an FIR because the stream RTP manager is null.

I don't really know what they really mean, but the look like mean to me.

(ps.: I have the same issues regardless of the n>0 value)

On the "new" stack versions are:
jicofo 1.0-319-1
jitsi-meet 1.0.1595-1
jitsi-videobridge 869-1

And the "old" stack versions are:
jicofo 1.0-192-1
jitsi-meet 1.0.777-1
jitsi-videobridge 612-1

Both stacks are running on Ubuntu 14.04 machines.

Thanks in advance.
Happy new year for everybody!

Best regards,
Luciano Rezende


#2

Hi Luciano,

Hello,

I'm having some issues with the lastN feature. I currently have two
jitsi stacks installed, let's call the "new" one and the "old" one;

Using Meet at the new one with lastN active I have several call quality
issues, making it unusable.

Using firefox (50) it adds a big de-synchronization between audio and
video, of several seconds (like 5 seconds).

On google chrome (55) beside the sync issue there's a major video
quality loss and frequently the other endpoints receive no video at all
from the new active endpoint.

I don't think we've seen any such issues.

In these cases where's there's no video is common to see the message
"XXXX is having connection issues". But the one who is supposedly with
issues still receive media normally.
Following the logs as I test I found that there's a cascade of the
following error when someone is having connection issues:

JVB 2016-12-29 11:47:10.875 SEVERE: [845922] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to handle an outgoing packet: java.lang.NullPointerException

This definitely looks like a problem. Can you please include more context from the logs?

In parallel to this "no video" issue. On both chrome and firefox I can
frequently see the following logs:

JVB 2016-12-29 11:49:47.732 INFO: [845923] org.jitsi.impl.neomedia.MediaStreamStatsImpl.log() Stream: b74ebb15ed391216, RTT computation may be wrong (-1): now 1483041384608, lsr 3907552804, dlsr 5994

This should be harmless.

And

JVB 2016-12-29 11:55:20.766 INFO: [848610] org.jitsi.impl.neomedia.rtp.translator.RTCPFeedbackMessageSender.log() Sending a FIR to ssrc=2786389800 remainingRetries=3

This is just normal operation.

JVB 2016-12-29 11:55:20.766 WARNING: [848610] org.jitsi.impl.neomedia.rtp.translator.RTCPFeedbackMessageSender.log() Not sending an FIR because the stream RTP manager is null.

I don't know what causes this, but we also see it, and it isn't known to cause problems.

Regards,
Boris

ยทยทยท

On 02/01/2017 12:06, Luciano Augusto Rezende wrote: