zamielia wrote: > Hello, > I've been referring to few version of sipxtapi.h. I did find > sipxAudioEnableAEC(g_hInst,true) in my sipxtapi.h but the > line was commented. So i uncommented and used it. As a > result, i got the error i mentioned in previous posting. > > Hehe don't do such things. I was tempted to use __sipxEventListenerAdd (internal function of sipxtapi) instead of sipxEventListenerAdd because it bypasses aditional OsServerTask which is not necessary in my case but then I thought what if somebody changes the behaviour or name so I use sipxEventListenerAdd.
btw could someone fix documentation in sipxtapievents.h for typedef bool (SIPX_CALLING_CONVENTION *SIPX_EVENT_CALLBACK_PROC) SIPX_EVENT_CATEGORY category, ? It states you should post event to another thread if you need to do heavy processing, which is not true, this is aleady done by sipxtapi by having sipxeventdispatcher which is an OsServerTask (thread with message loop). Sipxtapi posts events to this task and this task from the context of its thread calls the callback. So when your callback gets called you can take as much time as you need, you are in fact in the OsServerTask thread and you will not block your main aplication thread. This should be highlighted, so that you take note you are in another thread and should not access your variables or GUI unless you have proper locking. You need to post this event only if you need to get to your main application thread. > I search for sipxAudioSetAECMode() that u mentioned. I found > and used it inside my coding. But i got > "Entry Point Not Found : The procedure entry point > sipxAudioSetAECMode could not be located in the dynamic link > library sipXtapid.dll." > > As for now, i'm linking to sipXtapi.dll to run my softphone > program. If I were to refer other versions of dll, my > program would produce different kind of errors. > What is the difference of refering to sipxtapi.dll and > sipxtapid.dll? > > The *d version usually contains debugging symbols. If you get a crash and have corresponding source code, you can inspect the code where it crashed whereas if you use release version you are lost if something doesn't work. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
