-
What do you know, it works for me with the sofia-sip build we use in Maemo 5.
Can somebody else confirm if it works with sofia-sip trunk?.
2009-11-13 16:26:09 UTC by mzabaluev
-
> So, if the problem is with ekiga.net, has anyone contacted them about it
yet?
Sort of; last word I heard from them is, they need this restriction so that their own client keeps working. I still think they shouldn't impose a restriction on the address in Via, and sofia-sip should now re-register with a discovered mapped address in Contact. I didn't press this last comment to them yet, though.
2009-10-15 11:47:41 UTC by mzabaluev
-
So, if the problem is with ekiga.net, has anyone contacted them about it yet?.
2009-10-13 05:50:34 UTC by murrayc
-
Applied into darcs.
2009-09-24 15:52:54 UTC by ppessi
-
This patch removes the code that initializes the default CA file name for OpenSSL, if it is not set by the application. This causes TLS transport to fail if there is no such file available to the process.
In Maemo 5 and other distributions, OpenSSL has the default CA path set up just fine,
2009-09-24 13:29:40 UTC by mzabaluev
-
From the Maemo 5 branch:
These patches fix a crash in deferrable timer processing for a GLib mainloop.
Also, the NUA stack timer and the transport timer are set as deferrable. I hope this does not break anything :)
2009-09-24 13:24:58 UTC by mzabaluev
-
Thanks. Applied to darcs.
2009-09-24 10:33:40 UTC by ppessi
-
There is a copy-and-paste error in an inner loop, causing an endless busy loop in some circumstances.
2009-09-14 16:50:31 UTC by mzabaluev
-
I reverse my stance from the earlier comments The modification of transport address in Via may cause interoperability problems with proxies that implement support for RFC 3581 and rely on the specified behavior for NAT-aware policies.
The restriction imposed by the proxy is arbitrary. It does not follow any specification or best practice published by IETF that I'm aware of. The answer is, fix...
2009-06-08 13:54:45 UTC by mzabaluev
