GNOME Bugzilla – Bug 597549
ekiga doesn't work anymore with 1und1
Last modified: 2009-10-07 12:34:31 UTC
I used to use ekiga as sip client for 1und1 (german SIP provider). I just started to test ekiga 3.2.5 and found that it doesn't work anymore. The error is "403 Forbidden (No RFC 1918 IP allowed)". I'm behind a router with masquerading/nat so that makes perfect sense. Ekiga 3.0.1 (which I've used before) was using an external service to locate the public IP I guess what is not done anymore apparently. In addition I cannot find any configuration dialog which would let me set these network specific things and automatic NAT traversal is not sufficient in that case apparently.
%limited hack
Please use 3.2.6 instead, and add the string "%limit" in your account name, it should work, and close the bug afterwards.
I've now tried 3.2.6 and changed my account name to "1und1%limit", "%limit1und1", "1und1 %limit" and a few other combinations. But still I get the same error. ekiga still tries to register three contact bindings including a private ip address according to wireshark.
Hmm, after a restart it began to work even w/o adding %limit. Not sure why though.
There is a confusion here. Account name changing is taken into account only after restarting ekiga (bug #596185). So I think you did: - 1und1 does not work - change account name => does not work - restart ekiga => works - change account name => works (normal, since you need to restart ekiga) - now, if you restart ekiga, it should not work Conclusion: after changing account name, restart ekiga. Finally, this bug should be closed?
ok, could be the case. That a restart is required sounds even more weird than a magic string in the account name. So this can be closed as long as it doesn't mean that this hack is a final solution ;-)