On 03/23/2010 01:23 AM, Fraser Redmond wrote:
Emil, can you just clarify: If we have our pool of licenses set up on the server, is it then just a matter of enabling g729 in the code? (Or are additional licenses needed on the client somehow?)
Cheers, Fraser The conditions for G.729 patent licencing say each point in the chain which transcodes must be licenced. You need a licence for the client and a licence for the server, unless the server is operating in pass-through mode. Licences are not transferrable. You can't buy, say, a licence for the Freeswitch G.729 codec, but actually run a copy of the Java code from SIP Communicator. The products must be individually licenced. Those are the rules set by the licencing pool.
On Sun, Mar 21, 2010 at 10:05 AM, Emil Ivov <emcho@sip-communicator.org <mailto:emcho@sip-communicator.org>> wrote:
Yes we do have it, and it was implemented as a part of our participation in GSoC 2009. People can use it perfectly legally as long as they buy the corresponding licenses (just as with any other client).
Currently use of the codec is disabled by default and whoever needs it has to enable it in the code, after acquiring the necessary license.
Cheers, Emil
> > /b > > On Mar 20, 2010, at 8:24 AM, Raffaele P. Guidi wrote: > >> I believe sip communicator does handle g729. It has a strong >> community and a plugin model (based on osgi) that makes it easily >> (ok, kinda...) customizable. Of course the >> FSComm/givesomemoneytotheproject option is the best one. In any >> case: http://sip-communicator.org/ >> >> Ciao, R
Steve