Opensips+ RTPProxy only works fine with plain LXC containers, privileged, which basically have access to all the resources of the box. That is the model I use with great success.
On Tue, Dec 20, 2022 at 2:47 PM Brett Nemeroff <br...@nemeroff.com> wrote: > > Hello Terrance, > I wouldn't really recommend this. RTPProxy is going to use a lot of ports in > a very large range. That just doesn't work great in docker, but even worse in > K8S. > > I personally would put the RTPProxy outside of K8S. While you might be able > to get it to work, you are likely going against some basic design concepts in > containerization. I feel like the tech should propel the solution and not be > a hindrance to it. In this case, I'm not sure that K8S is buying you anything > of value, but instead creating architectural challenges. > > I'd love to hear feedback or experiences from others. There's always > something to learn :) > -Brett > > On Tue, Dec 20, 2022 at 11:43 AM Terrance Devor <ter.de...@gmail.com> wrote: >> >> Was it something I said? >> >> Terrance >> >> On Sun, Dec 18, 2022 at 12:50 PM Terrance Devor <ter.de...@gmail.com> wrote: >>> >>> Hello Everyone, >>> >>> Wow! Blast from the past... I am a long time member of this list, been a >>> while. >>> >>> Question, anyone successful in deploying RTPProxy to a dockerized >>> environment? Preferably to a Kubernetes managed environment. >>> >>> Please Help Team :) >>> >>> Kind Regards, >>> Terrance >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
