2010/8/18 Carsten Bock lists@bock.info:
Hi Inaki, 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.
I've added a comment about it in the wiki: http://www.kamailio.com/dokuwiki/doku.php/modules-new-design:dialog-module-d...
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...
Yes, but anyhow it requires two MI calls and makes the operation complex (the "terminating" party must first invoke "dlg_list", then parse the MI body and finally invoke "dlg_end_dlg").
Regards.
Carsten
2010/8/18 Iñaki Baz Castillo ibc@aliax.net
2010/8/18 Carsten Bock lists@bock.info:
- if the name of the timeout-socket starts with "http://", it assumes it
is an Kamailio-XML-RPC-Server. It will then retrieve the according dialog-info by issueing a dlg_list with the call-id and with this information execute a dlg_end_dlg using XML-RPC.
Hi. Having to retrieve the dialogs full list for each time a rtpproxy session expires wouldn't be efficient, am I right? IMHO there could be a new MI function in dialog module allowing to terminate a dialog by providing its Call-ID and From-tag rather than the internal hash_id:hash_entry.
Regards.
-- Iñaki Baz Castillo ibc@aliax.net
-- Carsten Bock Schomburgstr. 80 22767 Hamburg Germany
Mobile +49 179 2021244 Home +49 40 34927217 Fax +49 40 34927218 mailto:carsten@bock.info