Because of the database schema differences between the two versions, you will not be able to use the same database to run both.
One migration strategy could be: 1. Convert the configuration and migrate the database structure to the new version 3.4 on the current slave 2. Test the slave SIP logic using a separate IP address or port with a SIP client that uses the slave server address as outbound SIP Proxy. When everything works continue to the next step. 3. Switch over the cluster to the newly configured slave running the new OpenSIPS version 4. Copy the configurations from the newly promoted slave to master to the old master machine 5. Switch back to the old master Adrian > On 30. Aug 2024, at 16:54, Pyle, Jeff <[email protected]> wrote: > > Hello, > > I have an OpenSIPS 2.4 cluster I need to upgrade to 3.4. The cluster is > configured as an HA pair, with one active and one standby where keepalived > moves the IP between the two. > > Can instances on 2.4 and 3.4 participate in the same cluster? I'm hoping to > update one "half" at a time while maintaining call processing on the side > that isn't being upgraded. > > > Regards, > Jeff > > This message is subject to Fusion Connect, Inc.’s email communication policy: > www.fusionconnect.com/email-policy > <http://www.fusionconnect.com/email-policy>_______________________________________________ > Users mailing list > [email protected] <mailto:[email protected]> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
