Handling key input from callers Blueworx Voice Response supports up to 16 keys on the telephone keypad: A, B, C, and D in addition to the twelve normal keys (1 through 9, *, 0, and #). Callers can press single keys (for example, to select options) or multiple keys (to enter data such as personal identification numbers).
Handling spoken input from callers Speech recognition means that you can write voice applications that take action based on spoken input from the caller.
SIP Telephony activity How Blueworx Voice Response interacts with the SIP telephony network.
Designing voice messaging applications You can create your own voice messaging applications or add voice messaging to existing applications. For example, in an ordering application, you may choose to let people leave a voice message to be associated with an order. This is known as transaction-related voice messaging.
Managing voice messaging resources This section describes how to create and maintain mailboxes, subscriber classes and distribution lists for use by a voice messaging application. Messages occupy disk space, and disk space usage must be monitored.
Background music Blueworx Voice Response includes a background music subsystem called the juke box, which you can use to play background music in your applications. This section tells you how to implement background music using the juke box:
TDM connection management TDM connection management helps to coordinate the making and breaking of time-division multiplex (TDM) connections between resources such as channels on packs, and channels on digital signal processor (DSP) adapters. Custom server subroutines allow you to write applications that exploit industry-standard time-division multiplex (TDM) bus (TDM bus) capabilities such as matrix switching, one-call fax, speech recognition, and text-to-speech.
Designing for a single system image Most voice applications will run without any changes on Blueworx Voice Response systems that are configured as a single system image. State tables, prompts, or custom servers that use application data (by, for example, playing or recording voice segments) do not need to be aware of whether or not they are running on a single system image: they will access that data in exactly the same way whether they are running on a stand-alone Blueworx Voice Response system, on a client node, or on a database server node. However, you should consider the following points when you design a voice application that will be run on a single system image: