Alexey Trizno wrote: > Hello! > > Sometimes after CALLSTATE_CAUSE_TRANSFER_SUCCESS I does not receive > CALLSTATE_DESTROYED for tranfered call (but CALLSTATE_DISCONNECTED received > successfully, and sipxCallDestroy called in CALLSTATE_DISCONNECTED event > handler). > > May be this is known problem? >
Hi I think it is a waste of time to investigate this in current sipxtapi, since I have finished a refactored version with many bugs fixed and many internal changes. I managed to test a few things yesterday and fixed some minor bugs that I introduced, but most functions are untested. what is tested: + sipxtapi init/uninit + audio init/codecs + video codecs + line (add, credentials, register), line events + stun events + various sip settings what is not tested: - calls, call events (create, connect, destroy) - media events - conferences (add, join, split, remove, create, destroy) - hold (call, conference) - call transfer (blind, consultative) - chat So basically when I get to call transfer, I will have a look whether this problem also occurs in my version. Refactored version is much cleaner inside, so bugs are easier to fix (usually take a couple of minutes really). Refactored version has the same API, except for event to string conversion where it returns just const char*, and instead of passing parameters by &, they are passed by *, and bool type is changed to int so that sipxtapi can be used in C programs as well. I recommend to write down all problems you discovered in current sipxtapi so that I can make sure they don't exist in refactored version. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
