GNOME Bugzilla – Bug 590975
Registration port should be set on a per account basis
Last modified: 2009-09-01 08:13:15 UTC
Hi, Downstream bug réference: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/409842 "There is no option to specify custom port for an account registrar. It need to be configured per account bases. For example, Spikko uses port 5090 (d1.spikko.com) while SIPGate uses port 5060 (sipgate.co.uk)." To uncluttered the GUI, as it is unusual requirement, I propose this behaviour: In the account window, being able to set "registrar[:port]" Best regards, Yannick
From the downstream reporter: "Here are some [providers] that require none standard SIP ports: sip.ritstele.com d1.spikko.com i2telecom.com From my experience, many organizations deploy VoIP solutions on a none standard ports to increase security (by obscurity). There are some VoIP clients that do allow to specify a SIP port number for every account. For example, http://www.sip-communicator.org (as a field) and http://www.nch.com.au/talk/ (accept host:port combination)."
Reading exceptionnaly my mails from holidays. You can put sip.machin.com:5081 as registrar. => NOTABUG
There's this bug too: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530051.
I'm not sure it is correct. Last time I tested, it did work. Can you double check with trunk and stable ? It is easy to check.
I have just checked with trunk of two weeks ago. It does not work. I create a SIP account and put google.com:40000 as Registrar. -d 4, attached, does not mention any 40000 string; it still uses 5060. Citing Thomas Schorpp: "There's no such feature "user defined sip port", provider is responsible for correct DNS SRV setup." So maybe ekiga works when the dns has a correct srv setup? And if it does not, the only way (except asking the registrar to fix it) is that user adds himself the port in the Registrar field, but that does not work in ekiga.
Created attachment 140216 [details] Debug output, no 40000 inside, only 5060
Created attachment 140221 [details] same setup as Eugen using 3.2.0, registrar=google.com:40000 , different output
So: - I think the downstream bug is wrong (it works with 3.2.0) - I think trunk is broken Perhaps Robert should be warned about this.
It indeed works with 3.2.0 as reported by the downstream reporter. Still, it seems there is an issue with the account GUI in 3.2.0; not giving the usual feedback "Registered". Downstream reporter words: "You are absolutly right; this setup does work! I have received a phone call on the account which is using none standard port (Spikko) which really surprised me because Ekiga does not change to status to "Registred" as it does to any other SIP account which uses standard SIP port." Unfortunately, I've no test case to test this myself... and I'm still waiting a debug output from downstream reporter.
Damien, so this bug is fixed (http://git.gnome.org/cgit/ekiga/commit/?h=gnome-2-26&id=7b37850eaee3c57c3b7cc35ec353f36dab2d5102), is that right?
I think so.
It is fixed, indeed.
*** Bug 593705 has been marked as a duplicate of this bug. ***