[reSIProcate-users] Assertion issue with StaleCallTimeout

["Paul Kurmas" <pkurmas@xxxxxxxxxxxxx>]

Here's the situation...
1) "A" sends an INVITE to "B".
2) "B" sends a "180 Ringing" to "A".  "A" starts the stale call timer.
3) Some network error occurs that causes the "200 OK" from "B" to "A" to
be lost.
4) "A" gives up on the call, invoking ClientInviteSession::end via the
InviteSessionHandle.  This transmits a BYE.
5) A few seconds later, the stale call timer fires.  After our callback,
ClientInviteSession::dispatch calls InviteSessionHandler::terminate,
while in turn calls DialogSet::end.  The dialog set must be non-empty
because ClientInviteSession::cancel gets called.
6) The session is not in a valid state & there's an assertion.  The
application exits.

Can anyone give me an idea if our application is doing the wrong thing
to abandon the invite at this point?  Or is there really a bug within
DUM or the stack?

PK