[jitsi-users] Call failed - incompatible parameters. Error: hostname can't be null


#1

I have been using Jitsi for years but when I tried to establish a video call
yesterday it would always fail with the error message "incompatible
parameters. Error: hostname can't be null". I was running the latest
stable version at that point and tried upgrading both clients to the 2.9
5534 build and get the same error. The only thing that really changed prior
to this was upgrading Openfire, which is now at version 4.0.4. Any ideas
would be appreciated.

Both clients are the x64 version running on Windows 10 Pro.

Thanks


#2

I have been using Jitsi for years but when I tried to establish a video

call

yesterday it would always fail with the error message "incompatible
parameters. Error: hostname can't be null". I was running the latest
stable version at that point and tried upgrading both clients to the 2.9

5534

build and get the same error. The only thing that really changed prior to
this was upgrading Openfire, which is now at version 4.0.4. Any ideas

would

be appreciated.

Can you please send us the logs?
https://jitsi.org/logs

Both clients are the x64 version running on Windows 10 Pro.

Thanks

Ingo


#3

Here you go.

Thanks

2016-12-26@06.16.10-logs.zip (752 KB)

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Ingo Bauersachs
Sent: Monday, December 26, 2016 04:42
To: 'Jitsi Users'
Subject: Re: [jitsi-users] Call failed - incompatible parameters. Error: hostname can't be null

I have been using Jitsi for years but when I tried to establish a
video

call

yesterday it would always fail with the error message "incompatible
parameters. Error: hostname can't be null". I was running the
latest stable version at that point and tried upgrading both clients
to the 2.9

5534

build and get the same error. The only thing that really changed
prior to this was upgrading Openfire, which is now at version 4.0.4.
Any ideas

would

be appreciated.

Can you please send us the logs?
https://jitsi.org/logs

Both clients are the x64 version running on Windows 10 Pro.

Thanks

Ingo

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


#4

Here you go.

Thanks. This in an interesting case. Your Jingle Nodes relay sends the IPv6 address 2601:188:c501:8b96:6a05:caff:fe1c:1f38%bond0 as the relay address. Note the %bond0 thing there. This is a scope identifier and it is only valid on the machine/server that owns this IPv6 address. So basically your XMPP server hands out an invalid relay address.

Now Jitsi (or rather ice4j) receives that address, but is unable to handle it (the %bond0 is invalid). Unfortunately, it half-way continues to process this invalid candidate and sends it as an invalid ICE candidate to the remote. The remote Jitsi can't handle that invalid candidate either and the whole call fails.

I'll try to fix Jitsi so that it ignores invalid candidates. It will take a while until a new build is out, so in the meantime you can try:
- Fixing the XMPP so that it hands out a correct relay address
- Disable Jingle-Relay nodes (Tools/Options/Accounts/Your xmpp account/ICE/Use Jingle Nodes)

Thanks

Ingo


#5

I think I found the problem, only to uncover another one. I noticed the following errors in the client log file when trying to start an audio or video call:

2017-01-05 09:45:25.677 INFO: [1074] impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.processPacket().906 Error while handling incoming Jingle packet:
java.lang.IllegalArgumentException: hostname can't be null

I removed the Jingle plugin from Openfire and tried again, this time the call connected, however, now I'm not getting a video image from the cameras from either end, and they are both completely different computers with different cameras. Will start looking into that now.

···

-----Original Message-----
From: users [mailto:users-bounces@jitsi.org] On Behalf Of Ingo Bauersachs
Sent: Monday, December 26, 2016 04:42
To: 'Jitsi Users'
Subject: Re: [jitsi-users] Call failed - incompatible parameters. Error: hostname can't be null

I have been using Jitsi for years but when I tried to establish a
video

call

yesterday it would always fail with the error message "incompatible
parameters. Error: hostname can't be null". I was running the
latest stable version at that point and tried upgrading both clients
to the 2.9

5534

build and get the same error. The only thing that really changed
prior to this was upgrading Openfire, which is now at version 4.0.4.
Any ideas

would

be appreciated.

Can you please send us the logs?
https://jitsi.org/logs

Both clients are the x64 version running on Windows 10 Pro.

Thanks

Ingo

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


#6

I think I found the problem, only to uncover another one. I noticed the
following errors in the client log file when trying to start an audio or
video call:

2017-01-05 09:45:25.677 INFO: [1074]
impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.processPacket()
.906 Error while handling incoming Jingle packet:
java.lang.IllegalArgumentException: hostname can't be null

I removed the Jingle plugin from Openfire and tried again, this time the call
connected, however, now I'm not getting a video image from the cameras from
either end, and they are both completely different computers with different
cameras. Will start looking into that now.

Did you see my reply on dev after you sent the logs?
http://lists.jitsi.org/pipermail/dev/2016-December/030631.html

Ingo