<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:windowtext'>Speaking just for myself. <o:p></o:p></span></p><p class=MsoNormal><span style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:windowtext'>As opensips gains traction in production systems, the error when the rules are not loaded should be more clear, now it is : “No information available for dpid “. <o:p></o:p></span></p><p class=MsoNormal><span style='color:windowtext'>Secondly, this problem/issue is not trivial to find, therefore this should be seen in the logs on very low loglevels (0 or 1).<o:p></o:p></span></p><p class=MsoNormal><span style='color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:windowtext'>BR, <o:p></o:p></span></p><p class=MsoNormal><span style='color:windowtext'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:windowtext'>From:</span></b><span style='color:windowtext'> Users <users-bounces@lists.opensips.org> <b>On Behalf Of </b>Liviu Chircu<br><b>Sent:</b> Thursday, July 4, 2019 10:07 AM<br><b>To:</b> users@lists.opensips.org<br><b>Subject:</b> Re: [OpenSIPS-Users] problem in dialplan<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><tt><span style='font-size:10.0pt'>The issue was cleared off-list. After a successful startup, it would</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>take a while before the dialplan rules would become available, since child</tt><br><tt>process #1, responsible for loading the dialplan rules was stuck in</tt><br><tt>a DNS lookup while loading the drouting rules.</tt></span><o:p></o:p></p><p><tt><span style='font-size:10.0pt'>This behavior was introduced in OpenSIPS 2.4.</span></tt><o:p></o:p></p><p><tt><span style='font-size:10.0pt'>As I see it, an added problem is that script writers must now additionally</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>write opensips.cfg code that handles the "rules are not yet available"</tt><br><tt>case while processing SIP traffic. And I do not recall any support for</tt><br><tt>distinguishing between "rules not available" and "rule not matched" in any</tt><br><tt>of the data matching modules.</tt></span><o:p></o:p></p><p><tt><span style='font-size:10.0pt'>The question is: is this "post-startup data unavailability" glitch</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>something worth paying attention to, or is it harmless? Example affected</tt><br><tt>modules:</tt></span> drouting, dialplan<o:p></o:p></p><pre>Liviu Chircu<o:p></o:p></pre><pre>OpenSIPS Developer<o:p></o:p></pre><pre><a href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><o:p></o:p></pre><div><p class=MsoNormal>On 02.07.2019 19:51, johan de clercq wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Users mailing list<o:p></o:p></pre><pre><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><o:p></o:p></pre><pre><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><o:p></o:p></pre></blockquote></div></body></html>