Welcome to

Welcome to!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
See more
See less
  • Filter
  • Time
  • Show
Clear All
new posts

  • Shoretel supporting VMWare

    Does anyone know when VMWare will be supported by shoretel or what version that is or will be?

  • #2
    There are issues with VMWare that are outside of Shoretel's control and it has to deal with access to the network card that can cause garbled voicemail quality.

    Word on the street is that VMWare will have this addressed earlier next year in a release of VMWare Infrastructure (ESX).


    • #3
      Thanks for the information. In our environment we have several Distributed Voicemail Servers. If we kept those servers on their own physical machines and virtualized the director server would we still see the issue or does this issue affect the recordings used in the Auto-Attendants, Workgroups, and huntgroups as well?


      • #4
        It would impact voice quality from any server that is virutalized (VM, AA, Workgroup recordings, etc.).

        I've seen some people get it working without issue but there is a potential for problems and Shoretel will state it is unsupported given that they have no control.


        • #5
          We were thinking about putting a test environment up to test upgrades, new features, and VM Ware. Other than the issue with the VM Ware network adaptor are there any other issues people have run across with VM Ware that would be nice to know? Also, from a VM Ware standpoint does anyone have any more information about when they plan on releasing the fix in ESX so that Shoretel will support VM Ware.
          Last edited by w131jrd; 06-25-2008, 06:43 AM. Reason: Grammar and spelling errors


          • #6
            You could use vmware it if you had a dedicated NIC to only the voicemail. If you do not have a dedicated NIC you will not want to put the VM on it then. The NIC data needs to be real time and if you are sharing a NIC there will be delays in packets and poor voice quality.


            • #7
              I thought I would re-spark this conversation to see if anyone has some official news on Shoretel's stance on Virtualization.


              • #8
                There are several threads that have been through this topic time and time again. Not to be harsh, but it is not a ShoreTel issue. ShoreTel does not support virtualization because of hardware limitations of virtualization. The fact is that voice needs to be real time with specific bandwidth requirements, ShoreTel cannot slow down speech to wait for the virtual server. This is no different from Cisco or 3COM or any other VoIP phone system that requires real time availability for voice traffic. If you're happy with garbled quality voicemail for your staff and choppy auto attendents for your callers, then the software will run just fine.


                • #9
                  This was discussed in other threads but this is no longer a VMWare issue. With the release of ESX 4.0 (now called vSphere), VMWare resolved the limitations related to running real-time applications.

                  If you contact the right people, you'll get a better understand of what Shoretel's plans are for this.

                  By the way, both Avaya and Mitel have announced support for VMWare and now encourage the use of virtualization. In their case, they are able to consolidate a number of physical servers down to a single box running the previous machines as VMs.