[Rtcomm] [Rtcomm] [Bug 3928] sip on diablo

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Wed Dec 17 12:00:50 EET 2008
https://bugs.maemo.org/show_bug.cgi?id=3928


mikhail.zabaluev at nokia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikhail.zabaluev at nokia.com




------- Comment #1 from mikhail.zabaluev at nokia.com  2008-12-17 12:00 GMT+3 -------
The proxy at ekiga.net is badly configured, see the details:
https://sourceforge.net/tracker2/?func=detail&aid=2412241&group_id=143636&atid=756076
Implementing STUN for SIP (_not_ in-band with the SIP signalling) and then
mangling our Via header could be a solution, but it's bound to fail with many
NAT configurations. The in-band RFC 3581 approach we use is more robust, so I
can't see why ekiga.net has stopped supporting it, as it used to.
This is a WONTFIX, now on to the FWD problem:

(In reply to comment #0)
> fwd: can connect to server, but cannot connect to server

Sorry, I cannot understand what do you mean here.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=3928
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the Rtcomm mailing list