It's not easy and takes a long time to perfect, but our entire VoIP infrastructure is Dockerized, and composed of Asterisk, MySQL, Redis, NodeJS and Kamailio+RTPEngine (not rtpproxy, since rtpproxy isn't maintained anymore). No docker-level port forwarding required anywhere, since the entire system is designed to be volatile (see below).

We have over 500 Asterisk docker containers running, supporting many thousands of users across the world at this point, and it works quite well, so it can be done.

The concept behind the Asterisk containers is designing everything to be completely volatile: Outages happen, even in datacenters, so assume a container will reboot at some point on some random node at some random datacenter location. You don't know Asterisk's private IP, you don't even know where it might pop back up in the cluster. If you can ensure service continuity in that scenario, then you've built a solid setup. Our uptime has been 100% for over 4 years now (this is 3rd-party monitored and validated, in addition to our internal monitoring systems) so I assure you it is very possible.

I also HIGHLY recommend not using a cloud provider for any of the core infrastructure. We tried this, with AWS and GCP, and the voip quality was... meh. The cloud outages were frequent, although customers generally don't notice them when you're using lightweight containers to run everything. So we are fully operating on our own hardware across multiple colo locations, and only using cloud for file storage (eFaxes, voicemails, greetings/recordings, MMS content, phone LCD background images for provisioning, etc).

I am unable to help with your project, but I can at least provide the above pointers/experiences in case they get you in the right direction.

An alternative to building your own infrastructure might be reselling (white label) an existing service provider as well, in case the decision to build your own infrastructure is still up in the air.



Luke Escudé


972.600.1150

support@primevox.net

Schedule a meeting!



View the PrimeVOX R&D Roadmap here
View the PrimeVOX Status Page here

From: sr-users-request@lists.kamailio.org <sr-users-request@lists.kamailio.org>
Sent: Thursday, December 22, 2022 9:44 AM
To: sr-users@lists.kamailio.org <sr-users@lists.kamailio.org>
Subject: sr-users Digest, Vol 211, Issue 47
 
Send sr-users mailing list submissions to
        sr-users@lists.kamailio.org

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
        sr-users-request@lists.kamailio.org

You can reach the person managing the list at
        sr-users-owner@lists.kamailio.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sr-users digest..."

Today's Topics:

   1. Re: Dockerized VoIP Stack (Terrance Devor)
   2. Re: Dockerized VoIP Stack (Terrance Devor)
   3. Re: Dockerized VoIP Stack (Terrance Devor)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Dec 2022 09:31:33 -0500
From: Terrance Devor <ter.devor@gmail.com>
Subject: [SR-Users] Re: Dockerized VoIP Stack
To: "Kamailio (SER) - Users Mailing List"
        <sr-users@lists.kamailio.org>
Message-ID:
        <CA+w+2f8CtdwkiDtz+Md-pZz5xA4-59gv768b_vq4bkdjf2V3hw@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="000000000000398ece05f06b87af"

I did see the CyCore project and tried to connect with Laurel Lauson and
Sean McCord on LinkedIn

On Wed, Dec 21, 2022 at 9:18 PM Fred Posner <fred@palner.com> wrote:

> On Dec 21, 2022, at 8:41 PM, Terrance Devor <ter.devor@gmail.com> wrote:
>
>
> Does anyone have experience in deploying Kamailio, Asterisk and RTPProxy
> to a dockerized environment with K8s?
>
>
> Check out some past Kamailio World and Astricon presentations, including
> some from Sean McCord. He even has a GitHub demo:
>
> * https://github.com/CyCoreSystems/asterisk-k8s-demo
>
> -- Fred
> The Palner Group, Inc.
> +1 (212) 937-7844
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-leave@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
> Edit mailing list options or unsubscribe:
>
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 1806 bytes
Desc: not available

------------------------------

Message: 2
Date: Thu, 22 Dec 2022 09:39:23 -0500
From: Terrance Devor <ter.devor@gmail.com>
Subject: [SR-Users] Re: Dockerized VoIP Stack
To: Henning Westerholt <hw@gilawa.com>
Cc: "Kamailio (SER) - Users Mailing List"
        <sr-users@lists.kamailio.org>
Message-ID:
        <CA+w+2f9c+-zvY7f9h9s=zkgFPa2zFfSC2A1=+H3rTxRyEW5-2Q@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="00000000000039c07205f06ba374"

On Thu, Dec 22, 2022 at 2:15 AM Henning Westerholt <hw@gilawa.com> 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
>
>
I would love to know more about RTPEngine vs RTPProxy. Which of the 2 are
actively maintained? Why would you recommend RTPEngine over the other.
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 1741 bytes
Desc: not available

------------------------------

Message: 3
Date: Thu, 22 Dec 2022 09:43:50 -0500
From: Terrance Devor <ter.devor@gmail.com>
Subject: [SR-Users] Re: Dockerized VoIP Stack
To: David Villasmil <david.villasmil.work@gmail.com>
Cc: "Kamailio (SER) - Users Mailing List"
        <sr-users@lists.kamailio.org>
Message-ID:
        <CA+w+2f-0dXR9nN6=rjYWzcs2VOOXO5Trg5Mr4ua3wYrdxjjH8A@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="000000000000209cd505f06bb3a9"

On Thu, Dec 22, 2022 at 3:52 AM David Villasmil <
david.villasmil.work@gmail.com> wrote:

> https://github.com/Viking-VoIP
>
> Been working on that on and off, that might give you a few ideas (it’s AWS
> EKS based and freeswitch, but still)
>
> On Thu, 22 Dec 2022 at 08:16, Henning Westerholt <hw@gilawa.com> 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 <ter.devor@gmail.com>
>> *Gesendet:* Donnerstag, 22. Dezember 2022, 04:35
>> *An:* sr-users@lists.kamailio.org <sr-users@lists.kamailio.org>
>> *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 sr-users-leave@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to
>> the sender!
>> Edit mailing list options or unsubscribe:
>>
> --
> Regards,
>
> David Villasmil
> email: david.villasmil.work@gmail.com
> phone: +34669448337
>

Thank You David. What we are looking for is for someone with the capacity
and willing to complete the stack successfully. Please reach out to me if
you are interested in taking this on.
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 4591 bytes
Desc: not available

------------------------------

Subject: Digest Footer

_______________________________________________
sr-users mailing list -- sr-users@lists.kamailio.org
To unsubscribe send an email to sr-users-leave@lists.kamailio.org


------------------------------

End of sr-users Digest, Vol 211, Issue 47
*****************************************