I hope everything is OK on your side.
I'd like to reiterate that Google Summer of Code 2009 has entered the
community bonding period and to ask you once again to contact me (by
e-mail or chat).
Just for the record and not asking for an apology, I'm not in favor of
sign-of-life requests coming from me not getting answered in three
As to the projects at hand, I'd like to start clearing out the
following with respect to the G.729 support:
- Integrating Mobicents source code into SIP Communicator seems
unacceptable to me at the moment because of license incompatibility -
GPL for Mobicents and LGPL for SIP Communicator. I saw the "G729 GPL
or LGPL?" thread you started at
but I couldn't quite figure the final situation there so I need
further clarification from you.
- We also need a research on the available codec implementations other
than Mobicents that we can possibly use. Even if the licensing of the
Mobicents G.729 source code suits SIP Communicator, we still want to
know why we chose them, how the characteristics of the implementations
(for example, stability and performance) compare.
- We want the delivered codec to work with JMF because SIP
Communicator uses it at the moment. FMJ support is also required but
JMF is a definitive must.
On Wed, Apr 22, 2009 at 1:15 PM, Lubomir Marinov <firstname.lastname@example.org> wrote:
I'm pleased to "meet" you and have the chance to work with you as part
of Google Summer of Code 2009 on such interesting projects as DTMF and
G.729. I hope we'll be successful in our undertaking.
DTMF with RTP should be enjoyable even only because I have previous
experience with the telephony-related architecture functionality of
When it comes to G.729, I'm relatively confident we're set to be
successful at adding support for it. Mostly, there are clearly
existing implementations we can take inspiration from. Moreover, I was
honored to work with Damian Minkov on putting the finishing touches to
the H.264 codec in SIP Communicator and I thus feel comfortable with
the idea that we have the necessary knowledge as a community how to
achieve our goal.
As there are two projects in front of us and though I can see in your
application that you're busy, I'm eager to start our community bonding
period. I'd like us to agree not only on the general timeline that
you've provided in your application but also on a more fine-grained
workflow including what updates we'll be echanging throughout the
working period, when and where we're going to "meet" for them, what
intermediate deliverables I'll get and how they will be continually
integrated in the SIP Communicator source tree. Thus I invite you to
please contact me for a live chat over IRC in the #sip-communicator
channel at irc.freenode.net where I use the nickname lubomir_m or over
Google Talk. I can of course always be reached with a private message
to my e-mail.
Best of luck,
On Tue, Apr 21, 2009 at 11:35 PM, romain philibert > <email@example.com> wrote:
I am very glad to be part of Sip-Communicator.
Let's present myself :
I am a french student from Insa Lyon Telecommunication department.
I've studied Java, VoIP technologies and Signal Processing during my
courses. This project is a very good opportunity for me to put all that
During this summer I will work on two projects :
- G729 Implementation. (integrate Mobicents Codec in FMJ)
- DTMF over RTP (FMJ too)
I know that it will be hard, but I will do my best to succeed those two
As you saw, I will work with FMJ (or Sun JMF if no choice) API. If you
previously worked with those API, I would appreciate any advices
It will be the first time I'll code for an Open Source organization. I am
new to IRC too, bit I will make an effort to stay connected ^^
Anyway, you can always send me e-mails.
I hope we will have fun during summer together ^^
Thank you Google and Sip-Communicator
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com