As I stressed to Rouven this is a usability issue and not a "feature" issue. Jitsi works fine with direct connections on a standard server, but it needs your servers to have extra components like STUN and TURN for firewalled connections to work. Yes the error message is useless (especially to an end user) but the fact that it cannot connect is due to your XMPP/SIP server not being set up with these extra components. I would desperately support more user feedback on the ICE process being given to the end user though: we're currently trying to set this up in our company using OpenFire as a server and the only way we can "debug" is by pulling the logs from the calling client.
As for your disconnection issue, I don't know what would cause that. I'm just a user of Jitsi at the moment.
Hope this helps,
Toby Pinder | Telemetry Software Engineer
This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
I recently started to use jitsi, the chat works just fine. But calling
doesnt work. If someone calls me while connected through my student
residential NAT, the calling window pops up saying "ICE failed". If I
try to call someone it doesn't even start the call stating: "Call
ended by remote side. Reason: incompatible-parameters. Error: null".
Using my Android as Hotspot, everything works perfectly, so it's not a
problem with my XMPP server or Program settings. Must be restrictions
from my NAT, and I can't change anything here!
I think this is a bug for two reasons:
1. If Jitsi wants to compete with Skype it should just work, anywhere.
2. The Error message is useless.
Any possibilities to make it work ?!
I do have the same problem with my call partner, depending on location.
Jitsi sort of works from one place, but we get the ice-problem from the
other. My place is also behind a rather restrictive firewall, and
there's nothing I can do about it. So far this has ruined most attempts
of making voice/video calls using jitsi or linphone. In the rare cases
when it worked, a jitsi bug showed up after a few minutes and gone was
the audio, forcing both call partners to delete .jitsi in order to
make another call possible. This has gotten really frustrating.
I hope the jitsi devs will at some point go the remaining 90% and not
only implement feature after feature but also make sure that they work
On 10/10/13 17:21, Philipp Überbacher wrote:
On Thu, 10 Oct 2013 11:42:28 +0200 Rouven Volkmann <firstname.lastname@example.org><mailto:email@example.com> wrote:
dev mailing list
Unsubscribe instructions and other list options: