Resources.DocsMigration170to180 History

Hide minor edits - Show changes to markup

April 24, 2013, at 02:11 PM by 109.99.235.212 -
Changed lines 1-46 from:

Resources -> Documentation -> Version Migration -> Upgrading from 1.7.0 to 1.8.0

This page has been visited 2678 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 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.

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 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.
to:

(:redirect Documentation.Migration-1-7-0-to-1-8-0 quiet=1 :)

January 30, 2013, at 10:23 AM by bogdan -
Changed line 1 from:

Resources -> Documentation -> Upgrading from 1.7.0 to 1.8.0

to:

Resources -> Documentation -> Version Migration -> Upgrading from 1.7.0 to 1.8.0

April 10, 2012, at 06:55 PM by vlad_paiu -
Added lines 31-33:

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.

March 22, 2012, at 05:14 PM by vlad_paiu -
Changed line 43 from:
  • TODO - DR
to:
  • 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.
March 22, 2012, at 11:51 AM by vlad_paiu -
Changed lines 42-43 from:
  • 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)
to:
  • 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)
  • TODO - DR
March 22, 2012, at 11:42 AM by vlad_paiu -
Changed line 8 from:

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

to:

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

March 22, 2012, at 11:40 AM by vlad_paiu -
Changed line 13 from:

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

to:

You can migrate your 1.7.x DB to the 1.8.0 format by using the opensipsdbctl tool :

Changed line 15 from:
   # opensipsdbctl migrate opensips_1_6 opensips_1_7
to:
   # opensipsdbctl migrate opensips_1_7 opensips_1_8
Changed line 18 from:
   > migrate opensips_1_6 opensips_1_7
to:
   > migrate opensips_1_7 opensips_1_8
Changed lines 23-24 from:
  • 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
to:
  • 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
March 22, 2012, at 11:39 AM by vlad_paiu -
Changed lines 13-32 from:

TODO - USRLOC & DROUTING & DISPATCHER

to:

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

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

March 19, 2012, at 01:46 PM by vlad_paiu -
Changed lines 13-15 from:

TODO - USRLOC & DROUTING

to:

TODO - USRLOC & DROUTING & DISPATCHER

Changed lines 22-23 from:
  • 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 .
to:
  • 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)
March 13, 2012, at 04:40 PM by vlad_paiu -
Changed lines 13-36 from:

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

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

to:

TODO - USRLOC & DROUTING

Changed lines 22-29 from:
  • 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.
to:
  • 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 .
March 13, 2012, at 04:37 PM by vlad_paiu -
Changed line 42 from:
  • 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.
to:
  • 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 SIPMSGOPS documentation for the list of exported functions, and also load the SIPMSGOPS module, if needed.
March 13, 2012, at 04:32 PM by vlad_paiu -
Added lines 1-50:

Resources -> Documentation -> Upgrading from 1.7.0 to 1.8.0

This page has been visited 2678 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.7.0 release compiled under this page. Overviewing it may help you understanding the migration / update process.


DB migration

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

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

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


Script migration

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

Page last modified on April 24, 2013, at 02:11 PM