GNOME Bugzilla – Bug 340251
outbound SIP proxy setting should be attached to accounts
Last modified: 2017-03-07 11:32:58 UTC
the outbound SIP proxy setting should probably be attached to each account, rather than being a single global setting. In particular, note that for some reason REGISTER messages are always sent to the global outbound SIP proxy. This causes complications.
It is planned for 2.2 (see the roadmap on wiki.ekiga.org)
It is good to see that this has got some attention - currently I am not able to use my pc-to-phone account and ekiga.net account simultaneously.
*** Bug 427016 has been marked as a duplicate of this bug. ***
To be complete, bug #427016 was about both proxy *and* STUN attached to accounts.
I second this request. I'am getting very tired of changing the outbound proxy option! In general, I think the SIP, network and H323 options should be per account instead of just global option. The global option could be the default if not specified in the account.
"I'am getting very tired of changing the outbound proxy option!" It would be faster is somebody proposed a patch...
Created attachment 90197 [details] [review] Patch to define the outbound proxy (SIP) on a per account basis I simply removed the global SIP outbound proxy field and defined 3 fields for SIP accounts (host, user, password). I didn't implement any logic to migrate the global settings to the individual accounts. I find the way of storing SIP account settings disturbing (|-delimited string instead of subtree). For example, you can't use the character '|' in the password. Would you accept patches to correctly map accounts to a subtree in the gconf settings? Updating the GUI of ekiga involves much copy and paste. If ekiga used libglade, it would have been less work to implement. Would you accept patches to make ekiga use libglade?
Hi, Your patch is great, but OPAL does not support yet setting a different proxy for each account. Once it will support it (it is on my TODO list), I will reuse your code for the UI change. libglade is not interesting for us, because it means one more dependancy for all platforms we support (including WIN32), but thanks for the offer :) However if you have some spare time, there are many things in which you can help, including in the GUI ! Thanks !
Hi, yes, this would be a great feature. As it will take some time to get this running: Is it possible to set the SIP proxy via the command line? Option or variable? If not, is this easy to implement (as a quick workaround)? Frank
Is it easily possible to implement in 3.x before the release?
No, I wouldn't do that...
I checked the 3.2 roadmap[1], the feature is put at signaling features. It's there is any difficulty or reason to hold up merge the patch? :-) 1. http://wiki.ekiga.org/index.php/Roadmap_to_3.2.0#Signaling_Features
Is comment #8 still current (does opal support one proxy for each account)?
*** Bug 594467 has been marked as a duplicate of this bug. ***
Reopening as I can't see any open question addressed to a reporter.
This is fixed with https://git.gnome.org/browse/ekiga/commit/?id=2d60edd8.
I have ekiga 4.0.1 on debian testing but i do not see a way to enable per-account outbound proxy management. Ekiga wiki confirms this behavior: http://wiki.ekiga.org/index.php/Manual#Outbound_proxy
Unfortunately, this commit is only on development branch of Ekiga, not on the stable one (Ekiga version 4).