On Friday, August 17, 2012, JR Richardson &lt;jmr.richardson(a)gmail.com&gt; wrote: utilization, it doesn’t seem to make sense to keep running it on a physical host server. virtualized servers with OpenVZ, VMware and MS V-Server without issues. aware of specific to virtualized SIP-Router/Kamailio. I run kamailios in openvz containers for 2 years now, the only problems i encountered was with memory allocation, but with the latest vzswap functionalities, this is fixed. You might want to play with the mem argument that you see with ps aux so see if you hit the limit of the openvz container. Best, -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-3500762 "In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators."

On 08/17/2012 03:42 PM, JR Richardson wrote: It works great in VMware and XEN VMs without any issues. In my experience i had only two problems with virtual environment: - I/O (network, disc). - timing precision. Disc I/O can be a problem if you are going to write lots of logs and the VM running kamailio are connected to overloaded disc array or external storage. Use only async syslog mode otherwise kamailio process will be blocked in log operation and will be not available to process incoming sip traffic. So use fast drives and try to avoid time consuming operations (syslog, db queries, radius, etc...) during message processing as they block current process and kamailio has fixed number of running processes. From my point of view timing precision is not a problem for a sip-proxy as it's not a big deal to send some re-transmit few milliseconds earlier/later.