Hi Inaki,<div><br></div><div>probably you are right. I have not thought about this. I will take a look at it and put a patch for this on the tracker. But i think, you are right, that should be easy to implement.</div><div>

By the way: If you make a dlg_list_dlg with Call-ID and From-Tag (what i do), you just get the one dialog and you do not get the full list...</div><div><br></div><div>Carsten<br><br><div class="gmail_quote">2010/8/18 Iņaki Baz Castillo <span dir="ltr">&lt;<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">2010/8/18 Carsten Bock &lt;<a href="mailto:lists@bock.info">lists@bock.info</a>&gt;:<br>
<div class="im"><br>
&gt; - if the name of the timeout-socket starts with &quot;http://&quot;, it assumes it is<br>
&gt; an Kamailio-XML-RPC-Server. It will then retrieve the according dialog-info<br>
&gt; by issueing a dlg_list with the call-id and with this information execute a<br>
&gt; dlg_end_dlg using XML-RPC.<br>
<br>
</div>Hi. Having to retrieve the dialogs full list for each time a rtpproxy<br>
session expires wouldn&#39;t be efficient, am I right?<br>
IMHO there could be a new MI function in dialog module allowing to<br>
terminate a dialog by providing its Call-ID and From-tag rather than<br>
the internal hash_id:hash_entry.<br>
<br>
Regards.<br>
<font color="#888888"><br>
<br>
<br>
--<br>
Iņaki Baz Castillo<br>
&lt;<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Carsten Bock<br>Schomburgstr. 80<br>22767 Hamburg<br>Germany<br><br>Mobile +49 179 2021244<br>Home +49 40 34927217<br>Fax +49 40 34927218<br>mailto:<a href="mailto:carsten@bock.info">carsten@bock.info</a><br>

<br>
</div>