Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Saul, On 02/11/2013 01:38 PM, Saúl Ibarra Corretgé wrote: So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) Indeed, this is already on the list, with fixes, improvements, etc 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. I have this RFC on my list to read and see exactly what needs to be done to fully support it - I will add it on the list 3. WebSocket transport We do support the websocket as protocol in SIP, but we do not do gatewaying ..So you refer to the translation from websocket to SIP ? As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. For the bugs, it will be really helpful if you would open tickets on SF tracker, with all the relevant information. It is an easy and centralized way to keep track of all reports ;) Best regards, Bogdan ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Saul, On 02/11/2013 05:38 PM, Saúl Ibarra Corretgé wrote: So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. 3. WebSocket transport As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. I can elaborate on any of the points in case there are any doubts :-) Oh, since I'm here, let me add one more thing: - Get rid of the lumps or add a way to apply all pending lumps to a message manually. This would fix a number of issues that can now happen, like using engage_mediaproxy and removing the SDP of a 183 response. I have on TODO list some fixup to deal with some cases (like adding a lump to a section that was removed) - this will solve most of the problems . We had a talk on that some time ago ;) - and I just added on the list. To apply changes in realtime will imply a tremendous work (to change in all modules), which I'm not so sure it will pay off. A really bad compromise will be a function to force the changes to be push, but IMHO this is a terrible hack and it will open Pandora's box for script writers. Regards, Bogdan ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Bobby, Thanks for the feedback, see my inline comments. On 02/11/2013 06:32 PM, Bobby Smith wrote: 1) TCP fixes (async/non-blocking) -- I know these are already on the list, but as we move more and more traffic to TCP on older versions, we are seeing reduced performance and odd deadlocks/socket problems from time to time yes, this is a bit of a painful matter and it will be addressed in the next release. 2) better support of RFC 6140 (the gruu fixes that saul mentioned come to mind) OK, if you also have examples of cases which do not work, please fill in some bug reports on SF tracker - it will help the developers in fixing things. 3) not really related to the release, but representation at SIPNOC this year would be pretty awesome. A lot of people from the standards bodies meet here (IETF), and seeing some pursuit around sipconnect 1.1/2.0 would be great for the community IMO as most of the people here offering competing choices are vendors selling black box products, however there is asterisk representation and everyone uses SER in one flavor on their networks :). Indeed, it will be interested and useful, and I would love to do it if we find fonds to support the participation to such an event...as OSS project, there is no much income to help with the participation to various events. Best regards, Bogdan On Mon, Feb 11, 2013 at 10:38 AM, Saúl Ibarra Corretgé s...@ag-projects.com mailto:s...@ag-projects.com wrote: On Feb 11, 2013, at 12:38 PM, Saúl Ibarra Corretgé wrote: Hi Bogdan and team, On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. 3. WebSocket transport As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. I can elaborate on any of the points in case there are any doubts :-) Oh, since I'm here, let me add one more thing: - Get rid of the lumps or add a way to apply all pending lumps to a message manually. This would fix a number of issues that can now happen, like using engage_mediaproxy and removing the SDP of a 183 response. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org mailto:Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Bogdan, I haven't really pushed floating point capability much because I've depended on external systems like mysql to do that math. However, with the popularity of NoSQL systems, I think this may become more important. It is to me at least :) Thanks for considering it :) -Brett On Mon, Feb 11, 2013 at 7:43 AM, Bogdan-Andrei Iancu bog...@opensips.orgwrote: Hi Brett, At some point we had on TODO list a function to do math ops with floats (stored as strings), but we have not felt a real demand for that - we can add it on the todo list. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Very excited about those! Would floating point math and floating point comparisons be possible? Also I know it's probably application specific but I feel like there is a whole lot of use for sorting functions. Thanks again, Brett -Brett On Feb 9, 2013, at 1:49 PM, Bogdan-Andrei Iancu bog...@opensips.org wrote: Hi Brett, All these are on the list already - Vlad is already working on a db2cachedb module which will automatically enable nosql support for all modules that already support sql. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02/09/2013 08:49 PM, Brett Nemeroff wrote: I'd like to see some more events added to modules. Specifically I'd really like events on dialog callbacks. Having more integration with NOSQL back ends for data stores would also be great. I'm pretty sure that's already in the works tho. Thanks for all your contributions!! -Brett -Brett On Feb 9, 2013, at 12:40 PM, Bogdan-Andrei Iancubog...@opensips.org wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Bogdan and team, On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. 3. WebSocket transport As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. I can elaborate on any of the points in case there are any doubts :-) Thanks for letting us fill-up your TODO list ;-) -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Brett, At some point we had on TODO list a function to do math ops with floats (stored as strings), but we have not felt a real demand for that - we can add it on the todo list. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02/10/2013 03:31 PM, Brett Nemeroff wrote: Very excited about those! Would floating point math and floating point comparisons be possible? Also I know it's probably application specific but I feel like there is a whole lot of use for sorting functions. Thanks again, Brett -Brett On Feb 9, 2013, at 1:49 PM, Bogdan-Andrei Iancubog...@opensips.org wrote: Hi Brett, All these are on the list already - Vlad is already working on a db2cachedb module which will automatically enable nosql support for all modules that already support sql. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02/09/2013 08:49 PM, Brett Nemeroff wrote: I'd like to see some more events added to modules. Specifically I'd really like events on dialog callbacks. Having more integration with NOSQL back ends for data stores would also be great. I'm pretty sure that's already in the works tho. Thanks for all your contributions!! -Brett -Brett On Feb 9, 2013, at 12:40 PM, Bogdan-Andrei Iancubog...@opensips.org wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
On Feb 11, 2013, at 12:38 PM, Saúl Ibarra Corretgé wrote: Hi Bogdan and team, On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. 3. WebSocket transport As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. I can elaborate on any of the points in case there are any doubts :-) Oh, since I'm here, let me add one more thing: - Get rid of the lumps or add a way to apply all pending lumps to a message manually. This would fix a number of issues that can now happen, like using engage_mediaproxy and removing the SDP of a 183 response. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
1) TCP fixes (async/non-blocking) -- I know these are already on the list, but as we move more and more traffic to TCP on older versions, we are seeing reduced performance and odd deadlocks/socket problems from time to time 2) better support of RFC 6140 (the gruu fixes that saul mentioned come to mind) 3) not really related to the release, but representation at SIPNOC this year would be pretty awesome. A lot of people from the standards bodies meet here (IETF), and seeing some pursuit around sipconnect 1.1/2.0 would be great for the community IMO as most of the people here offering competing choices are vendors selling black box products, however there is asterisk representation and everyone uses SER in one flavor on their networks :). On Mon, Feb 11, 2013 at 10:38 AM, Saúl Ibarra Corretgé s...@ag-projects.com wrote: On Feb 11, 2013, at 12:38 PM, Saúl Ibarra Corretgé wrote: Hi Bogdan and team, On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu wrote: Hi all, According the the release policy ( http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). You asked for it :-) Here are 3 big items I think we should have in OpenSIPS: 1. Non-blocking TCP operations (this is already on the list) 2. Outbound support (RFC5626) - supporting this may affect the design of point 1. 3. WebSocket transport As for bug fixes, there are a few that come to mind: 1. Proper routing of in-dialog messages when GRUU is used. (the dialog should remember the path and loose_route should route the message to the right place even if an AoR is found in the contact, which happens when GRUU is used. This is a problem if a user re-registers while on a call and she chooses a different inbound proxy, as the in-dialog requests would now follow a different path). 2. PUA module should refresh outgoing subscriptions until told otherwise 3. presence_xml should validate incoming PIDF documents (validate them against the schema, that is). Right now it doesn't, and if a client sends a broken document then the aggregated PIDF document will also be broken. Those broken docs should not be stored. I can elaborate on any of the points in case there are any doubts :-) Oh, since I'm here, let me add one more thing: - Get rid of the lumps or add a way to apply all pending lumps to a message manually. This would fix a number of issues that can now happen, like using engage_mediaproxy and removing the SDP of a 183 response. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
He, he, it seems the for the same problems we got to the same solutions. For some prepaid scenarios, we also needed to do floating operation and we ended up pushing them at DB level - but I still agree that a nice solutions will be to be able to do such ops from script level - as you pointed out you can not (1) relay all the time on DB and (2) put a noSQL DB to do such job. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02/11/2013 06:31 PM, Brett Nemeroff wrote: Bogdan, I haven't really pushed floating point capability much because I've depended on external systems like mysql to do that math. However, with the popularity of NoSQL systems, I think this may become more important. It is to me at least :) Thanks for considering it :) -Brett On Mon, Feb 11, 2013 at 7:43 AM, Bogdan-Andrei Iancu bog...@opensips.org mailto:bog...@opensips.org wrote: Hi Brett, At some point we had on TODO list a function to do math ops with floats (stored as strings), but we have not felt a real demand for that - we can add it on the todo list. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
Hi Brett, All these are on the list already - Vlad is already working on a db2cachedb module which will automatically enable nosql support for all modules that already support sql. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 02/09/2013 08:49 PM, Brett Nemeroff wrote: I'd like to see some more events added to modules. Specifically I'd really like events on dialog callbacks. Having more integration with NOSQL back ends for data stores would also be great. I'm pretty sure that's already in the works tho. Thanks for all your contributions!! -Brett -Brett On Feb 9, 2013, at 12:40 PM, Bogdan-Andrei Iancubog...@opensips.org wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [OpenSIPS-Users] [RELEASES] Drafting OpenSIPS 1.10.0 TODO list
I'd like to see some more events added to modules. Specifically I'd really like events on dialog callbacks. Having more integration with NOSQL back ends for data stores would also be great. I'm pretty sure that's already in the works tho. Thanks for all your contributions!! -Brett -Brett On Feb 9, 2013, at 12:40 PM, Bogdan-Andrei Iancu bog...@opensips.org wrote: Hi all, According the the release policy (http://www.opensips.org/Development/Development), I would like to call for a brainstorming, ideas, discussion, etc regarding what should be the roadmap for OpenSIPS 1.10 - more or less, what new goodies should be in 1.10 release (next major release). The page is already ready (http://www.opensips.org/Main/Ver1100) and pre-populated with the pending items from 1.9 release plus some items from my side . I would like to stat the discussion here, on the mailing list first, to get from all community ideas on what should be done in 1.10 - things to improve, supporting new RFC/drafts, new functionalitites, etc. So, please do not be shy and make your points here ;). Also we plan a second round of discussion / selection via an IRC meeting (probably in 2 weeks or so). Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com ___ Users mailing list us...@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
