[sr-dev] dialog: reason behind not storing early state dialogs in db
Henning Westerholt
hw at skalatan.de
Wed Jun 10 11:24:27 CEST 2020
Hi Victor,
I guess it was done because of easier implementation and also DB load considerations.
I planned to add functionality to make it configurable in git master it this week, as I also have the requirements in one of my projects.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: sr-dev <sr-dev-bounces at lists.kamailio.org> On Behalf Of Victor Seva
Sent: Wednesday, June 10, 2020 10:32 AM
To: Kamailio Devel List <sr-dev at lists.sip-router.org>
Subject: [sr-dev] dialog: reason behind not storing early state dialogs in db
Hi,
is there a known reason not to store early state dialogs in db?
I have some logic relaying on event_route exported by dialog module and that logic breaks for non confirmed dialogs when a switch-over happens since those dialogs are not loaded from db.
Thanks in advance,
Victor
More information about the sr-dev
mailing list