Hi,<br><br>I use a modified version of functions db_check_from() and db_check_to() from the "uri" module. See <span><strong>patch upload </strong></span><span><strong>3076779.</strong></span> This adds a "q" option so that parse errors don't end up in syslog and an "e" option to only check for well-formed-ness, not actually check the db.<br>
<br>Regards,<br>Kennard<br><br><div class="gmail_quote">On Fri, Feb 11, 2011 at 2:57 PM, thrillerbee <span dir="ltr"><<a href="mailto:thrillerbee@gmail.com">thrillerbee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>What is the easiest way to identify traffic with invalid headers? Specifically, the from and to URIs.<br></div><div>For example, if OpenSIPS is unable to parse a from URI, would $fu be NULL?</div><div><br></div><div>
Thanks.</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>