Login | Register


Documentation -> Migration -> Migration from 2.4.x to 3.0.0

This page has been visited 191 times.

This section is meant to provide useful help in migrating your OpenSIPS installations from the 2.4.0 version to 3.0.0.

You can find the all the new additions in the 3.0.0 release compiled under this page. The ChangeLog may help your understanding of the migration / update process.

Make sure you don't have any Makefile.conf files in your sources' root before starting the migration. The configuration file generated by 'menuconfig is not compatible with the one in older version!

1.  DB migration

You can migrate your 2.4.x MySQL DB to the 3.0.x format by using the opensipsdbctl tool :

   # opensipsdbctl migrate opensips_2_4 opensips_3_0

where :

  • opensips_2_4 is the existing DB name corresponding to version 2.4.x format
  • opensips_3_0 is the DB name to be created for 3.0.x format


  • the old database will not be deleted, altered or changed - it will not be touched at all
  • new database will be created and data from old DB will be imported into it

NOTE that the migration tool is available only for MYSQL databases!

NOTE that the default MySQL DB engine is now InnoDB!

Back to Table of Contents

2.  Script migration

The following is the full list of backwards-incompatible syntax or functional changes in the OpenSIPS configuration script (some of them are fixes):

2.1  Global Parameters

  • example

2.2  Core keywords

  • example

2.3  Core MI commands

  • example

2.4  Statistics migration

  • example

3.  Module migration


  • example

3.2  AUTH_AAA module

3.3  TLS_MGM module

  • the address column from the tls_mgm table was removed and the TLS domain matching is now driven by two new columns: match_ip_address and match_sip_domain
  • the syntax for the server_domain and client_domain parameters now only accepts the TLS domain name
  • the client_domain_avp module parameter was renamed to client_tls_domain_avp

3.4  DB_MYSQL module

  • the tls_client_domain module parameter was removed in favor of a new way of enabling TLS for specific MySQL connections via the DB URL.

3.5  REST_CLIENT module

3.6  URI module

Page last modified on October 30, 2018, at 12:34 PM