sr-dev

sr-dev@lists.kamailio.org

8 participants
44520 discussions

git:sip-router: doc/NEWS: minor update
by Andrei Pelinescu-Onciul 16 Nov '08

16 Nov '08

Module: sip-router Branch: ser_core_cvs Commit: b5358fc9f8ae48b04c26c1f2e55988b782b48f33 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b5358fc… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Date: Sun Nov 16 18:29:06 2008 +0000 doc/NEWS: minor update - added missing sigio_rt poll method to tcp_poll_method --- NEWS | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 0b0d031..f9c0867 100644 --- a/NEWS +++ b/NEWS @@ -577,8 +577,8 @@ new config variables: tcp_connection_lifetime = value (s) - how long the lifetime of a tcp connection will be exteneded after an IO event (accept, connect, read, write). Default: 120 s. - tcp_poll_method = poll|select|epoll_et|epoll-lt|kqueue|devpoll - poll - method used (by default the best one for the current OS is selected) + tcp_poll_method = poll|select|sigio_rt|epoll_et|epoll-lt|kqueue|devpoll - + poll method used (by default the best one for the current OS is selected) tcp_max_connections = no. - maximum number of tcp connections (if the number is exceeded no new tcp connections will be accepted). Default: 2048.

1 0

git:test: added .gitignore
by Andrei Pelinescu-Onciul 16 Nov '08

16 Nov '08

Module: test Branch: master Commit: 078dc10293224d69cf567c42d7471ce09f8989aa URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/test/?a=commit;h=078dc10293224… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Date: Sun Nov 16 18:57:14 2008 +0100 added .gitignore - patterns for all the files that git should ignore (from *.o, *.d to config.mak, modules.lst a.s.o) --- .gitignore | 28 ++++++++++++++++++++++++++++ 1 files changed, 28 insertions(+), 0 deletions(-) diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..1a32c7e --- /dev/null +++ b/.gitignore @@ -0,0 +1,28 @@ +# ignore autogenerated files +cfg.tab.c +cfg.tab.h +lex.yy.c +librpath.lst +makecfg.lst +config.mak +modules.lst +# ignore dependency files +*.d +# ignore binary files and objects +ser +*.so +*.so.* +*.o +# archives +*.tar.gz +*.deb +*.rpm +# tags +tags +TAGS +# vi swaps +.*.swp +# various other binaries +test/udp_flood +utils/gen_ha1/gen_ha1 +utils/sercmd/sercmd

1 1

sip router meeting in Karlsruhe
by Daniel-Constantin Mierla 12 Nov '08

12 Nov '08

Hello, because of taking several days off, a complete report might show up a bit later, apologizes for that. Now a (short) summary... First, many thanks thanks to 1&1 for hosting the event and everyone that participated in such short notice. There were representatives from 10 companies: - 1&1 - FhG Fokus - Telio - Asipto - iptelorg/Tekelec - Voztelecom - Iptego - Itsyscom - Longphone - Basis AudioNet Some pictures should be published in the near future. After going in short introduction and presentation of the goals from the point of view of each project, we focused on: - identification of potential points of conflicts and how to get to a resolution in such case - code integration for common layer of the first phase - future development and proposals of new features - management of the larger eco-system that includes related projects and business entities I will send several emails detailing what was discussed and proposed there in few days. meanwhile, the outlines: - it is hard to avoid conflicts just by some clear and strict rules, so the common sense should lead the collaboration and discussions - GIT repository should be up in several days so the work can start, with a time line of 2-3 months from now to get core and tm in a very good shape of integration - another meeting shall be set in about 3 months time, to allow enough time for people to be able to attend, adjust the development and look more deep at the future. While the a lot of focus in the next months will be on integration, development of new features won't stop -- for examples, steps to a partial asynchronous processing are undertaking, couple of new modules are planned for release, several other modules to bring new functionalities - we should encourage and promote the development of related applications, like web interfaces, management tools, applications servers -- the add value for community and business Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

[OpenSIPS-Users] [Fwd: [Serdev] the sip router project]
by Adrian Georgescu 05 Nov '08

05 Nov '08

As Bogdan already revealed, our intentions is to produce a new design for the core that will address the scalability and security requirement in a completely different manner than the original project because with the passing of time the requirements of the customers of the original product have also changed. I believe that both projects will learn from each other and grow better by going their own separate ways. As an eco-system we have matured enough in the last five years to be able to learn from and admit about our own mistakes in the past and look now at a better future. Regards, Adrian 5 nov 2008 kl. 11.41 skrev Bogdan-Andrei Iancu: > After 7 year of SER/OpenSER I (and many other) got to simplest > conclusion that the current design is not able to sustain the progress > of SER / OpenSER (like scripting, async calls, integration, scaling, > etc) ? Mainly because SER was design 7 years ago when there was only > stateless processing, no TCP, etc.... > > And I personally do not see any future in keep trying to patch the > existing design as it has no future Bogdan, Thanks for the good insight in why you don't want to join the effort, but go your own way. If you have different ideas for the core than what you understand from the other teams, then there's no reason for you to join the effort. I did not realize that was the case, now I do understand you better. > nature invented forking for seeking new alternatives! A good way of expressing it :-) At the same time, there's something to be said for the old, solid and good non-forked original product... Abba is still more enjoyable than all the forks... Ha ha! Cheers, /O

1 0

Re: [SR-Dev] [OpenSIPS-Users] [Fwd: [Serdev] the sip router project]
by Johansson Olle E 05 Nov '08

05 Nov '08

5 nov 2008 kl. 11.41 skrev Bogdan-Andrei Iancu: > After 7 year of SER/OpenSER I (and many other) got to simplest > conclusion that the current design is not able to sustain the progress > of SER / OpenSER (like scripting, async calls, integration, scaling, > etc) ? Mainly because SER was design 7 years ago when there was only > stateless processing, no TCP, etc.... > > And I personally do not see any future in keep trying to patch the > existing design as it has no future Bogdan, Thanks for the good insight in why you don't want to join the effort, but go your own way. If you have different ideas for the core than what you understand from the other teams, then there's no reason for you to join the effort. I did not realize that was the case, now I do understand you better. > nature invented forking for seeking new alternatives! A good way of expressing it :-) At the same time, there's something to be said for the old, solid and good non-forked original product... Abba is still more enjoyable than all the forks... Ha ha! Cheers, /O

1 0

Re: [SR-Dev] [OpenSIPS-Users] [Fwd: [Serdev] the sip router project]
by jh＠tutpro.com 05 Nov '08

05 Nov '08

Bogdan-Andrei Iancu writes: > Have you ever consider a fork as an option driven by technical needs?? > Like to do something totally different than you have and than the other > people want to do. > > After 7 year of SER/OpenSER I (and many other) got to simplest > conclusion that the current design is not able to sustain the progress > of SER / OpenSER (like scripting, async calls, integration, scaling, > etc) ? Mainly because SER was design 7 years ago when there was only > stateless processing, no TCP, etc.... bogdan, the above makes sense, but i have never been able to figure out why you could not implement the new designs as part of openser project that you yourself started. if it was due to people, that may happen any time again (unless you work alone) and has nothing to do with technical needs. -- juha

1 0

the sip router project
by Daniel-Constantin Mierla 05 Nov '08

05 Nov '08

Hello Everybody, We are pleased to announce to you the SIP Router project. It aims to build a solid open source SIP routing platform, based on collaboration of the SIP Express Router (SER) and Kamailio (OpenSER) teams. Developers of these two projects believe that an united and non-conflicting environment will bring many benefits to them, community members and companies: * bring together the developers and user communities of both projects * reduce maintenance overhead * avoid duplicated efforts in development * develop a core framework that is flexible, extensible and scalable * promote and build a solid open source SIP server project * ensure business credibility * make future forking undesirable, this harms everybody, affects credibility and business You are welcome to join! Visit the web site at: http://sip-router.org There is a meeting in Karlsruhe, Germany, on Nov 10, 2008, hosted by 1&1, where the developers and community members have the chance to discuss and tune the last aspects of the new project. We are looking to see many of you there: http://sip-router.org/index.php/meeting/ We hope this is a great news for you, thanks to the effort of main developers and management teams of the two projects. We invite you to join the new mailing list for further discussions: http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev Daniel, Jiri Kamailio Management Team SER Management Team

10 10

Re: [SR-Dev] [OpenSIPS-Users] [Fwd: [Serdev] the sip router project]
by Adrian Georgescu 04 Nov '08

04 Nov '08

Hello Jiri, For myself and Bogdan things are pretty clear. We both have companies that closely depend on the success of the project and we have contracts with customers to which we deliver. There is no doubt about who we are, what we do, what is our motivation and driving factor. Clarity is something customers need to have for the sake of their current and future investments. It is pretty unclear at this stage how the new project will shape up. Merging and forking can lead to inimaginable places as we have seen before several times and is nothing bad in the end as long as the eco- system keeps going and the customers invest further in it, which happend a lot in the last four years. The real customers are the ones that can decide upon the best solution for their own interests and we shall let them express their choice once they have enough information and measurements. Regards, Adrian On Nov 4, 2008, at 2:46 PM, Jiri Kuthan wrote: > Folks, > > while there is not yet such a remarkable progress to be shared with > those > I have chosen to talk to on the opensips side, the invitation is of > course > very open to anyone with sincere interest in unforking. > > -jiri > > --- > Hello Everybody, > > We are pleased to announce to you the SIP Router project. > > It aims to build a solid open source SIP routing platform, based on > collaboration of the SIP Express Router (SER) and Kamailio (OpenSER) > teams. > > Developers of these two projects believe that an united and > non-conflicting environment will bring many benefits to them, > community > members and companies: > > * bring together the developers and user communities of both > projects > * reduce maintenance overhead > * avoid duplicated efforts in development > * develop a core framework that is flexible, extensible and > scalable > * promote and build a solid open source SIP server project > * ensure business credibility > * make future forking undesirable, this harms everybody, affects > credibility and business > > You are welcome to join! Visit the web site at: > > http://sip-router.org > > There is a meeting in Karlsruhe, Germany, on Nov 10, 2008, hosted by > 1&1, where the developers and community members have the chance to > discuss and tune the last aspects of the new project. We are looking > to > see many of you there: > http://sip-router.org/index.php/meeting/ > > We hope this is a great news for you, thanks to the effort of main > developers and management teams of the two projects. We invite you to > join the new mailing list for further discussions: > > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev > > Daniel, Jiri > Kamailio Management Team > SER Management Team > > > > _______________________________________________ > Users mailing list > Users(a)lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users

4 3

Re: [SR-Dev] [Kamailio-Users] the sip router project
by Johansson Olle E 04 Nov '08

04 Nov '08

4 nov 2008 kl. 16.24 skrev Bogdan-Andrei Iancu: > Hi Olle, > > Thank you for your thoughts. On a first view, it looks interesting, > but I'm missing some points here (important points): > > 1) as OpenSER was forked from SER because different views (and the > OpenSER view proved to be a very popular and successful one), I > wonder why, Kamilio is getting back to SER? not sharing any more the > OpenSER view as claimed? because such merging will definitely have a > great impact on the dynamical and openness of the projects (like > releases, contributions, driving the project) > > 2) this major change of perspective (at least for kamilio) was a > backstage decision, kept secret from the community - shouldn't be in > the interest of the community to say if going back to the roots > (merging into SER) is something wanted or not? it somehow > contradicts the self existence of OpenSER, right? > > 3) the benefits you mentions are mainly optimization of the internal > project activities and not optimizations of the outcome - what the > project will deliver. And I guess this is the most important. We > already went though the experience of large devel community, > frameworks, etc but with no outcome for more than 2 years... > >> From my personal perspective, the new project looks more like SER >> absorbing Kamilio (considering the sizes, the companies behind each > project, the resources, and the man-power behind each project). > > And at the moment I would like preserve the OpenSER vision and to > have an open source project (a standalone one), far away from the > "control" of any Big Brother ;) Bogdan, Thanks for your feedback, which clearly indicates where you stand today. We will have to see what the community says, but so far, I've only seen cheers and applauds. How this will work out in the future is something no one really can guess at this point. The more people that joins this effort and forms it, the better. The time to make it right is now, by working together and aligning the codebases as described, then working towards the future with new releases. We'll see if the combined forces can produce any deliverys or not. Today, we can only hope and guess. I think it's a great starting point that they have started talking, and agreed to work together on some parts. To me, it seems to be room for two final products stil, sharing the same core. One Kamailio and one SER. After the developer meetings, I think it's time to call for a joint community meeting to have people active in the community - not only developers - in the same room, discussing benefits of working together. I don't want to argue your standpoint, just hope that you will follow the progress and see if there's some benefits for OpenSIPS to join at some stage. Regardless, the GPL license allows you to benefit from the work as always. I might be naive, but I do have a positive feeling about this :-) /O

3 2

Welcome!
by Daniel-Constantin Mierla 03 Nov '08

03 Nov '08

Welcome to The SIP Router Project! Enjoy! http://www.sip-router.org

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev