Thanks for the advice. Krish<br><br><div class="gmail_quote">On Tue, Mar 6, 2012 at 10:35 AM, Henning Westerholt <span dir="ltr"><<a href="mailto:hw@kamailio.org">hw@kamailio.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tuesday 06 March 2012, Krishna Kurapati wrote:<br>
> It finally worked. I reconstructed the config file step by step with the<br>
> same modparam() and it worked. Still not sure what really was wrong<br>
> before.<br>
><br>
> The other day, I tried to create routes for sending asynchronous messages<br>
> to web service and the entire system stopped working. The routes became<br>
> empty. The config parser never complained. I rebuilt the config file and<br>
> checked to see if the file is ok by running Kamailio step by step. I could<br>
> not trust kamailio config check since it is the one that threw me off<br>
> track.<br>
><br>
> Are there any best practices out there in constructing long config file?<br>
> Is it possible to create smaller modular config files and link them to<br>
> create the system? Or a better tool to identify errors in the config file?<br>
<br>
</div>Hi Krishna,<br>
<br>
just some small suggestions, I'd suggest that you modularize your cfg in<br>
smaller parts by using sub-routes which you call then from the main routing<br>
logic. You can also use the "include" directive to move certain parts of the<br>
configuration to separate files.<br>
<br>
Viele Grüße/ best regards,<br>
<br>
Henning Westerholt<br>
</blockquote></div><br>