GNOME Bugzilla – Bug 626711
Ekiga 3.2.6 doesn't do re-registering of SIP accounts automatically (SuSE 11.3 86x64)
Last modified: 2011-11-15 08:52:32 UTC
After timeout is over a SIP account does not register again automaticaly, manualy can be unregistered and registered again and again. Changing timeout seconds does not make any difference, re-registering does not happen automatically. There are no other configuration options about registering with SIP accounts. Is there is a way ekiga can be forced to re-registered itself automaticaly ?
I have the same problem. Using Gentoo, version 3.2.6, opal-3.6.8. My sip server (swyx) has a 120 sec lifetime for sessions, and so that is my max time for phone calls. tcpdump confirms that Ekiga does not re-register despite a 60 sec timeout in sip account config.
Also a problem on ubuntu 10.04 (lucid) ekiga-3.2.6 and opal-3.6.6
After debugging Ekiga and playing a bit with the code, I see that this is not a bug. This has to do with headers not matching. Probably best explained here: http://mail.gnome.org/archives/ekiga-list/2010-January/msg00009.html For me the problem was that the sip connection tracker for iptables always added the port to my sip headers. Ekiga seems to skip the port part of the contact when the listen_port is 5060. A quick fix for this is to change the listen_port to non standard such as 5061.
olegue, do you have the same problem? If yes, this bug should be closed.
any news for this report?
in 5.2.7 this same problem (I think) I can connect from ekiga anywhere, but if i set timeout: 100 - after 100seconds I can't call to my voip from external line. If set 200 - after 200seconds!
same problem with Fedora 14 x86_64 I will have to use Twinkle meanwhile this problem is not solved in Ekiga
I think I am having the same problem. my SIP provider (callwithus.com) shows to set timeout to 120 seconds for ekiga, but after some time when I call my number i got extension unavailable message. I unregister and register manually and it works for some limited time.
There were many changes between ekiga 3.2.x and 3.3.x. Could someone who has this bug try with ekiga 3.3.2 and tell if this still appears? If still appears, please attach a new -d 4 output.
Mikołaj, aovacik, aderocha , can anyone reproduce the bug with ekiga 3.3.2 ?
I will try during next week and let you know if problem still exists
It seems problem does no longer exists, but I have found other for which I think I will create a new fault: Ekiga should recover registration after network connection lost (e.g. disconnected) and re-established
(In reply to comment #12) > It seems problem does no longer exists, but I have found other for which I > think I will create a new fault: > Ekiga should recover registration after network connection lost (e.g. > disconnected) and re-established I confirm it, please make a new bug report.