Hello,
We're here to ask you what's the ratio between cpu cores/ghz, ram and how many contemporary calls kamailio can manage before it maxes out its capabilities and crash.
Kind Regards
Renato Gallo
System Engineer sede legale e operativa: Via San brunone, 13 - 20156 - Milano (MI) Tel. +39 02 - 87049490 Fax +39 02 - 48677349 Mobile. +39 342 - 6350524 Wi | FreeNumbers: https://freenumbers.way-interactive.com Wi | SMS: https://sms.way-interactive.com Wi | Voip: https://voip.way-interactive.com Asterweb: http://www.asterweb.org
Le informazioni contenute in questo messaggio e negli eventuali allegati sono riservate e per uso esclusivo del destinatario. Persone diverse dallo stesso non possono copiare o distribuire il messaggio a terzi. Chiunque riceva questo messaggio per errore è pregato di distruggerlo e di informare immediatamente [ mailto:info@sigmaware.it | info@ ] asterweb.org
On Fri, Aug 10, 2018 at 04:59:21PM +0200, Renato Gallo wrote:
We're here to ask you what's the ratio between cpu cores/ghz, ram and how many contemporary calls kamailio can manage before it maxes out its capabilities and crash.
You will not get any definite answer to this question.
It depends on to many factors. What will the function of kamailio be? A simple proxy that "just passes" packets will most likely be limited by network bottlenecks. A registrar with a database backend might be limited by this database (if there is no caching being used)
And since you ask for concurrent calls, after call setup (from INVITE to a 200 OK) no further signaling is necessary, with low calls/s you can reach a near unlimited amount of concurrent calls (limited to memory).