<div dir="ltr"><div dir="ltr">Hi Diptesh ,<br><div><br></div><div>Thanks for your reply.</div><div><br></div><div>Apologies, I'm using the term 'blacklist' to generally mean that the endpoints are not available.</div><div><br></div><div>Also, the 502 Bad Gateway is response to an INVITE, not SIP OPTIONS, returned by the far end and the ITSP is just passing that back to us, because the call has failed. For such call failures, I'm not expecting for the dispatcher endpoints to be marked as unavailable for routing.</div><div><br></div><div>I am not using, or have not set, the '<b>ds_define_blacklist (str)</b>' option in my dispatcher module config.</div><div><br></div><div>My probing mode is:</div><div><br></div><div>modparam("dispatcher", "ds_probing_mode", 1)<br></div><div><br></div><div>I'm not seeing anything in the logs regarding the dispatcher nodes going into Probing mode - should there be logs for that, or can it be enabled to be logged?</div><div><br></div><div>When I check the endpoints with '
opensipsctl dispatcher dump' they always seem to be '<b>Active</b>' - so it is either they are like that, or they may have only been in '<b>Probing</b>' mode very briefly. Again, I was hoping to see mode/state change in the historical logs. </div><div><br></div><div>In my <b>opensips.cfg</b> (which was created for me) I can see the following code, which looks like this is where it is introducing this behaviour in question:</div><div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><font face="monospace">failure_route[call_failover]</font></div></div><div><div><font face="monospace">{</font></div></div><div><div><font face="monospace"> xlog("[$ci] call failed to established with $T_reply_code code\n");</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> rtpproxy_unforce("$avp(rtpp_set)");</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> if (t_was_cancelled()) {</font></div></div><div><div><font face="monospace"> t_reply("487","Request cancelled");</font></div></div><div><div><font face="monospace"> exit;</font></div></div><div><div><font face="monospace"> }</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> # any failure indication ?</font></div></div><div><div><font face="monospace"> if ( t_check_status("[56][0-9][0-9]")</font></div></div><div><div><font face="monospace"> || (t_check_status("408") && t_local_replied("all"))</font></div></div><div><div><font face="monospace"> ) {</font></div></div><div><div><font face="monospace"> xlog("[$ci] destination $rd failed with $T_reply_code -> retry\n ");</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> <b style="background-color:rgb(255,255,0)"><font color="#ff0000"> ds_mark_dst("p");</font></b></font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> if ( ds_next_domain() ) {</font></div></div><div><div><font face="monospace"> xlog("[$ci] using new destination <$rd>\n ");</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> # send it out again</font></div></div><div><div><font face="monospace"> t_on_failure("call_failover");</font></div></div><div><div><font face="monospace"> t_relay();</font></div></div><div><div><font face="monospace"> exit;</font></div></div><div><div><font face="monospace"> } else {</font></div></div><div><div><font face="monospace"> xlog("[$ci] no other destination to retry\n ");</font></div></div><div><div><font face="monospace"> t_reply("503","Service not available");</font></div></div><div><div><font face="monospace"> exit;</font></div></div><div><div><font face="monospace"> }</font></div></div><div><div><font face="monospace"> }</font></div></div><div><div><font face="monospace"><br></font></div></div><div><div><font face="monospace"> # if call failure, allow the reply to propagate to caller</font></div></div><div><div><font face="monospace"> exit;</font></div></div><div><div><font face="monospace">}</font></div></div></blockquote><div dir="ltr"><div><br></div><div><br></div><div>Thank you for the tip about the
'modparam("dispatcher", "options_reply_codes", "502")' option. I will try that if it is not recommend to change the above code.</div><div><br></div><div>Thank you.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 8 Jun 2020 at 10:47, Diptesh Patel <<a href="mailto:diptesh.patel@ecosmob.com">diptesh.patel@ecosmob.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello Solarmon,<div><br></div><div>Need some clarification on term blacklisting, Are you using the blacklist for Probing Mode of destination? or Are you using the <b>'ds_define_blacklist (str)' </b>parameter. If you are not using the blacklist parameter then below information help you. It is great if you share your script snippet and output of <b>'opensipsctl dispatcher dump'</b> which shows you the current status of your destinations.</div><div><br><div>If you are getting success(200 OK) response on OPTIONS then it is not possible that you got a negative response from a destination and it will not be blacklisted(probing mode) in dispatcher until you blacklist(probing mode) from the script using 'ds_mark_dst()' exported function. I doubt that you are also getting '502 Bad Gateway' on OPTIONS which is sending to the destination to check the availability. If It is right and you want to add the 502 response as a good response for OPTIONS. you can add the 502 as <b>'modparam("dispatcher", "options_reply_codes", "502")'.</b></div><div><b><br></b></div><div><div><div dir="ltr"><div dir="ltr"><div><div>Thanks & Regards</div><div dir="ltr"><b>Diptesh Patel</b><div>Software Developer </div><div>Ecosmob Technologies Ltd, </div><div>Ahmedabad</div><div>Mo:<b>+919898962659</b></div></div></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 8, 2020 at 2:24 PM solarmon <<a href="mailto:solarmon@one-n.co.uk" target="_blank">solarmon@one-n.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi,<br><div><br></div><div>I'm trying to understand whether this is the correct or expected behaviour.</div><div><br></div><div>We have two destinations configured in Dispatcher.</div><div><br></div><div>What I am noticing is that when we receive 502 Bad Gateway messages (logged as <span style="background-color:rgb(248,249,250);color:rgb(32,33,36);font-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap">("call failed to established with 502 code") </span>from both endpoints. After both endpoints have returned 502 Bad Gateway, opensips pass back 503 Service Unavailable back to the originating endpoint of the call. However, subsequent calls are being immediately rejected with 480 Temporarily Unavailable (logged as <span style="background-color:rgb(248,249,250);color:rgb(32,33,36);font-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap">"failed to find an available destination, rejecting") for a period of time.</span></div><div><br></div><div>It seems that opensips is blacklisting the Dispatcher endpoints because of receiving the 502 Bad Gateway messages. Is this the correct/expected behaviour? I would have thought the blacklisting should be based on the SIP OPTIONS sent to the Dispatcher endpoints.</div><div><br></div><div>I do not currently see any issues with SIP OPTIONS to these endpoints so I'm confused as to why they are seemingly blacklisted.</div><div><br></div><div>If this is the correct/expected behaviour, can it be changed to only blacklist based on the SIP OPTIONs pings?</div><div><br></div><div>Thank you.</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" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>
<br>
<div><font face="Arial" size="2" style="background-color:white" color="#808080"><b>Disclaimer</b></font></div><div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small">In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded.</span></div></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><br></span></div><div><font face="Arial" size="2" style="background-color:white" color="#808080"><b>Confidentiality</b></font></div><div><font face="Arial" size="2" style="background-color:white" color="#808080">This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error.</font></div><div><font face="Arial" size="2" style="background-color:white" color="#808080"><br></font></div><div><span style="background-color:white;color:rgb(128,128,128);font-family:Arial;font-size:small"><b>Caution for viruses, malware etc.</b></span></div><div><font face="Arial" size="2" style="background-color:white" color="#808080">This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems. </font></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" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div></div>