< Previous by Date | Date Index | Next by Date > |
Thread Index | Next in Thread > |
What I think we need to do is create a function in SipStack that takes a transaction id and a bool indicating whether this is a NIT, and schedules the deletion of the corresponding TransactionState. We shouldn't just delete the transaction immediately, because we would end up treating any retransmissions as new requests. This function will create a TimerH for invite transactions, or a TimerJ for non- invite transactions, as if the TU had sent a failure response (Timer G does not need to be added, since there is no "real" response to retransmit), which will prompt deletion of the TransactionState after it has had a chance to absorb retransmissions.
Any comments? Should we push for this to make it in the release? Best regards, Byron Campen
Attachment:
smime.p7s
Description: S/MIME cryptographic signature