<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Daniel,<br>
<br>
That's a tricky one - mediaproxy is also using the dialog module
(via internal API) to terminate the call. So, in both cases, the
dialog module is doing the hangup. I guess you can spot the difference
from the logs only :(.<br>
<br>
Having a Reason header will make sense here.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
OpenSIPS Summit May 2017 Amsterdam
<a class="moz-txt-link-freetext" href="http://www.opensips.org/events/Summit-2017Amsterdam.html">http://www.opensips.org/events/Summit-2017Amsterdam.html</a>
</pre>
<div class="moz-cite-prefix">On 03/20/2017 03:26 PM, Daniel Zanutti
wrote:<br>
</div>
<blockquote
cite="mid:CAN0jgiNNNcbXngxheF24ObgC6uubGYB2i2h39th4GTJw3tBRqg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>I have 2 modules that may hangup the call:<br>
</div>
<div>
<div> - Dialog - duration timeout or sip ping with sip options</div>
<div> - Mediaproxy - RTP timeout</div>
<div><br>
</div>
<div>On local_route, is there any way to know which module did
the hangup?</div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>