GNOME Bugzilla – Bug 495917
ekiga silently loses registration
Last modified: 2008-09-08 11:35:13 UTC
Please describe the problem: When my internet or wireless connection goes down, ekiga cannot re-register to my VoIP providers but instead of showing a warning message or even better trying re-register later it sits in the tray leaving the user to wonder why there are no incoming calls... Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
s/looses/loses/, and duplicate. *** This bug has been marked as a duplicate of 324564 ***
For I have only one network interface (eth1), which happens so be a wireless connection, I do not think that this problem is even remotely related to bug 324564. The problem is that, if ekiga fails to renew the registration, it silently drops that connection. I have to watch ekiga like a tamagotchi and whenever the number of registered accounts drops below the number it should be, I have to open the account configuration windows and manually disable and re-enable that account.
The other bug is twofold : 1) ekiga doesn't cope with interfaces going up or down ; 2) ekiga has issues with several interfaces. This bug is about (1), so I think it's a dupe. Damien will reopen if I'm wrong. :-) *** This bug has been marked as a duplicate of 324564 ***
This is a different issue as the network interface is not going down, it's just the network link between either my laptop and the wlan router, the DSL connection behind the WLAN router or even some remote network segment that prevents ekiga from renewing the SIP registration with my VoIP provider. You can easily try this for yourself. Register with a VoIP provider, then use iptables -j DROP to make that provider unavailable for a while. Now restore the network connection (by removing the iptables rule) and you will see that ekiga sits silently in the tray but does not accept incoming calls. Only by opening ekiga you see that the connection has failed and you must open the accounts window to manually re-establish it. In that case ekiga should show an error message, that the connection to $provider has been lost and keep trying to re-register with that provider. If it succeeds to re-establish the connection it might make sense to close the error message. At least it should not pop up another window if it looses the connection again.
I have exactly the same bug as described above. Ekiga does not re-register itself on a SIP proxy after first unsuccsessful attempt.
Should be fixed too. Ekiga is now able to react very well to that kind of change.