I would do this by matching the method of the packet in the main routing block, and then using textops to search for the 403 in a subsequent if () {} block, and then just drop; or exit;<div><br></div><div>My methods are usually not the most elegant solution - I'll wait for Dave or one of the Devs to chime in with a better method :)<br>
<br><div class="gmail_quote">On Tue, Feb 22, 2011 at 10:09 AM, Jason Yeh <span dir="ltr"><<a href="mailto:jason@streamoso.com">jason@streamoso.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>Hello everyone,</div><div><br></div><div>This certain SIP UAS keeps on sending "SIP/2.0 403" messages to my OpenSIPS machine out of blue, this failure/warning messages has nothing to do with this certain client on the call. I wanted to figure out how to drop ("not proxy") that annoying non-transactional 4XX SIP Messages being routed through this proxy server, however I couldn't figure out where to get this message landed to my routing script. Because the fact that this requests wasn't initially sent by proxy, it will not land to the "failure_route" routing block.</div>
<div><br></div><div>In summary, how can I configure OpenSIPS routing logic to handle the non-transactional 4XX request sent by someone else out of blue?</div><div><br></div><div>Thanks,</div><div>Jason</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>