I wrote about the GotSpeech Activity Library a few weeks ago. After posting that I had some people step up and express interest in creating activities for the library.
Unfortunately I got very busy right after I posted and things haven’t let up until now. I finally have the bandwidth to tackle a project like this so I’ve sent emails to the other participants and hopefully we will get this project into full swing.
I’ve already have the first activity in testing at the moment and I’m finishing up documenting it. I have another activity that I will be doing sometime in the next few days. It is something that I have written previously and now I just need to get it into the library and fully tested.
I’m also looking for your input on this project. Is there something that you think would make a great activity for the library? Is there some kind of functionality that you think is missing from Speech Server 2007? If so then now is your chance to get something done about it.
If you have ideas for an activity then email me or post it in the comments to this blog. I’ll make sure that the team gets your input.
Great Bill Gates interview and UC demo clip over at CNN – Out of Voicemail Jail.
I’m not sure how long this will be there so enjoy it while you can.
I would love to hear your take on this.
I would like to add to the list of bloggers here on GotSpeech.Net. If you are interested in blogging about Speech Server (2004 or 2007) related subjects or if you would like to start a SAPI blog then shoot me an email (or leave a comment to this post).
I already have some good bloggers but I want to see more participation from other knowledgeable speech developers. My personal feeling is that we can all learn something from other developers. I like seeing new and different ways of doing things.
I only have a few rules:
- No bashing of Microsoft or others. If something doesn’t work you can blog about it but there is a difference between constructive criticism and bashing. This is the same agreement I had with the speech team at Microsoft when I started this site.
- You will have to blog at least monthly. I hate finding a new blog on something that I am interested in only to find that there are gaps of weeks and months between posts.
I know from the reading the answers that are being posted in our forums that some of our members are very knowledgeable about Speech Server. I think sharing of experiences or blogging about how to do something in Speech Server can benefit all of us. For example Michael had a very good post recently that I learned some things from just as I did from Ken’s recent blog posting. If Michael and Ken can do it then I’m sure that others of you can too.
So, if you are interested in blogging speech stuff here is your opportunity to have your blog associated with the best speech site on the Internet.
At last night’s JAXDUG meeting Andrew Connell did an excellent presentation on using MbUnit for unit testing .Net applications. There was lots of lively discussion around MbUnit and the subject of doing unit tests.
I’ve decided to add MbUnit to my tool set and see how well it works at unit testing speech workflow applications. This will require some different thinking on how my speech applications are architected. My gut feeling is that MbUnit (or any of the other unit testing tools) won’t be able to actually test the workflow activities. But, if the application is structured right by segmenting logic off into classes when possible then you should be able to unit test those classes.
So, I’m wondering if any of you are doing unit testing on your speech applications. If so, would you share your experiences by posting a comment to this? I’m sure my readers can benefit from the experiences others have with testing their speech applications.
How are you testing your workflow? Please share that also.
Note: I don’t want to hurt any feelings so I should mention that Corey Grusden did a great presentation on how he attacks a client project as a consultant. His talk on the spec gathering process and how he defines the application was very informative.
I blogged yesterday about my initial experiences with my new AudioCodes VoIP Gateway. Well, today I started configuring the gateway.
The first step was to configure a IP address for the gateway and there are four ways of doing this.
- Use HTTP to access the built-in web interface
- Assign using BootP – this applications is supposed to be on the included CD but I never found it.
- Using the Voice Menu Guidance. You can attach a phone, dial a number (***12345) and follow voice prompts. Sounds like a pain in the ….
- Assign using the CLI – this requires attaching a serial cable and using Telnet. I’m just too lazy to use this approach.
After determining that option 1 was the only logical choice I moved on to the next step. This involved connecting the gateway to a PC (my laptop) using a crossover cable connecting the two devices. After connecting the devices you are supposed to “Change your PC/’ IP address and subnet mask to correspond with the MediaPack factory default IP address and subnet mask, shown in Table 3-1“. The default IP address is 10.1.10.10 so I reconfigured my laptop to have an address of 10.1.10.20.
The next step was to use a browser to connect to the gateway’s default address. Once connected you are presented with an “Enter Network Password” screen for logging in. Slight problem here as I failed to see the note that the username and password were case sensitive. A case sensitive username? Strange.
After logging in I picked the “Quick Start” menu option and set the IP Configuration as shown below. For my Linksys router the range below 100 is reserved for static IP addresses so I gave it one at the top of the range.
Now that the gateway shows up on my network monitor but it’s still not operational. The gateway still answers a call and immediately hangs up but I’m sure that I’ll get that problem resolved. I’ve taken a look at the routing tables and I thought I knew what to do to send a call to OCS 2007 Speech Server but that didn’t work.
I’ll do some more reading and report back later with the next blog installment.
Want a really cool screen saver? Go to the VoIP as you are Microsite and click “The Future is Flexible” on the orange ribbon.
You can use it to impress your co-workers and help spread the word about Office Communications Server.
I’ve been using it for a week or so but since I work out of my home I’ve only been impressing my wife and kids.
I received my AudioCodes MediaPack last week. I’ve just got to have a way to hook my OCS 2007 Speech Server up to the POTS and I thought this was the best approach. I’ve hooked up the gateway and I’ll be documenting the process of setting up the gateway in a series of blog posts.
I’ve already screwed up once though if I had though about it I could have avoided the problems I created for my home phone lines. After taking everything out of the box I proceeded to look at the documentation and hook up the gateway. But before I could do anything I had to make a trip to the local RadioShack to pick up the necessary network crossover cable an a long phone line cable.
After obtaining these items I connected the gateway to my switch using the crossover cable (1st mistake) and then I hooked up the analog phone line (2nd mistake) before plugging in the power. The gateway’s lights started flashing and the thing appeared to be working – or at least not dead on arrival.
That was it for the evening and early the next morning I had a meeting to attend. After the meeting I tried calling home only to discover the problems caused by me second mistake. The phone would ring once then disconnect so I called my wife on her cell phone to find out what was going on. Needless to say but she was a little aggravated as the phone had been ringing once all morning as if someone was calling and hanging up after the first ring. I knew instantly what was happening – the gateway was answering the phone but with no dial tables configured it was simply disconnecting. I’ve learned my lesson though and I’m leaving the gateway unplugged until I get it configured and get another analog line (anyone care to finance this?).
After I got home I discovered the results of my first mistake. When I plugged in the crossover cable I put it into the wrong slot on my switch. The way my switch is setup the up-link that connects it to my router disables the last port on the switch and I had plugged the gateway into that port. I would have thought that this would simply disable the gateway but instead it disabled the switch meaning everything connected to it lost their connectivity. Moving the cable and rebooting the switch solved that problem.
My next blog will cover my efforts to configure the switch as well as my pending contact with AudioCodes’ tech support. There isn’t a lot of information on the Internet about how to configure the gateway and in fact I can’t seem to find anything on the AudioCodes web site either.
Now for some images. The first shows what was included in the box -the gateway with power cable, the software CD and the documentation. The little plastic bag contains the four rubber feet for the bottom of the case.
The front view of the gateway…
The rear panel…
And in case you are wondering about the background in these images it’s just the couch in my office.