[reSIProcate] Timed out dialogs are never destroyed

[Dmitry Semyonov <dsemyonov@xxxxxxx>]

Hello.

My reSIProcate based application makes a call to SIP UAS.
SIP UAS sends 100, then 101 responses, and after that the connection 
is broken. I see that in this case the dialog is never destroyed, 
although TimerB fires in time.

Shouldn't

         case Timer::TimerB:
            if (mState == Calling)
            {
               sendToTU(Helper::makeResponse(*mMsgToRetransmit, 408));
               terminateClientTransaction(mId);
               delete this;
            }
            delete msg;
            break;

inside TransactionState::processClientInvite() be updated to terminate 
the transaction in Trying and Proceeding states as well?

-- 
...Bye..Dmitry.