You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Dialog and DMQ in db_mode 2 - dialog_vars entries created and not deleted.
Szenario: two proxies in DMQ synchronization with additional database. Configuration identical on both machines:
root@proxy-1:/etc/kamailio# grep dialog kamailio.cfg
loadmodule "dialog.so"
modparam("dialog", "db_mode", 2)
modparam("dialog", "db_update_period", 10)
modparam("dialog", "enable_dmq", 1)
modparam("dialog", "default_timeout", 60);
modparam("dialog", "send_bye", 1)
Call is placed on proxy1. Proxy1 handles the call, and synchronize the dialog data to proxy2. Proxy2 is able to list the dialog with kamcmd dlg.list etc..
Proxy2 will not write the dialog into dialog table, but will write the dialog variables to the dialog_var table:
root@proxy-2:/etc/kamailio# mysql kamailio
MariaDB [kamailio]> select * from dialog; select * from dialog_vars;
Empty set (0.00 sec)
+----+------------+---------+-------------+---------------------------------+
| id | hash_entry | hash_id | dialog_key | dialog_value |
+----+------------+---------+-------------+---------------------------------+
| 9 | 3479 | 1648 | _uac_fu | sip:customer-1@sip.XXXX.net |
| 10 | 3479 | 1648 | _uac_funew | sip:batman@XXX.org |
| 11 | 3479 | 1648 | _uac_fdp | |
| 12 | 3479 | 1648 | _uac_fdpnew | |
| 13 | 3479 | 1648 | _uac_to | sip:customer-2@sip.skalatan.net |
| 14 | 3479 | 1648 | _uac_tonew | sip:robin@XXX.org |
| 15 | 3479 | 1648 | _uac_tdp | |
| 16 | 3479 | 1648 | _uac_tdpnew | |
+----+------------+---------+-------------+---------------------------------+
8 rows in set (0.00 sec)
Because of this the dialog_vars will grow for every call.
In db_mode 1 this dialog_vars entries (and also dialog entries) are not written.
I suggest to adapt db_mode 2 with DMQ to the same behaviour.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.