I've used it for small deployments where VMWare is already in use. For example, at a firm with six phones and 2 concurrent media hits. it works fine for small deployments if you tune the guest properly.
Because of the way vm guests use time slices of hardware assets, you're never quite sure where the next slice of time will occur, and if you've got a larger load on those slices, there's no guarantee of when the next hardware allocation will arrive. That's when media quality goes south. It should would work fine if you dedicated the host to that one VM guest, guaranteeing it all the slices of hardware time. That would give you the recoverability of a VM, but that's about it. Given that recovering SipX is already dead easy, I'm not sure that's a real plus. On Wed, Jan 4, 2012 at 12:22 PM, Wyland, Tony <[email protected]> wrote: > In theory if given adequate CPU and network bandwidth, sipxecs should be > able to run in vmware without notice. I know it installs and “works” in > testing but am curious if people are doing this in production and if any > unexpected issues arose.**** > > ** ** > > Tony Wyland**** > > Messiah College**** > > [email protected]**** > > ** ** > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
