Hi,
according to our last IRC meeting [1] we want to release a minor release for the 1.4 branch in the next days. We've did already over 40 changes in this branch, many of them for important bugs, so i propose the next thursday, the 11th december as the date for 1.4.3. So if you have any important backports or other fixes that should go into this release, please commit them until this day.
While already on the release topic, the code freeze period for the 1.5.0 release will be start in the mid of Januar, roughly in about 6 weeks from now. So if you like to contribute something that should be included in this release, please commit it to our repository or upload the patch to the tracker for review. Already finished features and the roadmap can be found as usual in our wiki at [2, 3].
If you like to give the new features a try, then you find prebuild packages for several debian releases here [4]. Please report any bugs you find to our developer list.
Best regards,
Henning
[1] http://www.kamailio.org/mos/view/News/NewsItem/IRC-Devel-Meeting-Summary---N... [2] http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x [3] http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x [4] devel.kamailio.org
Henning Westerholt writes:
Already finished features and the roadmap can be found as usual in our wiki at [2, 3].
in my opinion the roadmap should include normal failure route processing of also tcp connect failures. now it is very bad that script writer needs to handle failures in two places in the script depending if udp or tcp is used for a particular contact.
also, i would like to see a conclusion regarding local route implementation, which was left out by default from 1.4.
-- juha
El Viernes, 5 de Diciembre de 2008, Juha Heinanen escribió:
in my opinion the roadmap should include normal failure route processing of also tcp connect failures. now it is very bad that script writer needs to handle failures in two places in the script depending if udp or tcp is used for a particular contact.
Could you explain it? What do you mean with "failure route just for TCP/UDP"? I already know about the bug when sending a request via TCP gets a DNS error (failure_route is not executed) but I know nothing about two separated failure routes, for UDP and TCP.
Thanks.
Iñaki Baz Castillo writes:
I already know about the bug when sending a request via TCP gets a DNS error (failure_route is not executed) but I know nothing about two separated failure routes, for UDP and TCP.
i meant different failure handling for an unreachable UA depending of if the UA uses udp or tcp transport. this is not limited to dns errors. you may get ip address of UA from dns ok, but tcp UA simply does not response.
i want that failure route gets executed if t_relay fails to reach the UA for any normal non-error reason (no dns response, tcp host unreachable). in 1.4 it was impossible to write a proper script for tcp case, because next_contacts() or next_gw() could not be executed in route block. in 1.5 it would be possible, but the resulting script would look really awkward.
-- juha
On 12/05/08 18:05, Juha Heinanen wrote:
Henning Westerholt writes:
Already finished features and the roadmap can be found as usual in our wiki at [2, 3].
in my opinion the roadmap should include normal failure route processing of also tcp connect failures. now it is very bad that script writer needs to handle failures in two places in the script depending if udp or tcp is used for a particular contact.
It is in my todo lists, but I was pretty busy with other projects.
also, i would like to see a conclusion regarding local route implementation, which was left out by default from 1.4.
Work is undertaken to fix what is possible, the new $T_req(pv) and $T_rpl(pv) got a similar solution (however, for local route is needed more than what was done here so far). As we are going to have first the SIP Router core and then go for full asynchronous mode and contexts (sip router has already kind of asynchronous processing support already), for 1.5.0 will be a jailed protection against the issues caused by local route.
There is another problem here, with the processes started by MI transport modules - local route is executed by these processes but they are not properly initialized, as a sip message worker. Probably another temporary hack to fix this one as well. Let's see how it gets until we freeze the code...
Cheers, Daniel
Juha Heinanen schrieb:
Henning Westerholt writes:
Already finished features and the roadmap can be found as usual in our wiki at [2, 3].
in my opinion the roadmap should include normal failure route processing of also tcp connect failures. now it is very bad that script writer needs to handle failures in two places in the script depending if udp or tcp is used for a particular contact.
Would be interesting if sr tm module has the same behavior.
regards klaus
also, i would like to see a conclusion regarding local route implementation, which was left out by default from 1.4.
-- juha
Devel mailing list Devel@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
We should screen opensips bug fixes for relevant fixes. I can take care of presence related fixes - but not before the weekend.
regards klaus
Henning Westerholt schrieb:
Hi,
according to our last IRC meeting [1] we want to release a minor release for the 1.4 branch in the next days. We've did already over 40 changes in this branch, many of them for important bugs, so i propose the next thursday, the 11th december as the date for 1.4.3. So if you have any important backports or other fixes that should go into this release, please commit them until this day.
While already on the release topic, the code freeze period for the 1.5.0 release will be start in the mid of Januar, roughly in about 6 weeks from now. So if you like to contribute something that should be included in this release, please commit it to our repository or upload the patch to the tracker for review. Already finished features and the roadmap can be found as usual in our wiki at [2, 3].
If you like to give the new features a try, then you find prebuild packages for several debian releases here [4]. Please report any bugs you find to our developer list.
Best regards,
Henning
[1] http://www.kamailio.org/mos/view/News/NewsItem/IRC-Devel-Meeting-Summary---N... [2] http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x [3] http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x [4] devel.kamailio.org
Devel mailing list Devel@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
On Tuesday 09 December 2008, Klaus Darilion wrote:
We should screen opensips bug fixes for relevant fixes. I can take care of presence related fixes - but not before the weekend.
Hi Klaus,
i could also need a little bit more time to investigate the DB bug that gets reported today. Daniel also with the tm retransmission bug.. So lets postpone the release date, perhaps to the next tuesday, 16.12? Is this ok for you too?
Cheers,
Henning
ok
Henning Westerholt schrieb:
On Tuesday 09 December 2008, Klaus Darilion wrote:
We should screen opensips bug fixes for relevant fixes. I can take care of presence related fixes - but not before the weekend.
Hi Klaus,
i could also need a little bit more time to investigate the DB bug that gets reported today. Daniel also with the tm retransmission bug.. So lets postpone the release date, perhaps to the next tuesday, 16.12? Is this ok for you too?
Cheers,
Henning
-
Daniel-Constantin Mierla -
Henning Westerholt -
Iñaki Baz Castillo -
jh＠tutpro.com -
Klaus Darilion