You know what I do?<div><br></div><div>I add append_hf("GW: BLAH") and change BLAH for each step in the if blocks.</div><div><br></div><div>Then you can grab a tcpdump and see your custom header. This has helped me ENORMOUSLY during testing to track packet flow.</div>
<div><br></div><div>I prefer looking at the packets themselves and the custom headers rather than searching through the logs.</div><div><br></div><div>It's a bit time consuming to add all the append_hf lines in nearly every if () block, but man, after a while I started "seeing" the code :)<br>
<br><br><div class="gmail_quote">On Tue, Feb 22, 2011 at 11:54 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;">
Tyler,<div><br></div><div>Yes, I have already thought the same thing. However that 403 SIP Message didn't land there in the main routing block, yet through pcap traces I could see the SIP Message being routed to the end-user client. I had this basic log of every new messages routed to the main route, for example:</div>
<div><br></div><div>============</div><div>route {</div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div># Simple Log</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div>xlog("L_INFO", "#### M=$rm RURI=$ru F=$fu USR=$tU T=$tu IP=$si ID=$ci\n");</div></blockquote>....<br><div>============</div><div><br></div><div>I don't see 403 message landed there.</div><div>
<br></div><div>I tried to add logic of something like this on main route:</div><div><br></div><div>============</div><div><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:40px;border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<div># Detect if SIP/2.0 403 Message</div><div>if ( status == "403" ) {</div></blockquote><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:40px;border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:40px;border-top-style:none;border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<div>xlog("got SIP 403");</div></blockquote>}</blockquote></div><div>============<br><br></div><div>Unfortunately, realized that the "status" reference of current message would only work for the onreply route.... I'm sure there is reason for it, most likely developers might can answer that.</div>
<div><br></div><div>-Jason</div><div><br></div><div><div><div></div><div class="h5"><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 9:10 PM, Tyler Merritt <span dir="ltr"><<a href="mailto:tyler@fonality.com" target="_blank">tyler@fonality.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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"><div><div></div><div>On Tue, Feb 22, 2011 at 10:09 AM, Jason Yeh <span dir="ltr"><<a href="mailto:jason@streamoso.com" target="_blank">jason@streamoso.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
<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></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">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>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>Regards,<br><br>Jason Yeh<br>Co-Founder & CEO<br>Streamoso, LLC.<br><br>This e-mail, including any attachments may contain information that is protected by law as PRIVILEGED AND CONFIDENTIAL and is intended solely for the use of the recipient or the employee or agent responsible for delivering the message to the recipient. Please note that if you are not the intended recipient, you are hereby notified that any dissemination, copying, distribution, retention, re-transmission, printing or any other use of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail communication in error, please immediately send an e-mail reply to notify the sender and immediately and permanently delete this e-mail from your computer system. Thank you.<br>
</div>
</blockquote></div><br></div>