Re: [SR-Users] State-full failover Kamailio+RTPProxy

Hello, accounting using acc module just work fine if both servers write to same database, there is nothing to sync in states between active and standby server. For rtpproxy, afaik, there is no hot HA system offered by the application. For rtpengine, there were some patches circulating around here (iirc, sent by Carsten Bock) to use a redis server for active-standby sync. Also, because each call uses at least 4 ports, be sure that the standby stays clean of other apps that can use ports which can be used by the active server. On the other hand, rtpproxy is rather basic UDP forwarder, unlikely to crash. If you use rtpproxy on another system than kamailio, then you are achieving the availability required by most of the services out there. You should just use many rtpproxy at once, kamailio is able to work with all of them (actually, this is recommended if you want to use properly the CPU cores, because rtpproxy is single process application). If you want to put the rtpproxy server in maintenance, use another host with rtpproxy, reconfigure kamailio to use them and let the old ones running for a while so existing calls keep going fine. Over the time, I got to the conclusion that replicating a lot of states during normal operations adds more overhead and problems than finding specif solutions for particular very rare cases. Have in mind that rtp stream means a lot of small packets, it is better to keep the handling of them as simple as possible not to affect the QoS. Cheers, Daniel On 15/12/15 19:02, Frank Costeira wrote: -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu