This actually works for me as well, just adding the --ipv4 option. I had
to modify the registry with this option in order for it to take effect on
Windows startup. Is there any way this could be a configuration option
within Jitsi to avoid the registry editing?
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of
Sent: Friday, May 24, 2013 10:38
Subject: [jitsi-dev] Re: Windows 7 multiple NIC issue
appending -4 to Jitsi.exe seems to solve this issue. we verified this on two
computers. according to
ipv6 on the interface should also fix this issue.
age: jitsi [OPTIONS] [uri-to-call]
-c, --config=DIR use DIR for config files
-d, --debug print debugging messages to stdout
-h, --help display this help message and exit
-m, --multiple do not ensure single instance
-6, --ipv6 prefer IPv6 addresses where possible only
-4, --ipv4 forces use of IPv4 only
-v, --version display the current version and exit
is -4 the option we are looking for i.e. is it equivalent to the jre option
Am 14.05.2013 11:31, schrieb g.spellauge:
one contact succeeded to make a jitsi-audio-call after moving the
active and connected interface to the last place behind the active but
maybe related: this user reported that jitsi is very memory-hungry
mb) on his machine. on my machine jitsi currently uses ~174 mb - less
than firefox but more than thunderbird.
Am 13.05.2013 12:40, schrieb g.spellauge:
two of my contacts changed the binding order by pushing the correct
nic to the first palce and i was able to call them/they were able to call
this workaround was not successful (no change) for two other contacts.
Am 11.05.2013 13:30, schrieb Ingo Bauersachs:
Changing the binding order might also help: if the NIC you want to
use is really at index 0, you luckily get the result you want.