On Wed, May 23, 2018 at 01:25:58PM +0000, Pinter, Gerd. wrote: > The question is, if anyone has experience if this issue maybe can be > solved by running the Sip Server on a standalone hardware plugged into > network Port on our Hardware Firewall, instead of a virtual Machine > running on VM with virtual switches and so on. The current SIP Server > has a Public IP Address, but all the Traffic runs thru Firewall, VPN, > Hardware Switches and Virtual Switches. What you think?
Virtualisation can/will add some jitter, but if you configure your setup correctly it will work fine for normal phone calls [*]. For example in VMware there is something caller NIC interrupt coalescing. AFAIK this is enable by default but introduces latency for RTP streams. But have bare hardware with a rtpproxy will perform better, without any tuning a recent machine relayed 900Mbit/s (simulated RTP packets) with ease, running vmware a single cpu guest instance was limited to about 40Mbit/s, 2 CPUs in the guest topped out at about 90Mbit/s before jitter and eventual loss occured (with coalescing disabled). *: jitter introduced by rtpengine is negligible compared to the jitter introduced by the endpoints themselves (either devices or network setup). _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users