[jitsi-dev] Jitsi Videobridge has a lot of org.ice4j.ice.ConnectivityCheckClient.processTimeout

Archive
#1

Is it ok to have ice4j connectivity processTimeout?

For example:

org.ice4j.ice.ConnectivityCheckClient.processTimeout() timeout for pair:
<external ip>:10000/udp/host -> <internal ip>:65211/udp/host (stream.RTP),
failing.

org.ice4j.ice.ConnectivityCheckClient.processTimeout() timeout for pair:
<external ip>:10003/udp/host -> <user ip>:51412/udp/host (stream.RTP),
failing.

Service still works ok, but I'm thinking if I have something bad on
configuration. I thought it's because my hosting ddos-protection, that
strips udp packets, and moved on other one, but I still see these in logs.

#2

We should probably make Jitsi Meet stop sending local candidates to the
bridge. They would at best be redundant and most of the time would just
fail so ...

--sent from my mobile

···

On 15 Oct 2014 10:17 PM, "Lyubomir Marinov" <lyubomir.marinov@jitsi.org> wrote:

2014-10-15 22:36 GMT+03:00 Michael Zalmoxisus <zalmoxisus@gmail.com>:
> Is it ok to have ice4j connectivity processTimeout?

Yes. The goal of ICE/ice4j is to establish the connectivity between
(multiple) local and remote addresses through thorough and complete
testing.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

#3

I was thinking the same. Pretty easy by introducing a session config setting that is checked in https://github.com/jitsi/jitsi-meet/blob/master/libs/strophe/strophe.jingle.session.js#L194

···

Am 15.10.2014 22:23, schrieb Emil Ivov:

We should probably make Jitsi Meet stop sending local candidates to the
bridge. They would at best be redundant and most of the time would just
fail so ...

#4

Yes. The goal of ICE/ice4j is to establish the connectivity between
(multiple) local and remote addresses through thorough and complete
testing.

···

2014-10-15 22:36 GMT+03:00 Michael Zalmoxisus <zalmoxisus@gmail.com>:

Is it ok to have ice4j connectivity processTimeout?

#5

It is normal to see some of these, but not too many (I don't think more than one per pair is normal). I think there is some kind of problem in videobridge (possibly fixed in the latest version), as I'm observing many of these (thousands) logged for one and the same pair.

Boris

···

On 15/10/14 22:36, Michael Zalmoxisus wrote:

Is it ok to have ice4j connectivity processTimeout?

For example:

org.ice4j.ice.ConnectivityCheckClient.processTimeout() timeout for pair:
<external ip>:10000/udp/host -> <internal
>:65211/udp/host (stream.RTP), failing.

org.ice4j.ice.ConnectivityCheckClient.processTimeout() timeout for pair:
<external ip>:10003/udp/host -> <user ip>:51412/udp/host (stream.RTP),
failing.

Service still works ok, but I'm thinking if I have something bad on
configuration. I thought it's because my hosting ddos-protection, that
strips udp packets, and moved on other one, but I still see these in logs.