How cool is that!  Thanks a lot, Laurent.  I'll try to have this tested
by tomorrow.

________________________________________________________________________

Basil Mohamed Gohar
[EMAIL PROTECTED]
www.basilgohar.com




On Mon, 2008-12-01 at 21:30 +0100, Tarrisse Laurent wrote:

> http://www.mbdsys.com/QuteCom/QuteCom-2.2-setup-release-339b18725d8e.exe
> 
> With speex 8000/ speex 16000/ ilbc with dynamic ptime (thanks Mauro)
> 
> 
> NOTE: now ilbc codec is a phapi plugin
> 
> Laurent
> 
> ----- Original Message ----- 
> From: "Basil Mohamed Gohar" <[EMAIL PROTECTED]>
> To: "Tarrisse Laurent" <[EMAIL PROTECTED]>
> Sent: Monday, December 01, 2008 5:30 PM
> Subject: Re: Speex codec & Freeswitch server
> 
> 
> > Laurent,
> >
> > Thanks for such an informative reply!  I really appreciate it!
> >
> > Unfortunately, I do not have a Visual Studio installation, nor am I a
> > Windows developer (I'm actually "just" a PHP web developer).  So, I
> > cannot at this time make my own build on Windows, but I'd be happy to
> > test one out if someone is kind enough to provide one.  ;)
> >
> > ________________________________________________________________________
> >
> > Basil Mohamed Gohar
> > [EMAIL PROTECTED]
> > www.basilgohar.com
> >
> >
> >
> >
> > On Mon, 2008-12-01 at 16:17 +0100, Tarrisse Laurent wrote:
> >> Hello Basil Mohamed Gohar,
> >>
> >> -Speex:
> >>     There are 3 bugs with speex codec
> >>         1/ if you debug qutecom with visual .net it will not handle
> >> correctly the plugin path
> >>         2/speex/8000 is not in the config.xml
> >>         3/speex/1600 payload is replaced by g726-64wb/1600 payload
> >>
> >>     => solution:
> >>         -Update your source (i've just commited a fix).
> >>         -build
> >>         -Copy wengophone/resources/config/config.xml to
> >> build/{BUILD_TYPE}/{BUILD_TYPE}/config/
> >>
> >> -ILBC:
> >> change PHAPI_CODEC_ILBC_SUPPORT in DefineWengoOptions.cmake to ON
> >>
> >> NOTE: like ILBC i've added an option to switch AMR codec in
> >> DefineWengoOptions.cmake, by default the value is OFF (no GPL licence)
> >>
> >>
> >> Laurent
> >>
> >> ----- Original Message ----- 
> >> From: "Basil Mohamed Gohar" <[EMAIL PROTECTED]>
> >> To: "Qutecom-dev" <[EMAIL PROTECTED]>
> >> Sent: Monday, December 01, 2008 1:52 PM
> >> Subject: Speex codec & Freeswitch server
> >>
> >>
> >> > Hey all!  I just got QuteCom to work on my laptop under Windows after
> >> > debugging a crash condition that I couldn't get around - turns out I 
> >> > had
> >> > to delete my old wengo profile directory.  After that, it started
> >> > without any problem.
> >> >
> >> > But the issue I wanted to inquire about is regarding using Speex via
> >> > Freeswitch trunk (going to be the 1.02 release).  I able to use Speex
> >> > with Twinkle (under GNU/Linux) as well as Ekiga 3.02 beta (under
> >> > Windows), but I was unable to connect to Freeswitch when using Speex as
> >> > the server's primary codec with QuteCom 2.2 (a recent build).  Other
> >> > codecs like GSM & G.711, etc., worked fine, just not Speex.
> >> >
> >> > I also noticed that iLBC doesn't seem to be amongst the choices for
> >> > using QuteCom.  Other VOIP clients seem to support it as a
> >> > lowest-common-denominator codec, and it's great for ultra-low bandwidth
> >> > connections (like mine, currently, which is capped at 64kb/s up/down).
> >> > On such connections, unfortunately even G.711 won't work because the
> >> > network overhead will take up data that could otherwise be used for
> >> > communication.
> >> >
> >> > Anyway, any tips on what I can do to get it to work, or what other
> >> > information you might need to help me find a solution?  Thanks!
> >> >
> >> > Great work as always, guys!
> >> >
> >> > ________________________________________________________________________
> >> >
> >> > Basil Mohamed Gohar
> >> > [EMAIL PROTECTED]
> >> > www.basilgohar.com
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > QuteCom-dev mailing list
> >> > [email protected]
> >> > http://lists.qutecom.org/mailman/listinfo/qutecom-dev
> >> >
> >>
> > 
> 
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to