<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<pre>This message was generated by the Security Alerts service ( Free Trial 14th of August - 14th of September )
<a class="moz-txt-link-freetext" href="http://www.opensips.org/Resources/AlertsMain">http://www.opensips.org/Resources/AlertsMain</a>
<b>
SVN commit</b>:
<a class="moz-txt-link-freetext" href="http://opensips.svn.sourceforge.net/opensips/?rev=9177&view=rev">http://opensips.svn.sourceforge.net/opensips/?rev=9177&view=rev</a>
<b>Severity</b>: Medium
<b>Version</b> : all
<b>Affected modules</b> : Load-Balancer module
<b>Effect</b> : Loosing load on destination after a restart
<b>Affected scenarios</b>: If loading (as module) the Dialog module before the Load-Balancer module, during an OpenSIPS restart,
the active load (number of ongoing calls) on the LB destinations will not be restored, but simply set to 0 for all
destinations and resources. This will break the load balancing alg, as OpenSIPS LB will do not "know" the calls established
prior to restart.
Nevertheless, the system will recover in time and start behaving normally once the inherited calls (established before the
restart) are terminated.
<b>Description:</b> The actual problem resides in the dialog module which was not able to properly restore the profile information
for the call loaded from DB at startup time. The interaction between the Dialog and LB module is a bit particular, as the
LB module creates (as init time) dynamic dialog profiles (according to destinations and resources). So, if the Dialog module
is loaded first, it will not know the dialog profiles required by LB, so it will not be able to restore the dialog context.
<b>Risks</b> : have more load on destinations than configured (as upper limit), but limited to a restart event
<b>Update</b> :
- if you have an SVN checkout, 1.7, 1.8 and trunk were fixed; so update to a revision later than 9177 (trunk),
9178 (1.8 branch) or 9179 (1.7 branch).
- if you have OpenSIPS from sources see the attached patch;
- if using tarballs, they were already regenerated (and include the fix). Available only for 1.8.
- If using the official Debian package (apt.opensips.org), they are also re-generated including the fix
(available for 1.8 and trunk).
</pre>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
</body>
</html>