On Friday, August 17, 2012, JR Richardson jmr.richardson@gmail.com wrote:

Hi All,

I’m considering running Kamailio as a virtual machine, with such low

utilization, it doesn’t seem to make sense to keep running it on a physical host server.

I’ve been virtualizing Asterisk PBX’s for years and run a host of other

virtualized servers with OpenVZ, VMware and MS V-Server without issues.

I’d like any opinions or thoughts about pitfalls or caveats I should be

aware of specific to virtualized SIP-Router/Kamailio.

Thanks in advanced.

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,

JR

On 08/17/2012 03:42 PM, JR Richardson wrote:

Hi All,

I'm considering running Kamailio as a virtual machine, with such low utilization, it doesn't seem to make sense to keep running it on a physical host server.

I've been virtualizing Asterisk PBX's for years and run a host of other virtualized servers with OpenVZ, VMware and MS V-Server without issues.

I'd like any opinions or thoughts about pitfalls or caveats I should be aware of specific to virtualized SIP-Router/Kamailio.

Thanks in advanced.

JR

---

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

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.