2009/3/5 Stefano Sabatini <ssabat...@reilabs.com>: > sofsip_cli bookeeps this information in the ssc_oper_s struct > (ssc_oper.h), I also tried the i_state event management approach but > it is not correct, since the i_state event (setting the state in the > operation context/magic) is processed by the sofia event handler > *after* the actual event which causes the state transition.
If you call nua_bye(), it will actually send a CANCEL request if no final response has been received for the INVITE transaction. Also, if 2XX has been received, nua_bye() is supposed to send ACK, too. Please report if that is not the case. > So I wonder if it would make sense to set this information in the > handle itself, when the various nua_invite/nua_ack/... operations are > performed, rather than re-implement that logic in every app. While is possible to cache the latest call state in nua handle, however, I don't think it will solve your problem. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
