The page contains the details about the changes that were made to old components during the development of v5.2.0 compared with what existed in v5.1.x. It does not include the brand new modules, focusing on how to upgrade database and configuration file from v5.1.x to run with Kamailio devel.

If you look for the guidelines to upgrade to previous stable release, see:

• Upgrade Kamailio v5.0.x to v5.1.0

Following tokens are used to mark the changes:

• INF - the change doesn't really have any direct impact - no action required in old config
• 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
• UPG - the change has to be done, older config does not work any longer

UPG: Several parameters that were used to specify AVP names were removed, you have to remove the appropriate config modparams:

modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
modparam("dispatcher", "attrs_avp", "$avp(AVP_ATTRS)")

Starting with v5.2.0, the module is using XAVPs instead of those AVPs, the related parameters are:

• xavp_dst
• xavp_dst_mode
• xavp_ctx
• xavp_ctx_mode

See: https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html

• none

• none

Run following SQL statements in MySQL client to upgrade database structure from v5.1 to v5.2:

ALTER TABLE presentity ADD COLUMN ruid VARCHAR(64);
CREATE UNIQUE INDEX ruid_idx ON presentity (ruid);
UPDATE version SET table_version=5 WHERE TABLE_NAME='presentity';