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 570511 - Enabling/disabling STUN should possible *per account*
Enabling/disabling STUN should possible *per account*
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: Engine
3.0.x
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2009-02-04 16:35 UTC by Alexander Hunziker
Modified: 2020-06-06 16:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Alexander Hunziker 2009-02-04 16:35:10 UTC 
Please describe the problem:
I have various SIP accounts, among others an ekiga.net account and one from a Swiss SIP provider (sipcall.ch) that maps to a Swiss phone number.

Sipcall.ch explicitly says that it needs STUN to be disabled. Indeed it doesn't function with STUN enabled.

Ekiga.net on the other hand, only works with STUN enabled.

With STUN only possible to be enabled/disabled globally, on not on a per account basis, there is currently no possible configuration in which both my accounts work.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Daniel Gimpelevich 2009-07-01 15:21:23 UTC 
This is STILL an issue in 3.2.4, and would fix bug #582713.
Comment 2 André Klapper 2020-06-06 16:29:48 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.