kapetr wrote: > Hello, > > > ----- PŮVODNÍ ZPRÁVA ----- >> Date: Thu, 25 Feb 2010 21:55:03 +0100 >> From: Eugen Dedu <[email protected]> >> To: Ekiga mailing list <[email protected]> >> Subject: Re: [Ekiga-list] Ekiga on Ubuntu using DSL >> 302G D-Link modem >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=UTF-8 >> >> kapetr wrote: >>> The reason, why You can't communicate with Ekiga >>> behind Yours D-link >>>> is simple. >>> EKIGA IS BUGGY >>> >>> I have report this Bug many times in many places. >>>> I have also try to contact the author of Ekiga. >>> Unfortunately - I have get NO replay anytime !!! >>> >>> The problem with Ekiga is, IT DO NOT WORK BEHIND >>> NAT. >>> >> You mean Symmetric nat... > > No, I don't - Ekiga works not behind normal, "(port) restricted NAT". > >>> The use of STUN is broken: >>> >>> Ekiga makes STUN request, but in INVITE (SDP section) >>> send only discovered >>>> public IP address, but the Port for RTM sends to >>> the other side as the >>>> local one, not that is reported by STUN replay !! >>>> >>> You can check it in wireshark - see the SIP INVITE >>> packet. >>> I can NOT understand, how such significant Bug is >>> ignored by developers >>>> of Ekiga !!! And especially, why have I get no replays >>> from them :-( >>> >> Where is this bug report? > > e.g. here: > > https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/517580 > > There is also saved tcpdump output - You can check, that it s True. > > I have report it also direct to [email protected]
For upstream bugs (like this one) the best solution is to report the bug to ekiga bugzilla (better than to the main developer privately), not be scattered to ubuntu, debian, fedora and so on. Thanks for it, I will find a way to solve/analyse it. For info, I have a port restricted nat and ekiga works, so not all such users are unfortunate like you :o) -- Eugen _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
