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

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

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

This section is meant to provide useful help in migrating your OpenSIPS installations from the 1.10 version over to 1.11.

This section is meant to provide useful help in migrating your OpenSIPS installations from the 1.10 version over to OpenSIPS 1.11.

This section is meant to provide useful help in migrating your OpenSIPS installations from the 1.10 branch to the 1.11 branch.

You can find the all the new additions in the 1.11.0 release compiled under this page. The changelog may help you understanding the migration / update process.

You can find the all the new additions in the 1.11.0 release compiled under this page. The changelog may help you understanding the migration / update process.

You can find the all the new additions in 1.11.0 release compiled under this page. The changelog may help you understanding the migration / update process.

• fr_timer_avp and fr_inv_timer_avp parameters from the TM module were removed. New $T_fr_timeout and $T_fr_inv_timeout exported pseudovariables have been added as a drop-in replacement.

• attrs_pvar parameter from the dialplan module was removed. The script writer can now pass a pseudovariable to be populated with the diaplan rule attrs when calling dp_translate()

• fr_timer_avp and fr_inv_timer_avp parameters from the TM module were removed. New T_fr_timeout and T_fr_inv_timeout exported pseudovariables have been added as a drop-in replacement.

• gw_attrs_avp , rule_attrs_avp , carrier_attrs_avp parameters from the drouting module were removed. Now the script writer can provide pseudovariables ( AVPs, regular vars, etc ) when calling the do_routing()/use_next_gw() functions, where the appropriate attrs will get populated. All parameters are optional. Any of them may be ignored,provided the necessary separation marks "," are properly placed.
• set_rtp_proxy_set() function and rtpp_sock_pvar parameter from rtpproxy module were removed. The script writer can now pass all the info ( the RTPProxy set to be used as well as a PVAR to store the actual RTPProxy used for the call ) directly when calling the rtpproxy_offer() / rtpproxy_answer() etc type functions

• timeout_avp parameter from the dialog module was removed. Functionality was kept via the new $DLG_timeout variable, which is R/W, and can be set an any time ( before matching the dialog or at any time after )
• gw_attrs_avp , rule_attrs_avp , carrier_attrs_avp parameters from the drouting module were removed. Now the script writer can provide appropriate pseudovariables ( AVPs, regular vars, etc ) when calling the do_routing()/use_next_gw() functions. All parameters are optional. Any of them may be ignored,provided the necessary separation marks "," are properly placed.

• timeout_avp parameter from the dialog module was removed. Functionality was kept via the new $DLG_timeout variable, which is R/W, and can be set an any time ( before matching the dialog or after )

Documentation -> Migration -> Migration from 1.10.x to 1.11.0

This page has been visited 5732 times. (:toc-float Table of Content:)

This section is to provide useful help in migrating your OpenSIPS installations from the 1.10 branch to the 1.11 branch.

You can find the all the new additions in 1.11.0 release compiled under this page. Over viewing it may help you understanding the migration / update process.

DB migration

You can migrate your 1.10.x DB to the 1.11.0 format by using the opensipsdbctl tool :

   # opensipsdbctl migrate opensips_1_10 opensips_1_11
   or
   # osipsconsole 
   > migrate opensips_1_10 opensips_1_11
   > quit
   # 

where :

• opensips_1_10 is the existing DB name corresponding to version 1.10.x format
• opensips_1_11 is the DB name to be created for 1.11 format

NOTE:

• 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!

(:toc-back Back to Table of Contents:)

Script migration

• SCA support for the presence_callinfo module is not by default activated. If you want to disable it, you have to set the on 1.
• The auth_username_avp, auth_realm_avp and auth_password_avp parameters have been moved from the uac module to uac_auth. See this FAQ for more information.