<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello all,<br>
<br>
This is an informative email, related to a known issue currently
present on the <b>1.9</b> branch. Since the fix also implies making
structural table changes, it will only be present in the upcoming
major release.<br>
<br>
Going into the details, the problem is related to storing the <b>branch
flags</b> of all contacts in the <b><i>location</i></b><b> <i>table</i></b>.
If the script is changed (in a way that <i>adds</i> branch flags,
or <i>interchanges</i> some branch flag assignments), all the
branch flag bitmasks of the contacts stored in the location table
suddenly have no meaning (in other words, they are now<i> corrupt</i>).<br>
<br>
<b>Symptoms</b>: If the server is restarted using the new script,
contacts may either be loaded with undesired branch flags, or some
of them may not be set (maybe a "DO_NAT" bflag will be missing).<br>
<br>
<b>Workaround</b>: If the script changes in the way described above
(<i>more/less</i> bflags or different b-flags are <i>assigned/cleared</i>
in a new order), <b>all the contacts</b> in the location table <b>must
be </b><b>purged</b> before restarting opensips.<br>
<br>
The issue will be addressed on the working branch, but we prefer not
to propagate the changes to the 1.9 branch because the (only)
solution is not quite backwards-compatible.<br>
<br>
We will soon create a "Known Issues" page in the <i>Manuals</i>
section of the <i>OpenSIPS Documentation</i> [1] to better inform
everyone of such details.<br>
<br>
Best regards,<br>
Liviu<br>
<br>
[1]:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://www.opensips.org/Documentation/Manuals">http://www.opensips.org/Documentation/Manuals</a>
</body>
</html>