!! Resources -> [[Resources.Documentation | Documentation]] -> [[Resources.DocsMigration | Version Migration]] -> Upgrading from 1.7.0 to 1.8.0
This page has been visited {$PageCount} times.
(:toc-float Table of Content:)
----

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

You can find the all the new additions in 1.8.0 release compiled [[http://www.opensips.org/Main/Ver180 | under this page]]. Overviewing it may help you understanding the migration / update process.

----
!!! DB migration

You can migrate your 1.7.x DB to the 1.8.0 format by using the '''opensipsdbctl''' tool :
[@
# opensipsdbctl migrate opensips_1_7 opensips_1_8
or
# osipsconsole
> migrate opensips_1_7 opensips_1_8
> quit
#
@]
where :
* opensips_1_7 is the existing DB name corresponding to version 1.7.x format
* opensips_1_8 is the DB name to be created for 1.8 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:
* Due to the latest DROUTING changes & improvements, in the gwlist per rule, the ';' is no longer accepted.
In order to create gateway groups, use the carriers addition. The migration tool will give out warnings regarding this, but there is no way to automatically migrate this information, so manual migration will be needed for this.

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


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

----
!!! Script migration

* Because of a large part of the TEXTOPS module was split to the SIPMSGOPS module, some functions that used to be in the TEXTOPS module will not reside in SIPMSGOPS. Please check the [[http://www.opensips.org/html/docs/modules/devel/sipmsgops.html | SIPMSGOPS]] documentation for the list of exported functions, and also load the SIPMSGOPS module, if needed.
* With the addition of the Key-Value Interface, for consistency, some modules were renamed. The old localcache module is now called cachedb_local , and the old memcached module is now called cachedb_memcached .
* The dispatcher 'list_file' module parameter was removed, as the support for text file (for provisioning destinations) was dropped. If you still want to use a text file for provisioning, use db_text DB driver (DB emulated via text files)
* With the new DROUTING module enhancements, the do_routing() function prototype has changed. The old 'sort' integer parameter was replaced by a string flags parameter. In order to sort gateways by weight, you can now pass the 'W' string flag. The addition of weights per gateway will now give you a much better control of gateways for a specific rule. For example, the old 'random' sort feature can now be implemented by adding equal weights for all GWs within the same rule.

!! Resources -> [[Resources.Documentation | Documentation]] -> Upgrading from 1.7.0 to 1.8.0

* TODO - DR

* The dispatcher 'list_file' module parameter was removed, as the support for text file (for provisioning destinations) was dropped. If you still want to use a text file for provisioning, use db_text DB driver (DB emulated via text files)

You can find the all the new additions in 1.7.0 release compiled [[http://www.opensips.org/Main/Ver180 | under this page]]. Overviewing it may help you understanding the migration / update process.

You can migrate your 1.6.4 DB to the 1.7.0 format by using the '''opensipsdbctl''' tool :

# opensipsdbctl migrate opensips_1_6 opensips_1_7

> migrate opensips_1_6 opensips_1_7

* opensips_1_6 is the existing DB name corresponding to version 1.6.4 format
* opensips_1_7 is the DB name to be created for 1.7.x format

TODO - USRLOC & DROUTING & DISPATCHER

TODO - USRLOC & DROUTING

* With the addition of the Key-Value Interface, for consistency, some modules were renamed. The old localcache module is now called cachedb_local , and the old memcached module is now called cachedb_memcached .

The database structure was not affected by major changes, only some fields additions in some tables and some fields type changing.

You can migrate your 1.6.4 DB to the 1.7.0 format by using the '''opensipsdbctl''' tool :
[@
# opensipsdbctl migrate opensips_1_6 opensips_1_7
or
# osipsconsole
> migrate opensips_1_6 opensips_1_7
> quit
#
@]
where :
* opensips_1_6 is the existing DB name corresponding to version 1.6.4 format
* opensips_1_7 is the DB name to be created for 1.7.x 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


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

* Remove the "report_ack" parameter from the ACC module. The parameter is considered obsolete.
* Remove the "bye_on_timeout_flag" parameter from the DIALOG module. To keep the bye on timeout behavior, you need to provide a "B" string parameter to the create_dialog() function, like create_dialog("B").
* Remove the "dlg_flag" parameter from the DIALOG module. The parameter is considered obsolete. The only way to create a dialog is to call the create_dialog() function
* Remove the "enable_full_lr" parameter from the RR module. The parameter is considered obsolete.
* A new RTPProxy module was split from the Nathelper module, so you must load this new module if you desire RTPProxy integration. The script API remains the same.
* A new module was added, UAC_AUTH, that provides a common API for UAC authentication functionality. The UAC and B2B modules now use the API provided by the UAC_AUTH module, so you must load this module before the UAC and B2B.
* The nat_traversal module was reworked in order to cope with the new Dialog API. If you used to reset the dlg_flag in order to cancel the late dialog creation, you must now set to 0 the $nat_traversal.track_dialog pvar.
* The mediaproxy and call_control module no longer allow the cancelation of the late dialog creation, so resetflag(dlg_flag) no longer makes sense.

* Because of the new AVP auto-aliasing feature for the script, you must remove the "avp_aliases" parameter if you were using aliases, and also remove all the "i:" and "s:" prefixes from AVP names.