Hello, Yes i've added it recently. (just after your first mail!) Amr, speex and ilbc plugins will be put in phapi-plugins directory
Note : due to license restriction, i don't think we can redistribute ilbc with the installer. Laurent ----- Original Message ----- From: "Basil Mohamed Gohar" <[EMAIL PROTECTED]> To: "qutecom-dev" <[email protected]> Sent: Friday, December 05, 2008 10:06 PM Subject: Re: Speex codec & Freeswitch server >I also went back and installed the RC2 package and found no > phapi-plugins directory there, either - I'm not sure if it was supposed > to have one or if you meant that you just added that recently. > > ________________________________________________________________________ > > > Basil Mohamed Gohar > [EMAIL PROTECTED] > www.basilgohar.com > > > > > > On Tue, 2008-12-02 at 21:47 +0200, Basil Mohamed Gohar wrote: >> Laurent, >> >> I did not find a phapi-plugins directory in my QuteCom installation >> folder. I have: >> * chat >> * config >> * css >> * imageformats >> * lang >> * pics >> * sounds >> * webpages >> >> >> ______________________________________________________________________ >> >> >> >> Basil Mohamed Gohar >> [EMAIL PROTECTED] >> www.basilgohar.com >> >> >> >> >> >> >> On Tue, 2008-12-02 at 17:59 +0100, Tarrisse Laurent wrote: >> > >> > Hello, >> > >> > Thanks for your comment. >> > I think it is an installer problem : Do you have a phapi-plugins/ >> > directory in c:\Program Files\QuteCom ? >> > >> > Laurent >> > ----- Original Message ----- >> > From: Basil Mohamed Gohar >> > To: qutecom-dev >> > Sent: Tuesday, December 02, 2008 5:33 PM >> > Subject: Re: Speex codec & Freeswitch server >> > >> > >> > Once again, thanks for taking care of this for me, Laurent. >> > One problem, though, is that I am still having the same >> > problem with Speex, and I couldn't get iLBC to work. Is >> > this because of the config.xml? I deleted all my old >> > QuteCom settings, but that still didn't work. If it is >> > indeed related to config.xml, from where can I get one that >> > has these codecs enabled, or how can I edit it myself to >> > enable them? >> > >> > Thanks in advance! >> > >> > ____________________________________________________________ >> > >> > >> > >> > >> > 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 >> _______________________________________________ >> 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 > _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
