<div dir="ltr">Hi Liviu<br><div><br></div><div>Thanks for the tip about the $shv global variables. The link you gave is for 3.1.x, I found the equivalent for 2.4.x which is the version I'm currently using. Is the 'drain' feature also included in this 2.4.x implementation?<br></div><div><br></div><div>Do you have any specific examples of how to do this 'drain' mode?</div><div><br></div><div>When I try the 'opensipsctl fifo shv_get debug' on my opensips server I get the following error:</div><div><br></div><div>500 command 'shv_get' not available<br></div><div><br></div><div>I assume I need to have the '<span style="color:rgb(0,0,0);font-family:Helvetica,Arial;font-size:12px;text-align:justify">cfgutils</span><span style="color:rgb(0,0,0);font-family:Helvetica,Arial;font-size:12px;text-align:justify">' </span>module enabled and loaded for it to work?</div><div><br></div><div>Thank you.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 20 Jan 2020 at 15:03, Liviu Chircu <<a href="mailto:liviu@opensips.org">liviu@opensips.org</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>
<p><tt>Hi solarmon,<br>
</tt></p>
<p><tt>I don't immediately recall such a mechanism in any of the
modules / core logic.<br>
However, you have the often underrated $shv global variables,
which allow you<br>
can implement some remarkable piece of logic! For example:</tt></p>
<p><tt>* "drain" mode, where the server stops accepting new calls,
in preparation<br>
for maintenance<br>
* test out a feature or a change in production while retaining
the ability to quickly<br>
revert back if things go south (optionally, you can do this
for a subset of users!)<br>
</tt></p>
<p><tt>Best regards,<br>
</tt></p>
<p><tt>[1]: </tt><tt><a href="https://opensips.org/html/docs/modules/3.1.x/cfgutils.html#mi_shv_set" target="_blank">https://opensips.org/html/docs/modules/3.1.x/cfgutils.html#mi_shv_set</a></tt></p>
<pre cols="72">Liviu Chircu
<a href="http://www.twitter.com/liviuchircu" target="_blank">www.twitter.com/liviuchircu</a> | <a href="http://www.opensips-solutions.com" target="_blank">www.opensips-solutions.com</a>
OpenSIPS Summit, Amsterdam, May 2020
<a href="http://www.opensips.org/events" target="_blank">www.opensips.org/events</a>
OpenSIPS Bootcamp, Miami, March 2020
<a href="http://www.opensips.org/training" target="_blank">www.opensips.org/training</a></pre>
<div>On 20.01.2020 16:54, solarmon wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,<br>
<div><br>
</div>
<div>I have an opensips two node cluster, and using the
dispatcher module for 'internal' and 'external' endpoints.</div>
<div><br>
</div>
<div>What is the recommended graceful method to put this
opensips cluster in maintenance so that current calls are not
affected. The overall effect I am looking for is for the
opensips cluster not to respond to SIP Options pings from the
endpoints.</div>
<div><br>
</div>
<div>Is it a simple case of making these endpoints 'inactive'?
Will this tell opensips not to respond to SIP Options pings
FROM those endpoints?</div>
<div><br>
</div>
<div>Thank you.</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</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>