<div dir="ltr">Hi Liviu,<div><br></div><div>I took and used the 'recommended' config as advised at <a href="https://blog.opensips.org/2018/03/23/clustering-ongoing-calls-with-opensips-2-4/">https://blog.opensips.org/2018/03/23/clustering-ongoing-calls-with-opensips-2-4/</a></div><div><br></div><div>Having to rely on an(other) script to 'fix' the issue does not sound like a good idea, but I'll look into it further and try to understand it.</div><div><br></div><div>Thank you.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 13 Jul 2021 at 12:59, 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>
    <div>On 25.06.2021 15:12, solarmon wrote:<br>
    </div>
    <blockquote type="cite">
      <div>The typical recommended configuration for an active/standby
        setup would be:</div>
      <div><br>
      </div>
      node1:<br>
      <div>
        <div>
          <p id="gmail-m_4516428698236715009gmail-u18543fcc" style="margin:0px;padding:0px;min-height:24px"><span>modparam("dialog",
              "dlg_sharing_tag", "vip=active")</span></p>
          <p id="gmail-m_4516428698236715009gmail-u06231fc1" style="margin:0px;padding:0px;min-height:24px"><br>
          </p>
          <p id="gmail-m_4516428698236715009gmail-u06231fc1" style="margin:0px;padding:0px;min-height:24px">node2:</p>
          <p id="gmail-m_4516428698236715009gmail-ua5e15d78" style="margin:0px;padding:0px;min-height:24px"><span>modparam("dialog",
              "dlg_sharing_tag", "vip=backup")</span></p>
          <br>
          <p id="gmail-m_4516428698236715009gmail-ua5e15d78" style="margin:0px;padding:0px;min-height:24px">How can this
            be properly resolved or managed for these situations where
            you want to take down an opensips node for maintenance?</p>
        </div>
      </div>
    </blockquote>
    <p><font face="monospace">Hi,<br>
      </font></p>
    <p><font face="monospace">Actually, I would recommend starting with
        "backup / backup" (!!) to prevent exactly the scenario you
        described above, where you take down the former-active node for
        maintenance, yet it boots in "active" mode, completely opposite
        to the state of the VIP.</font></p>
    <p><font face="monospace">Now, in order to fix the state where both
        tags are in "backup" mode, you'd deploy an external check-script
        that periodically scans the tag statuses and fixes a "backup"
        tag to "active" whenever a box owns the VIP.</font></p>
    <p><font face="monospace">Best Regards,</font><br>
    </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 2021 Distributed | <a href="http://www.opensips.org/events" target="_blank">www.opensips.org/events</a></pre>
  </div>

</blockquote></div>