[Bug 19328] cannot connect to ekiga.net account

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=19328

--- Comment #5 from Mikhail Zabaluev <mikhail.zabaluev at nokia.com> 2010-07-20 09:55:53 PDT ---
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.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.