Release Notes for Speech
Server

This document describes
system requirements, installation procedures, and last-minute known issues for
Microsoft® Office Communications Server 2007 Public Beta Speech Server.

Quick Install Guide for Developers

·
Speech Server Components

·
Hardware Requirements

·
User Permissions

·
Supported Operating Systems

·
Prerequisites for Speech Server
Components

·
Prerequisites Installation Procedures
and Notes

Installing Speech Server

·
Uninstalling Speech Server

·
Remarks

Known Product Issues

·
Setup and Installation

·
Speech Server Administration

·
Speech Server Services

·
Speech Server Analytics and Tuning

·
Documentation and Sample Applications

·
Authoring Tools and Application Development

Quick Install Guide
for Developers

This Quick Install Guide
for Developers is intended for voice response application developers who want
to get Speech Server Development Tools and Server Components up and running as
quickly as possible. This guide assumes a single-server
topology and provides no scalability instructions.

The instructions that
follow are not intended to guide installation for enterprise deployment or
voice response application deployment. For enterprise installation
instructions, install the Documentation component first and then see the Help
topic "Installing Speech Server". For information on voice response
application deployment, see the Help topic "Speech Application
Deployment".

Speech Server
Components

The Speech
Server installer enables you to install the following Speech Server components:

·       Server Components— Core software that provides
speech recognition, speech output, and management of telephony systems.

·       Development Tools— Tools used within Microsoft
Visual Studio® 2005 SP1 development system to develop and debug voice
response applications. Among the tools included are Conversational Grammar
Builder, Grammar Design Advisor, and Voice Response Application Debugger, as
well as Speech Server Application Analytics and Tuning Studio with Grammar
Tuning Advisor and Re-recognizer. This feature cannot be installed without the
Server Components and Administrative Tools components.

·       Documentation— Product documentation for
Speech Server, including setup, development, administration documentation, and
managed code reference libraries and code examples.

·       Administrative Tools— Administrator Console and
other administrative tools for Speech Server.

·       Data Processing Tools— Tools used to process
Speech Server log data.

Note  Speech Server Analytics and Tuning Studio
(included in the Development Tools component) supports application tuning and analysis
with English (United States)
operating systems using English (United States) locales only.
However, within that environment you can analyze data collected from voice
response applications running in any language that Speech Server supports.

Important  Planned improvements in Speech Server
tuning tools features and functionality have resulted in changes to the tuning
database schema in each successive release of Speech Server. As a result, the
tuning tools for each successive release of Speech Server are incompatible with
the databases that were created using the tuning tools in previous releases of
Speech Server. For example, you will not be able to use Speech Server tuning
tools with databases created using the Speech Server Beta 1 or Speech Server Beta
Refresh tools. For all databases created before this release, maintain a copy
of the tools with which you created the tuning databases if you need to retain
the databases for business purposes.

Installing Documentation and Administrative
Tools Only

If you do not want to
install all Speech Server components, you can install only the Documentation
and Administrative Tools by selecting these components and clearing all other
component check boxes on the Component Installation page of the
Installation Wizard. You can use the Administrative Tools to administer Speech
Server deployments on local computers and remote computers.

Hardware Requirements

The computer on which you
install Speech Server must meet the following hardware requirements.

Feature

Requirement for Speech
Server Installation

Processor

Pentium
4 class running at 2.5 gigahertz (GHz) or faster

Number
of Processors

1 (2
recommended)

RAM

1 GB
(4 GB recommended)

DVD-ROM Drive

Required
only if installing from DVD rather than from a network

Network
Interface Card (NIC)

Required

Free
hard disk space (for installation)

NTFS-formatted
local partition with 3.5 GB of available hard disk space

Free
hard disk space (for logging)

5 GB
minimum for Speech Server with Development Tools; 20 GB minimum for Speech
Server with other components. Requirement depends on the amount of log data
you want to store on the computer.

The following are
additional requirements and recommendations for computers that will be used to
develop voice response applications.

Feature

Requirement or Recommendation for Speech Application Development

Video

Super
VGA (800 x 600) or higher-resolution adapter and monitor

Keyboard
and Mouse

Required

Microphone

Optimal
performance is achieved with a high quality close-talk (headset) microphone.
A universal serial bus (USB) microphone with gain adjustment support is
recommended

Audio
Output Device

Recommended
for application development

User Permissions

You must be a member of
the Administrators group on the target computer to install Speech Server and
all prerequisite software. To verify that you are an Administrator, see the User
Accounts Control Panel on your computer. If you are not an Administrator,
see your network administrator.

You must be a member of
the Administrators group to open the sample and reference applications, or
solution files.

Administrative permissions
are required to develop voice response applications and to use the
Re-recognizer tuning tool. However, administrative permissions are not required
to use the other Analysis and Tuning tools or to view tuning reports.

Speech Server sets
permission levels on the computers where it is installed. When Speech Server is
installed on a computer running Windows Server 2003, only administrators and
power users (not users or guests) are able to log on interactively. However,
when Speech Server is installed on a computer running Windows XP or Windows
Vista, users in both the Admin group and the Interactive Users group are
allowed to log on interactively. For more information, see the Help topic
"Logon Permissions for the Computer Running Speech Server".

Supported
Operating Systems

All components listed in Speech Server Components are supported on one of the
following operating systems:

Server
Operating Systems

Client
Operating Systems

·
Microsoft
Windows Server® 2003 Standard Edition SP1 (32-Bit x86)

·
Windows
Server 2003 Standard x64 Edition SP1

·
Windows
Server 2003 R2 Standard Edition (32-Bit x86)

·
Windows
Server 2003 R2 Standard x64 Edition

·
Windows
Server 2003 Enterprise
Edition SP1 (32-Bit x86)

·
Windows
Server 2003 Enterprise
x64 Edition SP1

·
Windows
Server 2003 R2 Enterprise
Edition (32-Bit x86)

·
Windows
Server 2003 R2 Enterprise
x64 Edition

·
Windows®
XP Professional SP2 (32-Bit x86)

·
Windows
XP Professional SP2 64-Bit Edition

·
Windows
Vista™ Ultimate

·
Windows
Vista Business

·
Windows
Vista Enterprise

Prerequisites for Speech Server Components

The prerequisites required
for installing Speech Server depend on the Speech Server components that you
choose to install. The following table illustrates the prerequisites for these
components and the recommended order in which the prerequisites should be
installed. Click the name of the prerequisite to view installation procedures
and notes.

After installing
prerequisite software, install the latest service packs and all critical
updates for your operating system from Windows Update.

Prerequisites

Server
Components

Development
Tools

Documentation

Administrative
Tools

Data
Processing Tools

IIS and MSMQ

Required

Required

−

−

Microsoft .NET Framework 3.0 Redistributable Package

Required

Required

Required

Required

Required

MSXML 6.0.3883

Required

Required

−

−

Visual Studio 2005 SP1

(and for Windows Vista only, Visual Studio 2005 SP1 Update for Windows Vista)

−

One
of the following Editions is Required:

·
Standard
Edition

·
Professional
Edition

·
Professional
Edition 90-Day Trial

·
Team
Suite

·
Team
Suite 180-Day
Trial

·
Team
Edition for Software Architects

·
Team
Edition for Software Developers

·
Team
Edition for Software Testers

−

−

Microsoft Visual Studio 2005 Extensions for Windows
Workflow Foundation

−

Required

−

−

Hotfix for Microsoft .NET Framework 2.0 (KB917833) (Windows
Server 2003 and Windows XP only)

Required

Required

−

−

Integrated Windows Authentication enabled

Required

Required

−

−

Prerequisites Installation Procedures and Notes

Following are procedures
for installing Speech Server prerequisites and additional notes about the
prerequisites.

To
install IIS and MSMQ

On Windows
Server 2003

1.   Click Start, click Control
Panel, and then click Add or Remove Programs.

2.   Click Add/Remove Windows
Components.

3.   In the Components list box,
select Application Server, and then click Details.

4.   Select the check boxes next to ASP.NET
and Message Queuing.

Note  Selecting ASP.NET also causes Windows
to automatically select all of the components of IIS that are required for
Speech Server.

5.   Click OK, click Next, and then click Finish.

On Windows XP
Professional

1.   Click Start, click Control
Panel, and then click Add or Remove Programs.

2.   Click Add/Remove Windows
Components.

3.   In the Components list box,
select the check boxes next to Internet Information Services (IIS) and Message
Queuing.

4.   Click Next.

On Windows Vista

1.   Click Start and then click Control
Panel.

2.   Click Programs.

3.   Under Programs and Features,
click Turn Windows features on or off.

4.   Using the following table as a
guide, expand nodes as necessary and then enable the features that are
displayed in the table using boldfaced, blue font.

Note  When you enable the features indicated
in the table by boldfaced, blue font, Vista
will automatically enable additional, dependent features. These additional
features are indicated in the table by solid, black discs.

o     Internet
Information Services

o   FTP Publishing
Service

o   Web Management
Tools

o   IIS 6 Management
Compatibility

o   IIS 6 Management
Console

·
IIS 6 Scripting Tools

·
IIS
6 WMI Compatibility

·
IIS
Metabase and IIS 6 configuration compatibility

·    IIS Management Console

·    IIS Management Scripts
and Tool

·    IIS Management Service

o   World Wide Web
Services

o   Application
Development Features

·
.NET
Extensibility

o   ASP

·
ASP.NET

o   CGI

·
ISAPI
Extensions

·
ISAPI
Filters

o   Server-Side
Includes

o   Common Http
Features

·
Default
Document

o   Directory Browsing

o   HTTP Errors

o   HTTP Redirection

·
Static Content

o   Health And
diagnostics

o   Performance
Features

o   Security

o   Basic
Authentication

o   Client Certificate
Mapping Authentication

o   Digest
Authentication

o   IIS Client
Certificate Mapping Authentication

·    IP Security

·
Request
Filtering

o   URL Authorization

·
Windows Authentication

o    Microsoft Message
Queue (MSMQ) Server

·    Microsoft Message
Queue (MSMQ) Server Core

o   MSMQ DCOM Proxy

Note  The features that this procedure
directs you to enable together with the dependent features that Vista
automatically enables are the minimum set of features that are required to
install Speech Server on computers running Vista.

To
install Microsoft .NET Framework 3.0 Redistributable Package

On Windows
Server 2003 and Windows XP

Important  Speech Server does not support
pre-release versions of .NET Framework 3.0. If you have a pre-release version
installed, you must first uninstall the pre-release version and then install
the released version.

1.   Go to Microsoft .NET Framework
3.0 Redistributable Package.

2.   Click Download and follow
the program until the installation is complete.

Note  The final dialog screen of the .NET
Framework 3.0 Installation Wizard directs you to install Update for Windows
Communication Foundation (KB912817). If you accidentally close the .NET
Framework 3.0 Installation Wizard before installing this update, click the link
provided in this note, and then download and install the version of this update
that is appropriate for your computer's architecture.

On Windows Vista

1.   Click Start and then click Control
Panel.

2.   Click Programs.

3.   Under Programs and Features,
click Turn Windows features on or off.

4.   Select the check boxes for Microsoft
.NET Framework 3.0 and all of its subfeatures, and then click OK.

To install Microsoft XML 6.0.3883

1.   Go to Microsoft Core XML Services
(MSXML) 6.0.

2.   Under Files in this Download,
click the version that applies to your computer's chipset: x86, x64, or IA64.

3.   Click Run. Follow the
program until the installation is complete.

Visual
Studio 2005 SP1

If you do not have a copy
of Visual Studio 2005 SP1, you can download or order an evaluation copy of
Professional Edition or Team Suite Edition from the Microsoft Visual Studio
MSDN Evaluation Center.

Note  Speech Server tuning tools require
Microsoft SQL Server™. If you plan to use Speech Server tuning tools and
you do not already have SQL Server 2000 or SQL Server 2005 installed on your
computer, select the option to install SQL Express during the Visual Studio
2005 SP1 installation process. Speech Server Reporting Services (RDL) reports
require SQL Server 2005 (Standard Edition or later).

If you already have Visual
Studio 2005, you can download Visual Studio 2005 Service Pack 1 for free from
the Microsoft Developer Center.

Important  If you are installing Speech Server
on a computer running Vista, in addition to
installing Visual Studio 2005 SP1, you must also install Visual Studio 2005
Service Pack 1 Update for Windows Vista. The Visual Studio 2005 Service Pack 1
Update for Windows Vista addresses areas of Visual Studio impacted by Vista enhancements.

To download
Visual Studio 2005 Service Pack 1

1.   Go to Visual Studio 2005 Service
Pack 1.

2.   At the bottom of the page, click
your Visual Studio 2005 version.

3.   On the next page, click Download.

4.   In the File Download dialog
box, do one of the following:

·
To
start the installation immediately, click Run.

·
–
OR –

·
To
copy the download to your computer for installation at a later time, click Save.

5.   When you start the installation,
follow the wizard until the installation is complete.

Note  Visual Studio 2005 Service Pack 1 is a large
program that can take a long time to install. As a rule, allow as much time to
install Service Pack 1 as you did to install Visual Studio 2005.

To download
Visual Studio 2005 Service Pack 1 Update for Windows Vista

1.   Go to Visual Studio 2005 Service
Pack 1 Update for Windows Vista.

2.   Click Download.

3.   In the File Download dialog
box, do one of the following:

·
To
start the installation immediately, click Run.

·
–
OR –

·
To
copy the download to your computer for installation at a later time, click Save.

4.   When you start the installation,
follow the wizard until the installation is complete.

To install Visual Studio 2005 extensions for .NET Framework 3.0
(Windows Workflow Foundation)

1.   Go to Visual Studio 2005
extensions for .NET Framework 3.0 (Windows Workflow Foundation).

2.   Click Download.

3.   Click Run. Follow the
program until the installation is complete.

Speech Server
does not support pre-release versions of Visual Studio 2005 Extensions. If you
have a pre-release version installed, you must first uninstall the pre-release
version and then install the released version. To determine what version of
Visual Studio 2005 Extensions is installed on your computer, do the following:

1.   Click Start, click Control
Panel, and then click Add or Remove Programs.

2.   In the list of currently installed
programs, click Visual Studio 2005 Extensions for Windows Workflow
Foundation.

3.   Click Click here for support
information. Version information is displayed in the field labeled Version.

To
install the Hotfix for Microsoft .NET Framework 2.0 (KB917833)

1.   On the Speech Server distribution
DVD, change directories to %DVDROOT%\Prerequisites\dotNetFamework\KB917833.

2.   Double-click the appropriate
executable for your operating system (NDP20-KB917833-X86.exe for 32-Bit systems
or NDP20-KB917833-X64.exe for 64-Bit systems) and follow the instructions to
install the Hotfix.

Note  This hotfix is not required on Windows
Vista systems.

To enable Integrated
Windows authentication

On Windows
Server 2003 and Windows XP

1.   Click Start, click Control
Panel, click Administrative Tools, and then click Internet
Information Services (IIS) Manager.

2.   Expand the local computer node and
then expand Web Sites.

3.   Right-click Default Web Site
and then click Properties.

4.   Click Directory Security and
then click the first Edit button. On Windows Server 2003, the first Edit
button appears in the area labeled Authentication and access control. On
Windows XP, the first Edit button appears in the area labeled Anonymous
access and authentication control.

5.   Under Authenticated access
enable Integrated Windows authentication and then click OK twice.

On Windows Vista

1.   Windows Authentication is enabled
by following the previous procedure describing how to
install IIS and MSMQ on Windows Vista.

Installing Speech Server

Before installing Speech
Server, deactivate any real-time virus monitoring software that is running on the
target computer. Once installation is complete, reactivate real-time virus
monitoring. In addition, close any running programs before installing or
uninstalling Speech Server.

To install
Speech Server

1.   Verify that you have installed all Prerequisites for Speech Server Components that
you intend to install.

2.   Close all open programs.

3.   Run Setup.exe from the root
of the Speech Server installation DVD, and follow the program until the
installation is complete.

Important  The final screen of the Speech Server
Installation Wizard prompts you to install a Speech Server Language Pack from
either the installation DVD or from the Web. Speech Server does not support
user interaction in any specific language by default. You must install at least
one language pack in order to obtain support for user interaction.

Uninstalling Speech Server

Uninstalling Speech Server
removes all components listed in Speech Server
Components.

Important  Before uninstalling Speech Server, close
any running programs.

To uninstall
Speech Server

1.   Click Start, click Control
Panel, and then click Add or Remove Programs.

2.   Select Microsoft Office
Communications Server 2007 Speech Server Beta from the list of currently
installed programs.

3.   Click Change/Remove and then
click Remove.

4.   Click Next
and then click Uninstall.

5.   Click Finish after
uninstallation completes.

Remarks

·    Do not install Speech Server on a
computer that is running Microsoft Speech Server 2004 or Microsoft Speech Server
2004 R2.

·    A single-server topology (also called an
"all-in-one" topology) is a configuration in which Web server
software (IIS and ASP.NET) and all Speech Server components that are required
by an application are installed on the same computer as the application.

·    Speech Server 64-Bit is supported
only on Windows Server 2003 64-Bit operating systems, Windows XP Professional
SP2 64-Bit Edition, and 64-Bit editions of Windows Vista.

·    To minimize disruptions of service,
disconnect the computer from the production environment before installing
Speech Server.

·    Installing Speech Server restarts
the Windows Management Instrumentation (WMI) service. For more information
about the WMI service, see WMI Scripting Overview in the product documentation.

·    The Speech Server installation DVD
includes installers for Speech Server Business Intelligence Tools (BIT). These
tools can be used to create a new data warehouse for Speech Server, or to
migrate a Microsoft Speech Server 2004 or Microsoft Speech Server 2004 R2
tuning database to an Office Communications Server 2007 Public Beta Speech
Server Analytics and Tuning Studio database. Both the Data Warehouse and
Migration sets of tools require SQL Server 2005 Integration Services, and the Data
Warehouse reporting tools require SQL Server 2005 Analysis services. The BIT
installers are located in the Business Intelligence Tools directory at the root
of the Speech Server DVD. Use setup32.msi to install BIT on 32-Bit operating
systems, and setup64.msi to install BIT on 64-Bit operating systems.

·    For product news, updates,
technical articles, and links to other useful resources, see the Speech Server Home Page.

Back to Top

Known Product
Issues

Setup
and Installation

Problem:

Speech Server requires the ASP.NET Windows and .NET
Extensibility features to be enabled. However, when I upgraded my Windows XP
computer to Vista, I was unable to install
these features. When I tried to install ASP.NET, I received the following
error:

An
error has occurred. Not all of the features were successfully changed.

Solution:

To resolve this issue, follow these steps:

1.   Click Start and then click
Control Panel.

2.   Click System and Maintenance
and then click Administrative Tools.

3.   Double-click Internet
Information Services (IIS) Manager.

4.   In the center pane of the Internet
Information Services (IIS) Manager window, double-click ISAPI Filters.

5.   For each filter listed in the ISAPI
Filters pane click the filter name, and then in the Actions pane
click Remove.

6.   Close the Internet Information
Services (IIS) Manager window and then reinstall ASP.NET.

Note  To reinstall the ASP.NET on Windows
Vista, open the Windows Features window by following the first three
steps of the previously listed procedure describing how to install IIS and
MSMQ on Windows Vista, and then enable the ASP.NET
feature.

For additional information, see the following KB article: http://support.microsoft.com/kb/929772/en-us.

Problem:

When the
Speech Server installer is run on computers running Windows Vista, it will allow
you to install Speech Server even if you have not enabled all of the IIS
features listed in these Release Notes as prerequisites. As a result, Speech
Server might not function as expected.

Solution:

Resolve this
problem by ensuring that you enable all required IIS features
on Windows Vista listed in the section "To install IIS and
MSMQ" of this document before you run the Speech Server installer.

Problem:

When the
Speech Server installer is run on computers running Windows Vista, it will
allow you to install Speech Server even if you have not enabled all of the
MSMQ features listed in these Release Notes as prerequisites. As a result,
Speech Server might not function as expected.

Solution:

Resolve
this problem by ensuring that you enable all required MSMQ features on Windows Vista listed in the section
"To install IIS and MSMQ" of this document before you run the Speech
Server installer.

Back to Top

Speech
Server Administration

Problem:

When Speech Server is running on Vista,
disabling Trace Logging fails. An error is logged to the Windows Event Log and
Speech Server continues to log to the ETL file.

Solution:

After disabling Trace Logging through the MMC, open a
command window on the computer running Speech Server and run the following
command:

logman
-ets stop "MSSTrace"

Problem:

I cannot start the Speech Server service after upgrading
my computer operating system from Windows XP to Windows Vista.

Solution:

For the security reasons, the Windows Vista upgrade
process disables the World Wide Web Publishing
Service. This stops the Default Web Site in the Internet
Information Services (IIS) Manager. In order to start Speech Server
service normally, you must open the Services window of the Microsoft
Management Console and enable World
Wide Web Publishing Service, and then open Internet Information
Services (IIS) Manager and restart the Default Web Site.

Problem:

If the disk drive on which the Speech Server Event Trace
Log (ETL) files are being saved becomes full, the logging process stops even
though Speech Server can still be actively handling calls. Log data is not
recorded until the logging process is manually restarted.

Solution:

To resolve this problem, first free up space on the disk
drive that is used to save the ETL files and then restart logging.

To
free up disk space

Use one
of the following methods:

·
Move
or delete files from the disk drive.

·
Configure
Speech Server to save ETL files at a different location that has disk space
available. To do this using the Speech Server Administrator console, open the
Server Properties for the computer running Speech Server, click the Trace
Logging tab, specify a new path in the Location box, and then
click OK.

To
restart logging

The
procedure for restarting logging depends on whether your logging target
directory is on the same partition as Speech Server.

·
If
your logging target directory is on the same partition as Speech Server,
after freeing up disk space, restart logging by restarting the computer.

·
If
your logging target directory is on a separate partition or disk, after
freeing up disk space, restart logging as follows:

1.   Open Speech Server Administrator
Console.

2.   Expand Default and then
click Servers.

3.   In the Servers pane, right-click the
server name, click All Tasks, and then click Disable Trace Logging.

4.   Right-click the server name
again, click All Tasks, and then click Enable
Trace Logging.

To
prevent this problem from occurring, consider configuring a low disk space
alert. For information on how to configure a low disk space alert by using
the performance logs and alerts feature in Windows Server 2003, see KB Article 324796.

Back to Top

Speech
Server Services

Problem:

Installing Microsoft Speech Application SDK (SASDK) 1.1
on top of Speech Server results in a Speech Server failure. This problem is
indicated by an error in the event log such as the following:

SES
was unable to create an instance of the engine Microsoft English (U.S.
Telephony) v9.0 Server for the following reason: 'Specified cast is not
valid. (System.InvalidCastException)'.

The
reason for this is that the SASDK 1.1 TTS engines are incompatible with
Office Communications Server 2007 Public Beta.

Solution:

Resolve this problem by uninstalling SASDK 1.1 and then
reinstalling the Server Components of Speech Server.

Problem:

I am running Speech Server on Windows Vista. When I try
to call my application from an external source, Speech Server does not
connect.

Solution:

One possible source of this problem is that the Windows
Firewall on Vista may be blocking the
connection. To connect, you must create exceptions for Microsoft.SpeechServer.Tap.exe
and w3wp.exe.

Problem:

My application successfully accepts calls from a locally
hosted VoIP source (softphone, development environment, or TIMC). When I
deploy my application to a server other than the VoIP source, it no longer
accepts calls.

Solution:

One possible source of this problem is that calls are
blocked by the IPSec Service running on the server where the application is
deployed. In this case, stopping the IPSec Service will resolve the problem.
This applies only to topologies in which calls originate from a VoIP server
other than the server hosting the application (such as a VoIP gateway or
softphone).

Note  IPSec normally blocks inbound
connections to Speech Server. However, if a Speech Server outbound call was
accepted by a gateway, then for several minutes following this, Speech Server
will accept calls from that source even if IPSec is on.

For
deployments hosted on computers running Vista,
another possible source of this problem is that the firewall is not
configured correctly. On computers running Vista,
ensure that you add exceptions to the firewall for the following:

·
w3wp.exe
and Microsoft.SpeechServer.Tap.exe to enable outbound calls in Hosted mode

·
Each
voice response application for which you want to enable outbound calls in
Immediate mode

·
The
listening ports used by the voice response applications to enable inbound
calls

Important  Deployments on computers running Vista should
be used for testing purposes only because support for Vista
is limited to two localhost channels.

Problem:

If you
install Telephony Interface Manager Connector (TIMC) without first installing
a Telephony Interface Manager (TIM), Speech Server will not start because the
operation of TIMC is dependent on the presence of a TIM.

Solution:

TIMC is
intended to be installed with a TIM. If you do not plan to use a TIM, do not
install TIMC.

Back to Top

Speech
Server Analytics and Tuning

Problem:

When I use MssLogToDatabase on a machine running .NET
Framework 2.0, I either receive tabular data stream protocol errors, or the
import times out.

Solution:

Resolve this problem by installing the .NET hotfix
described at http://support.microsoft.com/kb/913177/en-us
on the computer that is running MssLogToDatabase.

Problem:

When I try to play back session audio for which there
were no dialog turns, Analytics and Tuning Studio says "The system cannot
find the file specified". When I try to export session audio for a
session which contains no dialog turns, I am prompted for a folder, but no
audio file is saved.

Solution:

Analytics and Tuning Studio is unable to recreate the
audio for sessions in which there were no dialog turns. Find sessions which
contain dialog turns (for example, for which the turn count value is > 0)
and playback or save the audio for those sessions.

Problem:

If I save an Analytics and Tuning Studio query file that
specifies a value for the Session Label filter and point it to a
different database, the data returned by the query is incorrect.

Solution:

When viewing the latter database, uncheck the Session
Label filter, refresh the query, and then re-check the Session Label
filters. The correct data should be returned.

Problem:

When I attempt to run a re-recognition cycle with the
same name as an existing re-recognition cycle, and select Replace when
prompted, I receive the following alert:

The
DELETE statement conflicted with the REFERENCE constraint
"FK_RecognitionWords_RecognitionResultId". The conflict occurred in
database "TryTuning", table "dbo.RecognitionWords",
column 'RecognitionResultId'.

Check the database connection is correct, that the database contains a valid
Speech Log Analyzer database and retry. The statement has been terminated.

Check the database connection is correct, that the database contains a valid
Speech Log Analyzer database and retry.

Solution:

Give the re-recognition cycle a different name before
executing.

Problem:

In Analytics and Tuning Studio, when I try to navigate
from a Turn view selection up to a Task or Session view,
or from a Task view selection up to a Session view, the
navigation does not reflect only my selection, but instead displays all data
as selected by the filters.

Solution:

To see containing session or task information for specific
turns or tasks, apply an explicit filter to return only the sessions or tasks
of interest.

Problem:

I used MssLogToText to convert a log file to text, and
now I am examining the log content. However, I do not understand the log schema,
and I cannot find documentation about the schema.

Solution:

Log schema documentation is provided in a separate HTML
document. When Speech Server is installed to the default location, the log
schema documentation is located in:

%ProgramFiles%\Microsoft
Office Communications Server 2007 Speech
Server\doc\EventSchemaForHelpDocs.htm

Problem:

Sometimes, after an execution of MssDataPurge, I see
rows left behind that should have been deleted and/or I am unable to re-import
a log file whose data was previously purged.

This is because in certain cases where trace messages
cannot be associated with sessions in the data (for example, because call
events are split across import sessions or events are otherwise left "orphaned"),
the trace messages cannot be removed by MssDataPurge.

Solution:

Orphan rows in the Messages table should be
manually removed.

Problem:

Using Analytics and Tuning Studio, when I set filters in
Turn Details View to view turns that have no TurnName, the size
of the TempDB dramatically increases.

Solution:

Analytics and Tuning Studio does not support querying
the Turn Details View in an unconstrained fashion. Either filter your query to include turn names or other turn
identifiers, or make a selection in the Turn List View and navigate to
the Turn Details View with the selection. To recover the disk space
consumed by the TempDB , restart SQL Server.

Problem:

When I try to purge recognition cycles from my tuning
database using MssDataPurge.exe with the /pre: and /post: arguments, it does not appear to work.

Solution:

As with the other types of data purging, the /pre: and /post: parameters refer to the time of
the session, not the time that the re-recognition cycle was conducted. To
purge re-recognition cycles based on dates, use /pre: and /post: to specify the time period for
the sessions holding the original recognition.

Back to Top

Documentation
and Sample Applications

Problem:

I installed Speech Server on a computer running a 64-Bit
Vista operating system. I am following the
procedure explaining how to create an application pool and set its identity
to the new user account contained in the Help topic "64-Bit
Issues". However, the user interface described in the procedure does not
match what I see on my computer.

Solution:

Use the following procedure to create an application
pool and set its identity to a new user account on computers running a 64-Bit
Vista operating system:

1.   Click Start, click Run,
type compmgmt.msc, and then click OK.

2.   In the Computer Management
dialog box, expand Services and Applications, and then click Internet
Information Services.

3.   In the Connections pane,
expand the local server name, right-click Application Pools, and then
click Add Application Pool.

4.   In the Add Application Pool
dialog box, type a name for the pool, and then click OK.

5.   In the Connections pane,
click Application Pools.

6.   In the Application Pools
pane, right-click the new application pool, and then click Advanced
Settings.

7.   In the Advanced Settings
dialog box, click Identity, click the listbox arrow next to NetworkService,
and then select SpecificUser from the listbox.

8.   Click Identity SpecificUser
Credentials, and then click the browse button next to the empty value
column.

9.   In the Set Credentials
dialog box, enter the user name and password for the new user account, and
then click OK twice.

Problem:

When I
look for the SurveyTutorial sample project files in the path shown in the
topic "Creating a Grammar Builder Grammar", there are no files. The
path shown, My
Documents\Microsoft Communications Server 2007 Speech Server\SDK\Speech
Projects\SurveyTutorial, is incorrect.

Solution:

By
default, the SurveyTutorial sample project files are created in My Documents\Visual Studio
2005\Projects\SurveyTutorial.

Problem:

The
descriptions of the FromTag and ToTag properties on CallInfo
(Microsoft.SpeechServer.CallInfo) are incorrect.

Solution:

The
correct descriptions for these properties are as follows:

FromTag

Gets
the text of the "tag" parameter of the From header field in
a SIP INVITE request.

ToTag

Gets the text of the
"tag" parameter of the To header field in a SIP INVITE
request.

Problem:

There
are several typographical errors in the topic "Phoneme Table for English
(United States)".
These include the following:

·
The
UPS transcription of "her" is missing the final phoneme /RA/

·
The
phoneme for the close-mid, back vowel is shown incorrectly as /O + U/ instead
of /O + UH/

·
The
UPS transcription of "ring" incorrectly uses the phoneme /R/
instead of /RA/

·
The
last syllable separator [.] in the UPS transcription of "secondary"
is incorrectly placed

Solution:

The
following tables show the corrected entries:

UPS
Label

Example
Word

UPS
Transcription of Example Word

ER

her

H
ER RA

O
+ UH

rose

RA
O + UH Z

N

nose

N
O + UH Z

RA

ring

RA
IH NG

UPS
Label

Description

Example
Word

UPS
Transcription of Example Word

S2

secondary
stress

secondary

S1
S EH . K AX N . S2 D EH . RA I

Problem:

In the
topic "Phoneme Table for French (Canada)", the example word
and UPS transcription string provided as examples for the use of the
consonant [T _^] do not match.

Solution:

The UPS transcription
string is correct. The example word should read "petit
enfant".

Problem:

In the
topic "Creating a Conversational Grammar Builder Grammar", the
documentation provides two steps for building the Survey Tutorial Application
project. The next set of steps explain how to
validate and build the grammar. However, after I build the project, I no
longer see the Conversational Grammar Builder menu.

Solution:

Visual
Studio displays the Conversational Grammar Builder menu only when the
Conversational Grammar Builder tool is in focus. Resolve this problem by
double-clicking the file SurveyTutorial.gbuilder in order to bring the
Conversational Grammar Builder tool into focus.

Problem:

The Help
documentation contains two topics which indicate that the Reason
headers from a SIP BYE message should be available to an application. These
topics are:

·
"DeclineCallActivity.ReasonText
Property"

·
"CallDisconnectedException.RemoteDisconnectHeaders
Property" (the member belonging to the CallDisconnectedException
Class)

However,
when I try to use the value of these properties, the properties are empty.

Solution:

The Reason
headers from a SIP BYE message are not available to an application. Do not
use the DeclineCallActivity.ReasonText property or the RemoteDisconnectHeaders
property that belongs to the CallDisconnectedException Class.

Problem:

When I
try to specify the target for a GoToActivity
(Microsoft.SpeechServer.Dialog.GoToActivity), the Dialog Flow Designer
does not let me choose the target I want.

Solution:

A GoToActivity
target must be a child of an ancestor (parent, grandparent,
great-grandparent, and so on) of the GoToActivity. In addition, the
ancestor must be a SpeechSequenceActivity or one of its derived
classes (CommandActivity, SpeechEventActivity, or SpeechSequentialWorkflowActivity).

For
example, using the following diagram for reference, suppose that your speech
application has a workflow that contains an IfElseActivity labeled ifElseActivity1,
which has two branches labeled ifElseBranchActivity1 and ifElseBranchActivity2.
Suppose further that ifElseBranchActivity1 contains a GoToActivity
labeled goToActivity1. The target of goToActivity1 cannot be ifElseBranchActivity2.
The reason for this is that the parent of ifElseBranchActivity2 is ifElseActivity1,
which is not a SpeechSequenceActivity (or one of the three classes
derived from it). However, because ifElseActivity1 is a child of the
workflow (type SpeechSequentialWorkflowActivity), ifElseActivity1
can serve as the target for goToActivity1. If you implement application
logic similar to this, consider that when ifElseActivity1 is executed
as a result of a jump to it, the condition or rule that determines the branch
to take is evaluated again. If you want ifElseBranchActivity2 to be
executed, change the value of the variable in the condition or rule to ensure
that this happens.

Problem:

When
viewing Speech Server documentation, I encounter broken links in the API
topics.

The
Speech Server documentation is designed for integration with the MSDN
documentation collection. When Speech Server documentation is installed on a
computer without MSDN, all links to MSDN topics are non-functional. Most of
these links can be fixed by installing the MSDN collection.

In
addition, the Speech Server product uses components of Windows Workflow
Foundation, and consequently, the Speech Server documentation references
Workflow documentation. Unfortunately, the Workflow documentation is not yet
part of the MSDN collection. After the Workflow Foundation documents have
been added to the MSDN collection, it will be possible to fix these links by
installing an MSDN collection that contains the Windows Workflow Foundation
documentation.

Solution:

Install
the latest version of MSDN to minimize broken links in the Speech Server
documentation.

Problem:

When I
type the tracking number into the Text Input box in Voice Response
Debugging Window, the CallRouter sample does not recognize it, even
though the sample recognizes the tracking number when I speak it.

When you
enter text from the keyboard, the speech recognition engine attempts to
construct words from the characters entered. If you want to enter acronyms or
single alphabetic characters from the keyboard, you need to follow each
character with a period ('.') character.

Solution:

Type a
period ('.') after each alphabetic character of the tracking number. For
example, if the tracking number is A-1234-Y, type the tracking number as
"A. one two three four Y.".

Problem:

When I
run a VoiceXML sample application, I hear an error message and the following
error is logged to the Application Event log:

The VoiceXml interpreter module encountered the
following error:

VoiceXML::Core::VXI:Failed to open URL

"http://localhost/VXMLRecordedPrompts/Default.aspx". Application
source:

http://localhost/VXMLRecordedPrompts/Default.aspx.

The
reason for this is that the virtual directories for the VoiceXML sample
applications are incorrectly configured.

Solution:

Resolve
this problem by performing the following steps:

1.   Click Start, click Administrative
Tools, and then click Internet Information Services (IIS) Manager.

2.   In the left pane, expand the
local machine, expand Web Sites, and then expand Default Web Site.

3.   Right-click the VoiceXML
application and then click Properties.

4.   Click the Directory Security
tab.

5.   Under Authentication and
Access control, click Edit.

6.   Under Authenticated access,
select the box labeled Integrated Windows authentication.

7.   Click OK twice.

8.   Repeat steps 3-7 for any other
VoiceXML sample application that you want to run.

Problem:

When
running the SupervisedTransfer sample application, I get a System.InvalidoperationException
when I enter any extra text in addition to a valid name in the askContactName
QA, for example, when I enter "John please".

The
reason for this is that the askContact QA uses the text of the
recognized result directly rather than using semantic values.

Solution:

Resolve
this problem by replacing the following block of Incorrect Code
with the following Replacement Code:

Incorrect Code

private
void askContactName_Closed(object sender, EventArgs e)

{

RecognitionResult result = this.askContactName.RecognitionResult;

if (result != null)

{

_contactName = result.Text;

_transferExtension =
LookupTransferNumber(_contactName, new Uri(ApplicationHost.LocalPath,
"Extensions.xml"));

this.supervisedTransfer.CalledParty =
_transferExtension;

this.supervisedTransfer.CallingParty =
this.TelephonySession.CallInfo.CallingParty.Uri.User;

}

}

Replacement Code

private
void askContactName_Closed(object sender, EventArgs e)

{

if (askContactName.RecognitionResult != null &&

this.askContactName.RecognitionResult.Semantics.ContainsKey("ContactNameContainer"))

{

_contactName =
askContactName.RecognitionResult.Semantics["ContactNameContainer"].Value.ToString();

_transferExtension =
LookupTransferNumber(_contactName, new Uri(ApplicationHost.LocalPath,
"Extensions.xml"));

this.supervisedTransfer.CalledParty =
_transferExtension;

this.supervisedTransfer.CallingParty =
this.TelephonySession.CallInfo.CallingParty.Uri.User;

}

}

Back to Top

Authoring
Tools and Application Development

Problem:

In Visual Studio while developing workflow or voice
application workflow applications, the "Windows Workflow" tab is
missing from the toolbox.

This can happen if C++ settings are the applied
settings.

Solution:

Resolve this problem by right-clicking the toolbox and
choosing Reset Toolbox from the context menu.

Problem:

Building a Visual Studio solution immediately after
having removed all pronunciations from the Custom Application Lexicon (CAL)
will cause a build error that prevents the application from running.

Solution:

Resolve this problem by clicking the Build button
on the CAL
editor user interface before using Visual Studio to build the project or
solution.

Problem:

Editing the Custom Application Lexicon (CAL) associated
with a grammar in the Conversational Grammar Builder does not cause the dirty
flag of the grammar to be set. The grammar needs to be rebuilt to absorb the
changes made in the CAL,
but the user is not informed of this via the dirty flag.

Solution:

Resolve this problem by rebuilding the Visual Studio
Solution or rebuilding the CGB grammar after every CAL editing session.

Problem:

Using the Custom Application Lexicon Editor to change
the pronunciation of a word appears to have no effect on whether or not that
word is highlighted as being acoustically similar to other words when I click
Check Acoustic Confusability in Simple Grammar Builder.

The reason for this is that during the acoustic
confusability test, the Custom Application Lexicon is not used, thus any
pronunciation modifications made in that lexicon are not reflected in the
test.

Solution:

There is no workaround for the acoustic confusability
test issue. However, when the grammar is used at runtime, the Custom
Application Lexicon is in fact employed and pronunciation edits are
accurately reflected.

Problem:

When I am using a Concept Recognition grammar that
employs several Concepts under a common Concept Answer I notice that
the resultant grammar requires more CPU to run effectively.

Explanation:

This is to be expected and is a consequence of the fact
that, typically, these grammars have an order of magnitude more training
sentences than the equivalent Keyword Answers, and therefore the
resultant Statistical Language Model generated is more complex.

Problem:

After renaming a nested custom activity on the workflow
canvas, the next instance of the nested custom activity fails to add.

Solution:

Resolve this problem by doing one of the following:

·
Save
and close the workflow file, then reopen the
workflow file before adding the next instance of the nested custom activity.

·
–OR–

·
Apply
the patch documented in KB
Article 932816.

Problem:

When an
application makes a speak request that specifies an audio source that cannot
be fetched (regardless of the reason), the alternate text will not be
rendered and the speak request will complete with an error having the
following inner exception:

Microsoft.SpeechServer.SpeechEngineServices.RequestFailedException

For
example, the following SSML contains a localhost reference to an audio source
file named "MyPrompt.wav":

<ssml:audio
src="http://localhost/MyPrompt.wav">

My alternative text.

</ssml:audio>

In this
example, if the audio source file does not exist, the alternate text "My
alternative text" will not be played.

Furthermore,
when an audio source reference cannot be fetched, the event log will contain
an error message similar to the following message:

Service was unable to download the audio file
http://localhost/MyPrompt.wav for the following reason: 'The remote server
returned an error: (404) Not Found. (System.Net.WebException)'. Until this
problem is corrected, any speak request that requires this file will fail.

Solution:

To
resolve this problem, do not rely on alternate text for audio source
references. If possible use a prompt database instead. If you need to use an
audio source reference in your prompt, you can simulate the alternate text
feature by replaying the prompt with the desired alternative text when a
speak error is encountered.

Problem:

Section
6.3.4 of the VoiceXML 2.0 specification (http://www.w3.org/TR/voicexml20/#dml6.3.4)
states that there are two types of barge-in available: speech or hotword.
The hotword type is not supported by the Speech Server VoiceXML
interpreter. If it is used in a VXML application, it will be ignored and no
error will be thrown.

Solution:

Resolve
this problem by removing instances of the hotword type in your
application.

Note  Removing instances of the hotword
type will cause barge-in behavior to default to the speech type of
behavior, which is described in the VoiceXML specification as follows:
"The prompt will be stopped as soon as speech or DTMF input is detected.
The prompt is stopped irrespective of whether or not the input matches a
grammar and irrespective of which grammars are active."

Problem:

When I
select Hang Up in the Voice Response Debugging Window while a
prompt is playing, the CallDisconnectedException does not appear to be
handled properly by the debugging session.

Solution:

Resolve
this problem by disabling the Enable Just My Code (Managed only)
debugging option in Visual Studio. To find this option, in Visual Studio
click Tools, click Options, and then click Debugging.

Problem:

In the
topic "64-Bit Issues" there is a procedure under the heading
"Debugging Managed Code Voice Response Applications on Windows
Vista." The documentation states that the Visual Studio 2005 Integrated
Development Environment (IDE) can time out when multiple instances of the
W3wp.exe process attempt to run without having correct permissions. Following
the procedure is supposed to prevent the problem. However, when I try to
perform step 5, I cannot find a %WINDIR%\Temp\SpeechWorkingFiles\Runtime directory.

Solution:

The
directory in question is not created until the problem that this procedure
was intended to prevent actually occurs. Wait for the problem to occur, and
then follow the procedure to prevent it from happening again.

Problem:

Debugging
an application over Remote Desktop works, but the use of direct audio input
via the microphone is not supported.

Solution:

Resolve
this problem by only using text or UI element input when debugging
applications over Remote Desktop.

Problem:

While debugging
an application on a computer running a 64-Bit operating system, when a call
is made with the debugger, I receive the following C runtime exception:

R6034 An application has made an attempt to load the C
runtime library incorrectly. Please contact the application's support team
for more information.

Solution:

Resolve
this problem by clicking OK and continuing. The application debugging
should continue without any further issues.

Problem:

When I
debug an application, I get an error message similar to the following:

Unable to attach to the process. Debugging cannot
continue. Unable to start debugging on the web server. The web server is not
configured correctly. See help for common configuration errors. Running the
web page outside of the debugger may provide further information.

This
problem is caused by the order in which Visual Studio and IIS are installed
relative to one another, and occurs only when IIS is installed after
installing Visual Studio.

Solution:

Reregister
ASP.NET. To re-register ASP.NET:

1.   From a command prompt window, run
the following command: systemroot\Microsoft.NET\Framework\ versionNumber
\aspnet_regiis -i

Note  With Windows Server 2003, you can
install ASP.NET using the Add or Remove Programs Control Panel.

2.   Insert the Visual Studio disc,
run the setup program, and select Repair/Reinstall. This step will create the
wwwroot$ share and add the appropriate permissions.

For more
information, see the MSDN topic Error: Unable to Start
Debugging on the Web Server.

Problem:

When I
debug my application, execution breaks after a wave file is submitted and
Speech Server throws the following exception:

Recording audio couldn't be completed: Failed to record
to file.

This
also happens when I try to use live audio for debugging instead of a wave
file.

Solution:

To
resolve this problem, temporarily disable calls to the EnableRetainAudio()
method on the SpeechRecognizer object while debugging your
application.

When
submitting either live audio or a wave file, the Speech Debugger internally
restarts the recognition process in order to confirm the text of the
recognition. Because the Speech Server API does not allow rerecording
to the file path specified in the call to EnableRetainAudio(),
it throws the above exception.

Back to Top

© 2007 Microsoft
Corporation. All rights reserved.