I would like to mention one more thing. Documentation says: 

The dialog is automatically destroyed when a “BYE” is received. In case of no “BYE”, the dialog lifetime is controlled via the default timeout (see “default_timeout” - Section 6.6, “default_timeout (integer)”) and custom timeout (see “timeout_avp” - Section 6.5, “timeout_avp (string)”). The dialog timeout is reset each time a sequential request is processed.  

But in my case i can see on wireshark BYE received from caller and callee side but when running kamctl dialog show command the dialog is still on the list.

Best regards,
Tom

pt., 24 kwi 2020 o 23:21 Voip support <voipexpert0@gmail.com> napisał(a):
Hello,
i am using dialog module in-memory to get all dialogs and show in a website.
I use for this kamctl dialog show which is run quite often for autorefresh.

I noticed that some calls get hung on kamailio while on caller side and callee side calls are disconnected.

I captured a wireshark trace and for same caller IP i get many good calls as well some bad calls (not disconnected properly). When comparing the BYE packets i could not notice any difference.

However in the "BAD" calls it looks like the BYE from caller get stuck on kamailio and is not sent/forwarded to callee side. I get BYE retransmissions from caller and all BYE requests got stuck on kamailio.

After few seconds Callee side sends BYE and that BYE also get stuck.

I am wondering how to trace this issue (differently than taking a wireshark trace) as i dont see any difference in the good BYE and the bad BYE.

It looks like for any reason from time to time BYE is not forwarded to the other side and when the other side sents BYE its also not forwarded to call initiator.

Please give me a clue how to continue on this.

I am using dispatcher module to send the calls.

Best regards
Tom