No problem Richard. It’s not trivial to spot. And indeed, using an event route is probably the solution of your problem.
From: Users <[email protected]> On Behalf Of Richard Revels Sent: Thursday, July 11, 2019 2:58 PM To: OpenSIPS users mailling list <[email protected]> Subject: Re: [OpenSIPS-Users] problem in dialplan We are using dialplan to create some site specific defaults in the startup route. If this is only encountered on startup I guess changing to an event route would work if an event is generated when the rules become available. Thank you for surfacing this problem. It may explain an issue I've been looking at for the last few hours. <https://lh6.googleusercontent.com/RHbmOLdT6iYkO7QryjK_2Cp5MZ6rur2H4QGOu09yDtXiT6OXl687J-UpI-8Bt2aDI_EA4WKBBpCrPWaIWdF5RkhjruxRoI7GfYE89_m8r2IBg73T8mPpsJOOOJylFwGMVNyuXZZ2> Richard Revels • System Architect II 900 Main Campus Drive, Suite 100, Raleigh, NC 27606 m: 919-578-3421 • o: 919-727-4614 e: [email protected] <mailto:[email protected]> On Thu, Jul 4, 2019 at 4:21 AM johan de clercq <[email protected] <mailto:[email protected]> > wrote: 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 <[email protected] <mailto:[email protected]> > On Behalf Of Liviu Chircu Sent: Thursday, July 4, 2019 10:07 AM To: [email protected] <mailto:[email protected]> 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 [email protected] <mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] <mailto:[email protected]> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
