The question is whether that DMQ synchronization for dialog data is sending all dialogs or only delta/incremental data. Some SBCs I've worked with only synchronize new dialog data, leaving standby nodes only aware of dialogs established since restarting or joining the cluster, not existing dialogs. In that circumstance, a failover to the restarted or new standby would break any dialogs created prior to the restart.

If Kamailio dialog DMQ synchronization is "complete" then we just need to know how to confirm the new standby is synchronized before performing a failover.

On Thu, Jun 8, 2023 at 12:53 PM Henning Westerholt <hw@gilawa.com> wrote:

Hello,

are you aware of the DMQ synchronisation for dialog data? It’s not replicated everything, but certainly a way to seed the dialog information after a restart.

Another way is of course the usual shared database, just keep in mind that you need to configure the dialog module (hash table “step” variables”) to properly work.

Cheers,

Henning

--

Henning Westerholt – https://skalatan.de/blog/

Kamailio services – https://gilawa.com

From: Calvin E. <calvine@gmail.com>
Sent: Donnerstag, 8. Juni 2023 19:36
To: Kamailio (SER) - Users Mailing List <sr-users@lists.kamailio.org>
Subject: [SR-Users] Dialog DMQ state after restart

Does the dialog module do anything similar to the htable dmq_init_sync behavior?

The scenario is restarting the offline member of an HA pair after modifying the script. We're unsure of the state of the replicated dialogs post-restart. Will the standby become aware of the dialogs prior to the restart? In other words, do we need to wait until the pre-restart calls end before we can safely failover?

-Calvin E.