[sr-dev] [kamailio/kamailio] dialog: failover database loading behaviour in shared DB scenario, expiration of dialogs (#2080)

[Henning Westerholt]

Thanks for the reply Daniel. You are right about the redundancy/high-availability remarks.

But still I can see scenarios where the current behaviour can cause problems. Imagine a small dialog timeout combined with SIP Session Timer keep-alive re-INVITEs. The proxy 1 would not expire the dialog, but proxy2 (which did not got the re-INVITE) would expire it. Of course one could use DMQ or synchronize the dialog data by another means.

What do you think about something like this skip_remote_socket option which exists in usrloc as well: 
https://kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.p.skip_remote_socket


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2080#issuecomment-536491255
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20190930/9569e950/attachment.html>