not really. in theory the issue is not with cpu or ram. it's incredibly about latency and the storage subsystem you use. ANY noticeable latency makes the media server functions (AA, conference and voicemail) problematic (as in garbled or unintelligible). it would also affect any remote user (media relay) or trunking (sipxbridge) that is anchoring.
sipx is making great strides in 4.6 to be cloud deployable, but i think that once the media server is able to be "separated" from the system, it can run as a standalone hardware device and separate from the other components. there is a lot of this in the freeswitch lists, since this is really a freeswitch/virtualization compatibility and tuning issue. We use VMWARE in our lab all the time for sipx. Once you start putting a sustained load on it though (media) it can have problems. 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services!
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
