I'm relatively new to OpenSIPs myself - but in my various experiments - the idea that OS cannot parse a header is a bit foreign. As a SIP proxy - it's job is more to use the routing logic in order to transmit packets from A through to C via B (OS itself).<div>
<br></div><div>I have sent packets with bogus From and To headers and they transmit to the end destination just fine. I don't believe that your answer will be found in the format of the headers. Rather, the best way to detect invalid headers (I think) would be to use TextOps modules and REGEX to act on the headers themselves and detect formats that you say are valid. </div>
<div><br></div><div>OS is flexible enough to do this - plenty of logic in the IF, THEN, ELSE statements within routing blocks in order to check these headers against rules that you assert are "valid".</div><div>
<br></div><div><br><br><div class="gmail_quote">On Sat, Feb 12, 2011 at 7:57 AM, thrillerbee <span dir="ltr"><<a href="mailto:thrillerbee@gmail.com">thrillerbee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;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></div>