Hi Jaro: I am interested in your wxCommuncator. I have tried wxCommunicator-1.0.1 binary release days ago, realy good! I am thinking about re-writing my-ez-phone currently developed by Borland Delphi based on sipXezphone. So I will spent some time in analyzing WxCommuncator. I've built sipxtapi_Experimental_r26 project, I removed HAVE_SPEEX and HAVE_ILBC (I could not find ILBC lib source files) pre-compiled selections and then at last I've got the sipXtapi.dll. Further testing of WxCommnunicator is being made. By the way, I would stop asking questions about SOUND CRASH from now on untill I find something valuable. I will not stop analyzing it and it really happens under certain circumstances. So issue really do exist, yet I have not found someone could completely and clearly explained it. Anyway thanks to you and thanks to Logan. Best Regards Feng XueSong Jaro wrote: ============================================================= logan wrote: > > Hello, > > Yes, I have tested it many times. And with different vocoders as well > (you can also try with speex, ILBC, etc). You said wxCommunicator worked > well, so why don't you try Jaro's experimental sipXtapi branch. He has > also provided prebuilt binaries of sipXtapi on sourceforge. >
I have time now so I will try to finish it. I wouldn't recommend using sipxEzPhone for testing, it's too basic and forgets configuration. WxCommunicator is difficult to compile, but once you do it its very useful. Jaro
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
