<div dir="ltr">If you want to store the state of a Kamailio server you should use db_mode 3. This mode stores everything (even socket information) in the database. In this case using a virtual IP address you can fail over to another server. This can be easily done using Pacemaker and Corosync. I created a simple set of Ansible playbooks that do this for you. Using these scripts you can even create a cluster of load balanced RTPProxy servers.<br><br><a href="https://github.com/ghrst/Kamailio-HA">https://github.com/ghrst/Kamailio-HA</a><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 12:01 PM, Carsten Bock <span dir="ltr"><<a href="mailto:carsten@ng-voice.com" target="_blank">carsten@ng-voice.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
just a quick note:<br>
Our implementation of the REDIS Backend for RTPEngine<br>
(<a href="https://github.com/ngvoice/rtpengine-redis-plugin" rel="noreferrer" target="_blank">https://github.com/ngvoice/rtpengine-redis-plugin</a>) got obsolete, as<br>
RTPEngine supports this functionality now natively without any<br>
external Plugin.<br>
<br>
Thanks,<br>
Carsten<br>
<div><div class="h5"><br>
2015-12-16 9:27 GMT+01:00 Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>>:<br>
> Hello,<br>
><br>
> accounting using acc module just work fine if both servers write to same<br>
> database, there is nothing to sync in states between active and standby<br>
> server.<br>
><br>
> For rtpproxy, afaik, there is no hot HA system offered by the application.<br>
> For rtpengine, there were some patches circulating around here (iirc, sent<br>
> by Carsten Bock) to use a redis server for active-standby sync. Also,<br>
> because each call uses at least 4 ports, be sure that the standby stays<br>
> clean of other apps that can use ports which can be used by the active<br>
> server.<br>
><br>
> On the other hand, rtpproxy is rather basic UDP forwarder, unlikely to<br>
> crash. If you use rtpproxy on another system than kamailio, then you are<br>
> achieving the availability required by most of the services out there. You<br>
> should just use many rtpproxy at once, kamailio is able to work with all of<br>
> them (actually, this is recommended if you want to use properly the CPU<br>
> cores, because rtpproxy is single process application). If you want to put<br>
> the rtpproxy server in maintenance, use another host with rtpproxy,<br>
> reconfigure kamailio to use them and let the old ones running for a while so<br>
> existing calls keep going fine.<br>
><br>
> Over the time, I got to the conclusion that replicating a lot of states<br>
> during normal operations adds more overhead and problems than finding specif<br>
> solutions for particular very rare cases. Have in mind that rtp stream means<br>
> a lot of small packets, it is better to keep the handling of them as simple<br>
> as possible not to affect the QoS.<br>
><br>
> Cheers,<br>
> Daniel<br>
><br>
> On 15/12/15 19:02, Frank Costeira wrote:<br>
><br>
> Hi,<br>
><br>
> I would prefer to maintain the dialog and rtp session, however push come to<br>
> shove maintaining the RTP session would be sufficient.<br>
><br>
> Is it possible to do state-full failover of both the dialog and rtp or just<br>
> rtp?<br>
><br>
> Any recommendations on documentation or how-to to read that would point me<br>
> in the right direction?<br>
><br>
> Thanks<br>
><br>
> Regards<br>
><br>
> On Tue, Dec 15, 2015 at 9:47 AM, Alex Balashov <<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>><br>
> wrote:<br>
>><br>
>> Well, that depends. Is your objective really RTP failover, or also<br>
>> failover of dialog state (e.g. for some accounting purpose)?<br>
>> <br>
>> --<br>
>> Alex Balashov | Principal | Evariste Systems LLC<br>
>> 303 Perimeter Center North, Suite 300<br>
>> Atlanta, GA 30346<br>
>> United States<br>
>><br>
>> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)<br>
>> Web: <a href="http://www.evaristesys.com/" rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.csrpswitch.com/" rel="noreferrer" target="_blank">http://www.csrpswitch.com/</a><br>
>><br>
>> Sent from my BlackBerry.<br>
>> Original Message<br>
>> From: Frank Costeira<br>
>> Sent: Tuesday, December 15, 2015 09:41<br>
>> To: Kamailio (SER) - Users Mailing List<br>
>> Reply To: Kamailio (SER) - Users Mailing List<br>
>> Subject: Re: [SR-Users] State-full failover Kamailio+RTPProxy<br>
>><br>
>><br>
>> _______________________________________________<br>
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
>> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
>> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
><br>
> --<br>
> Daniel-Constantin Mierla<br>
> <a href="http://twitter.com/#!/miconda" rel="noreferrer" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">http://www.linkedin.com/in/miconda</a><br>
> Book: SIP Routing With Kamailio - <a href="http://www.asipto.com" rel="noreferrer" target="_blank">http://www.asipto.com</a><br>
> <a href="http://miconda.eu" rel="noreferrer" target="_blank">http://miconda.eu</a><br>
><br>
><br>
> _______________________________________________<br>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
> <a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
<br>
<br>
<br>
--<br>
</div></div>Carsten Bock<br>
CEO (Geschäftsführer)<br>
<br>
ng-voice GmbH<br>
Schomburgstr. 80<br>
D-22767 Hamburg / Germany<br>
<br>
<a href="http://www.ng-voice.com" rel="noreferrer" target="_blank">http://www.ng-voice.com</a><br>
mailto:<a href="mailto:carsten@ng-voice.com">carsten@ng-voice.com</a><br>
<br>
Office +49 40 5247593-0<br>
Fax +49 40 5247593-99<br>
<br>
Sitz der Gesellschaft: Hamburg<br>
Registergericht: Amtsgericht Hamburg, HRB 120189<br>
Geschäftsführer: Carsten Bock<br>
Ust-ID: DE279344284<br>
<br>
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:<br>
<a href="http://www.ng-voice.com/imprint/" rel="noreferrer" target="_blank">http://www.ng-voice.com/imprint/</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</div></div></blockquote></div><br></div>