Greetings all,
I have installed Jitsi recently and have spent the past three days
attempting to make it work. I did everything from uninstall my firewall, to
disconnecting my router, to calling my ISP - no matter what I did to
Windows or otherwise I could not connect a call. I could log in, send
messages, but calls would be blocked as if a firewall was blocking it -
even with network monitoring I couldn't even locate where it was attempting
to connect to.
As part of the debug process I downloaded the previous major releases for
windows, and confirmed that the Linux distributions were functioning
(Latest Ubuntu & Debian). This confirmed to me it was a Windows issue, and
through other parties confirmed it was not specifically a Windows 8 issue.
Today I managed to track down the true problem, which required I google a
very specific part of the error code, and lead me to this obscure mailing
list post; which matches some of the debug information relating to ICE
failing to connect:
https://java.net/projects/jitsi/lists/dev/archive/2013-05/message/28
I had also disabled/enabled about every connection option in Jitsi, and
with ICE disabled it would connect but send no data (no sound/video). I
finally trawled through the entire mailing list and located this post that
a user presented as a solution, which I will quote part of here for
posterity (post by "Ken Ayott") :
I made some progress with this after digging through the code. The problem
appears to be related to unused network interfaces on one of my Win7-64bit
PC’s. This particular PC has 2 network interfaces, one of which is
unplugged and not in use. I disabled this interface and the TAP-Win32
Adapter via Control Panel and now I can establish video calls. 2-way video
is still intermittent; sometimes I end up with a black screen on one
endpoint, and sometimes it works on both, but that is likely a different
issue.I suspect this is an issue with the way network interfaces are determined
and processed within the ice4j code, but can’t confirm that.
The solution to the error "Caused by: java.io.IOException: Failed to bind
even a single host candidate for component:Component id=1 parent
stream=audio" is to disable every network interface/driver on Windows that
is not connected to the internet. Later today I also managed to locate a
bug report submitted to the bug tracker <https://trac.jitsi.org/ticket/1164>
.
The reason I am bringing this up to the mailing list is the following: No
single post, website, or piece of information, contains both the error code
and the solution together. Even if you google the error code, it takes an
immense amount of difficulty to find the correct fix. Furthermore, the bug
report is nine months old, and does not contain precisely accurate
information.
As it took me three days to find and apply the solution after endless
frustration, and as it is very common for laptops to have both
wifi/ethernet network drivers enabled at the same time, that it deserves a
significantly higher priority and immediate fix than it has. The current
nightly build does not fix this defect either.
Therefore I request additional comment on what can be done to notify
people, who will be trying to search for a solution when this bug appears,
as well as improve the bug tracker post with more relevant information.
Thank you!
P.S. I apologize if I have breached any etiquette for the mailing list, as
I have joined simply to try and get more information compiled on this very
aggravating defect. Please forgive any oversights in my posting.