Migration from 4.0.x to 4.1.x

This section is meant to provide useful help in migrating your OpenSIPS installations from the 4.0.x version to 4.1.x.

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

DB migration

You can migrate your 4.0.x MySQL DB to the 4.1.x format using the opensips-cli tool :

   $ opensips-cli -x database migrate 4.0_to_4.1 opensips_4_0 opensips_4_1

where :

opensips_4_0 is the existing DB name corresponding to version 4.0.x format
opensips_4_1 is the DB name to be created for 4.1.x format

See the opensips-cli documentation for more details.

Script migration

The following is the full list of backwards-incompatible syntax or functional changes in the OpenSIPS configuration script:

none

Global Parameters

The provisioning framework is now configured globally with the new pi_framework core parameter. If pi_http is used, move the framework path from modparam("pi_http", "framework", "...") to:
```
pi_framework = "/path/to/pi_framework.xml"
```
The provisioning MI commands are now core commands: use pi_list to inspect the framework and pi_reload to reload it. The old pi_reload_tbls_and_cmds / pi_http:reload_tbls_and_cmds commands should no longer be used.

Core Variables

example

Core keywords

example

Core functions

example

Statistics migration

example

Modules migration

PI_HTTP module

The framework module parameter has been removed. Configure the framework with the global pi_framework core parameter instead.
The provisioning MI commands have moved to core. Replace pi_reload_tbls_and_cmds and pi_http:reload_tbls_and_cmds with the core commands pi_list and pi_reload.