Created attachment 21555 [details] sofiasip-log when trying to my ekiga.net account with empathy (empathy-2.24.1-1.20081204svn1945.fc10.i386, telepathy-sofiasip-0.5.10-1.fc10.i386), I get "Network error" error and the attached sofiasip log. Needless to say, I can connect to ekiga.net account with the ekiga proper on the same computer.
The cause is a bad configuration of ekiga.net proxy: https://sourceforge.net/tracker2/?func=detail&aid=2412241&group_id=143636&atid=756076 The Ekiga client seemingly uses out-of-band STUN to discover the SIP binding, which is a flawed approach failing silently in certain NAT configurations.
(In reply to comment #1) > The Ekiga client seemingly uses out-of-band STUN to discover the SIP binding, > which is a flawed approach failing silently in certain NAT configurations. Clarification: that would be fine if the proxy did not reject the way to discover the address binding that actually works.
*** Bug 28909 has been marked as a duplicate of this bug. ***
Reported against ekiga's bug tracker at: https://bugzilla.gnome.org/show_bug.cgi?id=624751
Some additional thoughts. It should be possible to do a STUN binding lookup before registration and put the result in topmost Via header and the Contact URI. So in simple NAT cases it will work, and tricky cases would be hopefully saved if the proxy also applies RFC 3581, or just uses symmetric response routing regardless of the header information. But: 1) It requires non-trivial code additions to either in telepathy-sofiasip or sofia-sip, and takes some time to test and debug in many possible scenarios. 2) If done in telepathy-sofiasip, it introduces a dependency on a STUN implementation. In sofia-sip, it makes for more internal module dependencies, and requires Sofia STUN support to be enabled. 3) It adds a STUN roundtrip when registering with proxies that implement RFC 3581, which in some cases will increase time to register. An alternative is to add a runtime option, which is undesirable at least for MeeGo. In all, sounds like too much hassle in order to satisfy a strain of proxies that impose uncommon restrictions on top of standard SIP.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.