User Tools

Site Tools


install:upgrade:stable-to-devel

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
install:upgrade:stable-to-devel [2016/02/28 12:44]
miconda [Database]
install:upgrade:stable-to-devel [2020/07/17 08:41] (current)
miconda [Upgrade Kamailio from v5.4.x to v5.5.0 (devel)]
Line 1: Line 1:
-====== Upgrade Kamailio from v4.3.x to v4.4.0 (devel) ======+====== Upgrade Kamailio from v5.4.x to v5.5.0 (devel) ======
  
-The page contains the details about the changes that were made to old components during the development of v4.4.0 compared with what existed in v4.3.x. It does not include the brand new modules, focusing on how to upgrade database and configuration file from v4.3.x to run with Kamailio devel.+The page contains the details about the changes that were made to old components during the development of v5.5.0 compared with what existed in v5.4.x. It does not include the brand new modules, focusing on how to upgrade database and configuration file from v5.4.x to run with Kamailio 5.5.0.
  
 ===== Previous Stable Release ===== ===== Previous Stable Release =====
Line 7: Line 7:
 If you look for the guidelines to upgrade to previous stable release, see: If you look for the guidelines to upgrade to previous stable release, see:
  
-  * [[install:upgrade:4.2.x-to-4.3.0|Upgrade Kamailio v4.2.x to v4.3.0]]+  * [[install:upgrade:5.3.x-to-5.4.0|Upgrade Kamailio v5.3.x to v5.4.0]]
  
 ===== Remarks ===== ===== Remarks =====
Line 16: Line 16:
   * CPM - the change was used with the new value via explicit parameter in default config file from old releases   * CPM - the change was used with the new value via explicit parameter in default config file from old releases
   * RCM - the change is recommended to be done if you had an explicit different or lower value for this parameter in old config   * RCM - the change is recommended to be done if you had an explicit different or lower value for this parameter in old config
 +  * UPG - the change has to be done, older config does not work any longer
  
 ===== Modules ===== ===== Modules =====
 +
 +==== Upgraded Modules ====
 +
 +  * none
 +
 +==== Removed Modules ====
 +
 +  * none
 +
 +==== Renamed Modules ====
 +
 +  * none
 +
 +===== Internal Libraries =====
 +
  
 ===== Core ===== ===== Core =====
  
 ==== Parameters ==== ==== Parameters ====
 +
 +==== Misc ====
  
 ===== Database ===== ===== Database =====
  
-There are quite minimal changes to the database structure, in short: 
  
-  * presence active_watchers table has new columns 
-  * permissions trusted table has new columns 
-  * uac uacreg table has new columns 
 ==== MySQL Database Structure ==== ==== MySQL Database Structure ====
  
-Run following SQL statements in MySQL client to upgrade database structure from v4.to v4.4:+Run following SQL statements in MySQL client to upgrade database structure from v5.to v5.5:
  
 <code sql> <code sql>
--- table: active_watchers +...
-ALTER TABLE active_watchers +
-  ADD COLUMN flags int(11) NOT NULL DEFAULT '0', +
-  ADD COLUMN user_agent varchar(255) NOT NULL; +
-DELETE FROM version WHERE TABLE_NAME='active_watchers'; +
-INSERT INTO version (`table_name`, `table_version`) VALUES ('active_watchers','12'); +
- +
--- table: trusted +
-ALTER TABLE trusted +
-  ADD COLUMN priority int(11) NOT NULL DEFAULT '0', +
-  ADD COLUMN ruri_pattern varchar(64) NULL, +
-  CHANGE COLUMN tag tag varchar(64) NULL; +
-DELETE FROM version WHERE TABLE_NAME='trusted'; +
-INSERT INTO version (`table_name`, `table_version`) VALUES ('trusted','6'); +
- +
--- table: uacreg +
-ALTER TABLE uacreg +
-  ADD COLUMN reg_delay int(11) NOT NULL DEFAULT '0', +
-  ADD COLUMN flags int(11) NOT NULL DEFAULT '0'; +
-DELETE FROM version WHERE TABLE_NAME='uacreg'; +
-INSERT INTO version (`table_name`, `table_version`) VALUES ('uacreg','2'); +
- +
 </code> </code>
install/upgrade/stable-to-devel.1456659852.txt.gz · Last modified: 2016/02/28 12:44 by miconda