[OpenSIPS-Users] Planing the future OpenSIPS releases

Ionut Ionita ionutionita at opensips.org
Thu Jan 14 09:50:21 CET 2016


Hi,

     Can you please open a ticket with the crash on github? Posting a 
backtrace would be nice.

Regards,
Ionut-Razan Ionita

On 01/14/2016 12:34 AM, Dragomir Haralambiev wrote:
> Hi Bogdan,
>
> Thanks for your replay.
>
> Here is email describe Radius problem in Opensips 2.1.
> ===============================================
> Hi Arsen,
>
>     If i completely understand the problem, the server doesn't provide 
> the deserved response. The problem in this case is that rc_send_server 
> function which is used by rc_acct function (which gives you the error) 
> uses a blocking socket and recvfrom blocks until it receives the 
> RADIUS message response. You can see the source code here [0] line 
> 224. Blocking causes  problems in scheduling other timers in opensips, 
> in your case tm and dialog timers, and that is the cause for your 
> warnings. So it is a drawback of the freeradius-client(or 
> radiusclient-ng) implementation. *We tried to solve this problem in 
> opensips 2.2 with **radius** async features[1]*.
>
> Regards,
> Ionut-Razvan Ionita
> =================================================
>
>
> Opensips 2.2 was crashed when make a call.
>
> It is normal to ask for support of the radius protocol.
>
> Best regards,
>
> Dragomir
>
> 2016-01-13 12:27 GMT+02:00 Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>:
>
>     Hi Dragomir,
>
>     What you mean ? All OpenSIPS versions do have the radius support;
>     starting with 2.2 we will have the async support for radius too.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>     On 12.01.2016 22:03, Dragomir Haralambiev wrote:
>>     Hi,
>>
>>     Which Opensips version will maintain Radius?
>>
>>     Best regards,
>>     Dragomir
>>
>>     2016-01-12 19:11 GMT+02:00 Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>>:
>>
>>         Hi all,
>>
>>         Here is the proposed planning for the next OpenSIPS releases :
>>
>>
>>         Minor releases
>>         ---------------
>>         Versions : OpenSIPS 1.11.6, OpenSIPS 2.1.2
>>         When : 14th of January 2016
>>         Activity: close important bug reports (if any to be considered)
>>
>>
>>         Major release
>>         --------------
>>         Version : OpenSIPS 2.2
>>         When : second half of March 2016
>>         Activities: development, wrapping up and testing
>>
>>
>>         Major release
>>         --------------
>>         Version : OpenSIPS 3.0
>>         When : end of January 2016 to start
>>         Activities: work on the new cfg file model.
>>
>>
>>         The work/activities for each release will be further detailed
>>         / discussed in separate threads.
>>
>>
>>         Best regards,
>>
>>         -- 
>>         Bogdan-Andrei Iancu
>>         OpenSIPS Founder and Developer
>>         http://www.opensips-solutions.com
>>
>>
>>         _______________________________________________
>>         Users mailing list
>>         Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160114/d553ec99/attachment.htm>


More information about the Users mailing list