Module: sip-router
Branch: master
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.
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.
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
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
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
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
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