Hello,
thanks for the additional information. It should certainly expire the dialog after some
time, even if it's synchronized from DMQ to the first instance.
Maybe you can try it with a small dialog timeout variable in a test setup, if possible. If
its not expiring, an issue could be opened about it.
Cheers,
Henning
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com
-----Original Message-----
From: Benoit Panizzon <benoit.panizzon(a)imp.ch>
Sent: Tuesday, November 15, 2022 3:07 PM
To: Henning Westerholt <hw(a)gilawa.com>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] dialog_vars accumulating in database?
Hmm, I have a suspicion how this happens...
I could more or less reproduce the issue:
2 Kamailio instances, synced with DMQ.
Both store dialog_vars in a local database for performance.
While a dialog is ongoing, stop instance 2. This instance 2 probably has stored dialog
information in it's local database.
End the dialog. Instance 1 propperly removes dialog_vars from it's local database and
forgets about it.
Restart Instance 2.
No longer existing dialog data from instance 2 is getting DMQ synced to Instance 1. This
dialog is sticking around on both instances and never expiring.
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web
http://www.imp.ch
______________________________________________________