After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 624751 - Ekiga.net fails to interoperate with non-ekiga SIP clients behind NAT
Ekiga.net fails to interoperate with non-ekiga SIP clients behind NAT
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: ekiga.net
unspecified
Other Linux
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
: 650715 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-07-19 15:39 UTC by Jeremy Nickurak
Modified: 2020-06-06 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Nickurak 2010-07-19 15:39:09 UTC
The following bugs detail a buggy behavior with ekiga.net WRT non-ekiga SIP clients:

https://sourceforge.net/tracker/?func=detail&aid=2412241&group_id=143636&atid=756076
https://bugs.launchpad.net/ekiga/+bug/294994
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535796
https://bugs.freedesktop.org/show_bug.cgi?id=19328
https://bugs.maemo.org/show_bug.cgi?id=4259

To quote a few snippits:

> The cause is a bad configuration of ekiga.net proxy:
> https://sourceforge.net/tracker2/?func=detail&aid=2412241&group_id=143636&atid=756076
> The Ekiga client seemingly uses out-of-band STUN to discover the SIP binding,
> which is a flawed approach failing silently in certain NAT configurations.

...

> I reverse my stance from the earlier comments The modification of transport
> address in Via may cause interoperability problems with proxies that
> implement support for RFC 3581 and rely on the specified behavior for
> NAT-aware policies.
> 
> The restriction imposed by the proxy is arbitrary. It does not follow any
> specification or best practice published by IETF that I'm aware of. The
> answer is, fix the proxy.
Comment 1 David Ayers 2010-09-15 09:35:13 UTC
Thanks a lot for consolidating the reports, Jermey.  I can also confirm that I cannot connect to my ekiga.net account but I can successfully connect to the Ekiga-Call Out account I had registered to help support the ekiga project at the time.

Would it be a possibility to have correctly configured proxy under another server name like: nat.ekiga.net ?
Comment 2 Eugen Dedu 2011-05-17 10:03:53 UTC
A useful page: http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net
Comment 3 Eugen Dedu 2011-05-21 07:45:56 UTC
*** Bug 650715 has been marked as a duplicate of this bug. ***
Comment 4 kxra 2012-03-28 15:57:00 UTC
Is this something we can fix or that Ekiga needs to?
Comment 5 André Klapper 2020-06-06 16:29:14 UTC
Ekiga is not under active development anymore:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273

Ekiga saw its last release 7 years ago. The last code commits were 4 years ago.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.