Well, the way we implemented ‘persistence’ was by applying a different thinking. The goal is to allow live software updates without disrupting traffic. With MediaProxy one can shutdown gracefully a relay by allowing it to carry on finishing existing calls and then shutdown while the traffic is handled by other relays. This way one can upgrade the software on a relay farm without dropping a single call.
Adrian On 28 May 2014, at 03:04, Bogdan-Andrei Iancu <bog...@opensips.org> wrote: > Saul, > > the "carrier grade" features are mainly referring to HA and persistenceacross > restarts. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 27.05.2014 23:07, Saúl Ibarra Corretgé wrote: >> On May 27, 2014, at 4:29 PM, Bogdan-Andrei Iancu wrote: >> >>> Brett, you put the finger on the wound :) >>> >>> I looked around to other alternatives (to avoid re-inventing the wheel) - >>> like mediaproxy or rtpengine - and I saw no carrier-grade features in the >>> there - please correct me if I'm wrong. >>> >>> I'm looking to see if the problem is correctly identified and if there is a >>> large consent in the community about this need. As we would like to through >>> some resources into this (hopefully other parties too), as ideally we >>> should be going in the right direction :) >>> >> What "carrier grade" features are those? >> >> -- >> Saúl Ibarra Corretgé >> AG Projects >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > _______________________________________________ > Devel mailing list > de...@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
