[OpenSIPS-Users] problem in dialplan

[johan de clercq]

Speaking just for myself. 

 

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 “.  

Secondly, this problem/issue is not trivial to find, therefore this should be seen in the logs on very low loglevels (0 or 1).

 

BR,    

 

From: Users <users-bounces at lists.opensips.org> On Behalf Of Liviu Chircu
Sent: Thursday, July 4, 2019 10:07 AM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] problem in dialplan

 

The issue was cleared off-list.  After a successful startup, it would
take a while before the dialplan rules would become available, since child
process #1, responsible for loading the dialplan rules was stuck in
a DNS lookup while loading the drouting rules.

This behavior was introduced in OpenSIPS 2.4.

As I see it, an added problem is that script writers must now additionally
write opensips.cfg code that handles the "rules are not yet available"
case while processing SIP traffic.  And I do not recall any support for
distinguishing between "rules not available" and "rule not matched" in any
of the data matching modules.

The question is: is this "post-startup data unavailability" glitch
something worth paying attention to, or is it harmless?  Example affected
modules:  drouting, dialplan

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 02.07.2019 19:51, johan de clercq wrote:





_______________________________________________
Users mailing list
Users at lists.opensips.org <mailto:Users at lists.opensips.org> 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190704/ec307c15/attachment.html>