Hello,
it is time to set the time to release v3.2.0. From my point of view, testing went very well, considering also that core and main modules were not touched much during this devel cycle, the most of the efforts were on new modules and application service components such as presence server, Lua ...
A convenient date for me will be Tuesday, October 18, 2011, allowing to work a bit on packaging and docs. If there are other preferences, jump in this discussion.
Cheers, Daniel
Hello Daniel,
I had one issue in the sipcapture (mirroring mode), but the problem was found and I'll commit the patches today/tommorow.
Wbr, Alexandr
2011/9/28 Daniel-Constantin Mierla miconda@gmail.com
Hello,
it is time to set the time to release v3.2.0. From my point of view, testing went very well, considering also that core and main modules were not touched much during this devel cycle, the most of the efforts were on new modules and application service components such as presence server, Lua ...
A convenient date for me will be Tuesday, October 18, 2011, allowing to work a bit on packaging and docs. If there are other preferences, jump in this discussion.
Cheers, Daniel
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
______________________________**_________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**devhttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
On 09/28/2011 12:56 PM, Daniel-Constantin Mierla wrote:
Hello,
it is time to set the time to release v3.2.0. From my point of view, testing went very well, considering also that core and main modules were not touched much during this devel cycle, the most of the efforts were on new modules and application service components such as presence server, Lua ...
A convenient date for me will be Tuesday, October 18, 2011, allowing to work a bit on packaging and docs. If there are other preferences, jump in this discussion.
Cheers, Daniel
Hello Daniel,
I have some patches regarding IPv6 interface discovery on Linux. Now the IPv6 interfaces have to be manually binded to via a listen directive (because ipv6 discovery doesn't work on linux), but this patch fixes it .So if kamailio is not given a listen interface , he will discover any non-link-local ipv6 iface and bind to it. This changes the default behavior (no IPv6 default binding), and works for all supported transport protocols (UDP, TCP, SCTP, TLS(over TCP))
The patch is fairly well tested (but not yet in production), and is based on Linux specific RT_NETLINK sockets (for other NIX flavors like BSD the present code works well).
Do you think this patch is of interest for 3.2 release?
Marius
Hello Marius,
On 9/28/11 12:06 PM, marius zbihlei wrote:
On 09/28/2011 12:56 PM, Daniel-Constantin Mierla wrote:
Hello,
it is time to set the time to release v3.2.0. From my point of view, testing went very well, considering also that core and main modules were not touched much during this devel cycle, the most of the efforts were on new modules and application service components such as presence server, Lua ...
A convenient date for me will be Tuesday, October 18, 2011, allowing to work a bit on packaging and docs. If there are other preferences, jump in this discussion.
Cheers, Daniel
Hello Daniel,
I have some patches regarding IPv6 interface discovery on Linux. Now the IPv6 interfaces have to be manually binded to via a listen directive (because ipv6 discovery doesn't work on linux), but this patch fixes it .So if kamailio is not given a listen interface , he will discover any non-link-local ipv6 iface and bind to it. This changes the default behavior (no IPv6 default binding), and works for all supported transport protocols (UDP, TCP, SCTP, TLS(over TCP))
The patch is fairly well tested (but not yet in production), and is based on Linux specific RT_NETLINK sockets (for other NIX flavors like BSD the present code works well).
Do you think this patch is of interest for 3.2 release?
can you push it in a personal branch to review the impact on the existing code. It is of interest, of course, ultimately there can be a parameter (cfg or command line) to control it.
Thanks, Daniel
On Wednesday 28 September 2011, Daniel-Constantin Mierla wrote:
[default binding for IPv6]
Do you think this patch is of interest for 3.2 release?
can you push it in a personal branch to review the impact on the existing code. It is of interest, of course, ultimately there can be a parameter (cfg or command line) to control it.
Hi Daniel,
in my opinion the IPv6 behaviour should be consistent to the one in IPv4 - this is probably what out users expect anyway. So if we really need another cfg parameter for this, the default should be like in IPv4.
Best regards,
Henning
Hello,
On 9/28/11 12:31 PM, Henning Westerholt wrote:
On Wednesday 28 September 2011, Daniel-Constantin Mierla wrote:
[default binding for IPv6]
Do you think this patch is of interest for 3.2 release?
can you push it in a personal branch to review the impact on the existing code. It is of interest, of course, ultimately there can be a parameter (cfg or command line) to control it.
Hi Daniel,
in my opinion the IPv6 behaviour should be consistent to the one in IPv4 - this is probably what out users expect anyway. So if we really need another cfg parameter for this, the default should be like in IPv4.
I agree, I expressed my opinion for the case someone looks for backward compatibility, so there can be added a parameter that will allow that.
At some point in the (near :-) ) future, we may want auto-discover for IPv6 only, not for IPv4, because IPv4 will be sporadically used, just for some very old and crappy SIP phones (we have today). Cheers, Daniel
On Wednesday 28 September 2011, Daniel-Constantin Mierla wrote:
I agree, I expressed my opinion for the case someone looks for backward compatibility, so there can be added a parameter that will allow that.
Hi Daniel,
understand.
At some point in the (near :-) ) future, we may want auto-discover for IPv6 only, not for IPv4, because IPv4 will be sporadically used, just for some very old and crappy SIP phones (we have today).
I'm looking forward to this time.. ;-)
Best regards,
Henning
On 09/28/2011 01:24 PM, Daniel-Constantin Mierla wrote:
can you push it in a personal branch to review the impact on the existing code. It is of interest, of course, ultimately there can be a parameter (cfg or command line) to control it.
Thanks, Daniel
Hello Daniel,
Here it is http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=bcea195d...
branch mariuszbihlei/ipv6_fix
Cheers, Marius
On 09/28/2011 01:24 PM, Daniel-Constantin Mierla wrote:
Hello Marius,
On 9/28/11 12:06 PM, marius zbihlei wrote:
can you push it in a personal branch to review the impact on the existing code. It is of interest, of course, ultimately there can be a parameter (cfg or command line) to control it.
Hello Daniel,
I've added the auto_bind_ipv6 global (and cfg) parameter to enable/disable ipv6 discovery. By default it is off. As a side note, we can't use ipv6 functionality without this patch, so I consider this to be quite a bug fix
If nobody objects, I will merge the branch into master tomorrow.
Cheers, Marius
Thanks, Daniel
-
Alexandr Dubovikov -
Daniel-Constantin Mierla -
Henning Westerholt -
marius zbihlei