Welcome to GotSpeech.NET Sign in | Join | Help

Marshall Harrison - "the gotspeech guy"

Site news, Speech Server insight and assorted ramblings
Virtualizing OCS 2007 Speech Server

After talking with my good friend AC and reading a recent post he wrote on making the switch to VMWare I decided to experiment with setting up some virtual  environments. You have to realize that I have never been a fan of virtual environments. I come from the old school (where we only had 640K of memory) and I don't like giving up any CPU cycles unless I have to. Also in my previous job we just stood up  more servers when ever I needed a new environment for something.

I write a lot of experimental Speech Server applications just to test something or learn some new aspect of the tools. These tend to clutter up my hard drive mixing these experimental apps in with the real apps.

I've been toying lately with the idea of standing up a production environment using a virtual so after reading Andrew's post I decided to just do it. I respect Andrew's opinions very much (even though he is a SharePoint guy) so I downloaded and installed VMware Workstation.

Installation went very well and was fairly straight forward. The interface is very clean and easy to use. I had no problems creating a virtual machine - just some mouse clicks and then set back and wait.

Once you have a virtual machine you have to install an OS and there is where I ran into a problem. The normal procedure is to put a bootable OS CD in the drive and then start the virtual. My MSDN CDs are not bootable so the virtual wouldn't recognize it. What to do? A quick trip to the VMware web site and a few searches there I learned that you can point the virtual's CD drive to an ISO image on your hard drive and it would install the OS from that. A quick copy of the OS ISO image fro the MSDN CD and I was off and running. After finishing I simply pointed the drive back to the proper place.

I now had a base Windows 2003 Server image that I wanted to preserve so the next step was to clone that image which again was just a few mouse clicks and set back to wait.

I now had a base 2003 image and a clone which I called "OCS 2007 Speech Server Base". This is the virtual that i installed Speech Server on. After that was done and the install was tested I cloned this virtual also so that I would have a working production environment. I did this so that I can quickly and easily clone as many OCS Speech Server environments as I need.

So how does it work? Well, after a little tweaking it works very well. Using a soft phone on another machine I placed a call to the virtual and the WelcomeToOcs application answered but the sound quality really sucked. It was broken up and very choppy sounding. This was a disappointment and at first made me wonder if this concept was going to work. But rather than give up I started do some digging and found that the default memory allocation for a new virtual appears to be 384 MB. I quickly changed the memory to 1 GB and tested again. It sounded sweet. But this was to be expected as Speech Server loves memory.

All of this only took about 3 hours from downloading VMware Workstation to having a working Speech Server environment. I'm very happy and plan on pursuing this some more. As I do I'll blog and keep you updated.

Points to remember:

  1. OCS 2007 Speech Server works well in VMWare
  2. You need to allocate at least 1 GB of memory
  3. You should create both a base OS install as well as a base Speech Server install.
  4. Always clone the base installs and work off of the clones not the base installs

 

I would love to hear about your experiences with virtual machines - especially if you are using Speech Server.

Posted: Wednesday, September 05, 2007 10:28 AM by marshallharrison

Comments

Hayden said:

All of my MSS 2007 testing has been done using Windows 2003 Std on MS Virtual Server on XP (with 1 GB memory allocated).  No issues for dev and testing.

Hayden

# September 5, 2007 2:32 PM

bcxml said:

Well...here is the other side of the coin...

Base machine...Windows Server 2003 running Virtual Server 2005 R2

Virtual machine...Windows Server 2003

Although Speech Server 2007 installs just fine on the Virtual machine, there is no support for sound...makes development a little difficult.

You can get sound by using RDP to get to the virtual machine, however the RDP sound driver does not support a microphone, making verbal input quite tough.

I discovered this over a frustrating period of 3 days where nothing seemed to work

Although I love Virtual machines, I now do my Speech Server 2007 development on the base machine

Hope this helps someone to not waste as much time as I did

Brian

# September 5, 2007 3:26 PM

MichaelDunn said:

Need to upgrade to Virtual PC 2007...I personally hate VMWare..

# September 6, 2007 1:09 AM

rossm said:

I do my testing on a virtual XP box with around 300MB RAM - works fine so far.

Any reason you guys are opting for 2003 server? If i need to demo my app i will just take the virtual machine with me and find 2003 dosnt always play well on other networks and seems to take up a lot more disk space.

As mad as it sounds i also do all my dev work on a virtual XP box with VS installed

# September 6, 2007 4:07 AM

marshallharrison said:

Michael - read AC's blog entry about why he went with VMWare.

Rossm - In my opinion 2003 Server is the best development platform around. It doesn't have the quirks of Vista or the limitations of XP. It just works great. 90% of my development has been done on 2003 Server since it became available.

# September 6, 2007 7:32 AM

Azhuri said:

I have VPC2007 setup but found that it does not see my mic so I cannot use it very well for development. I have a 2003 server set up and a Vista set up and found the same issue on both. Might just need to update the mic I am using anyone found a work around for this?

Have to admit playing with the speech API (SAPI 5.3) built into Vista is interesting lots of possibilities here for future desktop apps to go along with the IVR apps.

# September 10, 2007 4:21 PM
Anonymous comments are disabled