[sr-dev] dialog: reason behind not storing early state dialogs in db

[David Escartin]

Dear all

this would be related to one query we sent to sr-users some time ago?
https://lists.kamailio.org/pipermail/sr-users/2018-November/103842.html

we would also be interested in having the dialog structure to be written on
db_redis during early dialog, but it still was in a to do list according to
Daniel. This would great to be able to track and store the dialogs on a db
redis for HA.

thanks a lot and regards
david


El mié., 10 jun. 2020 a las 11:25, Henning Westerholt (<hw at skalatan.de>)
escribió:

> 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
>
>
> _______________________________________________
> Kamailio (SER) - Development Mailing List
> sr-dev at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20200612/c50ed340/attachment-0002.html>