[jitsi-dev] ICE Problems


#1

Hi,

for a long time Jitsi has worked like a charm, but now the following phenomenon occurs:

- calling from my jabber accounts on jabber.ccc.de and gmx.de fails with an ICE failure
- calling the same addresses from my account jit.si works fine

I know the issue with the nonstandard STUN server at all United Internet sites (such as gmx or web.de etc.) so I configure all Jitsi on such accounts installations in a way that the jitsi STUN server is taken (no automatic configuration / use Jitsi's STUN server). No avail

I have a new router here which I do not trust. It is a rather locked down provider's device (Alice / O2 to be precise) They used to have an option called "VoIP helper" or something which when enabled caused Jingle to fail. No idea about that. This one doesn't have this option (which might be set by default)

Whom should I send my logs to?

Thanks for help
Conrad


#2

Hi Conrad, hi All,

I have been traveling for some months and noticed that it was not possible to use
Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems, but Jitsi voice
gave ICE failures. On the few times that it worked, the JITSI audio was unusable.
Jitsi chat worked fine.

I have noticed that often voice communication over any server other than jit.si has
ICE failures.

Earl

···

On 09/4/2012 23:41, Conrad Beckert wrote:

Hi,

for a long time Jitsi has worked like a charm, but now the following phenomenon occurs:

- calling from my jabber accounts on jabber.ccc.de and gmx.de fails with an ICE failure
- calling the same addresses from my account jit.si works fine

I know the issue with the nonstandard STUN server at all United Internet sites (such as gmx or web.de etc.) so I configure all Jitsi on such accounts installations in a way that the jitsi STUN server is taken (no automatic configuration / use Jitsi's STUN server). No avail

I have a new router here which I do not trust. It is a rather locked down provider's device (Alice / O2 to be precise) They used to have an option called "VoIP helper" or something which when enabled caused Jingle to fail. No idea about that. This one doesn't have this option (which might be set by default)

Whom should I send my logs to?

Thanks for help
Conrad


#3

Hi Earl, Dear Developers

nice to hear from you...

I do not think that it is so bad that none of the Jabber accounts work. But at least here, it seems to be the case. Strange: I suspected that the calls from/to jit.si get routed through a jingle node server- but it doesn't look like this.

Something must be wrong with the ICE/STUN settings. I use Jitsi's STUN server.

Any ideas?
Thank you
Conrad

-------- Original-Nachricht --------

···

Datum: Wed, 05 Sep 2012 11:29:13 +0200
Von: Earl <Large.Files@gmx.net>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems

Hi Conrad, hi All,

I have been traveling for some months and noticed that it was not
possible to use
Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems,
but Jitsi voice
gave ICE failures. On the few times that it worked, the JITSI audio was
unusable.
Jitsi chat worked fine.

I have noticed that often voice communication over any server other than
jit.si has
ICE failures.

Earl

On 09/4/2012 23:41, Conrad Beckert wrote:
> Hi,
>
> for a long time Jitsi has worked like a charm, but now the following
phenomenon occurs:
>
> - calling from my jabber accounts on jabber.ccc.de and gmx.de fails with
an ICE failure
> - calling the same addresses from my account jit.si works fine
>
> I know the issue with the nonstandard STUN server at all United Internet
sites (such as gmx or web.de etc.) so I configure all Jitsi on such
accounts installations in a way that the jitsi STUN server is taken (no automatic
configuration / use Jitsi's STUN server). No avail
>
> I have a new router here which I do not trust. It is a rather locked
down provider's device (Alice / O2 to be precise) They used to have an option
called "VoIP helper" or something which when enabled caused Jingle to fail.
No idea about that. This one doesn't have this option (which might be set
by default)
>
> Whom should I send my logs to?
>
> Thanks for help
> Conrad
>
>


#4

I have to confirm these issues with ICE:
calls via jit.si account work smoothly, however any other XMPP account
tested fails for calls in both directions (I have tested GMX and
jabber.ccc.de).

kind regards, MS

···

On 9/6/12 12:40 AM, Conrad Beckert wrote:

Hi Earl, Dear Developers

nice to hear from you...

I do not think that it is so bad that none of the Jabber accounts work. But at least here, it seems to be the case. Strange: I suspected that the calls from/to jit.si get routed through a jingle node server- but it doesn't look like this.

Something must be wrong with the ICE/STUN settings. I use Jitsi's STUN server.

Any ideas?
Thank you
Conrad

-------- Original-Nachricht --------

Datum: Wed, 05 Sep 2012 11:29:13 +0200
Von: Earl <Large.Files@gmx.net>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems
Hi Conrad, hi All,

I have been traveling for some months and noticed that it was not
possible to use
Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems,
but Jitsi voice
gave ICE failures. On the few times that it worked, the JITSI audio was
unusable.
Jitsi chat worked fine.

I have noticed that often voice communication over any server other than
jit.si has
ICE failures.

Earl

On 09/4/2012 23:41, Conrad Beckert wrote:

Hi,

for a long time Jitsi has worked like a charm, but now the following

phenomenon occurs:

- calling from my jabber accounts on jabber.ccc.de and gmx.de fails with

an ICE failure

- calling the same addresses from my account jit.si works fine

I know the issue with the nonstandard STUN server at all United Internet

sites (such as gmx or web.de etc.) so I configure all Jitsi on such
accounts installations in a way that the jitsi STUN server is taken (no automatic
configuration / use Jitsi's STUN server). No avail

I have a new router here which I do not trust. It is a rather locked

down provider's device (Alice / O2 to be precise) They used to have an option
called "VoIP helper" or something which when enabled caused Jingle to fail.
No idea about that. This one doesn't have this option (which might be set
by default)

Whom should I send my logs to?

Thanks for help
Conrad


#5

Hi,

as I was at the other end of the line :slight_smile: I checked where the media packets go to / come from: stun.jit.si:

2:19:38.349783 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 58
22:19:38.361853 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 106
22:19:38.377114 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 112
22:19:38.386268 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 58
22:19:38.389718 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 101
22:19:38.404236 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 62
22:19:38.406176 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 77

Looks like, the call gets routed by a JingleNode when done via jit.si.That's why they go through.

The same router worked fine some weeks ago. I have the protocols saved here. Is there anyone in the list who wants to have a look on what's going on?

ICE is a quite central component of Jitsi and we suspect that there is some kind of regression with it. We've seen quite a few updates to the ICE lib in recent times. I have saved all the protocols of the tests - whom should I send them to? Emil?

Thank you for your help in advance

Conrad

-------- Original-Nachricht --------

···

Datum: Thu, 06 Sep 2012 22:50:41 +0200
Von: "Mr.Smith" <mr.smith476@googlemail.com>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems

I have to confirm these issues with ICE:
calls via jit.si account work smoothly, however any other XMPP account
tested fails for calls in both directions (I have tested GMX and
jabber.ccc.de).

kind regards, MS

On 9/6/12 12:40 AM, Conrad Beckert wrote:
> Hi Earl, Dear Developers
>
> nice to hear from you...
>
> I do not think that it is so bad that none of the Jabber accounts work.
But at least here, it seems to be the case. Strange: I suspected that the
calls from/to jit.si get routed through a jingle node server- but it doesn't
look like this.
>
> Something must be wrong with the ICE/STUN settings. I use Jitsi's STUN
server.
>
> Any ideas?
> Thank you
> Conrad
>
> -------- Original-Nachricht --------
>> Datum: Wed, 05 Sep 2012 11:29:13 +0200
>> Von: Earl <Large.Files@gmx.net>
>> An: dev@jitsi.java.net
>> CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
>> Betreff: [jitsi-dev] Re: ICE Problems
>> Hi Conrad, hi All,
>>
>> I have been traveling for some months and noticed that it was not
>> possible to use
>> Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems,
>> but Jitsi voice
>> gave ICE failures. On the few times that it worked, the JITSI audio
was
>> unusable.
>> Jitsi chat worked fine.
>>
>> I have noticed that often voice communication over any server other
than
>> jit.si has
>> ICE failures.
>>
>> Earl
>>
>> On 09/4/2012 23:41, Conrad Beckert wrote:
>>> Hi,
>>>
>>> for a long time Jitsi has worked like a charm, but now the following
>> phenomenon occurs:
>>> - calling from my jabber accounts on jabber.ccc.de and gmx.de fails
with
>> an ICE failure
>>> - calling the same addresses from my account jit.si works fine
>>>
>>> I know the issue with the nonstandard STUN server at all United
Internet
>> sites (such as gmx or web.de etc.) so I configure all Jitsi on such
>> accounts installations in a way that the jitsi STUN server is taken (no
automatic
>> configuration / use Jitsi's STUN server). No avail
>>> I have a new router here which I do not trust. It is a rather locked
>> down provider's device (Alice / O2 to be precise) They used to have an
option
>> called "VoIP helper" or something which when enabled caused Jingle to
fail.
>> No idea about that. This one doesn't have this option (which might be
set
>> by default)
>>> Whom should I send my logs to?
>>>
>>> Thanks for help
>>> Conrad
>>>
>>>


#6

Hello Conrad,

Using a JingleNode relay means that ICE has not found any direct connection available.
Thereby, when using an account which does not provide JingleNode relay, this one must be able to provide another relay method such as TURN. Jitsi is compliant with RCF5766 and tried to experimentally comply with Google TURN (with still a lot of problems).

Another point, when Jitsi is configured to use "Jitsi's STUN server", this does not provide any TURN mechanism. Thus, if you disable the "Auto discover STUN/TURN servers" option, you have to manually fill the "Additional STUN servers" list with a TURN-able server.

If you want to, I can have a quick look at your logs [0] (the logs of the remote peer might be helpful too).

Regards,
Vincent

[0] https://jitsi.org/index.php/Documentation/FAQ#logs

···

On 9/6/12 11:08 PM, Conrad Beckert wrote:

Hi,

as I was at the other end of the line :slight_smile: I checked where the media packets go to / come from: stun.jit.si:

2:19:38.349783 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 58
22:19:38.361853 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 106
22:19:38.377114 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 112
22:19:38.386268 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 58
22:19:38.389718 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP, length 101
22:19:38.404236 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 62
22:19:38.406176 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP, length 77

Looks like, the call gets routed by a JingleNode when done via jit.si.That's why they go through.

The same router worked fine some weeks ago. I have the protocols saved here. Is there anyone in the list who wants to have a look on what's going on?

ICE is a quite central component of Jitsi and we suspect that there is some kind of regression with it. We've seen quite a few updates to the ICE lib in recent times. I have saved all the protocols of the tests - whom should I send them to? Emil?

Thank you for your help in advance

Conrad

-------- Original-Nachricht --------

Datum: Thu, 06 Sep 2012 22:50:41 +0200
Von: "Mr.Smith" <mr.smith476@googlemail.com>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems

I have to confirm these issues with ICE:
calls via jit.si account work smoothly, however any other XMPP account
tested fails for calls in both directions (I have tested GMX and
jabber.ccc.de).

kind regards, MS

On 9/6/12 12:40 AM, Conrad Beckert wrote:

Hi Earl, Dear Developers

nice to hear from you...

I do not think that it is so bad that none of the Jabber accounts work.

But at least here, it seems to be the case. Strange: I suspected that the
calls from/to jit.si get routed through a jingle node server- but it doesn't
look like this.

Something must be wrong with the ICE/STUN settings. I use Jitsi's STUN

server.

Any ideas?
Thank you
Conrad

-------- Original-Nachricht --------

Datum: Wed, 05 Sep 2012 11:29:13 +0200
Von: Earl <Large.Files@gmx.net>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems
Hi Conrad, hi All,

I have been traveling for some months and noticed that it was not
possible to use
Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems,
but Jitsi voice
gave ICE failures. On the few times that it worked, the JITSI audio

was

unusable.
Jitsi chat worked fine.

I have noticed that often voice communication over any server other

than

jit.si has
ICE failures.

Earl

On 09/4/2012 23:41, Conrad Beckert wrote:

Hi,

for a long time Jitsi has worked like a charm, but now the following

phenomenon occurs:

- calling from my jabber accounts on jabber.ccc.de and gmx.de fails

with

an ICE failure

- calling the same addresses from my account jit.si works fine

I know the issue with the nonstandard STUN server at all United

Internet

sites (such as gmx or web.de etc.) so I configure all Jitsi on such
accounts installations in a way that the jitsi STUN server is taken (no

automatic

configuration / use Jitsi's STUN server). No avail

I have a new router here which I do not trust. It is a rather locked

down provider's device (Alice / O2 to be precise) They used to have an

option

called "VoIP helper" or something which when enabled caused Jingle to

fail.

No idea about that. This one doesn't have this option (which might be

set

by default)

Whom should I send my logs to?

Thanks for help
Conrad

--
Vincent Lucas, Ph.D. Jitsi developer
chenzo@jitsi.org http://jitsi.org


#7

Hello Alois, Conrad

Hello Vincent,
pls find attached the log files (0) from yesterday

[snip]

The logs contain 2 calls.

For the first one, ICE has discovered the following addresses:
- /fe80:0:0:0:e2f8....... (Your local IPv6 address)
- /192.168.66..... (One of your local IPv4 address)
- /172.16.132..... (One of your local IPv4 address)
- /10.0.0.... (One of your local IPv4 address)
- /93.82........ (Your public IPv4 address. It is a server reflexive address discovered by STUN)
- /130.79.91.169 (jit.si JingleNode relay address)

This call works and is connected via JingleNode relay. Thus, you need a relay to call the remote peer.

Whereas, the second call has the same address list but without the JingleNode relay address. And indeed, this call fails because (as for the first call) you can not achieve a direct communication.

Hope the logs are useful, especially that we had similar tests some
weeks ago (with the very same router settings - at least on my side) and
everything was working using the GMX accounts.

This may be due to the new router Conrad was talking about: if it filters the STUN request you sent to him (meaning that your router was already filtering these requests for a while).

To conclude, Jitsi can not do anything to solve this case: there is no error or bug, just a limited configuration of your Internet access. But you may remove this limitation by turning on UPnP on your/Conrad router (if available), or manually adding a TURN server or a JingleNode relay for the second account.

Regards,
Vincent

if you need wireshark-logs pls let me know

kind regards,
Alois

[snip]

···

On 9/7/12 10:37 AM, Alois Schweighofer wrote:

On 9/7/12 10:00 AM, Vincent Lucas wrote:

Hello Conrad,

Using a JingleNode relay means that ICE has not found any direct
connection available.
Thereby, when using an account which does not provide JingleNode
relay, this one must be able to provide another relay method such as
TURN. Jitsi is compliant with RCF5766 and tried to experimentally
comply with Google TURN (with still a lot of problems).

Another point, when Jitsi is configured to use "Jitsi's STUN server",
this does not provide any TURN mechanism. Thus, if you disable the
"Auto discover STUN/TURN servers" option, you have to manually fill
the "Additional STUN servers" list with a TURN-able server.

If you want to, I can have a quick look at your logs [0] (the logs of
the remote peer might be helpful too).

Regards,
Vincent

[0] https://jitsi.org/index.php/Documentation/FAQ#logs

On 9/6/12 11:08 PM, Conrad Beckert wrote:

Hi,

as I was at the other end of the line :slight_smile: I checked where the media
packets go to / come from: stun.jit.si:

2:19:38.349783 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP,
length 58
22:19:38.361853 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP,
length 106
22:19:38.377114 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP,
length 112
22:19:38.386268 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP,
length 58
22:19:38.389718 IP becconmobil.local.rfe > stun.jitsi.net.31266: UDP,
length 101
22:19:38.404236 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP,
length 62
22:19:38.406176 IP stun.jitsi.net.31266 > becconmobil.local.rfe: UDP,
length 77

Looks like, the call gets routed by a JingleNode when done via
jit.si.That's why they go through.

The same router worked fine some weeks ago. I have the protocols
saved here. Is there anyone in the list who wants to have a look on
what's going on?

ICE is a quite central component of Jitsi and we suspect that there
is some kind of regression with it. We've seen quite a few updates to
the ICE lib in recent times. I have saved all the protocols of the
tests - whom should I send them to? Emil?

Thank you for your help in advance

Conrad

-------- Original-Nachricht --------

Datum: Thu, 06 Sep 2012 22:50:41 +0200
Von: "Mr.Smith" <mr.smith476@googlemail.com>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems

I have to confirm these issues with ICE:
calls via jit.si account work smoothly, however any other XMPP account
tested fails for calls in both directions (I have tested GMX and
jabber.ccc.de).

kind regards, MS

On 9/6/12 12:40 AM, Conrad Beckert wrote:

Hi Earl, Dear Developers

nice to hear from you...

I do not think that it is so bad that none of the Jabber accounts
work.

But at least here, it seems to be the case. Strange: I suspected
that the
calls from/to jit.si get routed through a jingle node server- but it
doesn't
look like this.

Something must be wrong with the ICE/STUN settings. I use Jitsi's STUN

server.

Any ideas?
Thank you
Conrad

-------- Original-Nachricht --------

Datum: Wed, 05 Sep 2012 11:29:13 +0200
Von: Earl <Large.Files@gmx.net>
An: dev@jitsi.java.net
CC: Conrad Beckert <conrad_videokonferenz@gmx.de>
Betreff: [jitsi-dev] Re: ICE Problems
Hi Conrad, hi All,

I have been traveling for some months and noticed that it was not
possible to use
Jitsi. I was able to use Skype and FreePP ( IAX2 ) with no problems,
but Jitsi voice
gave ICE failures. On the few times that it worked, the JITSI audio

was

unusable.
Jitsi chat worked fine.

I have noticed that often voice communication over any server other

than

jit.si has
ICE failures.

Earl

On 09/4/2012 23:41, Conrad Beckert wrote:

Hi,

for a long time Jitsi has worked like a charm, but now the following

phenomenon occurs:

- calling from my jabber accounts on jabber.ccc.de and gmx.de fails

with

an ICE failure

- calling the same addresses from my account jit.si works fine

I know the issue with the nonstandard STUN server at all United

Internet

sites (such as gmx or web.de etc.) so I configure all Jitsi on such
accounts installations in a way that the jitsi STUN server is
taken (no

automatic

configuration / use Jitsi's STUN server). No avail

I have a new router here which I do not trust. It is a rather locked

down provider's device (Alice / O2 to be precise) They used to
have an

option

called "VoIP helper" or something which when enabled caused Jingle to

fail.

No idea about that. This one doesn't have this option (which might be

set

by default)

Whom should I send my logs to?

Thanks for help
Conrad

--
Vincent Lucas, Ph.D. Jitsi developer
chenzo@jitsi.org http://jitsi.org