Henning,<br><br>The issue I'm facing is that, when this happens I get no record on the missed_calls table, but only for this attempt; all other attempts are recorded.<br><br>This will impact on teh ASR calculation script we developed and the routing logic that uses those values.<br>
<br>Do you think it was fixed on 1.5?<br>Uriel<br><br><div class="gmail_quote">On Mon, Mar 30, 2009 at 9:38 AM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Monday 30 March 2009, Uriel Rozenbaum wrote:<br>
> Kamailio is printing this error when it reaches the last failure_route.<br>
> I've left next_domain empty on all last routes.<br>
><br>
> Let me know if you need some piece of the cfg or something (I sent some on<br>
> a later mail).<br>
<br>
</div>Hi Uriel,<br>
<br>
the ERROR message you've reported is not a real problem. Its severity was<br>
changed to INFO in the 1.4.4 release, i also rephrased it a bit (r5426). Now<br>
its behaves exactly like the "normal" routing.<br>
<br>
This message is reported when cr fails to lookup a route, i.e. no more<br>
(failure) routes are available, or can be matched against the message<br>
content/ flags.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>