Jaunty: Using custom registrar port, Account GUI do not show "Registered", Karmic (Ekiga 3.2.5): custom registrar port do not work

[John Markh]

Binary package hint: ekiga

There is no option to specify custom port for a 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).

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.2.0-0ubuntu2
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ekiga
Uname: Linux 2.6.28-14-generic i686

[Yannick Defais (sevmek)]

Hi,

What happen if you specify a port in the registrar field in the account window?

e.g.

Spikko
Registrar: "d1.spikko.com:5090"

SIPGate
Registrar: "sipgate.co.uk:5060"

Best regards,
Yannick

[John Markh (dragonsol)]

Tired, does not work (nothing happens at all).

[Yannick Defais (sevmek)]

I pushed upstream and attached the bug here.

Thank you.

Best regards,
Yannick

[Pedro Villavicencio (pedro)]

Thanks for sent this upstream, marking it as triaged.

[John Markh (dragonsol)]

Thanks.

I would change the importance from low to show stopper because it is impossible to use Ekiga with large number of VoIP providers.

[Yannick Defais (sevmek)]

Hi,

Could you write down a list? I'm doing support for Ekiga on a daily basis since years and we do not have much reports about SIP providers not using the standard 5060 listen port. A list will effectively raise the priority upstream. btw, i'm part of upstream: Ekiga -> About

Best regards,
Yannick Defais

[John Markh (dragonsol)]

A list... that would be tough as there are thousands of VoIP providers. Here are some 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).

[Yannick Defais (sevmek)]

Thank you.

[Yannick Defais (sevmek)]

Hi John Markh,

We ran some tests and it seems this feature works with 3.2.0 using the setup explained in comment #2.

It might be a configuration issue. To help you configure properly, I'm giving you an example in form of a screenshot attached.

It might be another issue. To get a more clean picture of your issue, please attach a debug output:
Setup your accounts accordingly to the screenshoot. Close Ekiga. Open a terminal and start ekiga using this command:
$ ekiga -d 4 2>output.txt
Wait until the registration fails. Close Ekiga.
The output.txt file contains the debug output of ekiga you need to attach here. This file should be in your home directory.

Best regards,
Yannick

[John Markh (dragonsol)]

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.

[Yannick Defais (sevmek)]

Hi,

Please attach a debug output; I would like to understand this registration issue.

Best regards,
Yannick

[Yannick Defais (sevmek)]

3.2.5 has the custom port for registrar bug issue, it has been fixed in

http://git.gnome.org/cgit/ekiga/commit/?h=gnome-2-26&id=7b37850eaee3c57c3b7cc35ec353f36dab2d5102

3.2.6 will most probably fix it.