<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello,</p>
    <p>maybe not directly related to the issue, but could be better to
      separate rtpengine on its own system, likely it requires less
      failover scenarios, so active calls are not affected at all if you
      have to do a failover for the signaling server...</p>
    <p>Anyhow, as you trigger a failover and you know it is not going to
      recover the active calls, you can close them via dialog module.</p>
    <p>Cheers,<br>
      Daniel<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 05.01.18 09:45, Karsten Horsmann
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFArqsZYVqnfEDH99x+ruCN4gBMDKCjchTBR=4ZrKktxOYjMTg@mail.gmail.com">
      <div dir="auto">Hi Daniel, 
        <div dir="auto"><br>
        </div>
        <div dir="auto">Yes, they are.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">At this point I using only one redis key space
          for both rtpengines. I just fire it up on the backup machine
          so it reads the RTP sessions from redis.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Both rtpengines had the same configuration. Only
          one is active. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">But I found the nice redis key space separated
          and active / active - multiple rtpengine feature for it. Not
          implemented this at the moment. </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">Am 05.01.2018 8:49 vorm. schrieb
          "Daniel-Constantin Mierla" <<a
            href="mailto:miconda@gmail.com" moz-do-not-send="true">miconda@gmail.com</a>>:<br
            type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <p>Hello,</p>
              <p>are kamailio and rtpenigine on same system?</p>
              <p>Cheers,<br>
                Daniel<br>
              </p>
              <br>
              <div class="m_6533628836130340040moz-cite-prefix">On
                04.01.18 12:21, Karsten Horsmann wrote:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">Hello List,
                  <div><br>
                  </div>
                  <div>and also an happy new year to everyone.</div>
                  <div><br>
                  </div>
                  <div>I use CentOS 7.4.x with kamailio 5.0.5 and
                    rtpengine on a pacemaker/corosync cluster</div>
                  <div>in front of an internal kamailio siprouter and
                    media-services.</div>
                  <div><br>
                  </div>
                  <div>If i did an "pcs node standby" to failover my
                    frontend-kamailio (udp/tcp 5060, udp/tcp 5061-tls
                    and tcp websocket-secure) i noticed the following
                    scenarios:</div>
                  <div><br>
                  </div>
                  <div>1) Plain RTP: just stocks a few seconds and
                    flows. Everything fine.</div>
                  <div>2) SDES/RTP: silence - but REINVITE manually in
                    my client brings audio back. Need improvement.</div>
                  <div>3) DTLS/RTP WebRTC: silence - all clients shows
                    an active call. I know that there is NO way to
                    recover this call - because of the temporay DTLS
                    certificate due the rtpengine start-up.</div>
                  <div><br>
                  </div>
                  <div><br>
                  </div>
                  <div>So i thought - for scenario1) i dont need
                    anything to do. Works nice.</div>
                  <div>For scenario2) i need something to "remember its
                    SDES/RTP calls and send them an REINVITE"</div>
                  <div>And for scenario3) i should just hangup all
                    WebRTC calls - IMHO the best for that.</div>
                  <div><br>
                  </div>
                  <div>How can i fire-up these tasks to get an
                    "clean-up" or "reinvite" after an failover?</div>
                  <div><br>
                  </div>
                  <div>
                    <div><br>
                    </div>
                    <div>scenario legend:</div>
                    <div>
                      <div>1) unencrypted call</div>
                      <div>2) TLS/SDES encrypted call</div>
                      <div>3) DTÖS WebRTC encrypted call</div>
                    </div>
                    <div><br>
                    </div>
                    -- <br>
                    <div class="m_6533628836130340040gmail_signature">Kind
                      Regards<br>
                      *Karsten Horsmann*<br>
                    </div>
                  </div>
                </div>
                <br>
                <fieldset
                  class="m_6533628836130340040mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
Kamailio (SER) - Users Mailing List
<a class="m_6533628836130340040moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org" target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a>
<a class="m_6533628836130340040moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a>
</pre>
              </blockquote>
              <br>
              <pre class="m_6533628836130340040moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="m_6533628836130340040moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank" moz-do-not-send="true">www.twitter.com/miconda</a> -- <a class="m_6533628836130340040moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank" moz-do-not-send="true">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - <a class="m_6533628836130340040moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank" moz-do-not-send="true">www.asipto.com</a>
Kamailio World Conference - May 14-16, 2018 - <a class="m_6533628836130340040moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank" moz-do-not-send="true">www.kamailioworld.com</a></pre>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - March 5-7, 2018, Berlin - <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
Kamailio World Conference - May 14-16, 2018 - <a class="moz-txt-link-abbreviated" href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>
  </body>
</html>