Hi Daniel-Constantin,
I'm sorry that you feel offended by my summary.
My summary you just commented on, as well as the perspectives found in
the Getting Started document are attempts at presenting gathered experience
and understanding to the benefit of new users and the community in general.
You guys, the developers, will always be closer to where things happen, and
the rest of us try to keep up with what happens. On the other hand, being on
the outside as mere users we sometimes see things differently than
iptelorg.com and voice system and other developers.
So, thanks for your feedback and I look forward to your continued
corrections in the future (note: not intended ironic, even though it may
sound like it).
See below for my comments and questions for further clarifications.
Daniel-Constantin Mierla wrote:
Just to point the proper information where is the case
...
On 09/13/05 10:59, Greger V. Teigre wrote:
AFAIK, Tekelec bought
iptelorg.com with its
intellectual property
(commercial extensions/extras/related software to SER) and its
employees.
Iptel.org was NOT part of the deal and is still sponsored
by FOKUS Fraunhofer (as stated on the
iptel.org website). SER is an
independent GPL project and Tekelec cannot do anything about that.
However,
iptelorg.com sponsored development resources on the open
source SER. Tekelec is free to decide to stop this sponsoring. I
cannot see how this can be in their interest, but if the focus on the
development they want to do with SER is too far away the open source
project, the project may not give Tekelec enough value. If this
happens, the developers must decide whether to continue in their
spare time, quit SER development, or look for employment with another
company willing to sponsor hours on open source SER development. In
addition, SER has MANY other developers who were not involved at all
with
iptelorg.com. Of course, as some of the most active coders were
with
iptelorg.com, such a decision may impact SER's development.
Also, note that the OpenSER project has branched off and is hosted
and controlled by Voice System.
this is not true, see the management board and you can make a simple
computation to see if Voice System controls openser
(
http://openser.org/management.php). I do not want to open any other
flame of war, but let's try to tell the truth.
Excellent! I was not aware of that. With limited time I cannot follow
everything (and yes, I don't follow openser lists, sorry about that), I see
I'm about two weeks behind the news :-) Adrian, Juha, and Klaus are
excellent folks with lots of experience. However, again from an outsider's
perspective: The core developers are Voice System only and even though I
agree that "controls" is not the right word, I would still insist that Voice
System has a pretty heavy influence on openser. As my post was related to
Tekelec, I would also say that in this context such control is part of the
safety that users can feel in openser not being affected by the acquisition.
BTW, the openser site still states that the project is managed by Voice
System developers:
http://openser.org/about.php
You may want to change that ;-)
The Voice
System developers are not affected by the Tekelec deal.
However, as OpenSER tries to incorporate SER code development into
its own code base, OpenSER will be equally affected if those
contributing this SER code are prevented from working on the code in
their day-time job.
I am pretty sure that you talked with people from the management board
of openser and this is the answer you got, or?!?! Am I wrong? The
truth is something else, openser development was not (and is not
going to be) affected by any
iptelorg.com/tekelec deal.
And that's exactly what I state. Except that since openser has a published
policy to stay compatible with ser (ex. the openser faq and from the
discussion after the creation of openser). This implies that ser development
will be merged into openser (I have also seen that you actually do this, ex.
the ser experimental modules), which again means that openser will be
affected by reduced ser development. I agree that this can be misunderstood.
I will correct the error regarding management and be a bit clearer on this
issue and re-post.
See the list
of new features and bug fixes present now in openser. Also, I am sure
that you did some statistics to see how much code different companies
have sponsored/contributed to ser and you base your conclusions on
that (just look after copyright).
No, I haven't and I don't really care who contributed what. That was not the
point either. Who contributed what in GPL ser/openser is hardly relevant to
the Tekelec acquisition of
iptelorg.com. I think you guys do a great job
developing new features, I would love to get access to those. I just wish
they would be part of an early-and-often release system in one, single
project where today's ser could be the stable release and openser the
early-and-often releases. As it is today,
onsip.org had to stay with ser
only (we are over-worked already maintaining and developing new issues, and
choosing ser makes sense due to the better compatibility over to openser).
So, Daniel, you accuse me of not telling the truth and mock me for not being
updated or doing analysis on code.
ONsip.org and the
ONsip.org volunteers
do contribute a lot to getting people up and running on ser and openser. I
am sure both projects benefits a great from this in increased community and
more knowledgable users.
I invite you or other openser guys to keep a continued dialog directly
with one of us instead of through such public corrections. Thus you can make
sure that we don't make uninformed conclusions.
And BTW, if you want to help out in maintaining configuration files that
are more adapted to openser (where there are openser "ways of doing
things"), you are very welcome to contribute to the on-going
ONsip.org
effort.
Regards,
Greger
>
>
> g-)
>
> carlos ivan grajales wrote:
>
>> Hi Guys,
>>
>> And now what Tekelec bought to iptelorg that it will
>> be of SER??? your users list??? and GPL software ???
>>
>> Sincerely,
>>
>> CArlos Ivan Grajales M.
>> Colombia, South America
>>
>>
>>
>> --- serusers-request(a)lists.iptel.org wrote:
>>
>>> Send Serusers mailing list submissions to
>>> serusers(a)lists.iptel.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web,
>>> visit
>>>
http://lists.iptel.org/mailman/listinfo/serusers
>>> or, via email, send a message with subject or body
>>> 'help' to
>>> serusers-request(a)lists.iptel.org
>>>
>>> You can reach the person managing the list at
>>> serusers-owner(a)lists.iptel.org
>>>
>>> When replying, please edit your Subject line so it
>>> is more specific
>>> than "Re: Contents of Serusers digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>> 1. I cannot compile "check_from()" method
>>> although I load module
>>> "uri" (tulay sazak)
>>> 2. Compilation Error on Mac OS (Darwin) - SEMS..
>>> (Amos Nungu)
>>> 3. call me (harry gaillac)
>>> 4. SER + Mediaproxy sl_send_reply: I won't send a
>>> reply for
>>> ACK!! (GT)
>>> 5. HELP! duplicate accounting (torres lloyd)
>>> 6. Re: SER + Mediaproxy sl_send_reply: I won't
>>> send a reply for
>>> ACK!! (Greger V. Teigre)
>>> 7. Re: Re: SER + Mediaproxy sl_send_reply: I
>>> won't send a reply
>>> for ACK!! (GT)
>>> 8. Re: t_check_status in failure_route (Klaus
>>> Darilion)
>>> 9. Media proxy idle calls. (Vikash Khatuwala)
>>> 10. Re: t_check_status in failure_route (Juha
>>> Heinanen)
>>> 11. Re: t_check_status in failure_route (Andreas
>>> Granig)
>>>
>>>
>>>
>> ----------------------------------------------------------------------
>>
>>>
>>> Message: 1
>>> Date: Sun, 11 Sep 2005 04:12:08 -0700 (PDT)
>>> From: tulay sazak <tulaysazak(a)yahoo.com>
>>> Subject: [Serusers] I cannot compile "check_from()"
>>> method although I
>>> load module "uri"
>>> To: serusers(a)lists.iptel.org
>>> Message-ID:
>>> <20050911111208.51148.qmail(a)web52108.mail.yahoo.com>
>>> Content-Type: text/plain; charset=iso-8859-1
>>>
>>> Hello everbody,
>>>
>>> I loaded module "uri" and my ser.cfg is as below:
>>>
>>> .....
>>> loadmodule "/usr/local/lib/ser/modules/uri.so"
>>> .....
>>> if (method=="INVITE") {
>>> if (!radius_proxy_authorize("iptel.org")) {
>>> proxy_challenge("iptel.org", "1");
>>> break;
>>> }
>>>
>>> if (!check_from()) {
>>> sl_send_reply("403", "Forbidden");
>>> break;
>>> }
>>> }
>>> ........
>>>
>>> When I run ser, it says:
>>>
>>> 0(10457) find_export: <check_from> not found
>>> 0(10457) find_export: <check_from> not found
>>> 0(10457) parse error (183,35-36): unknown command,
>>> missing loadmodule?
>>>
>>> Can you see what am I doing wrong ??
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> Tulay
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> ______________________________________________________
>>
>>>
>>> Yahoo! for Good
>>> Watch the Hurricane Katrina Shelter From The Storm
>>> concert
>>>
http://advision.webevents.yahoo.com/shelter
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Sun, 11 Sep 2005 15:05:54 +0200
>>> From: Amos Nungu <amos.nungu(a)gmail.com>
>>> Subject: [Serusers] Compilation Error on Mac OS
>>> (Darwin) - SEMS..
>>> To: serusers(a)lists.iptel.org
>>> Message-ID:
>>> <86caff8805091106053263560b(a)mail.gmail.com>
>>> Content-Type: text/plain; charset=ISO-8859-1
>>>
>>> I'm installing SEMS-0.9 on Mac OS (Darwin 8.2.0).
>>> upon running the make
>>> all command, I got an error as shown below
>>> -------------------------------------------------
>>> # make all
>>> make[1]: Nothing to be done for `deps'.
>>> g++ -o sems AmApi.o AmAudio.o AmCmd.o AmConfig.o
>>> AmEventQueue.o
>>> AmIcmpWatcher.o AmMail.o AmPlugIn.o AmRequest.o
>>> AmRtpPacket.o
>>> AmRtpPacketTracer.o AmRtpScheduler.o AmRtpStream.o
>>> AmSdp.o AmServer.o
>>> AmSession.o AmSmtpClient.o AmThread.o AmUtils.o
>>> EmailTemplate.o
>>> SemsConfiguration.o SerClient.o SerDBQuery.o log.o
>>> sems.o -lm -ldl
>>> -lsocket -lnsl -lpthread
>>> /usr/bin/ld: can't locate file for: -lsocket
>>> collect2: ld returned 1 exit status
>>> make[1]: *** [sems] Error 1
>>> make: [all] Error 2 (ignored)
>>>
>> -------------------------------------------------------
>>
>>>
>>> Any idea on how to go about it will be great.
>>>
>>> Regards
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Sun, 11 Sep 2005 19:19:03 +0200 (CEST)
>>> From: harry gaillac <gaillacharry(a)yahoo.fr>
>>> Subject: [Serusers] call me
>>> To: serusers(a)lists.iptel.org
>>> Message-ID:
>>>
>> <20050911171904.17161.qmail(a)web25502.mail.ukl.yahoo.com>
>>
>>> Content-Type: text/plain; charset=iso-8859-1
>>>
>>> hello,
>>>
>>> Please to call me at for tests.
>>>
>>> sip:84@nxs;yi.org
>>> or
>>> sip:85@nxs;yi.org
>>> or
>>> sip:86@nxs;yi.org
>>> or
>>> sip:87@nxs;yi.org
>>>
>>> Regards
>>> Harry
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> ___________________________________________________________________________
>>
>>
>>>
>>> Appel audio GRATUIT partout dans le monde avec le
>>> nouveau Yahoo! Messenger
>>> Téléchargez cette version sur
>>>
http://fr.messenger.yahoo.com
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 4
>>> Date: Sun, 11 Sep 2005 20:11:26 -0800
>>> From: "GT" <geotelcom(a)yahoo.fr>
>>> Subject: [Serusers] SER + Mediaproxy sl_send_reply:
>>> I won't send a
>>> reply for ACK!!
>>> To: serusers(a)lists.iptel.org <serusers(a)lists.iptel.org>
>>> Message-ID: <20050911181312.D169319C6(a)fox.iptel.org>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>>
>>> Hello,
>>>
>> === message truncated ===
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>>
http://mail.yahoo.com
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers(a)lists.iptel.org
>>
http://lists.iptel.org/mailman/listinfo/serusers
>
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
>
http://lists.iptel.org/mailman/listinfo/serusers