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 427016 - stun and outbound proxy should be part of the account, not preferences
stun and outbound proxy should be part of the account, not preferences
Status: RESOLVED DUPLICATE of bug 340251
Product: ekiga
Classification: Applications
Component: general
GIT master
Other All
: Normal minor
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-06 18:50 UTC by Matthew Daniel
Modified: 2007-04-12 15:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Matthew Daniel 2007-04-06 18:50:39 UTC
I have three different VoIP providers and NONE of them share a STUN server or Outbound Proxy. Thus, when I want to switch between them, I must open Preferences, change the value and restart Ekiga for the new settings to take effect.

Until I make this change, I can have as many Accounts defined as I wish, but only one of them can work at a time.

If this information were part of the Account (in Accounts dialog), this would not be so painful.

Other information:
The three accounts are Teliax, CallCentric and FreeWorldDialup (if that matters).
Comment 1 Snark 2007-04-07 16:12:53 UTC
But... a single STUN server is enough to punch your firewall -- it would be ridiculous to use several of them. Likewise for outbound proxies.

Or do I err ?
Comment 2 Jan Schampera 2007-04-07 18:03:52 UTC
IMHO you err.
Some providers use the STUN query as part of their auth process - the auth only succeeds if their STUN server was queried from the same IP. Currently I hack that into a test accounts management backend.

J.
Comment 3 Snark 2007-04-07 18:29:44 UTC
Gasp... is that even standard-compliant !?
Comment 4 Jan Schampera 2007-04-07 20:25:23 UTC
Which standard should cover that?

J.
Comment 5 Snark 2007-04-08 15:48:32 UTC
There certainly is a standard (probably RFC) on how to authenticate. I would be a little surprised if an IETF draft on "SIP authentification" would have as a MUST to  configure a proxy and a STUN as part of the process...

Damien ?
Comment 6 Jan Schampera 2007-04-08 23:09:29 UTC
I more meant it vice versa: Which standard should forbid that an ISP checks if the client that tries to authenticate did a STUN request within the last N seconds on one of their STUN server?

I can't remember which ones, but that practise exists, I had 2 or 3 such issues in #ekiga on FreeNode.

J.
Comment 7 Damien Sandras 2007-04-09 18:02:22 UTC
I have taken a few days holidays, I only read a few bug reports.

If a provider relies on STUN to authenticate, then it is broken. I have never seen that.

From my point of view, STUN settings should be global, they are common to all protocols. However, the SIP Outbound Proxy should be account specific.

I have made the H_Release code ready to support several outbound proxies. So once Robert has committed the code, I'm ready to change that.

I disagree for the STUN code. However, I will check how SNOM phones are doing things.
Comment 8 Snark 2007-04-12 15:05:06 UTC
Sigh. In fact, we already have a bug about it...

*** This bug has been marked as a duplicate of 340251 ***