<div dir="ltr"><div dir="ltr"><span style="font-family:monospace"><span style="font-family:verdana,sans-serif">I did catch the logs, and after looking at the trace, it seems like dialog mismatch with a serial forking scenario :</span><br></span><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:verdana,sans-serif">- log line 3 is telling us that a NO-ACK disconnection should be triggered<br></span></div><div><span style="font-family:monospace"><span style="font-family:verdana,sans-serif">- log line 1-2 is telling us what happened when the ACK was received in dlg_onroute()</span>, <span style="font-family:verdana,sans-serif">oddly enough state 5 was old and new, could it be a mismatch/confusio with the previous dialog, looking in this direction ...</span><br></span></div><div><span style="font-family:monospace"><br>1:
2020-09-25T16:30:16.896: dialog [dlg_handlers.c:1273]:
extra_ack_debug_info(): [ACK][1] state not changed >>>
call-id[562419_125824138_2072238224] to-tag[<<a href="mailto:sip%3A%2B14019991904@anon.com" target="_blank">sip:+14019991904@anon.com</a>>;tag=gK02b68836]<br>2: 2020-09-25T16:30:16.896: dialog [dlg_handlers.c:1440]: dlg_onroute(): [ACK] state not changed old[5]new[5] <br>...<br>3: 2020-09-25T16:32:22.674: dialog [dlg_hash.c:247]: dlg_clean_run(): dialog disconnection no-ACK call-id[562419_125824138_2072238224][1601051416]<[1601051542 - 60]<br><br><br><span style="font-family:verdana,sans-serif">After looking at the pcap trace, call-id 562419_125824138_2072238224 was involved in serial forking :</span><br><br>call attempt #1<br><br>X >> INVITE >> Y // no to-tag <br>X << 100<br>...<br>X << 408 // to-tag=594d50c3218065a60bb91fd47a70fbc1-59edef02 (locally generated)<br>X >> ACK // to-tag=594d50c3218065a60bb91fd47a70fbc1-59edef02<br><br>call attempt #2<br><br>X >> INVITE >> Z // no to-tag<br>X << 100<br>X << 200 << Z // to-tag=gK02b68836<br>X
>> ACK >> Z // to-tag=gK02b68836 (Should be state
old[3]new[4], I wonder how it could possibly be state old[5]new[5])<br><br><br></span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">I did look at several occurrences and there is always a locally generated 408/to-tag before, seems like I have a good lead to investigate further.</span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace"></span><br></div></div></div>