I have tried to use and does not work for me because limited IPv6 support. For now we looking to https://datatracker.ietf.org/doc/html/rfc5626 In this case client register on two SIP proxy servers. If one registration is failed, the second still active.
This also has some side effect but extending Kamailio outbound module manage this side affect. On Sat, 2025-11-01 at 08:21 +0000, dries--- via sr-users wrote: > Hi all, > > Our current VOIP infrastructure includes a pair of Asterisk servers > behind an F5 load balancer, but I'm in the process of migrating to a > Kamailio cluster. > > I've set up a master/backup Kamailio cluster with Keepalived, > accessible via a virtual IP. The system uses an active/active MariaDB > Galera cluster for storing registrations, and I plan to implement DMQ > in the future to handle active dialogs as well. > > However, I've noticed that during failover, it takes a significant > amount of time for SIP clients to detect that their TCP session is > broken and re-register. I'm looking for best practices to minimize > the downtime for SIP clients. > > Has anyone successfully used the Linux Virtual Server (LVS) > implementation in Keepalived to synchronize TCP sessions, so that the > backup node can seamlessly handle the existing sessions from clients? > Or is the only solution to reduce the SIP client’s registration timer > to something like 1 minute to speed up the re-registration? > > Cheers, > Dries > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- > [email protected] > To unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only > to the sender! __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
