Hi all,
we'll have to postpone 1.11.8 release still by a few weeks. There's a few
problems - especially with the new refactored transport code - that we
need to solve before release.
One known problem is that CVS/darcs Sofia-SIP does not correctly handle
wildcard transports (user doesn't specific which address/protocol to use).
As a temporary workaround, specify the contact URL to nua_create():
- NUTAG_ULR() tag, for example NUTAG_URL("sip:0.0.0.0") to select
some available local IPv4 address as contact
- with sofsip-cli, "./sofsip_cli --contact="sip:0.0.0.0"
Otherwise, feature-wise we are getting close to a stable release (1.12 or
2.0, still have to decide which :)). Today's merge added features like SIP
over HTTP-CONNECT, registration update (support multiple ways to register
to network over NATs, etc), simple OPTIONS-based NAT-keepalive for those
SIP servers that do not support any other mechanisms (-> most existing
servers I'm afraid), mt-friendly sresolv, etc, etc. AFAIK, no features
planned for 1.12 (see TODO) are now missing -- we just need more
testing, and fixing known bugs.
If someone wants to point out any ugly places still left in our APIs, now
would be a very good time to do so. :) Once the stable release is out,
we'll be stuck with the APIs for a long time to come.
--
under work: Sofia-SIP at http://sofia-sip.sf.net
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
