Andy, The reason for the registration fail *in your case* is this:
Looking at the SIP protocol, the via field is like this when Ekiga try to register: Via: SIP/2.0/UDP 85.200.112.246:14370;branch=z9hG4bK865b099f-f766-de11-8cb8-00188b857008;rport The IP (yours) is a public one (internet wise): 85.200.112.246 When Ekiga.net answer to it, the via field is: Via: SIP/2.0/UDP 192.168.80.80:15476;branch=z9hG4bK865b099f-f766-de11-8cb8-00188b857008;rport=14370;received=85.200.112.246 The IP here is private: 192.168.80.80 (inside a LAN). Ekiga.net service do not rewrite this field. Thus we think it is your router which rewrite the address (for some reason). The expected practical working solution is to turn off the NAT traversal service ekiga use (STUN). To do this, using ekiga 3.2.x, you have to: Disable network detection in ekiga should be enable: this is accessed under the Edit → Preferences → General Settings → Network Settings menu. Then restart Ekiga and see if it can register. Best regards, Yannick P.S. : to other reporters, this solution might work for you, or not, depending on what your issue is. The only way for us to understand your issue is to have a "-d 4" output as explained above. -- Fails to register ekiga.net account https://bugs.launchpad.net/bugs/362647 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
