VMware PBX on the VMware Solution Exchange

vmware pbxWe are pleased to announce our new VMware PBX image that allows you to test PBXware in a VM workstation or ESXi host.

Our developers created this by installing a VMware Workstation on a separate PC which ran Windows 10. We made a virtual machine that had 1 Vcpu, 1 GB of RM, 30 HDD (which was thin provisioned, meaning as the need for storage arises the HDD will expand) and open-VMware tools were added to this image for it to work properly. 

This was tested on the Windows machine first with up to 20 concurrent calls and 100 extensions. After that test was a success, we moved to testing ESXi hosts. ESXi hosts were tested with the same image with up to 30 concurrent calls and we did not encounter any problems. The test included Vmotion too, which was done while 30 concurrent calls were active. No calls dropped, the only thing we noticed was that 3 seconds before the virtual machine services started on the other ESXi host, we had 3 seconds of silence. Other than that, everything worked fine. 

The second test was VMware’s HA (High Availability) which worked as well. After the host that was running VM goes down, the other host takes over and keeps VM up with no downtime. 

After these tests were a success, we created a VMware marketplace account (as developers) and set it up with our company’s logo, information, and our PBX solution. The image was uploaded and sent for approval. It was approved 24 hours later. Check it out here: solutionexchange.vmware.com/store/products/pbxware–2 

Just click the “Try” button to download this image for usage with a VMware Workstation or VMware Player PRO and Vsphere client.

More posts like this one:

Official Press Release

VMware

UPDATE: PBXware is now on the VMware Solution Exchange as VMware PBX

While the rise of VMware seems unstoppable, Bicom Systems generally does not support virtual machines or VMware. The reasons are simple.

First, the clock source needs to be accurate. Because this service relies so heavily on time, any time-related problem will result in choppy audio, clicks, etc. The time must be accurate. When you open up facebook.com, for example, you won’t care if it is 100ms or 600ms at times. What you care about is getting SOMETHING. But when it comes to voice, this is not the case.

A MySQL/Orace Support forum user stated it best: “if you want a database for production, do not consider virtualization AT ALL. It is impossible to guarantee that when you write to the ‘disk’, you have actually written anything.” This has been tested and proven by professionals.

A second issue is not only the limit on the number of calls, but the reliability of that limit. Because of the real-time requirements of voice and video in PBXware, VMware simply cannot guarantee consistent performance. The exception is a fixed pre-allocated in real bounds of hardware, but that would usually mean no more than 2-3 VMs per machine, at most.

In short, virtual machines are a big no, but virtual servers such as SERVERware are made to the purpose of VoIP. If you must use a virtual machine, we recommend no more than 200 extensions more machine.

VMware Enterprise ESG is a robust and reliable platform for our products:
– Customer running PBXware Multi-Tenant CD install for about 3 years, 60,000 Calls / mo
– Customer running SERVERware with PBXware Multi-Tenant, test mode for 2 years, Calls Volume 20,000 in bulk no issues
– Customer running TELCOware with 2 PBXware for 3 years.

For more information, visit the Bicom Systems Wiki.

More posts like this one:

Voice on VMware

UPDATE: PBXware is now on the VMware Solution Exchange as VMware PB

Bicom Systems does not support VMware as a product platform for a number of reasons including issues with time scheduling, syncing, lack of Linux addons, insufficient performance boundaries, processing delays, and more. Bicom Systems staff has compiled a list of relevant reading on the problems with supporting VMware and some potential solutions:

For more information, visit the Bicom Systems Wiki or the VMware blog.

More posts like this one: