Hi,
[email protected] wrote:
Author: rco
Date: 2010-04-09 14:19:28 +0200 (Fri, 09 Apr 2010)
New Revision: 1778
Modified:
trunk/core/AmB2BSession.cpp
trunk/core/AmSipDialog.cpp
trunk/core/AmSipDialog.h
trunk/core/AmSipMsg.cpp
trunk/core/AmSipMsg.h
trunk/core/SipCtrlInterface.cpp
trunk/core/SipCtrlInterface.h
trunk/core/sip/sip_ua.h
trunk/core/sip/trans_layer.cpp
trunk/core/sip/trans_layer.h
Log:
the old serKey has been replaced by a proper transaction ticket specific to the
internal SIP stack.
to me it looks like the transaction ticket in AmSipDialog layer is
only used for cancel()-ing a request, is that correct?
I am wondering whether this makes sense, then. the tt (which contains
pointers into the transaction structures in sip stack) is saved and
copied everywhere in e.g. uas_trans, where it is not used at all. It
would be different if AmSipDialog::reply() would take the
AmSipTransaction, not the AmSipRequest it replies to.
Stefan
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
