Looking at the trace, looks related to sending a reply. In 5.2.2 I pushed a fix for a case when a reply processing happened at the same when the transaction was supposed to be deleted, after the safety wait timer of 5sec. Can you try with 5.2.2 just to rule out this issue is not a side effect of the same problem?

If crash still, would you be able to make a sipp scenario and a docker image to reproduce it? I tried, but could't reproduce, I guess it is a specific combination of events specific for your deployment.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.