Architecture Diagram: Design Time
Collapse the table of content
Expand the table of content
This documentation is archived and is not being maintained.

Architecture Diagram: Design Time

Speech Server 2007

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The following high-level diagram illustrates the Speech Server??components and the relationships between them as applied to the design stage of application development. This diagram assumes that the developer is running a single computer that contains Microsoft Visual Studio 2005, Speech Server, and a Web server.

The Session Initiation Protocol (SIP) peer represents all possible client endpoints.


The developer uses Visual Studio 2005 to create a speech application, choosing one of the following application types:

  • Voice Response Workflow Application ??? Choose this under New Project to create a managed code voice response application.
  • Voice Response Web Application ??? Choose this under New Website to create a SALT voice response application.
  • VoiceXML Speech Application ??? Choose this under New Website to create a VoiceXML application.

Following the Web model for which they are designed, SALT voice response applications and VoiceXML applications are deployed to the Web server. However, because the code that drives a managed code assembly from one state to the next is located on the computer running Speech Server, the assembly must be deployed to the computer running Speech Server itself.

After deploying the application, the developer tests it with a connected SIP peer or simulator.

© 2016 Microsoft