Registration/call limits

[CD_]

Hi,

I'm going to use kazoo as a PBX for a service that I'm building that requires a modular VoIP system. I will use Kazoo only for registrations and simple calls between 2 registered devices; no conferences, no call centers, no carriers, only internal calls.

1) I would like to know how many registrations/calls Kazoo can manage for each Kazoo/kamailio node (for registrations) and for each FreeSwitch node (for calls). How can I estimate these values? Do I have to evalutate for each node or for the entire cluster?
I'm thinking to use dedicated servers (one server per node) with these specs:
Intel Xeon E3-1230v6 (4/8 cores with 3.5G/3.9Hz), RAM 16GB 2400MHz DDR4, SoftRaid 2x4TB, bandwitdth 500mbps and vRack for nodes at 1Gbps.
Starting with the 7 nodes configuration (3 DB, 2 FS and 2 Kazoo) is expensive (I have no fundings), so I would like to know the very basic configuration and its theoretical limits.

2) I would like to start with 2 nodes. How can I setup them? 1 FS + 1 DB/Kazoo? 1FS+1DB + 1Kazoo? All-in-one? Next they will be scaled as the registered devices increase.

3) I know Kazoo 4.0 pretty good (applications and source code). Is it a good idea to start with 4.1 instead?

[Darren Schreiber]

Thanks for writing. I'll try to answer your questions as best I can!

 

You wrote:

"1) I would like to know how many registrations/calls Kazoo can manage for each Kazoo/kamailio node (for registrations) and for each FreeSwitch node (for calls). How can I estimate these values? Do I have to evalutate for each node or for the entire cluster?"

Currently we have a number of people hitting between 10,000 and 30,000 on a single proxy. There are some optimizations we're working on which should raise that limit, but that's the norm, on mediocre hardware.

 

You wrote:

"2) I would like to start with 2 nodes. How can I setup them? 1 FS + 1 DB/Kazoo? 1FS+1DB + 1Kazoo? All-in-one? Next they will be scaled as the registered devices increase."

Yes, we support this now. All-in-one nodes are fine. You can split the components out later. But use at least 2 servers so you have some redundancy.

 

You wrote:

"3) I know Kazoo 4.0 pretty good (applications and source code). Is it a good idea to start with 4.1 instead?"

Up to you, 4.1 is stable now. There was a memory leak in Kamailio 5.0.3a but I believe that is patched also, so should be good to go. We are running 4.1 publicly on many clusters now.

 

[CD_]

Hi Darren, thanks for your reply.

OK, so I will start with 2 nodes all-in-one in VPS for testing then I will setup  2 nodes into dedicated servers. I will keep you update.

Thanks

[Darren Schreiber]

OK sounds good!