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:  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.
From: users [mailto:email@example.com] 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
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
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.
Can you please send us the logs?
Both clients are the x64 version running on Windows 10 Pro.
users mailing list
Unsubscribe instructions and other list options: