[reSIProcate] server non-invite transaction lifetime

["Justin Matthews" <jmatthewsr@xxxxxxxxx>]

Hello,

When processing a server non-invite transaction, what happens if a request
is received from the wire and then no response is ever generated from the TU
(InviteSession->acceptNIT())?  There are no timers specified in 3261
(17.2.3) so the stack is not handling this case.  In DUM, if a call is
terminated and a response was never given, an entry in the
mServerTransactionMap will remain, causing a memory leak (I have seen this
number grow under this condition using SipStack::dump()).

Are there any recommendations, besides always responding to the non-invite
transaction?  Can DUM be made to handle this by terminating all outstanding
non-INVITE transactions when an invite session is terminated?

Thanks,

-Justin