<div dir="ltr">Thanks, this looks like a good idea! changed your code a little to set DLG_timeout=5 right after create_dialog (otherwise even though you set DLG_timeout=12hrs for ACK, outside the if it gets reset to 5 again). I'm testing and will let you know.<div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 31, 2022 at 2:27 AM John Burke via Users <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Hello,<br>
<br>
One way to handle the ACK timeout scenario that you described is to
initially set the dialog timeout to a low value, then increment to
the desired value after receiving the ACK. Here's a minimal example
with some notes I have. In this config, your call would hang for
5sec before being auto-closed by the dialog module.<br>
<br>
route {<br>
if (has_totag()) {<br>
# sequential request logic<br>
...<br>
if (is_method("ACK"))<br>
$DLG_timeout = 43200; # 12hrs<br>
...<br>
}<br>
<br>
# to handle case of lost ACK, we set low dialog timeout then<br>
# increase once ACK is received; without this the call will stay<br>
# in DLG_STATE=3 until default dialog timeout is met<br>
# NOTE: timer doesn't start until 200 received, so this is
essentially<br>
# an ACK timeout (ie 200 -> ACK)<br>
$DLG_timeout = 5;<br>
<br>
...<br>
# initial request logic<br>
}<br>
<br>
<br>
If the code ever changes to start the DLG timer before the 200, then
this doesn't work... but I think this is baked into RFC and in any
rate my unit tests for this scenario have never failed when
migrating versions :)<br>
<br>
Thanks,<br>
John Burke<br>
<br>
<div><br>
</div>
<div>On 10/30/22 9:44 AM, M S wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi list,
<div>When a dialog is created with initial INVITE, it seems like
it is not available to dlg_end_dlg until the call is answered
(OK received) and the caller also acknowledges (ACK) to the OK
message.</div>
<div>So in a scenario where a caller sends an INVITE and then
dies, the call goes to callee, gets answered, OK is sent to
caller but there is no response, and the dialog stays open
until default_timeout and that's when the CDR is generated (if
default_timeout is 12 hours then a 12 hour call is in CDR).</div>
<div>Anybody has any ideas how we can fix this? If I use PpB for
dialog, it never PINGs the callee because apparently the
dialog is not fully established on the callee side. If I use
rtpengine to detect media timeout, it correctly detects it but
when it calls dlg_end_dlg opensips says "dialog not found".</div>
<div><br>
</div>
<div>Thank you!</div>
</div>
<br>
--<br>
<table style="border-collapse:collapse;width:100%;height:64px;background-color:rgb(253,61,20)" border="1">
<tbody>
<tr style="height:64px">
<td style="width:100%;height:64px;text-align:center">
<pre><span style="background-color:rgb(253,61,20);color:rgb(255,255,255)"><strong><span style="font-size:300%"> Please be cautious!</span></strong>
<span style="font-size:x-large"> This email was sent from outside of Voxtelesys.</span></span></pre>
</td>
</tr>
</tbody>
</table>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>