Alexey Trizno wrote: >>> NewCall received, ok. Offering, ok, than I call SipxRejectCall. >>> I expect Disconnected event, but not receive it. >>> >>> >> Disconnected events are often missing for various reasons. I only rely >> on disconnecting event. >> > > Hmm... what reasons, for example? > > I have read in JIRA bug tracker that some people complained about destroyed events missing. I get them once I call sipxCallDestroy, but I don't do any processing once I receive them since I do not consider them to be 100% accurate. But maybe those people in bugtracker didn't call sipxCallDestroy after receiving disconnected event. sipxtapi.h claims calls are not automatically destroyed.
You also might miss all events if you use conferencing in sipxtapi without my patch as there are some bugs in the code. This patch is in JIRA and is quite necessary if you want conferencing, but isn't applied because it isn't fully finished (there is a problem for inbound calls). Also use sipxtapi branch not the main branch unless you are doing it already. What exactly do you want to use sipxtapi for? Or are you just experimenting? Jaroslav Libak _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
