1. Kamailio does not handle RTP, so audio is not a scaling factor at all;
2. The only scaling factors are transactional memory (TM) and any dialog state you are keeping;
3. Without I/O wait from external sources, Kamailio can handle a practically infinite amount of concurrent calls and CPS. But, most practical applications of Kamailio require database backing;
4. Therefore, performance and throughput will depend almost entirely on the database you are using for database backing, and any tuning on its settings. This certainly includes the CDRs and storage, and getting the most performance out of your database is outside the domain of your question (or this list);
5. A quad-core host with 8 GB of RAM should be more than sufficient for Kamailio itself to meet your needs. But most of the answers to your question don't have much to do with Kamailio.
-- Alex On 03/28/2014 06:36 AM, Rizwan Khan wrote:
HI Guys, can you refer me to some resources which help me dimension the hardware for a setup. Total users will be 20,000. What percentage should i assume for concurrent audio and video calls? What is the standard practice? How does this all map to the cpu, ram and storage etc. given that I will be storing the cdrs as well. In the futute this setup should be scalable so that it should support 200,000+ users within a span of 6-8 months. What would be the ideal architecture? Thanks, Rizwan Khan _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
