Upgrade from 3.0.x to 3.1.x

Note: 3.1.x has not been released it, target date is September 2010. Until then, 3.1.x means GIT master branch (development version).

3.0.x refers to Kamailio releases 3.0.x and SR branch sr_3.0.

• a new column in address table to hold a tag value per record. The value is returned in peer tag avp upon address matching.

• no timer parameters value adjustments - they are milisecond, therefore make sure the values of fr_inv_timer, fr_timer are given in mili-seconds otherwise you get a very fast timeout. Note that dynamic timeout values given via avps for each transaction are still in seconds. You can use t_set_fr(…) functions with milisecond parameters as alternative to avps.
• new parameter failure_reply_mode to control winning branch selection (reply code) for failure_route - if you used kamailio config, be sure you set this parameter to 3 in order to have same behavior as in 1.5.x or lower and 3.0.x. Otherwise, see t_drop_replies() function to control the behaviour per transaction inside config file, within failure_route.

• Major rewrite: lcr and gw tables have been replaced by lcr_rule, lcr_rule_target, and lcr_gw tables. Upgrade script is available as http://box.openxg.com/tmp/lcr_upgrade_from_3.0.sh.
• A rule can be specified as a "stopper" rule meaning that no shorter prefixes will be tried if "stopper" rule matches.
• A rule may be marked as "disabled".
• Added new gateway property: URI parameters.
• Gateway IP address can be NULL, if hostname is not NULL.
• If gateway IP address is NULL, all test functions fail on that LCR instance, because for performance reasons, DNS queries are not done and test functions operate only on IP addresses.
• MI functions are not supported anymore; use RPC functions instead.

• Module is now using modules_s/auth api, which means that modules_s/auth module needs to be loaded instead of modules_k/auth module before this module is loaded.
• Functions www_challenge()/proxy_challenge() are not anymore used to send 401/407 responses. See examples in README file on how to send those responses.
• Functions radius_www_authorize()/radius_proxy_authorize() now return a new negative result value -2 if there was something wrong in the request.
• Realm argument must now be always given when radius_www_authorize()/radius_proxy_authorize() functions are called.
• See modules_s/auth for new auth module parameters.

• rl_drop() was dropped (same functionality can be achieved with: append_to_reply() and sl_send_reply() - see the README file.

• rtpproxy functionality was removed from the nathelper module and belongs to the new rtpproxy module - see README files for both modules.

• If configuration parameter "detect_spirals" is set (true by default), spiraling messages will be detected and not cause the creation of another dialog structure. Otherwise, the old behavior of maintaining one dialog per spiral occurrence will be maintained.
• New callback type DLGCB_SPIRALED will be executed on detection of a spiraling message ("detect_spirals" must be enabled, however).

• no effect of config compat mode in core - drop() action is the same all the time
  • drop a reply in onreply route
  • drop the request in onsend route