<div dir="ltr">Mike,<div><br></div><div>I accomplish this with the gflags module. I define a flag for maintenance, say flag 1. I check to see if gflag 1 is set early in the script but after handling any in-dialog requests. If it is set, I return a 503 and leave it to the client to go to the next server. If it is not set, I process the call as normal.</div><div><br></div><div>If you wanted to have server-side control of where the call goes, you may be able to use a 302 instead.</div><div><br></div><div>I set the flag with opensipsctl fifo set_gflags.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 10, 2014 at 12:14 PM, Mike Kane <span dir="ltr"><<a href="mailto:kanem1@gmail.com" target="_blank">kanem1@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 dir="ltr"><div>Hello all, is there a concept of placing Opensips in maintenance mode where all ongoing call will be processed, but any new requests will be diverted to another instance of Opensips. I thought I had read a thread on this in relation to the DR module at one point.<br><br></div>Thanks Mike <br></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></div>