On Thu, Dec 22, 2022 at 12:05 PM Maxim Sobolev <[email protected]> wrote:
> Terrance, > > Both are actively maintained & developed with a slightly different focus. > Speaking of k8s in particular you might want to check presentation done by > Liviu Chircu at the last OpenSIPS summit here: > > https://youtu.be/JwO0UmauuT4?t=13034 > > Most of the stuff he talked about would apply to Kamailio as well. > > -Maksym > > On Thu, Dec 22, 2022, 6:40 AM Terrance Devor <[email protected]> wrote: > >> Wow gents! I really appreciate the input here. As to why we are doing >> this? It's because we have all our applications deployed to the k8s >> instance and it's easier for us to maintain/migrate once the heavy initial >> lifting has been completed. >> >> On the note of RTPProxy vs RTPEngine, which of the 2 is actively >> being developed and maintained. I am coming from the MediaProxy days.... >> >> Lastly, if this is a project that you are interested in working on, and >> confident we can successfully deploy I would be very happy to hear from >> you. (Hope I am not breaking any mailing list rules here....) >> >> Terrance >> >> On Thu, Dec 22, 2022 at 5:35 AM Alex Balashov <[email protected]> >> wrote: >> >>> I would have to agree with Henning that this may be more trouble than >>> it's worth, particularly when it comes to the bottom-line result. >>> >>> — >>> Sent from mobile, apologies for brevity and errors. >>> >>> On Dec 22, 2022, at 2:22 AM, Henning Westerholt <[email protected]> wrote: >>> >>> >>> Hello, >>> >>> we have done some projects in this area. Its some work, but doable. The >>> benefits of k8s are not that great for this kind of applications and you >>> will not achieve a perfect isolation (security/network level). >>> >>> As a note, you probably want to use rtpengine instead of rtpproxy. >>> >>> Cheers, >>> >>> Henning >>> >>> ------------------------------ >>> *Von:* Terrance Devor <[email protected]> >>> *Gesendet:* Donnerstag, 22. Dezember 2022, 04:35 >>> *An:* [email protected] <[email protected]> >>> *Betreff:* [SR-Users] Dockerized VoIP Stack >>> >>> Hello Everyone, >>> >>> Does anyone have experience in deploying Kamailio, Asterisk and RTPProxy >>> to a dockerized environment with K8s? >>> >>> In short, we are looking to deploy the following applications to our >>> Kubernetes environment to support a SIP based PBX for our company: >>> - Kamailio (Sip Proxy with DID, Outbound, edge routing and LB >>> capabilities) >>> - Asterisk Realtime (PBX, IVR) >>> - RTPProxy (Media Relay) >>> >>> Has anyone been successful, or failed, in doing this? I would love to >>> hear from you. >>> >>> Terrance >>> >>> __________________________________________________________ >>> Kamailio - Users Mailing List - Non Commercial Discussions >>> To unsubscribe send an email to [email protected] >>> Important: keep the mailing list in the recipients, do not reply only to >>> the sender! >>> Edit mailing list options or unsubscribe: >>> >>> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> To unsubscribe send an email to [email protected] >> Important: keep the mailing list in the recipients, do not reply only to >> the sender! >> Edit mailing list options or unsubscribe: >> > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > Maxime, thank you for not calling me out on the cross-thread (mailing list) post. We have been trying to get this deployed into our kubernetes cluster for a year now, really appreciate the support from the community.
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
